Purchase Order

 

Purchase order messages may pertain to physical locations only, or to virtual or physical locations. If RMS is configured to run in a multi-channel environment, virtual warehouse locations hold stock, while physical warehouse locations would not. If the RMS does not use multi-channel, physical warehouse locations hold stock.

 

RMS publishes purchase orders as a header with multiple detail lines. Each detail line specifies the location the detail must be routed to. A Purchase Order routing TAFR may route a single published RMS purchase order message to more than one warehouse (RWMS instance) or store.

 

A Store system may also publish purchase orders for RMS and RWMS subscription.

 

During the Purchase Order creation process, the publication state of the order is maintained in a RIB table. No records are queued for publication until the order has been approved. Approval enables the RIB to harvest the order details and then to publish the information. After approval, all modifications to the order are available for publication as they occur and are published in chronological order.

 

The messages are routed based on their facility type, derived from the routing information, and the physical warehouse identifier. The physical warehouse identifier is extracted from the message data. A new message type is created and published by the TAFR, which is only subscribed to by the appropriate RWMS warehouse or store.

 

 

Message Type

XSD

POCre

PODesc.xsd

POHdrMod

PODesc.xsd

PODel

PORef.xsd

PODtlCre

PODesc.xsd

PODtlMod

PODesc.xsd

PODtlDel

PORef.xsd

 

 

TAFRs

 

OrderToOrderISOTAFR

OrderToOrderWHTAFR

 

 

Disclaimer: This document is a general data mapping and reference guide for data coming in and out of Oracle Retail application systems via RIB messages; it is not meant to give detailed information about every possible data scenario.