Scenario: Purchase Order Mediation v2
From SWS Challenge Wiki
Changes to the Legacy System
In the second phase of the challenge, two changes are introduced to the legacy system of Moon. (1) The Order Management (OM) system gets renamed to Stock Management (SM). While names differ, the message exchange pattern and the types of the messages for the SM system remain exactly the same as they were previously in OM system. (2) The big change is addition of the Production Management (PM) system from which mediator can now order products to be scheduled for production, when they are not available from SM system. The complete process for Moon 2 is presented in figure 1.
When the Stock Management system is incapable to fulfil request from the custerm and it replies that the particular line item cannot be accepted, the Mediator must communicates with the legacy Production Management system to obtain relevant information on date and price to manufacture a new product. If this information meets initial expectations of the customer as specified in the RosettaNet message, the product should be ordered.
- Production capabilities can be checked with Production Management system. Both the XML Schema and an example of Check Production Capability message have been provided.
- Production capabilites are confirmed by the Confirmation message. Again challenge participants should refer to XML Schema. An example of such a Confirmation message generated with this schema is also available.
- Scheduling production does not differ from checking production capabilites (only a different operation in Production Management should be called). Identical messages are send and received from PM system, so again Production Scheduling message and its Confirmation can be used for reference.
WSDL Quicklinks
- Customer Relationship Management System
- Stock Management System
- Production Management System
- Blue's endpoint to receive POC messages
Changes to RosettaNet
With the new changes to RosettaNet schema, there is a posibility to define shipment address at the line item level. If present, this address should be used instead the one defined at the purchase order level.
The new Purchase Order Request (POR) schema PO Request
An example of changed PO Request Message
The new Purchase Order Confirmation (POC) schema PO Confirmation
An example of changed PO Confirmation Message
We also provide a page summarizing all the RosettaNet schemas used for scenario 2.

