Processing EDI Messages in Sub Folders
Processing EDI messages in sub folders is a common requirement when partners or internal systems separate files by customer, document type, or business unit. This tutorial explains how to process EDI messages in sub folders using Advanced ETL Processor. The entire workflow is automated, self-hosted, and handled visually without scripting.
Why process EDI files in sub folders
In real-world EDI environments, files rarely arrive in a single flat directory. Sub folders are often used to separate trading partners, document flows, or integration points. Advanced ETL Processor handles these scenarios cleanly by tracking both file names and folder metadata during processing.
How it works
This workflow was created to assist one of our customers who needed to process multiple EDI files stored across dynamic sub folders. The process uses global variables, a File Loop, and file metadata to maintain full control over file movement.
- Incoming EDI files are stored in sub folders under the Waiting directory
- A File Loop processes files one by one
- The current file name is stored in the #ASN_FILE# variable
- File Metadata stores the parent sub folder in #ASN_PARENT_FILE_FOLDER# and the folder name in #ASN_FILE_FOLDER#
- All files in the Buffer folder are deleted
- The current file is copied into the Buffer folder
- The file format is validated
- If validation fails, a matching sub folder is created in the Failed folder and the file is moved there
- If validation succeeds, the file is transformed
- A matching sub folder is created in the Backup folder
- The original file is moved to the Backup sub folder
- The transformed file is moved to the Completed folder
- The source sub folder is checked and deleted if empty
- The loop repeats for the next file
Notes on folder handling
File locations are controlled through global variables, making it easy to adjust directory paths without redesigning the workflow. Validation is also used to calculate output file names, ensuring consistent naming across transformed files. The design assumes that each sub folder may contain multiple files.
Why Advanced ETL Processor fits this scenario
Advanced ETL Processor is well suited for complex folder-based EDI workflows. Once configured, the process runs unattended and adapts automatically as new sub folders and files appear.
- Visual configuration with reusable variables
- Reliable File Loop and metadata handling
- Built-in EDI validation and transformation
- Automated export to databases, files, or partner systems
Self-hosted and fully controlled
This solution is fully self-hosted. All EDI files remain on your infrastructure, which is essential for organizations with strict data security and compliance requirements.
Useful links for EDI automation
Start with the Advanced ETL Processor Enterprise overview, then download the fully functional 30-day trial.
Use the WIKI, Video Tutorials, and Support Forum while testing the workflow.
Business usage examples
Trading partner separation
EDI files arrive in partner-specific sub folders and are validated, transformed, and archived automatically while preserving folder structure.
ASN processing
Advance Shipping Notices stored by warehouse or carrier are processed from sub folders and exported to internal logistics systems.
Multi-department intake
Different departments drop EDI files into their own sub folders while a single automated workflow processes everything consistently.
Video walkthrough
FAQ
Can Advanced ETL Processor automate EDI processing?
Yes. Advanced ETL Processor can automate EDI-style file intake, validation, transformation, export, archive, and error handling in self-hosted workflows.
Do I need scripts for EDI automation?
No scripting is required for routine workflow steps. You configure the process visually, then test it with sample files before scheduling it.
Which EDI documents can be handled?
Use it for repeatable purchase orders, invoices, shipping notices, inventory updates, and other structured partner files once the format rules are known.
Can failed EDI files be separated from good files?
Yes. A workflow can move failed files to an error folder, keep the raw message, write a log entry, and continue with the files that passed validation.
Can EDI data be loaded into a database?
Yes. After validation and transformation, the workflow can load clean data into supported databases or export it into the next required format.
Can I try the EDI workflow before buying?
Yes. Download the fully functional trial and build a small intake, validation, and export package first.
What should I agree with a trading partner first?
Agree the document type, version, required segments, test files, acknowledgement rules, and error process before scheduling production runs.
When should I not automate EDI yet?
Do not automate the process until the partner rules, expected document types, folder structure, and failure path are clear. Automation repeats rules; it does not repair missing decisions.
Stop chasing EDI files by hand. Start processing new messages on arrival.
Use directory monitoring and consistent validation before data lands in your target.
Direct link, no registration required.