Process Description for Integrating EPM Planning Projects and Project Management

Data Integration provides an out of the box solution that enables customers to apply predefined mappings for the two way integration between EPM Planning Projects and Project Management.

Customers can customize and extend these integrations, for example, when they need to use a different calendar to the business unit other than the default project accounting calendar from the primary ledger calendar.

You must be assigned a Service Administrator role to perform most of the tasks below. For more information about EPM roles, see Understanding Predefined Roles.

At a high level, here are the steps for integrating EPM Planning Projects and Project Management:

1. Enable EPM Planning and complete any setup and configuration requirements in EPM Planning Projects.

   For detailed steps on setting up and performing the integration, see Integrating EPM Planning Projects and Project Management.

2. Assign security privileges and job roles required to use the feature.

   This step requires that you have been assigned BI Publisher privileges and Projects and Budgets File-Based Data Import Processes security roles.

   For more information, see Security Role Requirements for EPM Cloud to Project Management Integrations.

3. In Data Management, select the Source System and complete the following:

   1. Add Project Management as a source system and identify the application type as Oracle ERP Cloud.

   2. Configure and then test the source connection.

      This step requires that you specify the connection information to the Oracle ERP Cloud including the user name, password, and Services URL.

      The test connection part of this step fails when the user has been assigned only Project Management roles but has not been provisioned for GL integration roles. However, integrations run with only Project Management roles.

      For information on GL integration roles, see Security Role Requirements for Oracle ERP Cloud Integrations.

4. Register the primary EPM Planning Projects application with an OEP_PFP input cube or All Input Cubes.

   For more information, see Registering the EPM Planning Projects Application.

5. In Application Details for the primary EPM Planning Projects application, verify that the Project, Project Element, and Resource Class dimensions have been categorized to the appropriate dimension classifications.

   For more information, see Classifying Project Dimensions in the EPM Planning Projects Application.

6. Register the Reporting plan type application with the PFP_REP cube as an application.

   For more information, see Register the Reporting Type Application.

7. Register the Dimension applications.

   Only the Entity and Custom dimensions are mandatory. Other dimension types, such as the Account, Scenario, and Version can be optionally deleted after the registration.

   For more information, see Registering the Dimensions Application.

8. On the Application page, verify that the list of applications includes the following:

   1. Primary EPM Planning Projects
   2. Reporting Type
   3. Dimension

   If any of the above applications have not been registered, the initialization of the integration fails.

9. On the Application page, click to the right of the primary EPM Planning Projects application, and then select Initialize Integration.

10. On the Initialize Integration page, select the Project Portfolio Management (PPM) initialization type, connection to the Oracle ERP Cloud, and any prefix used to designate an integration iteration.

    For more information, see Initializing the Integration.

    This process creates all out of the box integration definitions required to integrate the EPM Planning Projects and Project Management including:

    • Export Project Budgets

    • Export Projects

    • Exported Project Status Sync

    • Import Project Actuals

    • Import Project Budgets

    • Import Project Organizations

    • Import Projects

    • Imported Project Status Sync

    For a description of the integration definitions created after the initialization, see Integration Definition Reference.

11. If the application has multiple integration definitions, define the required mapping for the following integration definitions:

    • Exported Project Status Sync

    • Export Project Budgets

    • Import Actuals

    • Import Budgets

    • Import Project Properties

    For more information, see: Post Initialization Mappings

12. If the application has additional custom dimensions, define the required mapping for these dimensions on the Map Dimensions page in Data Integration.

    For more information, see Mapping Custom Dimensions.

13. Add period mappings to define the period and years relationships between EPM Planning Projects and Project Management during the integration.

    By default, period mappings between EPM Planning Projects and Project Management are set up automatically during the application creation. For the integration, both EPM Planning Projects and Project Management use the default calendars set up in Period Mappings defined in Data Management.

    If you need to add or modify a period mapping, you can customize period mappings using the Application mapping and Source mapping options defined in Data Management. Period mappings can be defined at two levels:

    • Application period mappings are used to define any special period mapping used in the export of budgets to Project Management. For more information, see Defining Application Mappings.

    • Source period mappings are required to create calendar period mappings for actuals and budgets in EPM Planning Projects and Project Management. For more information, see Applying Source Mappings.