SaleToPOIMessageRejectionV02

casp.013.001.02

The SaleToPOIMessageRejection message is sent by one of the parties when it detects a technical or functional error in a previous received message.

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
%% SaleToPOIMessageRejectionV02 recursion level 0 with max 0
SaleToPOIMessageRejectionV02 *-- "1..1" Header41 : Header
SaleToPOIMessageRejectionV02 *-- "1..1" AcceptorRejection2 : Reject
  

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

Header building block

Set of characteristics related to the transfer of the request. Set of characteristics related to the protocol. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Header41 recursion level 0 with max 1
class Header41{
    MessageFunction RetailerMessage1Code
    ProtocolVersion IsoMax6Text
    ExchangeIdentification IsoMax35Text
    CreationDateTime IsoISODateTime
}
Header41 *-- "1..1" GenericIdentification177 : InitiatingParty
Header41 *-- "0..1" GenericIdentification177 : RecipientParty
Header41 *-- "0..0" Traceability8 : Traceability
%% GenericIdentification177 recursion level 1 with max 1
class GenericIdentification177{
    Identification IsoMax35Text
    Type PartyType33Code
    Issuer PartyType33Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
GenericIdentification177 *-- "0..1" NetworkParameters7 : RemoteAccess
GenericIdentification177 *-- "0..1" Geolocation1 : Geolocation
%% GenericIdentification177 recursion level 1 with max 1
class GenericIdentification177{
    Identification IsoMax35Text
    Type PartyType33Code
    Issuer PartyType33Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
GenericIdentification177 *-- "0..1" NetworkParameters7 : RemoteAccess
GenericIdentification177 *-- "0..1" Geolocation1 : Geolocation
%% Traceability8 recursion level 1 with max 1
class Traceability8{
    ProtocolName IsoMax35Text
    ProtocolVersion IsoMax6Text
    TraceDateTimeIn IsoISODateTime
    TraceDateTimeOut IsoISODateTime
}
Traceability8 *-- "1..1" GenericIdentification177 : RelayIdentification
  

Header41 members

Reject building block

Information related to the reject. Reject of an exchange. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AcceptorRejection2 recursion level 0 with max 1
class AcceptorRejection2{
    RejectReason RejectReason1Code
    AdditionalInformation IsoMax500Text
    MessageInError IsoMax100KBinary
}
  

AcceptorRejection2 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    SaleToPOIMessageRejectionV02 --|> IOuterRecord : Implements
    SaleToPOIMessageRejectionV02Document --|> IOuterDocument~SaleToPOIMessageRejectionV02~ : Implements
    class IOuterDocument~SaleToPOIMessageRejectionV02~ {
        SaleToPOIMessageRejectionV02 Message
     }
  

Document wrapper for serialization

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

classDiagram
    SaleToPOIMessageRejectionV02Document *-- SaleToPOIMessageRejectionV02 : 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:casp.013.001.02">
    <SaleToPOIMsgRjctn>
        <Hdr>
            <!-- Header inner content -->
        </Hdr>
        <Rjct>
            <!-- Reject inner content -->
        </Rjct>
    </SaleToPOIMsgRjctn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_IAhL0Q1UEeqjM-rxn3HuXQ"
  previousVersion="_4R49hN6cEeiwsev40qZGEQ"
  name="SaleToPOIMessageRejectionV02"
  definition="The SaleToPOIMessageRejection message is sent by one of the parties when it detects a technical or functional error in a previous received message."
  registrationStatus="Registered"
  messageSet="_O55JAIX9EemxIqbaFEE8-w"
  xmlTag="SaleToPOIMsgRjctn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_IAhy4Q1UEeqjM-rxn3HuXQ"
    previousVersion="_4R49ht6cEeiwsev40qZGEQ"
    name="Header"
    definition="Set of characteristics related to the transfer of the request."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_BwWUYQuKEeqYM5yH99IYQw" />
  <messageBuildingBlock
    xmi:id="_IAhy4w1UEeqjM-rxn3HuXQ"
    previousVersion="_vgCQ4d6dEeiwsev40qZGEQ"
    name="Reject"
    definition="Information related to the reject."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Rjct"
    complexType="_8TjN8TTfEeO5e9wx3yvd8g" />
  <messageDefinitionIdentifier
    businessArea="casp"
    messageFunctionality="013"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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