Scenarios

Understand the integration by referring to the supported and unsupported scenarios.

Supported scenarios

Consider a sales order with one order line with Delivery method as SHP and Document type as 0001.

  • According to the Sterling™ Order Management System Software sourcing rule, this line can be sourced from any one of the 15 nodes.
  • The integration is enabled in live mode.
  • The minimum nodes for ranking are set to 10 and the rank nodes limit is set to 5.

The scheduleOrder API is called. The integration calls the Rank API.

The Rank API returns 5 optimum nodes and the eligibleForRank attribute as Y.

Choices and the best solution are generated by Sterling Order Management System Software based on the 5 nodes.

The integration calls the Optimizer API with the generated choices and the best solution.

The Optimizer API suggests a node that is different than the node that is selected by Sterling Order Management System Software for best solution.

Sterling Order Management System Software regenerates the new best solution by using the node that is suggested by the Optimizer API.

The new best solution is used for order scheduling and the scheduleOrder API call ends.

Note: In the idle mode, the best solution that was generated by Sterling Order Management System Software is used for order scheduling.

Unsupported scenarios

Consider a sales order with one order line with Delivery method as PICK and Document type as 0001.

The ShipNode="N1" and IsFirmPredefinedNode="N" attributes are set.
  • According to the Sterling Order Management System Software sourcing rule, this line can be sourced from any one of the 15 nodes.
  • The integration is enabled in live mode.
  • The minimum nodes for ranking are set to 10 and the rank nodes limit is set to 5.

The scheduleOrder API is called. The integration calls the Rank API.

The Sterling Intelligent Promising Optimization service does not support the PICK Delivery method. The Rank API returns the eligibleForRank attribute as N.

Sterling Order Management System Software ignores the Rank API response and generates choices based on all 15 nodes and picks a node for the best solution.

The integration calls the Optimizer API with the generated choices and the best solution.

The Optimizer API does not optimize this call and returns eligibleForOptimization = N.

The Sterling Order Management System Software generated solution is used for order scheduling.

Note: In the idle mode, the best solution that was generated by Sterling Order Management System Software is used for order scheduling.