About This Recipe
This recipe integrates Oracle Autonomous Transaction Processing (ATP) with Oracle Financials Accounting Hub.
This is a scheduled integration recipe that reads the Oracle MICROS Reporting and Analytics (R&A) data stored in Oracle ATP, and imports the data into Accounting Hub to create accounting journals.
For this recipe, you'll create sample tables in Oracle Autonomous Transaction Processing (ATP) and configure Oracle Financials Accounting Hub to receive and store data 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 store and extract any available data points in ATP and Oracle Financials Accounting Hub, 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 one integration flow:
- Oracle ATP Sales to AH Journals: This scheduled integration fetches
data stored in ATP tables and generates Transaction header, line, and metadata files.
Subsequently, it compresses these files into zip archive and uploads them to Universal
Content Management (UCM) using ERP Integration Service. It then places a request to submit
the Oracle Enterprise Scheduler (ESS) job
Import Accounting Transactions(XLATXNIMPORT), which imports the data into Oracle Financials Accounting Hub.
Assumptions
- You have installed and run the Oracle MICROS R&A — Oracle ATP | Export Sales Data recipe on your Oracle Integration instance.
- You have created all the ATP tables and views for the sales data by running the SQL scripts provided 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.
- Both recipes 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 recipes by using additional data type invokes, which means that corresponding ATP tables and Accounting Hub configurations must be added/modified accordingly.