|
INTERFACE ID |
IB29 - Stock Order Status |
|||||
|
SOURCE |
RWMS, SIM |
|||||
|
DESTINATIONS |
RMS |
|||||
|
INTEGRATION STYLE |
Asynchronous – Unidirectional |
|||||
|
DESCRIPTION |
A stock order status message contains line items, or detail, of a ship order. Each line item has an associated stock order status. RMS subscribes to stock order status to keep transfer and allocation records up to date. Because of the number of reasons a stock order status message may be published, a TAFR is used to ensure RMS receives only stock order status messages that pertain to transfers and allocations. |
|||||
|
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 |
|
|||||