> Syntax independent - MCIs - Messages > Details

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Identifier : AMEME - - (A Message Envelope - holding Message(s) being Exchanged)
- Approved , and is part of release 202101 - ( TB2-UN/Edifact MIG : Fr / Nl ) - ( TB2-XML : added info )
( Additional information is present below the details-table )
Version : 1
Status : 2
Seq. n° n
u
d
(*)
Data element
Code list
Usage
Mandatory
Conditional
Optional (**)
Condition(s)
TB2-UN/EDIFACT representation (including comments)
Indicator
Identifier
Version
10  
Message Envelope - Syntax version number
No
-
-
Mand.
 
XGH+1' 
20  
Envelope Sender Domain Address
No
-
-
Mand.
 
XGH+1+x--x' 
30  
Envelope Sender User Address
No
-
-
Option.
 
XGH+1+x--x:x--x' 
40  
Envelope Sender Type Coded
No
-
-
Option.
 
XGH+1+x--x:x--x:x--x' 
50  
Envelope Recipient Domain Address
No
-
-
Mand.
 
XGH+1+x--x:x--x:x--x+x--x' 
60  
Envelope Recipient User Address
No
-
-
Option.
 
XGH+1+x--x:x--x:x--x+x--x:x--x' 
70  
Envelope Recipient Type Coded
No
-
-
Option.
 
XGH+1+x--x:x--x:x--x+x--x:x--x:x--x' 
80  
Envelope Content Group Type
No
-
-
Option.
 
XGH+1+x--x:x--x:x--x+x--x:x--x:x--x+x--x' 
90  
Envelope Content - Message = Exchange Unit
No
-
-
Mand.
1..n occurrencies - each one of (M0101v17 / M0103v17 / M0104ANNv6 / M0104MODv17 / M0104REMv17 / M0104RESv7 / M0104REXv17 / M0104SUSv5 / M0104TFTv17 / M0104TFTRv13 / M0105v6 / M0108v6 / M0109v11 / M0114v17 / M0118v17 / M0119v15 / M0121v13 / M0122v13 / M0123v13 / M0124v12 / M0125v5 / M0126v10 / M0130v7 / M0131v6 / M0139v5 / M0140v3 / M0147v4 / M0202v10 / M0203v6 / M0204v10 / M0205v10 / M0206v10 / M0207v6 / M0210v10 / M0211v10 / M0214v4 / M0215v3 / M0216v1 / M0302v4 / M0303v2 / M0304v10 / M0306v4 / M0307v2 / M0308v2 / M0401v2 / M0403v2 / M0405v2 / M0410v10 / M0603v3 / M0701v3 / M0901v1 / M0902v1 / M9101v2 / M9103v5 / M9120v3 / M9130v1 / M9730v5) 
XEH … XET 
100  
Message Envelope - Syntax version number
No
-
-
Mand.
 
XGT+1' 

(*) n u d : new / updated / deleted since previous version.

(*bis) u : updated : this can be a codelist-version incrementing.
  Note that in many, not to say all such cases, the user-community does not await such next release to implement/activate such new codelist-values.
  The reasoning is that such added value does not affect the current data-structures and hence is considered easely implementable.
  Such reasoning tends to forget how given new codelist-values might not simply affect the data, but also affect the process, which might be more of a problem...

(**) 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.



Added information :

Voir dans les BBP dans les généralités la partie décrivant le -flux d'une transaction-. ( Suivre >Models >Broker Business Processes) - Dans le schéma (variante 2) les flèches représentant les Response Record et les Structured Message.
/ Zie in de BBP in de algemeenheden het deel over de -transactionele stream-. ( Volg >Models >Broker Business Processes) - In het schema (variante 2) de pijlen die het response Record en de Structured Message voorstellen.
( http://www.telebib2.org/ProcessBB.htm#Invocation )