Note: Integration with P6 application applies to Unifier CBS type Shell only. The integration does not apply to the Unifier Project (Standard).
For details about the Activity Sheet, see Unifier Activity Manager and Master Rate Sheet.
Additional information about an Activity Sheet integrated with an external application
- It is required that an Activity Sheet to have the following fields as fixed columns:
- Activity ID
- Activity Name
Note: You cannot remove the two required fields from an Activity Sheet.
- When an Activity Sheet attribute form is deployed to Unifier for the first time, all fields present in the Activity Sheet attribute form are saved and displayed as columns in the Activity Sheet following the same order.
- If you remove a field from an Activity Sheet attribute form and the Activity Sheet attribute form is deployed to Unifier, then the deployment does not go through if the field that you had removed from the Activity Sheet attribute form is present as a column in the Activity Sheet in Unifier; otherwise, the deployment goes through if the field that you had removed from the Activity Sheet attribute form is not present as a column in the Activity Sheet.
- If you add a new field to an existing Activity Sheet attribute form and the Activity Sheet attribute form is deployed to Unifier, then the columns in the Activity Sheet do not reflect this change and you need to add the field to the columns in the Activity Sheet manually.
- You can add columns to or remove columns from an Activity Sheet view.
- You can arrange the columns order in an Activity Sheet.
- You can find, sort, group, and filter Activity Sheets.
- The data within and Activity Sheet is synchronized with P6 by way of Gateway (Import/Export Synchronization) daily.
Note: Exchange of data with inactive Unifier CBS type Shells is not permitted whether initiated manually or by Gateway.
You can map the P6 CBS Code to the Unifier CBS Code (bitemID) in Gateway (in the field mappings).
When the Activity Sheet data is synchronized between P6 and Unifier, then Unifier Provider converts the P6 CBS Code to the corresponding Unifier CBS Code (bitemID), and the Activity Sheet, in Unifier, is populated automatically.
When the data is synchronized between Unifier and P6, then Unifier Provider converts the Unifier CBS Code (bitemID) to the corresponding P6 CBS Code, and the Activity Sheet, in P6, is populated automatically.
The CBS auto-population works differently in Base commit, Change commit, and Payments with respect to other classifications that are under Cost type business processes.
The auto-population for the CBS Code occurs in Base Commit business processes and Change Commit business processes.
In Payments business processes, the CBS Code matches with the Commit line item of SOV, then the CBS Code is auto-populated; otherwise, the CBS Code does not auto-populate.
- If there is only one Commit line item matching the CBS Code/Cost Code, then the CBS Code will be auto-populated along with the Commit line item from the SOV, if the CBS Code/Cost Code matches with what is present in the SOV.
- If there is more than one Committed line item (where the CBS Code matches with the Activity picker), then the value for the CBS code remains as it was.
- If the Activity picker is associated with a CBS Code that is not used by any of the Committed line items in the SOV, then the value for the CBS code remains as it was.
You can change the CBS Code by clicking the CBS Picker, which will over-write the auto-populated value.