Memory Based Planner Failed Program Was Terminated By Signal 6 in msopmmd3.cpp (Doc ID 859179.1)

Last updated on AUGUST 13, 2016

Applies to:

Oracle Advanced Supply Chain Planning - Version 12.0 and later
Information in this document applies to any platform.

Symptoms

Distribution planning is failing.  Tried setting profile, MSO: Maximum Allowable Days Late before Forecast Expiration - NULL,  to correct the issue, but it still fails:

...Load data completed 0:00
BATCH process=1 plan_type=5
On entry to SCO
Planning time fence is 1

Begin Date: 2455028
End Date: 2455235MSO_SCO_ASSIGNED_UNITS: 1
MSO_SCO_MAXIMIZE_POWO = 0
MSO_SCO_EXIST_SUPP_ABR_SUBSCOMP = 0
MSO_SCO_COST_ROLLUP_INCR_FACTOR = 1
MSO_SS_PLAN_LEVEL: 1
DSM om->createAbstEntities(), time taken = 0
DSM om->createLinks(), time taken = 0
MSO_MIN_PROC_LEAD_TIME_ADJ_FACTOR not set.
Lead Time Rollup, time taken = 0
MSO_SCO_ASSIGNED_UNITS: 1
MSO_SCO_MAXIMIZE_POWO = 0
MSO_SCO_EXIST_SUPP_ABR_SUBSCOMP = 0
MSO_SCO_COST_ROLLUP_INCR_FACTOR = 1
MSO_SS_PLAN_LEVEL: 1
om cost roll-up, time taken = 0
reading mbp sup, time taken = 0
MSONWL64.exe: /disk1/R12/64bitwkr/R12_64bit_wkr/mso/src/scoobj/msopmmd3.cpp:2493: virtual int SCPMathModel::endTime(int, int, int, int): Assertion `ok == 1' failed.
/ERP/STGWIRE/apps/apps_st/appl/mso/12.0.0/bin/MSONWL64.exe
Program was terminated by signal 6

  

STEPS
1. Run the plan.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms