In this article
Fixed-width file to EDI mapping lets you turn an existing manufacturing system export into a trading partner's required EDI document without rebuilding the system that produces the file. A map reads values from defined character positions, applies business rules and translates the result into the appropriate transaction. For inbound EDI, the same approach can produce a file your legacy system can import.
The important work is defining the source layout and checking it against the trading partner's published EDI implementation guide. BOLD VAN uses BOLD Integration to map EDI into and out of ERP, WMS and other systems, allowing you to keep a functioning legacy export while managing partner-specific translation separately.
What fixed-width mapping means
In a fixed-width file, each field has an assigned starting position and length. A record might reserve one range for a document reference, another for an item identifier and another for quantity. Spaces may be meaningful padding. Unlike a comma-separated file, the boundaries are determined by position rather than punctuation.
Many exports also have different record types. A header can describe the document, line records can carry individual items and a trailer can carry control information. The actual layout varies by application. Before you translate anything, you need the source specification, the record sequence and examples covering the situations your business handles.
Mapping then connects those source records to an EDI transaction. An 810 is an invoice, an 855 is a purchase order acknowledgment and an 856 is a ship notice or manifest. An inbound 850 purchase order may need the reverse path, from EDI into the legacy system's import file. Which transactions, values and rules apply depends on the EDI version and the partner's published implementation guide.
Check the layout before you check the EDI. A shifted character position can produce a plausible-looking but incorrect value. Validate record lengths and source meanings before testing partner compliance.
How to build the map
Document the export as it actually runs
Ask the system owner for the current layout, then compare it with representative files. Record each field's position, length, type, padding rule and meaning. Identify how the file marks a new document, associates lines with a header and indicates the end of a document. If several plants or business units share an export, check whether they produce the same layout.
Define translation and ownership
Decide which values pass through unchanged and which need a lookup or conversion. Item identifiers, units of measure, dates and customer references deserve particular attention. If a required EDI value is absent from the file, assign a business owner to decide whether the source system should produce it or an approved mapping rule can supply it. Avoid guessing from a sample.
Test the complete document path
Test parsing, translation, transmission and the receiving workflow as separate checkpoints. Compare source and EDI document counts, references, line quantities and totals where applicable. Include error cases so you know what happens when a file is short, a code cannot be translated or a document is submitted twice. Partner testing must follow the partner's published guide.
| Checkpoint | What to confirm | Failure to catch |
|---|---|---|
| Source layout | Record types, positions and lengths match the export. | A shifted field changes the meaning of later values. |
| Business rules | Identifiers, units and optional values have agreed handling. | A valid file carries an unusable business value. |
| Document structure | Headers, lines and totals remain associated correctly. | Lines attach to the wrong document. |
| Partner test | The output follows the applicable guide and version. | Translation succeeds but partner validation fails. |
| Recovery | The team can identify the failed document and its disposition. | A retry creates a duplicate business transaction. |
Common failure points in manufacturing exports
- Leading zeros disappear. Treat item, account and location identifiers as text unless the source specification says otherwise.
- Blank fields are misread. An optional blank may be acceptable in the source but may require a business decision before an EDI document can be sent.
- Quantities lose context. Confirm the unit alongside the number, especially when the legacy system stores several units for the same item.
- Layouts change quietly. A new field or revised export can shift positions. Version the source layout and retest affected maps.
- Acknowledgments are overinterpreted. A 997 functional acknowledgment tells the sender whether a document passed the receiver's syntax check. It can report acceptance or rejection, and it does not mean the order or its content was accepted.
For invoices and shipment notices, a structurally valid document can still contain a wrong item reference, amount or shipment detail. Check business outcomes after syntax testing. Accurate mapping and review help reduce the risk of chargebacks, an industry problem when trading partner requirements are missed.
Best practices for a controlled rollout
Start with one document flow and a clear owner for source data, mapping decisions and partner testing. Keep production-like examples that cover multiple lines, optional data, corrections and invalid inputs. Reconcile output to the original file before switching a production route, and agree on how your team will handle a failed or repeated document.
When a partner changes its requirements, review that partner's current implementation guide and test the affected transaction again. With BOLD VAN, we update the map when a trading partner changes its requirements, and minor changes are typically handled at no cost. New maps are typically ready to test in about two days. Your testing schedule should also account for source-system review and any partner certification steps.
Modernize without replacing the ERP
A managed cloud EDI mapping layer can leave the existing export in place while moving partner translation and map maintenance out of an on-premise process. That reduces dependence on one employee's knowledge and gives you a clearer business continuity plan. BOLD VAN maps data to and from ERP systems including SAP, Oracle ERP, Infor CloudSuite and others, as well as WMS, TMS and e-commerce platforms. Where a platform uses an API instead of EDI, the integration can map data in either direction. Check the platform's own documentation for version-specific integration details.
For day-to-day review, every document is tracked in the portal, where customers can search, requeue and report, with notifications when something needs their attention. If your manufacturing system already exports dependable files, the practical next step is to document one layout and test it against one partner guide. Our integration and mapping service can help you plan that path.
Frequently asked questions
Can a legacy ERP send EDI using fixed-width exports?
Yes. A mapping layer can read the ERP's fixed-width export, validate its values and translate it into the EDI transaction required by a trading partner. Check the partner's published EDI implementation guide before testing.
What information do you need to map a fixed-width file?
You need the current record layout, field positions and lengths, record relationships, representative files and the trading partner's published EDI implementation guide. Business owners should confirm the meaning of identifiers, quantities and codes.
Does an accepted 997 mean the trading partner accepted the order?
No. A 997 functional acknowledgment reports whether a document passed the receiver's syntax check and can indicate acceptance or rejection. It does not confirm that the order or its business content was accepted.
How do you test fixed-width file to EDI mapping?
Test normal and invalid source files, verify field positions and business rules, reconcile document counts and values, then test the EDI output against the trading partner's published implementation guide. Include recovery and duplicate-handling scenarios.
