|
INTERFACE ID |
IB76 – Fulfill Order Confirm |
|||||||||
|
SOURCE |
RMS, SIM |
|||||||||
|
DESTINATIONS |
External (OMS) |
|||||||||
|
REFERENCE |
||||||||||
|
INTEGRATION STYLE |
Asynchronous – Unidirectional |
|||||||||
|
DESCRIPTION |
Oracle Retail supports two methods of communicating fulfillment order messages between an order management system (OMS) and RMS, via RIB or via web service. In a web service implementation, a confirmation message is able to be sent automatically as part of the architecture of a web service upon processing a fulfillment order request. However, in a RIB implementation, this confirmation cannot be sent as the RIB is considered a ?fire and forget? type architecture. So, in order to ensure that OMS is notified if a customer order cannot be fulfilled based on the information sent to RMS, a confirmation RIB message is generated to communicate any issues. This service takes the RIB message generated by RMS and transforms it into a web service that is readable by OMS. |
|||||||||
|
DATA |
|
|||||||||
|
DEPLOYMENT |
RIB and RSB |
|||||||||
|
INTEGRATION SERVICE LEVELS |
Guaranteed, once-only delivery to destination |
Yes |
||||||||
|
Scheduled data exchange |
No |
|||||||||
|
Audit-trail kept for data exchange (state historical duration of audit trail) |
Auditing at message level. |
|||||||||
|
Alerting required should data exchange fail? |
Yes |
|||||||||
|
Retry of data exchange necessary? (state number of times before error is logged or failure condition is met) |
Yes. RIB Hospital. |
|||||||||
|
Data purge on data transmittal? |
Yes |
|||||||||
|
Security on data exchange required? |
No |
|||||||||