VDA 4915 (ORDERS) vs VDA 4987 (DESADV): A Field-by-Field Comparison
When a German OEM or Tier-1 onboards you, you usually meet the purchase order first (VDA 4915, the EDIFACT ORDERS profile) and the despatch advice second (VDA 4987). The two messages are not independent: a correct VDA 4987 is, to a large degree, a restatement of VDA 4915 data plus shipping facts. Matching them field by field is the single most reliable way to build - and to audit - a DESADV mapping. This article walks the shared structure element by element.
The relationship in one sentence
ORDERS says “here is what I bought, under which contract, at which price”; DESADV says “here is what physically leaves my dock in fulfilment of that”. Every DESADV therefore carries a set of echoed references back to the order, and goods receipt at the plant matches them automatically.
Field-by-field comparison
| Business fact | VDA 4915 (ORDERS) | VDA 4987 (DESADV) | Matching rule |
|---|---|---|---|
| Document type | BGM+220 (order) | BGM+351 (despatch advice) | Different codes - a 220 in a DESADV header means a copy-paste bug |
| Document number | Order number in BGM-2 | Despatch note number in BGM-2 | DESADV number is yours, not the order's - never reuse the order number |
| Contract link | RFF+CT (contract), RFF+AAK (blanket order) | RFF+CT often echoed at header level | Echo the contract reference your customer expects; it drives their booking run |
| Order reference per item | Item carries LIN + internal order line | RFF+ON (order number) + RFF+OP (order line) at line level | The ON/OP pair must match the order and its line - line-level mismatches are the top booking error |
| Item identity | LIN+...<part>:IN buyer's part number | LIN with same buyer part number; PIA+1+...:SA your number | Part number must be identical; PIA is the cross-reference back to your ERP |
| Quantity semantics | QTY+21 ordered quantity | QTY+12 despatched quantity (and QTY+11 for split deliveries) | Despatched ≤ ordered, never a different qualifier set - qualifier 12 vs 21 confusion is a classic |
| Delivery date | DTM+2 requested delivery date per schedule | DTM+132 estimated arrival; DTM+11 actual despatch | Arrival in the DESADV should land on or before the ORDERS requested date |
| Parties | NAD+BY, NAD+SU, NAD+ST (ship-to), NAD+DP (deliver-to) | NAD+BY, NAD+SE, NAD+ST | Ship-to must be byte-identical; SU in the order becomes SE in the DESADV |
| Prices / amounts | MOA, PRI, TAX | None (weights instead: MEA+AAX+AAD/AAL) | Never copy MOA/PRI blocks into a DESADV - it is not an invoice |
| Packaging | PAC only if order-specific packaging agreed | Full CPS/PAC/PCI/GIN hierarchy mandatory | The order rarely constrains packing; the DESADV must fully describe reality |
Worked example: one order line becomes one despatch line
ORDERS: LIN+1++12345-A:IN'
QTY+21:500:PCE'
DTM+2:20261120:102'
RFF+ON:4500012345:1'
DESADV: RFF+ON:4500012345'
LIN+1++12345-A:IN'
QTY+12:500:PCE'
DTM+11:20261118:102'
DTM+132:20261119:102'
Reading it: you promise 500 pieces for 20 November, actually despatch them on the 18th, and they arrive the 19th. The order number travels via RFF+ON, the part number in LIN is unchanged, and the quantity qualifier changes from 21 (ordered) to 12 (despatched). Every field in the right-hand column either echoes the left or adds shipping truth.
Three reconciliation rules plants check automatically
- Part number + order line + quantity must resolve against the order. A DESADV line that does not match any open order line goes to a manual queue - and manual queues mean late booking, sometimes late payment.
- Arrival date (
DTM+132) inside the agreed delivery window. Early by more than the allowed tolerance can be as disruptive as late, because dock slots are scheduled. - Ship-to code (
NAD+ST) exactly as master data. One transposed digit routes the whole shipment to the wrong plant in the booking system, even if the truck physically drives to the right gate.
Practical auditing workflow
When a customer complains that bookings fail, pull the order (or the latest DELFOR, which repeats the same references) and the rejected DESADV side by side, and check in this order: BGM type = 351, then per line RFF+ON/OP present and matching, LIN part number identical, QTY qualifier 12 and value not exceeding the open order balance, dates in format 102, and NAD+ST identical. The VDA 4987 validator automates the structural half of that audit - envelope, required segments, date formats, control counts - so you can focus on the business matching itself.
Mapping pitfalls when echoing ORDERS into DESADV
Four mistakes account for most field mismatches in real mappings:
- Qualifier amnesia. Mappers remember “put the quantity in QTY” and forget that the qualifier is the meaning: 21 on the order side, 12 on the despatch side. A DESADV line carrying
QTY+21parses perfectly and books nothing - many gateways treat it as a missing quantity. - Line-number drift. Order lines are numbered per order; DESADV lines are numbered per despatch. Reusing the order's line counter (
LIN-1) instead of renumbering 1..n per message breaks receivers that key on the line number. Keep RFF+OP as the stable back-reference, not the LIN counter. - Ship-from confusion. ORDERS
NAD+SF(ship-from) is often a distribution centre, while your DESADVNAD+SEis the legal entity invoicing. Copying addresses instead of codes produces messages where every NAD is technically present but none match the code list. - Assuming one order per despatch. Mixed loads routinely fulfil two orders in one truck. That means two RFF+ON references at line level under one BGM - perfectly legal and very common - but mappings built on “one header order number” collapse on it. Test this case explicitly.
Why the comparison pays off
Every booking algorithm at the receiving plant is, in effect, the comparison table above executed automatically: order reference, part, quantity, date, ship-to. If your DESADV generation was built by translating the comparison row by row - rather than by copying a sample file until it looked similar - then the customer’s automated checks and your mapping are literally the same rules, and test phases get boring. Boring is what you want in EDI.