|
INTERFACE ID |
IB23 - ASN Outbound - Bill of Lading (BOL) |
|||||||||
|
SOURCE |
RWMS, SIM, RMS |
|||||||||
|
DESTINATIONS |
RMS, SIM, RWMS |
|||||||||
|
INTEGRATION STYLE |
Asynchronous Unidirectional |
|||||||||
|
DESCRIPTION |
ASN inbound messages are advanced shipment notification (ASN) messages that inform RWMS or SIM to expect a shipment of merchandise. These messages can originate from an outside vendor, from another RWMS instance, or from SIM (in the case of a transfer or allocation shipment). RMS and Store systems subscribe to ASN inbound messages (as well as RWMS). RMS and Store systems use the ASN inbound message to create shipment records. For ASNs originating from external vendors or SIM, the message is routed to the proper RWMS warehouse instance based on the facility type found in the routing information and the To location found in the message data. SIM will subscribe to any messages routed to a store from a vendor or warehouse. Because only one database instance exists for SIM, all ASN messages bound for a store will be subscribed to. For transfers between warehouses, ASN Inbound messages are created when RWMS publishes an ASN Outbound message. The outbound message is a notification that a shipment is leaving the warehouse. Transformation from an ASN Outbound (from the warehouse) to an ASN Inbound (to the specific distribution center) occurs, routing the transformed message to the appropriate subscribing systems. |
|||||||||
|
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 |
|
|||||||||