EDI File - Load Data

Loads data from an EDI document into a Data Model.

Remarks

The LoadData command extracts and loads structured data from an EDI X12 document into a Data Model for a Batch Folder.

Overview

• This command parses the attached EDI file, maps its contents to the configured Content Type, and generates a Document Instance containing the extracted data.
• Optionally, it can classify the Batch Folder by matching the EDI schema to a Content Type using the 'Mappings' property.
• After extraction, the command can save the data, export it, or perform both actions, as determined by the 'Disposition' property.

Typical Workflow

1. The EDI file is parsed and validated.
2. If 'Mappings' are provided, the command attempts to assign the correct Content Type to the Batch Folder based on the EDI schema.
3. The Batch Folder's index data is cleared and a new Document Instance is generated from the EDI content.
4. Any errors encountered during parsing are flagged on the Batch Folder.
5. Depending on the 'Disposition':
   • Save: The extracted data is saved to the Batch Folder.
   • Export: The data is exported using the configured export behaviors for the Content Type.
   • Both: Both save and export actions are performed.

Configuration

• Mappings: Define how EDI schemas are mapped to Content Types. If documents are already classified, this can be left empty.
• Disposition: Choose whether to save, export, or do both with the extracted data.

Usage Notes

• Use this command as part of an automated workflow to convert EDI X12 files into structured data for downstream processing, validation, or export.
• The command supports complex EDI documents, including those with multiple envelopes, groups, and transaction sets.
• Errors encountered during extraction are flagged for review, ensuring data quality and traceability.

Example

To process a batch of EDI files:

• Configure 'Mappings' to associate each EDI schema with the correct Content Type.
• Set 'Disposition' to 'Both' to save the extracted data and trigger export behaviors.
• Run the command on each Batch Folder containing an EDI file.

Related Concepts

• Content Type: Defines the data model and export behaviors for the extracted data.
• Document Instance: The structured data result of the extraction process.
• Export Behavior: Controls how and where extracted data is exported.

For more information, see the documentation for Data Model, Content Type, and EDI X12 processing in Grooper.

Properties

See Also

Schema MappingEDI File