1. Administering Planning Modules
  2. Followup Administrative Tasks
  3. Pushing Data Using Data Maps
  4. Pushing Data to Integrate Business Processes

Pushing Data to Integrate Business Processes

Perform this task if you enabled and configured integration between Financials, Workforce, Projects, and Capital as described in Integration Scenarios and Workflow. As users prepare plans and forecasts, when they are ready to move data, administrators must push data using the predefined data maps.

Table 9-3 Data Maps for Integration

Integration Scenario Description/Planner Action Administrator Rule/Data Map to Run

Projects to Financials

When a planner rolls up the Projects cube (using the rules OPF_Rollup Projects and Rollup Project Cube), the data is moved to Financials.

Not required.
Projects to Capital

When a planner saves the form Project Capitalization, the data is moved to Capital.

To see asset usage in Capital, a planner adds equipment costs in Projects, runs the Calculate Project rule and then the Roll up Capital rule.

Not required.
Projects to Workforce

When a planner runs the rule Calculate Expenses for a project with driver-based labor, the data is moved to Workforce for use in the utilization calculation.

In Workforce, the planner must run the Aggregate rule.

Not required.
Workforce to Financials

Data is moved when compensation data or non compensation data is calculated and the planner runs the Synchronize rule.

In Data Maps, select Compensation Data to Financial Statement or Non Compensation Data to Financial Statement, then Push Data, and then click Yes to confirm the option to clear the data.

If you are pushing non-compensation data, see Pushing Non-Compensation Data from Workforce to Financials Using Data Maps with Detailed Member-Level Mappings and Smart Push.

If you are using your own chart of accounts in Financials, or if you want more flexibility in mapping Salary and Merit, you can customize the mappings. See Customizing the Mapping for Integration between Workforce and Financials.

Workforce provides Groovy rules for administrators to execute these data maps. See Workforce Groovy Rules.

Capital to Financials Data is moved when a planner adds an asset and runs Calculate Assets. Data is also moved when a planner transfers assets.

  • In the Configure page for Capital, select Map Capital Accounts to Financials, and then from the Actions menu, select Synchronize.

  • In Data Maps, select Financial Statement Integration, then Push Data and then click Yes to confirm the option to clear the data.

You can configure the system to push data in batches.

Pushing Non-Compensation Data from Workforce to Financials Using Data Maps with Detailed Member-Level Mappings and Smart Push

To push non-compensation data from Workforce to Financials, define detailed member-level mappings in the provided data map, Non Compensation Data to Financial Statement, to map account names in Workforce to account names in Financials to define where to push the data. Attach the modified data map to a form with Smart Push to push the data whenever you save changes on the form.

Overview of steps:

  1. Open the data map Non Compensation Data to Financial Statement in Data Maps and modify the detailed mappings to map account names in Workforce to account names in Financials.

    Tip: You can export the data map to Excel to make it easy to modify the detailed member-level mappings. Then, import the data map to Data Maps.

  2. Create a new form or modify an existing form in Workforce, such as Manage Non Compensation Expenses for All Employees.
    1. On the Layout tab, add Level 0 members to the rows for each non-compensation account you want to push to Financials.
    2. On the Smart Push tab, add OWP_Non Compensation Data to FinStmt and select Run After Save.

Now, whenever you update data on the form, after you save, Smart Push pushes the non-compensation data from Workforce to Financials.

Using detailed member level mappings along with Smart Push allows you to push non-compensation data between Workforce and Financials even if the member names don’t match.

Detailed member-level mappings currently work only with Smart Push on a form.

For more information, see the following topics:

Troubleshooting

For help with troubleshooting Smart Push, see Resolving Issues with Smart Push in Oracle Enterprise Performance Management Cloud Operations Guide.