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.
Showing results for 
Search instead for 
Did you mean: 

How to create a session using call transaction method.

Former Member
0 Kudos

hi , this is nagaraju,

How to create a session using call transaction method.


Former Member
0 Kudos

Using call Transation U can't create the session.

The Call transaction is used only when the update is immediate.


Former Member
0 Kudos

I think u cannot create a Session using Call Transcation Method...

We have Session Method to create the Sessions......

Other wise do one thing write the session method program in one report,

execute that Report using Call Transcation method..( i.e)

call se38 and write report name and execute that program then u can get the session ...........

Former Member
0 Kudos


About Data Transfer In R/3 System

When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.

In the process of replacing current applications and transferring application data, two situations might occur:

• The first is when application data to be replaced is transferred at once, and only once.

• The second situation is to transfer data periodically from external systems to SAP and vice versa.

• There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.

The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called “batch input” or “batch data communication”.




First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.

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 the next screen is processed.

When the program has finished generating the session, you can run the session to execute the SAP transactions in it. Unless session is processed, the data is not transferred to database table.

A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program.


Data is not updated in database table unless Session is processed.

No sy-subrc is returned.

Error log is created for error records.

Updation in database table is always synchronous


Immediate updation in database table.

Sy-subrc is returned.

Errors need to be handled explicitly

Updation in database table can be synchronous Or Asynchronous.



Former Member
0 Kudos



You cant create the session using the call transaction method.