|
INTERFACE ID |
IB39 – Clearance Price Change |
|||||||||
|
SOURCE |
RPM |
|||||||||
|
DESTINATIONS |
SIM |
|||||||||
|
INTEGRATION STYLE |
Asynchronous – Unidirectional |
|||||||||
|
DESCRIPTION |
RPM publishes approved clearance price changes at the transaction item/location level. They are published as fixed price clearances with the change type and price guides already applied. The message type for this event is “clrprcchgcre”. Clearance changes include a markdown number, out of stock date and reset date. Clearance changes also include a clearance retail price change when another price event’s retail affects an approved clearance price change. The message type for this event is “clrprcchgmod”. When approved clearances are unapproved, RPM sends a message with type = “clrprcchgdel”. SIM subscribes to the “clrprcchgcre” and “clrprcchgRef” messages and will extract the clearance when it goes into effect or is reset. In some cases, SIM already has this information when the clearance is initiated by SIM. In that case, SIM overrides the existing records. |
|||||||||
|
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 |
|
|||||||||