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
[Copy] Have one "map" to convert EDI into a human readable format, such as HTML
Currently, we have several maps that translate EDI into HTML. They are for 824s, 864s, and 860s. There are separate maps for various versions (i.e. 4010, 4060, 5010). The maps are VERY large and complex. Plus, they all contain user exits, and IBM currently does not support maps with user exits through Config Hub. Therefore, we cannot modify these maps, or create new maps like this.
We need a single "map" that will take any EDI file and produce a human readable document, such as HTML, like Liaison EDI Notepad.
What is your industry?
How will this idea be used?
Having one "map" to create human readable documents from any EDI file would greatly simplify our process of providing the necessary info to business users for transactions like Application Advice, Text Message, and PO Change Request. These are transactions that do not create an application file, yet the data needs to be presented in a user-friendly format.
Because there are differences in the current HTML maps, based on who created them, they do not all produce a "standard" format, and this is what we need.
Do not place IBM confidential, company confidential, or personal information into any field.