> Syntax independent - MCIs - Messages > Details

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Identifier : ECNTRCT - Echange contextuel, données contrat - (Données contrat, pour avenant ou pour consultation)
- Approved , and is part of release 201801 - ( TB2-UN/Edifact MIG : Fr / Nl ) - ( TB2-XML : added info )
( Additional information is present below the details-table )
Version : 2
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  
Contrat
No
-
-
Mand.
 
XEH+01+2 
20 u 
Numéro de police
No
-
-
Cond.
At least the one or the other 
RFF+001+x--x 
30 n 
Numéro de tarification à la compagnie
No
-
-
Cond.
At least the one or the other 
RFF+004+x--x 
40 u 
Intermédiaire
No
-
-
Mand.
 
PTY+002 
50 u 
Intermédiaire - Numéro FSMA
No
-
-
Option.
 
PTY+002+x--x:006 
60 u 
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie (numéro de compte producteur)
No
-
-
Mand.
 
PTY+002++x--x:002 
70  
Contrat - indication fin dossier
No
-
-
Mand.
 
XET+01 

(*) 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.



Added information :

Voir dans les BBP le point 1. ( Suivre >Models >Broker Business Processes >Next->... jusqu'à ce point 1)
/ Zie in de BBP het punt 1. ( Volg >Models >Broker Business Processes >Next->... tot aan dat punt 1)
( http://www.telebib2.org/ProcessBB01.htm )