This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
The loadInvnetoryMismatch API is used to bulk load inventory (supply qty for each SKU/location combination) into OMS and this API has a feature (CompleteInventoryFlag) where the API can reset inv to 0 for any items that are not passed in the input to OMS. Using the CompleteInventoryFlag, the external system feeding inventory to OMS can feed inventory only for items with non zero.
If the external system is feeding net available units (on hand supply - open orders released to fulfillment center) to OMS instead of the on hand supply qty, the loadInventoryMismatch API cannot be used and the OMS product provides processAvailabilitySnapshot API to import available qty into OMS. This API calculates the net on hand by adding back specific demands to the available units passed in the input to this API. But, this API does have the feature where we can only pass items with net available units > 0 and expect OMS to reset inventory to 0 for items that are not passed in the input and have no open demands that are released to the fulfillment center.
What is your industry? | Retail |
How will this idea be used?
Currently, at Tapestry, inventory availability is tracked in SAP and SAP provides net available units t OMS as part of the inventory sync process (full sync). SAP will deduct any open orders sent to the fulfillment center from the net on hand supply to derive the net available units. Please note that SAP tracks demands for all business units (direct to consumer, wholesale, replenishment etc) and not all demands are made visible to OMS (OMS tracks only direct to consumer demands from retail and eComm channels). The SAP DB view that is exposed to OMS to track inventory availability(for inv full sync) also does not have any date/timestamp indictor to identify which records have been modified. As a result, the number of records in the SAP inv view is very high if we include SKU's with net available as 0 as this can include items that had inventory at any point in time (could have gone to 0 units 2 years ago). To minimize the number of SKU's we process in the OMS inv full sync process, we would like to only include items that have net available units more than 0. By enhancing the processAvailaibltySnashot API to work in a batch mode and have a mode where it can reset inventory for items that are not passed in the input and for which there are no open demands in a specific state, it will help us support the Tapestry inv sync requirements without customizations. |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
This Idea is from 2019 and set as planned for Future release. In which we can expect this change.