Service Change Announcements
Cost Tiers
Service Change: Oracle Restaurants Reporting and Analytics module Cost Tiers end of life
Date Announced: July 1, 2026
Date in Effect: July 1, 2027
Details: Oracle is announcing the end of life for Cost Tiers in Oracle Restaurants Reporting and Analytics. On or after July 1, 2027, Cost Tiers will be removed and will no longer be supported or available for use.
Cost Tiers allow customers to maintain menu item costs in Reporting and Analytics. Customers can export cost data from external inventory or costing systems, link cost tiers to menu item master items, and define cost of goods sold (COGS) values for those master items. Together with the Menu Item Cost Tier Upload Interface, customers can upload menu item cost data in bulk.
After Cost Tiers are removed, customers will no longer be able to create, maintain, assign, or upload menu item cost tier data in Reporting and Analytics. This may affect reports, custom reports, scheduled reports, exports, iQuery workbooks, or operational workflows that depend on Cost Tier data or menu item costs maintained through Cost Tiers.
Data that was uploaded or maintained before the removal date will be retained according to each customer’s contracted data retention limits.
Does this impact me? This impacts customers who use Cost Tiers in Reporting and Analytics to maintain menu item costs, link cost tiers to menu item master items, upload cost data through the Menu Item Cost Tier Upload Interface, or report on COGS, food cost, margin, or menu item profitability using Cost Tier data.
This does not impact customers who do not use Cost Tiers, the Menu Item Cost Tier Upload Interface, or reports based on Cost Tier-maintained menu item costs.
This does not impact customers using Oracle Restaurants Inventory Management.
This does not impact customers maintaining menu item costs from within Simphony Enterprise Management Console (EMC).
Next steps: Before the effective date, review your use of Cost Tiers and identify affected upload workflows, menu item cost maintenance processes, reports, custom reports, scheduled reports, exports, iQuery workbooks, and operational procedures.
Enterprise Maintenance Services (EMS)
Service Change: Oracle Restaurants Reporting and Analytics module Enterprise Maintenance Services (EMS) end of life
Date Announced: July 1, 2026
Date in Effect: July 1, 2026
Details: Oracle is announcing the end of life for Oracle Restaurants Reporting and Analytics module Enterprise Maintenance Services (EMS). On or after July 1, 2026, EMS will be removed and will no longer be supported or available for use.
EMS is a legacy RES3700 related capability.
Customers will no longer be able to access EMS functionality, or download the EMS client after removal. This also includes legacy EMS-related reporting.
Does this impact me? This impacts customers who use EMS or EMS-related workflows for legacy RES 3700 Enterprise Back Office maintenance, menu item, tax, or discount maintenance, reporting, or related operational processes.
This does not impact customers who do not use EMS or EMS-related RES 3700 functionality.
Next steps: Before the effective date, review your EMS usage and identify any affected workflows or operational procedures. Customers using EMS to maintain menu items, prices, taxes, or discounts need to change their operational procedures to maintain those definition types within RES3700 directly. Contact your Oracle representative for guidance on available alternatives and migration planning.
Financial Forms
Service Change: Oracle Restaurants Reporting and Analytics module Financial Forms end of life
Date Announced: July 1, 2026
Date in Effect: July 1, 2027
Details: Oracle is announcing the end of life for Financial Forms in Oracle Restaurants Reporting and Analytics. On or after July 1, 2027, Financial Forms will be removed and will no longer be supported or available for use.
Financial Forms are customer-specific data-entry forms used to capture individual operational or financial data points directly in Reporting and Analytics when those values are not captured through the point-of-sale system. Examples include rent or other operating costs, end-of-shift cash drawer counts by denomination, cash management information, cash discrepancy explanations, and other manager-entered values.
Financial Forms are created by Oracle Professional Services for a customer’s specific business process. In many cases, each Financial Form is delivered with a corresponding custom report that allows the business to review, analyze, and report on the values entered by store managers.
Does this impact me? After Financial Forms are removed, customers will no longer be able to enter, maintain, or report on Financial Forms data in Reporting and Analytics. This includes any accompanying custom reports, iQuery workbooks, exports, or operational procedures that depend on Financial Form data.
This impacts customers who use Financial Forms to enter or report on manually captured operational, financial, cash management, or store-level data in Reporting and Analytics.
This may also impact customers who use reports, custom reports, scheduled reports, iQuery workbooks, exports, or business processes that depend on Financial Form Detail or Financial Form Ledger Detail data.
This does not impact customers who do not use Financial Forms or Financial Forms-based reports.
Next steps: Before the effective date, review your use of Financial Forms and identify affected forms, reports, scheduled reports, iQuery workbooks, exports, and operational procedures. Export or preserve any Financial Forms data required for historical reference, audit, reconciliation, or business continuity.
Customers should plan to transition affected business processes to non-Oracle workflows or customer-managed alternatives before the effective date. Oracle Restaurants does not provide a replacement application for Financial Forms.
Forecasting
Service Change: Oracle Restaurants Forecasting and Budget end of life
Date Announced: July 1, 2026
Date in Effect: June 1, 2027
Details: Oracle is announcing the end of life for the Oracle Restaurants Forecasting and Budget module. On or after June 1, 2027, the Forecasting and Budget module will be removed and will no longer be supported or available for use in Reporting and Analytics. Customers will no longer be able to create or generate forecasts, configure forecast profiles, assign historical seed data, adjust or approve forecasts, configure forecast retention/performance settings, or create and schedule forecasting events.
Forecasts displayed in the Oracle MICROS InMotion Mobile app are not impacted by this announcement and will continue to appear within the app.
Does this impact me? This impacts customers who use Forecasting and Budget for sales, inventory, labor, staffing, or event-based forecasting. It may also impact customers whose labor or inventory planning processes depend on forecast profiles, generated forecasts, adjusted forecasts, approved forecasts, or event impact calculations.
This does not impact customers who only view forecasts in the Oracle MICROS InMotion Mobile app.
Next steps: Before the effective date, review your Forecasting and Budget usage, document affected workflows, export or preserve required forecast data, and transition affected users to replacement planning processes. Customers using forecast outputs for labor, inventory, or staffing decisions should validate replacement workflows before the effective date.
Master Items and Alignment
Service Change: Oracle Restaurants Reporting and Analytics modules Master Item Configuration UI and Alignment UI end of life
Date Announced: July 1, 2026
Date in Effect: July 1, 2027
Details: Oracle is announcing the end of life for the Master Item Configuration UI and Alignment UI in Oracle Restaurants Reporting and Analytics. On or after July 1, 2027, these user interfaces will be removed and will no longer be supported or available for use.
The Master Item Configuration UI and Alignment UI are part of the Reporting and Analytics item-alignment workflow. Item alignment standardizes menu items and other definitions by linking different location-level item names or POS references to a common master item, so reporting and calculations treat those variations as the same item.
Master Items are parent item definitions used to unify name variations. The Master Item Configuration UI is used to create and maintain those master items, including menu item master records, specific attributes, and category assignments.
The Alignment UI is used to manually align unaligned items, change alignments, transfer aligned items to a different master item, designate aligned items as aliases, unalign items, merge master items, create a master item from an unaligned item, modify alignment rules, and run the alignment process.
After the Master Item Configuration UI and Alignment UI are removed, customers will no longer be able to create, edit, merge, align, unalign, transfer, or alias master items through these Reporting and Analytics user interfaces.
There is no replacement for the Master Item Configuration UI or Alignment UI. However, with the architecture of Simphony for the enterprise, it will take over the creation of master items and the relevant item alignment. Attributes, types, category groups etc. that are today configured from the Master Item Configuration UI, will be migrated to appropriate EMC or Simphony configuration screens.
Does this impact me? With Simphony, those user interfaces should only be used in certain edge cases. If items are properly maintained at the enterprise level, there is no need to manually create master items or change the alignment of items.
Remote Transfer Agent (RTA) / .Connect Admin
Service Change: Oracle Restaurants Reporting and Analytics module Reporting Transfer Agent (RTA) / .Connect Admin end of life
Date Announced: July 1, 2026
Date in Effect: July 1, 2027
Details: Oracle is announcing the end of life for Oracle Restaurants Reporting and Analytics module Remote Transfer Agent (RTA) / .Connect Admin for legacy RES 3700 customers. On or after July 1, 2027, RTA / .Connect Admin will be removed and will no longer be supported or available for use.
For RES 3700 customers, RTA provides the connection between the on-premises POS environment and Reporting and Analytics. After RTA / .Connect Admin is removed, RES 3700 customers will essentially no longer be able to use Reporting and Analytics.
Without this data transfer, Reporting and Analytics reports, dashboards, exports, and analytics that depend on RES 3700 POS data will no longer receive new data.
Does this impact me? This impacts customers who use Oracle Restaurants Reporting and Analytics with legacy MICROS RES 3700.
This does not impact customers who use Simphony.
Next steps: Contact your Oracle Restaurants representative as soon as possible to start planning the migration to Simphony, our modern, cloud based POS System.
Upload Interfaces UI and Microsoft Excel Upload Templates
Service Change: Oracle Restaurants Reporting and Analytics modules Upload Interfaces and Templates end of life
Date Announced: July 1, 2026
Date in Effect: July 1, 2027
Details: Oracle is announcing the end of life for certain upload interfaces and templates in Oracle Restaurants Reporting and Analytics. On or after July 1, 2027, the defined upload interfaces will be removed and will no longer be supported or available for use.
Upload interfaces support specialized Reporting and Analytics upload workflows that allow customers to import selected supplemental datasets into the Reporting and Analytics database using downloadable Microsoft Excel templates. The uploaded data can then be used by specific reports and analytics workflows.
Upload interfaces and templates being removed are:
- Menu Item Cost Tier Interface
- Financial Form Interface
- Forecast Interface
- History Interface
- Budget Interface
After the upload interfaces are removed, customers will no longer be able to download upload templates, upload completed template files, or insert new data through these upload interfaces. This may also affect reports, custom reports, scheduled reports, exports, iQuery workbooks, or operational workflows that depend on data uploaded through these interfaces.
Data that was uploaded before the removal date will be retained according to each customer’s contracted data retention limits.
Does this impact me? This impacts customers who use upload interfaces to import supplemental data into Reporting and Analytics, including menu item cost tier data, financial form data, forecast data, historical data, or budget data.
This may also impact customers who use reports, custom reports, scheduled reports, exports, iQuery workbooks, or business processes that depend on data loaded through those upload interfaces.
This does not impact customers who do not use upload interfaces and templates or reports based on uploaded data.
Next steps: Before the effective date, review your use of upload interfaces and identify affected upload workflows, reports, custom reports, scheduled reports, exports, iQuery workbooks, and operational procedures.
Customers should plan to transition affected business processes to non-Oracle workflows or customer-managed alternatives before the effective date. Oracle Restaurants does not provide a replacement application for the upload interfaces and templates.