RFF

Reference. The universal EDIFACT segment for pointing — "this relates to that order, that contract, that despatch note."

Definition

The RFF segment is officially defined in UN/EDIFACT D.96A "to specify a reference". Its structure is minimal — a single mandatory composite:

1. 010 — C506 (REFERENCE), mandatory:
2. 1153 Reference qualifier (an..3, M) — UNCL 1153 qualifier stating the reference type: ON order number, CT contract, AAJ despatch note, VA VAT number, etc.
3. 1154 Reference number (an..35, C) — the actual reference value.
4. 1156 Line number (an..6, C) — line number if the reference targets a specific line of another message.
5. 4000 Reference version number (an..35, C) — version, revision.

Origin

RFF is one of the most frequently reused service segments in D.96A. It appears as early as EDIFACT version 1 (1987) in a similar form. The GS1 EANCOM subset mandates an RFF in most business messages (ORDERS, DESADV, INVOIC) to explicitly link a transaction to its context. The ediverse.io-archived specification follows trsdrff.htm verbatim.

Example in context

In a DESADV, we link the shipment back to the original order:

Reads as: "this shipment relates to order PO-2026-00042 per the ON (Order Number) qualifier." Several RFFs may coexist: a CT for the framework contract, a DL for the despatch number.

Related terms

• Segment — the general concept.
• Qualifier — code 1153 is a textbook qualifier.
• DTM — companion segment often placed after RFF.
• ORDERS — message where RFF binds to a contract.