Examples of Updating Costing Cross-Validation Rules

As a best practice, you must define and enable the cross-validation rules before you run the costing process for the first time.

After you set the end date for your validation rule, you must also set the end date for the existing combinations with that rule.

You can use Cross Validation Rule Report.catalog, uploaded in Cloud Customer Connect, to find all the existing cross validation rules.

Delete Validation Rules

Using HCM Data Loader, you can delete validation rules that you erroneously created.

METADATA|CostKffValidationRule|StructureInstanceCode|RuleCode
DELETE|CostKffValidationRule|HDL_COST_CVR_COST_KFF_INST|ACTIVITY_CHECK_RULE

End Date Validation Rules

Use HCM Data Loader to set the end date for your validation rules. Let's consider this example. There's an existing validation rule that states that the Activity Code is Prohibited for Company = 01, which isn't valid any more. You want to set the end date for this rule to 31-Jul-2019.

Use this dat file to set the end date for your validation rule.

METADATA|CostKffValidationRule|StructureInstanceCode|RuleCode|StartDateActive|EndDateActive
MERGE|CostKffValidationRule|HDL_COST_CVR_COST_KFF_INST|ACTIVITY_RULE_CODE|2020/12/31

Enable or Disable Validation Rules

You can use HCM Data Loader to disable the existing validation rule.

Example: An existing validation rule states that if Activity Code is equal to 2200, then Location can't be equal to 2201 and 22EE. You want to disable this rule because you don't want to validate the rules in earlier periods.

Use this dat file to disable validation rules.

METADATA|CostKffValidationRule|CrossValidationRuleId|StructureInstanceCode|RuleCode|RuleDescription|ErrorMessageText|EnabledFlag|StartDateActive|EndDateActive|ConditionFilterText|ValidationFilterText
MERGE|CostKffValidationRule|31|HDL_COST_CVR_COST_KFF_INST|<RuleCode>|<ruleDesc>|<errorMsgTxt|Y|2010/01/01|4712/12/31|Company = 01,ACTIVITY_CODE ISNOTBLANK|ACTIVITY_CODE STARTSWITH 0,ACTIVITY_CODE STARTSWITH 1,ACTIVITY_CODE STARTSWITH 2,ACTIVITY_CODE STARTSWITH 3,ACTIVITY_CODE STARTSWITH 4

In this example, you update the existing rule to extend it for additional conditions. You have an existing validation rule that states that Cost Center is required for Company=01. In this rule, blank isn't a valid value. You want to extend this rule for Company =02.

Use this dat file to extend the validation rule for Company =02.

METADATA|CostKffValidationRule|StructureInstanceCode|RuleCode|RuleDescription|ErrorMessageText|EnabledFlag|StartDateActive|EndDateActive|ConditionFilterText|ValidationFilterText
MERGE|CostKffValidationRule|HDL_COST_CVR_COST_KFF_INST|<RuleCode>|<ruleDesc>|<errorMsgTxt>|Y|2010/01/01|4712/12/31|Company = 01,Company = 02|COST_CENTER ISNOTBLANK

In another scenario, you might want to extend this rule such that Cost Center and Activity Code are required for Company = 01 and 02.

Use this dat file to extend the validation rule for Activity Code.

METADATA|CostKffValidationRule|StructureInstanceCode|RuleCode|RuleDescription|ErrorMessageText|EnabledFlag|StartDateActive|EndDateActive|ConditionFilterText|ValidationFilterText
MERGE|CostKffValidationRule|HDL_COST_CVR_COST_KFF_INST|<RuleCode>|<ruleDesc>|<errorMsgTxt>|Y|2010/01/01|4712/12/31|Company = 01|COST_CENTER ISNOTBLANK,ACTIVITY_CODE ISNOTBLANK