Guidelines for Loading Calculation Cards

Calculation cards capture values required for payroll calculation of some earnings and deductions, such as absence payments and involuntary deductions.

Various types of calculation cards exist. For example, UK calculation cards include those for statutory deductions, automatic enrollment in pensions, court orders and student loans, and benefits and pensions. Most legislations support the Calculation Card object. However, the types of calculation cards that are supported vary by legislation. This topic describes some general considerations that apply to all calculation cards when you load them using HCM Data Loader. For legislation-specific information, see DOC ID 1504483.1

Each calculation card has one or more components, and each component may have one or more sets of component details, or value definition overrides. For example, in the UK court orders and student loans calculation card, each component corresponds to a different type of court order. You enter information about that court order in the component details and value definition overrides.

Calculation cards are used mainly at the level of the payroll relationship. Depending on the legislation, they can also be used at the level of the payroll statutory unit or tax reporting unit.

Key Support

Calculation Card objects are integration-enabled. They support all key types that HCM Data Loader supports.

Identify Autogenerated Calculation Cards

Some calculation cards are autogenerated, and you’re unlikely to know the source key values that uniquely identify the calculation card records.

You can supply user key values to identify these records, but this relies on you knowing the assignment number of your employee’s assignment. If you don't know this, you can:

• Extract the autogenerated source key values using the Integration Object User Key Map Extract
• Optionally update the autogenerated source key

Create New Calculation Cards

If you're creating a new calculation card, you're recommended to use source keys to uniquely identify the records being loaded. This simplifies the file shape and allows you to easily identify your calculation card records when you need to maintain them.

Update Existing Calculation Cards

If you know your source key values, it is recommended that you use these to reference the records to be updated; user keys are also supported.

When updating existing values for components, the effective date of the component and calculation value definitions in your file or spreadsheet must be the original start date of the existing card component. The Enterable Calculation Values include the actual date of the value change.

If required, the Integration Object User Key Map Extract can be used to extract all key values for existing calculation card records.

You can find details of the parent source key attributes and alternate user key attributes using the View Business Objects task.

Change Logical Start and End Dates

In general, you can change the first effective start date and last effective end date of an existing calculation card. Include the ReplaceFirstEffectiveStartDate and ReplaceLastEffectiveEndDate attributes in your METADATA line, as appropriate, and set them to Y. Provide the new values on the EffectiveStartDate and EffectiveEndDate attributes.

Note: Legislation-specific validations may mean that some changes to logical start and end dates aren't valid.

Delete Calculation Cards

You can delete all components of the Calculation Card object using HCM Data Loader. When you delete a Calculation Card component, its child components are deleted automatically. You can also delete individual child components.