BaselineReportV04

tsmt.011.001.04

Scope The BaselineReport message is sent by the matching application to the parties involved in an amendment request or to the parties involved in a data set match. The message is used to report either a pre-calculation or final calculation of the dynamic part of an established baseline. Usage The BaselineReport message can be sent by the matching application to the parties involved in an amendment request for a transaction established in the push-through mode. In the outlined scenario, the message is sent

to the party requested to accept or reject an amendment request after the matching application has received a BaselineAmendmentRequest message. The message informs about the provisional status of the dynamic part of the baseline.
to the requester and the accepter of an amendment request after the matching application has received an AmendmentAcceptance message conveying the acceptance of the amendment request. The message informs about the actual status of the dynamic part of the baseline. or The BaselineReport message can be sent by the matching application to the party which has sent an amendment request for a transaction established in the lodge mode. In the outlined scenario the message is used to inform about the actual status of the dynamic part of the baseline. or The BaselineReport message can be sent by the matching application to the parties involved in a data set match. In the outlined scenario, the message is sent
to the submitter of the data set(s) in the case of a data set match for a transaction established in the lodge mode.
to the submitter of the data set(s) and to the counterparty in case of a data set match for a transaction established in the push-through mode.The message can be sent after a successful data-set match or after the acceptance of mis-matched data sets to inform about the actual status of the dynamic part of the baseline.

Message Construction

Every ISO20022 message has at the highest level what we call ‘building blocks’. Because the message is constructed as immutable records, the association is by composition. Below you can see the relationship between the message and its constituent building blocks: For comparison, see the ISO20022 official specification

classDiagram
     direction LR
%% BaselineReportV04 recursion level 0 with max 0
BaselineReportV04 *-- "1..1" MessageIdentification1 : ReportIdentification
BaselineReportV04 *-- "0..1" MessageIdentification1 : RelatedMessageReference
BaselineReportV04 *-- "1..1" ReportType2 : ReportType
BaselineReportV04 *-- "1..1" SimpleIdentificationInformation : TransactionIdentification
BaselineReportV04 *-- "1..1" DocumentIdentification6 : EstablishedBaselineIdentification
BaselineReportV04 *-- "1..1" TransactionStatus4 : TransactionStatus
BaselineReportV04 *-- "0..2" DocumentIdentification5 : UserTransactionReference
BaselineReportV04 *-- "1..1" PartyIdentification26 : Buyer
BaselineReportV04 *-- "1..1" PartyIdentification26 : Seller
BaselineReportV04 *-- "1..1" BICIdentification1 : BuyerBank
BaselineReportV04 *-- "1..1" BICIdentification1 : SellerBank
BaselineReportV04 *-- "1..1" LineItem14 : ReportedLineItem
BaselineReportV04 *-- "0..1" PendingActivity2 : RequestForAction

Now, we will zero-in one-by-one on each of these building blocks.

ReportIdentification building block

Identifies the report. Identifies a message by a unique identifier and the date and time when the message was created by the sender. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MessageIdentification1 recursion level 0 with max 1
class MessageIdentification1{
    Identification IsoMax35Text
    CreationDateTime IsoISODateTime
}

MessageIdentification1 members

Member name	Description	Data Type / Multiplicity
Identification	Identification of the message.	IsoMax35Text - Required 1..1
CreationDateTime	Date of creation of the message.	IsoISODateTime - Required 1..1

RelatedMessageReference building block

Reference to the related message at the origin of the report or sent at the same time than the report. Identifies a message by a unique identifier and the date and time when the message was created by the sender. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MessageIdentification1 recursion level 0 with max 1
class MessageIdentification1{
    Identification IsoMax35Text
    CreationDateTime IsoISODateTime
}

MessageIdentification1 members

Member name	Description	Data Type / Multiplicity
Identification	Identification of the message.	IsoMax35Text - Required 1..1
CreationDateTime	Date of creation of the message.	IsoISODateTime - Required 1..1

ReportType building block

Type of baseline report. Specifies the type of report. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ReportType2 recursion level 0 with max 1
class ReportType2{
    Type ReportType2Code
}

ReportType2 members

Member name	Description	Data Type / Multiplicity
Type	Specifies whether the report is precalculated or current.	ReportType2Code - Required 1..1

TransactionIdentification building block

Unique identification assigned by the matching application to the transaction. This identification is to be used in any communication between the parties. . Information related to an identification, eg, party identification or account identification. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SimpleIdentificationInformation recursion level 0 with max 1
class SimpleIdentificationInformation{
    Identification IsoMax35Text
}

SimpleIdentificationInformation members

