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.

GTIN based Inventory Availability and Scheduling in OMS CoC and Inventory Visibility

For our current client, inventory items are uniquely identified using UPCs(not to be confused with UPC in generic sense) and not SKUs, while the selling catalog identifies items using SKUs. These UPCs can change every year for the same item. For example, a warehouse in Balsam can have below 3 different supplies for SKU-A as Onhand.

Catalog Item Identifier

Inventory Item Identifier

Warehouse

Manufacturing Year

Quantity

SKU-A

UPC-A1

43

2019

50

UPC-A2

43

2020

70

UPC-A3

43

2021

100

But the client needs visibility across all associated UPCs while they are looking for inventory of a particular SKU.

This was earlier handled using the GTIN functionality in OMS. We use to setup SKU-A and all associated UPCs as separate products and with a common GlobalItemID and OMS would take care of ATP visibility across items and also the scheduling of it.

With GTIN functionality now missing in IV we are not sure how to handle this situation. This is an absolute necessity for our client to go live.

  • Guest
  • Nov 18 2021
  • Planned for future release
What is your industry? Retail
How will this idea be used?

For our current client, inventory items are uniquely identified using UPCs(not to be confused with UPC in generic sense) and not SKUs, while the selling catalog identifies items using SKUs. These UPCs can change every year for the same item. For example, a warehouse in Balsam can have below 3 different supplies for SKU-A as Onhand.

Catalog Item Identifier

Inventory Item Identifier

Warehouse

Manufacturing Year

Quantity

SKU-A

UPC-A1

43

2019

50

UPC-A2

43

2020

70

UPC-A3

43

2021

100

But the client needs visibility across all associated UPCs while they are looking for inventory of a particular SKU.

This was earlier handled using the GTIN functionality in OMS. We use to setup SKU-A and all associated UPCs as separate products and with a common GlobalItemID and OMS would take care of ATP visibility across items and also the scheduling of it.

With GTIN functionality now missing in IV we are not sure how to handle this situation. This is an absolute necessity for our client to go live.

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.