Q

When should we call by session, and when should we call by transaction?

What time is right for calling by session vs. transaction? Site expert Matt Billingham provides advice for developers.

When we should use call by session and call by transaction? What will happen when the error occurs during data transfer in both the methods? Is it necessary to do the conversion every time, transferring data from a non-legacy system to SAP? What does synchronous and asynchronous processing mean?
For your first two questions: If you call by session, then you can use SAP error handling, re-run the session, etc. If you call transaction, you have to write error handling yourself. Which one you use is up to you. For dataloads, I use sessions. For anything else, I use call transaction.

For your third question: It depends on how you set things up.

For your fourth question: Synchronous means that your program waits for the update to finish before proceeding. Asynchronous means it doesn't.

This was first published in July 2005

Dig deeper on SAP Web applications

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

-ADS BY GOOGLE

SearchManufacturingERP

SearchOracle

SearchDataManagement

SearchAWS

SearchBusinessAnalytics

SearchCRM

SearchContentManagement

SearchFinancialApplications

Close