![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
After you configure the interchange version, you configure the group version, even if a functional group is not used. To add a group version, do the following:
2. Click New Group Version.
In some cases, you may need to handle inbound B2B-EDIFACT messages of the same message type that do not use a function group. These messages may belong to different version numbers or message release numbers or both, but not be contained within a function group. For information on handling such messages, refer to Adding a Message to a Group Version.
Table 2 Group Version Fields The name must correspond to the message version number and message release number which would be designated in the functional group header (UNG) segment. For example: Version number: D. Release number: 98A. If you are not using a functional group, enter EmptyGroup and then proceed to Adding a Message to a Group Version. Example: D Example: 98A UNG-S006/0040 Application Sender ID Within the sender's organization: name or code identifying the originating division, department, and so on. UNG-S007/0044 Application Recipient ID Within the recipient’s organization for which the group of messages is intended: name or code identifying the division, department, and so on.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |