Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

regarding BDC

Former Member
0 Kudos
93

Hi folks,

I wud like know the diff b/w call transaction method n session....plz

5 REPLIES 5

RichHeilman
Developer Advocate
Developer Advocate
0 Kudos
62

CALL TRANSACTION will run in the current work process, hence locking up the dialog process. Using BI Session, allows you to run the session totally in the background via a background task.( You could run in foreground also) The session also provides logs and error messages. One nice thing about sessions is, say you have 100 transactions in the session, and 5 of them have errors, if you re-run the session, it will only process the 5 transaction which had an error, and not the entire run.

Regards,

Rich Heilman

Former Member
0 Kudos
62

Hi Rajesh ,

Following are some points of diffrence between session and call transaction method based on How databse is updated and how errors are handled

1.How database is updated:-

In Batch Input session , sap databse is updated during processing of the bach input session , while in Call transaction/Dialog method , the databse is updated as per execution of the of the batch input program.

2. How errors are handled:- In session method arrors are handled automatically by the system during the processing odf the session.These erros are kept there and if u run this session again then only erros are processed.

While in Call transcation method , erros are not handled by system , they must be handled manually.If u run proagram for this case, process starts from scratch.

Regards

Former Member
0 Kudos
62

Hi Rajesh ,

Following are some points of diffrence between session and call transaction method based on How databse is updated and how errors are handled

1.How database is updated:-

In Batch Input session , sap databse is updated during processing of the bach input session , while in Call transaction/Dialog method , the database is updated as per execution of the of the batch input program.

2. How errors are handled:- In session method arrors are handled automatically by the system during the processing odf the session.These erros are kept there and if u run this session again then only erros are processed.

While in Call transcation method , erros are not handled by system , they must be handled manually.If u run proagram for this case, process starts from scratch.

Regards

Note: Reward if useful

Former Member
0 Kudos
62

Hi Rakesh,

Just check these links.

BDC SESSION

CALL TRANSACTION

CALL DIALOG

What is BDC or batch input

The Batch Input is a SAP technic that allows automating the input in transactions. It lies on a BDC (Batch Data Commands) scenario.

BDC functions:

E BDC_OPEN_GROUP : Opens a session group

E BDC_CLOSE_GROUP : Closes a session

E BDC_INSERT : Insert a BDC scenario in the session

E The ABAP statement "CALL TRANSACTION" is also called to run directly a transaction from its BDC table.

It runs the program RSBDCSUB in order to launch automatically the session. The session management is done through the transaction code SM35.

The object itself is maintanable through the transaction SE24.

BDC methods:

Method

Description

Parameters

OPEN_SESSION

Opens a session

SUBRC (Return Code ? 0 OK)

SESSIONNAME (Session to be created)

CLOSE_SESSION

Closes a session

None

RESET_BDCDATA

Resets the BDC Internal Table...

None. Normally, for internal purposec

BDC_DYNPRO

Handles a new screen

PROGNAME (Name of the program)

DYNPRONR (Screen Number)

BDC_FIELD

Puts a value on the screen

FIELDNAME (Name of the field)

FIELDVALUE (Value to be passed)

CONSTRUCTOR

Constructor - Initializes NO_DATA

NODATA (No data character). The constructor is called automatically when the object is created.

RUN_SESSION

Launches a session with RSBDCBTC

None

CALL_TRANSACTION

Calls a transaction with the current BDC Data

MODE (Display Mode)

UPDATE (Update Mode)

TCODE (Transaction to be called)

BDC_INSERT

Inserts the BDC scenario in the session

TCODE (Transaction to be called)

BDC techniques used in programs:

1) Building a BDC table and calling a transaction,

2) Building a session and a set of BDC scenarios and keeping the session available in SM35,

3) Building a session and lauching the transaction right after closing the session.

-


BDC using Call Transaction

BDC using Call transaction involves calling an SAP transaction in back ground from within the ABAP

program. The process involves building an Internal BDC table containing the screen information needed to

execute the required transaction and then passing this to the Call transaction command (See code example).

The full procedure for creating a BDC program is as follows:

-


What is the difference between batch input and call transaction in BDC?

Session method.

1) synchronous processing.

2) can tranfer large amount of data.

3) processing is slower.

4) error log is created

5) data is not updated until session is processed.

Call transaction.

1) asynchronous processing

2) can transfer small amount of data

3) processing is faster.

4) errors need to be handled explicitly

5) data is updated automatically

-


BATINPUT/DIRECT INPUT

-


A: Batch-inputs can not be used to fill the "delivery due list" screen because it is not a dynpro. This is a standard SAP report. A SAP report (check with "System -> Status") may be called using SUBMIT sentence with the appropriate options . It is preferred to call a report than create a Batch-input program.

GO THROUGH THIS LINK

http://www.guidancetech.com/people/holland/sap/abap/zzsni001.htm

Regards

Sreeni

Former Member
0 Kudos
62

Hi Rakesh,

http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html

go to the above site and click on BDC & Files there u can find the detail difference between Call Transaction & Session Methods.

Thanx,

Madhuri

Pls reward me if it is useful.