cancel
Showing results for 
Search instead for 
Did you mean: 

How to manage Material staging with one WM two sloc (Internal & External)?

Former Member
0 Kudos

Hi Experts,

We have a situation with client here:

One plant having his own WM managed SLOC need to take most of raw/pack goods from 3rd party Warehouse. Client wants to manage it as one Warehouse with two different storage location-internal one & exteranl one for 3P.

We are talking for creation of two storage types within one Warehouse, but client asked for two storage locations within one warehouse, how to handle material staging in this case?

Thanks

Digambar

Accepted Solutions (1)

Accepted Solutions (1)

csaba_szommer
Active Contributor
0 Kudos

Hi,

I'm not sure this is the best solution, just an idea:

Sloc1, Sloc2 (3rd party) are assigned to WH, in SLoc1 you do packaging.

First transfer your goods from SLoc2 to SLoc1 by IM material staging (MF60); after that comes the WM material staging for all your components.

Other solution is "Storage location control" - SPRO > LE > WM > Interfaces > IM > Define Storage Location Control; here check help (Scenario3 Example2)

...

Stocks that are actually in production are managed in storage location 0092 in plant 0001. Stocks in the warehouse are managed in storage location 0091 / plant 0001. As soon as the goods are physically in production, the stock is reposted in plant 0001, storage location 0092. The following example assumes that the WM-PP interface is active and that stocks that have been made available by Warehouse Management are in storage type 100.

The following Customizing settings are required for this: storage locations 0091 and 0092 in plant 0001 are assigned to warehouse number 001. Storage location 0091 is designated as the standard storage location. For storage location 0092 you have set the indicator that the storage location is not copied into the transfer requirement. You define for production storage type 100 that the stock of this storage type belongs in plant 0001, storage location 0092 and that the posting change is to take place as an accumulated posting. This Customizing configuration gives the following procedure for material staging for a production order.

In the component of the production order, plant 0001 and storage location 0092 are entered. The storage location of the respective supply area is also 0092. The material staging takes place for production order 10000011. In Warehouse Management, a transfer requirement is automatically created through this material staging. Since you have set the indicator for storage location 0092 that the storage location is not copied into the transfer requirement, the transfer requirement has no storage location. For this reason, the standard storage location 0091 is determined as the storage location during transfer order creation. This means that only (1) quants in the warehouse (storage location 0091 are selected for stock removal (picking). A positive quant is created in storage type 100 with storage location 0091 through the transfer order.

When the transfer order has been confirmed, you must execute a posting change for the stock in Inventory Management. Through this posting change, the quant in storage type 100 (storage location 0091) is deleted and a new quant is created with storage location 0092. The subsequent goods issue posting for the production order also takes place from storage location 0092 and thus reduces the stock of the quant

In this scenario, make sure that at the time when the production order is released no stock of the material is in storage location 0092. In this case, the availability check must only take place at plant level.

General data on posting changes:

As described above, the time of the posting change is controlled by the indicator "Cumulate posting change". The posting change is executed using the program RLLQ0100 or Transaction LQ01.

As a rule, the available quantity of the quantity is always included in the posting change. You also change quants whose storage location is different from the storage location defined in Customizing for the storage type. The posting change takes place directly in the storage bin of the quant; both quants there are deleted by this.

Here, too, no posting change notice is created. This type of posting change can therefore only take place in storage types for which direct postings from Inventory Management are suitable.

...

Regards,

Csaba

Edited by: Csaba Szommer on Oct 18, 2009 9:08 PM

Edited by: Csaba Szommer on Oct 18, 2009 9:09 PM

Edited by: Csaba Szommer on Oct 18, 2009 9:12 PM

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Csaba,

Thanks for your prompt reply, I will create this config & run scenario But I am having 2 concerns here

1) Both SLOC are WM managed & Stock exists at both SLoCs , so availabilty check has to cary at both SLOCs & the WM staging

2) If SLOC 0091 is configured with ST Type 100 in Control cycle Record, TR will be generated for SLOC 0091

Thanks

Digambar

Former Member
0 Kudos

Hi,

According to the second option,

1) Both SLOC are WM managed & Stock exists at both SLoCs , so availabilty check has to cary at both SLOCs & the WM staging

Both SLOC are WM managed. but Stock exists only in 0091.

In 0092 stock exists temporarily i.e. only from Posting change (after TO Confirm, by program RLLQ0100 or Transaction LQ01) till

Order Confirmation (Material doc. creation)

2) If SLOC 0091 is configured with ST Type 100 in Control cycle Record, TR will be generated for SLOC 0091

It will not. It is config setting to stop SLOC in TR but not control cycle.

For storage location 0092 you have set the indicator that the storage location is not copied
into the transfer requirement. You define for production storage type 100 that the stock of this
storage type belongs in plant 0001, storage location 0092 and that the posting change is to
take place as an accumulated posting.

SLOC 0092 should be configured with ST Type 100 in Control cycle Record.

This is the standard solution provided by SAP.

If it is not suitable to you, plz explain your scenario with example SLOC names clearly.