topic LSMW import data in Application Development and Automation Discussions

LSMW import data

Former Member — Wed, 11 Jul 2007 19:06:33 GMT

In LSMW which is the best way to import data - batch input, direct input , BAPI or IDOC What is the benefit of one over the other

Re: LSMW import data

RichHeilman — Wed, 11 Jul 2007 19:10:34 GMT

This is an excellent question, and there may not be a concrete correct answer as I've used LSMW extensivly over the past few years. First, if there is a standard object, like creating material masters, there may only be one option using standard programs, in this case direct input, i have used it and I can't say that I am all that impressed with it. Others, like Bill of Material creation, you can only do batch input, again, I got it working, but really bad error reporting, in my opinion. I've never used IDOCs, so can't anything there. Also, I've never had to use BAPI within LSMW, but would most likely try using that if I couldn't get the direct input or batch input working correctly.

Regards,

Rich Heilman

Re: LSMW import data

ferry_lianto — Wed, 11 Jul 2007 19:14:05 GMT

Hi,

Please check these information from other thread.

IDoc in LSMW:

- If you need to transfer data into more than one system you can use IDoc in LSMW

- You can use the LSMW IDOC method to create IDOC out of the Flat file and then for the same IDOC you can trigger an outbound to the desired system.

BDC: - If you less amount of data and if you need to transfer data regularly you can use BDC. When u use BDC for data transfer, the sequence of steps is the same as when you use standard sap transaction screens for data upload.

There are two ways to run BDC Programs:

Batch Input (BI):

- The Transaction is simulated & the data is transferred as if it had been executed online. Its slow process since its calling the screens. It mentions the error clearly.

- Error Log created automatically.

- Batch input session can’t be created in Parallel.

- BI procedure, data is always posted synchronously.

Call Transaction:

- Online Process

- Call Transaction posts the data directly via the Online Transaction.

- No Session created.

- If any error occurs the faulty record collected & put into the separate process.

Direct Input:

Direct Input programs work exactly similar to Batch Input programs. But the only difference is, instead of processing screens they validate fields and directly load the data into tables using standard function modules in place of online Transaction screens. For this reason, DI programs are much faster than the BDC counterpart and so ideally suited for loading large volume data.

Direct Input or BAPI would be preferable way.

Regards,

Ferry Lianto