This content has been marked as final. Show 18 replies
Here is a direct hit in MetaLink
MSCFNSCW Sales Order Collected But Missing In ASCP Planners Workbench After Plan Run [ID 565033.1]
Has an associated bug Bug 6837780 - The problem sales order had a null ship_to_site_use_id in table msc_sales_orders - Sales orders that did show up in the plan have this populated correctly. The problem here was that a new customer or ship to site was created but not collected by data collections. Data collections can miss this depending on the value of profile option MSC:Collection Window for Trading Partner Changes (Days) when it is set to something other than NULL.
Profile option "MSC: Collection Window for Trading Partner Changes (Days)" is set to NULL. Suppliers/Customers/Orgs and Trading Partners parameters in the Planning Data Pull are set to yes. This doesn't appear customer related because there are definitely customers where some of their sales orders show up and some don't.
I am not sure whether your issue is fixed if not check the following in All area's
1.Check whether the item is Collected in ASCP workbench as well as the sales order.
a. In Item attribute definition --> under order management Tab enable the following.
1.Source - Internal.
2.OE Transactable flag.
2.In the sales order check the following.-
a.Whether the Ship from organization is as a part of your collection process...
b.through folder options- - add Visible Demand Flag field and make sure it is "Y".
c.Scheduled Ship Date is populated or not.
d. Transaction type whether it is RMA Type or shippable line
If all the above are ok..
Run a targeted collection for sales orders,and ensure the Collect Sales order set to yes.
Try all possibly it will collect.
I love all of these ideas but no luck yet! I did find something interesting today. It appears that even within a single sales order one line may show up in ASCP but not the other. The only difference appears to be that the one that is seen has a scheduled ship date of that day or earlier but the missing one has a ship date in the future.
I verified that both lines are being collected, but the sales order number for the missing one looks like "258945" while the one that shows up looks like "258945.USA Sales Order.ORDER ENTRY(6.2)". What is it that Collections is doing to append order type and line information to the order number? It seems that if a sales order line in Collections does not have that info appended then it also doesn't show up in the Plan.
Any more ideas?
Based on your comment about the order number, it seems that you're trying to look for sales orders which were scheduled using ATP/ GOP after last ASCP plan run. You may either be using ATP based on collected data or some of these items aren't included in your plan thereby forcing ATP to use ODS/ Collected data to promise/ schedule these sales orders.
When ATP/ GOP promises these sales orders using collected data, you'll see them dynamically inserted in ODS data (msc_sales_orders) and order number will show up as "258945" but after next collections, same sales order record is replaced by collected version with SO# as "258945.USA Sales Order.ORDER ENTRY(6.2)".
Here are possible ways to validate/ resolve this issue:
1. If you use "ATP/CTP based on Planning Data", these SO will be inserted dynamically in ASCP Plan and will be visible in ASCP workbench in Pink/ Magenta color though no pegging will be available until next plan run. You'll find these orders will have a record_source value as '1'
2. If you use "ATP based on Collected Data", these SO will be included in the ASCP plan in next collections/ ASCP Plan run and same must be happening now as long as these items are included in the plan based on your plan options setting. Please note that ASCP Plan is a statis information as of the time of plan run and any SO scheduled after ASCP plan run won't be included until next plan run.
Hope this clarifies the concern and you'll be able to validate the scenario in your case. For any further concerns, please contact me directly and I'll be glad to help you.