Data Transfer Questions

[Former Member]

1)

In LSMW we have Batch Input, direct Input, Recording, BAPI and Idoc. Why does LSMW doesn't support call transaction method. ?

2)

In BDC programming -- for the below code.

Call transaction 'XK01' mode 'E' update 'S' message into messtab.

If sy-subrc ne o.

call funtion 'BDC_insert'.

endif.

The wrong record gets stored in Batch session as its synchronous update and system returns the error records into session.

But, in these code ..

Call transaction 'XK01' mode 'E' update 'A' message into messtab.

If sy-subrc ne o.

call funtion 'BDC_insert'.

endif.

How does the system would know that its wrong record - as we are giving Asynchronous update, how will it get stored into session. Please explain it. ?

3)

How to know all the available standard Batch input / direct input program available in the SAP system. Is there any Tcode for it ?

4)

In LSMW - what can we specify in the sub-routine step 6.

5)

Do we use LSMW for one time transfer or Periodic transfer.

In periodic it provides two more steps. What should we specify in these 2 steps.

Thanks! in advance to all the Techies.

[Former Member]

Answers to questions 3 & 5 are available within the LSMW instruction file - this can be found on the service marketplace.

For 3 - Just go into LSMW and the first step and use the search help to see what objects are available to you.

For 5 - I only get one extra step - but that could just be a setting thing. The kicker is the frame job for period data transfer. esentia this interface will read, convert, and then load your data based on what you have configured for that object in LSMW. You will need to provide all the indicators, variants, and settings needed to execute those steps manually. SAP just gives you one page for BI/DI/BAPI/IDOC settings.

1. LSMW does support CT in some area's - particularly any BI/DI where the program used is IBIP. Just keep in mind that CT should only be used for testing purposes and executed from the front end.

Sorry - but I really don't have any additional answers for your other questions.

[Former Member]

Hi,

2) For synchronous update, system will wait for database update, so the sy-subrc you get in synchronous update will tell you whether record has been updated to database or not, hence you can easily differentiate between success & error records. But in the case of asynchronous update, system will not wait for the database update, so the sy-subrc you get will only tell whether the transaction has been processed successfully or not, hence you can not differentiate between success & error records in terms of database update for asynchronous update.

3) For Direct Input Programs, check out following:

<b>Transactions :</b> SXDA, SXDA_TOOLS

<b>Tables :</b> SXDA0, SXDA1, SXDA2, SXDA3, SXDA1T, SXDA2T

Reward points if the answer is helpful.

Regards,

Mukul

[Former Member]

Hi Mukul,

2) In synchronous mode - the sy-subrc would check the database update is success or failure, and where as in Asyncronous mode - the sy-subrc would check the transaction success or not.

But, in synchronous update it stores the failed records in session as its not updated in DB.

But, in asynchronous update - the DB gets updated later but how to differentiate - whether the records already exists or not in DB. How it internally handles the record.