cancel
Showing results for 
Search instead for 
Did you mean: 

WM-PP Material Staging - No Automatic staging occurring on Release of PP Order

dotcom0123
Explorer
0 Kudos

Hello gurus...

I have a question as to the dates used for the automatic material staging on the release of a production order.

Let me use the example that the production order was created yesterday, 11/14/2023. The components are all in the available storage locations in ERP and the stock is in EWM. There are float days for this production order which has the "Scheduled Start Date" set for 11/16/2023. The Prod.Sch. profile has the transfer of requirements set to 2, create the TO, TR and send when the order is released.

User releases the production order today, 11/15/2023 but no staging occurs. User tries to force the "execute" of the WM material staging, but no delivery is created for this production order to be sent to EWM.

If user changes the "requested" quantity in the pull list to match the required quantity and executes the material staging, a warning is displayed that the requested quantity is greater that then required quantity. However, hitting enter will then give you a message that material staging executed with no errors. User saves production order and delivery is sent to EWM.

I can only assume that the material staging did not trigger on the release because the scheduled start date is in the future and the component requirement date is also set in the future. So system did not create the order because the components are not yet required.

My question would be if there is a way to force the transfer of requirements (WM staging) to still be executed even though the requirement date is in the future. This would allow the warehouse ample time to pick and relocate the goods to the PSA.

I found a couple topics related to the pick, pack times in WM inside of the ERP system which may influence the material staging times however, we are using EWM. So the requirements are sent via a 311 movement to get the components from EWM and relocate the to the PSA.

Thanks for any suggestions/ help.

EszterN
Product and Topic Expert
Product and Topic Expert
0 Kudos

Do you have a stuck PR* queue in SMQ2 with an error message, that could help further?

Accepted Solutions (0)

Answers (1)

Answers (1)

dotcom0123
Explorer
0 Kudos

I checked the system and there are no stuck queues.

To add to my original topic, I did find a field within the BOM for "Lead Time Offset". What I can do with this is add a -2. This negative 2 will offset the float days. Meaning, if the basic start date is set to 11/15/2023 but the scheduled start date isn't till 11/17/2023, this would move the component requirement date forward 2 days to match the 11/15/2023 basic start date. I tested this and when I released the production order, the material staging was triggered.

I only added the lead time offset to just 1 out of the 5 BOM components. So in EWM, I have my single relocation to the PSA for the single component. The rest of the components had the requirement date still at 11/17/2023.

I tried to use COHV for the mass processing of material staging and when executed for my production order, I still did not get any movements/ delivery created for EWM to pick the remaining parts even though, the log states material staging executed without error. I even tried to execute the staging directly in the production order but nothing is created.

The only way I get the posting change document (WM material staging) to execute was to go into the pull list for the production order and put the required quantity in for each of the 4 remaining components. Then I could save the production order which triggered the WM staging and in EWM, I received my posting change document.

So I'm not sure why this can't be triggered some other way? This means, if a component doesn't have the leadtime offset, no WM staging occurs. Then someone must go into each of the production orders, pull list, then add the required quantity into the field so that when they save it, the WM staging will produce the required document.