on ‎2007 Dec 29 10:58 AM
Request clarification before answering.
Hi,
Batch input-Batch input is a standard technique for transferring large sets of data into the SAP System. The transaction flow is simulated and the data is transferred as if it were entered online. The advantage of this is that all relevant checks of the transaction are executed, thereby ensuring that the data is consistent.
The batch input process is divided into two steps:
The data transfer program creates a batch input session that contains all the relevant data. The batch input session is processed and the data it contains is transferred into the SAP System. The Data Transfer Workbench only executes step 1.
The majority of SAP standard data transfer programs use the batch input technique. The data transfer program creates a batch input session which is processed later. Batch input sessions can be processed in various ways:
In the foreground
In the background
During processing, with error display
You should process batch input sessions in the foreground or using the error display if you want to test the data transfer. If you want to execute the data transfer or test its performance, process the sessions in the background.
=============================================
Purpose-Batch input is one of the primary ways in which data can be transferred into the R/3 System. Batch input is used for bulk data transfers and not for near real-time data transfers.
Typical uses of batch input include the one-time import of data from a legacy system into a newly installed R/3 System. Another typical use is for periodic (hourly, daily...) transfers of data from external systems or legacy systems that are still in use into R/3, where all enterprise data is consolidated.
For the system administrator, batch input usually requires minimal attention, only a periodic check to make sure all batch input sessions have been processed successfully. In the event of an error in a session, then the responsibility for triggering the error analysis and correction of the problem usually lies with the system administrator. Detailed analysis of the problem will require the help of the department or specialist responsible for the data to be entered. Incorrect entries in an R/3 financials transaction in a session, for example, have to be evaluated and corrected by the book-keeping department.
The process description here explains the typical workflow in batch-input operation from the point of view of the system administrator.
Prerequisites-The R/3 applications deliver many programs for batch input that are ready to use. Sometimes, however, a customer must write his or her own batch input program in order to convert data from a legacy system or from a proprietary format into an R/3 data format.
Batch input operation occurs only if a customer explicitly sets its up. The customer must activate a program that prepares a batch input session and that delivers it to the R/3 System.
============================================
Batch input sessions enter data non-interactively into an R/3 System. Batch input is typically used to transfer data from non-R/3 Systems to R/3 Systems or to transfer data between R/3 Systems.
This section describes how to manage batch input sessions.
To reach the main menu of the batch input system, select System->Services-> Batch input. Alternatively, enter transaction SM35.
Hope this makes things clear. Please assign points.
Rgds
Manish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 32 | |
| 16 | |
| 7 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.