Loading Calc Card With HDL

Loading Calculation Cards for the United Kingdom
Using HCM Data Loader
Oracle Fusion Human Capital Management 11g Release 10 (11.1.10)

ORACLE WHITE PAPER | AUGUST 2018
Table of Contents
Loading Calculation Cards for United Kingdom Using HCM Data Loader 0
Introduction 1
How to Use the Information in This Document 1
Example Dat Files 2
Calculation Card 3
Common Considerations 3
Statutory Deductions Card 7
Prerequisites for Statutory Deductions Card 7
Loading Statutory Deductions Cards 8
Calculation Card Hierarchy 8
Calculation Card 9
Card Component 10
Component Detail 11
Card Association 19
Card Association Details 20
Statutory Deductions Calculation Card Errors 22
Pensions Automatic Enrolment Calculation Cards 26
Considerations and Prerequisites for Pensions Automatic Enrolment Card 26
Loading Pensions Automatic Enrolment Calculation Cards 26
Calculation Card 28
Card Component 29
Component Detail 29
Component Association 34
Component Association Details 35
Pensions Automatic Enrolment calculation card Errors 36
Court Orders and Student Loans Calculation Cards 40
Considerations and Prerequisites for Court Orders and Student Loan Card 40
Loading Court Orders and Student Loans Calculation Cards 40
LOADING UK CARDS USING HCM DATA LOADER

Calculation Card 45
Card Component 46
Component Detail 47
Calculation Value Definition 52
Enterable Calculation Value 53
Card Association 54
Component Association 57
Court Orders and Student Loans Calculation Card Errors 58
Benefits and Pensions Calculation Cards 60
Considerations and Prerequisites for Benefits and Pensions Card 60
Loading Benefits and Pensions Calculation Cards 60
Calculation Card 62
Card Component 62
Calculation Value Definition 63
Enterable Calculation Value 64
Card Association 65
Changing the Logical Start and End Date 67
Deletion Support for Calculation Card 67
Annexes 69
Use Case 1 - Update the PAYE component details on statutory deduction card for a
new hire 69
Use Case 2 – Create a New Starter Declaration component details on statutory
deduction card for a new hire 72
Use Case 3 – Create a new Court Order calculation card for new hires. 74
Appendix 1 – Finding the correct SourceSystemOwner and SourceSystemId 77

Table of Figures
Figure 1: Manage Calculation Cards: Statutory Deductions ................................................................................... 10
Figure 2: Calculation Components – Aggregation Information, NI & PAYE ............................................................ 11
Figure 3: Calculation Component Details – Aggregation Information ...................................................................... 17
Figure 4: Calculation Component Details – Pay As You Earn................................................................................. 18
Figure 5: Calculation Component Details – New Starter Declaration ...................................................................... 18
Figure 6: Calculation Component Details – Pension Notification ............................................................................ 19
Figure 7: Calculation Component Details – Expatriate Notification ......................................................................... 19
Figure 8: Card Association ..................................................................................................................................... 20
Figure 9: Card Association Details ......................................................................................................................... 21
Figure 10: Manage Calculation Cards: Pensions Automatic Enrolment .................................................................. 28
Figure 11: Calculation Components........................................................................................................................ 29
Figure 12: Calculation Component Details ............................................................................................................. 34
Figure 13: Component Association ......................................................................................................................... 35
Figure 14: Association Details ................................................................................................................................ 36
Figure 15: Manage Calculation Cards: Court Orders and Student Loans ............................................................... 46
Figure 17: Calculation Component Details – Student Loan .................................................................................... 50
Figure 18: Calculation Component Details – Child Maintenance Service Deduction from Earnings Order ............. 51
Figure 19: Calculation Component Details – Involuntary Deduction Information..................................................... 51
Figure 20: Calculation Component Details – Attachment of Earnings Order Priority............................................... 52
Figure 21: Calculation Component Details – Deduction from Earnings Order......................................................... 52
Figure 22: Enterable Calculation Values ................................................................................................................. 54
Figure 23: Associations .......................................................................................................................................... 55
Figure 25: Association Details ................................................................................................................................ 56
Figure 24: Component Association ......................................................................................................................... 58
Figure 26: Manage Calculation Cards: Benefits and Pensions ............................................................................... 62
Figure 28: Enterable Calculation Values ................................................................................................................. 65
Figure 29: Associations .......................................................................................................................................... 66
Figure 30: Card Association Details........................................................................................................................ 67

Introduction
When implementing Oracle Fusion HRMS (UK) for the first time, or providing regular updates, you can
create calculation card records using HCM Data Loader (HDL).
For general information about how to prepare data for loading using HCM Data Loader, or the HCM
Data Loader file format, refer to the HCM Data Loader User Guide (MOS Doc ID: 1664133.1)
How to Use the Information in This Document

This document provides a separate section for each business object that it describes. Each section
covers the following topics:
• Considerations and Prerequisites What to consider before attempting to load data

• Loading Describes the business object hierarchy. For each business object component, a table of
the attributes that are commonly supplied when creating new records is provided. These tables
have the following columns:
• HCM Data Loader Attribute The attribute name to supply when providing your data in the
business object data (.dat) file. Attribute names with a *1 suffix are foreign-object references
that support the integration key types. As source keys are recommended where possible, the
document describes how to supply source key values. User key attributes are identified for
when you do not have the source key value.
• User Interface Prompt The prompt seen on the user interface. The data that you supply in
the associated attribute derives this field value, which is not necessarily the same as the value
that you supply. For example, for the Location field on an Organization page you can supply
the Oracle Fusion surrogate ID, source key, or Oracle Fusion GUID to identify the location
uniquely. The value seen on the user interface will be the location name.
If the User Interface Prompt is prefixed with an asterisk (*), then the attribute is mandatory
when you create a new record.
• Functional Description Additional information describing the attribute and how to supply
valid values.
• Errors Identifies errors that may occur when loading data for the business object. Information
about resolving the error is provided.
• Deletion Support Describes the extent to which the business object supports data deletion. Some
objects do not support deletion, while others may support deletion of child records only.
• Translation Information on how to provide translation data for the translatable attributes in the
business object hierarchy.
1 | LOADING CALCULATION CARDS FOR THE UK USING HCM DATA LOADER

Example Dat Files
This document provides working dat file examples for loading and deleting data using HCM Data
Loader. To use the source key examples, change the source system owner to a lookup code you have
preconfigured in the HRC_SOURCE_SYSTEM_OWNER lookup.
For both user key and source key examples ensure any references to foreign objects refer to data that
exists in your test environment.
2 | LOADING UK CARDS USING HCM DATA LOADER

Calculation Card
Calculation cards capture values required for payroll calculations for certain earnings and deductions, such as
absence payments, statutory deductions, pensions, and involuntary deductions. Calculation cards are mainly used
at payroll relationship level, but, depending on the legislation, they can also be used at payroll statutory unit (PSU) or
tax reporting unit (TRU) level to store calculation information specific to those organizations.
There are various types of calculation cards, for example Statutory Deductions, Absences, Time & Labor, Benefits
and Pensions, Court Orders, and Student Loans. Some of these cards are populated automatically based on
predefined interfaces, such as Absences (absence records are created using Manage Absences: on saving the
record a calculation card is automatically generated so that the absence can be processed through Payroll) or Time
& Labor. Others are maintained by payroll professional users.
Each calculation card comprises of one or more components, and each component may have one or more
component details, allowing data to be grouped in a logical manner. For example, in the Court Order and Student
Loan card, each component corresponds to a different type of court order and information relating to that order is
entered in the component details.
For UK, the following types of calculation cards are supported for bulk upload using HCM Data Loader (HDL):
• Statutory Deductions
• Pensions Automatic Enrolment
• Court Orders and Student Loans
• Benefits and Pensions
Note: No other types of card than the ones mentioned above are supported for HDL.
Note: Only payroll relationship level calculations cards are currently supported for HDL. PSU and TRU level cards
are not supported.
Common Considerations
This section provides information and guidance for all types of cards.
HCM Data Loader scope
HCM Data Loader cannot be used in parallel with HCM File-Based Loader or HCM Spreadsheet Data Loader for
maintaining the same business objects. The HCM Data Loader Scope parameter on the Configure HCM Data
Loader page controls whether HCM Data Loader is used for all bulk data loading or just for those objects that are
not supported by HCM File-Based Loader. The HCM Data Loader Scope parameter has two settings:
Limited: Only business objects not supported by HCM File-Based Loader can be loaded using HCM Data Loader.
Full: HCM Data Loader is used for bulk loading data into all supported business objects. HCM File Based Loader
and HCM Spreadsheet Data Loader are disabled.
Note: Setting the scope to Full is irreversible. It is therefore critical to understand which choice is right for you. For
further information, please refer to the HCM Data Loader User Guide (MOS Doc ID: 1664133.1).

Using the SourceSystemOwner / SourceSystemId
None of the business objects for Calculation Cards currently support user keys, so each business object occurrence
must be identified using source keys. You can do this by using the SourceSystemOwner and SourceSystemId
attributes available on all business objects. Whenever a new business object occurrence is created using HDL, it
uses those attributes if available. Else it automatically sets the SourceSystemOwner to FUSION and sets the
SourceSystemId to be the surrogate ID of the business object occurrence.
Note: The application validates the value set for SourceSystemOwner against the
HRC_SOURCE_SYSTEM_OWNER lookup.
This process occurs independently of how the business object occurrence is created, that is, user interface, service,
or HDL. All business object occurrences have a SourceSystemOwner and a SourceSystemId.
The SourceSystemOwner FUSION is reserved for internal use and cannot be explicitly used in the interface when
creating new objects. This means it is not possible to identify a parent object using a SourceSystemId with a
SourceSystemOwner of FUSION when creating a new object – the SourceSystemOwner applies to both the
SourceSystemId for the business object itself as well as any business object references using SourceSystemId. To
avoid this situation the parent business object can be alternatively identified using the unique GUID which is
automatically assigned to each business object instance when it is created.
Use these attributes to identify existing business object occurrences when updates or deletions are required. You
can also use these to identify related business object occurrences. For example, when adding a new component to
an existing card, the card reference on the component is set using the attribute DirCardId(SourceSystemId) which
identifies the appropriate card using the relevant card’s SourceSystemId.
Following is the list of references:
Business Object Business Object Reference(s)
CalculationCard (DircardId)
CardAssociation (DirRepCardId) DirCardId(SourceSystemId)

DirCardId(GUID)
CardAssociationDetail DirRepCardId(SourceSystemId)
DirCardCompId(SourceSystemId)
DirRepCardId(GUID)
DirCardCompId(GUID)
CardComponent (DirCardCompId) DirCardId(SourceSystemId)

ParentDirCardCompId(SourceSystemId)
DirCardId(GUID)
ParentDirCardCompId(GUID)
ComponentAssociation (DirRepCardId) DirCardCompId(SourceSystemId)

DirCardCompId(GUID)
ComponentAssociationDetail DirRepCardId(SourceSystemId)
DirRepCardId(GUID)
ComponentDetail DirCardCompId(SourceSystemId)
DirCardCompId(GUID)
CalculationValueDefinition (ValueDefnId) SourceId(SourceSystemId) – this is a reference to appropriate

component
SourceId(GUID)
EnterableCalculationValue ValueDefnId(SourceSystemId)
ValueDefnId(GUID)
If the source keys are set explicitly when creating new business object occurrences then they are already known
and can be used for subsequent updates and deletes. To be able to work with those business object occurrences
with a SourceSystemOwner of FUSION the SourceSystemId and GUID information needs to be extracted from the
Oracle system so they can used for any updates or deletes. For guidance on how to extract this information, refer to
Appendix 1 – Finding the correct SourceSystemOwner and SourceSystemID.
The source keys are only supported for integration enabled objects. There might be existing business object
occurrences that were created before the business object was integration enabled and may be some missing
SourceSystemOwner / SourceSystemIds. To correct this, run the process Reconcile Integration Keys for a specific
business object. This finds any missing SourceSystemOwner / SourceSystemIds and sets them to FUSION and the
relevant surrogate ID.
You only need to run this once per business object as it is maintained automatically after that. Run the process for
the following business objects: CalculationCard, CalculationCardComponents, CalculationCardComponentDetails,
CalculationCardAssociations, CalculationCardAssociationDetails, ValueDefinition, and RangeItem.
Translated Content
The attributes describing the card, components, and override values are translated values and vary depending on
the language that is set for the user. To ensure that the .dat file uploads correctly, it is important that the user loading
the file uses the same language as the user who created it. The translated values are DirCardDefinitionName,
DirCardCompDefName, and ValueDefinitionName.
Ordering of Components
Card components can be organized in a hierarchical structure, with multiple levels. On creation of a new card, all
components can be provided within the same .dat file; HDL will work out based on the hierarchy in which orders to
create the components. However in order for the automatic component ordering to happen, both
ParentDirCardCompId(SourceSystemId)’ and ‘ParentDirCardCompDefName’ need to be provided.

Note: if the component hierarchy has only two levels (i.e parent – child) the ordering happens automatically without
having to provide those 2 attributes. This is the case for all UK calculation cards.

Statutory Deductions Card
Statutory Deductions card stores all the information required to accurately compute Tax and National Insurance (NI)
contributions for an employee, such as tax code, NI category, and pension basis. It also includes information
required for the Real Time Information (RTI) reports. One Statutory Deduction card must be created for each
employee and for the TRU that the employee reports to.
A Statutory Deductions card is created automatically when a new employee is entered using the New Hire task with
a set of default values specified at the PSU or the TRU level (if the product license is set to Payroll or Payroll
Interface).
However there may be cases where this information must be loaded in bulk.
• During implementation for data migration:
o Employee PAYE and NI information must be uploaded into Oracle Fusion Payroll, in order to
ensure that contributions are calculated correctly. If HDL is used to migrate employee records, a
default statutory deduction card is automatically created. In most cases, the default will not
reflect the employee’s actual tax and NI information, and therefore the card must be updated.
There are also a number of information fields that must be provided for RTI purposes:
- Previous HMRC Payroll ID from your legacy system to inform HMRC of the change in
Payroll ID.
Note: The new Fusion HRMC Payroll ID is generated automatically when a new
Statutory Deduction card is created for the person. When the Full Payment Submission
(FPS) is submitted for the first time from Oracle Fusion Payroll, it contains the mapping
between the new and old HMRC Payroll ID. If the employment has already been filed
with HMRC, it will not be reported as a new one.
- Information such as Late Hire Reason, Number of Hours Worked, New Hire
Declaration, Pensioner Notification, or Expatriate Notification, if required.
• Ongoing bulk updates
o Bulk loading of new hire data: If you have to do a mass upload of New Hire information, a default
Statutory Deduction card and Pensions Automatic Enrolment card may be generated
automatically (if the new hire records are created through HDL or the interface with Taleo). In this
case, you need to update the default card with the correct tax and NI informationand create a
component detail to store new hire information as requested for RTI reporting.
It is recommended to have a good understanding of the Statutory Deductions card and the information it contains
prior to attempting mass upload as it has a direct impact on statutory deductions and reporting. For further
information, see Oracle Fusion HRMS (United Kingdom): Payroll Implementation and Functional Considerations
(Doc ID 1921464.1).
Prerequisites for Statutory Deductions Card

You must create element eligibility for the Tax and NI elements.

Loading Statutory Deductions Cards
Provide the calculation card data in the CalculationCard.dat file for processing by HDL. Statutory Deductions cards
use the following components of the calculation card object.
Calculation Card Hierarchy
COMPONENTS USED FOR STATUTORY DEDUCTIONS CARD
Component Functional Description Discriminator
Calculation Card The Statutory Deductions calculation card. CalculationCard
Card Component The card components for the Statutory Deductions calculation card. CardComponent
Component Detail The component detail holds information specific to the statutory deduction. ComponentDetail
This is defined using the Further Deduction Information descriptive flexfield,
as shown in the hierarchy above.
Card Association An association between the Statutory Deductions card and the TRU. CardAssociation
Card Association between the components and Term or Assignment. CardAssociationDetail

Association Details Both PAYE and NI components needs component association to one or more
terms or assignments.
The following section explains each component listed above:

