- It is possible for a SAP Enterprise Inventory and Service-Level Optimization (EIS) scenario to optimize and/or fail in version 6.9 and the LOADSET_STATUS_ID never changes/progresses beyond the status of an 8 (Gateway Data Loader in Progress).
- The application log will produce the following statement showing that the loadset completed successfully.
2013-10-21 11:36:28 EDT INFO DataLoaderGatewayWorkerThread com.smartops.mipo.Mipo3_3ComputationTaskProgressMonitor runComputation() [scalability] scenario 'SCENARIO NAME - Mon Oct 21 07:52:12 EDT 2013' computed successfully in 2742.454 secs
- Transfers of the MIPO scenario to DataStore do not initiate when using the automatic transfer method. However, the DIM scenario transfer is successful and appears in the SOPS_DATASTORE.DATASTORE_QUEUE table.
SAP Enteprise Inventory and Service-Level Optimization (EIS) versions prior to 126.96.36.199
SAP Enterprise Inventory Optimization 6.9 by SmartOps
SmartOps, MIPO, EIS, EIO, long, time, transfer, Data Store, Datastore, transfer not started , KBA , SCM-EIS , SAP Enterprise Inventory and Service-Level Optimization , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.