VDA, outbound

Envelopes are header and trailer segments that enclose EDI data, much like a paper envelope encloses a paper document.

Overview

An outbound envelope that contains the data that is sent from one sender to one receiver in the same transmission. An outbound envelope is, alternatively, referred to as "To EDI" envelope.

Key identifiers

When you edit an envelope configuration, the values for some of the key identifier fields, such as the Sender ID and Receiver ID fields, cannot be edited. Editing the fields might impact the associated routing rules. However, to edit the fields, you can contact IBM Support. For more information about which Key identifiers remain noneditable, see Noneditable fields.

Acceptor lookup alias: Identifying string that is used with the sender ID and the receiver ID to look up this envelope with the EDI Encoder service. This alias associates a document with the service that it requires. The valid value must be at least one limited standard character.
Note: For 997 or 999 documents, the ALA format must be entered in the format as defined by the Inbound GS/GE envelope. For example, if an inbound 004030 document is received and Acceptor lookup alias for generated 997/999s is set to use 99X_[group version] format, then the ALA must be entered as 99X_004030.

From sender code: Allowed characters are a-z, A-Z, 0-9, space, -, _, period, comma, ?, =, *, +, ', (, ), %, @, &, and #. The sender identification number. The valid value can be 1 to 12 characters.

Unto receiver code: Allowed characters are a-z, A-Z, 0-9, space, -, _, period, comma, ?, =, *, +, ', (, ), %, @, &, and #. The sender identification number. The valid value is 3 standard characters.

TTYP transaction type: This field accepts alphanumeric characters.

Supplier details

Sales tax ID number (receiver): This alphanumeric string accepts up to 20 characters.

Sub-suppliers: This alphanumeric string accepts up to 20 characters.

Company registration number: This alphanumeric string accepts up to 20 characters.

Carrier number: This alphanumeric string accepts up to 20 characters.

Warehouse keeper code: This alphanumeric string accepts up to 20 characters.

Transmission purpose code: This alphanumeric string accepts up to 20 characters.

Payment identification number: This alphanumeric string accepts up to 20 characters.

Payment date: The date format must be YYYY-MM-DD.

Envelope options

Use Global Control Number for SNRF Sender Reference: By default, No is selected from the drop-down. You can change it to Yes. If you select No, you must provide some value in the Local Control Number for SNRF Sender Reference field.

Local Control Number for SNRF Sender Reference: If you select No, you must provide some value in the Use Global Control Number for SNRF Sender Reference field, the caption of this field changes to Global Control Number for SNRF Sender Reference.

Hold locks until commit: Holding a lock until commit does not allow for any gaps in control numbers. However, selecting this checkbox slows down performance. Enable it only when you cannot have gaps in control numbers.

Max Docs Per Interchange: Select the checkbox to perform a duplicate control check. If you select the checkbox, the Checksum TFD1 and Checksum TDF 2 fields are required fields that accept string value for input.

Encode documents: By default, the checkbox is cleared. If you select this checkbox, you must input a value in the Encoding field. You can select the encoding type from the drop-down.

Use correlation overrides: Select Always, Default, Never, or Wildcard (*) from the drop down.

Validate transaction input: Select this checkbox to validate the input.

Validate transaction output: Select this checkbox to validate the output.

Pr-enveloping map name: Alphanumeric field.