Gateway developers and Gateway administrators can access and view all the parameters listed below. Set the behavior of these parameters in the business flow wizard by specifying the Attribute for each as any of the following values: Hidden, Optional, Read-only, or Required.
Note: Data identified by each parameter is processed by a flow step of the business flow. For more information on flow steps, see Executing a Business Flow. All values specified in the filter parameters will be used in the Load step of the flow for loading data from the providers designated as the source or the destination.
Source Application Default Parameters
The following provider application parameters display for a P6 deployment designated as the source application in a project data flow. Gateway developers and Gateway administrators can access and view all parameters listed below. Set values and attributes for the following parameters:
- P6 Filter
Use this setting to identify and select projects in P6 using Lookup in P6, Project Ids, EPS Ids, Project Code, Project Code Type Name, or Project Code Value.
Note: Lookup in P6 option is available only to Gateway users and administrators for synchronizations only.
Select projects by:
- Entering multiple values for Project Id and Project Code as comma-separated values
- Entering multiple values for EPS Id as comma-separated values or
- Entering multiple Project Codes with values in the following format:Type Name = Value Name.
For example:
- In the Fields list, select Project Code.
- In the Value list, enter: Integrate to P6 = Yes, and then select Add Row.
To specify a second condition for Project Code:
- In the Fields list, select Project Code.
- In the Value list, enter Sales Country Code = DE, and then select Add Row.
- Baseline
Use this setting to select the type of baseline to be created in Unifier or migrate P6 data. Options include: No Baseline, Baseline Names, Project Baseline, and All Baseline. This parameter is specific to a Unifier - P6 integration only. This information is used in the Load step of the flow.
- Activity Filter
Use this setting to identify and select projects in P6 by using Activity Ids, Activity Status, Activity Type, and Activity Code. Enter multiple values as comma-separated values. Select Add Row to enter multiple filter criteria for selecting activities. Select Edit Row to change the current filter criteria or value for selecting activities.
- Resource Assignment Filter
Use this setting to select ResourceAssignments in P6 using Resource Ids or Resource Type. Enter multiple values as comma-separated values. Select Add Row to enter multiple filter criteria for selecting resource assignments. Select Edit Row to change the current filter criteria or value for selecting resource assignments.
- Summarize project(s) before synchronization?
Use this setting to determine whether to summarize projects before a synchronization. This information is used in the Load step of the flow.
- Spread Period type
Use this setting to select the default spread period type in P6 EPPM. Options include: Week, Month, Day, and Financial Period. This information is used in the Load step of the flow.
- Synchronize WBS Hierarchy
Use this setting to determine to what extent you would like to synchronize the WBS hierarchy in P6. Options include: Complete, Partial, or Levels. The P6 WBS setting in P6 will override the Gateway setting.
Destination Application Default Parameters
The following provider application parameters display for a P6 deployment designated as the destination application in a project data flow. Users with Gateway administrator roles can access and view all parameters listed below. Set values and attributes for the following parameters:
Note: Unless specified in parentheses, all parameters listed below are hidden from a non-administration user.
- EPS Location
Use this setting to specify the EPS node where the project should be created in the destination P6. This information is used in the Load and Save steps of the flow.
- Copy from Existing Project or Template
Use this setting when you want to add project data in P6 by copying data from another existing project or project template in P6.
If the project did not previously exist in the P6, it is first created from the project or template, and the data from the source application is then sent to P6 to create additional project data using the field-mapping templates included in the business flow.
For existing projects in P6, this parameter is ignored. Data from the source application is sent to P6 to create the project using only the field-mapping templates included in the business flow.
- Resource Destination
Use this setting to specify the location of the Resource objects imported into P6.
- Role Destination
Use this setting to specify the location of the role objects imported into P6. This information is used in the Save step of the flow.
- Calculate Costs from Units
Use this setting to determine whether to calculate costs from the units. This information is used in the Save step of the flow.
- Auto Compute Actuals
Select this setting if you want the actuals to be auto-computed in P6. This information is used in the Save step of the flow.
- Schedule project(s) after synchronization?
Use this setting to determine whether to schedule projects after a synchronization. This information is used in the Save step of the flow.
- Summarize project(s) after synchronization?
Use this setting to determine whether to summarize projects after a synchronization. This information is used in the Save step of the flow.
- Save data to P6 if there are errors
Use this setting to determine whether to save the imported data in P6 with errors. This information is used in the Save step of the flow.
- Provide email notification for selected job status
This parameter displays only when you have specified an Email Address in the Mail Configuration tab of the Gateway Settings page.
Use this setting to enter email IDs of individuals who would need to be notified when synchronization jobs are completed with any of the following job statuses on the Monitoring page: Completed, Review, Cancelled, Completed with Errors, Completed with Warnings, or Failed.
Select the Attach Data Details for Job check box to include details of the data transfer in the email.
- Synchronize one project at a time
A synchronization job is usually split into multiple child jobs with each child job transferring data in each project. By default all child jobs are executed simultaneously. Use this setting to determine whether to synchronize data one project at a time.
- Delete data that no longer exists in the source application?
Use this setting to determine whether data that no longer exists in the source application is to be deleted in the destination application. This parameter must be used in conjunction with the Compare flag selected in the Business Flow wizard.
Note: When you run a project data flow, it will delete only project level data in a business flow, but not the master data. This will prevent you from deleting master data elements such as resources, roles etc., that may be used in another project. However, if used in a master data flow, it will delete all relevant objects and fields.
- Only delete data that has been linked previously with the source application?
To use this parameter, you must also select the parameter, Delete data that no longer exists in the source application? During a synchronization, when the data is compared between the source and the destination application, data that has been added only in the destination application will not be deleted. However, if you deleted source data that was previously synced in the destination application, it will also be deleted from the destination application.
- Partition data to child jobs for large data transfers?
Use this setting if you are integrating large data sets between projects and between applications when P6 EPPM or Oracle Primavera Cloudis the source application. This parameter partitions large data sets logically into multiple child jobs.
- Child job object limit for partitioned data
Use this setting in conjunction with the Partition Data into Child Jobs? parameter. Enter a limit on the number of objects that can be included in the child jobs in the range 50 - 5000. Zero (0) is the default value.