Onhand Fails In Pre-Process Monitor When Total Rows in MSC_ST_SUPPLIES is Greater Than the Processing Batch Size
Last updated on JUNE 28, 2017
Applies to:Oracle Advanced Supply Chain Planning - Version 12.1.1 and later
Information in this document applies to any platform.
OnHand records are getting kicked out during the pre-process monitor with the following error:
Advanced Supply Chain Planning: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
MSCPPM module: Pre-Process Monitor
Table Name: MSC_ST_SUPPLIES, Number of Occurences: 8999, Error: The value provided for PLANNING_PARTNER_SITE_CODE is invalid. Please resubmit this record with a valid value for PLANNING_PARTNER_SITE_CODE.
Note that the client in this case was not using Legacy load or API to load into the staging tables (ex. Msc_St_Supplies) but rather a custom procedure (ex. Update MSC_ST_Supplies as Select * from XXX_Supplies) which is acceptable practice. The client then used the Pre Process Monitor and while other staging tables like Msc_St_Sales_Orders doesn't seem to be affected by the value in the Processing Batch Size being larger than the Processing Batch Size parameter.
Other order types seems getting validated without error.
1. Populate the MSC_ST_Supplies table with records
2. Run pre-process monitor with Processing Batch Size to be less than the Total Number of Rows in MSC_ST_SUPPLIES table
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms