1. Administering Data Integration for Oracle Enterprise Performance Management Cloud
  2. Integrating Data
  3. Integrating Account Reconciliation Data
  4. Loading Reconciliation Compliance Transactions
  5. Loading Reconciliation Compliance Transactions Process Description

Loading Reconciliation Compliance Transactions Process Description

At a high level, this is how you load Reconciliation Compliance Transactions to Account Reconciliation using Data Integration.

Note:

As a best practice recommendation while loading transactions through Data Integration , do not replicate your General Ledger or sub-ledgers in Account Reconciliation. Loading activity from your ERP is not a best practice for period end reconciliations. If you need to load more than a 100 transactions; then as an implementer, you need to ask more questions to better understand the customer's requirements. For a reviewer, a large number of transactions for period-end reconciliation would be difficult to review. Use cases with higher volumes of transactions are candidates for Transaction Matching and not Reconciliation Compliance.

To set up the load for Reconciliation Compliance Transactions in Data Integration:

  1. Create an Reconciliation Compliance Transactions application.

    See Registering a Reconciliation Compliance Transactions Application.

  2. Create an integration between the source and Reconciliation Compliance Transactions file and the target Reconciliation Compliance Transactions application.

    When creating the integrating, you also specify location information.

    See Creating a Reconciliation Compliance Transactions Integration.

  3. Map the dimensions between the source file to the dimensions in the Reconciliation Compliance Transactions application by building an import format.

    See Mapping Dimensions.

    The "Data" dimension is required when mapping dimensions. You must specify "All Data Type" instead of "Numeric Data," for example "Delimited – All Data Type."

  4. Map the "Data" and "Profile" dimension so that the system can create a mapping to pair intersections of data from the source to the target during the load.

    For the others dimensions, member mappings are not required when most attributes are mapped to the ATTR target dimension class. However, they are required when they are mapped to UD.

    See Mapping a Data Member for Reconciliation Compliance Transactions.

  5. Run the integration.

    See Running the Reconciliation Compliance Transactions Integration.