|
INTERFACE ID |
SL05 - Purchase Order |
||||||||||||
|
SOURCE |
RMS |
||||||||||||
|
DESTINATIONS |
SIM |
||||||||||||
|
INTEGRATION STYLE |
Synchronous – Unidirectional |
||||||||||||
|
DESCRIPTION |
RMS exposes a Store LocationPO API that will allow external systems to create, edit, and delete purchase orders within RMS. The transaction will be performed immediately upon message receipt so success or failure can be communicated to the calling application.
SIM and external systems uses RSL to communicate with RMS in a real time fashion. POs can be created, modified or deleted at the header or the detail level, each with its own indicator.. The interface also gives additional visibility to deals or other attributes of the items on the PO.
All validation is owned and performed by RMS.
|
||||||||||||
|
DATA |
|
||||||||||||
|
DEPLOYMENT |
RSL |
||||||||||||
|
INTEGRATION SERVICE LEVELS |
Guaranteed, once-only delivery to destination |
|
|||||||||||
|
Scheduled data exchange |
|
||||||||||||
|
Audit-trail kept for data exchange (state historical duration of audit trail) |
No |
||||||||||||
|
Alerting required should data exchange fail? |
N/A |
||||||||||||
|
Retry of data exchange necessary? (state number of times before error is logged or failure condition is met) |
No |
||||||||||||
|
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 |
|
||||||||||||
|
Frequency of messaging or batch data exchange |
|
||||||||||||
|
XSD |