0% found this document useful (0 votes)

88 views10 pages

Call Transaction VS Session Method

This document compares two methods for batch data communication (BDC) in SAP: the call transaction method and the session method. The call transaction method immediately updates the database table but only supports small amounts of data. It returns a SY-SUBRC error code. The session method loads data into sessions and updates tables asynchronously in batches, supporting both small and large amounts of data. It creates an error log instead of returning SY-SUBRC. The session method is generally faster than the call transaction method as it allows asynchronous, batched updates to the database versus the immediate updates of the call transaction method.

Uploaded by

shruti5488

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PPTX, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

88 views10 pages

Call Transaction VS Session Method

Uploaded by

shruti5488

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PPTX, PDF, TXT or read online on Scribd

You are on page 1/ 10

CALL TRANSACTION VS SESSION METHOD

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.

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 46 for all the records in the file display audit report

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

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

BDC Using Session Method

In 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

Function modules for BI program

Session overview Tcode SM35