Message Content Inventory |
Archived, and was part of release 200901 : Identifier : M0116 - Contrat, péréquation - (Péréquations, première version) - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Insurer
Receiver : Broker
Status : 3 - Version : 1
|
Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
||||||
10 | n |
Message issuing date and time
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitIssueDateTime
|
|
11 | n |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescription
|
|
12 | n |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescriptionVersion
|
|
20 |
Numéro de police
|
No
|
-
|
-
|
Mand.
|
PolicyReference
|
||
25 | n |
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
|
26 | n |
Nombre de documents annexes
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
DocumentsAttachedQuantity
|
30 |
Numéro du producteur dans la compagnie
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
40 |
Référence police producteur
|
No
|
-
|
-
|
Option.
|
BrokerPolicyReference
|
||
50 |
Nom du produit à la compagnie
|
No
|
-
|
-
|
Option.
|
ProductNameProductcode
|
||
60 |
Date d'effet de l'adaptation
|
No
|
-
|
-
|
Mand.
|
InceptionDate
|
||
70 |
Nom du preneur d'assurance
|
No
|
-
|
-
|
Mand.
|
OfficialName NameDetail LastName FirstName NameExtension
|
||
80 |
Commission d'acquisition supplémentaire suite à l'adaptation
|
No
|
-
|
-
|
Mand.
|
SupplementaryAcquisitionCommissionAmount
|
||
90 |
Code mouvement : indexation ou refus d'indexation
|
Yes
|
1
|
Mand.
|
CurrentAccountLineFollowingRedistributionProcesscode
|
|||
100 |
Péréquations par garantie ...
|
No
|
-
|
-
|
Mand.
|
(Sub)Guarantee...
|
||
110 |
Garantie - Nouveau capital
|
No
|
-
|
-
|
Mand.
|
CapitalAmount
|
||
120 |
Garantie - Augmentation du capital
|
No
|
-
|
-
|
Mand.
|
ChangeOfCapitalAmount
|
||
130 |
Garantie - Nouvelle prime
|
No
|
-
|
-
|
Mand.
|
NetPremiumAmount
|
||
140 |
Garantie - Augmentation de prime
|
No
|
-
|
-
|
Mand.
|
IncreaseOfPremiumAmount
|
(*) 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.