VDA EDI Tools

VDA 4905 to VDA 4984 Migration Guide: Field Differences, Parallel-Run Errors, Checklist

VDA EDI Tools Blog · 2026-11-14 · Migration

The migration is no longer optional for an increasing share of the German automotive supply chain. Training providers such as GEFEG now teach VDA 4984 T2 Global DELFOR explicitly as the message that replaces VDA 4905 and 4915, and OEMs publish their own implementation requirements - for example the VDA 4984 Lieferabruf (Global DELFOR) - Anwendungshandbuch / Application Guideline for VW Group, whose current English edition (VW 1.9) specifies segment usage down to the element level. If your plant still emits fixed-length 4905/4913 records, this guide is the migration path - with the field-level differences and the errors you will actually meet during the parallel phase.

Fixed-length vs EDIFACT: what actually changes

VDA 4905 thinks in records and offsets: a record type identifies the line, and every value occupies fixed character positions. VDA 4984 thinks in tagged segments on an EDIFACT syntax (UN/EDIFACT D.04A or newer, per the partner's guideline):

AspectVDA 4905 (classic)VDA 4984 (Global DELFOR)
Structure unitFixed-length records (e.g. 512 chars), type-codedVariable-length segments separated by UNA-declared delimiters
Document codeRecord type positionBGM+241 (forecast + firm), 236 (forecast only), 242 (JIT)
Item identificationMaterial number at fixed offsetLIN loop with buyer/seller article numbers (PIA)
Schedule logicSeparate record types per quantity typeSCC status 1/2/3/4 + QTY + DTM triplets
DatesDDMMYY at fixed positionsDTM with format code 102 (CCYYMMDD) or 203 (CCYYMMDDHHMM)
PartiesFixed supplier/customer number fieldsNAD+SE/BY/ST/SU with GLN or assigned codes
IntegrityRecord counts, sequence checksUNT segment count, UNZ message count, UNB/UNZ control reference equality
NumbersPadded, implied decimalsPlain numerics: QTY+113:1250:PCE - no thousand separators

Common errors during the parallel transition - and how to troubleshoot them

  1. BGM document code copied from the wrong template. A 4905-era generator retrofitted for 4984 often emits BGM+351 (the DESADV code) in a forecast file. Symptom: OEM mapping rejects at first segment. Fix: generator-side constant review; the VDA 4984 validator flags wrong BGM codes with the exact segment position.
  2. Date format leaks. DTM+2:13.11.2026:102 - a German dotted date pasted into a code-102 field. The old fixed-length format encouraged this shape; EDIFACT rejects it. Fix: format dates as 8/12 raw digits at serialization time, never at display time.
  3. Separator collision from hardcoded delimiters. The UNA header declares UNA:+.? ' for the whole file, but a part description containing + corrupts every following segment unless the release character is applied. Fix: always emit UNA-aware escaping; validate inbound files after re-reading UNA, which the validators do automatically.
  4. Stale control counts after hand-edited test files. Fix a quantity in a test file, forget to recompute UNT/UNZ, and the OEM parser rejects at the envelope before any content check. This is the single most common self-inflicted reject in the parallel phase.
  5. Quantity encoding drift. QTY+113:1.250:PCE parses as 1.25 pieces - a short-shipment bug. Pin the plain-numeric rule in your mapping specification per field; do not assume.
  6. SCC flattening. The 4913 call-off logic often gets flattened to SCC+4 (forecast) during migration, destroying commitment strength. The OEM's planning department notices when firm orders disappear from its MRP.

Migration checklist

  1. Pin the versions. Record per partner: VDA 4984 recommendation status, EDIFACT directory (D.04A / D.07A / D.20B), guideline name and version - e.g. the VW Group VDA 4984 Lieferabruf application manual (VW 1.9, English edition) where applicable.
  2. Build the field mapping. Convert the 4905 record layout into a 4984 segment specification; agree element-level defaults (date codes, SCC semantics, number formats) with the OEM's EDI contact before coding.
  3. Generate and validate test files. Paste every outbound file into the VDA 4984 validator (and DESADV into the VDA 4987 validator) before sending; both run locally, so real part numbers stay in your browser.
  4. Dual-run one full week. Keep 4905 alive while 4984 runs in parallel; reconcile quantities per material number, not per file. Differences reveal mapping bugs structural validation cannot see.
  5. Test unhappy paths. Truncated file (missing UNZ), hand-edited quantity, Umlauts in UTF-8 where the partner expects ISO 8859-1, empty file at end-of-day. Document behavior before the OEM's test team finds it for you.
  6. OEM test cycle and sign-off. Complete the partner's test cases, collect confirmations, then decommission the legacy interface with a written cutover date.

Related reading

Try it: Validate your migrated DELFOR before the OEM sees it - segment-level errors with positions, entirely local. Open the VDA 4984 validator →

← All articles