Calculation Card
The discriminator CalculationCard is used to load calculation card records using HCM Data Loader. The following
CalculationCard attributes must be provided when loading a Statutory Deductions calculation card.
CALCULATION CARD ATTRIBUTES
HCM Data Loader

User Interface Prompt Functional Description
Attribute
SourceSystemId / * not displayed You must provide a unique reference for the record being created. User keys are not
SourceSystemOwner currently supported and so the source key must be supplied.
LegislativeDataGroup * Legislative Data Group The name of the legislative data group this calculation card belongs to.
Name
DirCardDefinitionNam * Calculation Card The type of calculation card, that is, Statutory Deductions.
e
AssignmentNumber * Assignment Number The assignment number of the employee for whom this calculation card is created.
The source key is not supported for the assignment record.
EffectiveStartDate * Effective Start Date The start date of the calculation card, which is the date of update to the calculation
card if you provide date-effective history.
EffectiveEndDate Effective End Date The end date of the Statutory Deductions card, or, if you are providing date-effective
history, the last day of the date-effective changes. If no value exists, then this is the
end of time by default.
The value supplied will derive the value seen in the field specified in the User Interface Prompt.

Figure 1: Manage Calculation Cards: Statutory Deductions
Card Component
The Card Component represents the skeleton structure of the card. Each type of card has specific components, and
each component may have one or more flexfield definitions to store relevant data.
The discriminator CardComponent is used to load Card Component records using HCM Data Loader. The
following CardComponent attributes must be provided when loading a new Statutory Deductions component.
Note: You cannot create multiple PAYE components for the same card within a single file. If you need to create
multiple PAYE components, you will need to upload them in individual files.
CARD COMPONENT ATTRIBUTES
HCM Data Loader

Attribute
EffectiveStartDate * Effective Start Date The start date of the card component or of the update to the card component if you
are providing date-effective history. This must be after or equal to the
EffectiveStartDate provided for the Statutory Deductions Calculation Card
component.
EffectiveEndDate Effective End Date The end date of the Statutory Deductions card component, or, if you are providing
date-effective history, the last day of the date-effective changes. If left blank, this
value is the end of time by default.
LegislationDiscriminat Legislation code Optional. If not provided, it is defaulted based on the Legislative Data Group.
or
DirCardCompDefNam * Calculation Component The component definition name. Provide:
e
• Aggregation Information
• NI
• PAYE
If you are creating multiple components, you must create multiple lines, one for each
component.
LegislativeDataGroup * Legislative Data Group The name of the legislative data group this calculation card belongs to. This must
Name match the LegislativeDataGroupName of the calculation card.
ParentDirCardCompId Parent Component ID For NI component, supply the Aggregation Information Component ID. As user keys
are not supported, supply the source system ID value and add the hint to the
attribute name. For example ParentDirCardCompId(SourceSystemId).
The other components do not have a parent.
DirCardId * not displayed A unique reference to the Statutory Deductions calculation card this component
belongs to. As user keys are not currently supported, provide the source key for the
Statutory Deductions calculation card and add the source key hint to the attribute
name, for example DirCardID(SourceSystemId).
Only provide the following segments if the component is NI (Contexts 3 to 6 are not used)
Context1 * NI Category NI Category. This attribute is validated using the HRX_GB_NI_CATEGORY lookup.
Context 2 * Pension Basis Pension Basis. This attribute is validated using the HRX_GB_PENSION_BASIS
lookup.

HCM Data Loader
Attribute
Only provide the following segments if the component is PAYE (Contexts 2 to 6 are not used)
Context1 HMRC Payroll ID This field is generated automatically and cannot be uploaded.
The value supplied will derive the value seen in the field specified in the User Interface Prompt.
Figure 2: Calculation Components – Aggregation Information, NI & PAYE
Component Detail
The Component Details hold the values that are used to process the earnings or deductions in payroll. Each card
component comprises different component details.
The discriminator ComponentDetail is used to load Component Detail records using HCM Data Loader. The
following ComponentDetail attributes are commonly provided when loading a new Statutory Deductions calculation
card.
COMPONENT DETAIL ATTRIBUTES
HCM Data Loader

Attribute
EffectiveStartDate * Effective Start Date The start date of the component detail (or the update date if you are providing date-
effective history). This must be equal to the EffectiveStartDate for the Card
component.
EffectiveEndDate Effective End Date The end date of the card details (or for date-effective history, the last day of the date-
effective changes). If left blank, this value is the end of time by default.
LegislativeDataGroup * Legislative Data Group The name of the legislative data group this calculation card belongs to. This should
Name match the LegislativeDataGroupName provided for the card component.
LegislationDiscrimina Legislation Code Optional. If left blank, it is defaulted based on the Legislative Data Group.
tor

HCM Data Loader
Attribute
DirCardCompDefNa * Calculation Component The component definition name. Provide:

me • Aggregation Information
• NI
• PAYE
DirCardCompId * not displayed A unique reference to the Statutory Deduction card component this detail belongs to.
User keys are not currently supported.
Provide the source key for the Statutory Deduction card component and add the
source key hint to the attribute name. For example, DirCardCompId(SourceSystemId).
DirInformationCatego * Calculation Component The information category for the Statutory Deductions flexfield. Enter one of the
ry Details following values:
• HRX_GB_AGGREGATION_INFO for Aggregation Information
• HRX_GB_PAYE for PAYE
• HRX_GB_NEW_STARTER for New Starter Declaration
• HRX_GB_PENSIONER for Pensioner Declaration
• HRX_GB_EXPATRIATE for Expatriate Declaration
FLEX: Deduction * not displayed The flexfield code. Enter the flexfield context for the data row. Five contexts are
Developer DF available and so you must provide a separate ComponentDetail record for each
context:
• HRX_GB_AGGREGATION_INFO for Aggregation Information
• HRX_GB_PAYE for PAYE
• HRX_GB_NEW_STARTER for New Starter Declaration
• HRX_GB_PENSIONER for Pensioner Declaration
• HRX_GB_EXPATRIATE for Expatriate Declaration
The flexfield segment attribute names include the context to which they apply.
Enter the following flexfield segment attribute values only if the FLEX: Deduction Developer DF attribute has a value of
HRX_GB_AGGREGATION_INFO.
_PROCESS_TYPE(D Process Type Specify the process type applicable to the employee for the purpose of NI calculation.
eduction Developer This attribute is validated using the HRX_GB_PROCESS_TYPE lookup.
DF=HRX_GB_AGGR
EGATION_INFO)
_SCON(Deduction SCON Scheme Contracted-Out Number: the number assigned to an occupational contracted-
Developer out pension scheme. It must have 9 characters in the format ANNNNNNNA (where A
DF=HRX_GB_AGGR is alphanumeric character and N is a number) and be prefixed by the letter ‘S’.
EGATION_INFO)
_NUMBER_OF_PER Number of Periods If the Process Type is Multiple Periods or Irregular Periods, then the Number of
IODS(Deduction Periods must be entered.
Developer
DF=HRX_GB_AGGR
EGATION_INFO)
_PRIORITY_PERIOD Priority Period Type Specify the period type to use in the pay run process in the event of there being
_TYPE(Deduction multiple assignments, which may result in there being more than one period type.
Developer This attribute is validated using the PAY_PROC_PERIOD_TYPE lookup.
DF=HRX_GB_AGGR
EGATION_INFO)
_CERTIFICATE(Ded Certificate Certificate as required for certain NI Categories.

uction Developer This attribute is validated using the HRX_GB_CERTIFICATE lookup.
DF=HRX_GB_AGGR

HCM Data Loader
Attribute
EGATION_INFO)
_RENEWAL_DATE( Certificate Renewal Date The certificate renewal date, as required for certain NI categories.
Deduction Developer
DF=HRX_GB_AGGR
EGATION_INFO)
_DATE_BECAME_DI Date Became Director If the employee is a company director, indicate the date on which he or she became a
RECTOR(Deduction director.
Developer
DF=HRX_GB_AGGR
EGATION_INFO)
_NIC_REFUND(Ded NIC Refund Yes or No

uction Developer
DF=HRX_GB_AGGR
EGATION_INFO)
Only provide the following flexfield segment attribute values if the FLEX: Deduction Developer DF attribute has a value of
HRX_GB_PAYE
_TAX_CODE(Deducti * Tax Code Employee’s tax code

on Developer
DF=HRX_GB_PAYE)
_TAX_BASIS(Deduct * Tax Basis Indicates whether tax should be calculated on a cumulative or noncumulative basis.
ion Developer
This attribute is validated using the HRX_GB_TAX_BASIS lookup.
DF=HRX_GB_PAYE)
_PREVIOUS_TAXAB Previous Taxable Pay on Indicates the employee’s previous taxable pay in the current tax year from a previous
LE_PAY_ON_P11(D P11 employment.
eduction Developer
DF=HRX_GB_PAYE)
_PREVIOUS_TAX_P Previous Tax Paid on P11 Indicates the employee’s previous tax paid in the current tax year from a previous
AID_ON_P11(Deduct employment.
ion Developer
DF=HRX_GB_PAYE)
_AUTHORITY(Deduc Authority Legal source of information for previous employment figures.
tion Developer This attribute is validated using the HRX_GB_TAX_AUTHORITY lookup.
DF=HRX_GB_PAYE)
_AUTHORITY_DATE Authority Date Date the legal source of information was obtained.
(Deduction Developer
DF=HRX_GB_PAYE)
_UPDATE_METHOD Last Update Process Indicates how the PAYE data was last updated. During migration, it can be set to ‘M’.
(Deduction Developer This attribute is validated using the HRX_GB_UPDATE_METHOD lookup.
DF=HRX_GB_PAYE)
_LAST_UPDATE_PR Last Update Process Date Date on which the PAYE data was last updated.
OCESS_DATE(Dedu
ction Developer
DF=HRX_GB_PAYE)
_ISSUE_DATE(Dedu Issue Date
ction Developer Date of issue of the change. This field is not editable in the user interface as it is
DF=HRX_GB_PAYE) updated during the upload of an incoming EDI file. It is updatable using HDL in order
to migrate the history.
_MESSAGE_DATE( Message Date The date the EDI message was sent. This field is not updatable using the UI as it is
Deduction Developer updated during the upload of an incoming EDI file. It is updatable using HDL in order
DF=HRX_GB_PAYE) to migrate the history.

HCM Data Loader
Attribute
_PENSIONER(Deduc Pensioner Indicates whether the employee is a pensioner. Supply Yes or No

tion Developer
DF=HRX_GB_PAYE)
_REASON_TO_WIT Reason to Withhold Tax Reason for withholding a tax refund.

HHOLD_TAX(Deduct This attribute is validated using the HRX_GB_REASON_WITHHOLD lookup.
ion Developer
DF=HRX_GB_PAYE)
_PAY_FREQUENCY Pay Frequency Allows the user to select the period type to use in the pay run process in the event of
(Deduction Developer there being multiple assignments which, may result in there being more than one
DF=HRX_GB_PAYE) period type.
This attribute is validated using the PAY_PROC_PERIOD_TYPE lookup.
_P45_ACTION(Dedu P45 Action Indicates the conditions for how the P45 should be issued.
ction Developer This attribute is validated using the HRX_GB_P45_ACTION lookup.
DF=HRX_GB_PAYE)
_P45_DATE_ISSUE P45 Manual Issue Date Date of issue of a manually issued P45. It is required when the P45 Action selected is
D(Deduction Manual issue.
Developer
DF=HRX_GB_PAYE)
_EMPLOYMENT_FIL Employment filed with Indicates whether the employment has already been filed with HMRC. If set to No, it is
ED_HMRC(Deductio HMRC included as part of the next FPS submission.
n Developer Supply Yes or No.
DF=HRX_GB_PAYE)
_NUMBER_OF_PER Number of Periods Indicates the number of tax periods covered in the payroll calculations. This
IODS_CVD(Deductio Covered information will get reported in the next FPS submission and reset to null.
n Developer
DF=HRX_GB_PAYE)
_NUMBER_OF_HRS Number of Hours Worked Range within which the employee’s working hours fall. If this information is not
_WORKED(Deductio entered, it is derived based on assignment normal working hours.
n Developer This attribute is validated using the HRX_GB_HRS_WORKED lookup.
DF=HRX_GB_PAYE)
_REPORT_NI_YTD_ Report NI YTD values Indicates whether the YTD values should be reported on the FPS. Note that it can
VALUES(Deduction only be set on one of the calculation breakdowns.
Developer Supply Yes or No.
DF=HRX_GB_PAYE)
_IRREGULAR_EMP_ Irregular employment Indicates whether the employee is on irregular payment. This information is reported
PAYMENT(Deduction payment in the next FPS submission.
DF=HRX_GB_PAYE)
_ONE_OFF_PAYME One-off payment Indicates whether the employee is receiving a one-off payment during the pay period.
NT(Deduction This information is reported in the next FPS submission.
DF=HRX_GB_PAYE)
_PAYMENT_NON_I Payment to a non- Indicates whether a payment is made to a non-individual. This information is reported
NDIVIDUAL(Deductio individual in the next FPS submission.
n Developer Supply Yes or No.
DF=HRX_GB_PAYE)
_UNPAID_ABSENCE Unpaid absence Indicates whether the employee has an unpaid absence during the pay period. This
(Deduction Developer information is reported in the next FPS submission.
DF=HRX_GB_PAYE) Supply Yes or No.
_ON_STRIKE(Deduc On strike Indicates whether the employee has been on strike during the pay period. This
tion Developer information is reported in the next FPS submission.
DF=HRX_GB_PAYE) Supply Yes or No.
_PREV_HMRC_PAY Previous HMRC Payroll ID The Previous HMRC Payroll ID needs to be provided when migrating to Oracle Fusion
ROLL_ID(Deduction Payroll. The mapping between the previous HMRC Payroll ID and the one
Developer automatically allocated to the employee in Oracle Fusion is sent to HRMC so that they
DF=HRX_GB_PAYE) know it is not a new record of employment.

HCM Data Loader
Attribute
_SEND_HMRC_PAY Send HMRC Payroll ID Indicates whether the change of HMRC Payroll ID should be reported.
ROLL_ID_CHG(Dedu change Supply Yes or No.
ction Developer
DF=HRX_GB_PAYE)
_HMRC_PAYROLL_I HMRC Payroll ID change Noneditable field. This field is set automatically once the change of HMRC Payroll ID
D_CHG_FILED(Dedu filed has been submitted by the first FPS.
ction Developer
DF=HRX_GB_PAYE)
_EMPLOYMENT_FIL Employment Filed with Internal field only. Noneditable field which is defaulted automatically. Do not supply.
ED_HMRC_PA(Dedu HMRC Action
ction Developer
DF=HRX_GB_PAYE)
_HMRC_PAYROLL_I HMRC Payroll ID Change Internal field only. Noneditable field which is defaulted automatically. Do not supply.
D_CHG_FILED_PA( Filed Action
Deduction Developer
DF=HRX_GB_PAYE)
_DATE_LEFT_REPO Date of Leaving Reported Indicates whether the leaving date has already been field with HMRC. If set to No, it is
RTED_HMRC(Deduc to HMRC included as part of the next FPS submission.
tion Developer Supply Yes or No.
DF=HRX_GB_PAYE)
_DATE_LEFT_FILED Date of Leaving Filed Internal field only. Non editable field which is defaulted automatically. Do not supply.
_PA(Deduction Action
Developer
DF=HRX_GB_PAYE)
_ORA_HRX_GB_LA Late PAYE Reporting Reason for reporting PAYE past the submission deadline.
TE_PAYE_RSN(Ded Reason This attribute is validated using the ORA_HRX_GB_RTI_LATE_PAYE_RSN lookup.
uction Developer
DF=HRX_GB_PAYE)
_RETAIN_LATE_PA Retain late PAYE reporting If late submission is recurring from one period to the next, the reason can be retained,
YE_RSN(Deduction reason so that it is reported in the FPS every period.
DF=HRX_GB_PAYE)
_LATE_PAYE_RSN_ Late PAYE Reporting Internal field only. Noneditable field which is defaulted automatically. Do not supply.
CLR_PA(Deduction Reason Cleared Action
Developer
DF=HRX_GB_PAYE)
_FAPR(Deduction Flexibility Accessing Supply Yes or No.
Developer Pension Rights
DF=HRX_GB_PAYE)
_FAPR_CHECK(Ded Flexibility Accessing Supply Yes or No.
uction Developer Pension Rights to
DF=HRX_GB_PAYE) Continue
HRX_GB_NEW_STARTER
_NS_STATEMENT(D * Statement Statement that fits this employee's employment.

eduction Developer This attribute is validated using the HRX_GB_P46_STATEMENT lookup.
DF=HRX_GB_NEW_
STARTER)
_STUDENT_LOAN_ Student loan deductions to Select this option if student loan deductions need to be taken for this employee.
DEDUCTIONS(Dedu continue Supply Yes or No.
ction Developer
DF=HRX_GB_NEW_
STARTER)
_NOT_PAID_BEFOR Not paid before tax year Select this option if the new employee won't receive any pay before the end of the
E_TAX_YEAR(Deduc end current tax year.
tion Developer Supply Yes or No.
DF=HRX_GB_NEW_
STARTER)

