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.
Connect with users and IBM experts on the
B2B Collaboration Community
Submit ideas for other Watson Customer Engagement Products:
• Watson Marketing
• Watson Campaign Automation
• Watson Commerce
While on-boarding partners to the SCBN platform whenever we are trying to clone an existing outbound EDIFACT envelope we are getting the Scenario Release Number value : D96A getting populated by default . This should not be the case as the existing envelope we are cloning did not have this value/parameter in the first place . The cloned new envelope should have the same parameters as the existing envelope . The value is conditional as per UNH/EDIFACT standard and should not be populated by default. This value results in a bad UNH segment for the EDI file and partners reject it on their side harming business .
Salesforce Case :TS001240649 where customer had complained of bad UNH segment as D96A value populating twice .
How will this idea be used?
As part of Watson Customer Engagement we work on on-boarding partners to our Hosted Sterling Integrator under SCBN offerings . Our customers engage in EDI transactions with their on-boarded partners and this value coming twice in the EDI UNH segment is unacceptable for many of the partners and causes data to fail on their side affecting business. This would restrict failures to happen for business transactions resulting to faster realizations .
|What is your industry?||Other|
|What is the idea priority?||Medium|
|Link to original RFE|