Initial stock upload in WM

[Former Member]

Hi Gurus,

My Client has been using sap since 4 years and modules using are fi, sd, mm,

Now they planned to implement WM also.

Here My doubt is Stock is already available in IM.

If we implement WM now, how we upload stock into WM??

I mean if it is fresh implementation as and when we upload the stock in MM, in WM side it will be posted into 902 storage type.

But in this case stock is already available in IM. How to upload the same stock into WM.

Can someone give me clear picture please.

Regards,

YHKK

[Former Member · Accepted solution]

Initial stock entry of materials to HU & WM managed storage location with label printout

*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

Regards,

eswarmanu...

[Former Member]

thanx

[Former Member]

If it is WM- then all material documents in IM has to have Transfer order telling source and destination stoage types and bin

the default storage tyoes(interim) can be set in movement types for WM

example LT06 - create TO for material docuemnt, LT03-pick delivery etc

[Former Member]

Hi

You need to remenber that linking a warehouse to your present Storage Location will not put the stock in WM and so you will be out of balance between the two.

You need to build a new st location which has WM attached and then do a St Loc to St loc transfer (MB1B movement 311) for all of the stock and then the stock will be in 921 in WM and you can use a LSMW to locate it from there.

I hope that this helps

Frenchy