on 09-13-2013 11:55 AM
Hi All,
We have observed for few Locations Sock transfer order (STO's) are showing under Distribution demand confirmed key figure in planning book instead of Distribution demand TLB confirmed key figure. Order category also showing EG category
For remaining location category group showing as BI, for these location orders also showing under Distribution demand TLB confirmed..
Can any one tell us what could be the root cause?
The orders with EG category are not confirmed by TLB, which creates BI order out of EG.
You may need to run TLB for the concerned locations.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Actual issue is when we run the CCR report (Comparison/Reconciliation) using the documents to be checked (Purchase orders, purchase requisition and Confirmation)
We are getting a number of results with error code 188 and 189, APO Quantities different than R/3 quantity in categories “Confirmations, Purchase Orders and Purchase Requisitions
If you look for this same object in the Product View, it shows up wrongly as ‘Dep: PReq’ rather than a ‘PO Memo’
If you clear the CIF error, it corrects the category, and quantity when required.
In this case for few source location, this is wrongly, and extraneously included as ‘Distribution Demand (Confirmed)’ even though the quantity has already been ship noted in R/3:
And this is resulting in a incorrect shortage in planning book
If not cleared before the heuristics run, the resulting shortage creates an erroneous production req to solve for the shortage.
In consolidation system we have created a STO , this order coming and showing correctly as distribution demand TLB confirmed
Note: in our project we are not using TLB functionality, deployed orders goes to R/3 there we have separate tool it converts TLB orders and sent to APO
This issue happening only for few locations…
User | Count |
---|---|
8 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.