HCM Data Loader
Attribute
_RTI_FILED(Deducti Filed with HMRC Indicates whether the new starter record has already been filed with HMRC. If set to
on Developer No, it is included as part of the next FPS submission.
DF=HRX_GB_NEW_ Supply Yes or No.
STARTER)
Enter the following flexfield segment attribute values only if the FLEX: Deduction Developer DF attribute has a value of
HRX_GB_PENSIONER
_ANNUAL_PENSION * Annual Pension Amount of Annual Pension.

DF=HRX_GB_PENSI
ONER)
_DATE_PENSION_S * Date Pension Started Date on which the pensioner starter receiving pension payments
TARTED(Deduction
Developer
DF=HRX_GB_PENSI
ONER)
_RECENTLY_BERE Recently bereaved Indicates whether the employee was recently bereaved.
AVED(Deduction Supply Yes or No.
Developer
DF=HRX_GB_PENSI
ONER)
_RTI_FILED(Deducti Filed with HMRC Indicates whether the pensioner record has already been filed with HMRC. If set to
DF=HRX_GB_PENSI Supply Yes or No.
ONER)
_RTI_FILED_HMRC_ RTI Filed with HMRC Internal field only. Noneditable field. On Insert, this is automatically populated. Do not
PA(Deduction Action supply.
Developer
DF=HRX_GB_PENSI
ONER)
HRX_GB_EXPATRIATE
_EXPAT_STATEME * Statement Statement that fits this employee's expatriate status.

NT(Deduction This attribute is validated using the HRX_GB_EXPAT_STATEMENT lookup.
Developer
DF=HRX_GB_EXPA
TRIATE)
_EEA_CITIZEN(Ded EEA citizen Indicates whether the employee is an EEA citizen.
uction Developer Supply Yes or No.
DF=HRX_GB_EXPA
TRIATE)
_EPM6_SCHEME(D EPM6 scheme Indicates whether the employee is included in an EPM6 agreement.
eduction Developer Supply Yes or No.
DF=HRX_GB_EXPA
TRIATE)
_RTI_FILED(Deducti Filed with HMRC Indicates whether the expatriate record has already been filed with HMRC. If set to
DF=HRX_GB_EXPA Supply Yes or No.
TRIATE)
_RTI_FILED_HMRC_ RTI Filed with HMRC Internal field only. Noneditable field. On Insert, this is automatically populated. Do not
PA(Deduction Action supply.
Developer
DF=HRX_GB_EXPA
TRIATE)
The value provided will derive the value seen in the field specified in the User Interface Prompt.

Figure 3: Calculation Component Details – Aggregation Information
Navigation: Payroll Calculation > Manage Calculation Cards

Figure 4: Calculation Component Details – Pay As You Earn
Figure 5: Calculation Component Details – New Starter Declaration


Figure 6: Calculation Component Details – Pension Notification
Figure 7: Calculation Component Details – Expatriate Notification

Card Association
The card association enables the Statutory Deductions card to be associated to a tax reporting unit.
The discriminator CardAssociation is used to load card association records using HCM Data Loader. The following
CardAssociation attributes are commonly provided when loading a new Statutory Deductions card.
CARD ASSOCIATION ATTRIBUTES
HCM Data Loader

Attribute
component.
effective changes). If left blank, this value is the end of time, by default.
LegislativeDataGroupN * Legislative Data Group The name of the legislative data group this calculation card belongs to. This must
ame match the LegislativeDataGroupName provided for the calculation card.
TaxReportingUnitName * Tax Reporting Unit The name of the tax reporting unit to associate the Statutory Deductions card with.
TruBatchId Unique ID Unique ID that provides a grouping mechanism for certain statutory reports.
Use the lookup type previously created and associated to the TRU.

DirCardId * not displayed A unique reference to the Statutory Deductions calculation card this component
belongs to. User keys are not currently supported.
Provide the source key for the Statutory Deductions calculation card and add the
source key hint to the attribute name, for example, DirCardId(SourceSystemId)
Figure 8: Card Association

Navigation: Payroll Calculation > Manage Calculation Cards > Associations
Card Association Details

The card association detail allows the components of the Statutory Deduction card to be associated to a term or
assignment.
The discriminator CardAssociationDetail is used to load card association detail records using HCM Data Loader.
The following CardAssociationDetail attributes are commonly provided when loading a new Statutory Deduction
card.
Note: Only NI and PAYE components require a card association details.
CARD ASSOCIATION DETAILS ATTRIBUTES
HCM Data Loader

Attribute
component.
effective changes). If left blank, this value is the end of time, by default.
DirRepCardId * not displayed A unique reference to the card association these details belong to. User keys are not
currently supported.
Provide the source key for the card association and add the source key hint to the
attribute name, for example, DirRepCardId (SourceSystemId)

DirCardCompId * not displayed A unique reference to the Statutory Deduction card component being associated.
User keys are not currently supported.
Provide the source key for the card component and add the source key hint to the
AssignmentNumber * Assignment Number The assignment number for the worker this component is associated to. The source
key is not supported for the assignment record. If the employee has multiple
assignments, the component could be associated to a different assignment than the
one referenced in the card component.
Figure 9: Card Association Details


Statutory Deductions Calculation Card Errors
You may experience errors while loading the Statutory Deductions calculation card, if the data is not provided as
required. Following is a list of some the common errors that may occur:
Message Resolution
You cannot change the tax reporting unit for this calculation A Statutory Deductions calculation card cannot move to a different TRU once
card because it was already used within a payroll run. it has been used within a payroll run.
You cannot change the tax reporting unit for this calculation A Statutory Deductions calculation card can only be associated to one TRU
card using a date-effective update. You can only make a for the entire date track history.
correction.
You must select a tax reporting unit with an associated The TRU assigned to a Statutory Deductions card must be classified as
legislative category equal to HMRC. HMRC.
The process type is not one of the valid process types. Provide a valid value for process type.
This process type is not valid because there are multiple The value Irregular Periods is only valid if there is one and only one term
association details for this calculation card. associated to this calculation card.
The process type cannot be updated until the start of the If the process type is currently Director or Director Normalized and a payroll
next tax year because a payroll was run using the current run has occurred using this data, then the process type can only be changed
value. at the start of the next tax year
You must provide a SCON for the NI categories D, E, I, K SCON is mandatory with certain NI categories.
and L.
The SCON must follow the format ANNNNNNNA, where A is SCON must have 9 characters in total ANNNNNNNA, (where A are alpha and
an uppercase letter and N is a number. N are numeric)
The SCON prefix must be S. SCON must start with the letter “S”.
The SCON fails the check for a valid SCON. The checksum calculated using the numeric component and alpha suffix must
evaluate correctly.
You must enter a number of periods for the process type you If the process type is Multiple Periods of Irregular Periods then the number of
have selected. periods is mandatory.
You cannot enter a number of periods for the process type If the process type is Multiple Periods of Irregular Periods then the number of
you have selected. periods is mandatory, otherwise it will not be allowed to enter a value.
The number of periods must be between 1 and 366. Valid number of periods must be provided.
The priority period type is not one of the valid period types. Provide a valid value for priority period type.
The certificate is not one of the valid certificates. Provide a valid value for certificate.
This certificate is not valid for males. There is a restriction on gender for some certification. Ensure the right
certification is selected.
This certificate is appropriate only for people over the state There is a restriction on age for some certification. Ensure the correct
pension age, and this person is not yet that age. certification is selected.
You cannot specify a renewal date if you have not specified The renewal date is only allowed if there is a certificate specified
a certificate.
The date the employee became a director is invalid for the On setting the process type to one of Director Normalised or Director the
director process type. You must enter a valid director Date Became Director attribute is set to the current effective date if a value
process type date. has not been provided. If a value has been provided it is validated to ensure it
is equivalent to the effective start date of an earlier date effective record with
Director Normalised or Director process type set.

Message Resolution
The NI category is required. NI Category must be provided.
The NI category {NI_CATEGORY} is not one of the currently Provide a valid value for NI category.
valid NI categories.
NI category {NI_CATEGORY} cannot be used in conjunction The NI Category provided is not allowed to be used in conjunction with any
with any other categories on the same calculation card. other categories.
The pension basis is required. A Pension Basis must be provided.
You must enter an authority for this update. The authority can only be “NULL” when the record is migrated, in which case
the last update process is “MIGRATION”.
You can no longer enter a new starter authority for this Authorities of “P46 or New Starter Default”, “P46 or New Starter” or “P45” will
PAYE component detail. only be available for selection when the current authority is “P46 or New
Starter Default”, “P46 or New Starter” or “P45” or on initial creation.
For this combination of authority and tax basis, you should If authority is updated to “P45” and the tax basis is “Cumulative” the previous
enter previous taxable pay on P11 and previous tax paid on taxable pay on P11 and previous tax paid on P11 should be entered.
P11.
For this combination of authority and tax basis, you can only If authority is updated to “P45” and the tax basis is “Noncumulative” the
update previous taxable pay on P11 and previous tax paid previous taxable pay on P11 and previous tax paid on P11 can only be
on P11 to zero. entered as 0.
The combination of values provided is not valid for authority If authority is updated to “P46 or New Starter Default” the tax code should be
P46 employer declaration. “0T”, tax basis should be “Noncumulative” and the previous taxable pay on
P11 and previous tax paid on P11 can only be entered as 0.
The combination of values provided is not valid for authority If authority is updated to “P46 or New Starter” the tax code should be “BR” or
P46 employee declaration. emergency tax value, tax basis should be “Cumulative” if BR (otherwise it can
be either) and the previous taxable pay on P11 and previous tax paid on P11
can only be entered as 0.
The combination of values provided is not valid for authority If the authority is updated to “P9X” and the last update process is not
P9X. “Uplifted”, it will allow a change to the tax code, will require the tax basis to be
set to “Cumulative” and will only allow the previous taxable pay on P11 and
previous tax paid on P11 to be removed or reset to 0.
If you update the authority to P7X, you cannot change the If the authority is updated to “P7X”, it will allow a change to the tax code only.
tax basis, the previous taxable pay on P11, or the previous
tax paid on P11.
If you update the authority to P9, you cannot change the The authority is updated to “P9” tax code or tax basis can be updated, but the
previous taxable pay on P11 or the previous tax paid on previous taxable pay on P11 and previous tax paid on P11 cannot be
P11. changed.
The tax code must be a valid tax code. The tax code must have a valid format.
The monetary value entered can be up to 9 digits in length The Previous Taxable Pay on P11 as well as Previous Tax Paid on P11 must
and to 2 decimal places. be a positive value with 9 or fewer numeric characters and at most 2 decimal
places.
The previous taxable pay on the P11 must be equal to or Verify that accurate previous Taxable Pay and Previous Tax Paid have been
greater than the previous tax paid on the P11. entered.
The previous tax paid on P11 is not 0 so the previous Verify that accurate previous Taxable Pay and Previous Tax Paid have been
taxable pay on P11 cannot be 0. entered.
Only one PAYE component on a calculation card can report If the Report NI YTD Value is checked on the PAYE component then there
NI YTD values at any time. cannot be another PAYE component with this field checked on the same
calculation card for the same date effective range.

Message Resolution
The reason to withhold tax is not one of the valid reasons. Provide a valid value for reason to withhold tax.
The number of periods covered must be between 1 and 99. The number of periods covered cannot exceed two digits in length.
You must enter a manual issue date for the P45 update. If the action is manual issue, the P45 manual issue date is required.
The P45 action cannot be updated because the P45 was If the current action is Issue when final pay on or after actual termination date
already processed. or Issue when final pay in prior period then the user will not be able to update
the action if the record has been archived.
You must not enter a P45 manual issue date for this update. If the current action is Issue when final pay on or after actual termination date,
Issue when final pay in prior period or Do not file, the Manual Issue Date must
be left blank.
The PAYE component detail cannot be deleted because a If the P45 Manual Issue Date is populated or if the P45 has been archived the
P45 was already issued. PAYE Component Detail will not be able to be deleted.
You cannot update or delete the new starter record because If a PAYE child context has been filed it cannot be updated or deleted, unless
it was already reported. the filing is rolled back.
You cannot make date-effective updates to a new starter A PAYE child context can only be corrected (it cannot be updated through
record. You can make corrections only. update insert mode).
This is already associated with a component of this type, so Terms can only be associated to one PAYE and NI component on any date.
cannot be associated with another of the same type.
You can associate with both PAYE and NI components only Terms cannot be associated to PAYE and NI components subscribed to
on the same calculation card. different calculation cards.
You cannot add association details to this PAYE component Terms cannot be associated to PAYE components once a P45 is issued
because a P45 was issued. against the PAYE component.
You cannot remove the association details from this Term associations can only be deleted against NI and PAYE components, if
component because payroll actions exist for it. there aren’t any payroll actions for that term yet against the component.
You cannot end date the association details for this Term associations can only be end dated against NI and PAYE components,
component because they were processed beyond this end if the term has not been processed beyond this end date.
date.
You can only correct an association detail. The term or calculation component of an association detail can only be
corrected.
You cannot correct this association detail because payroll The term or calculation component of an association detail cannot be
actions exist. modified if the record has any payroll actions against it, during its effective
period.
Note that some of the validation that is enforced via the user interface cannot be enforced whilst loading records via
HDL. We would therefore advise that you run either the Payroll Validation Report or the Diagnostic report after
loading Statutory Deduction records via HDL.
Those error conditions are:
Message Resolution
An active calculation card of this type for this tax There can be only one effective Statutory Deductions calculation card
reporting unit already exists. related to a specific TRU on any date, for a payroll relationship.

Message Resolution
You cannot create this association because a Statutory A Statutory Deductions calculation card can have only one TRU
Deductions calculation card can have only one association.
association.
An active calculation card of this type, with no There can be only one active Statutory Deductions card that is not
associations, already exists. associated to a TRU at any one time.
The priority period type is invalid for the combination of A priority period type is entered for the calculation component, but it
association details with this calculation card. does not correspond to one of the payroll frequencies assigned to one of
the component associations.
You must enter a priority period type because there are If there are multiple component associations with different payroll
association details with different payroll frequencies. frequencies, the priority period type must be entered so that the payroll
run can process these associations with that same frequency.
NI category {NI_CATEGORY} is not valid for the current The NI category is dependent upon the certificate entered on the
certificate. Aggregation Information. Select a valid NI Category for the certificate.
Pension basis {PENSION_BASIS} is not valid for the The pension basis field is dependent upon the NI category.
current NI category {NI_CATEGORY}.

