972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Master data

CLASET Classification information set

The UN/EDIFACT message used to exchange classifications, meaning tree structures or code lists and the links between them.

Sent by
Classification owner or data provider
Received by
Trading partner or data user
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT CLASET message?

CLASET is the UN/EDIFACT classification information set message. The directory describes it as designed to exchange tree structures or code lists and the links between them, referred to as classifications. It covers general information about a classification and all or part of its content or structure.

Product classifications, such as category trees used in catalogues, need to be shared so that both partners place items in the same categories. CLASET lets a classification owner distribute a new version, or changes, in a form systems can load.

How the EDIFACT CLASET message worksDiagram of the UN/EDIFACT CLASET Classification information set message. Classification owner or data provider sends it to trading partner or data user. It usually starts the exchange. It is usually followed by PRODAT. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message). 3 conditional segment groups are listed by their trigger segment.How the EDIFACT CLASET message worksClassification information set: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeCLASETSENDERClassification owneror data providerRECEIVERTrading partner or datauserCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYPRODATProduct data2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage CLASETUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPS+ 3 conditional groups, starting with:RFFPNAVLIBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for CLASET. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT CLASET message worksDiagram of the UN/EDIFACT CLASET Classification information set message. Classification owner or data provider sends it to trading partner or data user. It usually starts the exchange. It is usually followed by PRODAT. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message). 3 conditional segment groups are listed by their trigger segment.How the EDIFACT CLASETmessage worksClassification information set: who sends it,where it fits and what the directory marksmandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeCLASETSENDERClassificationowner or dataproviderRECEIVERTrading partneror data userCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYPRODATProduct data2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message CLASET (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPS+ 3 conditional groups, starting with:RFFPNAVLIBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for CLASET.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends CLASET, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around CLASET and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Distributing a product category tree
  • Sending updates to a code list
  • Mapping between two classification schemes

Where it fits in the message flow

This message CLASET Classification information set
Usually followed by PRODAT Product data

Structure

Mandatory segments in CLASET (directory D.21A)

In UN/EDIFACT directory D.21A, the CLASET message has 51 segment positions arranged in 20 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • UNT

Practical example

CLASET in practice

A wholesaler reorganizes its online catalogue categories. It sends its suppliers a CLASET with the new category tree and the codes of each node. Suppliers update their systems so the product data they send with PRODAT is classified in the wholesaler's new categories.

Implementation

Implementation considerations for CLASET

  • Version classifications and state their validity dates.
  • Send changes as well as full sets, as agreed.
  • Keep mappings between old and new codes during transitions.
  • Agree who owns and maintains the classification.

How ECOM helps

Automate CLASET with ECOM

Industry

Wholesale Distribution

Customer orders, supplier purchasing, catalogs and drop-ship for distributors.

Solution

B2B Integration

Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.

Industry

Retail

Retail and eCommerce EDI for suppliers and retailers, from purchase order to payment, with compliance built in.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related master data messages

All 11 master data messages

Need help with CLASET?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us