Integration Workflows

The following sections describe the main behavior at a high level.

Note:

For exact request payloads and run steps, see Activate and Run the Accelerator.

Integrate Resources, Roles, and Rates

Creates or updates resources, roles, and work rates in the Primavera Unifier Master Rate Sheet.

  1. A request triggers the integration in Oracle Integration.
  2. If the request was triggered from the Primavera Unifier user interface (includes a valid unifierJobId), Oracle Integration publishes a "job started" status to Primavera Unifier.

  3. Oracle Integration retrieves the required data from Oracle Primavera Cloud to retrieve the necessary data:

    • workspace details
    • currency details
    • resources and roles
  4. Oracle Integration creates/updates records in the Primavera Unifier Master Rate Sheet by matching them to the source system, Oracle Primavera Cloud.

  5. If the request was triggered from the Primavera Unifier user interface, Oracle Integration publishes a "job completed" status to Primavera Unifier.

    If an error occurs, Primavera Unifier receives a "failed" status with the message returned by the job tracking service.

Note:

  • Hierarchy must stay within one workspace: Parent/child resource and role structures must remain within the same Oracle Primavera Cloud workspace.
  • Resource ID changes are disruptive: If a resource ID changes in Oracle Primavera Cloud, the hierarchy typically must be removed and recreated in Primavera Unifier.
  • One work rate per resource/role: Only a single rate value is synchronized (specifically pricePerUnit1) due to Primavera Unifier Master Rate Sheet limitations.
  • Work rate updates are limited: Primavera Unifier does not apply new or updated work rate entries for an existing resource/role in the Master Rate Sheet through the available APIs. In practice, only the initial rate remains visible.

Integrate Activities, Assignments, and Spreads

Creates or updates WBS, activities, assignments, and (optionally) baseline data in Primavera Unifier. Spreads are processed by a dedicated integration after schedule data is in place.

  1. A request triggers the integration in Oracle Integration and identifies:

    • the Oracle Primavera Cloud project to read from
    • the Primavera Unifier project to update
  2. If the request was triggered from the Primavera Unifier user interface (includes a valid unifierJobId), Oracle Integration publishes a "job started" status to Primavera Unifier.

  3. Oracle Integration retrieves the following schedule data from Oracle Primavera Cloud:

    • work breakdown structure (WBS)
    • activities (including activity dependencies - relationships)
    • assignments
    • baseline data (only when baseline synchronization is requested)
  4. Oracle Integration creates/updates schedule records in Primavera Unifier.

  5. The Oracle OPC Unifier Activity and Assignment Spreads integration is invoked:

    • spreads are uploaded into Primavera Unifier
    • project recosting is triggered

  6. If the request was triggered from the Primavera Unifier user interface, Oracle Integration publishes a "job completed" status to Primavera Unifier.

    If an error occurs, Primavera Unifier receives a "failed" status with the message returned by the job tracking service.

Note:

  • Workspace alignment matters: Use the same workspace code and workspace name in Oracle Primavera Cloud to avoid mapping issues.
  • Resource/role assignment scope: Resources and roles created under an Oracle Primavera Cloud project workspace can only be assigned within that project.
  • Resource/role relationships are not synchronized: Primavera Unifier does not maintain a relationship between a resource and its roles. If an activity assignment in Oracle Primavera Cloud includes both a resource and a role, the integration syncs the resource assignment and does not sync the role as an implicit role of that resource.
    • To sync a role to an activity, assign the role as a separate assignment in Oracle Primavera Cloud.

  • Baseline naming rules (Oracle Primavera Cloud):

    • baseline project name and current project name cannot be identical
    • baseline project names should be unique across all projects