About This Accelerator

Overview

This accelerator integrates Oracle Primavera Cloud resources, roles, rates, activities, assignments, and spreads with Primavera Unifier on an event-driven basis based on the data received in the request.

The accelerator delivers a project that includes three integrations:

Oracle OPC Unifier Resources Roles Sync
Oracle OPC Unifier Activity Sync
Oracle OPC Unifier Activity and Assignment Spreads

The Oracle OPC Unifier Resources Roles Sync integration is used to integrate resources, roles, and rates, while the Oracle OPC Unifier Activity Sync and Oracle OPC Unifier Activity and Assignment Spreads integrations are used together to integrate activities, assignments, and spreads.

To use this accelerator, you run the Oracle OPC Unifier Resources Roles Sync integration first, and then run the Oracle OPC Unifier Activity Sync integration second.

The Oracle OPC Unifier Activity Sync integration is dependent on the Oracle OPC Unifier Resources Roles Sync integration; therefore, you should wait until after the Oracle OPC Unifier Resources Roles Sync integration has finished running (after the resources, roles, and rates have been integrated) before you run the Oracle OPC Unifier Activity Sync integration. The third integration listed above (labeled Oracle OPC Unifier Activity and Assignment Spreads) is called automatically, after the activities and assignments from the Oracle OPC Unifier Activity Sync integration have been integrated.

These application integrations use the standard REST Adapter and the Oracle Primavera Cloud Adapter available in the Integration Store.

To use these integrations, you need to install the accelerator and configure the connections and other resources. Then, activate and run the integrations using the Oracle Integration interface or REST API.

Integration Workflows

The following sections contain high-level explanations about how the main integrations in this accelerator work.

Integrate Resources, Roles, and Rates

The following is a high-level explanation about how resources, roles, and rates are created or updated in Primavera Unifier from Oracle Primavera Cloud.

The integration is triggered by a request sent to the integration deployed in Oracle Integration. (For information about how to structure your request, see Activate and Run the Accelerator.)
If the request includes a valid unifierJobId, Oracle Integration notifies Primavera Unifier that the synchronization process has begun, which helps track the status of the synchronization task.
Oracle Integration calls Oracle Primavera Cloud to retrieve the necessary data. The key data elements include:
- Workspace
- Currency
- Resources
- Roles
The resources and roles data is then created or updated in Primavera Unifier by matching with the Primavera Unifier workspaces.
If the unifierJobId was provided, Oracle Integration sends a final notification to Primavera Unifier confirming that the synchronization job has ended successfully.

Note:

The Workspace code of the parent and child Resource/Role codes should be the same in order to integrate them into Primavera Unifier.
If the Resource Id for the parent Workspace code is updated in Oracle Primavera Cloud, then the whole hierarchy has to be removed and recreated in Primavera Unifier.
Each Resource/Role supports only one work rate value – specifically, the pricePerUnit1 rate. This limitation exists because Primavera Unifier does not allow multiple work rates under the same cost and rate type.

Integrate Activities, Assignments, and Spreads

The following is a high-level explanation about how activities, assignments, and spreads are created or updated in Primavera Unifier from Oracle Primavera Cloud.

The integration is triggered when a request is sent to an integration in Oracle Integration. This request contains information about the data that should be created or updated in Primavera Unifier. (For information about how to structure your request, see Activate and Run the Accelerator.)
If the request includes a valid unifierJobId, Oracle Integration notifies Primavera Unifier that the synchronization process has begun, which helps track the status of the synchronization task.
Oracle Integration calls Oracle Primavera Cloud to retrieve data for the specified project. This includes:
- Activities and their dependencies (relationships)
- Assignments
- Work Breakdown Structure (WBS) objects
- Spreads:
  - The spread synchronization uses a dedicated integration process (Oracle OPC Unifier Activity and Assignment Spreads).
  - In this process, activity and assignment spreads are first downloaded from Oracle Primavera Cloud, then uploaded to Primavera Unifier.
  - If both processes complete successfully, Oracle Integration triggers a project recosting of the current system activity sheet data.
The project and its associated data is then created or updated in Primavera Unifier by creating a matching Primavera Unifier project. If baseline synchronization is specified in the request, this data will also be created or updated during the process.
If the unifierJobId was provided, Oracle Integration sends a final notification to Primavera Unifier confirming that the synchronization job has ended successfully.