Message Content Inventory |
Archived, and was part of release 200601 : Identifier : M0104SUS - Contrat, avenant - (Avenant de suspension) |
Sender : Insurer
Receiver : Broker
Status : 3 - Version : 1
|
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 |
|||||||
15 |
Nature du document
|
Yes
|
2
|
Mand.
|
GIS+EW05
|
MessageNatureProcesscode
|
|||
20 |
Date de suspension
|
No
|
-
|
-
|
Mand.
|
DTM+060
|
SuspensionDate
|
||
25 |
Numéro de police
|
No
|
-
|
-
|
Mand.
|
RFF+001
|
PolicyReference
|
||
30 |
Numéro d'avenant
|
No
|
-
|
-
|
Mand.
|
RFF+002
|
EndorsementReference
|
||
35 |
Motif de suspension
|
Yes
|
3
|
Option.
|
ATT+A311
|
SuspensionMotiveCode
|
|||
40 |
Origine de la résiliation
|
Yes
|
1
|
Option.
|
ATT+A314
|
OriginForCancellationCode
|
|||
45 |
Etat de l'acceptation de la nouvelle affaire ou du projet
|
Yes
|
2
|
Option.
|
ATT+A055
|
StateOfAcceptanceCode
|
|||
54 |
Assureur
|
No
|
-
|
-
|
Option.
|
PTY+006
|
PartyInsurer
|
||
55 |
Assureur - Numéro CBFA
|
No
|
-
|
-
|
Mand.
|
X044
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
69 |
Intermédiaire
|
No
|
-
|
-
|
Option.
|
PTY+002
|
PartyIntermediary
|
||
70 |
Intermédiaire - Numéro CBFA
|
No
|
-
|
-
|
Option.
|
X044(1)
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
71 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
X044(2)
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
75 |
Intermédiaire - Référence police producteur
|
No
|
-
|
-
|
Option.
|
RFF+003
|
BrokerPolicyReference
|
(*) 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.