Pensions Automatic Enrolment Calculation Cards
The Pensions Automatic Enrolment card stores the employee’s situation related to Pensions Automatic Enrolment,
such as the employee’s eligibility for pension, which qualifying pension scheme they are enrolled into, and opt-in and
opt-out details. A default card is generated automatically when an employee record is created by the New Hire flow
(if the license is set to Payroll or Payroll Interface).
By default, an employee’s classification is set to Not Yet Assessed. If a TRU is provided for the employee during
the New Hire flow, the Pensions Automatic Enrolment card is associated automatically to that TRU. The Pensions
Automatic Enrolment process can then be run on a regular basis to assess the employee’s eligibility to Pensions
Automatic Enrolment and make all the relevant updates to the card. If the employee is found eligible, a Benefits and
Pensions card is also created automatically by the process for the default Qualifying Pension Scheme.
There may be instances where mass upload is required for the Pensions Automatic Enrolment card:
• During implementation for data migration :
o Employees Pensions Automatic Enrolment must be uploaded. This is to ensure that all relevant
information about Pensions Automatic Enrolment is migrated from your legacy system. When
you use HDL to migrate the employees’ records, a card is generated with the default
classification of Not Yet Assessed. This needs to be edited to reflect the employee current
status (else they will be re-enrolled the first time the Pensions Automatic Enrolment process is
run in Oracle Fusion Payroll).
• Ongoing bulk updates:
o Bulk Load of New Hire data: if you need to mass upload New Hire information, a default
Pensions Automatic Enrolment card may be generated automatically (if the New Hire records are
created using HDL or the interface with Taleo). In this case you may need to update the card if
the defaulted data is not relevant.
o Bulk upload of Pensions Automatic Enrolment information: in the case where some of the
Pensions Automatic enrolment is managed by a third party such as opt-in, opt-out, and
notification letters, information obtained from the third party must be uploaded to Oracle Fusion
Payroll.
It is recommended to have a good understanding of the Pensions Automatic Enrolment card and the information it
contains prior to attempting mass upload. For further information, see Oracle Fusion HCM (United Kingdom):
Pensions Automatic Enrolment and Functional Considerations (Doc ID 2006584.1).
Considerations and Prerequisites for Pensions Automatic Enrolment Card

• You must have created the element eligibility for the Pensions Automatic Enrolment element.
• You must have created the Pension Deduction elements.
• When uploading Qualifying Pension Scheme via HDL, you will need to ensure that the corresponding
component exists in the Benefits and Pensions card.
Loading Pensions Automatic Enrolment Calculation Cards

You must provide the calculation card data in the CalculationCard.dat file for processing by HDL.
Pensions Automatic Enrolment cards use the following components of the Calculation Card object:

Key:
CalculationCard
CardComponent
ComponentDetail
CalculationValueDefinition
DirCardDefinitionName : Pensions Automatic Enrolment
DirCardCompDefName : Pensions Automatic Enrolment

Context1 (Reference Code) :
FLEX:Deduction Developer DF : HRX_GB_PAE (Pensions Automatic Enrolment)
FLEX:Deduction Developer DF : ORA_HRX_GB_PAE_ADNL (Pensions Automatic Enrolment Additional Information)
COMPONENTS USED FOR PENSIONS AUTOMATIC ENROLMENT
Calculation Card The Pensions Automatic Enrolment calculation card. CalculationCard
Card Component The card component for the Pensions Automatic Enrolment calculation card. CardComponent
Component Detail The component detail holds Pensions Automatic Enrolment specific ComponentDetail
information. This is defined using the Further Deduction Information
descriptive flexfields as shown in the diagram above.
Component An association between the Pensions Automatic Enrolment component and ComponentAssociation
Association the Tax Reporting Unit.
Note: If there is only one TRU in your organization, the component
association is not mandatory: by default it will automatically be associated to
the unique TRU.
If you add another component to the card, it must be associated to a TRU.
Component An Association between the Pension Automatic Enrolment component and a ComponentAssociationDetail
Association Details term or assignment.
Note: When there are multiple components on the same card, each
component must be associated to a TRU, and to Terms or Assignments.
Each of those components is explained in detail in the following sections.

Calculation Card
The discriminator CalculationCard is used to load calculation card records using HCM Data Loader. You must
enter the following CalculationCard attributes when loading a Pensions Automatic Enrolment card.
HCM Data Loader

Attribute
Name
DirCardDefinitionNam * Calculation Card The type of calculation card, that is, Pensions Automatic Enrolment.
e
AssignmentNumber * Assignment Number The assignment number for the employee for whom this calculation card is created.
The source key is not supported for the assignment record.
EffectiveStartDate * Effective Start Date The start date of the calculation card or of the update to the calculation card if you
are providing date-effective history.
EffectiveEndDate Effective End Date The end date of the Pensions Automatic Enrolment card, or, if you are providing
Figure 10: Manage Calculation Cards: Pensions Automatic Enrolment


Card Component
The Card Component represents the skeleton structure of the card. Each type of card has specific components;
each component can have one or more flexfield definitions that store the relevant data.
following CardComponent attributes must be provided when loading a Pensions Automatic Enrolment new
component.
HCM Data Loader

Attribute
EffectiveStartDate provided for the Pensions Automatic Enrolment Calculation Card
component.
EffectiveEndDate Effective End Date The end date of the Pensions Automatic Enrolment card component, or, if you are
providing date-effective history, the last day of the date-effective changes. If left
blank, this value is the end of time by default.
LegislationDiscriminator * Legislation code Optional. If not provided, it is defaulted based on the Legislative Data Group.
DirCardCompDefName * Calculation Component The component definition name. Provide one of the following values:
• Pensions Automatic Enrolment Information
• Pensions Automatic Enrolment Additional Information
LegislativeDataGroupNa * Legislative Data Group The name of the legislative data group this calculation card belongs to. This should
me match the LegislativeDataGroupName provided for the calculation card.
Context1 Reference The Pensions Automatic Enrolment reference.
DirCardId * not displayed A unique reference to the Pensions Automatic Enrolment calculation card this
component belongs to. User keys are not currently supported.
Provide the source key for the Pensions Automatic Enrolment calculation card and
add the source key hint to the attribute name, for example,
DirCardId(SourceSystemId)
Figure 11: Calculation Components

Component Detail
The Component Details holds the actual values that are used to assess and record an employee’s right to Pensions
Automatic Enrolment. Each card component comprises different component details.

following ComponentDetail attributes are commonly provided when loading a new Pensions Automatic Enrolment
cards.
HCM Data Loader

Attribute
EffectiveStartDate * Effective Start Date The start date of the card component or of the update to the card component if you are
providing date-effective history. This must be after or equal to the EffectiveStartDate
provided for the Pensions Automatic Enrolment Calculation Card component.
EffectiveEndDate Effective End Date The end date of the Pensions Automatic Enrolment card component, or, if you are
providing date-effective history, the last day of the date-effective changes. If left blank,
this value is the end of time by default.
LegislationDiscrimina Legislation Code Optional. If not provided, it is defaulted based on the Legislative Data Group.
tor
DirCardCompDefNa * Calculation Component The component definition name. Provide one of the following values:
me • Pensions Automatic Enrolment Information
• Pensions Automatic Enrolment Additional Information
DirCardCompId * not displayed A unique reference to the Pensions Automatic Enrolment card component this detail
Provide the source key for the Pensions Automatic Enrolment card component and add
the source key hint to the attribute name. For example,
DirInformationCatego * Calculation Component The information category for the Pensions Automatic Enrolment flexfield. Provide:
ry Details
• ‘HRX_GB_PAE’ for Core Pensions Automatic Enrolment information
• ‘ORA_HRX_GB_PAE_ADNL’ for Additional Pensions Automatic Enrolment
Information
FLEX: Deduction * not displayed The flexfield code. Provide the flexfield context for the data row. Two contexts are
Developer DF available and so you must provide a separate ComponentDetail record for each context:
• HRX_GB_PAE - Core Pensions Automatic Enrolment information
• ORA_HRX_GB_PAE_ADNL - Additional Pensions Automatic Enrolment Information
The flexfield segment attribute names include the context for which they apply.
HRX_GB_PAE.
_EMPLOYEE_CLAS * Employee Classification Employee’s assessment to Pensions Automatic enrolment. By default, before the PAE
SIFICATION(Deducti for Pensions process is run, the Classification is set to “Not yet assessed”.
on Developer This attribute is validated using the ORA_HRX_GB_PENSION_WORKER_STA lookup.
DF=HRX_GB_PAE)
_ELIGIBLE_JOBHOL Eligible Jobholder Date Date the employee became an Eligible jobholder.
DER_DATE(Deductio
n Developer
DF=HRX_GB_PAE)
_RE_ENROLMENT_ Re-enrolment Assessment Indicates whether the employee should only be assessed for Re-enrolment.
ASSESSMENT_ONL Only

HCM Data Loader
Attribute
Y(Deduction Supply Yes or No.

Developer
DF=HRX_GB_PAE)
_REASON_FOR_EX Reason for Exclusion Reason why an employee may be excluded from re-enrolment.
CLUSION(Deduction This attribute is validated using the ORA_HRX_GB_PAE_EXCL_REASON lookup.
Developer
DF=HRX_GB_PAE)
_OVERRIDING_WO Overriding Worker Select the appropriate Worker Postponement rule for the employee (this will override the
RKER_POSTPONE Postponement Rule Worker postponement rule set at either PSU or TRU).
MENT(Deduction This attribute is validated using the ORA_HRX_GB_PENSION_POSTP_RULE lookup.
Developer
DF=HRX_GB_PAE)
_OVERRIDING_ELI Overriding Eligible Select the appropriate Eligible Jobholder Postponement rule for the employee (this will
GIBLEJH_POSTPMN Jobholder Postponement override the Worker postponement rule set at either PSU or TRU).
T(Deduction Rule This attribute is validated using the ORA_HRX_GB_PENSION_POSTP_RULE lookup.
Developer
DF=HRX_GB_PAE)
_OVERRIDING_QUA Overriding Qualifying Select the qualifying scheme that the employee should be enrolled in during the
LIFYING_SCHEME( Scheme Name Pensions Automatic Enrolment process.
Deduction Developer This attribute is validated using the
DF=HRX_GB_PAE)
ORA_HRX_GB_PENSION_QUALIFYING_PENSION_SCHEME valueset.
_ACTIVE_POSTPON Active Postponement Type The active postponement type indicates the type of postponement the employee is
EMENT_TYPE(Dedu currently subject to.
ction Developer This attribute is validated using the ORA_HRX_GB_PENSION_POST_TYPE lookup.
DF=HRX_GB_PAE)
_ACTIVE_POSTPON Active Postponement Rule The active postponement rule indicates which postponement rule currently applies to the
EMENT_RULE(Dedu employee.
ction Developer This attribute is validated using the ORA_HRX_GB_PENSION_POSTP_RULE lookup.
DF=HRX_GB_PAE)
_ACTIVE_POSTPON Active Postponement End End date of the current postponement.

EMENT_END_DATE Date
DF=HRX_GB_PAE)
_ACTIVE_QUALIFYI Active Qualifying Scheme Name of the Qualifying Pension Scheme the employee is currently enrolled in.
NG_SCHEME(Deduc Name
tion Developer
DF=HRX_GB_PAE)
_QUALIFYING_SCH Qualifying Scheme Joining Indicates the method by which the employee joined the Qualifying Pension scheme
EME_JOIN_METHO Method (such as Opt-in or Manually enrolled)
D(Deduction This attribute is validated using the ORA_HRX_GB_PENSION_JOIN_METHOD lookup.
Developer
DF=HRX_GB_PAE)
_QUALIFYING_SCH Qualifying Scheme Joining Date on which the employee enrolled into the Qualifying Pension Scheme.
EME_JOIN_DATE(D Date
eduction Developer
DF=HRX_GB_PAE)
_QUALIFYING_SCH Reason for Leaving Reason the employee left the Qualifying Pension Scheme.
EME_LEAVE_REAS Qualifying Scheme The attribute is validated using the ORA_HRX_GB_PENSION_LEAVE_REASN lookup.
ON(Deduction
Developer

HCM Data Loader
Attribute
DF=HRX_GB_PAE)
_QUALIFYING_SCH Qualifying Scheme Date on which the employee left the Qualifying Pension Scheme.
EME_LEAVE_DATE( Leaving Date
Deduction Developer
DF=HRX_GB_PAE)
_OPT_OUT_PERIOD Opt-Out Period End Date An employee found to be an eligible jobholder has a certain period of time during which
_END_DATE(Deducti he or she has the right to opt-out. This indicates the end date of the opt-out period.
on Developer
DF=HRX_GB_PAE)
_OPT_OUT_REFUN Opt-Out Refund Due If an employee opted-out after pension contributions were taken, he or she might be
D_DUE(Deduction entitled to a refund of the contributions.
DF=HRX_GB_PAE)
_JOINING_SCHEME Joining Scheme This field is hidden but required for processing.
_PROCESSED_DAT Processed Date
E(Deduction
Developer
DF=HRX_GB_PAE)
_LEAVING_SCHEM Leaving Scheme This field is hidden but required for processing.
E_PROCESSED_DA Processed Date
TE(Deduction
Developer
DF=HRX_GB_PAE)
_CLASSIFICATION_ Classification Change This field is hidden but required for processing.
CHANGED_PROC_ Processed Date
DT(Deduction
Developer
DF=HRX_GB_PAE)
_ACTIVE_POSTPON Active Postponement This field is hidden but required for processing.
EMENT_PROC_DAT Processed Date
E(Deduction
Developer
DF=HRX_GB_PAE)
_PAYROLL_FOR_P Payroll for Pay Reference Indicates the payroll that needs to be used to identify the Pay Reference Period.
AY_REF_PERIOD(D Period
eduction Developer
DF=HRX_GB_PAE)
_OVERRIDING_STA Overriding Staging Date Employee can have an individual staging date (date when the Pensions Automatic
GING_DATE(Deducti Enrolment becomes applicable to them). That date overrides the PSU staging date.
on Developer
DF=HRX_GB_PAE)
_QUALIFYING_SCH Qualifying Scheme Each Qualifying Pension scheme needs to be created as an element using the Manage
EME_ID(Deduction Component Element task. This will generate the element, as well as a component in the Pension &
Developer Benefit calculation card.
DF=HRX_GB_PAE) This is the name of the Pension component corresponding to the Qualifying Pension
scheme the employee is enrolled in.
It is populated automatically by the Pensions Automatic Enrolment process, but can also
be uploaded.
Note: When uploading this information via HDL you need to make sure that the
corresponding component in the Pensions and Benefits card already exists.

HCM Data Loader
Attribute
_RE_ENROLMENT_ Automatic Re-enrolment Date on which the employee was re-enrolled into a pension scheme.
DATE(Deduction Date
Developer
DF=HRX_GB_PAE)
_QUALIFYING_SCH Qualifying Scheme Start Start data of the qualifying scheme.

EME_START_DATE( Date
Deduction Developer
DF=HRX_GB_PAE)
_LETTER_TYPE_GE Letter Type Type of letter generated by the process, based on the employee’s classification.
NERATED(Deduction This attribute is validated using the ORA_HRX_GB_PAE_LETTER_TEMPLATE lookup.
Developer
DF=HRX_GB_PAE)
_LETTER_STATUS( Letter Status Status of the letter

Deduction Developer This attribute is validated using the ORA_HRX_GB_PAE_LETTER_STATUS lookup.
DF=HRX_GB_PAE)
_LETTER_TYPE_DA Date Letter Generated The date on which the letter was generated.
TE(Deduction
Developer
DF=HRX_GB_PAE)
_SUBSEQUENT_CO Subsequent Indicates whether subsequent Pensions Automatic Enrolment letters are required.
MMS_REQ(Deductio Communication Required Supply Yes or No.
n Developer
DF=HRX_GB_PAE)
_LETTER_HISTORY Letter History If the employee was previously issued with the letter type N, this needs to be brought
(Deduction Developer forward to Oracle Fusion.
DF=HRX_GB_PAE) Supply N.
ORA_HRX_GB_PAE_ADNL.
_PROC_AUTO_REE Overriding Automatic Re- Employee can have an individual re-enrolment date (date when the Pensions Automatic
NROLMENT_DATE( enrolment Date Re-enrolment becomes applicable to them). That date overrides the date set at
Deduction Developer organization level.
DF=ORA_HRX_GB_
PAE_ADNL)
_WULS_TAKEN_DA Winding Up Lump Sum Date on which the employee received a Winding Up Lump Sum.
TE(Deduction payment Date
Developer
DF=ORA_HRX_GB_
PAE_ADNL)
_NOTIFICATION_DA Notice Given Date Date on which the employee gave notice of termination. This date is derived from the
TE(Deduction notification date on the Manage Termination.
Developer
DF=ORA_HRX_GB_
PAE_ADNL)
_NOTIFICATION_WI Notice Withdrawn Date Date on which the employee withdrew his or her notice of termination.
THDRAWAL_DATE(
Deduction Developer
DF=ORA_HRX_GB_
PAE_ADNL)

