Configuring CBS Shell Types with Oracle Integration for P6 System Activity Sheets

Company Administrators and Shell Administrators can configure Oracle Integration as the default integration engine for specific projects in single shells of CBS shell type. This ensures all system actions and integrations consistently follow the selected engine, supporting Oracle’s transition to Oracle Integration and removing ambiguity from integration paths.

Benefits

• Clear Engine Selection: Administrators can explicitly select the integration engine for each project, preventing misconfiguration and ensuring systems route integration requests to the correct platform.
• Simplified Management: Configuration and migration steps are visible and straightforward, reducing ambiguity over which integration path is active.
• Confirmation on Migration: Built-in confirmation dialog boxes to switch engines help avoid accidental data or configuration loss.
• Consistent Schema: No changes to field names or data types when switching engines means existing reports and workflows.
• Enhanced Auditing: Each integration run is recorded with engine details, status, and user activity, supporting efficient troubleshooting and compliance tracking.
• Unambiguous routing ensures all system activity for the project uses only the chosen integration engine.
• No disruption to existing reports or mobile applications.

Limitations

• Only one engine can be selected per project. Fallback is not supported.
• If Oracle Integration prerequisites are not met, action is blocked until resolved.
• Prior Primavera Gateway configuration is deleted when switching to Oracle Integration.

Prerequisites

• Oracle Integration is enabled at the company level as the integration engine as outlined in the Initial Oracle Integration Setup.
• You have the required permissions to set up P6 schedule integrations as an administrator.
• Existing Primavera Gateway integrations are removed upon switching to Oracle Integration. Be aware of business and technical impacts.

Procedure

To set up Oracle Integration as the default integration engine of choice in single shells of CBS shell type for P6 System Activity Sheets:

1. Go to the Company Workspace tab, and switch to Admin mode.
2. In the left Navigator, go to the targeted shell node.
   For example, select the Vision Corporation tab.
3. In the <Shell_Name> log (right pane), select the applicable single shell and then select Open from the gear menu.
4. 4. On the Shell’s landing page, from the My Dashboard menu, select Details, and then select the Integration tab.
   The Integration tab displays only those projects that are configured to use Oracle Integration as the default integration engine.
5. If you choose to migrate one or more projects that are already configured with Primavera Gateway integration, they will be migrated to use Oracle Integration by default when you select the Integration tab. A confirmation dialog box displays indicating that these projects will be migrated to Oracle Integration as the default integration engine.
   • • Select Yes to migrate projects to use Oracle Integration. The projects listed in the Gateway Integration tab are relocated to the Integration tab.
   • Select No to retain the projects configured with Primavera Gateway integration.
6. To configure additional projects (in the same shell) in the Integration tab:
   1. a. From the Add menu, select P6 Schedule from the following options:
      • Primavera Cloud Cash Flow
      • Primavera Cloud Schedule
      • P6 Schedule

      Note:

      In the Integration tab, you can select only one source for schedule: Primavera Cloud Schedule or P6 Schedule.
   2. Enter the following project details:
      1. Project ID: Enter the unique alphanumeric project ID available in this shell.
      2. Project Name: Displays the project name associated with the Project ID.
      3. Primavera Cloud Workspace ID: Displays the Workspace ID in Primavera Cloud only if you chose Primavera Cloud Schedule or Primavera Cloud Cash Flow. This field is not applicable if you chose P6 Schedule (step 6a).
      4. Integration Type: Displays the integration source you selected from the Add menu (step 6a).
   3. 
      
7. Repeat the previous step to set up multiple projects with Oracle Integration for P6 System Activity Sheets.
8. To confirm all the above changes, select Save.
9. Ensure the required Oracle Integration mappings are set up for each Activity Sheet before attempting Get/Send calls.
10. Validate changes by checking audit logs (engine, job ID/status, project name, schedule type, timestamp, actor are logged for each run).
11. If required, proceed to configure shell templates with Oracle Integration engine enabled for P6 System Activity Sheets as outlined in Configuring Oracle Integration for P6 System Activity Sheets in Shell Templates.

Alternative Method

You can also configure shells to use Oracle Integration as the default engine using the Update Shell REST endpoint.