calltransaction, session input

[Former Member]

hi experts,

when we use call transaction and when we use session input...

[Former Member]

SESSION METHOD CALL TRANSACTION

1. Data is not updated in

database table unless

Session is processed. Immediate updation in database table.

2. No sy-subrc is returned. Sy-subrc is returned.

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

4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.

[Former Member]

just i simple words

1. if any errors in calltransaction then that error files will send to session method

this session will run in error mode.

Regards

yours ,

sreekanth....

[Former Member]

Hi hemanth,

plz see the various methods for different purpose as shown below

SESSION METHOD----

---

CALL TRANSACTION

1.Data is not updated----

---

Immediate updation in

in database table unless ---database table.

Session is processed.-------

2.No sy-subrc is returned.------Sy-subrc is returned.

3.Error log is created -

---

Errors need to be handled explicitly

4.Updation in database----

---

Updation in database table

table is always synchronous--can be synchronous Or Asynchronous.

[Former Member]

hi hemanth,

Use the CALL TRANSACTION USING statement

Summary: With CALL TRANSACTION USING, the system processes the data more quickly than with batch input sessions. Unlike batch input sessions, CALL TRANSACTION USING does not automatically support interactive correction or logging functions.

Your program prepares the data and then calls the corresponding transaction that is then processed immediately.

The most important features of CALL TRANSACTION USING are:

Synchronous processing

Transfer of data from an individual transaction each time the statement CALL TRANSACTION USING is called

You can update the database both synchronously and asynchronously

The program specifies the update type

Separate LUW (logical units of work) for the transaction

The system executes a database commit immediately before and after the CALL TRANSACTION USING statement

No batch input processing log

Create a session on the batch input queue.

Summary: Offers management of sessions, support for playing back and correcting sessions that contain errors, and detailed logging.

Your program prepares the data and stores it in a batch input session. A session is a collection of transaction data for one or more transactions. Batch input sessions are maintained by the system in the batch input queue. You can process batch input sessions in the background processing system.

Your program must open a session in the queue before transferring data to it, and must close it again afterwards. All of these operations are performed by making function module calls from the ABAP program.

The most important aspects of the session interface are:

Asynchronous processing

Transfers data for multiple transactions

Synchronous database update

During processing, no transaction is started until the previous transaction has been written to the database.

A batch input processing log is generated for each session

Sessions cannot be generated in parallel

The batch input program must not open a session until it has closed the preceding session.

Use the CALL DIALOG statement

Summary: Not recommended if you can enter data by way of sessions or CALL TRANSACTION USING.

Your program prepares data for a sequence of dialog screens, and calls a dialog module for immediate processing.

The most important aspects of the CALL DIALOG interface are:

Synchronous processing

Transfers data for a sequence of dialog screens

No separate database update for the dialog

A database update occurs only when the calling program executes a commit operation.

Shares LUW with calling program

No batch input processing log is generated

<b>Hope this is helpful, Do reward.</b>

[Former Member]

Hi,

I think ur in intial stage of BDC. So, at first u go through this and then u can go to rest ( others who sent to u).

Batch Data Communication (BDC)

BDC is not a typical integration tool, it is used for uploading data into R/3.

The input comes in the form of a flat file. The ABAP program reads this file and formats the input data screen by screen into an internal table (BDCDATA). The transaction is then started using this internal table as the input and executed in the background.

BATCH INPUT SESSION METHOD:

1) This is a sequence of transactions, which is generated when user run a particular program.

2) Session Method can transfer LARGE amount of data.

3) But Session Method data processing is slower.

4) In this Session Method error log is created

5) In this Session Method until the session is processed data is not updated .

6) In this Session Method sy-subrc is not returned.

7) This is Synchronous processing

CALL TRANSACTION METHOD:

1) This is Asynchronous processing

2) Call Transaction can transfer SMALL amount of data.

3) In Call Transaction data processing is faster.

4) In this Call Transaction Method errors need to be handled explicitly :

In this Call Transaction method, the transactions are triggered at the time of processing itself. So the ABAP program must do the error handling. It can also be used for real-time interfaces and custom error handling & logging features.

5) In this Call Transaction Method data is updated automatically.

6) In this Call transaction is sy-subrc is returned.

Hope u can understand this.

Best Regards,

kiran sam

[Former Member]

Hi,

According to ur question. we can simply say that:-

We use call transaction to transfer the small amount of data. Because this is faster when compared to session method. But errors need to be handled explicitly .

where as, We use session method to transfer the huge amount of data. But this is slower when compared to call transaction. Here in this error log is created.

But u first go through the data which i have sent to u.

Best Regards,

kiransam.