BDC session method problem

[Former Member]

Hi,

if we will start a session method and it was stopped because of a wrong data, if we start the the session method with the same flat file how the system will behave. Will it update the records to the database which were already updated or the system will leave them and proceed with the other data? if the system will ignore the already updated data then how it happens, what is the exact mechanism how system understands that these are duplicate date ?

What will happen if the same scenario is apllied to the call transaction method ?

regards,

santosh

[Former Member]

If you rerun the file either for session or call transaction, then the already updated records will be updated again. That's why the session method creates the error session.

Rob

[Former Member]

Hi,

Session Method:

Once you Run your program as soon as session is Created in SM35.

Whole data to be upload gets stored in SESSION ID(File on application server).

As you execute the session a LOG is created for each session.So while running the session

if some of the data is no uploaded or Error Occures.The whole session is marked as Error.

You can Double click on the SESSION and check Where exactly error has occured.

Once you restart the session again SAP check the log file which data has been uploaded

and which is not .Depending on the log file only those data is uploaded which has not been uploaded.

CAll Transaction:

In Call transaction there is no log files that get created automatically.You need to use BDCMSGCOLL

to store MESSAGES.Once an error has occured and you rerun that program ALready entered data will be uploaded again.

Error handling is better in Session metho as compared to call transaction.

Regards,

Gurpreet