IBM Sterling Ideas
Shape the future of IBM!
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:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you, 1. Post an idea 2. Upvote ideas that matter most to you 3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
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.
Do not place IBM confidential, company confidential, or personal information into any field.