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-365

Informations to reject on header level at receipt advice

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Major
    • Resolution: Applied
    • Component/s: None
    • Labels:

      Description

      We need new elements to specify the Acceptance Code and the reasons so a receipt advice can reject the delivery as a whole, like:

       

      1. cbc:DeliveryAcceptanceCode[0..1] Code specifies the acceptance or rejection of the delivery (Accept in full, partial accepted, refused (not today) or rejected). 
      2. cbc:RejectReasonCode [0..1]    The reason for a rejection, expressed as a code.
      3. cbc:RejectReason [0..*]    The reason for a rejection, expressed as text.
      4. cbc:RejectActionCode [0..1]    A code signifying the action that the delivery party wishes the despatch party to take as the result of a rejection

        Attachments

          Activity

          Descending order - Click to sort in ascending order
          Hide
          Permalink
          kenneth.bengtsson Kenneth Bengtsson added a comment -

          It is also necessary to change the Receipt advice definition so it also can be used as a reply to the despatch advice, as recorded in https://issues.oasis-open.org/browse/UBL-370.

          Show
          kenneth.bengtsson Kenneth Bengtsson added a comment - It is also necessary to change the Receipt advice definition so it also can be used as a reply to the despatch advice, as recorded in  https://issues.oasis-open.org/browse/UBL-370 .
          Hide
          Permalink
          kenneth.bengtsson Kenneth Bengtsson added a comment -

          Discussed at today's Pacific call that there are use cases where a header level response is useful together with Receipt Lines. Agreed to ask the originator if the addition of rejection information at header level without making the receipt lines optional will solve the requirements.

          Show
          kenneth.bengtsson Kenneth Bengtsson added a comment - Discussed at today's Pacific call that there are use cases where a header level response is useful together with Receipt Lines. Agreed to ask the originator if the addition of rejection information at header level without making the receipt lines optional will solve the requirements.

            People

            • Assignee:
              kenneth.bengtsson Kenneth Bengtsson
              Reporter:
              peter.borresen Peter Borresen
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: