Have you ever wondered that what BDC is? Ive never thought what BDC stands for!

I knew that it is related with batch inputs. Here it is what BDC stands for Batch Data Communication. If you have generated a batch input program, the following function modules are automatically assigned the correct values. If you want to write your own program, proceed as follows: 1. 2. Generate the batch input session using function moduleBDC_OPEN_GROUP The proceed as follows for each transaction that session contains: 3. 1. In the BDCDATA structure, enter the value for all screens and fields that must be processed in the transaction. 2. Use BDC_INSERT to transfer the transaction and BDCDATA structure to the session. 4. 5. Close the batch input session with BDC_CLOSE_GROUP Start to process the generated session.

BDC_OPEN_GROUP
Use the BDC_OPEN_GROUP function module to create a new session. Once you have created a session, then you can insert batch input data into it with BDC_INSERT. You cannot reopen a session that already exits and has been closed. If you call BDC_OPEN_GROUP with the name of an existing session, then an additional session with the same name is created. A batch input program may have only one session open at a time. Before opening a session, make sure that any sessions that program closes any sessions that it previously had opened.

BDC_OPEN_GROUP takes the following EXPORTING parameters:

CLIENT Client in which the session is to be processed. Default: If you dont provide a value for this parameter, the default is the client under which the bathc input program runs when the session is created. GROUP Name of the session that is to be created. May up to 12 characters long. Default: None. You must specify a session name. HOLDDATE Lock date. The session is locked and may not be processed until after the date that you specified. Only a system administrator with the LOCK authorization for the authorization object Batch Input Authorizations can unlock and run a session before this date. KEEP Retain session after successful processing. Set this option to the value X to have a session kept after it has been successfully processed. A session that is kept remains in the input/output queue until an administrator deleletes it. Sessions that contain errors in transactions are kept even if KEEP is not set. Default: If not set, then sessions that are successfully processed are deleted. Only the batch input log is kept. USER Authorizations user for background processing. This is the user name that is used for checking authorizations if a session is started in background processing. The user must be authorized for all of transactions and functions that are to be executed in a session. Otherwise, transactions will be terminated with no authorization errors. The user can be of type dia log or background. Dialog users are normal interactive users in the R/3 System. Background users are user master records that are specially defined for providing authorizations for background processing jobs.

BDC_INSERT
Use the BDC_INSERT function module to add a transaction to a batch input session. You specify the transaction that is to be started in the call to BDC_INSERT. You must provide a BDCDATA structure that contains all of the data required to process the transaction completely.

BDC_INSERT takes the following parameters:

TCODE The code of the transaction that is to be run. POST_LOCAL Parameter to update data locally. If POST_LOCAL = X, data will be updated locally. DYNPROTAB The BDCDATA structure that contains the data that is to be processed by the transaction. DYNPROTAB is a table parameter in the function module.

BDC_CLOSE_GROUP
Use the BDC_CLOSE_GROUP function module to close a session after you have inserted all of your batch input data into it. Once a session is closed, it can be processed. BDC_CLOSE_GROUP needs no parameters. It automatically closes the session that is currently open in your program. You must close a session before you can open another session from the same program.

BDCDATA Structure
IF you want to write data to a batch input session or to process the data using CALL TRANSACTION USING or CALL DIALOG, you must prepare an internal table <bdc_tab>. This internal table must be

structured according to ABAP Dictionary structure BDCDATA. The internal table <bdc_tab> stores the data that is to be entered into R/3 System and the actions that are necessary to process data. You can think of the table as storing the script that the R/3 System is to follow in processing batch input data.