Figure 12: Calculation Component Details
Component Association
The component association allows the Pensions Automatic Enrolment component to be associated to a tax reporting
unit.
The discriminator ComponentAssociation is used to load component association records using HCM Data Loader.
The following ComponentAssociation attributes are commonly provided when loading a new Pensions Automatic
Enrolment card.
COMPONENT ASSOCIATION ATTRIBUTES
HCM Data Loader

Attribute
EffectiveStartDate * Effective Start Date The start date of the card Association or of the update to the card association if you
EffectiveStartDate provided for the Pensions Automatic Enrolment Card component.
EffectiveEndDate Effective End Date The end date of the Pension Automatic Enrolment card component, or, if you are

LegislativeDataGroup * Legislative Date Group The name of the legislative data group this calculation card belongs to. This should
Name match the LegislativeDataGroupName provided for the calculation card.
TaxReportingUnitNam * Tax Reporting Unit The name of the tax reporting unit to associate Pension Automatic Enrolment
e component with.
DirCardCompId(Sourc * not displayed User keys are not currently supported; you must therefore provide a source key. The
eSystemId) combination of SourceSystemOwner and SourceSystemId serves as unique
reference for the record being created or modified.
Figure 13: Component Association

Component Association Details

The component association detail allows the components of the Pensions Automatic Enrolment card to be
associated to a term or assignment.
The discriminator ComponentAssociationDetail is used to load card association records using HCM Data Loader.
The following ComponentAssociationDetail attributes are commonly provided when loading a new Pensions
Automatic Enrolment card.
Note: Only in case of multiple Pensions Automatic Enrolment components on the same card, the component
association details are required.
COMPONENT ASSOCIATION DETAILS ATTRIBUTES
HCM Data Loader

Attribute
EffectiveStartDate * Effective Start Date The start date of the component association detail or of the update to the association
details if you are providing date-effective history. This must be after or equal to the
EffectiveStartDate provided for the Pensions Automatic Enrolment Calculation Card
component.
EffectiveEndDate Effective End Date The end date of component association detail or, if you are providing date-effective
history, the last day of the date-effective changes. If left blank, this value is the end of
time by default.
DirCardCompId * not displayed A unique reference to the Pensions Automatic Enrolment card component this detail

HCM Data Loader
Attribute

Provide the source key for the Pensions Automatic Enrolment card component and
add the source key hint to the attribute name. For example,
DirRepCardId * not displayed A unique reference to the card association these details belong to. User keys are not
assignments, the component could be associated to a different assignment from the
Figure 14: Association Details

Pensions Automatic Enrolment calculation card Errors

You may experience errors while loading Pensions Automatic Enrolment calculation cards if the data is not provided
as expected. Some of the more commonly occurring errors are:
Message Resolution
You cannot modify overriding postponement When there is an active jobholder postponement, the jobholder
{OVERRIDING_POSTPONEMENT} if that postponement type is postponement rule cannot be changed.
active.
You cannot set the qualifying pension scheme joining method to The qualifying pension scheme joining method cannot be set to opt in for
opt in when an employee has classification an employee who is not a noneligible jobholder.
{EMPLOYEE_CLASSIFICATION}.
You must enter a value for the staging date. A Staging Date must be provided at either PSU or Payroll Relationship
level.
You can enter an eligible jobholder date only if the employee is Eligible jobholder date cannot be entered when the employee
classified as an eligible jobholder. classification is not eligible jobholder.
You must enter an eligible jobholder date when attribute Eligible jobholder date is mandatory when the employee’s classification is

Message Resolution
employee classification is eligible jobholder. eligible jobholder.
The postponement formula must be one of the valid This error occurs because a value for postponement formula was
postponement formula values. supplied but this value does not exist in the valid list of options.
The postponement rule must be one of the valid postponement This error occurs if a value for postponement rule was supplied but this
rule values. value does not exist in the valid list of options.
You cannot enter deferment {POSTPONEMENT_TYPE} for an An eligible jobholder postponement was selected for an employee who is
employee with classification {EMPLOYEE_CLASSIFICATION}. not classified as an eligible jobholder.
You cannot enter an active postponement end date later than When the active postponement rule is manual, the active postponement
{MAX_POSTPONEMENT_END_DATE}. end date cannot exceed 3 months after the pension date.
The qualifying pension scheme must be one of the valid This error occurs because a value for qualifying pension scheme was
qualifying pension scheme values. supplied but this value does not exist in the valid list of options.
You can select automatic enrolment for qualifying scheme joining The qualifying pension scheme joining method has been set to automatic
method only when employee is classified as an eligible jobholder. enrollment but the employee is not an eligible jobholder.
The end of DB or hybrid transitional period must be a date prior This error occurs if the user has specified a date beyond the allowed
to {EFF_DATE}. value.
An eligible jobholder can opt in only if that person previously left Qualifying pension scheme joining method was set to opt in for an
or opted out of a qualifying pension scheme. eligible jobholder who has not left or opted out previously.
You must enter a qualifying scheme leaving date when a Qualifying pension scheme leaving reason was entered without a date.
qualifying scheme leaving reason is entered.
You must enter a qualifying scheme leaving reason when a Qualifying pension scheme leaving date was entered without a reason.
qualifying scheme leaving date is entered.
You can enter attribute {LEAVING_VALUE} only if the employee Leaving value cannot be entered when no active qualifying pension
is participating in a qualifying scheme. scheme exists and leaving scheme processed date is null.
The qualifying scheme leaving date must be on or after the This error occurs when the leaving date entered is prior to joining date.
qualifying scheme joining date.
You can enter leaving reason of opt out only for an employee Qualifying pension scheme leaving reason cannot be set to opt out for a
who opted in or was automatically enrolled in the qualifying nonautomatically enrolled or opt-in joining type.
scheme.
The qualifying pension scheme formula and qualifying pension A value for both qualifying pension scheme formula and qualifying
scheme are mutually exclusive. pension scheme were provided. Only one of the fields can be entered.
You cannot change the active postponement rule during an The active postponement rule cannot be changed during an active
active postponement. postponement.
You can only enter a notice withdrawn date that is later than or The notice withdrawn date cannot be earlier than the notice given date for
equal to the notice given date the person.
The qualifying scheme leaving date must be on or before the opt- When the qualifying pension scheme leaving reason is opt out, the
out period end date when leaving reason is opt out. qualifying pension scheme leaving date cannot be past the opt-out period
end date.
The postponement rule requires you to enter a postponement If a user-specified formula postponement rule is specified, then a
formula. postponement formula must be entered.
The start date of the eligible jobholder postponement must be at There must be a gap between worker postponement and eligible
least one day after the worker postponement end date jobholder postponement.
{WORKER_POST_END_DATE}.
You must select an active postponement rule when an active No active postponement rule was entered when an active postponement
postponement type is selected. type exists.

Message Resolution
You can select an active postponement rule only if an active An active postponement rule value is entered when no active
postponement exists. postponement type exists.
An active postponement type of worker postponement was The selected worker postponement type is already active for this
already applied to this employee. employee.
Active postponement end date is not required when active Active Postponement End Date is not required when the active
postponement type is {ACTIVE_PP_TYPE}. postponement rule is not manual.
You must enter an active postponement end date when active Postponement end date must be entered when postponement type is
postponement type is manual. manual.
You must not enter an active postponement rule when active Active postponement rule cannot be entered when active postponement
postponement type is none. type is none.
The value of attribute {PENSION_DATE_TYPE} must be on or This error occurs if trying to enter a date prior to employer's staging date.
after the employer's staging date.
You can enter an active postponement end date only if an active Active postponement date is entered when no active postponement
postponement type is selected. exists.
You cannot enter an active postponement type for an employee An active postponement type is added to an employee who is already
who was already enrolled or belongs to a qualifying pension enrolled into a qualifying pension scheme.
scheme.
You cannot change the qualifying scheme component because The Qualifying Scheme Component cannot be changed after an
an automatic enrolment was processed already. automatic enrollment has been processed previously for the existing
Qualifying Scheme. If the employee must be enrolled in a different
Qualifying Scheme, a new Pensions Automatic Enrolment component
must be added for the employee, and the existing one end dated.
A qualifying scheme component is required to set the qualifying The Qualifying Scheme Joining Method cannot be set to 'Manually
scheme joining method to manually enrolled. enrolled' if a Qualifying Scheme Component is not entered.
You must enter a qualifying scheme joining method when a Qualifying pension scheme name cannot be entered without a qualifying
qualifying pension scheme name is entered. scheme joining date.
You must enter a joining method when you enter the qualifying Qualifying scheme name cannot be entered if the employee is not
scheme name. participating in a scheme.
You must enter a qualifying scheme name when attribute Qualifying pension scheme joining date was entered without a qualifying
{ENTRY_TYPE} is entered. pension scheme name.
Enter a date within the six-month period that starts three months The re-enrolment date can be any date within the six month period which
before the third anniversary of the staging or re-enrolment date starts three months before the third anniversary of the original staging
and up to three months after. date or the previous re-enrolment date and ends three months after that
third anniversary
A staging date or a previous re-enrolment date must exist when A re-enrolment date is entered but there is no staging date or previous re-
you enter a new re-enrolment date. enrolment date present for this PSU or TRU. Staging date or previous re-
enrolment date is required to validate the re-enrolment date being
entered to ensure it is within the valid range.
An active Pensions Automatic Enrolment card already exists for This error occurs when trying to create a second active Pensions
this payroll relationship. Automatic Enrolment card for the same payroll relationship at the same
time. There can be only one active card of this type related to a specific
payroll relationship at any one time.
This group of terms or assignments is already associated with This error occurs when attempting to associate the same group of terms
the qualifying pension scheme. or assignments to a component for the same qualifying pension scheme
when that association already exists.
Payroll for pay reference period must exist for a component when This error occurs when no payroll for pay reference period exists for a
multiple terms that are not all on the same payroll are associated component when multiple terms that are not all on the same payroll are

Message Resolution
to the component. associated to the component.

Court Orders and Student Loans Calculation Cards
The Court Orders and Student Loans card holds information on whether an employee is subject to court order or
student loan deductions, and, if yes, then what type of orders, deduction amount, protected earnings, or payee. Use
the Manage Element task to create Court Orders and Student Loans elements. When you create the element, a
card component of the same name as the element is created. Those components are then available to use on the
predefined Court Orders and Student Loans calculation card.
Unlike Statutory Deduction or Pensions Automatic Enrolment cards, the Court Order and Student Loan card is not
generated automatically. It only needs to be created for those employees who are subject to those types of
deductions. However, there may be cases where they need to be uploaded in bulk:
o Employees Court Orders and Student Loans must be migrated to Oracle Fusion to ensure that
appropriate deductions are considered. Using HDL, you must create the card and all the
necessary components and component details.
o New Hire may also have Student Loans that need to be uploaded in bulk.
It is advised to have a good knowledge of the Court Orders and Student Loans card in order to upload using HDL.
Refer to Oracle Fusion HCM (United Kingdom): Court Orders and Student Loans Implementation and Functional
Considerations (Doc ID 2009287.1) for further information.
Considerations and Prerequisites for Court Orders and Student Loan Card
» Eligibility for the following element must be created: Court Order and Student Loan
» One element must be created for each type of Court Orders and Student Loan
» Set up Third Party Payee and Third Party Payment Methods for people or organizations the payment of court
order is made to.
» Court Orders Issuing Authorities must be added to the lookup type ORA_HRX_GB_CO_ISSUE_AUTHORITY.
Loading Court Orders and Student Loans Calculation Cards

Calculation Card data must be provided in the CalculationCard.dat file for processing by HDL.
Court Orders and Student Loans cards use the following components of the Calculation Card object.

Key:
CalculationCard
CardComponent
ComponentDetail
DirCardDefinitionName : Court Orders and Student Loans
DirCardCompDefName : Court Order Information
DirCardCompDefName : <name from element template> * - Student Loan
FLEX:Deduction Developer DF : ORA_HRX_GB_SL (Student Loan)
ValueDefinitionName : Override Amount
DirCardCompDefName : <name from element template> * - Court Order
FLEX:Deduction Developer DF : ORA_HRX_GB_PCT (Court Order Percentage Deductions)
FLEX:Deduction Developer DF : ORA_HRX_GB_INVD (Involuntary Deduction Information)
FLEX:Deduction Developer DF : ORA_HRX_GB_DEO (Deduction from Earnings Order)
FLEX:Deduction Developer DF : ORA_HRX_GB_AEO (Attachment of Earnings Order Priority)
FLEX:Deduction Developer DF : ORA_HRX_GB_CMSDEO (Child Maintenance Service Deduction from Earnings Order)
ValueDefinitionName : Normal Deduction Rate
ValueDefinitionName : Protected Earnings Rate
ValueDefinitionName : Original Outstanding Debt
ValueDefinitionName : CMA Daily Deduction Rates
ValueDefinitionName : CMA Daily Protected Earnings Rate
ValueDefinitionName : EA Original Outstanding Debt

COMPONENTS USED FOR COURT ORDERS AND STUDENT LOANS CARD
Calculation Card The Court Orders and Student Loans calculation card. CalculationCard
Card Component The card component for the Court Orders and Student Loans calculation CardComponent
card. The components are not predefined but they are generated when the
Court Orders or Student Loans elements get created. The component has the
same name as the element.
Component Detail The component detail holds Court Orders and Student Loans specific ComponentDetail
information. This is defined using the Further Deduction Information descriptive
flexfield.
Only a subset of contexts is applicable based on the court order types. For
details, refer to table 1.
Calculation Value Allows the creation of value definition so that overriding values can be CalculationValueDefinition
Definition specified on the Court Orders and Student Loans card.
Only a subset of value definitions is applicable based on the court order
types. For details, refer to table 2.
Enterable Overriding value for the Calculation Value Definition. When uploading data EnterableCalculationValue
Calculation Value using HDL, value definitions and enterable calculation values have to be
created in separate lines in the .dat file. You cannot just create the enterable
calculation values.
Only a subset of value definitions is applicable based on the court order
types. For details, refer to table 2.
Card Association An association between the Court Order and Student Loan card and the Tax CardAssociation
Reporting Unit.
Component An association between the Student Loan card component and the Tax ComponentAssociation
Association Reporting Unit.
Note: Unlike Court Order components, Student Loan needs to be associated
to a TRU (and not a Term or Assignment).
Card Association An Association between the Court Order components and a term or CardAssociationDetail
Details assignment.
Each of those components is explained in detail in the following sections.

Table 1: Flex contexts applicable by Court Order type
Flex Contexts applicable by Court Order type
ORA_HRX_
ORA_HRX_
ORA_HRX_
ORA_HRX_
ORA_HRX_
ORA_HRX_
GB_CMSD
GB_INVD
GB_DEO
GB_AEO
GB_PCT
GB_SL
EO
Attachment of Earnings Order (AEO) Fines Yes Yes
Attachment of Earnings Order (AEO) Non-Priority Yes Yes
Attachment of Earnings Order (AEO) Non-Priority Northern Yes Yes

Ireland
Attachment of Earnings Order (AEO) Priority Yes Yes
Attachment of Earnings Order (AEO) Priority Northern Yes Yes

Ireland
Child Maintenance Service Deduction from Earnings Order Yes Yes
(CMSDEO)
Conjoined Arrestment Order (CAO) Yes
Council Tax Attachment of Earnings Order (CTAEO) Yes Yes
Current Maintenance Arrestment (CMA) Yes
Deduction from Earnings Order (DEO) Yes Yes
Direct Earnings Attachment (DEA) Yes Yes
Earnings Arrestment (AE) Yes
Student Loan Yes

