EDI document properties
The following tables list the document properties based on whether the element you select is a composite, record, or field.
Any inbound document that deviates from the properties you set for each of the elements generates
appropriate validation errors in the Course of transaction. For information
on how to set the validate option, see the webMethods Integration documentation for the Electronic Data
Interchange application. The errors that appear in the Course of transaction
depend on how the orchestration you define on webMethods Integration handles and returns the
errors.
Note: For inbound EDI documents, if an attribute is not mandatory and an error occurs during
its extraction, the status is set to error instead of a warning.
Record Properties
| Property Name | Description |
|---|---|
| Name | Name of the selected node. |
| Alternate name | Another name for the record definition. |
| Description | Description of the record definition. |
| Mandatory | An instance of this record must exist in the inbound document.
|
| Ordered | Child records in the inbound document must appear in the same order as they
appear in the record definition. This property applies only to records that are children of this
record.
|
| Max repeat | Maximum number of times this record definition can repeat in the inbound
document. Specify a positive integer. The maximum limit is 999,999,999. The following values are
interpreted in a specific manner:
|
| Area | The area that is assigned to this record definition. The property determines the
possible values that you can assign to a record.
|
| Position | The position of the record in an inbound document. Select the checkbox to specify the position of the record. The maximum limit is 9999. |
| Allow undefined data | The record definition is considered valid despite having undefined data. A
record definition allows undefined data only if the inbound document is configured to do so.
|
| Check fields | Indicates whether extra fields in the record instance must be treated as errors.
|
| Validator | The type of validator to use to validate instances of this record definition.
|
Composite Properties
| Property Name | Description |
|---|---|
| Name | Name of the selected node. |
| Alternate name | Another name for the composite definition. |
| Description | A description of the composite definition. |
| Mandatory | The field must exist as a composite in the document.
|
| ID code | The ID code of the composite definition. The composite definition in the referenced record definition defines the value of the ID code.. |
| Check fields | Indicates whether extra fields in the composite instance are treated as errors.
|
| Validator | Type of validator to use to validate instances of this composite definition.
|
| Extractor | Field number in the record that contains the composite you want to extract. It extracts the
field or composite data from the record or extracts the sub-field data from the composite. If this
property is empty, the composite is not extracted. Note: The extractor works for a composite only if
the field delimiters and sub-field delimiters are defined for the inbound document.
|
Field Properties
| Property Name | Description |
|---|---|
| Name | Name of the selected node. |
| Alternate name | Another name for the field definition. The alternate name is used as the name of the
String field that corresponds to this field definition in an inbound
document. |
| Description | The field definition in a composite reference or a record reference at the specified location in the inbound document. |
| Mandatory | An instance of this field definition must exist in the inbound document.
|
| Data type | The data type of the field that accepts inputs in (data type, minimum length, maximum
length) format. The maximum character length limit is 9999. Modifying Data
type updates the Format service. The following data types are supported
|
| ID code | The ID code for the field definition. The EDI standards define an ID code. |
| Format service | Format type that is applied to the field definition. The format service validates either the
content in a field or converts the content in an associated field to an appropriate format. For
example, a format service can validate if the content associated with a node is of numeric type.
Another format service might convert a timestamp from HH:mm:ss.SS format to
HHmmssSS. The following list describes the properties of the Format service:
|
| Validator | The type of validator to use to validate the field. The following list lists the supported
types:
|
| Extractor | Location of the data to extract for this field. The extractor works for a field only if the
field delimiters are defined for the inbound document.
|