The Oracle Retail Product Family
RMS doesn't work alone. It operates at the center of a massive software ecosystem. Learn how Store Inventory Management (SIM), Sales Audit (ReSA), Pricing (RPM), and Point of Sale (Xstore) integrate to run global retailers.
While Oracle RMS (Retail Merchandising System) is the undisputed core of the Oracle Retail suite, it is only one module in a sprawling ecosystem. Modern enterprise retailers use a specialized piece of software for every distinct function of their business.
To become a true Oracle Retail architect, you must understand not just how RMS works internally, but how it communicates with its sibling applications.
1. The Hub-and-Spoke Model
Oracle Retail is built on a Hub-and-Spoke architecture.
RMS acts as the Hub. It holds the "Golden Record" for all Master Data: items, suppliers, locations, and the organizational hierarchy. The other applications act as Spokes.
The Integration Engine
These systems do not talk to each other via direct database links. They communicate asynchronously using the Oracle Retail Integration Bus (RIB). RMS publishes an XML message (e.g., ItemCre) to a JMS topic, and interested systems (like SIM or RPM) subscribe to that topic to receive the new item data.
2. Store Operations (SIM & Xstore)
Oracle Xstore (Point of Sale)
Xstore is the physical cash register application running in the stores.
- Inbound from RMS: Xstore receives item definitions, barcodes, and current prices.
- Outbound to ReSA: At the end of the day (or via trickle polling), Xstore sends raw transactional logs (T-Logs) containing every sale, return, and discount applied.
Oracle SIM (Store Inventory Management)
SIM (now often called SIOCS - Store Inventory Operations Cloud Service) is the mobile application used by store associates on handheld scanners.
- Inbound from RMS: SIM receives advance shipping notices (ASNs) telling the store what inventory is arriving on the truck.
- Outbound to RMS: When a store associate counts inventory or receives a shipment, SIM publishes a message to RMS. RMS then updates the corporate
STOCK_ON_ORDERandSOH(Stock on Hand).
3. Pricing and Promotions (RPM)
Oracle RPM (Retail Price Management) handles the complex logic of pricing goods. While RMS tracks the cost of an item, RPM dictates the retail price.
- Regular Price Changes: When a buyer wants to raise the price of a t-shirt from $15 to $18, they do it in RPM.
- Clearance: When seasonal items need to be marked down, RPM schedules the markdown.
- Promotions: "Buy One Get One Free" or "20% off all Denim" are configured in RPM.
RPM to RMS Integration
When RPM executes a price change, it must immediately inform RMS. Why? Because RMS calculates the financial value of the inventory in the Stock Ledger. If the retail price drops, the total value of the company's assets drops, which must be recorded financially.
4. Financial Integrity (ReSA & ReIM)
Oracle ReSA (Retail Sales Audit)
ReSA is the gatekeeper for sales data. Xstore generates raw T-Logs, but cashiers make mistakes (e.g., scanning the same item twice, or applying manual discounts incorrectly). ReSA audits these transactions against strict rules. Only after ReSA cleans and validates the sales data does it pass the totals to RMS to decrement inventory.
Oracle ReIM (Retail Invoice Matching)
When a supplier sends a bill (invoice) for a shipment of goods, someone has to verify that the retailer actually received the goods before paying. ReIM automates this matching process.
- It compares the Supplier Invoice against the Purchase Order (from RMS) and the physical Receipt (from the Warehouse/SIM).
- If the quantities and costs match within tolerance, ReIM approves it for payment and sends it to the corporate Accounts Payable (AP) system.
5. Planning & Optimization (RPAS)
Oracle RPAS (Retail Predictive Application Server) is a specialized multidimensional database used for planning and forecasting. It is fundamentally different from the transactional nature of RMS.
While RMS records what happened, RPAS is used to determine what should happen.
- Demand Forecasting: Predicting how many umbrellas will sell next month based on historical sales (fed from RMS) and weather patterns.
- Merchandise Financial Planning (MFP): Setting budgets (Open to Buy) for different departments.
- Assortment Planning: Deciding which specific styles and colors should be sent to which stores.
Once RPAS creates a plan (e.g., "Buy 50,000 blue sweaters"), that plan is pushed into RMS as an approved Purchase Order.
6. Key Takeaways
Key Takeaways
- RMS is the master data hub. Items, locations, and suppliers are created in RMS and published to the rest of the ecosystem via the RIB.
- Xstore and SIM handle physical store operations (selling and receiving), feeding inventory updates back to RMS.
- RPM isolates all pricing logic, ensuring complex promotions don't bog down the core merchandising engine.
- ReSA ensures sales data is clean before it impacts inventory, while ReIM ensures suppliers are paid accurately based on physical receipts.
