Oracle Retail Integration (RIB and RICS)
Every Oracle Retail estate is really an integration estate. RIB moves the messages that keep merchandising, stores, point of service and finance agreeing with each other — and when a message stops moving, the symptom always appears somewhere other than the cause.
What actually goes wrong
RICS is being deprecated, and there is a dated cutoff
Oracle states that many RICS components are scheduled for deprecation in phases and that RICS will receive no further feature enhancements. Concretely: SOAP RIB-EXT with Basic Authentication is supported only until Q3 of calendar year 2027, after which integrations must use REST with OAuth 2.0. Oracle has not publicly named a single replacement product, so anyone telling you the answer is definitely Oracle Integration Cloud is ahead of the documentation. The right first step is an inventory of what you actually integrate and which interface each one uses.
Stuck messages and hospital records nobody is watching
RIB error hospital tables accumulate quietly. By the time a business user reports that inventory looks wrong, the hospital may hold weeks of failed messages, and reprocessing them in the wrong order makes the position worse rather than better. Sequencing matters.
Integration built as point-to-point because it was faster at the time
Direct database links and file drops between applications work until an upgrade removes the access they depend on. Cloud migration is where this debt comes due, usually with no documentation of what talks to what.