In Primavera Cloud the following codes and UDFs are supported at the object level:
Primavera Cloud Object Name | Code | UDF | Primavera Cloud as Source | Primavera Cloud as Destination |
|---|---|---|---|---|
Project | Yes | Yes | Yes | Yes |
Activity | Yes | Yes | Yes | Yes |
Resource | Yes | Not Supported | Yes | Yes |
WBS | Yes | Yes | Yes | Yes |
ResourceAssignment | Not Supported | Yes | Yes | Yes |
In Unifier, the following codes and UDFs are supported at the object level:
Unifier Object Name | Code | UDF | Unifier as Source | Unifier as Destination |
|---|---|---|---|---|
Project | add as field | add as field | Yes | Yes |
P6ActivitySheet | add as field | add as field | Yes | Yes |
Resource | add as field | add as field | Yes | Yes |
WBS | add as field | add as field | Yes | Yes |
Glossary
The following is a list of common Gateway terms used in this document.
B
Business Flow
A collection of business objects and their underlying supported fields selected for data transfer.
C
Cross-reference
A means for Gateway to track data being sent from the source application and received in the destination application. A cross-reference determines if the data is to be regarded as new data or an update to existing data in the destination application. If you delete or remove a cross-reference in Gateway, all history of data transfers is deleted within Gateway, although the data that was sent using this cross-reference will continue to exist in the destination application.
D
Deployment
The information required to connect to a specific database or an instance of an application from or to Gateway. For example, you may want to connect to two instances of a P6 EPPM application: Testing and Production from Gateway.
Destination Application
The application to which the data is being sent to.
F
Field Mapping Template
A template file which contains a list of fields mapped between the source application, Gateway, and the destination application for each business object. Gateway uses this file to determine how to populate data in the destination application. More than one field mapping template can be created for each business object. These template files are used by a business flow to transfer data during a synchronization run.
Flow Step
A business flow is an ordered sequence of flow steps where data is processed within each flow step. The success or failure of each flow step can be viewed from the Monitoring page of Primavera Gateway.
J
Job
A job number assigned in Gateway for each synchronization run to uniquely identify and monitor the data transfer.
M
Master Data
Master data is data that influences all subsequent data transfers between the source and destination applications. A destination application must be equipped with this data from the source application before sending or receiving data. For example, roles and resources are considered as master data for managing any project in an application and must be setup before any project data is transferred between applications.
Migration Data
Migration Data refers to a collection of master data and project data elements identified for a project in the source application for migration to a destination application. Gateway provides a Migration Data flow type for creating business flows to migrate data between applications. When you use this business flow, you will need to create your own migration data business flow and synchronization to migrate the data.
P
Project Data
Project data refers to data belonging to a project within the source application. Project data is sent to Gateway and then received in the destination application. These data elements influence only a specific project in an application.
S
Source Application
The application from which the data is being sent from.
Synchronization
A synchronization is a job that is executed to transfer data from a source application to a destination application. Gateway transfers data between two applications using synchronizations.