> Syntax independent - MCIs - Messages > Details

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Identifier : EPTY002 - Echange contextuel, données producteur - (Numéro compte producteur)
- Approved , and is part of release 201901 - ( TB2-UN/Edifact MIG : Fr / Nl ) - ( TB2-XML : added info )
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  
Intermédiaire - Intermédiaire
No
-
-
Mand.
 
PTY+002 
30 u 
Intermédiaire - Numéro FSMA
No
-
-
Option.
Since 15/7/2017 the FSMA no longer attributes such number 
PTY+002+x--x:006 
40 u 
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie (numéro de compte producteur)
No
-
-
Mand.
 
PTY+002++x--x:002 
41 n 
Intermédiaire - Numéro d'entreprise
No
-
-
Option.
Added as FSMA-broker-id abandoned 15/7/2017 
PTY+002 - RFF+075:x--x 
42 n 
Intermédiaire - Numéro unité d'exploitation
No
-
-
Option.
Added as FSMA-broker-id abandoned 15/7/2017 
PTY+002 - RFF+076:x--x 
43 n 
Intermédiaire - LEI
No
-
-
Option.
Added as FSMA-broker-id abandoned 15/7/2017 
PTY+002 - RFF+107:x--x 
50  
Contrat - indication fin dossier
No
-
-
Mand.
 
XEH+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.