Best practices
Here is the checklist of Sterling™ Order Management System Software and Sterling Intelligent Promising Inventory Visibility phase 2 integration best practices to enable System Integrators with necessary information to ensure a successful integration.
Limit on the message size of the JSON input
Sterling Intelligent Promising Inventory Visibility imposes a limit on the message size of the JSON input that is
sent to Sterling Intelligent Promising Inventory Visibility. Many factors such as the number of order lines, number of
ship nodes in your sourcing rule, or size of the text fields such as item IDs, UOMs, product classes
can impact the size of the message. If the message size of the JSON input exceeds the limit, Sterling Intelligent Promising Inventory Visibility returns an error response code, for example, 2019-08-06
09:31:15,500:ERROR :Thread-27_Sub_IVPostSuppliesAsynchronously: Received failure status code:413 in
response:{status=413|headers=[Date->Tue, 06 Aug 2019 13:31:15 GMT, Content-Type->text/plain;
charset=UTF-8, Transfer-Encoding->chunked, Connection->close]} with body:Payload too large.
To avoid such error, configure the number of applicable nodes and order lines appropriately. For
example, for 1 line order, the applicable ship nodes must be less than 25.
In scheduling rule, ensure that the Cancel order for inventory shortage checkbox is not selected. This is because, in case of shallow inventory the order might get backordered initially and scheduled the next time when the order is picked up for scheduling. However, for orders that remain backordered for a given duration use the Order Monitor agent to cancel the backorders.