|
INTERFACE ID |
SL02 - Price Change Request/Confirmation |
|||
|
SOURCE |
RPM |
|||
|
DESTINATIONS |
SIM |
|||
|
INTEGRATION STYLE |
Synchronous – Unidirectional |
|||
|
DESCRIPTION |
Price changes are used by the retailer to change the price of a particular item at a location. In the merchandising system (such as RMS), users create the initial retail prices for items. The price zone structure is held in the price management system (such as RPM). Items are no longer limited to a specific store, zone, or corporate level zone group.
Regardless of the level at which the initial prices are set, all prices in RMS are held at the item/location level. After the initial prices have been set, ensuing control of prices is handled through RPM.
This communication is handled by RSL (providing a real-time connection between the applications). Normal operation of pricing assumes that RSL and RPM are both available.
SIM uses RSL for real time price change requests. Only a single item/store request can be asked for at one time. It handles regular price changes, clearances or promotions. After the price change request is approved SIM will store a temporary record of the price change until the official message from RPM arrives over the RIB. RPM can also indicate that a price change request is not approved in a real time fashion based on its own internal rules.
|
|||
|
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 |