RS00649: INTERNAL ERROR IN ILOMSMODELI::SOLVE' DURING BATCHING

APAR status

• Closed as program error.

Error description

• After getting a successful planning solution, the batching
  engine
  crashes with:
  
  --------------------------------------------------------
          H E U R I S T I C    B A T C H I N G
  --------------------------------------------------------
  ilog.opi.jni.runtime.IloCppRuntimeException: Internal error in
  IloMSModelI::solve
  
   at ilog.plant.IloMSModel.solve(Native Method)
   at ilog.plant.IloMSModel.solve(IloMSModel.java:3167)
   at ilog.plant.gui.util.IloMSDefaultEngineOptimizer.solve
  (IloMSDefaultEngineOptimizer.java:37)
   at ilog.plant.gui.appframe.IloMSAppFramePlatform.solve
  (IloMSAppFramePlatform.java:1676)
   at ilog.plant.gui.appframe.IloMSAppFramePlatform.access$2000
  (IloMSAppFramePlatform.java:145)
   at ilog.plant.gui.appframe.IloMSAppFramePlatform$70.construct
  (IloMSAppFramePlatform.java:1493)
   at ilog.powerops.swing.SwingWorker$2.run(SwingWorker.java:134)
   at java.lang.Thread.run(Unknown Source)
  Internal error in IloMSModelI::solve
  dynamic pegging time = 0.093
  

Local fix

• There are 3 possible work-arounds:
  * Use "Advanced Heurstic" instead of "Heuristic"
  * Set the batch size min of recipes to 0 before applying
  batching heuristic (this can be done in a PPO plug-in)
  * Recompute the "plannedNumberOfBatches" of planned productions
  to take into account the batch size min / max constraints before
  calling the batching heuristic.
  

Problem summary

• workaround provided to customer
  

Problem conclusion

• workaround provided to customer
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  ILOG PPO

• Fixed component ID

  5724Y2600

Applicable component levels

• R330 PSY

     UP