ItineraryStep - Edifact assemble

UNOA and UNOB Character Sets in EDIFACT

When the receiving partner is configured to use either the UNOA or UNOB character set in their EDIFACT settings, the system's assembler ensures that the resulting EDIFACT message complies with the selected character set's restrictions.

Character Replacement Handling

Since UNOA and UNOB support only a limited set of characters, any unsupported characters in the message must be replaced. The system handles this automatically using a predefined replacement character or a set of custom replacement rules.

Default Replacement Character

• Key: EdifactDefaultReplacementChar

• Description: Specifies the default character that will replace unsupported characters.

• Constraints: Only one single character is allowed (e.g., 0 by default).

Custom Replacement Characters

• Key: EdifactCustomReplacementChars

• Description: Allows you to define specific character replacements in the form of mappings.

• Format:

  A=B##C=D##E=F

  This example means:

  • Replace A with B

  • Replace C with D

  • Replace E with F

You can configure both settings through the Settings menu to tailor the EDIFACT output to the required character set constraints of your trading partner.

Overwrite values via context properties

This step gives the option to overwrite values in the UNA and UNB segments with values from context-properties.

The following properties can be overwritten:

If any of the above properties are promoted before edifact assemble step, these values will be used instead of the values from the flow and the partner edi-configuration.