> Syntax independent - MCIs - Messages > Details
SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
|
> Syntax independent - MCIs - Messages > Details
|
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : M0104RES - Contrat, avenant - (Avenant de résiliation) - Approved , and is part of release 201001 - ( TB2-UN/Edifact MIG : Fr / Nl ) - ( TB2-XML : added info ) ( Additional information is present below the details-table ) |
Version : 3 Status : 2 |
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2-UN/EDIFACT representation (including comments) |
||
Indicator |
Identifier |
Version |
||||||
| 10 | n |
Message issuing date and time
|
No
|
-
|
-
|
Mand.
|
XEH+01+2+0104+++domain ++++yyyymmddhhmm +E1' (=X916 and =X918) (domain is mandatory)
|
|
| 20 | n |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
XEH+01+2+0104+++domain ++++yyyymmddhhmm +E1:::M0104RES' (=X943)
|
|
| 30 | n |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
XEH+01+2+0104+++domain ++++yyyymmddhhmm +E1:::M0104RES:3' (=X944)
|
|
| 40 |
Contrat
|
No
|
-
|
-
|
Option.
|
XEH+01+2
|
||
| 50 | u |
Nature du document
|
Yes
|
3
|
Mand.
|
Mandatory and with value 5
|
GIS+EW05
|
|
| 60 |
Date de résiliation
|
No
|
-
|
-
|
Mand.
|
DTM+019
|
||
| 70 |
Numéro de police
|
No
|
-
|
-
|
Mand.
|
RFF+001
|
||
| 80 |
Numéro d'avenant
|
No
|
-
|
-
|
Mand.
|
RFF+002
|
||
| 90 | n |
GUID (Globally Unique IDentifier) du message, sera référencé par le(s) document(s) annexe(s)
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
RFF+084
|
| 100 |
Motif de résiliation
|
Yes
|
5
|
Option.
|
ATT+A705
|
|||
| 110 |
Origine de la résiliation
|
Yes
|
1
|
Option.
|
ATT+A314
|
|||
| 120 |
Etat de l'acceptation de la nouvelle affaire ou du projet
|
Yes
|
2
|
Option.
|
ATT+A055
|
|||
| 130 | n |
Nombre de documents annexes
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
QTY+134
|
| 140 | u |
Assureur
|
No
|
-
|
-
|
Mand.
|
PTY+006
|
|
| 150 |
Assureur - Numéro CBFA
|
No
|
-
|
-
|
Mand.
|
PTY+006+x--x (X044-1)
|
||
| 160 | u |
Intermédiaire
|
No
|
-
|
-
|
Mand.
|
PTY+002
|
|
| 170 |
Intermédiaire - Numéro CBFA
|
No
|
-
|
-
|
Option.
|
PTY+002+x--x (X044-1)
|
||
| 180 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
PTY+002++x--x (X044-2)
|
||
| 190 | u |
Intermédiaire - Référence producteur
|
No
|
-
|
-
|
Mand.
|
PTY+002 - RFF+003
|
|
(*) n u d : new / updated / deleted since previous version.
(*bis) u : updated : this can be a codelist-version incrementing.
Note that in many, not to say all such cases, the user-community does not await such next release to implement/activate such new codelist-values.
The reasoning is that such added value does not affect the current data-structures and hence is considered easely implementable.
Such reasoning tends to forget how given new codelist-values might not simply affect the data, but also affect the process, which might be more of a problem...
(**) 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.