INTERFACE ID |
IB76 – Fulfill Order Confirm Cancel |
|||||||
SOURCE |
SIM |
|||||||
DESTINATIONS |
External (OMS) |
|||||||
REFERENCE |
oms-FulfillOrderCancelConfirmService_prv_FunctionalSpec.html |
|||||||
INTEGRATION STYLE |
Asynchronous – Unidirectional |
|||||||
DESCRIPTION |
If a customer order cancellation is initiated by an order management system (OMS) that is being fulfilled from a store, it is assumed that prior to cancelling the order a confirmation is needed from the store that the order can in fact be cancelled. In some cases, it may be considered too late to cancel because the customer has already picked up the order or SIM has already shipped it, but the update was not yet processed by OMS. So, enforcing a confirmation prior to canceling the order and reimbursing the customer is intended to prevent possible fraud. This service is used by OMS to process a cancellation confirmation sent by SIM. If the order was considered ?cancelable?, then OMS would next send the approved cancellation onto RMS to release inventory. |
|||||||
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 |