SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Archived, and was part of release 201301 : Identifier : M0126 - Contrat, message production origine assureur hors contrat - (MPB : Message Production, mais hors contrat / Productie Bericht, maar los van bestaand contract) - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Insurer
Receiver : Broker
Status : 3 - Version : 2
|
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
||||||
| 10 |
Message issuing date and time
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitIssueDateTime
|
||
| 20 |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescription
|
||
| 30 | u |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescriptionVersion
|
|
| 40 |
Contrat
|
No
|
-
|
-
|
Mand.
|
|||
| 50 |
Type de police
|
Yes
|
7
|
Option.
|
PolicyProductcode
|
|||
| 60 |
Produit
|
No
|
-
|
-
|
Option.
|
ProductNameProductcode ProductDetail ProductIdentifier CodeListResponsibleAgencyCoded ProductName
|
||
| 70 |
Date d'effet
|
No
|
-
|
-
|
Mand.
|
InceptionDate
|
||
| 80 |
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.
|
MessageGuidReference
|
|
| 90 |
Référence des paiements
|
No
|
-
|
-
|
Option.
|
PaymentReference
|
||
| 100 |
Nombre de documents annexes
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
DocumentsAttachedQuantity
|
|
| 110 |
Acte de gestion
|
No
|
-
|
-
|
Mand.
|
ActionRating
|
||
| 120 | u |
Acte de gestion - Code MPB origine assureur (texte libre)
|
Yes
|
3
|
Cond.
|
Mandatory when text is present
|
CodeMpbOriginInsuranceCompanyCode
|
|
| 130 |
Acte de gestion - Texte de communication
|
No
|
-
|
-
|
Option.
|
CommunicationText
|
||
| 140 |
Assureur
|
No
|
-
|
-
|
Mand.
|
PartyInsurer
|
||
| 150 |
Assureur - Numéro CBFA
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 160 |
Assureur - Type d'assureur en coassurance
|
Yes
|
1
|
Option.
|
InsurerInCaseOfCoInsuranceCode
|
|||
| 170 |
Assureur - Correspondant - Correspondant, gestionnaire
|
No
|
-
|
-
|
Option.
|
RelatedCorrespondentOrManager
|
||
| 180 |
Assureur - Correspondant - Nom officiel
|
No
|
-
|
-
|
Mand.
|
OfficialName
|
||
| 190 |
Assureur - Correspondant - Numéro de téléphone bureau
|
No
|
-
|
-
|
Option.
|
OfficeTelephoneCommID
|
||
| 200 |
Assureur - Correspondant - Numéro de fax
|
No
|
-
|
-
|
Option.
|
FaxCommID
|
||
| 210 |
Assureur - Correspondant - e-Mail
|
No
|
-
|
-
|
Mand.
|
EmailAddressCommID
|
||
| 220 |
Intermédiaire
|
No
|
-
|
-
|
Mand.
|
PartyIntermediary
|
||
| 230 |
Intermédiaire - Numéro CBFA
|
No
|
-
|
-
|
Option.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 240 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 250 |
Intermédiaire - Numéro du dossier
|
No
|
-
|
-
|
Option.
|
FileReference
|
||
| 260 |
Intermédiaire - Correspondant
|
No
|
-
|
-
|
Option.
|
RelatedCorrespondentOrManager
|
||
| 270 |
Intermédiaire - Correspondant - Nom officiel
|
No
|
-
|
-
|
Mand.
|
OfficialName
|
||
| 280 |
Intermédiaire - Correspondant - Numéro de téléphone bureau
|
No
|
-
|
-
|
Option.
|
OfficeTelephoneCommID
|
||
| 290 |
Intermédiaire - Correspondant - Numéro de fax
|
No
|
-
|
-
|
Option.
|
FaxCommID
|
||
| 300 |
Intermédiaire - Correspondant - e-Mail
|
No
|
-
|
-
|
Option.
|
EmailAddressCommID
|
||
| 310 | u |
Preneur d'assurance
|
No
|
-
|
-
|
Option.
|
one of PTY003GRPv5- PTY003PMv5- PTY003PPv6
|
PartyMainPolicyHolder
|
| 320 |
Objet de risque
|
No
|
-
|
-
|
Option.
|
0..n presencies
|
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.