BDC recording from testing client to development client

This method would be useful, when you don’t have required datum in development client and when you have same in testing client and you want to BDC recording with that datum.  

Login to the Testing client where you will have data.

Go to transaction SHDB and press new recording.  

As an instance, here we will try to modify vendor’s postal code of his address.  So, give FK02 as the transaction code to be executed and give recording name like ‘ZRECORD’. 

  

Now it goes to Vendor master update screen. Opt a vendor and click the address checkbox and press enter.

  

It will show the vendor’s address information.  

Now change the existing PIN code 700019 to 560076 and press save. It will take you to the recording screen.  

Now you cannot create a program with this recording information in testing client. So, import your recording information to one presentation server file. Press import button.

Give a text file name and save it in the presentation server.  

Then Go to SHDB transaction in development client and go to new recording. Give the recording name as ZRECORDINGNEW and opt the same vendor master updation transaction code FK02. 

  

In this case your development client should have at least one vendor. If not create it and input the vendor in FK02 transaction and as you did earlier select the address checkbox.  

  

It will show you the address information. You don’t change anything in that and come back. Because this is not the vendor to whom we are going to change his PIN Code.  

Now it will show you the recording information. Delete all the recording information and press the import button and browse bdc_recording file from the presentation server.  

 

 

The previous recording information will loaded in to BDC recording and go back from the screen. It would popup for saving the recording. Now save that recording.  

 

  

Select the recording and press ‘program’ button. It will popup for new program creation. Input the required details and the expected BDC recording program will get created.  

 

    

report ZVENDORUPDATE
       no standard page heading line-size 255.include bdcrecx1.

start-of-selection.perform open_group.perform bdc_dynpro      using 'SAPMF02K' '0106'.perform bdc_field       using 'BDC_CURSOR'
                              'RF02K-LIFNR'.perform bdc_field       using 'BDC_OKCODE'
                              '/00'.perform bdc_field       using 'RF02K-LIFNR'
                              'B002568'.perform bdc_field       using 'RF02K-D0110'
                              'X'.perform bdc_dynpro      using 'SAPMF02K' '0110'.perform bdc_field       using 'BDC_CURSOR'
                              'LFA1-PSTLZ'.perform bdc_field       using 'BDC_OKCODE'
                              '=UPDA'.perform bdc_field       using 'LFA1-NAME1'
                              'MURARI SHARAN SRIVASTAVA'.perform bdc_field       using 'LFA1-SORTL'
                              '000568'.perform bdc_field       using 'LFA1-STRAS'
                              'Brook House, Shakespeare Sarani'.perform bdc_field       using 'LFA1-ORT01'
                              'Kolkatta'.perform bdc_field       using 'LFA1-PSTLZ'
                              '560076'.perform bdc_field       using 'LFA1-LAND1'
                              'IN'.perform bdc_field       using 'LFA1-REGIO'
                              '25'.perform bdc_field       using 'LFA1-SPRAS'
                              'EN'.perform bdc_transaction using 'FK02'.perform close_group.



CALL TRANSACTION 

Display mode

• CTU: either CALL TRANSACTION ... USING ... MODE <dismode> ..., or ls_ctu_params-dismode = <dismode>. CALL TRANSACTION ... USING ... OPTIONS FROM ls_ctu_params ...
• BI session: you can choose it only by running the session interactively (SM35), a popup dialog is displayed with many options.

dismode	Meaning
N	Screens are not displayed. You must choose this mode when you run the BDC in a background job.
A	All screens are displayed. On each screen, a little popup is displayed with the next recorded function, the user has to press Enter to execute it.
E	By default, screens are not displayed, except if an error occurs, or if the end of BDC data is reached although the recorded transaction was not exited
P	Same as N. The difference is that if a breakpoint is reached and the classic debugger is used, then P will avoid the error 00344 concerning screen SAPMSSY3 0131 (or other SAPMSSY3 screen). For more information, see Note 72551 CALL TRANSACTION USING and DEBUGGER. Since the new debugger has been introduced, mode P is more or less obsolete
Others	Like A

Since SAP WAS 6.10, there are 4 additional execution modes, for more information see note 433137 - Batch input: Simulating background mode:

dismode	Meaning
Q	Same as N + the execution is run with SY-BATCH = 'X'
D	Same as A + the execution is run with SY-BATCH = 'X'
H	Same as E + the execution is run with SY-BATCH = 'X'
S	Same as P + the execution is run with SY-BATCH = 'X'

Update mode

It indicates how the function modules in the update task will be run.

• CTU: either CALL TRANSACTION ... USING ... UPDATE <updmode> ..., or ls_ctu_params-updmode = <updmode>. CALL TRANSACTION ... USING ... OPTIONS FROM ls_ctu_params ...
• BI session: you can choose it only by running the session interactively (SM35), a popup dialog is displayed with many options.

updmode	Meaning
A	Asynchronous. Update function modules are executed in UPD workprocess. A is the default mode.
S	Synchronous. Update function modules are executed in UPD workprocess BUT all COMMIT WORK are processed as if they were COMMIT WORK AND WAIT.
L	Local update task. Update function modules are executed as if SET UPDATE TASK LOCAL has been executed at the start of each LUW, i.e. they are executed in the same workprocess as the main program.