Scenario 17 - Plant Data Collection / Warehouse Management / Production Orders
17.0 Overview
Scenario #17 describes the integration for handling production orders between purchasing with receiving software, MRP, receiving and handheld device software.
The purpose of this scenario is to enable the visualization of the participant applications and the dialogs between them for this specific integration. This scenario is not meant to be the only model for integrating these participants. This is one model that may be used to design one’s own integration based on the specific.
17.1 Scenario
The scenario below contains the participants involved in the interaction, the dialog flows or conversation between them, certain assumptions about the sequence of events, and assumptions about the technical approach, for example, publish and subscribe.
This is a example to be used as a design recommendation.
17.2 Assumptions
This scenario assumes a loosely coupled, asynchronous approach with transaction management required but not explicitly defined.
The environment for this integration may be within a single enterprise, or across enterprises.
17.3 Participant Definitions
This Scenario contains four major participants: the purchasing with receiving application and the MRP, receiving and handheld device applications.
The definitions and details of these applications are left to the designer but are assumed to contain the functionality as defined by what is commonly sold in the commercial market place today. This definition is broadly accepted by the scenario designers and is a direct result of the decision not to define how the processing takes place within any individual application.
Each application must be able perform the services defined by the message BOD (business object document), but the internals of the application are not required or desired to be exposed at this level of standardized abstraction.
The most important factors in defining these participants is to ensure that an integration designer can communicate the requirements precisely enough to detail the interfaces needed and their interrelationships.
17.4 Business Workflow (Sequence)
The business workflow is graphically represented by starting at the Scenario top and reading from top down and from left to right.
17.5 Exception Handling
Exception handling is highly localized as the result of an implementation’s infrastructure, management and business rules. As such, this section of the Scenario documentation is planned to be used as a guide to help understand the additional intent of these Scenarios. If no exceptions are noted here, then it can be assumed that the Scenario designers agreed that the Scenario is straight forward and has no additional needs:
-
Note that the Confirm BOD is not shown in the scenario and that it is the most obvious method for providing an application level exception and feedback mechanism between business software components. Full Confirm BOD use is described in other OAGIS documentation in detail, but it should be noted that the specific use of the Confirm BOD may vary significantly from scenario to scenario and from integration to integration.
-
The Confirm BOD is typically intended to be used by the original receiving application to communicate to the sending application that the information it sent in the message BOD (business object document) was received and understood and can be processed.
-
If the information was not received or nor understood, or contained errors of any type, it is accepted practice for the OAGIS users to presume that the data was not acted on and in the absence of a Confirm BOD within a partnership previously agreed to time limit to resend the original message again.
-
As errors and assumptions are the bane of any implementation, it is strongly recommended that the Confirm BOD be used to prevent any potential problem although it is not a requirement by OAGIS use.
Feedback
OAGi and its members welcome your feedback.