IBM Sterling Ideas
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:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you, 1. Post an idea 2. Upvote ideas that matter most to you 3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
"Error in ParseElement" occurs because only the standard 36 field / 524 character EDI_DC40 Control Record is supported by the TX SAP JALE Adapter. This is causing the interface which uses a custom Idoc control record more than the 540 character to fail with the Error in ParseElement message
|What is your industry?||Energy & Utilities|
How will this idea be used?
This will allow customers to continue using custom SAP idocs with the JALE adapter. In most of the cases it would not be possible for the SAP application to revert back to standard Idocs as there might be specific business cases to add custom fields to EDI_DC40 control record
Do not place IBM confidential, company confidential, or personal information into any field.