QUALIFIER
The short code that says "this value plays such-and-such role": without it, a number or a date would be semantically ambiguous.
Definition
A qualifier is a short alphanumeric code — typically 2 to
4 characters — drawn from a reference code list, that pins down
the role, type or context of a value inside an EDI segment. Without a
qualifier, several segments would be semantically ambiguous. A
20260513 date in a DTM means nothing on its own: is it the
order date, the requested delivery date, the payment due date? Qualifier
137 states "document date", qualifier 2 states
"delivery date/time, requested", and so on. The UN/EDIFACT code lists are
published in the UNCL sub-directory of each directive (D.96A:
uncl0035.htm, uncl1001.htm, uncl2005.htm…).
Origin
The qualifier mechanism is consubstantial with EDI. ANSI ASC X12 uses it
heavily from 1979 onwards: qualifier elements appear in nearly
every segment, for instance BEG02 ("Purchase Order Type Code")
in the 850, or DTM01 ("Date/Time Qualifier"). UN/EDIFACT
embraced the same logic by formalising its UNCL code lists inside
ISO 9735.
The principle reaches into PEPPOL and UBL (Schematron-validated code lists)
and even cXML (type attributes).
Example in context
Four dates in the same ORDERS message, separated only by their qualifier:
Without the qualifier 137 / 2 / 35 / 44 (UNCL 2005), there is
no way to tell which date is the due date and which is the order date. The
102 qualifier in third position specifies the format
(CCYYMMDD).
Related terms
- Segment — the structural unit where qualifiers apply.
- ICD — a specific qualifier scheme (ISO 6523) for identification authorities.
- NAD — a segment whose first element is always a qualifier (3035).
- BGM — a segment that carries several qualifiers (1001, 1225, 4343).
- EDI — the global context of the mechanism.