X hits on this document

131 views

0 shares

0 downloads

0 comments

32 / 48

London Market Implementation of ACORD DRI Messages and Data

first <MsgItem> aggregate will be used, i.e. immediately following the <TimeStamp> element.

A ‘negative’ Post Response is returned, with <MsgStatusCd> and <MsgStatusDetails> values populated as indicated, if any of the operations prescribed in the London Market ACORD DRI Messages Completion and Validation Rules v1 at the Post Response level fail. Otherwise, all checks to date will have been successful and a ‘positive’ Post Response is returned (‘received’).

Repository Operation Response messages

All further errors in RepositoryOperationRq messages arising from checks in the validity of payloads and attachments are to be sent asynchronously via the RepositoryOperationRs message.

<RepositoryOperationRs xmlns =”…“>

<MsgId>f81dfae-7dec-11d0-a765-00a0c91e6bf9</MsgId>

:

:

<ResponseInfo>

<MsgId>e98fcae-5dec-11d0-a123-00a0c91e6bf9</MsgId>

<AcknowledgementLevelIndicator>

application_validation</AcknowledgementLevelIndicator>

<AcknowledgementStatusCd>rejected

</AcknowledgementStatusCd>

<ErrorIndicator>reference_number_missing

</ErrorIndicator>

<ResponseDescription>reference number

missing</ResponseDescription>

</ResponseInfo>

:

:

</RepositoryOperationRq>

RepositoryOperationRs messages will not trigger a further response as these are not supported in the ACORD standards.

RepositoryOperationRs messages are validated as per the validation rules established for a request message.  However, failures against the validation rules are handled via out of band communication using the information resulting from the validation.

London Market restricted RLC A45 code table

London Market Implementation of ACORD DRI Messages v1.doc

Page 32 of 48

Document info
Document views131
Page views131
Page last viewedSat Dec 10 16:45:21 UTC 2016
Pages48
Paragraphs1101
Words9338

Comments