INTERFACE ID |
IB26 – Item Warehouse |
|||||||||
SOURCE |
RWMS |
|||||||||
DESTINATIONS |
External |
|||||||||
INTEGRATION STYLE |
Asynchronous – Unidirectional |
|||||||||
DESCRIPTION |
RWMS communicates items that reside in a forward picking/forward case picking location to a third-party SKU profiling system for the purposes of warehouse optimization. RWMS item information can be published in one of two ways. The first is through a Distribution Center (DC) Profiling support function provided within RWMS. The second is through a series of item related event triggers that result in the item data being sent. These event triggers include: · Modification or Deletion of an optimized and published item/SKU (item has sku_optimized and sku_opt_published flags set to Y). · Modification or Deletion of an optimized and published SKU’s supplier information. · Modification or Deletion of an optimized and published SKU’s supplier country information. · Modification or Deletion of an optimized and published SKU’s supplier country DIM information. · Creation, Modification, or Deletion of an optimized and published SKU’s association to a forward picking/case picking location. · First association of an optimized SKU to an appointment. · First association of an optimized SKU to an allocation. The information sent to the third-party system for add or modify requests includes the following: item header information, item supplier information, item supplier country information, and item supplier country DIM information. Deletes of item information will include only the DC Destination ID (from location) and the item id for the item being deleted. |
|||||||||
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 |
|