Calculation Cards Transfer

Calculation cards capture values required for payroll calculations. When using the Local and Global Transfer process, you can select to copy calculation cards and their components at a payroll relationship level.

Note: The process doesn't copy calculation cards from other applications such as Oracle Cloud Time, Absence, and Workforce Compensation.

The process copies the cards and components at the payroll relationship level based on each country's legislation. It doesn't copy cards at the payroll statutory unit (PSU) and tax reporting unit (TRU) levels.

Rules for Copy

These rules determine how the process copies the calculation cards and components.

1. It copies the card or component from the source payroll relationship, if the target payroll relationship doesn't already have the card or component.

2. It creates an association for the target TRU only if it exists for the source TRU.

   For cards and components associated to the source TRU, it verifies whether the target card and component is associated to the target TRU. It creates an association if one doesn't already exist.

3. For cards and components having an association detail record on the source assignment, the process creates an association detail for the target assignment.

4. If you selected not to copy the calculation cards, none of these rules apply.

   You can manually add the info if required.

5. Country legislations may deliver additional logic to reset or initialize values on specific cards and components.

Calculation Card Copy Scenarios

These scenarios describe whether the process creates or reuses calculation cards and components.

For these transfers	This is what the flow does
Transfer within the same payroll relationship and TRU	Creates an assignment in the same payroll relationship. Uses the existing cards and components. Adds an association detail to the target assignment, if required.
Transfer to a new TRU but the same payroll relationship	Creates an assignment in the same payroll relationship. Reuses the cards and components associated to the source TRU by adding an appropriate TRU association. If that's not possible (such as the source TRU doesn’t have a TRU association with the target), the process creates cards and components and associates them to the target TRU. If the process reuses the cards and components, it may support only one TRU at a time. In this case, the process updates the TRU association to the new TRU as of the transfer date. Otherwise, the process doesn't change the source TRU association. Instead, it associates the cards and their components to the new TRU. Creates an association detail to the target assignment, if required.
Transfer to a new payroll relationship and TRU	Creates a card and component. Copies the source info to them. Adds an association to the target TRU and an association detail for the new assignment.

Note: If the person already has a card or component on the target payroll relationship, the task uses it. This could be through a different assignment, which isn't part of the global transfer. In such cases, the rules defined under scenario 2 apply.

Rules Delivered by Country Legislations

Each country's legislation delivers rules that control how the Local and Global Transfer process copies cards and components. These rules define whether it needs to create or reuse a card based on preconfigured data. Here's some examples you can configure based on your country's legislation.

• Whether the application copies a card or component.

• If the global transfer is across TRUs, you can choose if the process should reuse an existing card or component.

• Support of an association with more than one TRU at a time by a reused card or component.