INTERFACE ID |
IB65 – Pending Returns |
|||||||||||||||
SOURCE |
External |
|||||||||||||||
DESTINATIONS |
RWMS |
|||||||||||||||
INTEGRATION STYLE |
Asynchronous – Unidirectional |
|||||||||||||||
DESCRIPTION |
Pending Return messages are used by RWMS to create and maintain Pending Returns information. Pending Returns messages are published by a Host system. Pending Returns messages notify the warehouse of merchandise that is being returned to the warehouse. These messages provide information to the warehouse about the amount of each item that is being returned. The Pending Returns messages are specific to a particular warehouse instance and therefore contain routing information so that the bus can guarantee successful delivery of the message to the appropriate DC. |
|||||||||||||||
DATA |
|
|||||||||||||||
DEPLOYMENT |
RIB |
|||||||||||||||
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 |
|||||||||||||||
PERFORMANCE SERVICE LEVELS |
If this is a server application, what is the design-time number of concurrent clients that will be serviced? |
|
||||||||||||||
Priority of integration (High, Medium, Low)? |
|
|||||||||||||||
Fail-over required? |
|
|||||||||||||||
Expected response time or batch processing window |
N/A |
|||||||||||||||
Frequency of messaging or batch data exchange |
|