Packages example

The edfiso9735-41 type tree contains service segment definitions for packaging and security along with any updates to the CONTRL message.

The EDIFACT documentation identifies the UNO, Object, UNP as a package. The UNO/UNP should follow EDIFACT syntax with a segment terminator following the segment information. The documentation states that the data presented as an object shall not be governed by EDI syntax rules. This means the object cannot be validated as a typical EDI message. Although it is possible the object is encrypted data and when decrypted could be validated using the usual EDI syntax and the SupplyChain EDI compliance checking.

The documentation does not identify if the Object attached in the package should be terminated with a segment terminator or any other terminator.

Terminating the Object attachment would allow the UNO/UNP segments to be parsed and processed in the TX map using the edfiso9735-41 type tree and allow the Object to be detached without the UNO/UNP service segments. The edfiso9735-41 type tree defines the OBJECT group to allow this processing for both inbound and outbound for the Package Category.

If the Object is not terminated with a segment terminator, the UNO/UNP become part of the Object to be detached and must be processed outside the TX map used to detach the package which requires a user defined type tree and separate map. The edfiso9735-41 type tree defines the PACKAGE group to allow this processing for both inbound and outbound for the Package Category.

The input definition used for the example packages is defined as UTF-8 to ensure binary data is processed preserving the original data.

The output definition for the EDIFACT package object is defined as UTF-8.