About This Recipe

This recipe integrates Oracle MICROS Reporting and Analytics with Oracle Autonomous Transaction Processing.

This is a scheduled integration recipe that extracts sales and dimensions data from Oracle MICROS Reporting and Analytics using its Business Intelligence APIs and imports the data into Oracle Autonomous Transaction Processing.

For the purpose of the recipe integration, sample tables are created in Oracle Autonomous Transaction Processing and the integration is configured to run SQL statements based on those tables. See Support note Supplemental Code for Oracle MICROS – ATP – Accounting Hub Oracle Integration Cloud Recipes for the SQL scripts that you must run to create the tables. Note that the recipe can be extended to extract any available data points from Reporting and Analytics, with the integration adapter configuration and mapping updated accordingly.

To use the recipe, you must install the recipe and configure the connections and other resources within it.

The recipe contains three integration flows:

Oracle MICROS RnA to ATP Export Process: This integration calls Oracle MICROS RnA Dimensions to ATP and Oracle MICROS RnA Sales to ATP to be executed consecutively. It acts as a scheduler integration.
Oracle MICROS RnA Dimensions to ATP: This integration fetches all the location information from Reporting and Analytics and inserts it into a dimensions table in ATP. Then, for each location, it inserts all the location dimension details (Tender Media Dimensions, Service Charge Dimensions, Order Type Dimensions, Discount Dimensions, Revenue Center Dimensions, Menu Item Dimensions, and Tax Dimensions) into the corresponding tables in ATP. For the list of tables, see Configure Oracle Autonomous Transaction Processing.
Oracle MICROS RnA Sales to ATP: This integration fetches all the location dimensions from Reporting and Analytics. Then, for each location, it gets the latest business date and for that particular date, inserts sales and operational data (Menu Item Daily Totals, Service Charge Daily Totals, Tax Daily Totals, Tender Media Daily Totals, and Discount Daily Totals) into the corresponding tables in ATP. For the list of tables, see Configure Oracle Autonomous Transaction Processing.

Assumptions

You have created all the tables for the dimensions, and sales and operational data, as described in Support note Supplemental Code for Oracle MICROS – ATP – Accounting Hub Oracle Integration Cloud Recipes.
The table and view names are used as defined in Supplemental Code for Oracle MICROS – ATP – Accounting Hub Oracle Integration Cloud Recipes. If any change is made to the table or view names, you must modify the connector configuration in the integration accordingly.
Recipe integration includes only sample error handling and notifications. Robust error handling based on customer needs must be implemented by the recipe consumer.
The recipe include a set of chosen dimensions, and sales and operational data points to enable the Oracle Financials integration. Recipe consumers can choose to extend the recipe by using additional API invokes, which means that corresponding ATP tables must be added/modified accordingly.

System and Access Requirements

Oracle Integration, Version 22.1.3.0.0 or higher
- An account in Oracle Integration with the Service Invoker role to configure the recipe
Oracle Autonomous Transaction Processing, Version 19c
Oracle MICROS Reporting and Analytics, Version 20.1 or higher
- Oracle MICROS Simphony Cloud Service, Business Intelligence Interface (BI API)