Planning ODS Load - Not All Records Are Moved From MSC_ST_SAFETY_STOCKS To MSC_SAFETY_STOCKS
(Doc ID 2729110.1)
Last updated on NOVEMBER 17, 2020
Applies to:
Oracle Advanced Supply Chain Planning - Version 12.2.6 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.6 version, Data Collections
Planning ODS Load - Not all records are moved from msc_st_safety_stocks to msc_safety_stocks.
When Planning Data Collection - Purge Staging Tables concurrent request is completed, it is purging all data including the records that contain errors. Concurrent log states:
Error: No org is assigned to instance 1 ! Collection could be failed due to this error!
NOTE***
Safety Stock records from Oracle eBS are loading correctly, the issue is coming from records loaded from the Custom interface. These records appear to be complete in MSC_ST_SAFETY_STOCKS table.
ERROR
-----------------------
Error: No org is assigned to instance 1 ! Collection could be failed due to this error!
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Load data into the table "msc_st_safety_stocks" using custom script
2. Run Planning ODS Load process
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |