Hi Folks,
We are facing a pressing issue on Back-order processing transaction in client's upgrade to SCM 5.0.
While we are executing the BOP transaction with similar settings on older 4.0 Version on a different server, the transaction gives clean results.
While in this case, the results are complete mismatch. The system shows same results before the BOP run even after the run.
I will explain this in detail.
a.) We have 6 no.s stock of a material in warehouse and the sales orders are generated on a different location called garage. When we create sales order, it executes availability check on the connected warehouse since garage has no stocks. First 6 orders are confirmed on the same planned delivery date as given in the sales order. (Each order has one line item only with quantity one.). These 6 orders have Delivery date of early next month (September first week).
b.) From order no. 7 onwards, it confirms the order depending on the PDT maintained in the materials master data. The deliver date for these orders is within the next 7 days. As per pegging relationships maintained, the first 6 orders above (in point a) are confirmed with the stock available and the orders later are confirmed only on the procurement proposals generated for the component material.
c.) When we run BOP, GATP should reshuffle the priorities and allocate the stock to order no.s 7 onwards since their delivery date comes first. The first 6 orders are pushed with PDT in mind.
d.) This cycle is perfectly running in 4.0 environment but not in 5.0.
There must be some issue concerning 5.0 upgrade and some missing settings required for this version.
Gurus, please step-in.
Chandra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.