INTERFACE ID |
IB08 – Merchandising Hierarchy (Item Nodes) |
|||||||||||||||||||||||||||||||||
SOURCE |
RMS |
|||||||||||||||||||||||||||||||||
DESTINATIONS |
SIM |
|||||||||||||||||||||||||||||||||
INTEGRATION STYLE |
Asynchronous – Unidirectional |
|||||||||||||||||||||||||||||||||
DESCRIPTION |
RMS allows new items to be created that have an existing parent item. In RMS, the merchandise hierarchy levels for item assignment are required. RPM must know the merchandise hierarchy values that RMS contains. To ensure that RPM has the most current merchandise hierarchy values that RMS has, this API will send the merchandise hierarchy information to the RIB so that RPM may subscribe to it. |
|||||||||||||||||||||||||||||||||
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 |
|