Prologue to Batch input
Cluster input is commonly used to move information from non-R/3 frameworks to R/3 frameworks or to move information between R/3 frameworks.An information move strategy permits you to move datasets naturally to screens having a place with exchanges, and subsequently to a SAP framework. Clump input is constrained by a bunch input meeting.In this instructional exercise you will learn:
Clump input meeting
Bunches a progression of exchange assembles with input information and client activities . A clump input meeting can be utilized to execute a discourse exchange in cluster input, where some or every one of the screens are handled by the meeting. Group input meetings are put away in the data set as data set tables and can be involved inside a program as inward tables while getting to exchanges.
Focuses to note
BDI works via completing typical SAP exchanges similarly as a client would however it execute the exchange automatically.All the screen approvals and business rationale approval will be finished while utilizing Batch Data Input.It is reasonable for entering huge measure of information.No manual cooperation is requiredTechniques for Batch InputSAP give two essential strategies to moving heritage information in to the R/3 System.
Traditional Batch Input strategy
In this strategy an ABAP/4 program peruses the outside information to the SAP System and stores in a cluster input meeting.
In the wake of making the meeting, you can run the meeting to execute the SAP exchange in it.
This strategy utilizes the capability modules BDC_ OPEN, BDC_INSERT and BDC_CLOSE
Clump Input Session can be process in 3 ways
In the closer view
Behind the scenes
During handling, with mistake show
You ought to deal with bunch input meetings in the frontal area or utilizing the mistake show if you have any desire to test the information move.
To execute the information move or test its presentation, you ought to handle the meetings behind the scenes.
Focuses to note about Classical Batch Input strategy
Move information for various exchanges.
Simultaneous information base update.
A group input process log is produced for every meeting.
Meeting can't be produced in equal.
You will regularly notice the accompanying grouping of moves toward foster Batch Input for your association
Investigation of the inheritance information. Decide how the information to be moved is to be planned in to the SAP Structure. Additionally observe fundamental information type or information length changes.
Create SAP information structures for involving in send out programs.
Send out the information in to a consecutive record. Note that character design is expected by predefined SAP group input programs.
In the event that the SAP provided BDC programs are not utilized, code your own clump input program. Pick a fitting clump input strategy as indicated by the circumstance.
Process the information and add it to the SAP System.
Break down the interaction log. For the CALL TRANSACTION strategy, where no legitimate log is made, utilize the messages gathered by your program.
From the aftereffects of the cycle investigation, right and go back over the wrong information.
Composing BDC program
You might notice the accompanying system to compose your BDC program
Dissect the transaction(s) to deal with clump input information.
Settle on the cluster input strategy to utilize.
Peruse information from a consecutive document
Perform information transformation or mistake checking.
Putting away the information in the clump input structure,BDCDATA.
Produce a group input meeting for old style clump input,or process the information straightforwardly with CALL TRANSACTION USING explanation.
Making Batch Input Session
Open the bunch input meeting utilizing capability module BDC_OPEN_GROUP.
For every exchange in the meeting:
Fill the BDCDATA with values for all screens and fields handled in the exchange.
Move the exchange to the meeting with BDC_INSERT.
Close the cluster input meeting with BDC_CLOSE_GROUP
Group Input Recorder
Group input recorder (System > Services > Batch input > Recorder) records exchanges which are physically placed and makes a cluster input meeting which can be executed later utilizing SM35.