Table 2 – Value definitions applicable by court order type
Earnings Rate
Earnings Rate
Outstanding
Outstanding
EA Original
Amount to
CMA Daily
CMA Daily
Deduction
Deduction
Protected
Protected
Override
Amount
Original
Normal
Deduct
Fixed
Debt
Debt
Rate
Rate
Attachment of Earnings Order (AEO) Fines Yes
Attachment of Earnings Order (AEO) Non- Yes Yes

Priority
Attachment of Earnings Order (AEO) Non- Yes Yes

Priority Northern Ireland
Attachment of Earnings Order (AEO) Yes Yes Yes

Priority
Attachment of Earnings Order (AEO) Yes Yes Yes

Priority Northern Ireland
Child Maintenance Service Deduction Yes - all

from Earnings Order (CMSDEO) frequenc
ies
Conjoined Arrestment Order (CAO) Yes Yes
Council Tax Attachment of Earnings Order Yes

(CTAEO)
Current Maintenance Arrestment (CMA) Yes Yes
Deduction from Earnings Order (DEO) Yes Yes
Direct Earnings Attachment (DEA) Yes Yes
Earnings Arrestment (AE) Yes
Student Loan Yes

Calculation Card
CalculationCard attributes must be provided when loading a Court Orders and Student Loans card.
HCM Data Loader

Attribute
Name
DirCardDefinitionNam * Calculation Card The type of calculation card. Provide ‘Court Orders and Student Loans’.
e
AssignmentNumber * Assignment Number The assignment number for the worker this calculation card is for. The source key is
not supported for the assignment record.
EffectiveStartDate * Effective Start Date The start date of the calculation card or the update to the calculation card if you are
providing date-effective history.
EffectiveEndDate Effective End Date The end date of the Court Orders and Student Loans card, or, if you are providing

Figure 15: Manage Calculation Cards: Court Orders and Student Loans
Card Component
following CardComponent attributes must be provided when loading a Court Orders and Student Loans new
component.
HCM Data Loader

Attribute
EffectiveStartDate provided for the Court Orders and Student Loans calculation
Calculation Card component.
EffectiveEndDate Effective End Date The end date of the Court Orders and Student Loans calculation card component, or,
if you are providing date-effective history, the last day of the date-effective changes.
If left blank, this value is the end of time by default.

LegislationDiscriminat * Legislation code Optional. If not provided, it is defaulted based on the Legislative Data Group.
or
DirCardCompDefNam * Calculation Component The component definition name. Provide the name of the component as generated
e by the element template.
Context1 * Reference The Court Order or Student Loan reference, as provided on the official notification.
ParentDirCardCompId Parent component ID Provide a unique reference to the component “Court Order Information”. User keys
are not currently supplied, so supply the source system ID and add the source key
hint to the attribute name. For example, ParentDirCardCompId(SourceSystemId).
DirCardId * not displayed A unique reference to the Court Orders and Student Loans calculation card this
Provide the source key for the Court Orders and Student Loans calculation card and
DirCardId(SourceSystemId)

Component Detail
The Component Details holds the actual values that are used to process the court orders and student loans
deductions in payroll. Each card component comprises different component details.
following ComponentDetail attributes are commonly provided when loading a new Court Orders and Student Loans
cards.
HCM Data Loader

Attribute
EffectiveStartDate * Effective Start Date The start date of the card component or the update to the card component if you are
provided for the Court Orders and Student Loans Calculation Card component.
EffectiveEndDate Effective End Date The end date of the Court Orders and Student Loans card component, or, if you are

HCM Data Loader
Attribute
LegislationDiscriminat Legislation Code Optional. If not provided, it is defaulted based on the Legislative Data Group.
or
DirCardCompDefNam * Calculation Component The component definition name. Provide the name of the component as generated by
e the element template.
DirCardCompId * not displayed A unique reference to the Court Orders and Student Loans card component this detail
Provide the source key for the Court Orders and Student Loans card component and
add the source key hint to the attribute name. For example,
DirInformationCategor * Calculation Component The information category for the Court Orders and Student Loans flexfield. Provide
y Details one of the following:
ORA_HRX_GB_SL – Student Loans
ORA_HRX_GB_CMSDEO – Court orders of type CMSDEO
ORA_HRX_GB_INVD – All court order types
ORA_HRX_GB_DEO – Court orders of type DEO
ORA_HRX_GB_AEO – Court orders of type AEO
ORA_HRX_GB_PCT – Court orders of type Fines and Council Tax
For an exhaustive list of which component details must be used based on the type of
Court Order, refer to Table 1.
FLEX: Deduction The flexfield code. Provide the flexfield context for the data row. Six contexts are
Developer DF available and so you must provide a separate ComponentDetail record for each
context.
Context is same as flexfields above.
The flexfield segment attribute names include the context for which they apply.
ORA_HRX_GB_SL.
_PLAN_TYPE((Deduc * Plan Type Type of Plan for the Student Loan as specified on the notice.
tion Developer This attribute is validated using the ORA_HRX_GB_SL_PLAN_TYPE lookup.
DF=ORA_HRX_GB_S
L)
_START_DATE(Dedu * Student Loan deduction Date when the student loan deduction must start being deducted.
ction Developer start date
DF=ORA_HRX_GB_S
L)
_START_DATE_NOTI Start Notice Date of Issue Start date of the Student Loan as per SL1 notice.
CE(Deduction SL1
Developer
DF=ORA_HRX_GB_S
L)
_STOP_DATE(Deduct Student Loan deduction Date when the student loan deduction must stop being deducted.
ion Developer stop date
DF=ORA_HRX_GB_S
L)
_STOP_DATE_NOTI Stop Notice Date of Issue End date of the Student Loan as per SL2 notice
CE(Deduction SL2
Developer
DF=ORA_HRX_GB_S
L)

HCM Data Loader
Attribute
_TEACHER_REPAY Eligibility for Repayment of Yes or No

MENT(Deduction Teachers Loans
Developer
DF=ORA_HRX_GB_S
L)
ORA_HRX_GB_CMSDEO.
_UNDERPAY_REAS Underpayment Reason Reason for underpayment of the CMSDEO.

ON(Deduction This attribute is validated using the ORA_HRX_GB_CMSDEO_UNDERPAY_RSN
Developer lookup.
DF=ORA_HRX_GB_C
MSDEO)
_FREQUENCY(Deduc * Frequency Normal deduction rate frequency for the CMSDEO.

tion Developer This attribute is validated using the ORA_HRX_GB_CMS_DEO_FREQUENCY lookup.
DF=ORA_HRX_GB_C
MSDEO)
ORA_HRX_GB_AEO.
_FREQUENCY(Deduc * Frequency Normal deduction rate frequency for the AEO.

tion Developer This attribute is validated using the ORA_HRX_GB_CO_FREQUENCY lookup.
DF=ORA_HRX_GB_A
EO)
ORA_HRX_GB_INVD.
_DATE_OF_ISSUE(D * Date of Issue Issue date of the Court Order.

eduction Developer
DF=ORA_HRX_GB_I
NVD)
_DATE_OF_RECEIPT Date of Receipt Date of receipt of the official notification of the court order by the employer.
DF=ORA_HRX_GB_I
NVD)
_ISSUING_AUTHORI * Issuing Authority Authority who issued the court order.

TY(Deduction This attribute is validated using the ORA_HRX_GB_CO_ISSUE_AUTHORITY lookup.
Developer
DF=ORA_HRX_GB_I
NVD)
_THIRD_PARTY_PAY * Payee For Order Amount If the court order payment is made through Oracle Fusion Payroll, indicate the payee.
EE(Deduction It must have been set up as a third-party payee with a third-party payment method
Developer associated to it.
DF=ORA_HRX_GB_I
NVD)
ORA_HRX_GB_DEO.
_CALCULATION_TYP * Calculation Type Calculation type for the court order of type DEO (Post 2003 assessment or not).
E(Deduction This attribute is validated using the ORA_HRX_GB_DEO_CALC_TYPE lookup.
Developer
DF=ORA_HRX_GB_D
EO)

HCM Data Loader
Attribute
_FREQUENCY(Deduc * Frequency Normal deduction rate frequency for the DEO.

tion Developer This attribute is validated using the ORA_HRX_GB_CO_FREQUENCY lookup.
DF=ORA_HRX_GB_D
EO)
ORA_HRX_GB_PCT.
_PRIMARY_PAYROL * Primary Earnings Payroll If the employee has multiple assignments on different payrolls, indicate which payroll is
L(Deduction the primary one.
Developer
DF=ORA_HRX_GB_P
CT)
Figure 17: Calculation Component Details – Student Loan


Figure 18: Calculation Component Details – Child Maintenance Service Deduction from Earnings Order
Figure 19: Calculation Component Details – Involuntary Deduction Information


Figure 20: Calculation Component Details – Attachment of Earnings Order Priority
Figure 21: Calculation Component Details – Deduction from Earnings Order

Calculation Value Definition

The calculation value definition allows the creation of rate definition, so that overriding rates can be provided on the
Court Orders and Student Loans calculation card.
The discriminator CalculationValueDefinition is used to load calculation value definition records using HCM Data
Loader. The following CalculationValueDefinition attributes are commonly provided when loading a new Court
Orders and Student Loans card.
CALCULATION VALUE DEFINITION ATTRIBUTES
HCM Data Loader

Attribute

HCM Data Loader
Attribute
provided for the Court Orders and Student Loans Calculation Card component.
DirCardCompDefNam * Calculation component The component definition name as generated by the element template.
e
ValueDefinitionName * Value Definition Name Name of the value definition. Provide one of the following:
• Normal Deduction Rate
• Protected Earnings Rate
• Original Outstanding Debt
• CMA Daily Deduction Rate
• CMA Daily Protected Earnings Rate
• EA Original Outstanding Debt
• Override Amount
You must create one line per value definition you need to create. For the list of Value
Definition applicable for each type of card, refer to Table 2.
or
Enterable Calculation Value

The enterable calculation value allows the creation of the actual value of the calculation value definition created
above.
The discriminator EnterableCalculationValue is used to load enterable calculation value records using HCM Data
Loader. The following EnterableCalculationValue attributes are commonly provided when loading a new Court
Orders and Student Loans card.
ENTERABLE CALCULATION VALUE ATTRIBUTES
HCM Data Loader

Attribute
EffectiveStartDate provided for the Court Orders and Student Loans Calculation
Card component.

HCM Data Loader
Attribute
or
*Value1 * Value Value of the rate definition for that court order.
ValueDefnId * not displayed Supply a unique reference to the Calculation Value Definition this record belongs to.
User keys are not currently supported. Provide the source key Calculation Value
Definition component and add the source key hint to the attribute name. For
example, ValueDefnId(SourceSystemId).
Figure 22: Enterable Calculation Values

Card Association
The card association allows the Court Orders and Student Loans card to be associated to a tax reporting unit.
CardAssociation attributes are commonly provided when loading a new Court Orders and Student Loans card.
HCM Data Loader

Attribute
EffectiveStartDate * Effective Start Date The start date of the card association or the update to the card association if you are
provided for the Court Orders and Student Loans Card component.

HCM Data Loader
Attribute
EffectiveEndDate Effective End Date The end date of the card association, or, if you are providing date-effective history,
the last day of the date-effective changes. If left blank, this value is the end of time by
default.
TaxReportingUnitNam * Tax Reporting Unit The name of the tax reporting unit to associate the Court Orders and Student Loans
e card with.
TruBatchId This is not applicable for this type of card. Do not supply.
DirCardId * not displayed A unique reference to the Court Orders and Student Loans calculation card this
Provide the source key for the Court Orders and Student Loans calculation card and
DirCardId(SourceSystemId).
Figure 23: Associations


The card association detail allows Court Orders components to be associated to a term or assignment.
The following CardAssociationDetail attributes are commonly provided when loading a new Court Orders and
Student Loans card.

Note: Only Court Orders components need card association details. Student Loans components are associated to a
TRU.
HCM Data Loader

Attribute
EffectiveStartDate * Effective Start Date The start date of the component association detail or the update to the association
EffectiveStartDate provided for the Court Orders and Student Loans Calculation
Card component.
history, the last day of the date-effective changes. If left blank, this value is the end of
time by default.
DirRepCardId * not displayed A unique reference to the card association these details belong to. User keys are
not currently supported.
attribute name, for example, DirRepCardId (SourceSystemId).
DirCardCompId * not displayed A unique reference to the card component being associated. User keys are not
attribute name, for example, DirCardCompId (SourceSystemId).
assignments, the component could be associated to a different assignment from the
Figure 24: Association Details


Component Association
The component association allows the Student Loans card component to be associated to a tax reporting unit.
The discriminator ComponentAssociation is used to load component association records using HCM Data Loader.
The following ComponentAssociation attributes are commonly provided when loading a new Court Orders and
Student Loans card.
Note: Only the Student Loan component needs to be associated to a TRU.
COMPONENT ASSOCIATION ATTRIBUTES
HCM Data Loader

Attribute
EffectiveStartDate * Effective Start Date The start date of the component association or the update to the component
association if you are providing date-effective history. This must be after or equal to
the EffectiveStartDate provided for the Court Orders and Student Loans Card
component.
EffectiveEndDate Effective End Date The end date of component association, or if you are providing date-effective history,
the last day of the date-effective changes. If left blank, this value is the end of time by
default.
LegislativeDataGroup * Legislative Date Group The name of the legislative data group this calculation card belongs to. This should
TaxReportingUnitNam * Tax Reporting Unit The name of the tax reporting unit to associate the Court Orders and Student Loans
e component with.
TruBatchId Unique ID This is not applicable for this type of card.
DirCardCompId * not displayed A unique reference to the card component this association is for. User keys are not
attribute name. For example, DirCardCompId(SourceSystemId).

Figure 25: Component Association
Court Orders and Student Loans Calculation Card Errors

You may experience errors while loading Court Orders and Student Loans calculation card if the data is not provided
as expected. Some of the more commonly occurring errors are:
Message Resolution
You cannot enter association details for a calculation This message is raised when the user tries to setup court order and student
component if the calculation component is already loan associations incorrectly. The user must not create court order association
associated with a tax reporting unit. details under the parent student loan association. The valid setup for court
orders is one association row for TRU association, and one or more
association detail rows associating the earnings to the court orders
component. The valid setup for student loans is one association row for TRU
+ component association together, and no rows for association details.
You must use a single calculation type for each Deduction of You cannot create more than one Deduction of Earnings Order with different
Earnings Order. calculation types.
Fixed amount must be less than the original outstanding The fixed amount override value must be less than the original outstanding
debt. debt override value.
You must enter a frequency if you enter a fixed amount. When a fixed amount override value is provided, the frequency must be
provided too.
You cannot remove this component because payroll actions The calculation component cannot be deleted as it was processed by a
exist. payroll run.
The calculation card type {CARD_TYPE} is not supported for Involuntary Deductions and Obligatory Deductions are global solutions and
the UK. Use the calculation card type Court Orders and not supported for the UK.
Student Loans.
Date of Issue must be equal or later than {DATE}. The date of issue for certain court order types must be equal or later than a
specific date.

