|
|
|
Problem
Statement |
|
|
To ensure a reliable flow of information between companies, Business Managers must be assured that their
trading partners receive GS1 Messages and are able to process them without error. The GS1 Simple-eb
specification calls for the full choreography of messages to support business processes.
For example, the Order process calls for an Initiator to create an Order document and a need to know it was
received prior to back end processing by the Responder’s business application. This is what we mean by The
Responder will create an Application Receipt Acknowledgement And Or ErrorApplication Receipt
Acknowledgement document for the Initiator to confirm that the Responder received the Order document. This
BMS does not deal with the additional separate need for a business level Response (Acceptance, Modification,
or Rejection) to an Order. So, for example, the Application Receipt Acknowledgement (ARA) for an Order would
not indicate that the Responder plans to fulfill the order exactly as requested by the Initiator e.g. with respect to
quantity, price, etc. Rather the ARA indicates receipt of the order document and optionally detection of errors or
warnings.
This choreography or, conversation ensures that trading partners are aware that the process is progressing in a
predictable fashion. A proper automated choreography allows trading partners to reduce expensive safeguards
and manual checks, to recognize data receipt and errors quickly, and therefore smooth the flow of goods and
services through the supply chain.
|
|
|
|
|
|
Audience |
|
|
Initiator – organization responsible for generating and sending a GS1 Business Message.
Responder – organization that receives and processes a GS1 Business Message. This organization is also
responsible for creating an XML Application Receipt Acknowledgment And Or Error Application Receipt
Acknowledgement in reply to the received GS1 Business Message when applicable. A Responder may
outsource to an Agent to act on their behalf.
|
|
|
Business
Context
|
|
|
Industry:
All
Geopolitical:
All
Product:
All
Process:
All
System
Capabilities: GS1
Official
Constraints: None
|
|
|
Business
Transaction View
|
|
|
|
|
|
Business
Transaction Use Case
Diagram |
|
|
This Business Requirement Document outlines the requirements and supporting processes for a
business application level acknowledgement of the receipt of a GS1 XML message and optional
indication of detected validation errors or warnings.
|
|
|
Use Case
Description
|
|
|
| Use
Case Name |
Initiator sending directly to a Responder |
| Use
Case Description |
The Initiator sends the intended XML Instance Document (business message) within
the context of a Business Process and potentially and a multi-step Collaboration. The
Responder upon receiving the XML Instance Document acknowledges receipt (and
optionally detects errors/warnings) at the SBDH,, Transaction, Command and/or
Document hierarchical levels and responds to the message Initiator. |
| Actors |
Initiator, Responder |
| Performance
Goals: |
None
|
| Preconditions: |
The Responder receives message.
|
| Postconditions: |
The message Initiator receives the Application Receipt Acknowledgement, including
optional error/warning message(s).
|
| Scenario: |
Begins when 1. The Responder’s Back End application receives an XML Instance Document
(business message)
Ends
when 2. The Responder generates and sends the Application Receipt Acknowledgement
message back to the Initiator.
|
|
|
|
Business
Transaction Activity Diagram(s) |
|
|
|
|
Business
Transaction Sequence Diagram(s) |
|
|
No Sequence Diagram(s)
|
|
