EDIFACT outbound Syntax 4 UNB UNZ (Interchange level) envelope properties
These properties are displayed when you view or edit an EDIFACT outbound Syntax 4 UNB UNZ (Interchange level) envelope. Not all properties can be edited.
Basic properties
For a description of these properties, see the General properties topic.
Control Numbers
For a description of these properties, see the General properties topic.
Advanced properties: 1. Outbound Properties
- (0001) Syntax Identifier
- Coded identification of the agency that controls the syntax and of the character set used in an interchange. Required.
- (0002) Syntax Version Number
- Version number of the standard syntax. Required.
- (0080) Service Code List Directory Version Number
- Version number of the service code list directory.
- (0133) Character Encoding, Coded
- Coded identification of the character encoding that is used in the interchange.
- (0007) Identification Code Qualifier (Sender)
- Coded qualifier of the interchange sender internal ID, as it appears
on the interchange header segment sent to this company or division.
Valid value: Four standard characters
- (0008) Interchange Sender Internal Identification
- Internal interchange ID as it appears on the interchange header
segment sent to this company or division.
Valid value: 12 standard characters
- (0042) Interchange Sender Internal Sub-identification
- Subinterchange ID as it appears on the interchange header segment
sent to this company or division.
Valid value: 12 standard characters
- (0007) Identification Code Qualifier (Recipient)
- Coded qualifier of the interchange recipient internal ID, as it
appears on the interchange header segment that is received from this
company or division.
Valid value: Four standard characters
- (0014) Interchange Recipient Internal Identification
- Internal interchange ID as it appears on the interchange header
segment that is received from this company or division.
Valid value: 12 standard characters
- (0046) Interchange Recipient Internal Sub-identification
- Subinterchange ID as it appears on the interchange header segment
that is received from this company or division.
Valid value: Four standard characters
- Use Correlation Overrides
- When to use correlation overrides.
- Never
- Default. If a document that is being enveloped has outbound envelope correlations set, ignore them.
- Only when the envelope field has a wildcard value (*)
- If the document that is enveloped has outbound envelope correlations set, use them only for fields that the envelope definition defines as the wildcard.
- Always
- If outbound envelope correlations are set for an enveloped document, use them on any field regardless of the value in the envelope definition.
- Use the default specified in enveloping.properties
- Specify any of the above three choices in the enveloping.properties file. If outbound envelope correlations are set for an enveloped document, use the value from enveloping.properties.
- Use global control number
- Whether this envelope definition must use a global control number
to uniquely identify transactions. No indicates that the envelope
definition must use its local global control number. Required. Valid values:
- Yes
- Yes (and generate name from data)
- No
- Default.
These are the Assign control number properties:
- (0020) Local Interchange Control Reference
- Interchange control reference number that is used locally. Select
a previously defined number to reference.
Valid value: Nine standard characters
- Sequence Type
- The type of control number sequencing that is used.
Valid values: SPE (default), Database
If Sequence Type is set to
SPE, this Locking Mode property is displayed:
- Hold locks until commit
- Whether to restrict access to the messages until all changes are
committed.
Valid values: Yes, No (default)
- (0022) Recipient Reference/Password
- Reference or password to the recipient's system or to a third-party
network as specified in the partner interchange agreement. Optional.
Valid value: Up to 15 standard characters
- (0025) Recipient Reference/Password Qualifier
- Qualifier for the recipient's reference or password. Optional.
Valid value: Two standard characters
- (0026) Application Reference
- Identification of the application area, assigned by the sender,
to which the messages in the interchange relate. Optional.
Valid value: Up to 15 standard characters
- (0029) Processing Priority Code
- Code that is determined by the sender that is requesting processing
priority for the interchange. Optional.
Valid value: One standard character
- (0031) Acknowledgment Request
- Code requesting acknowledgment for the interchange. Optional.
Valid value: String
- Acknowledgment overdue after this many hours
- Number of hours after which the acknowledgment is considered overdue.
Optional.
Valid value: Four numeric characters
- Acknowledgment overdue after this many minutes
- Number of minutes after which the acknowledgment is considered
overdue. Optional.
Valid value: Four numeric characters
- (0032) Interchange Agreement Identifier
- Identification by name or code of the type of agreement under
which the interchange takes place. Optional.
Valid value: String
- (0035) Test Indicator
- Mode of operation to use for this envelope. Optional.
Valid value: String
- Use WebSphere Transformation Extender compliance checking
- Whether to use WebSphere Transformation Extender compliance checking.
Valid values: Yes, No (default)
Advanced properties: 2. Limit Interchange Size
- Maximum number of documents per interchange
- Maximum number of transactions that can be sent in each interchange.
- Limit Interchange Size
- Maximum size that is allowed for an interchange before it is split
into multiple interchanges that are each under the maximum size limit. Valid values:
- No
- Use smallest transaction limit
- Default.
- Specify size limit
- Use global default in enveloping.properties
- Invoke SPE Driver for Each Interchange:
- Whether the SPE driver is invoked for each interchange.
Valid values: Yes, No (default)
Advanced properties: 3. Delimiters
- Specify Non-Standard delimiters
- Whether nonstandard delimiters are used in the messages.
Valid values: Yes, No (default)
- UNA Segments
- Whether UNA segments are used. The specifications in the UNA segment define the characters that are used as separators and indicators for the interchange. Use this segment only if the interchange contains nonstandard separator characters.
- Stream Segments
- Whether to insert an end-of-line character after each segment
record.
Valid values: Yes, No (default)
Advanced properties: 4. Document Encoding
- Encode Document
- Whether the message is encoded.
Valid values: Yes, No (default)
If Encode Document is set to
Yes, this Encoding property is displayed:
- Encoding
- Type of encoding.
Valid values: Select of the list of encoding types.
Advanced properties: 5. Invoking a Business Process
- Determine the SPE Driver by this criteria
- Criteria by which the SPE driver is determined before invoking
a business process. Valid values:
- None
- Default.
- Specifying a SPE Driver
- Generating the SPE Driver name from the data
- Extraction Options
- (Sterling B2B Integrator hosted installations only.) Criteria
by which the data is extracted by the SPE driver. Valid values:
- Determined by SPE Driver (default)
- Extract to a file system directory
Advanced properties: 6. User Data parameters
- User data name n
A user-supplied name that is set in the process data of an envelope as part of a name-value pair for use in later steps of the process flow.
Valid value: String
- User data value n
- A user-supplied value that is set in the process data of an envelope
as part of a name-value pair for use in later steps of the process
flow.
Valid value: String