SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Archived, and was part of release 201101 : Identifier : M0121 - Contrat, mise à jour garanties vie et placements - (Échéance contrat ou investissement - Relevé de compte au 31.12 ou en date anniversaire) |
Sender : Insurer
Receiver : Broker
Status : 3 - Version : 2
|
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 UN/EDIFACT representation |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
|||||||
| 10 |
Message issuing date and time
|
No
|
-
|
-
|
Mand.
|
XEH+01+2+0121+++domain++++yyyymmddhhmm+xx' (=X916 and =X918) (domain is mandatory)
|
ExchangeUnitIssueDateTime
|
||
| 20 |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
XEH+01+2+0121+++domain++++yyyymmddhhmm+xx:::M0121' (=X943)
|
ExchangeUnitBusinessContentDescription
|
||
| 30 | u |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
XEH+01+2+0121+++domain++++yyyymmddhhmm+xx:::M0121:2' (=X944)
|
ExchangeUnitBusinessContentDescriptionVersion
|
|
| 40 |
Contrat
|
No
|
-
|
-
|
Mand.
|
XEH+01+2
|
|||
| 50 |
Mouvement suite à péréquation
|
Yes
|
1
|
Mand.
|
GIS+1025+x--x
|
CurrentAccountLineFollowingRedistributionProcesscode
|
|||
| 60 |
Type de police
|
Yes
|
5
|
Option.
|
IPD+A502+x--x
|
PolicyProductcode
|
|||
| 70 |
Produit
|
No
|
-
|
-
|
Option.
|
IPD+A532+code::002:label'
|
ProductNameProductcode ProductDetail ProductIdentifier CodeListResponsibleAgencyCoded ProductName
|
||
| 80 |
Date d'effet
|
No
|
-
|
-
|
Mand.
|
DTM+008:x--x:001
|
InceptionDate
|
||
| 90 |
Numéro de police
|
No
|
-
|
-
|
Mand.
|
RFF+001:x--x
|
PolicyReference
|
||
| 100 |
Numéro d'avenant
|
No
|
-
|
-
|
Mand.
|
RFF+002:x--x
|
EndorsementReference ReferenceDetail ReferenceContent
|
||
| 110 |
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:x--x
|
MessageGuidReference
|
|
| 120 |
Référence des paiements
|
No
|
-
|
-
|
Option.
|
RFF+068:x--x
|
PaymentReference
|
||
| 130 |
Etat de la police
|
Yes
|
2
|
Mand.
|
ATT+A003+x--x
|
ContractStatusCode
|
|||
| 140 |
Commission d'acquisition - total
|
No
|
-
|
-
|
Option.
|
MOA+030:x--x:EUR:2:(status)
|
AcquisitionCommissionTotalAmount
|
||
| 150 |
Commission d'acquisition - supplémentaire
|
No
|
-
|
-
|
Option.
|
MOA+090:x--x:EUR:2:(status)
|
SupplementaryAcquisitionCommissionAmount
|
||
| 160 |
Valeur de rachat du contrat à la fin de l'année précédente
|
No
|
-
|
-
|
Option.
|
MOA+089:x--x:EUR:2:(status)
|
SurrenderValueOfContractAtEndOfLastYearAmount
|
||
| 170 |
Nombre de documents annexes
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
QTY+134
|
DocumentsAttachedQuantity
|
|
| 180 |
Assureur
|
No
|
-
|
-
|
Mand.
|
PTY+006
|
PartyInsurer
|
||
| 190 |
Assureur - Numéro CBFA
|
No
|
-
|
-
|
Mand.
|
PTY+006+x--x (X044-1)
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 200 |
Assureur - Type d'assureur en coassurance
|
Yes
|
1
|
Option.
|
PTY+006 - ATT+A020+x--x
|
InsurerInCaseOfCoInsuranceCode
|
|||
| 210 |
Intermédiaire
|
No
|
-
|
-
|
Mand.
|
PTY+002
|
PartyIntermediary
|
||
| 220 |
Intermédiaire - Numéro CBFA
|
No
|
-
|
-
|
Option.
|
PTY+002+x--x (X044-1)
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 230 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
PTY+002++x--x (X044-2)
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 240 |
Intermédiaire - Référence police producteur
|
No
|
-
|
-
|
Mand.
|
PTY+002 - RFF+003:x--x
|
BrokerPolicyReference
|
||
| 250 | u |
Preneur d'assurance
|
No
|
-
|
-
|
Mand.
|
PTY+003 (-GRP/PM/PP all rel. 201101)
|
PartyMainPolicyHolder
|
|
| 260 | u |
Objet de risque
|
No
|
-
|
-
|
Mand.
|
ROD+xxx
|
ObjectInsured...
|
|
(*) 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.
(***) Remark: In 2020 things evolved into another "approach A" and then yet another "approach B" - It is that "appoach B" which you see here - That "approach B" is the basis of the EDIMERX development.
In TB2-XML "Namespace 2018" (as well as in eEG7-UN/CEFACT), things were/are structurally different.
EDIMERX is supporting the transition from Edifact (messages) to JSON (API's).
The so-called "Business API's" are what comes next / after such transition-phase - and there things will be structurally differrent again.