Load/Copy/Merge MDS OR Forecast With Explosion Terminates With Signal 11 - BUT Completes With MRP: Debug Mode - Yes, Yet The Planning BOM Does Not Explode
(Doc ID 2636530.1)
Last updated on FEBRUARY 07, 2020
Applies to:Oracle Materials Requirement Planning - Version 12.2 and later
Information in this document applies to any platform.
Unable to explode a Planning Bill Forecast - program terminates with signal 11 - Copy function without Explode Option ends normally - error also occurs with MDS Load/Copy/Merge - job log details are below:
Loading periods. Please wait ..
SELECT TO_CHAR(period_start_date, 'j')
WHERE calendar_code = :calendar_code
AND exception_set_id = :exception_set_id
ORDER BY period_start_date
Loading periods. Please wait ...
...Loading periods. Please wait . 0:00
..mrlrt1_load_tree has fetched 1 row(s) from MRP_FORECAST_DATES 0:00
.Loaded forecast/schedule entries for 1 designator onto the tree (NUMBER 0:00
autoload has updated 1 row(s) from MRP_LOAD_PARAMETERS 0:00
.Forecast explosion completed 0:00
Item: TEST_ITEM1 (Id=123456)
Program was terminated by signal 11
Then if we run with MRP: Debug mode - Yes, the program completes, but it does not explode the Planning BOM
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