Watson Supply Chain Ideas

Use this form to submit an idea for a new product feature. The product team will review your input and provide status updates as decisions are made regarding the request.

Before you submit a new idea, please view requests that have already been submitted. If your idea has already been submitted, you can add comments or vote on the existing idea, thereby indicating your agreement with the idea. We may use this information to help prioritize development of new features.

 

Submit ideas for Watson Marketing and Watson Commerce products

Business specific Translation Report feature in GIODE

Every Translation Report generated should be first routed through an Internal database specifically created for each client within GIODE, before it is being displayed in Inflight. The translation report would go in as input to the database pointing to client specific issues built entirely on the user defined error codes.

The client specific data base can be identified by the business alias the translation report belongs to

The database reads the file, looks for the specific user defined codes for the business fields that are either missing or non-compliant and generates a report that a business user will clearly understand. Right now, the reports just a field with a corresponding number is missing. The field number has no significance to the business user. The Enhanced translation report also does not provide the information the business user is looking for.


Hence, there is a imminent need to upscale and upgrade the translation report as recommended above.

 

The Benefits would be:

Client need not reach out to PER Implementers and Support to findout the reason for failure.

Business users would love these reports in comparison to the translation reports that are displayed currently.

The ease of understanding the failure increases by several notches.

The translation reports finally starts speaking business and not just technical verbiage.

Support and PER Implementers need not reach out to mapping team to find out the reason for failure, which gets counted as iteration.

Mappers do not have to do unit testing to find out the reason for failure and communicate back to the source which requested information.

Reduces significant time for all stakeholders involved and also cuts down iterations.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Apr 24 2018
  • Declined
How will this idea be used?

Client need not reach out to PER Implementers and Support to findout the reason for failure.

Business users would love these reports in comparison to the translation reports that are displayed currently.

The ease of understanding the failure increases by several notches.

The translation reports finally starts speaking business and not just technical verbiage.

What is your industry? Non-Industry Specific
What is the idea priority? High
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files
  • Admin
    John DELPIZZO commented
    October 17, 2018 17:40

    Will reconsider Error Reporting as part of SCBN Next. Not clear that we'll take it quite this far.