Call Transaction in BDC

How to use CALL TRANSACTION to submit BDC in different modes. This technique is very useful for mass data upload to SAP system from external data sources. Lets assume that external data is what user enters in the selection screen.

Program designed to change the delivery date of the sales order line items according to selection using the transaction va02.
Note that landscape is SAP AFS vertical.
Main steps in creating a BDC program
  1. Record BDC using transaction SHDB.

  2. Create driver program and application logic class.

Step 1:Record BDC using transaction SHDB.

Go to transaction SHDB and select “New Recording”
Select the recording options and set the names
Start recording
Save the recording. Remove unwanted elements from the recording
Identify the parameters that need to be set from driver program (eg: sales order no and del. date which is marked in red)

Step 2:Create driver program and application logic.

Driver Program: ZTEST_VA02_DRIVER
Application logic class: ZCL_VA02_BDC
Set select parameters
Set BDC data
Fill BDC dynpro
Fill BDC field
Call transaction
N – Do not display dynpro
E – Show dynpro on error only
A – Show all dynpro
Update is set to “L” which implies as local.
All the messages that is returned from the transaction while executing will be imported to internal table GI_BDC_RETURN.

4 thoughts on “Call Transaction in BDC

  1. ankur says:

    could you please elaborate more in BDC for mm side like uploading material master through BDC call transaction and about EDI in purchase order. that would great you

  2. Kevin says:

    BDC will not run in E or A mode with SAP versions 7.5 or 7.6. In addition, in N mode, the return message is always “Changes Complete” and will not return actual message when there is an error. Have you had similar issues?

Leave a Reply

Your email address will not be published. Required fields are marked *