Use this page to check project definitions such as class or cost set assignments and project audit log records. You can also check apportionment definitions.
Contents
Field | Description |
Validate classes
|
Select this check box to validate the definition of classes in the project. Cobra performs the following validations when you select this check box:
- Missing default classes - If missing default classes are found, Cobra adds them back. Default classes are Budget, Earned, Forecast, Actual, Replanned, and OTB (Over Target Baseline). No message is entered in the log file.
|
Validate cost sets
|
Select this check box to validate the definition of cost sets in the project. Cobra performs the following validations when you select this check box:
- Missing default cost sets - If missing default cost sets are found, Cobra adds them back. Default cost sets are Actual, Budget, Forecast, Earned, OTB, Replan, and ETC (Estimate to Complete). No message is entered in the log file. Below are the included classes in the cost sets that are added back:
- Class Actual in the Actual cost set
- Class Budget, Replanned, and OTB in the Budget cost set
- Class Earned in the Earned cost set
- Class Forecast in the ETC cost set
- Class OTB in the OTB cost set
- Class Replanned in the Replan cost set
- Cobra checks for missing classes in the default cost sets.
|
Consistent class definitions
|
Select this check box to validate that the default classes have the correct class types associated and that those classes are included in the proper categories according to their class type. For example, this validation option checks that a Budget class with type Budget is included in the cost set Budget and in the Earned class. This validation option searches for classes of a certain type that are not assigned as proper included classes. Cobra performs the following validations on classes when you select this check box:
|
Validate apportionment definitions
|
Select this check box to verify that the apportionment definition for the resource is correct. Cobra performs the following validations:
- That a source resource exists in the resource file that is defined as the source for the target apportionment resource.
- That a target resource exists for the source resource. Cobra checks that the target resource defined is a valid resource in the project's resource file.
- That the target apportionment resource result is an existing result in the resource file.
- That the apportionment order is valid. Cobra sets this order automatically when you add apportionment resources. However, Cobra resets the order when an apportionment resource is added or deleted. This validation determines instances where the order is not reset correctly and a loop is created. For example, if the resource Test is based on a QA apportioned resource, the QA resource needs to be higher than the Test resource.
|
Validate apportionment mappings
|
Select this check box to verify that the control account and work package where the apportioned budget resources will be created are correctly defined and that the source control account exists. Cobra performs the following validations:
- That the target resource is a valid resource in the resource file for the project.
- That the control account and work package defined as targets on the Apportionment Mapping page exist.
- That the source control account specified as an apportionment source exists in the source project.
- That rate sets are valid for the target apportioned resource.
- That a source is defined for the corresponding apportionment target.
|
Note: The validity check runs only for the Master Project selected. The validity check does not run against all the sub projects listed under the master project.