OASIS Universal Business Language (UBL) TCIcon indicating the project type

OASIS Universal Business Language (UBL) TC

Uploaded image for project: 'OASIS Universal Business Language (UBL) TC'
  1. OASIS Universal Business Language (UBL) TC
  2. UBL-241

Additional information item to clarify Status reasons

    Details

    • Proposal:
      Hide

      Agreed at the conference calls on July 17 to add a repeatable Sub Status to the status:

      <cac:Status>
    <cbc:StatusReasonCode listID="RMStatusReason">LEG</cbc:StatusReasonCode>
    <cbc:StatusReason>Legal issue</cbc:StatusReason>
    <cac:SubStatus>
        <cbc:StatusReasonCode listID="RMStatusClarification">VAT1</cbc:StatusClarificationCode>
        <cbc:StatusReason>No VAT reference</cbc:Description>
    </cac:SubStatus>
    <cac:Condition>
        <cbc:AttributeID schemeID="RMFieldValue">BT-48</cbc:AttributeID>
        <cbc:Description>EU123456789</cbc:Description>
    </cac:Condition>
</cac:Status>

      https://lists.oasis-open.org/archives/ubl/201907/msg00018.html

      Show
      Agreed at the conference calls on July 17 to add a repeatable Sub Status to the status: <cac:Status> <cbc:StatusReasonCode listID= "RMStatusReason" > LEG </cbc:StatusReasonCode> <cbc:StatusReason> Legal issue </cbc:StatusReason> <cac:SubStatus> <cbc:StatusReasonCode listID= "RMStatusClarification" > VAT1 </cbc:StatusClarificationCode> <cbc:StatusReason> No VAT reference </cbc:Description> </cac:SubStatus> <cac:Condition> <cbc:AttributeID schemeID= "RMFieldValue" > BT-48 </cbc:AttributeID> <cbc:Description> EU123456789 </cbc:Description> </cac:Condition> </cac:Status> https://lists.oasis-open.org/archives/ubl/201907/msg00018.html

      Description

      EESPA reports that it is sometimes necessary to provide additional information to clarify a Status Reason Code / Status Reason in an application response. For example:

      Status reason: Legal issue

      Status clarification: VAT reference is required

      There may be several clarifications for a status reason, why simply providing more elaborate code lists for status reason codes is not sufficient. The Condition ASBIE is already being used to provide detailed information about required and/or missing elements and values, why the reporter doesn't find that it can fulfill their requirement.

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          keesduvekot Kees Duvekot added a comment -

          would it be possible to add a "SubStatus" to the Status element to provide a "additional level" for status codes.

          Show
          keesduvekot Kees Duvekot added a comment - would it be possible to add a "SubStatus" to the Status element to provide a "additional level" for status codes.
          Hide
          Permalink
          kenneth.bengtsson Kenneth Bengtsson added a comment -

          The solution would then look something like:

          <cac:Status>
    <cbc:StatusReasonCode listID="RMStatusReason">LEG</cbc:StatusReasonCode>
    <cbc:StatusReason>Legal issue</cbc:StatusReason>
    <cac:SubStatus>
        <cbc:StatusReasonCode listID="RMStatusClarification">VAT1</cbc:StatusClarificationCode>
        <cbc:StatusReason>No VAT reference</cbc:Description>
    </cac:SubStatus>
    <cac:Condition>
        <cbc:AttributeID schemeID="RMFieldValue">BT-48</cbc:AttributeID>
        <cbc:Description>EU123456789</cbc:Description>
    </cac:Condition>
</cac:Status>

          And users may add further levels of sub statuses within the sub status. I think that might be a good solution as well.

          Show
          kenneth.bengtsson Kenneth Bengtsson added a comment - The solution would then look something like: <cac:Status> <cbc:StatusReasonCode listID= "RMStatusReason" > LEG </cbc:StatusReasonCode> <cbc:StatusReason> Legal issue </cbc:StatusReason> <cac:SubStatus> <cbc:StatusReasonCode listID= "RMStatusClarification" > VAT1 </cbc:StatusClarificationCode> <cbc:StatusReason> No VAT reference </cbc:Description> </cac:SubStatus> <cac:Condition> <cbc:AttributeID schemeID= "RMFieldValue" > BT-48 </cbc:AttributeID> <cbc:Description> EU123456789 </cbc:Description> </cac:Condition> </cac:Status> And users may add further levels of sub statuses within the sub status. I think that might be a good solution as well.
          Hide
          Permalink
          kenneth.bengtsson Kenneth Bengtsson added a comment -

          SubStatus added to the Status ABIE

          Show
          kenneth.bengtsson Kenneth Bengtsson added a comment - SubStatus added to the Status ABIE

            People

            • Assignee:
              kenneth.bengtsson Kenneth Bengtsson
              Reporter:
              kenneth.bengtsson Kenneth Bengtsson
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: