Watson Supply Chain Ideas

Submit new product ideas for Watson Supply Chain 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

Submit ideas for other Watson Customer Engagement Products:

Watson Marketing
Watson Campaign Automation
Watson Commerce

Multiple custom data locations for a field in Document Configuration

Currently, there is only one selection offered when Document Configuration is established for a UI Field.
Need functionality to have multiple locations checked and often the qualifier is the trigger.
Illustration:
PO# collection from an 850 Order:
I could set one data location to read from BEG04 when BEG02 is SA and second data location to read BEG03 when BEG02 is BE.

BEG*00*SA*Branch-D*1234567*20190308@
vs
BEG*00*BE*CC0092111*000*20190307@

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Mar 8 2019
  • Needs More Information
How will this idea be used?

Without this, 50% of the orders in BTI will be aggregated on a concept, not the working PO# exchanged between the companies.
This gives IF ELSE logic to manage key fields.

What is your industry? Fabrication & Assembly
What is the idea priority? High
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    17 May 12:26

    Document Configuration only offers One location to assign a field identifier. The request is for document configuration to have multiple locations, to function as an IF ELSE style of logic. Look for a matching value of the 1st listed element and if false fall to the 2nd listed element. When I pull up Document Configuration I can see that many times a field identifier has 2-3-4 elements/codes that are researched. Why Can't I also assign more?

    The business case is an Open PO (BE) vs Standalone. (SA). 

    Today, BTI will read for the BEG 03, regardless of the BEG qualifying element. 
    In my business,
    if the BEG 02 = BE then assign the PO# identifier from the BEG 04.
    if the BEG 02 = SA then assign the PO# identifier from the BEG 03.