|
Explain what is batch input session in SAP.
Menu Path: System > Services -> Batch Input -> Sessions
1) What should be the approach for writing a BDC program? 1. Analyzing data from local file. 2. Analyzing transaction 3. Declaring internal table - First Internal table similar to structure like local file - Declaring internal table like BDCDATA 4. Transferring data from local file to internal table 5. Population of BDCDATA. From Internal table the data is transferred to database
table by two ways. I.e. Session method or Call transaction.
2) What is a batch input session? In this method you transfer data from internal table to database table through sessions. In this method an ABAP/4 program reads the external data that is to be entered in the SAP system and stores the data in a session. A session stores the actions that are required to enter your data using normal SAP transactions. I.e. Data is transferred to session, which in turn transfer data to database table. Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e. Data for screen fields to which screen it is passed, the program name behind it, and how next screen is processed. When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system. Unless session is processed, the data is not transferred
to database table.
3) What is the alternative to batch input session? Call Transaction Method
The transaction for background processing is SM36. Defining background jobs. It is two steps process
If batch-input session is terminated with errors, it appears in the list of INCORRECT session and it can be processed again. To correct session, first you can analyze the session. The analysis function allows to determine which screen and value produced error. If you find small errors in the data, you can correct them interactively, otherwise you need to modify batch input program, which are generated the session or many times even the data file. While batch input is a two-step procedure, call transaction
does both steps online one right after the other. In this method, you call
a transaction from your program.
6) What are the fields in a BDC_Tab Table?
BDCTAB is like BDCDATA. The fields are 1. Program: Name of module pool program associated with the screen set this field only for the first record for the screen. 2. Dynpro: Number of the screen. Length(4). Set this field only in the first record for the screen. 3. Dynbegin: Indicates the first record for the screen. Length(1). Set this period to X only for the first record for the screen. (Reset to blank for all other records). 4. Fnam: Name of a field in the screen. Length(35). The Fnam field is not case-sensitive. 5. Fval: Value for the field named in Fnam. Length(132). The fval field is case-sensitive. Values assigned to this field are always padded on the right if they are less than 132 characters. Values must be in character format.
If batch-input session is terminated with errors, it appears in the list of INCORRECT session and it can be processed again. To correct session, first you can analyze the session. The analysis function allows to determine which screen and value produced error. If you find small errors in the data, you can correct them interactively, otherwise you need to modify batch input program, which are generated the session or many times even the data file.
BDC Data.
You should use write to statement to a character field.
10) What is difference between Batch input Method and Call Transaction? 1. Tables get updated only when the session is processed.
2. No sy-subrc is returned incase of session method
3. Errors log is created for error records.
4. Updation in database table is always synchronous in
case of session method.
|
|
Related ABAP Topics:
More ABAP Tips
SAP ERP Modules, Basis, ABAP and Other IMG Stuff All the site contents are Copyright © www.erpgreat.com
and the content authors. All rights reserved.
|