Is there an approach that would allow a user to get an audit history for all Items for a specific Tenant/Enterprise and receive the data in a format that can be converted to a CSV file. The intent is to have a business user be able to evaluate all...
In SIP, PATCH itemAssignedAttributes should have capability to modify or override the value in the collection field "values" of the existing itemAssignedAttribute.
While capturing the demand in SIP, we want to collect, persist, and publish additional information associated with the Demand. This will help the demand data to be more informative to downstream systems.
Configuration to control Sell and Fulfill capability at node level
Can a product feature be provided as: 1. Ability to turn ON/OFF a node for availability or fulfilment or both. 2. Ability to associate a duration on the action to turn OFF.
Business is expecting the following capability in SIP: 1. Ability to identify a product as a launch product 2. Ability to manage inventory association offered for launch pre-order/pre-sale 3. Seamless integration between OMS and IV w.r.t changes i...
Business if expecting following capability : 1. Ability to sell beyond available quantity. 2. Ability to define quantity to be sold beyond available Qty, as a percentage or unit in the catalog hierarchy 3. Ability to configure, calculation of over...
SIP: Implement Priority Based Sourcing Rules in Sterling Intelligence Promising
Priority of shipnode in Distribution group is not working while calculating estimated delivery date using Calculate item delivery or pickup date using finite capacity windows API. Customers need Ship Node Priority Based Sourcing” in SIP
Sync Supply to have a capability to just report the mismatches and not apply the differences.
We want a capability in SIP to just report / publish an event with the mismatches evaluated during the inventory synchronization flow and not always apply the same. Something similar to the " ApplyDifferences " capability in the GIV world. There a...
Configure additional costs to be considered by SFO for optimizing the node
Apart from the Processing and Shipment Charges, that are being considered as part of the Shipping Model to calculate the cost to serve from the node, SFO should also have a way to add the cross-border customs charges, insurance cost and other misc...
SFO to consider the ad hoc/unplanned node delays during optimization
The ad hoc delays need to be captured in SFO as separate parameter in order to account, longer processing time to ship the orders from the nodes during and post a sale event or, shortage in the manpower leading to delays. The ad-hoc delays need to...