Integration flow

Understand the flow of integration with IBM® Sterling™ Intelligent Promising Optimization Service.

  1. After you enable the integration with Sterling Intelligent Promising Optimization Service, the IBM Sterling® Order Management System Promising API call starts - findInventory and scheduleOrder APIs.
  2. The API reads sourcing nodes according to the Sterling Order Management System sourcing rules.
  3. The integration calls the Rank API with a set of nodes from Sterling Order Management System.
  4. Depending on the supported and unsupported scenarios, the Rank API returns the response for the eligibleForRank attribute as Y or N.
    1. If eligibleForRank = N, the response of the Rank API is ignored and Sterling Order Management System continues with the original node set.
    2. If eligibleForRank = Y, nodes that are returned by the Rank API are updated on the promise lines and used for promising.
    3. If the API call throws an error or an exception occurs,
      • When the integration is set up in the idle mode, if any error occurs while calling the Optimization APIs, those errors are printed in the error log. The transaction continues according to the default Sterling Order Management System flow.
      • When the integration is set up in the live mode, if any error occurs while calling the Optimization APIs, an error is displayed and the transaction ends.
  5. If implemented, the SourcingCorrectionUE user exit is called to override node set after the Rank API call.
  6. Sterling Order Management System generates choices and offers a best solution for promise lines.
  7. The Optimization API is called with the created choices and the best solution that is offered by Sterling Order Management System.
  8. Based on the supported and unsupported scenarios, the Optimization API returns the response for the eligibleForOptimization attribute as Y or N.
    1. If eligibleForOptimization = N, the response for the Optimization API is ignored and Sterling Order Management System continues with the generated best solution.
    2. If eligibleForOptimization = Y, the flow continues with the choices that are selected by the Sterling Intelligent Promising Optimization Service.
    3. If the API call throws an error or an exception occurs,
      • When the integration is set up in the idle mode, if any error occurs while calling the Optimization APIs, those errors are printed in the error log. The transaction continues according to the default Sterling Order Management System flow.
      • When the integration is set up in the live mode, if any error occurs while calling the Optimization APIs, an error is displayed and the transaction ends.
  9. If implemented, the ExternalCostForOptionsUE user exit is called to filter out carrier services, override per-unit costs for product choices, or reject the product choice.
  10. If choices are overridden by the Optimization APIs or by the ExternalCostForOptionsUE user exit, a new best solution is generated.
  11. The Sterling Intelligent Promising Optimization Service, the Sterling Order Management System Promising API call ends.
    Note: As the optimization in the idle mode is done asynchronously, the flow continues with the Sterling Order Management System generated best solution.