Product Allocationa vs Incoming sales order

[Former Member]

Hi ,

We have SCM 5.0 with DP and PPDS. Using CDP and CTP.

We have defined the product allocations according to the product family and sold to party.Every month is devided in two cycles A(15 days) and B (15days). Key figures in planning book PB_ALLOCS_BB

Original Allocations

Allocations Adjustments

Revised Allocations

Last Month Revised Allocations

Incoming Sales Orders

Revised Alloc VS Incoming SO

Revised allocations is the available allocation for sales order and key figure Incoming sales order has the confirmed order quantity on material availability date.The key figure "Revised allocations vs Incoming SO" tells the actual available allocations for a particular

cycle in a month.

Problem : The Key Figure value "Revised allocations vs incoming SO" is changing by system in background automatically even though all sales orders in a particular cycles has been entered. No changes have been

made to any confirmed sales order neither any new sales order is entered in that cylce.

This is impacting production environment and disturbing existing confirmed sales orders.We are not able to give the confirm date to customers as dates are keep on changing due allocation change.

Need urgent help, Please!

Regards

Kumar

[Former Member]

Dear Kumar,

We maintain connection of Porduct allocatn grp to planning area in SPRO, where we actually specify which key figure is for allocation and which one for Sales Order (incoming order quantity). Only these key figures mentioned in Prod Allcatn grp will impact your ATP. Check whether correct key figures are connected.

Check if at all any Temporary quantity assignment is made.

All other key figures are for planning book perspective. Usually for your problem key figure, there would be macro designed to calculate the quantity for arithmatic operation of allocation key figure and incoming order quantity key figure.

Do check whether macro is run in background. Sometimes when data are huge, default macro won't run properly. Run it in foreground and check whether the problem still persists.

Regards,

Bipin