Message Resolution
CAO cannot be entered if a CMA or EA exist, or vice versa. CAO entry cannot be created when CMA or EA court order type already
exists, or vice versa. CAO and CMA/EA are mutually exclusive.
The classification type {CLASSIFICATION} for an issuing The maximum number of Council Tax Attachment of Earnings Orders or
authority cannot exceed {NUMBER}. Attachment of Earnings Order Fines for the same issuing authority is
exceeded.
This court order type cannot have multiple entries. Multiple entries of the same court order type are created where multiple
entries are not allowed. Only certain court order types are allowed to have
multiple entries.
You cannot update this component because payroll actions The component cannot be updated because it has already been processed in
exist for it. payroll run.
The student loan deduction start date must be equal to or Verify the student loan deduction start date: it must be equal to or later than
later than the start date notice of issue. the start date notice of issue.
The student loan deduction stop date must be equal to or Verify the student loan deduction stop date: it must be equal to or later than
later than the deduction start date. the deduction start date.
The student loan deduction stop date must be equal to or Verify the student loan deduction stop date: it must be equal to or later than
later than the stop date notice of issue. the stop date notice of issue.
Court order reference must be unique for each court order. A court order with the same reference already exists. Make sure the reference
is unique.
Corrections to the current court order reference are allowed. Updates to court order references are not allowed, only corrections.
Update is not permitted.
The student loan value is not a valid student loan value. A value for student loan has been provided but this value does not exist in the
valid list of student loan values.
Note: Some of the validation that is enforced through the user interface cannot be enforced whilst loading record
using HDL. It is recommended that you run the Diagnostic report after loading Court Orders and Student Loans
records using HDL. Those error conditions are:
Message Resolution
CMA daily protected earnings rate is required if a CMA daily The user attempts to create a Conjoined Arrestment Order with CMA daily
deduction rate exists. deduction rate without entering CMA daily protected earnings date.
Override value is required for either Earning Arrestment You cannot create a Conjoined Arrestment Order without entering Earning
Order or Current Maintenance Arrestment Order, or both. Arrestment override or Current Maintenance Arrestment override value
An override value is required for the override type Certain override values are required for the type of court order being created.
{OVR_TYPE}.

Benefits and Pensions Calculation Cards
The Benefits and Pensions calculation card stores information about the benefits and pension schemes an
employee is enrolled into. For the UK, the Benefits and Pensions card is an integral part of the Pensions Automatic
Enrolment solution, as it records the qualifying pension scheme an employee has been enrolled in as the result of
the Pension Automatic Enrolment process.
There are two ways a Benefits and Pensions card can be attached to an employee’s record:
- By the Pensions Automatic Enrolment process: When an employee is found to be eligible for Pensions
Automatic Enrolment by the Pensions Automatic Enrolment Process, a Benefits and Pensions card is
generated automatically based on the default qualifying scheme.
- Created manually by the Payroll Manager or Payroll Administrator
There are cases where the Benefits and Pensions card may need to be created or updated in bulk:
o In order to process pension deductions accurately for those employees who are already enrolled
in a pension scheme (whether qualifying or not), the pension contribution information need to be
brought forward to Oracle Fusion Payroll.
o Bulk upload of pension rate: When employees are enrolled into a pension scheme (whether
qualifying or not), employees may be allowed to choose the rate at which they want to contribute
(either using Oracle Fusion Benefits or third party). These rates are stored as an override on the
employee Benefits and Pensions card, and need to be updated to ensure the correct contribution
is calculated (this is true for both employee and employer rate).
Considerations and Prerequisites for Benefits and Pensions Card

One element must be created for each Pension scheme for which contributions need to be processed through
Oracle Fusion Payroll. Eligibility for those elements must also be created.
Loading Benefits and Pensions Calculation Cards

Calculation Card data must be provided in the CalculationCard.dat file for processing by HDL.
Benefits and Pensions cards use the following components of the Calculation Card object.

Key:
CalculationCard
CardComponent
ComponentDetail
DirCardDefinitionName : Benefits and Pensions
DirCardCompDefName : <name from element template>
ValueDefinitionName : Payee
ValueDefinitionName : Reference Number
ValueDefinitionName : Partial Deduction Allowed
ValueDefinitionName : Percentage of Employee Contribution
ValueDefinitionName : Percentage of Employer Contribution
COMPONENTS TO BE USED FOR BENEFITS AND PENSIONS CARD
Calculation Card The Benefits and Pensions calculation card. CalculationCard
Card Component The card component for the Benefits and Pensions calculation card. The components are CardComponent
not predefined but they are generated when the Benefits or Pensions elements get
created. The component has the same name as the element.
Calculation Allows the creation of a value definition so that overriding values can be specified on the CalculationValueDefinition
Value Definition Benefits and Pensions card.
Enterable Overriding value for the Calculation Value Definition. EnterableCalculationValue

Calculation Note that when uploading data using HDL, value definitions and enterable calculation
Value values have to be created in separate lines in the .dat file. You cannot just create the
enterable calculation values.
Card Association An association between the Benefits and Pensions card and the Tax Reporting Unit. CardAssociation
Card Association An association between the components and a term or assignment. This is only required CardAssociationDetail
Details if the pension elements have been set up at term or assignment.
Each of those components is explained in details in the following sections.

Calculation Card
CalculationCard attributes must be provided when loading a Benefits and Pensions card.
HCM Data Loader

Attribute
Name
DirCardDefinitionNam * Calculation Card The type of calculation card. Supply ’Benefits and Pensions’.
e
AssignmentNumber * Assignment Number The assignment number for the worker this calculation card is for. The source key is
not supported for the assignment record.
EffectiveStartDate * Effective Start Date The start date of the calculation card or the update to the calculation card if you are
providing date-effective history.
EffectiveEndDate Effective End Date The end date of the Benefits and Pensions card, or, if you are providing date-
effective history, the last day of the date-effective changes. If left blank, this value is
the end of time by default.
Figure 26: Manage Calculation Cards: Benefits and Pensions

Card Component
following CardComponent attributes must be provided when loading a Benefits and Pensions new component.

HCM Data Loader

Attribute
EffectiveStartDate provided for the Benefits and Pensions Calculation Card
component.
EffectiveEndDate Effective End Date The end date of the Benefits and Pensions calculation card component, or, if you are
LegislationDiscriminat * Legislation code Optional. If not provided, it is defaulted based on the Legislative Data Group.
or
DirCardCompDefNam * Calculation Component The component definition name. Provide the component name as generated by the
e element template.
DirCardId * not displayed A unique reference to the Benefits and Pensions calculation card this component
Provide the source key for the Benefits and Pensions calculation card and add the

Calculation Value Definition

The calculation value definition allows the creation of rate definition, so that overriding rates can be provided on the
Benefits and Pensions calculation card.
The discriminator CalculationValueDefinition is used to load calculation value definition records using HCM Data
Loader. The following CalculationValueDefinition attributes are commonly provided when loading a new Benefits
and Pensions card.
CALCULATION VALUE DEFINITION ATTRIBUTES
HCM Data Loader

Attribute

HCM Data Loader
Attribute
SourceSystemId / * not displayed You must provide a unique reference for the record being created. User keys are
SourceSystemOwner not currently supported and so the source key must be supplied.
component.
EffectiveEndDate Effective End Date The end date of the Benefits and Pensions card component, or, if you are providing
DirCardCompDefNam * Calculation Component The component definition name as generated by the element template.
e
ValueDefinitionName * Value Definition Name Name of the value definition. Provide one of the following:
• Payee
• Reference Number
• Partial Deduction Allowed
• Percentage of Employee Contribution
• Percentage of Employer Contribution

or
Enterable Calculation Value

The enterable calculation value allows the creation of the actual value of the calculation value definition created
above.
The discriminator EnterableCalculationValue is used to load enterable calculation value records using HCM Data
Loader. The following EnterableCalculationValue attributes are commonly provided when loading a new Benefits
and Pensions card.
ENTERABLE CALCULATION VALUE ATTRIBUTES
HCM Data Loader

Attribute
provided for the Benefits and Pensions Calculation Card component.

HCM Data Loader
Attribute
or
Value1 * Value Value of the rate definition for that court order.
ValueDefnId * not displayed Supply a unique reference to the Calculation Value Definition this record belongs to.
User keys are not currently supported. Provide the source key Calculation Value
Definition component and add the source key hint to the attribute name. For
example, ValueDefnId(SourceSystemId).
Figure 28: Enterable Calculation Values

Card Association
The card association allows the Benefits and Pensions card to be associated to a tax reporting unit.
CardAssociation attributes are commonly provided when loading a new Benefits and Pensions card.
HCM Data Loader

Attribute
EffectiveStartDate * Effective Start Date The start date of the card Association or the update to the card association if you are
provided for the Benefits and Pensions Card component.
TaxReportingUnitNam * Tax Reporting Unit The name of the tax reporting unit to associate the Benefits and Pensions card with.
e
TruBatchId Unique ID This is not applicable for this type of card.

HCM Data Loader
Attribute
DirCardId * not displayed A unique reference to the Benefits and Pensions calculation card this component
Provide the source key for the Benefits and Pensions calculation card and add the
The value provided derives the value seen in the field specified in the following screen:
Figure 29: Associations


The component association detail allows the components of the Benefits and Pensions card to be associated to a
term or assignment.
The following CardAssociationDetail attributes are commonly provided when loading a new Benefits and Pensions
card.
Note: Card Association Details are only required if the Pension element has been set to Term or Assignment.
HCM Data Loader

Attribute
EffectiveStartDate * Effective Start Date The start date of the component association detail or the update to the association
component.
history, the last day of the date-effective changes. If left blank, this value is the end
of time by default.
DirRepCardId * not displayed A unique reference to the card association these details belong to. User keys are
not currently supported.
DirCardCompId * not displayed A unique reference to the card component being associated. User keys are not

attribute name, for example, DirCardCompId (SourceSystemId)
key is not supported for the assignment record. If the employees has multiple
assignments, the component could be associated to a different assignment from
the one referenced in the card component.
Figure 30: Card Association Details

Changing the Logical Start and End Date

It is not possible to change either the first effective start date or the last effective end date for an existing calculation
card. Make sure that you create your calculation card records with an effective start date prior to any records that
will be referencing them.
It is possible to change the first effective start date for an existing calculation card. Include the
ReplaceFirstEffectiveStartDate attribute in your METADATA line and provide a Y value to state that the
EffectiveStartDate supplied is a change to the existing logical start date of your record.
Deletion Support for Calculation Card

It is possible to delete calculation cards using HCM Data Loader.
Care should be taken when using HCM Data Loader to delete records, as deleted records cannot be recovered. Do
not supply DELETE instructions in the same file as MERGE instructions.
All calculation card components (calculation card, card component, component details, and card association) can be
deleted using HCM Data Loader.

Note: All objects need to be deleted separately. That is, if you want to delete a card that has 2 components and
component details, you will need to provide delete rows for each of the component details, delete rows for each of
the components, and a delete row for the card.
Note: All card components can be provided in a single file EXCEPT for association details. If you need to delete a
card as well as its association details, it will be a two-steps process: first upload a file for the deletion of the
association details, then upload a file for the deletion of the other card components (card association, card
component details, card component, and card).

Annexes
Use Case 1 - Update the PAYE component details on statutory deduction card for
a new hire
Assumption – New hire records have been created using HDL or interface from Taleo Recruitment. The default
Statutory Deduction card was created during the upload process.
Test Case description:

The employee’s statutory deduction card needs to be updated with information on their P45, by updating the PAYE
Component Details (already created)
Step 1 – Retrieve required SourceID using BI Publisher.

For Update to PAYE Component Details:
- SourceSystemOwner
- SourceSystemID
To retrieve this information, you will need to define a report in Oracle Business Intelligence. Refer to Appendix 1 for
guidance.
The results of the report will either be an xls file, that can easily be converted to a spreadsheet format.
Sample report output:
PAYE component PAYE component

Step 2- Create .dat file Source ID Detail Source ID
Navigate to Data Exchange Work Area
Select Initiate Data Load

Select Calculation Card then Generate Template
Note: The sample file contains all the components and attributes available for upload via HCM Data Loader.
Example .dat file based on information above:
Information PAYE component PAYE component

from P45 Source ID Detail Source ID
Note: This is just a subset of information on the P45 for the purpose of the example.
Make sure you save into a zip file.
Step 3- Upload .dat file

Navigate to Data Exchange Work Area
Select Import and Load data
Select your zip file, then submit.

If the upload has not been successful, you can view the list of error messages via the Message icon.
Step 4 – Verify data has been uploaded correctly
Navigate to Manage Calculation Card via Payroll Calculation Work Area.
Step 5 – Run Payroll Validation report or Diagnostic report to validate loaded data.

Use Case 2 – Create a New Starter Declaration component details on statutory
deduction card for a new hire
Assumption – New hire records have been created using HDL or interface from Taleo Recruitment. The default
Statutory Deduction card was created during the upload process.

The employee’s statutory deduction card needs to be updated with new hire declaration as requested for FPS
reporting, by creating a component details called New Started Declaration under PAYE component.
Step 1 – Retrieve required GUID using BI Publisher.

For creating a new component under PAYE Component Details, the following ID are required:
- DirCardCompId(GUID)
Note: The combination of Source System ID and Source System Owner cannot be used to identify the parent
record in that case, because the Source System Owner of the parent is different from that of the child record. GUID
has to be used instead.
To retrieve this information, you will need to define a report in Oracle Business Intelligence. Refer to Appendix 1 for
guidance.
The results of the report will either be an xls file, that can easily be converted to a spreadsheet format.
Sample report output:
PAYE component
Step 2 – Create the .dat file. GUID
Example .dat file based on data above:
PAYE component New Starter

You need to provide Declaration information
GUID (per above) the Source Owner
and Source System
ID for component
detail being created.

Step 3 – Upload the .dat file as per Use Case 1.
Step 4- Verify that New Starter Declaration component details have been created successfully:

Use Case 3 – Create a new Court Order calculation card for new hires.
Assumption – New hire records have been created using HDL or interface from Taleo Recruitment. Only default
Statutory Deduction and Pension Automatic Enrolment card were created during the upload process. No Court
Order card exists for the employees.

Three new hires are subject to Student Loan. A new Court Order card needs to be created, with Court Order
Information Component, Student Loan component and Component Association.
Step 1 – Retrieve required Assignment ID – this can be retrieved via Manage Calculation Card:
Step 2 – Create the .dat file.

Example .dat file based on data above:

Step 3 – Upload the .dat file as per Use Case 1.
Step 4- Verify that Court Orders and Student Loans calculation card as well as the Student Loan component have
been created successfully:

As well as the component association:

Appendix 1 – Finding the correct
SourceSystemOwner and SourceSystemId
To be able to either update or delete business objects the SourceSystemOwner and SourceSystemId must be
used to identify the specific business object instance to be affected. This information is not visible on the UI having
been explicitly set during the HDL upload of new business objects or automatically set internally when the business
objects were created through the UI.
Oracle Business Intelligence can used to define reports to show the required information. The basic steps are
outlined below. General information on using Oracle Business Intelligence can be found here.
Navigate to Reports and Analytics.
Navigate to the Catalog.
Create a new data model to be used as the data source for the reports.

Create as many datasets (typically one per business object) as required based on SQL to extract the information
required.

Example SQL statements for each of the business objects are provided later in this section. They can be changed
as required to include extra criteria as needed e.g. restricting to a particular legislative data group, a particular card,
a particular component, etc based on the information required.
It is recommended that the different datasets representing the different business objects are linked to mimic the
business object hierarchy so that all the information shown is tied together making identification of specific business
object instances a lot easier i.e. the components that belong to each specific card, etc.

When the data model is complete it can be tested by going to the data TAB, setting the number of example rows to
be returned and then use either View or Export. The former shows the data in either a Tree or Table view while the
latter creates an XML document with the extracted data in it.

To be able to build reports on top of the data model the Save As Sample Data must be used as this creates some
reference data to be used within the report editor. This option is available when some data is being shown after the
View option is chosen.
To create a basic report you can use the Create Report option.
Select the Data Model that was created above

Select Table layout and Landscape page option as the focus is on a simple tabular list of values.
Build the report by dragging the required attributes in the required order.
Now the report is created it is possible to output the results in different formats

Using the Excel option allows for easy post processing of the result set i.e. filtering, sorting, merging data, writing of
macros, etc along with the ability to write out the rows into different formats such as csv in preparation for the .dat
file creation.
Multiple data models and reports can be created as required with a data model being reusable across multiple
reports. They are all available from the catalog once saved.
The example SQL for each business object returns some key identifiers to help ensure the correct data is found as
well as the SourceSystemOwner and SourceSystemId from the HRC_INTEGRATION_KEY_MAP table that
matches the relevant OBJECT_NAME and SURROGATE_ID for the given business object.
It should be noted that all the example SQL provided finds records as of SYSDATE and all translated values are
shown in US English. These can be changed according to specific requirements.
CalculationCard
OBJECT_NAME CalculationCard
Base Table PAY_DIR_CARDS_F
SURROGATE_ID DIR_CARD_ID + date effective dates
Links
Example SQL SELECT card.dir_card_id,

