It is the technique of transferring in data from legacy system (NON-SAP) to SAP is called BDC.
There are two techniques available for transferring data.
Outbound process
Inbound process
OUTBOUND PROCESS:
The process of transferring the data from SAP to NON-SAP or another SAP server is called “Outbound Process”.
INBOUND PROCESS
The process of receiving the data from NON-SAP to SAP server is called as “Inbound Process”.
BDC is an “Inbound Process”.
DIFFERENT METHODS OF BDC:
Call transaction (Screen Level Processing)
Session method (Screen Level Processing)
Direct input method->(Standard SAP Programs)
LSMW -> (A tool)
CALL TRANSACTION METHOD:
It is the process of transferring the data from flat file into SAP by calling a transaction through a series of sequence of steps.
Properties:
This method is used for transferring less amount of data(<10,000 records).
This method uses Synchronous and Asynchronous updates.
This method will update the DB immediately.
We need to handle the errors and the success messages by declaring an internal table of type BDCMSGCOLL.
This method is very fast.
Syntax:
Call Transaction <Tcode>
Using <BDC DATA>
UPDATE <A/S>
MODE <A/E/N>
MESSAGES INTO <Message Internal Table>
BDC Data:
It is a structure defined in a data dictionary with the below fields.
Program -> Name of the program of a screen
Dynpro -> Screen number
Dynbegin -> Start the Process
Fnam -> Field name on the SAP screen
Fval -> Field value on to the field name of SAP screen
USE OF BDC DATA:
It is a structure which holds the information related to each screen i.e. program name, screen no, field name, field values, information of that particular screen to be transferred into the SAP.
BDC DATA
In simple words, it holds all the screen related information and field information to be transferred into corresponding SAP transaction.
BDC DATA
To find the above information for each field, press F1 on particular field
It will display help information.
Click on the button “technical information”
It will show the entire technical information of a screen.
Please note down the program name, screen number, screen field name.
This procedure has to be repeated for each field on a SAP screen.
Since, it is very difficult to note down the technical information for each field, we have an alternate and easy method called as “RECORDING METHOD”.
Update:
Update: There are two types of updates are available.
Asynchronous Update(COMMIT) : In this Mode, the called transaction passes the data to the UPDATE Work process and it does not wait for the update to be finished. It simply starts processing next record.
That is why, this is very fast.
It is not recommended for processing large amount of data, because the called transaction does not return any error message to the program if any error occurs.
It uses COMMIT statement internally.
Synchronous Update : In this Mode, , the called transaction passes the data to the UPDATE Work process and it waits for the update to be finished .
It is slower than asynchronous update; B’coz Called Transaction waits for update to be finished.
Here, The called transaction returns error message to the program if any error occurs.
DIAL0G WORK PROCESS: A work process which is dedicated to process screen information is called “Dialog work process”.
There will be 6 to 7 dialog work processes.
These dialog work processes are defined by basis consultant.
UPDATE WORK PROCESS: This work process is responsible for updating the data into the database.
There will be always only ‘1’ update work process.
ASYNCHRONOUS UPDATE (COMMIT):
In this type the call transaction screens will communicate with the update work process to update the data into database.
It doesn’t wait for the update to be finished.
It immediately starts to process the next record without waiting for the update to be finished.
That’s why this process is very fast.
It is generally not recommended for the large amount of data, because the called transaction doesn’t return any success or error messages.
SYNCHRONOUS UPDATE (COMMIT & WAIT):
In this mode, the called transaction communicates with the update work process to update the data into database.
It will wait for the update to be finished.
Once the update is finished, then it continues to process the next record.
That’s why this process is very slow.
It is generally recommended for large amount of data because it returns success and error messages.
MODE:
It specifies the type of the mode to execute the transaction.
There are 3 options for mode
___________________________________________________________
MODE DESCRIPTION
___________________________________________________________
A All screen mode (Foreground)
E Error screen mode (only error screens will be displayed)
N No screen mode (Background)
MESSAGES:
In the called transaction, we need to handle the messages by declaring an internal table of type BDCMSGCOLL.
All the messages will be stored in the above internal table.
The structure of BDCMSGCOLL is as below:
MSGTYP Message type(E-error, S-success W –Warning etc..)
MSGID Message ID
MSGNR Message number
MSGV1 Variable part of a message
MSGV2 Variable part of a message
MSGV3 Variable part of a message
MSGV4 Variable part of a message
The variable BDCMSGCOLL – MSGV1 will contain the created material number or vendor number whenever the message type is success (S).
Whenever the message type is error, we need to use the function module FORMAT_MESSAGE to display the meaningful message.
This is dummy text. It is not meant to be read. Accordingly, it is difficult to figure out when to end it. But then, this is dummy text. It is not meant to be read. Period.
ConversionConversion EmoticonEmoticon