The following tables list all field-mapping templates that support each master data business object. Each business object can be supported by more than one field-mapping template. You can edit the delivered business flows to include or exclude business objects by selecting the corresponding field-mapping templates or also create your own if these templates don't fit your needs. For a detailed list of the fields mapped in each template, see Appendix B: Fields Supported in Mapping Templates.
When P6 is the source provider, select the following field-mapping templates to transfer each business object in the Master Data flow type:
P6 Source Business Objects | Associated Field-Mapping Templates | Used In Business Flow |
|---|---|---|
Calendar | Send P6 calendar data to Primavera Cloud |
This flow sends resources and roles at the same time.
If a role does not exist, then it is created. |
EPS | Create P6 EPS in Primavera Cloud as EPS Code | Create EPS Code in Primavera Cloud |
Location | Send P6 locations to Primavera Cloud | None |
Resource | Send Primavera Cloud resources to P6 | None |
Send P6 resources to Primavera Cloud |
Note: Primavera Cloud does not support multiple roles or resources with identical names. | |
Role | Sync role data for Primavera Cloud |
If a resource does not exist, then it is created. |
Send Primavera Cloud role to P6 | None | |
UDFType | Create P6 UDF fields in Primavera Cloud | None |
When Primavera Cloud is the source provider, select the following field-mapping templates to transfer each business object in the Master Data flow type:
Primavera Cloud Source Business Objects | Associated Field-Mapping Templates | Used In Business Flow |
|---|---|---|
ProjectCode | Create Workspace structure in P6 as Primavera Cloud Workspace code | Create Workspace Code in P6 |
ProjectCodeType | Create Project Code Type Fields in P6 | Create Workspace Code in P6 |