card.effective_start_date,
card.effective_end_date,
key_map.source_system_owner,
key_map.source_system_id,
RAWTOHEX(key_map.guid),
card_def.display_name,
pay_rel.payroll_relationship_number,
rel_grp.assignment_number,
ldg.name
FROM fusion.pay_dir_card_definitions_tl card_def,
fusion.pay_dir_cards_f card,
fusion.hrc_integration_key_map key_map,
fusion.pay_pay_relationships_dn pay_rel,
fusion.pay_rel_groups_dn rel_grp,
fusion.per_legislative_data_groups_tl ldg
WHERE card.dir_card_definition_id = card_def.dir_card_definition_id
AND key_map.object_name = 'CalculationCard'
AND key_map.surrogate_id = card.dir_card_id
AND pay_rel.payroll_relationship_id = card.payroll_relationship_id
AND rel_grp.payroll_relationship_id = pay_rel.payroll_relationship_id
AND rel_grp.group_type = 'A'
AND ldg.legislative_data_group_id = card.legislative_data_group_id
AND card_def.LANGUAGE = 'US'
AND ldg.LANGUAGE = 'US'
AND TRUNC(sysdate) BETWEEN card.effective_start_date
AND card.effective_end_date

CardAssociation
OBJECT_NAME CalculationCardAssociations
Base Table PAY_DIR_REP_CARDS_F
SURROGATE_ID DIR_REP_CARD_ID + date effective dates
Links PAY_DIR_CARDS_F.dir_card_id = PAY_DIR_REP_CARDS_F.dir_card_id
Example SQL SELECT rep_card.dir_rep_card_id,

rep_card.effective_start_date,
rep_card.effective_end_date,
tru.name,
rep_card.dir_card_id
FROM fusion.pay_dir_rep_cards_f rep_card,
hr_all_organization_units_tl tru
WHERE rep_card.dir_card_id IS NOT NULL
AND key_map.object_name = 'CalculationCardAssociations'
AND key_map.surrogate_id = rep_card.dir_rep_card_id
AND tru.organization_id = rep_card.tax_unit_id
AND tru.LANGUAGE = 'US'
AND Trunc(SYSDATE) BETWEEN rep_card.effective_start_date
AND rep_card.effective_end_date
CardAssociationDetail
OBJECT_NAME CalculationCardAssociationDetails
Base Table PAY_DIR_REP_CARD_USAGES_F
SURROGATE_ID DIR_REP_CARD_USAGE_ID + date effective dates
Links PAY_DIR_REP_CARDS_F.dir_rep_card_id =
PAY_DIR_REP_CARD_USAGES_F.dir_rep_card_id
Example SQL SELECT *

FROM (SELECT rep_card_usg.dir_rep_card_usage_id,
rep_card_usg.effective_start_date,
rep_card_usg.effective_end_date,
card_comp_def.component_name,
rep_card_usg.dir_rep_card_id
FROM fusion.pay_dir_rep_card_usages_f rep_card_usg,
fusion.pay_dir_rep_cards_f rep_card,
fusion.pay_dir_card_components_f card_comp,
fusion.pay_dir_card_comp_defs_tl card_comp_def
WHERE rep_card.dir_rep_card_id = rep_card_usg.dir_rep_card_id
AND rep_card.dir_card_id IS NOT NULL
AND rep_card_usg.dir_card_comp_id IS NOT NULL
AND key_map.object_name = 'CalculationCardAssociationDetails'

AND key_map.surrogate_id = rep_card_usg.dir_rep_card_usage_id
AND rel_grp.relationship_group_id =
rep_card_usg.relationship_group_id
AND card_comp.dir_card_comp_id = rep_card_usg.dir_card_comp_id
AND card_comp_def.dir_card_comp_def_id =
card_comp.dir_card_comp_def_id
AND card_comp_def.LANGUAGE = 'US'
AND Trunc(SYSDATE) BETWEEN rep_card.effective_start_date AND
rep_card.effective_end_date
AND Trunc(SYSDATE) BETWEEN rep_card_usg.effective_start_date
AND
rep_card_usg.effective_end_date
AND Trunc(SYSDATE) BETWEEN card_comp.effective_start_date AND
card_comp.effective_end_date
UNION ALL
SELECT rep_card_usg.dir_rep_card_usage_id,
NULL component_name,
fusion.pay_rel_groups_dn rel_grp
WHERE rep_card.dir_rep_card_id = rep_card_usg.dir_rep_card_id
AND rep_card.dir_card_id IS NOT NULL
AND rep_card_usg.dir_card_comp_id IS NULL
AND key_map.object_name = 'CalculationCardAssociationDetails'
AND key_map.surrogate_id = rep_card_usg.dir_rep_card_usage_id
AND Trunc(SYSDATE) BETWEEN rep_card_usg.effective_start_date
AND rep_card_usg.effective_end_date)
CardComponent
OBJECT_NAME CalculationCardComponents
Base Table PAY_DIR_CARD_COMPONENTS_F
SURROGATE_ID DIR_CARD_COMP_ID + date effective dates
Links PAY_DIR_CARDS_F.dir_card_id = PAY_DIR_CARD_COMPONENTS_F.dir_card_id

FROM (SELECT card_comp.dir_card_comp_id,
card_comp.effective_start_date,
card_comp.effective_end_date,
card_comp.context_value1,

parent_card_comp_def.component_name parent_component_name,
parent_card_comp.context_value1 parent_context_value1,
card_comp.dir_card_id
FROM fusion.pay_dir_card_components_f card_comp,
fusion.pay_dir_card_comp_defs_tl card_comp_def,
fusion.pay_dir_card_components_f parent_card_comp,
fusion.pay_dir_card_comp_defs_tl parent_card_comp_def
WHERE card_comp.parent_dir_card_comp_id IS NOT NULL
AND key_map.object_name = 'CalculationCardComponents'
AND key_map.surrogate_id = card_comp.dir_card_comp_id
AND parent_card_comp.dir_card_comp_id =
card_comp.parent_dir_card_comp_id
AND parent_card_comp_def.dir_card_comp_def_id =
parent_card_comp.dir_card_comp_def_id
AND parent_card_comp_def.LANGUAGE = 'US'
AND Trunc(SYSDATE) BETWEEN card_comp.effective_start_date
AND card_comp.effective_end_date
AND Trunc(SYSDATE) BETWEEN
parent_card_comp.effective_start_date
AND parent_card_comp.effective_end_date
UNION ALL
SELECT card_comp.dir_card_comp_id,
card_comp.effective_start_date,
card_comp.effective_end_date,
NULL parent_component_name,
NULL parent_context_value1,
card_comp.dir_card_id
FROM fusion.pay_dir_card_components_f card_comp,
WHERE card_comp.parent_dir_card_comp_id IS NULL
AND key_map.object_name = 'CalculationCardComponents'
AND key_map.surrogate_id = card_comp.dir_card_comp_id
AND card_comp.effective_end_date)

ComponentAssociation
OBJECT_NAME CalculationCardAssociations
Base Table PAY_DIR_REP_CARDS_F
SURROGATE_ID DIR_REP_CARD_ID + date effective dates
Links PAY_DIR_CARD_COMPONENTS_F.dir_card_comp_id =
PAY_DIR_REP_CARDS_F.dir_card_comp_id
Example SQL SELECT rep_card.dir_rep_card_id,

rep_card.effective_start_date,
rep_card.effective_end_date,
tru.name,
rep_card.dir_card_comp_id
FROM fusion.pay_dir_rep_cards_f rep_card,
hr_all_organization_units_tl tru
WHERE rep_card.dir_card_comp_id IS NOT NULL
AND key_map.object_name = 'CalculationCardAssociations'
AND key_map.surrogate_id = rep_card.dir_rep_card_id
AND tru.organization_id = rep_card.tax_unit_id
AND tru.LANGUAGE = 'US'
ComponentAssociationDetail
OBJECT_NAME CalculationCardAssociationDetails
Base Table PAY_DIR_REP_CARD_USAGES_F
SURROGATE_ID DIR_REP_CARD_USAGE_ID + date effective dates
Links PAY_DIR_REP_CARDS_F.dir_rep_card_id =
PAY_DIR_REP_CARD_USAGES_F.dir_rep_card_id

FROM (SELECT rep_card_usg.dir_rep_card_usage_id,

fusion.pay_dir_card_components_f card_comp,
WHERE rep_card.dir_rep_card_id =
AND rep_card.dir_card_comp_id IS NOT NULL
AND rep_card_usg.dir_card_comp_id IS NOT NULL
AND key_map.object_name =
'CalculationCardAssociationDetails'
AND key_map.surrogate_id =
rep_card_usg.dir_rep_card_usage_id
AND card_comp.dir_card_comp_id =
rep_card_usg.dir_card_comp_id
AND
rep_card.effective_end_date
rep_card_usg.effective_start_date AND
rep_card_usg.effective_end_date
AND
card_comp.effective_end_date
UNION ALL
SELECT rep_card_usg.dir_rep_card_usage_id,
NULL component_name,
fusion.pay_rel_groups_dn rel_grp
WHERE rep_card.dir_rep_card_id =
AND rep_card.dir_card_comp_id IS NOT NULL
AND rep_card_usg.dir_card_comp_id IS NULL
AND key_map.object_name =
'CalculationCardAssociationDetails'
AND key_map.surrogate_id =
rep_card_usg.dir_rep_card_usage_id
rep_card_usg.effective_start_date
AND
rep_card_usg.effective_end_date)
ComponentDetail

OBJECT_NAME CalculationComponentDetails
Base Table PAY_DIR_COMP_DETAILS_F
SURROGATE_ID DIR_COMP_DETAIL_ID + date effective dates
PAY_DIR_COMP_DETAILS_F.dir_card_comp_id
Example SQL SELECT comp_dtl.dir_comp_detail_id,

comp_dtl.effective_start_date,
comp_dtl.effective_end_date,
comp_dtl.dir_information_category,
comp_dtl.dir_card_comp_id
FROM fusion.pay_dir_comp_details_f comp_dtl,
fusion.hrc_integration_key_map key_map
WHERE key_map.object_name = 'CalculationComponentDetails'
AND key_map.surrogate_id = comp_dtl.dir_comp_detail_id
AND Trunc(sysdate) BETWEEN comp_dtl.effective_start_date
AND comp_dtl.effective_end_date
OBJECT_NAME ValueDefinition
Base Table PAY_VALUE_DEFINITIONS_F
SURROGATE_ID VALUE_DEFN_ID + date effective dates
PAY_VALUE_DEFINITIONS_F.source_id
Example SQL SELECT val_def.value_defn_id,

val_def.effective_start_date,
val_def.effective_end_date,
val_def_tl.name,
val_def.source_id
FROM fusion.pay_value_definitions_f val_def,
Fusion.pay_value_definitions_tl val_def_tl,
WHERE val_def.source_type = 'PDCC'
AND val_def_tl.value_defn_id = val_def.value_defn_id
AND key_map.object_name = 'ValueDefinition'
AND key_map.surrogate_id = val_def.value_defn_id
AND val_def_tl.language = 'US'
AND Trunc(sysdate) BETWEEN val_def.effective_start_date
AND val_def.effective_end_date
EnterableCalculationValue

OBJECT_NAME RangeItem
Base Table PAY_RANGE_ITEMS_F
SURROGATE_ID RANGE_ITEM_ID + date effective dates
Links PAY_VALUE_DEFINITIONS_F.value_defn_id = PAY_RANGE_ITEMS_F.value_defn_id
Example SQL SELECT range_itm.range_item_id,

range_itm.effective_start_date,
range_itm.effective_end_date,
range_itm.value_defn_id
FROM fusion.pay_range_items_f range_itm,
WHERE key_map.object_name = 'RangeItem'
AND key_map.surrogate_id = range_itm.range_item_id
AND Trunc(sysdate) BETWEEN range_itm.effective_start_date
AND range_itm.effective_end_date

Oracle Corporation, World Headquarters Worldwide Inquiries
500 Oracle Parkway Phone: +1.650.506.7000
Redwood Shores, CA 94065, USA Fax: +1.650.506.7200
CONNECT W ITH US
blogs.oracle.com/oracle Copyright © 2014, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
facebook.com/oracle fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
twitter.com/oracle means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
oracle.com
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0818
White Paper Title: Loading Calculation Cards for the UK Using HCM Data Loader
Author: Jo Spendeler
August 2018

Loading Calc Card With HDL

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Loading Calc Card With HDL

Hochgeladen von

Copyright:

Verfügbare Formate

Loading Calculation Cards for the United Kingdom

Using HCM Data Loader

Oracle Fusion Human Capital Management 11g Release 10 (11.1.10)

LOADING UK CARDS USING HCM DATA LOADER

LOADING UK CARDS USING HCM DATA LOADER

LOADING UK CARDS USING HCM DATA LOADER

How to Use the Information in This Document

• Considerations and Prerequisites What to consider before attempting to load data

1 | LOADING CALCULATION CARDS FOR THE UK USING HCM DATA LOADER

2 | LOADING UK CARDS USING HCM DATA LOADER

• Pensions Automatic Enrolment

• Court Orders and Student Loans

• Benefits and Pensions

HCM Data Loader scope

3 | LOADING UK CARDS USING HCM DATA LOADER

Following is the list of references:

Business Object Business Object Reference(s)

CardAssociation (DirRepCardId) DirCardId(SourceSystemId)

CardComponent (DirCardCompId) DirCardId(SourceSystemId)

ComponentAssociation (DirRepCardId) DirCardCompId(SourceSystemId)

CalculationValueDefinition (ValueDefnId) SourceId(SourceSystemId) – this is a reference to appropriate

4 | LOADING UK CARDS USING HCM DATA LOADER

5 | LOADING UK CARDS USING HCM DATA LOADER

6 | LOADING UK CARDS USING HCM DATA LOADER

• During implementation for data migration:

• Ongoing bulk updates

Prerequisites for Statutory Deductions Card

7 | LOADING UK CARDS USING HCM DATA LOADER

Calculation Card Hierarchy

COMPONENTS USED FOR STATUTORY DEDUCTIONS CARD

Component Functional Description Discriminator

Calculation Card The Statutory Deductions calculation card. CalculationCard

Card Association between the components and Term or Assignment. CardAssociationDetail

The following section explains each component listed above:

8 | LOADING UK CARDS USING HCM DATA LOADER

CALCULATION CARD ATTRIBUTES

HCM Data Loader

9 | LOADING UK CARDS USING HCM DATA LOADER

CARD COMPONENT ATTRIBUTES

HCM Data Loader

10 | LOADING UK CARDS USING HCM DATA LOADER

Figure 2: Calculation Components – Aggregation Information, NI & PAYE

COMPONENT DETAIL ATTRIBUTES

HCM Data Loader

11 | LOADING UK CARDS USING HCM DATA LOADER

DirCardCompDefNa * Calculation Component The component definition name. Provide:

_CERTIFICATE(Ded Certificate Certificate as required for certain NI Categories.

12 | LOADING UK CARDS USING HCM DATA LOADER

_NIC_REFUND(Ded NIC Refund Yes or No

_TAX_CODE(Deducti * Tax Code Employee’s tax code

13 | LOADING UK CARDS USING HCM DATA LOADER

_PENSIONER(Deduc Pensioner Indicates whether the employee is a pensioner. Supply Yes or No

_REASON_TO_WIT Reason to Withhold Tax Reason for withholding a tax refund.

14 | LOADING UK CARDS USING HCM DATA LOADER

_NS_STATEMENT(D * Statement Statement that fits this employee's employment.

15 | LOADING UK CARDS USING HCM DATA LOADER

_ANNUAL_PENSION * Annual Pension Amount of Annual Pension.

_EXPAT_STATEME * Statement Statement that fits this employee's expatriate status.

16 | LOADING UK CARDS USING HCM DATA LOADER

17 | LOADING UK CARDS USING HCM DATA LOADER

Figure 5: Calculation Component Details – New Starter Declaration

18 | LOADING UK CARDS USING HCM DATA LOADER

Figure 7: Calculation Component Details – Expatriate Notification

CARD ASSOCIATION ATTRIBUTES