SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : M0104SUS - Contrat, avenant - (Avenant de suspension)
- Approved
, and is part of release 201901 - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Insurer
Receiver : Broker
Status : 2 - Version : 4
|
| 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 |
Nature du document
|
Yes
|
6
|
Mand.
|
Mandatory and with value 7
|
MessageNatureProcesscode
|
||
| 60 |
Date de suspension
|
No
|
-
|
-
|
Mand.
|
SuspensionDate
|
||
| 70 |
Numéro de police
|
No
|
-
|
-
|
Mand.
|
PolicyReference
|
||
| 80 |
Numéro d'avenant
|
No
|
-
|
-
|
Mand.
|
EndorsementReference
|
||
| 90 |
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
|
|
| 100 |
MOTIF de suspension
|
Yes
|
3
|
Option.
|
SuspensionMotiveCode
|
|||
| 110 |
Origine de la résiliation
|
Yes
|
2
|
Option.
|
OriginForCancellationCode
|
|||
| 120 |
Etat de l'acceptation de la nouvelle affaire ou du projet
|
Yes
|
2
|
Option.
|
StateOfAcceptanceCode
|
|||
| 130 |
Nombre de documents annexes
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
DocumentsAttachedQuantity
|
|
| 140 |
Assureur
|
No
|
-
|
-
|
Mand.
|
PartyInsurer
|
||
| 150 |
Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 151 | n |
Assureur - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
CompanyNumberReference
|
|
| 152 | n |
Assureur - Numéro d'unité d'établissement
|
No
|
-
|
-
|
Option.
|
EstablishmentUnitNumberReference
|
|
| 153 | n |
Assureur - LEI
|
No
|
-
|
-
|
Option.
|
LegalEntityIdentifierReference
|
|
| 160 |
Intermédiaire
|
No
|
-
|
-
|
Mand.
|
PartyIntermediary
|
||
| 170 |
Intermédiaire - Numéro FSMA
|
No
|
-
|
-
|
Option.
|
Since 15/7/2017 the FSMA no longer attributes such number
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
|
| 180 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 181 | n |
Intermédiaire - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
Added as FSMA-broker-id abandoned 15/7/2017
|
CompanyNumberReference
|
| 182 | n |
Intermédiaire - Numéro unité d'établissement
|
No
|
-
|
-
|
Option.
|
Added as FSMA-broker-id abandoned 15/7/2017
|
EstablishmentUnitNumberReference
|
| 183 | n |
Intermédiaire - LEI
|
No
|
-
|
-
|
Option.
|
LegalEntityIdentifierReference
|
|
| 190 | u |
Intermédiaire - Référence police producteur
|
No
|
-
|
-
|
Option.
|
BrokerPolicyReference
|
|
| 200 | u |
Message end
|
No
|
-
|
-
|
Mand.
|
||
(*) 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.