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 - ( UN/Edifact MIG : Fr / Nl )
Version : 1
Status : 2
n
u
d
(*)
Data element
Code list
Usage
Mandatory
Conditional
Optional (**)
Condition(s)
XML-tag
UN/EDIFACT representation (including comments)
Indicator
Identifier
Version
 
Contrat
No
-
-
Mand.
 
Message MessageAboutContract 
XEH+01+2 
 
Riskobject, type
No
-
-
Mand.
 
Animal 
ROD+090 
 
Nom
No
-
-
Option.
 
Animal AnimalNameText 
ROD+090 - NME 
 
Date d'achat/d'acquisition
No
-
-
Option.
 
Animal AnimalAcquisitionDate 
ROD+090 - DTM+061 
 
Numéro matricule
No
-
-
Option.
 
Animal AnimalRegistrationIdentifier 
ROD+090 - RFF+061 
 
Type d'animal
Yes
4132
1
Option.
 
Animal AnimalTypeCode 
ROD+090 - ATT+4132+x--x 
 
Sexe
Yes
A124
2
Option.
 
PhysicalPerson GenderCode 
ROD+090 - ATT+A124+x--x 
 
Nombre d'animaux
No
-
-
Option.
 
Animal AnimalsCount 
ROD+090 - QTY+035 
 
Description race/elevage
No
-
-
Option.
 
Animal BreedText 
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.