Run the Integrations

After activating the integrations, you can then run them.

These instructions describe how to run the integrations using the OIC interface:

If you want to run the integrations using REST, see:

Run 'Oracle P6 Unifier Resources Roles Sync'

Note:

Run this integration first. The Activities Sync depends on resources/roles/rates being present in Unifier. Activate this integration and complete one successful run before running the schedule sync.
  1. In the Integrations section of the project workspace, click Actions Actions icon next to the integration, then select Run.
  2. On the Configure and run page, in the Request section, click the Body tab to enter the required JSON payload.
  3. Click Run and watch the Activity Stream / Tracking to verify success.

Request payload (example) 

{
        "p6FilterExpressions": {
        "resources": "Id LIKE 'WS-%' AND ResourceType != 'NonLabor'",
        "roles": "Id LIKE 'WS-%'"
        },
        "unifierJobId": "123456"
        }
Element Required Data Type Description
p6FilterExpressions.resources Yes String P6 filter to limit Resources. If omitted/empty, all accessible resources are synced.
p6FilterExpressions.roles Yes String P6 filter to limit Roles. If omitted/empty, all accessible roles are synced.
unifierJobId No String Optional correlation ID for Primavera Unifier job tracking (if launched from Unifier).

About P6 Filters

Filters follow Oracle Primavera P6 EPPM Web Services syntax. See Using Filters in the Oracle Primavera P6 EPPM Web Services Programming Guide for examples and allowed operators/fields.

Run 'Oracle P6 Unifier Activities Sync' (WBS, Activities, Assignments)

Prerequisite: Run Resources & Roles Sync successfully first.

You can run the Activities sync in two ways: either manually or by schedule.

Option A - Direct Trigger (HTTP POST) (recommended for ad‑hoc runs)

  1. In the Integrations section of the project workspace, click Actions on the integration, then select Run.
  2. On the Configure and run page, in the Request section, click the Body tab to enter the required JSON payload.
  3. Click Run and watch the Activity Stream / Tracking to verify success.

Request payload (example)

{
  "unifierJobId": "B80A18356A44D61",
  "synchronizeBaselineProjects": false,
  "p6_project_id": "P6UniTest1",
  "removeUnreferencedData": true,
  "unifierProjectNumber": "UniP6Project"
}
Element Required Data Type Description
p6_project_id Yes String Primavera P6 EPPM project identifier to sync from (use the P6 Project ID used by your environment).
synchronizeBaselineProjects No Boolean When true, also create/update the current baseline from Primavera P6 EPPM in Primavera Unifier. Default: false.
unifierProjectNumber Yes String Target Primavera Unifier project/shell identifier number to sync to.
removeUnreferencedData No Boolean When true, delete Primavera Unifier WBS/activities/assignments not present in Primavera P6 EPPM (full refresh). Default: false.

Option B - Oracle P6 Unifier Activities Sync Scheduler (preferred for recurring, unattended runs)

  1. In the Integrations section of the project workspace, click Actions Actions icon next to the scheduled integration, then select Run (first‑time parameterization)
    • Select Add Schedule to set the recurrence interval.
  2. For the first time parameterization set the Request type as Ad hoc request.
  3. Provide the same payload fields as the direct trigger (the scheduler passes them through to the underlying Activities Sync):
    • P6-ProjectId - p6_project_id (required)
    • synchronizeProjectBaselines - synchronizeBaselineProjects (optional)
    • Unifier-ProjectNumber - unifierProjectNumber (required)
    • removeUnreferencedDataInUnifier - removeUnreferencedData (optional)
  4. Click Run and watch the Activity Stream / Tracking to verify success. If the schedule was also set, the scheduler will now trigger the Activities Sync at the configured cadence.

Run 'Oracle Unifier P6 Activity Actuals Sync'

  1. In the Integrations section of the project workspace, click Actions Actions icon next to the integration, then select Run.
  2. On the Configure and run page, in the Request section, click the Body tab to enter the required JSON payload.
  3. Click Run and watch the Activity Stream / Tracking to verify success.

Request payload (example)

{
  "unifierJobId": "06620F000DE58EA",
  "p6_project_id": "TestProjRa",
  "unifierProjectNumber": "DevTestLocalSec",
  "env_label": "Development"
}
Element Required Data Type Description
p6_project_id Yes String Primavera P6 EPPM project identifier to apply actuals to.
unifierProjectNumber Yes String Primavera Unifier project/shell that is the source of the actuals.
unifierJobId No String Optional correlation ID for Primavera Unifier job tracking (if launched from Primavera Unifier).

Note:

The env_label parameter in the request payload example above is an optional parameter that is not used in the integration. It is an internal parameter that is used to label whether the environment is development, testing, or production.

Run the Integrations via REST

Use this method if you prefer to invoke integrations through REST instead of the Oracle Integration user interface.
  1. In the Integrations section of the project workspace, click Actions on the integration flow, then select Run.
  2. On the Configure and run section, open the Endpoint Metadata.
  3. Copy the Endpoint URL and review the Resource information (HTTP method, request/response schemas). Use this with your REST client (Postman/curl). Oracle also supports publishing OpenAPI documents for REST-triggered integrations for easy client import.