Skip to Main Content
IBM Sterling


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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Submitted
Created by Guest
Created on Dec 4, 2025

Deenvelope service failing due to string X in the UNB segment

We are currently on Sterling Integrator 6.2 version - On Premise. We had a connection with a partner who used to send us EDIFACT file for DELJIT Message Type.


Recently due to the version change from 2.1 to 3.1 - there is the change in the UNB segment from the partner.



As the underlying VDA 4985 T2 Global DELJIT increases


from version 2.1 to 3.1, there is a change in the Syntax


Version Number field in the UNB segment.


• Instead of version number 3, code X will be transferred


here in the future.


• The new syntax version number also results in a change in


the "Date of creation" field.


• In the future, the date will be transmitted here in 8 digits,


including two digits for the century.


Before: UNB+UNOC:3+O0013000560MB050000


:1:X+X:1:X+071005:0951+123++++++1'



After: UNB+UNOC:X+O0013000560MB050000


:1:X+X:1:X+20071005:0951+123++++++1

When partner sent the file with this new UNB segment - it failed at Deenvelope step.



We would like to know if the value X is supported as this is EDI standard, however when file passes through the EDI Devenelope step it fails due to string value X.

What is your industry? Energy & Utilities
How will this idea be used?

This will allow the support for EDIFACT 3.1 version of files from all customers.