Member name	Description	Data Type / Multiplicity
Identification	Name or number assigned by an entity to enable recognition of that entity, eg, account identifier.	IsoMax35Text - Required 1..1

EstablishedBaselineIdentification building block

Unique identification assigned by the matching application to the baseline when it is established. Identifies a document by a unique identification and a version. Also provides reference to a baseline amendment number. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% DocumentIdentification6 recursion level 0 with max 1
class DocumentIdentification6{
    Identification IsoMax35Text
    Version IsoNumber
    AmendmentSequenceNumber IsoMax3NumericText
}

DocumentIdentification6 members

Member name	Description	Data Type / Multiplicity
Identification	Identification of a set of data.	IsoMax35Text - Required 1..1
Version	Unambiguous identification of the version of a set of data. Example: Version 1.	IsoNumber - Required 1..1
AmendmentSequenceNumber	Number that is assigned sequentially by the TSU to a baseline amendment.	IsoMax3NumericText - Optional 0..1

TransactionStatus building block

Identifies the status of the transaction by means of a code. Identifies the status of the transaction by means of a code. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% TransactionStatus4 recursion level 0 with max 1
class TransactionStatus4{
    Status BaselineStatus3Code
}

TransactionStatus4 members

Member name	Description	Data Type / Multiplicity
Status	Identifies the status of the transaction by means of a code.	BaselineStatus3Code - Required 1..1

UserTransactionReference building block

Reference to the transaction for each financial institution which is a party to the transaction. Identifies a document by a unique identification and its issuer. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% DocumentIdentification5 recursion level 0 with max 1
class DocumentIdentification5{
    Identification IsoMax35Text
}
DocumentIdentification5 *-- "1..1" BICIdentification1 : IdentificationIssuer
%% BICIdentification1 recursion level 1 with max 1
class BICIdentification1{
    BIC IsoBICIdentifier
}

DocumentIdentification5 members

Member name	Description	Data Type / Multiplicity
Identification	Identification of a set of data.	IsoMax35Text - Required 1..1
IdentificationIssuer	Uniquely identifies the financial institution which has issued the identification of the set of data by using a BIC.	BICIdentification1 - Required 1..1

Buyer building block

Party that buys goods or services, or a financial instrument. Entity involved in an activity. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% PartyIdentification26 recursion level 0 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
%% GenericIdentification4 recursion level 1 with max 1
class GenericIdentification4{
    Identification IsoMax35Text
    IdentificationType IsoMax35Text
}
%% PostalAddress5 recursion level 1 with max 1
class PostalAddress5{
    StreetName IsoMax70Text
    PostCodeIdentification IsoMax16Text
    TownName IsoMax35Text
    CountrySubDivision IsoMax35Text
    Country CountryCode
}

PartyIdentification26 members

Member name	Description	Data Type / Multiplicity
Name	Name by which a party is known and which is usually used to identify that party.	IsoMax70Text - Required 1..1
ProprietaryIdentification	Unique and unambiguous identifier assigned to a party using a proprietary identification scheme.	GenericIdentification4 - Optional 0..1
PostalAddress	Information that locates and identifies a specific address, as defined by postal services.	PostalAddress5 - Required 1..1

Seller building block

Party that sells goods or services, or a financial instrument. Entity involved in an activity. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% PartyIdentification26 recursion level 0 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
%% GenericIdentification4 recursion level 1 with max 1
class GenericIdentification4{
    Identification IsoMax35Text
    IdentificationType IsoMax35Text
}
%% PostalAddress5 recursion level 1 with max 1
class PostalAddress5{
    StreetName IsoMax70Text
    PostCodeIdentification IsoMax16Text
    TownName IsoMax35Text
    CountrySubDivision IsoMax35Text
    Country CountryCode
}

PartyIdentification26 members

Member name	Description	Data Type / Multiplicity
Name	Name by which a party is known and which is usually used to identify that party.	IsoMax70Text - Required 1..1
ProprietaryIdentification	Unique and unambiguous identifier assigned to a party using a proprietary identification scheme.	GenericIdentification4 - Optional 0..1
PostalAddress	Information that locates and identifies a specific address, as defined by postal services.	PostalAddress5 - Required 1..1

BuyerBank building block

The financial institution of the buyer, uniquely identified by its BIC. Unique and unambiguous identifier of a financial institution, as assigned under an internationally recognised or proprietary identification scheme. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% BICIdentification1 recursion level 0 with max 1
class BICIdentification1{
    BIC IsoBICIdentifier
}

BICIdentification1 members

