Example of Updating Cost Code Combinations

You can use HCM Data Loader to end date or disable the existing cost account combinations so that the invalid cost results doesn't get created based on the new organization policy.

For example, your organization has determined that the company Operations can't use the cost center Marketing. However, you already have the cost account combinations with this data. If you don't set the end date or disable these combinations, the costing process will continue to refer to the existing combinations and successfully create the costing results.

You can use Cost Combination Report.catalog, uploaded in Cloud Customer Connect at https://cloudcustomerconnect.oracle.com/posts/0b2fb95bc4, to find all the existing cost code combinations.

Let's consider these examples.

Example 1

As per the new organization rule effective on 01-Aug-2019, the Funding Source must not be 1010 for the Fund 4310. However, the cost code combinations already exists with these values. So, you end date all the combinations that have Fund = 4310 and Funding Source = 1010 with 31-Jul-2019.

Use this cost account combination.dat file to end date the cost account combinations. This dat file is created with a single record that has the combination. You need to add all the records that has this segment combination. Once you set an end date to all the existing cost account combinations with this data, the application gives an error message, saying that "FLEX-COMBINATION HAS EXPIRED". If you have setup suspense account at payroll or department level, then the costing result is created with suspense account. If there's no suspense account, the payroll process will error.

You must provide CostAllocationKeyflexId for performing this operation.

METADATA|CostAccountCombination|CostAllocationKeyflexId|EndDateActive|IdFlexNum
MERGE|CostAccountCombination|300100032377007|2019/07/31|448

Example 2

As per the new organization rule, the Department 3710 must not use Program as 6530, including prior periods. In this case, you can use HCM Data Loader to disable all cost code combinations with these values. Once you disable all the existing cost account combinations with this data, the application gives an error message, saying that "FLEX-COMBINATION DISABLED". If you have setup suspense account at payroll or department level, then the costing result gets created with suspense account. If there's no suspense account, the payroll process will error.

This dat file is created with a single record that has the combination. You need to add all the records that has this segment combination.

You must provide CostAllocationKeyflexId for performing this operation.

METADATA||CostAccountCombination|CostAllocationKeyflexId|EnabledFlag|IdFlexNum
MERGE|CostAccountCombination|300100032377007|N|448