Since it’s the holiday season, I hope y’all won’t mind that there haven’t been as many posts as normal. I’m trying to take a page from my favorite podcaster, Jack Spirko, and focus on my family this time of year. So that means, enjoying my time with them and taking a little break from work (not an easy thing for me).
Anyway, I hope everyone has a safe and fun New Year’s Eve and a relaxing New Year’s Day. Talk to you more next year 🙂
Since I’m working on training someone completely new to SAP and ABAP, I’m realizing there are a lot of tricks that I know that I take for granted. One of the things I realized was the ABAP Help On feature. It’s actually very good and often even includes sample code to show you how it looks.
This is the magic button. If you have some text highlighted, it will pull it directly into the next screen.
Now, there are a lot of options, but the most commonly used by me is the first option. enter in your keyword, take the defaulted index search and hit enter.
Now you get your result list. Find the best match and double click it.
it will come back with a good explanation, syntax diagrams, options you can attach, and sometimes sample code.
in addition, it drops you into the correct place in the help menu, so if you didn’t pick exactly what you needed, you might see it in one of the nearby menu options.
Anyway, basic to my expert readers out there, but if you don’t know much about ABAP, it could come in handy.
Thanks for reading,
I hope everyone has a great Christmas. Take this time to enjoy your family and loved one. I’m going to take a couple of days off and I’ll be back soon. I want to focus on my family during this great time of year, and I hope y’all do the same.
Remember why we all work so hard… for me it’s my family and love of the challenge… but always family first.
Merry Christmas.
When you use variant configuration, one of the things you often need or want to do is setup sales order costing for your configuration. Surprisingly to me, sales order costing is NOT setup automatically for the TAC item category. So let me walk you through how to set this up (at least as far as I can take you). Like so many things, you’ll need some input from your FICO expert to make sure all the settings are proper for their world 🙂
Now, I’m going to start at the beginning, so you might be able to skip this step, but I’m going to assume you don’t know the requirements class you need to update.
So, use this path to the IMG in order to find your requirements class based on your item category.
I’m going to show the standard Item Category, TAC for a configurable material. You can simply substitute your item category in here.
Now, it’s nice because you can see your requirements class at the bottom portion of this screen without backtracking to the requirements type screen.
We can get to the real work. We have to go to a little bit different spot in configuration to adjust these settings.
Now, using the requirements class we located earlier, we can go to the details.
Now, all the work happens on this screen. Originally, this screen was completely blank in standard SAP. What I’ve populated is the most standard configuration I’ve used in the past.
Costing: Setting this to X makes it required for sales order costing.
Costing ID: determines if you want automatic sales order costing (A) or automatic with marking (B).
Costing Method: (1) Product Costing, (2) unit costing
Costing Variant: PPC4 for sales order costing
CndTypLinItm: this is something optional, but it tells you where you can put the value within pricing if you wish to use it for margin or cost plus calculations
Acct Assignment Cat: M for Ind Cust wo KD-CO
Valuation: M Separate valuation with reference to Sales Document/Project.
Settlement Profile: SD1 – Sales Order Make to Order Production
The one field I skipped is the Settlement Profile. This one I always defer to my FICO person. I don’t even pretend to know which one of these to select.
Once you set this stuff, you should be good to.
Thanks for reading,
Well, we’ve created a program, and done the BDC recording. Now, all that’s left is the BDC ABAP Code to make it all useful. So, let’s jump right into it.
First off, you’ll need 2 FORMS and some standard data declarations:
DATA: BEGIN OF bdcdata OCCURS 100.
INCLUDE STRUCTURE bdcdata.
DATA END OF bdcdata.
DATA: mess TYPE TABLE OF bdcmsgcoll WITH HEADER LINE.
*———————————————————————*
* FORM BDC_DYN *
*———————————————————————*
* start a new screen in the BDC table *
*———————————————————————*
* –> PROGRAM *
* –> DYNPRO *
*———————————————————————*
FORM bdc_dyn USING program dynpro.
CLEAR bdcdata.
bdcdata-program = program.
bdcdata-dynpro = dynpro.
bdcdata-dynbegin = ‘X’.
APPEND bdcdata.
ENDFORM. “bdc_dyn
*———————————————————————*
* FORM BDC_FLD *
*———————————————————————*
* add a field to the BDC table *
*———————————————————————*
* –> FNAM *
* –> FVAL *
*———————————————————————*
FORM bdc_fld USING fnam fval.
CLEAR bdcdata.
bdcdata-fnam = fnam.
bdcdata-fval = fval.
APPEND bdcdata.
ENDFORM. “bdc_fld
Now, the actual transactional stuff that will change with every transaction…
FORM load_cnf.
REFRESH: BDCDATA, MESS.
PERFORM bdc_dyn USING ‘SAPLCORU’ ‘3000’.
PERFORM bdc_fld USING CORUF-AUFNR ‘ ‘4000100’.
PERFORM bdc_fld USING CORUF-VORNR ‘ ‘0010’.
PERFORM bdc_fld USING ‘BDC_OKCODE’ ‘=ENTR’. ” ENTER
PERFORM bdc_dyn USING ‘SAPLCORU’ ‘3200’.
PERFORM bdc_fld USING AFRUD-ISMNW_2 ‘ ‘2’.
PERFORM bdc_fld USING AFRUD-LEARR ‘ ‘SRV’.
PERFORM bdc_fld USING AFRUD-AUERU ‘ ‘’.
PERFORM bdc_fld USING AFRUD-LEKNW ‘ ‘’.
PERFORM bdc_fld USING ‘BDC_OKCODE’ ‘=MB03’. ” ENTER
PERFORM bdc_dyn USING ‘SAPLCOWB’ ‘0130’.
PERFORM bdc_fld USING ‘BDC_OKCODE’ ‘=WEIT’. ” ENTER
* runs transaction defined above, mode ‘A’ goes step by step, use this
* to prototype code, mode ‘N’ runs automatically, use this in
* production, mode ‘E’ generates errors only, use this for debug
COMMIT WORK AND WAIT.
CALL TRANSACTION ‘IW41’ USING bdcdata
MODE ‘A’ ” mode ‘A’,’N’,’E’
UPDATE ‘S’
MESSAGES INTO mess.
endform. “load_cnf
Now, the biggest piece to remember is the MODE. In the code above, it’s set to A, which means that it will go through step by step. When you execute, it will look something like this.
Beyond that, it’s all about translating the recording into the steps. You’ll notice that every screen must start with the bdc_dyn. The bdc_fld will be all the steps within that screen. At the end of each screen, you will add a BDC_OKCODE. This will be like hitting enter, or pressing a button. After ever BDC_OKCODE, you will do a bdc_dyn (even if you don’t leave the screen).
Beyond that, it’s all about entering in the data to populate the screen. Now something to keep in mind, it won’t always be sufficient to use the same data type as the screen field. For example, I did transaction IW41, and you have to enter in a number of time units (hours/mins/etc). I used the same data type, but when I executed the transaction, it told me that the values didn’t fit in the field… WTF?”. So i changed it to a text field to enter in the number, and magically it worked. Keep in mind, you may need to do tricks like that from time to time.
Hope you found this useful and thanks for reading,
Well, since I’ve been talking about BDC, seems logical that I should actually show you how to get a BDC Recording. It’s easier than you might expect, but reading the results can take some effort.
Use this menu path to start the BDC recorder.
Start a new recording.
Enter in your transaction, and a description. Then press Start Recording. Just to give you an idea, let’s walk through a simple recording.
Now, the biggest thing to keep in mind is to know the steps of your transaction, eliminate extra steps (don’t randomly hit enter) and make sure to populate every field you want to be able to populate in your program.
Fill in the values you want, and then press the Goods Movement Button.
Finally, press Save.
Now, you will get your results:
Now, the recording will give you this result:
0000 T IW41
SAPLCORU 3000 X
0000 BDC_CURSOR CORUF-VORNR
0000 BDC_OKCODE =ENTR
0000 CORUF-AUFNR 4000100
0000 CORUF-VORNR 10
SAPLCORU 3200 X
0000 BDC_CURSOR AFRUD-LEKNW
0000 BDC_OKCODE /00
0000 AFRUD-ARBPL SERVICE
0000 AFRUD-WERKS 1100
0000 AFRUD-ISMNW_2 28
0000 AFRUD-ISMNU H
0000 AFRUD-LEARR srv
0000 AFRUD-BUDAT 12/06/2013
0000 AFRUD-AUERU
0000 AFRUD-LEKNW
0000 AFRUD-OFMNU H
0000 AFRUD-ISDD 01/11/2013
0000 AFRUD-ISDZ 07:00:00
0000 AFRUD-IDAUE H
0000 AFRUD-IEDD 12/06/2013
0000 AFRUD-IEDZ 23:31:37
0000 AFRUD-PEDZ 24:00:00
SAPLCORU 3200 X
0000 BDC_CURSOR AFRUD-ARBPL
0000 BDC_OKCODE =MB03
0000 AFRUD-ARBPL SERVICE
0000 AFRUD-WERKS 1100
0000 AFRUD-ISMNW_2 28
0000 AFRUD-ISMNU H
0000 AFRUD-LEARR SRV
0000 AFRUD-BUDAT 12/06/2013
0000 AFRUD-OFMNU H
0000 AFRUD-ISDD 01/11/2013
0000 AFRUD-ISDZ 07:00:00
0000 AFRUD-IDAUE H
0000 AFRUD-IEDD 12/06/2013
0000 AFRUD-IEDZ 23:31:37
0000 AFRUD-PEDZ 24:00:00
SAPLCOWB 0130 X
0000 BDC_OKCODE =WEIT
0000 BDC_SUBSCR SAPLCOWB 0806HEADER
0000 BDC_SUBSCR SAPLCOWB 0510TABLE
0000 BDC_CURSOR COWB_COMP-ERFMG(01)
Now, this will translate into the following ABAP code. In a future post, I’ll give you the simple bdc_dyn and bdc_fld form code.
PERFORM bdc_dyn USING ‘SAPLCORU’ ‘3000’.
PERFORM bdc_fld USING CORUF-AUFNR ‘ WA_CNF-AUFNR.
PERFORM bdc_fld USING CORUF-VORNR ‘ WA_CNF-VORNR.
PERFORM bdc_fld USING ‘BDC_OKCODE’ ‘=ENTR’. ” ENTER
PERFORM bdc_dyn USING ‘SAPLCORU’ ‘3200’.
PERFORM bdc_fld USING AFRUD-ISMNW_2 ‘ WA_CNF-TIME.
PERFORM bdc_fld USING AFRUD-LEARR ‘ WA_CNF-LEARR.
PERFORM bdc_fld USING AFRUD-AUERU ‘ WA_CNF-AUERU.
PERFORM bdc_fld USING AFRUD-LEKNW ‘ WA_CNF-LEKNW.
PERFORM bdc_fld USING ‘BDC_OKCODE’ ‘=MB03’. ” ENTER
PERFORM bdc_dyn USING ‘SAPLCOWB’ ‘0130’.
PERFORM bdc_fld USING ‘BDC_OKCODE’ ‘=WEIT’. ” ENTER
* runs transaction defined above, mode ‘A’ goes step by step, use this
* to prototype code, mode ‘N’ runs automatically, use this in
* production, mode ‘E’ generates errors only, use this for debug
COMMIT WORK AND WAIT.
CALL TRANSACTION ‘IW41’ USING bdcdata
MODE ‘N’ ” mode ‘A’,’N’,’E’
UPDATE ‘S’
MESSAGES INTO mess.
That’s it for today. The recording is pretty easy. Using it, well, I’ll get to that soon 🙂
Thanks for reading,
Continuing on my training of an intern, one of the things I need is a series of BDC programs to automatically generate data within my test systems. While, there are a lot of ways to make transactional data, I need something that I can “fire and forget”. So that means I need programs with either a BAPI or BDC. In my opinion, for this, I want simple and I want quick, so I’ve gone down the BDC path. So… I’m using it as a training opportunity for my intern. Today, I’m going to focus on simply copying an existing program. I know it sounds simple, but hey, not everyone is an ABAP expert. That’s what I”m going to be sharing with y’all today 🙂
Now, since I’ve already developed a few of these (I’m working my way through the in-house repair process), the easiest way is to copy from an existing one.
This program will be to generate service order confirmations.
Now, the next question is if you want to copy all the attached pieces of the program. In general, I say yes, but obviously, this depends on your goal.
Now, the transport portion. This may depend on your system and your plans. For me, I want to make sure I can transport this forward, but perhaps you’re just playing. In that event, skip the package, and just select Local Object
But, if you choose a transportable object, you’ll need to create a transport.
Give it a description, press Save.
Now your transport is listed, press the green check to accept it.
Finally, we just need to make some minor updates, like the program title. Select Attributes and Press Change.
Change the title and press Save.
Normally, I’ll change the boilerplate as well.
Once I add the information to boiler plate, you can activate it, and even execute it if you choose (granted, it’ll execute the program you copied, but at least you can be sure syntax is good to go).
There you go… how to properly copy an ABAP program.
Thanks for Reading,
Well, it occurred to me. I have a new intern, and he knows nothing about SAP or ABAP. So I’m having to go back to the beginning to try to get him in the swing of things. So, I thought I’d start throwing some of the things I’m teaching him out here. Who knows? maybe it’s useful to some of you out there too 🙂 Today I’m going back to the very basics. Finding field and type from a screen.
For this example, I’m using transaction IW41
Highlight the field you want information on.
Press the technical details button.
This magical screen gives you quite a bit of information. Typically, Field Name and Data Type are the most valuable. Occasionally, you can even get the Table name. In a future post, I’ll talk about digging further when this screen only gives you a structure (which happens quite often).
Thanks for reading,
Ok… now I finally got to the really important stuff for me. I have a configuration table that tells how columns are available, and how they sequenced by default. So obviously, if I’m going to use the ALV simple table versus the “standard” Table Class, I need to control the ALV Table Columns, this includes sequence, visibility and column header text.
So, again, I’m doing all of this in the WDDOINIT method, since it’s a one time read. Here’s how you can do it yourself.
data lo_cmp_usage type ref to if_wd_component_usage.
DATA lo_INTERFACECONTROLLER TYPE REF TO IWCI_SALV_WD_TABLE .
DATA lv_value TYPE ref to cl_salv_wd_config_table.
*** instantiate the component
lo_cmp_usage = wd_this->wd_cpuse_alv_comp( ).
if lo_cmp_usage->has_active_component( ) is initial.
lo_cmp_usage->create_component( ).
endif.
lo_INTERFACECONTROLLER = wd_this->wd_cpifc_alv_comp( ).
*** get the ALV table
lv_value = lo_interfacecontroller->get_model( ).
** first, get all of the columns from the table.
lt_cols = lv_value->if_salv_wd_column_settings~get_columns( ).
READ TABLE lt_cols INTO ls_cols with key ID = <TABLE FIELD NAME>.
*** For visibility, you the following values
* WHen ‘VISIBLE’
lv_vis = ’02’.
* when ‘INVISIBLE’.
lv_vis = ’01’.
ls_cols-r_column->set_visible( lv_vis ).
*** set the sequence of the columns
lv_seq = lv_sequence.
ls_cols-r_column->set_position( lv_seq ).
*** Set the header text and tooltip
ls_col_hdr = ls_cols-r_column->get_header( ).
lv_col_text = lv_text.
ls_col_hdr->set_text( lv_col_text ).
ls_col_hdr->set_tooltip( lv_col_text ).
Of course, you can loop through and find your values from anywhere. The important thing to notice is that it’s pretty simple. Especially in comparison to the process I was using that had to delete a column and re-add it in order to sequence it properly. This is a lot less involved. So far, I haven’t found anything that I do that would force me away from the ALV Table. I guess I’ll see what happens, but I may start converting my SM Portal to the ALV Tables. The processing time doesn’t seem bad, so if you happen to know why the “standard” vs SALV table is preferable, I’d love to hear from you.
As always, Thanks for reading,
Well, the next phase of my journey was the ABAP Web Dynpro ALV Table Settings. I wanted to control things like the number of rows to display, what buttons should be available etc…
So after a little more research, I found that is pretty easy to do too.
Again we go to the WDDOINIT and add the follow code (or something like it ).
data lo_cmp_usage type ref to if_wd_component_usage.
DATA lo_INTERFACECONTROLLER TYPE REF TO IWCI_SALV_WD_TABLE .
DATA lv_value TYPE ref to cl_salv_wd_config_table.
*** instantiate the component
lo_cmp_usage = wd_this->wd_cpuse_alv_comp( ).
if lo_cmp_usage->has_active_component( ) is initial.
lo_cmp_usage->create_component( ).
endif.
lo_INTERFACECONTROLLER = wd_this->wd_cpifc_alv_comp( ).
*** get the ALV table
lv_value = lo_interfacecontroller->get_model( ).
*** Set Table Buttons and attributes
lv_value->IF_SALV_WD_TABLE_SETTINGS~SET_SCROLLABLE_COL_COUNT( value = 10 ).
lv_value->IF_SALV_WD_STD_FUNCTIONS~SET_EXPORT_ALLOWED( value = abap_false ).
lv_value->IF_SALV_WD_STD_FUNCTIONS~SET_PDF_ALLOWED( value = abap_false ).
this particular example turns off the print button (PDF Allowed), turns off the Export button (Export_Allowed), and sets the scrollable column count = 10. Just because my particular table could be 100 columns wide. So I want it to render nicely, and 10 is a pretty good number of columns. In addition, I’m leaving the settings button available, so a user can make his own settings if he doesn’t like my default. I really like this ALV stuff 🙂
Alright, back to it. Thanks for reading,