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.
getAjustmentReasonList API is unusable since there is no WMS screen to create Adjustment Reason at store level.
- Use Common Code List to maintain adjustment reason. Maintained from Application manager
- Use Custom table to maintain adjustment reason in OMOC UI. Build maintenance screen for table
- Use hard-coded list of reason in OMOC. Requires code changes to add/remove reasons
The current SIM API to add/remove inventory does not capture Adjustment Reason Code and Reason Text.
Comparing the existing adjustLocationInventory API, we have a Audit tag in which we pass the above attributes.
The audit records the AdjustmentType as ADJUSTMENT along with ReasonCode and ReasonText.
There is a provision to pass adjustmentType in SIM API but is limited to the following adjustment types:
RECEIVING, SALE, COUNT, RECLASSIFICATION or RETURN
Because of this limitation we are not able to save the ReasonCode and ReasonText as references.
Expectation from IBM:
Add an additional AdjustmentType as ADJUSTMENT or MANUAL
|What is your industry?||Retail|
How will this idea be used?
This is used in the manual adjustment process. Not having a manual adjustment type is a defect. We use it in 9.1.
Do not place IBM confidential, company confidential, or personal information into any field.