Stock upload conversion program

[Former Member]

Hello Experts,

I have few questions below.

What is the case that we require to do a BDC program for stock upload? What is the difference of using LSMW Vs BDC?

I have about 500 materials and need to upload the stock into SAP from external excel file and need to move them into physical bins.

Do I need to develop a conversion program for LSMW to full fill my requirement.I am asked to write a functional spec for stock upload.Please help..

Do i need a seperate conversion program for stock transfer from 998 storage to physical bin?I should also print the SU labels during this program.

Please explain the process.

Thanks for your time in advance.

Edited by: RKsap193 on Oct 13, 2008 12:28 PM

[kunal_ingale · Accepted solution]

hi

LSMW and BDC are vastly different.

BDC (Batch Data Communication) is a technology used for data transfer. it is meant for transferring data thru SAP transactions itself. when u use BDC for data transfer, the sequence of steps is the same as when u use standard sap transaction screens for data upload. the only difference is that u can use different options for foreground/background processing.

LSMW on the other hand is a tool that helps migrate data from a legacy system (non-sap system ) to SAP system. it offers u various options to use either batch input, direct input, BAPIs or idocs. it involves a series of some 17-18 steps to migrate data.

Both BDC and LSMW are used for Data transfer. Usually LSMW is used initially when the project kicks off. The data from the legacy system is transferred to SAP using various methods like Direct input, IDOCs etc... This is usually a onetime process. Unlike LSMW, BDC can be used on regular basis for Data transfer.

refer following

regards

kunal

[Former Member]

If you send your personal email than i can send you the document with screen shot.

Here is the complete step bu step process to load initial stock with LSMW

you can use LSMW or BDC program

LSMW can eb designed by analyst and BDC can be desined by ABAPer

I did not find any documentation describing scenario of initial stock entry of material to HU & WM managed storage location. It inspired me to write this wiki.

I use the following scenario of loading initial stock entry:

u2022 Creation of inbound delivery using standard batch input import method - program RM07MMBL with following tip:

o Input file from legacy system is prepared it such a way that one line contains information about one palette (or other packing materials) and storage bin coordinate.

o In the standard field MTSNR (Material slip) storage bin coordinates information is recorded.

o Field MTSNR is transferred to field LIKP-LIFEX (External Delivery ID)

u2022 Creation of transfer order in reference to inbound delivery using batch input recording of transaction LT03

o Field NLPLA (Destination Bin) is read using simple ABAP code from delivery header - LIKP-LIFEX

To create transfer order for inbound delivery in transaction LT03, material in inbound delivery must be packed, i.e. handling unit must be created. It can be archived by using an automatic packing functionality (packing instruction and packing instruction determination).

After TO confirmation the goods receipts can be posted for deliveries.

Standard output can be generated for handling unit using message type E128 (EAN128 sticker). If needed storage bin information can be printed to simplify label sticking on palette or other packing materials in the warehouse complex.

In this scenario homogeneous materials are packed into one handling unit.

Step 1: LSMW for initial stock entry in MM using 561 movement type:

This is the well known standard LSMW procedure which use standard batch input import method - program RM07MMBL .

1a. LSMW Process steps:

I apply only following tip: in the standard field MTSNR (Material slip) storage bin coordinates information is recorded.

1b. Maintain Source Fields LSMW process (step No. 3):

1c. Input file - example:

1d. Create batch input session LSMW (step No. 14).

It is important to set "1" for Max. number of items. It ensures that one delivery is created per one input line.

1e. Log sample from batch input session.

1f. Inbound delivery monitor - transaction VL06I

Selecting deliveries for Putaway you can control deliveries created in preceding step

Each delivery is packed:

and output - message type E128 is created:

Step 2: LSMW for transfer order creation in reference to inbound delivery:

This LSMW procedure is based on batch input recording of LT03 transaction.

2a. LSMW Process steps

2b. Maintain Source Fields LSMW (step No. 3).

Deliveries numbers can be simply generated to input file form inbound delivery monitor (see 1f step)

There is no need to fill LGTYP (Storage type) and LGPLA (Storage section) because these fields are derived in LT03 transaction from storage bin - LGPLA (only if LGPLA is unique for all storage types and storage section - LAGP table).

2d. Display Read Data LSMW (step No. 10)

2e. Run Batch Input Session (step No. 14)

Log from the batch input session:

LT23:

I have customized the system to automatically confirm TO. Finally all HU are put away.

Tip & Trick

You can confirm TO using RF devices (standard transaction LM02) while label sticking on a palette.

Last step is to post GR for inbound deliveries which were put away. It can be done collectively in inbound delivery monitor by selecting deliveries for goods receipt:

Summary

u2022 Easy to implement: two simple LSMW scenarios (one with few ABAP lines)

u2022 Standard message type for label printout with information about storage bin coordination

u2022 Possibility to analyze correctness of data migration in inbound delivery monitor before posting GR

u2022 Possibility to confirm label sticking with RF transaction

u2022 This scenario can be adapted for non homogeneous HUs