|
INTERFACE ID |
IB11 - Receiver Unit Adjustment |
|||||
|
SOURCE |
RMS |
|||||
|
DESTINATIONS |
SIM |
|||||
|
INTEGRATION STYLE |
Asynchronous – Unidirectional |
|||||
|
DESCRIPTION |
When receipt adjustments are made in RMS it is necessary to communicate the new inventory positions to other systems that track inventory positions. A message is published to the RIB to accomplish this task. The Location id is used as the business object id. For each location, all Receiver Unit Adjustments (that have not already been published) are rolled up to the item level and published. (Each location may have one or more items for which a RUA has been applied.) SIM subscribes to this message to ensure that the receipt adjustments reflect what is recorded at the store. This allows for a consistent view among ReIM, RMS, and SIM. |
|||||
|
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 |
|
|||||