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

Allow duplicate 997's to create SAP Status Message instead of failing

Today in SCBN, if a partner resends a 997or sends a new 997 for an already acknowledged document, and the 997 is used to generate a status message back to SAP, the process fails. SCBN should allow for SAP Status messages to be generated and sent to the client's SAP System regardless of how many 997's have been received for the original document. Our specific use case involves a trading partner who routinely has to reprocess documents in their EDI system. On each reprocess it sends the 997 back to us and SCBN. For the first 997 received, the SAP status message is generated correctly. For any subsequent 997 received, SCBN fails the process creating unnecessary failures for the support team to manage and inflating the dashboard error message reporting.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Sep 6 2019
  • Needs review
How will this idea be used?

997's acks will generate SAP Status messages and flow through the system instead of generating failures if a recurring acknowledgement.

What is your industry? Consumer Products
What is the idea priority? High
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files