Integration Overview

Integration is a bi-directional movement of data between Primavera Cloud and external applications. During integration, business objects and their data fields are transferred between applications. Field mapping templates list the objects and fields to be transferred and how they should be mapped from fields in the source application to fields in the destination application. A business flow is a specific set of field mapping templates that fulfill a particular data transfer requirement. The data contained in a business flow is transferred by running the business flow from the Synchronize page of the workspace or project-level Integration app. You can run the business flows on demand or schedule them to run at regular intervals.

A variety of integration solutions enable you to synchronize and share data between Oracle Primavera Cloud and external applications. You can create new projects using existing P6 EPPM or Microsoft Project data, or use Primavera Gateway to define your own business flows for integration with other external sources. There are two integration methods that you can use:

Direct Integration: The direct integration method requires minimal configuration to set up and provides default business flows to support the most common data migration requirements. Use this method if your organization does not require additional customization. Direct integration is performed from within Primavera Cloud.
Integration using Primavera Gateway: Use this method if your organization requires customized solutions beyond the default options provided by Primavera Cloud. Primavera Gateway provides you an option to create new business flows if the available flows don't fit your needs. You can also use Primavera Gateway to create connections to P6 and Primavera Cloud. After these connections are established, you can run synchronizations from Primavera Gateway. You can also add the synchronizations from Primavera Gateway to your Primavera Cloud deployment and run the synchronizations from Primavera Cloud.
Consult the Primavera Gateway documentation for a comprehensive selection of Gateway information including user administration, end user help documentation, custom business flow and synchronization configurations, connecting P6 and Primavera Cloud applications, and transferring data between P6 and Primavera Cloud. The use of Gateway requires a Gateway license.

After your Gateway deployment is connected to P6 and Primavera Cloud and you have created the necessary business flows and synchronizations, you can add and run the synchronizations from Primavera Cloud. See the Integrate Gateway section of the Primavera Cloud Help for more information

Initial Configuration Considerations

If you are configuring Primavera Cloud integration for the first time, it may take up to 14 days to set everything up and get it running. This assumption is based on whether the system you are integrating with is on the cloud or on-premises and whether you are using Secure Socket Layer (SSL). The process may take time as it may involve adding ports and URLs to the allowlist. These ports and URLs are opened and on the allowlist as needed to keep the system secured for users.

Here are the various scenarios:

Using Primavera Gateway:
If Primavera Gateway is on the cloud then you may have to check if it is on Oracle Cloud or an external cloud. If it is on Oracle Cloud then it will be accessible. If it is on an external cloud, contact support.

If Primavera Gateway is on-premises, contact support to add the URL to the allowlist.
Using Oracle Primavera Cloud:
If P6 EPPM is on the cloud then you may have to check and see if it is on Oracle Cloud or an external cloud. This will have to be handled differently based on the cloud hosting the P6 environment. Contact support in either case.

If P6 EPPM is on-premises, contact support to add the URL to the allowlist.
Using SSL:
This requires extra steps to import certificates and therefore adds time to the process of adding the URL to the allowlist. Contact support to enable SSL.

Key Features

Connection: A connection is set up between the source and destination application to integrate data.
Field Mapping Template: A field mapping template lists the objects and fields to be transferred and how they should be mapped from fields in the source application to fields in the destination application.
Business Flow: A business flow is a combination of one or more field mapping templates containing one or more business objects and fields that fulfills a particular data transfer requirement.
Synchronization: Data is transferred between the source and destination application using synchronization. Each synchronization relies on a business flow to transfer the data from the source application to the destination application.

Next: Get Started With Integration