IBM Sterling Ideas

formerly Watson Supply Chain

Submit new product ideas for IBM Sterling solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain

Connect with IBM experts and your peers on the Supply Chain Collaboration Community and the Order Management Interest Group

ITXA support Bulk Update Codelist API without Version Number

Build-Date: 20181003.0829

Case Number: TS001467199


  1. We are referring here Bulk Update Codelist API . Not the Update Codelist API
  2. We want to use the API from Sterling Business process
  3. The below is the API URL used in the SBI BP http Post Service and this works fine.

<assign to="URI" from="&apos;/spe/svc/codelists/DEFAULT|DON_TEST|||8/actions/bulkupdatecodes&apos;"/>

Here "DON_TEST" is the Codelist Name , 8 is the Codelist Version Number.


Our Objective is to not use version number in the URL whereas API should intelligent enough to find out the selected default version from the Codebase and work on that version. It's difficult for us to keep track the latest version and provide the same in the URL and it will be more error prone incase version mismatch.

API also should create a new version while updating the latest version and mark the new version as latest version in the system.

4. We have to provide the Old items value as well as the new item value when we want to do any update of the existing item using Bulk Update .


We have to provide ID field details in the API Body when we want to update any existing item(Sender Code, Receiver Code, Start Date, End Date, Description) with new item.

Ex. Here we want to update Don15(Old Sender Code/Receiver Code) with Don156( New Sender Code/ Receiver Code). Input Json file will be look like below


"codes": [


"columns": null,

"description": "don156",

"endDate": null,

"id": "DEFAULT|DON_TEST|||8|don15|don15",

"receiverItem": "don156",

"senderItem": "don156",

"startDate": null




Expectation: There must be some way to avoid giving Old data items while updating with new data items. As we are trying to build some automation to update Codelist from SBI Business Process hence it will be difficult for us to maintain both Old Items and New items.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Oct 22 2018
  • Declined
How will this idea be used?

Customer wants this feature should be available ASAP in Production as there is a situation where we want to Update Multiple Code list at a time and we want to build some automation to update all code List at a time.

What is your industry? Wholesale Distribution & Services
What is the idea priority? High
DeveloperWorks ID
Link to original RFE
  • Attach files
  • Admin
    Luke Raiano commented
    9 Jan 02:50pm

    No plans to implement as it would require extensive work in the API.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    31 Jan, 2019 05:38am

    Hi Team,

    We have not received any update on the subject idea yet. Kindly let us know the progress.



    Prosenjit Das