This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Alter The Transformation Extender Error Reject Report To Have An XML Format Similar To B2Bi
We currently running SI B2Bi v 6.1 and also have ITX 10.1.1 installed. ITX running with launcher on our AIX file system which works with BP's in SI B2Bi. We are requesting that the failures coming out of ITX be in the B2Bi XML Trans Report format so that both error reports have a consistent format. One issue we have is that the ITX and B2B Integrator legacy mapper have very different error report outputs and thus cannot be run through the same XSLT to format the data in a nice readable email. The consistent format would enable automatic error notification to the data sender in a format that can even be interpreted by non EDI users. While ITX error codes are published in a defined list, the structure of the report and record relationships are not published. Without a published format or .mtt the error file format is not completely known to users. The error files rules for how error records (potentially multiple error records per error condition) tie together or to a parent record is also not published. In the example below a human with EDI familiarity can determine the pairing of E0158 records and E0178 record but a machine cannot make that pairing without understanding the parent child relationship, number of record occurrences and the ‘rules’ without a defined format.
I0000 Interchange unique id: NoUniqueID
I0001 Group index: 1, control number: 56
I0002 Transaction index: 1, control number: 0043
E0198 One or more segments in the transaction are in error.
E0158 The segment at position 2, segment id 'BSN' contains data element errors.
E0178 A data element contains an invalid date value: element 3, subelement/part n/a, value '150218'.
E0158 The segment at position 4, segment id 'DTM' contains data element errors.
E0178 A data element contains an invalid date value: element 2, subelement/part n/a, value '150218'
The ultimate goal is an XML based error report for ITX that mirrors what Sterling Integrator B2Bi uses in translation report service. The XML based report should have a hierarchy that ties all relevant notes about a particular error together.
What is your industry?
How will this idea be used?
The updated format will allow us to create automated error emails for failed transactions in a readable business friendly way via an XSLT. The automation will negate the need for support staff to manually read error files, describe the failures for email recipients and manually email them. This is very important to our organization as we have a compliance program with fines for bad data. We have the automated alerting functionality with B2Bi today and are taking a step backward with ITX error reporting.
Do not place IBM confidential, company confidential, or personal information into any field.