VDA 4984 Validation: Common DELFOR Errors and Fixes
DELFOR files fail for different reasons than despatch advices. These are the issues our validator reports most often on VDA 4984 files.
1. Unexpected BGM document type
VDA 4984 commonly uses 241 (delivery schedule), 236 (forecast) or 242 (JIT). A header copied from another message family - or a numeric typo - lands here first.
2. DESADV date qualifiers in a DELFOR
Schedule dates in DELFOR use their own qualifier set (2, 10, 64, 137, 158, 159 in common usage). Seeing 11 or 132 means someone mapped a despatch-advice field into the forecast.
3. Malformed date values
Same rule as everywhere in EDIFACT: format 102 = CCYYMMDD, 203 = CCYYMMDDHHMM, digits only. German-locale exports with dots (29.09.2026) break this instantly.
4. UNS separator code wrong
The UNS segment separates detail and summary sections and should carry D (or S per guideline). An empty or invented code here confuses strict parsers.
5. Missing schedule document number
BGM-2 (DE 1004) identifies the delivery schedule. Without it the receiver cannot match the file to a planning run or detect duplicates.
6. Unusual party roles
DELFOR headers commonly use BY/SE/SF/ST/IV/CN. A missing ship-to, or a role code from another message family, usually indicates a mapping table that was never updated for this customer.
7. Non-numeric quantities
Schedule quantities in QTY must be numeric. Decimal commas from German number formats are the classic failure.
8. Control reference and count mismatches
UNZ-1 must equal the real message count, UNZ-2 must match UNB-5, and UNT-1 must match the actual segment count. Concatenating files by hand breaks all three at once.
Pre-flight check
Forecast files are generated far more often than they are inspected. Running each new OEM mapping through the VDA 4984 validator once - and re-checking after every ERP change - catches all of the above before the customer's gateway does.