Member name	Description	Data Type / Multiplicity
BIC	Code allocated to a financial institution by the ISO 9362 Registration Authority as described in ISO 9362 “Banking - Banking telecommunication messages - Business identifier code (BIC)”.	IsoBICIdentifier - Required 1..1

SellerBank building block

The financial institution of the seller, uniquely identified by its BIC. Unique and unambiguous identifier of a financial institution, as assigned under an internationally recognised or proprietary identification scheme. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% BICIdentification1 recursion level 0 with max 1
class BICIdentification1{
    BIC IsoBICIdentifier
}

BICIdentification1 members

Member name	Description	Data Type / Multiplicity
BIC	Code allocated to a financial institution by the ISO 9362 Registration Authority as described in ISO 9362 “Banking - Banking telecommunication messages - Business identifier code (BIC)”.	IsoBICIdentifier - Required 1..1

ReportedLineItem building block

Information on the goods. Calculation of the current situation of a baseline as a result of the submission of a commercial data set. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% LineItem14 recursion level 0 with max 1
class LineItem14{
    OrderedLineItemsTotalAmount IsoCurrencyAndAmount
    AcceptedLineItemsTotalAmount IsoCurrencyAndAmount
    OutstandingLineItemsTotalAmount IsoCurrencyAndAmount
    PendingLineItemsTotalAmount IsoCurrencyAndAmount
    OrderedTotalNetAmount IsoCurrencyAndAmount
    AcceptedTotalNetAmount IsoCurrencyAndAmount
    OutstandingTotalNetAmount IsoCurrencyAndAmount
    PendingTotalNetAmount IsoCurrencyAndAmount
}
LineItem14 *-- "1..0" LineItemDetails12 : LineItemDetails
%% LineItemDetails12 recursion level 1 with max 1
class LineItemDetails12{
    LineItemIdentification IsoMax70Text
    ProductName IsoMax70Text
    OrderedAmount IsoCurrencyAndAmount
    AcceptedAmount IsoCurrencyAndAmount
    OutstandingAmount IsoCurrencyAndAmount
    PendingAmount IsoCurrencyAndAmount
}
LineItemDetails12 *-- "0..0" IProductIdentifier2Choice : ProductIdentifier
LineItemDetails12 *-- "0..0" IProductCharacteristics1Choice : ProductCharacteristics
LineItemDetails12 *-- "0..0" IProductCategory1Choice : ProductCategory
LineItemDetails12 *-- "1..1" Quantity9 : OrderedQuantity
LineItemDetails12 *-- "1..1" Quantity9 : AcceptedQuantity
LineItemDetails12 *-- "1..1" Quantity9 : OutstandingQuantity
LineItemDetails12 *-- "1..1" Quantity9 : PendingQuantity
LineItemDetails12 *-- "0..1" PercentageTolerance1 : QuantityTolerance
LineItemDetails12 *-- "0..1" PercentageTolerance1 : PriceTolerance

LineItem14 members

Member name	Description	Data Type / Multiplicity
LineItemDetails	Calculated information about the goods of the underlying transaction.	LineItemDetails12 - Unknown 1..0
OrderedLineItemsTotalAmount	Line items total amount as indicated in the baseline.	IsoCurrencyAndAmount - Required 1..1
AcceptedLineItemsTotalAmount	Line items total amount accepted by a data set submission(s).	IsoCurrencyAndAmount - Required 1..1
OutstandingLineItemsTotalAmount	Difference between the ordered and the accepted line items total amount.	IsoCurrencyAndAmount - Required 1..1
PendingLineItemsTotalAmount	Line item total amount for which a mismatched data set has been submitted and has not yet been accepted or rejected.	IsoCurrencyAndAmount - Required 1..1
OrderedTotalNetAmount	Total net amount as indicated in the baseline.	IsoCurrencyAndAmount - Required 1..1
AcceptedTotalNetAmount	Total net amount accepted by a data set submission.	IsoCurrencyAndAmount - Required 1..1
OutstandingTotalNetAmount	Total net amount for which a mismatched data set has been submitted and has not yet been accepted or rejected.	IsoCurrencyAndAmount - Required 1..1
PendingTotalNetAmount	Difference between the ordered and the accepted total net amount.	IsoCurrencyAndAmount - Required 1..1

RequestForAction building block

Information on the next processing step required. Specifies the event that require an action from one of the parties to the trade transaction. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% PendingActivity2 recursion level 0 with max 1
class PendingActivity2{
    Type Action2Code
    Description IsoMax140Text
}

PendingActivity2 members

Member name	Description	Data Type / Multiplicity
Type	Code which specifies the next course of action that the receiver of the message must take.	Action2Code - Required 1..1
Description	Further information on the course of action that the receiver of the message must take.	IsoMax140Text - Optional 0..1

