ppt_conv

10
CALL TRANSACTION VS SESSION METHOD

Transcript of ppt_conv

Page 1: ppt_conv

CALL TRANSACTION VS

SESSION METHOD

Page 2: ppt_conv

BDC (BATCH DATA COMMUNICATION)It is the oldest batch interfacing technique that SAP provided since the early versions of R/3.

Requirement: - For Developing BDC, we need Recording & flat file in which the data is stored. Flat file can be Text file or Excel File.

Types: It has two types:

1. CALL TRANSACTION METHOD.2. SESSION METHOD.

Page 3: ppt_conv

Data transfer program structure– Declare primarily two internal tables, one to store the

uploaded file data and the other to store the screen flow data.

– Upload the file data– Check for any pre-validations– Populate the BDC data– Call the required data transfer method– Handle any errors– Repeat steps 4–6 for all the records in the file– display audit report

Page 4: ppt_conv

Populating BDC data

Populate the Internal table, which is similar to BDCDATA structure detailing the values to be passed to the screen fields and the sequence in which the screen functions are to be performed

Structure of BDCDATA : • PROGRAM - BDC module pool• DYNPRO- BDC Screen number• DYNBEGIN- BDC screen start• FNAM- Field name• FVAL- BDC field value

Page 5: ppt_conv

In BDC we use structure BDCDATA for Batch Input, Which has following components.

• PROGRAM - BDC module pool• DYNPRO- BDC Screen number• DYNBEGIN- BDC screen start• FNAM- Field name• FVAL- BDC field value

Page 6: ppt_conv

BDC Using Session MethodIn this method you transfer data from internal table to database table through sessions using the following function modules in the program– Bdc_open_group :

• Client• Group: Name of the session• Lock date: The date on which you want to process the session.• Keep: This parameter is passed as ‘X’ when you want to retain session after

processing it or ‘ ‘ to delete it after processing• User-Authorized user

– Bdc_insert• Tcode: Transaction name• Dynprotab: BDCDATA internal table

– Bdc_close_group

Page 7: ppt_conv

Function modules for BI program

Page 8: ppt_conv

Session overview — Tcode SM35

Page 9: ppt_conv

Call transaction Vs. session method

Call transaction Session

Immediate updation in database table Data is not updated in database table unless session is processed

Sy-subrc is returned No sy-subrc is returned

Errors need to be handled explicitly Error log is created for error records

Updation in database table can be synchronous or asynchronous

Updation in database table is always synchronous

Call transaction exclusively for small amount of data

Session method supports both small amount of data as well as large amount of data

Page 10: ppt_conv

Call transaction Session

Processing is slow. Processing is faster.