> Syntax independent - MCIs - Messages > Details > Representations

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Identifier : EROD090 - Echange contextuel, données animal - (Données animal) - Approved , and is part of release 201401
- ( TB2-UN/Edifact MIG : Fr / Nl ) - (UN/Edifact & XML/JSON : added info )
Sender : Any
Receiver : Any
Status : 2 - Version : 1
Seq. n° n
u
d
(*)
Data element
Code list
Usage
Mandatory
Conditional
Optional (**)
Condition(s)
TB2 UN/EDIFACT representation
Indicator
Identifier
Version
10  
Contrat
No
-
-
Mand.
 
XEH+01+2 
20  
Riskobject, type
No
-
-
Mand.
 
ROD+090 
30  
Nom
No
-
-
Option.
 
ROD+090 - NME 
40  
Date d'achat/d'acquisition
No
-
-
Option.
 
ROD+090 - DTM+061 
50  
Numéro matricule
No
-
-
Option.
 
ROD+090 - RFF+061 
60  
Type d'animal
Yes
1
Option.
 
ROD+090 - ATT+4132+x--x 
70  
Sexe
Yes
2
Option.
 
ROD+090 - ATT+A124+x--x 
80  
Nombre d'animaux
No
-
-
Option.
 
ROD+090 - QTY+035 
90  
Description race/elevage
No
-
-
Option.
 
ROD+090 - FTX+019+x--x:x--x:x--x:x--x:x--x 

(*) n u d : new / updated / deleted since previous version.

(**) Usage: The indications Mandatory / Conditional / Optional are to be understood in respect of the actual level of the Data element:
  example given; some party data-set as a whole can be optional, while, if present, the party's name within that party data-set can be mandatory.

Remark: in UN/Edifact, "Mandatory / Conditional" are notions used within the standard. And within edi-guides (a refinement of a standard) the "Conditional" can become "Required / Optional / Dependent / Advised / Not used". Ideally we should implement the same ideas.