Extensibility and generalization considerations

To facilitate generalized design patterns in the system, the BaselineReportV04 implementation follows a specific implementaiton pattern. First of all, BaselineReportV04 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, BaselineReportV04Document implements IOuterDocument. Because BaselineReportV04 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type BaselineReportV04.

classDiagram
    class IOuterRecord
    BaselineReportV04 --|> IOuterRecord : Implements
    BaselineReportV04Document --|> IOuterDocument~BaselineReportV04~ : Implements
    class IOuterDocument~BaselineReportV04~ {
        BaselineReportV04 Message
     }

Document wrapper for serialization

The only real purpose BaselineReportV04Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:tsmt.011.001.04’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using BaselineReportV04.ToDocument() method. The returned BaselineReportV04Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    BaselineReportV04Document *-- BaselineReportV04 : Document

Sample of message format

This is an abbreviated version of what the message should look like.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:tsmt.011.001.04">
    <BaselnRpt>
        <RptId>
            <!-- ReportIdentification inner content -->
        </RptId>
        <RltdMsgRef>
            <!-- RelatedMessageReference inner content -->
        </RltdMsgRef>
        <RptTp>
            <!-- ReportType inner content -->
        </RptTp>
        <TxId>
            <!-- TransactionIdentification inner content -->
        </TxId>
        <EstblishdBaselnId>
            <!-- EstablishedBaselineIdentification inner content -->
        </EstblishdBaselnId>
        <TxSts>
            <!-- TransactionStatus inner content -->
        </TxSts>
        <UsrTxRef>
            <!-- UserTransactionReference inner content -->
        </UsrTxRef>
        <Buyr>
            <!-- Buyer inner content -->
        </Buyr>
        <Sellr>
            <!-- Seller inner content -->
        </Sellr>
        <BuyrBk>
            <!-- BuyerBank inner content -->
        </BuyrBk>
        <SellrBk>
            <!-- SellerBank inner content -->
        </SellrBk>
        <RptdLineItm>
            <!-- ReportedLineItem inner content -->
        </RptdLineItm>
        <ReqForActn>
            <!-- RequestForAction inner content -->
        </ReqForActn>
    </BaselnRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_1IisAQy4EeS3puOfnJm56A"
  previousVersion="_l8xdSNE8Ed-BzquC8wXy7w_1618740400"
  name="BaselineReportV04"
  definition="Scope&#xD;&#xA;The BaselineReport message is sent by the matching application to the parties involved in an amendment request or to the parties involved in a data set match.&#xD;&#xA;The message is used to report either a pre-calculation or final calculation of the dynamic part of an established baseline.&#xD;&#xA;Usage&#xD;&#xA;The BaselineReport message can be sent by the matching application to the parties involved in an amendment request for a transaction established in the push-through mode. In the outlined scenario, the message is sent&#xD;&#xA;- to the party requested to accept or reject an amendment request after the matching application has received a BaselineAmendmentRequest message. The message informs about the provisional status of the dynamic part of the baseline.&#xD;&#xA;- to the requester and the accepter of an amendment request after the matching application has received an AmendmentAcceptance message conveying the acceptance of the amendment request. The message informs about the actual status of the dynamic part of the baseline.&#xD;&#xA;or&#xD;&#xA;The BaselineReport message can be sent by the matching application to the party which has sent an amendment request for a transaction established in the lodge mode. In the outlined scenario the message is used to inform about the actual status of the dynamic part of the baseline.&#xD;&#xA;or&#xD;&#xA;The BaselineReport message can be sent by the matching application to the parties involved in a data set match. In the outlined scenario, the message is sent&#xD;&#xA;- to the submitter of the data set(s) in the case of a data set match for a transaction established in the lodge mode.&#xD;&#xA;- to the submitter of the data set(s) and to the counterparty in case of a data set match for a transaction established in the push-through mode.The message can be sent after a successful data-set match or after the acceptance of mis-matched data sets to inform about the actual status of the dynamic part of the baseline."
  registrationStatus="Registered"
  messageSet="_1a374FXOEeOkkLyrDUP66g"
  xmlTag="BaselnRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_1IisAwy4EeS3puOfnJm56A"
    previousVersion="_l8xdSdE8Ed-BzquC8wXy7w_1618741339"
    name="ReportIdentification"
    definition="Identifies the report."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RptId"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_1IisBQy4EeS3puOfnJm56A"
    previousVersion="_l9OJMNE8Ed-BzquC8wXy7w_1619662400"
    name="RelatedMessageReference"
    definition="Reference to the related message at the origin of the report or sent at the same time than the report."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="RltdMsgRef"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_1IisBwy4EeS3puOfnJm56A"
    previousVersion="_l9X6MNE8Ed-BzquC8wXy7w_1619662305"
    name="ReportType"
    definition="Type of baseline report."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RptTp"
    complexType="_RJ8op9p-Ed-ak6NoX_4Aeg_44495022" />
  <messageBuildingBlock
    xmi:id="_1IisCQy4EeS3puOfnJm56A"
    previousVersion="_l9X6MdE8Ed-BzquC8wXy7w_1618741237"
    name="TransactionIdentification"
    definition="Unique identification assigned by the matching application to the transaction.&#xA;This identification is to be used in any communication between the parties.&#xA;."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="TxId"
    complexType="_P-ile9p-Ed-ak6NoX_4Aeg_745508310" />
  <messageBuildingBlock
    xmi:id="_1IisCwy4EeS3puOfnJm56A"
    previousVersion="_l9X6MtE8Ed-BzquC8wXy7w_1618741167"
    name="EstablishedBaselineIdentification"
    definition="Unique identification assigned by the matching application to the baseline when it is established."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="EstblishdBaselnId"
    complexType="_RJWLtNp-Ed-ak6NoX_4Aeg_-481192802" />
  <messageBuildingBlock
    xmi:id="_1IisDQy4EeS3puOfnJm56A"
    previousVersion="_l9X6M9E8Ed-BzquC8wXy7w_1619661993"
    name="TransactionStatus"
    definition="Identifies the status of the transaction by means of a code."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="TxSts"
    complexType="_RbFb-Np-Ed-ak6NoX_4Aeg_1598523783" />
  <messageBuildingBlock
    xmi:id="_1IisDwy4EeS3puOfnJm56A"
    previousVersion="_l9X6NNE8Ed-BzquC8wXy7w_1618741729"
    name="UserTransactionReference"
    definition="Reference to the transaction for each financial institution which is a party to the transaction."
    registrationStatus="Provisionally Registered"
    maxOccurs="2"
    minOccurs="0"
    xmlTag="UsrTxRef"
    complexType="_RJWLsdp-Ed-ak6NoX_4Aeg_-86119846" />
  <messageBuildingBlock
    xmi:id="_1IisEQy4EeS3puOfnJm56A"
    previousVersion="_l9X6NdE8Ed-BzquC8wXy7w_1618740443"
    name="Buyer"
    definition="Party that buys goods or services, or a financial instrument."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Buyr"
    complexType="_PcH049p-Ed-ak6NoX_4Aeg_-1219999095" />
  <messageBuildingBlock
    xmi:id="_1IisEwy4EeS3puOfnJm56A"
    previousVersion="_l9X6NtE8Ed-BzquC8wXy7w_1618740739"
    name="Seller"
    definition="Party that sells goods or services, or a financial instrument."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Sellr"
    complexType="_PcH049p-Ed-ak6NoX_4Aeg_-1219999095" />
  <messageBuildingBlock
    xmi:id="_1IisFQy4EeS3puOfnJm56A"
    previousVersion="_l9X6N9E8Ed-BzquC8wXy7w_1619661898"
    name="BuyerBank"
    definition="The financial institution of the buyer, uniquely identified by its BIC."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="BuyrBk"
    complexType="_QEp0kNp-Ed-ak6NoX_4Aeg_792527554" />
  <messageBuildingBlock
    xmi:id="_1IisFwy4EeS3puOfnJm56A"
    previousVersion="_l9X6ONE8Ed-BzquC8wXy7w_1619661795"
    name="SellerBank"
    definition="The financial institution of the seller, uniquely identified by its BIC."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="SellrBk"
    complexType="_QEp0kNp-Ed-ak6NoX_4Aeg_792527554" />
  <messageBuildingBlock
    xmi:id="_1IisGQy4EeS3puOfnJm56A"
    previousVersion="_l9hEINE8Ed-BzquC8wXy7w_1618741434"
    name="ReportedLineItem"
    definition="Information on the goods."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RptdLineItm"
    complexType="_9RsSgQy6EeS3puOfnJm56A" />
  <messageBuildingBlock
    xmi:id="_1IisGwy4EeS3puOfnJm56A"
    previousVersion="_l9hEIdE8Ed-BzquC8wXy7w_1618740834"
    name="RequestForAction"
    definition="Information on the next processing step required."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="ReqForActn"
    complexType="_RaowBtp-Ed-ak6NoX_4Aeg_-888447978" />
  <messageDefinitionIdentifier
    businessArea="tsmt"
    messageFunctionality="011"
    flavour="001"
    version="04" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.