Disposal of Employee Data in Oracle Fusion HCM PDF

Implementing Information Retention and Disposal
Policies in Oracle Fusion HCM
Oracle Fusion Human Capital Management 11g Release 10 (11.1.10)

ORACLE WHITE PAPER | NOVEMBER 2017
Table of Contents
Implementing Information Retention and Disposal Policies in Oracle Fusion HCM 0

Introduction 1
Approach 2
HCM Extracts 2
HCM Data Loader 2
Best Practices 3
Disclaimer 3
Designing the HCM Data Loader File 3
HCM Data Loader File Control Commands 4
Identifying HCM Data Loader Components and Attributes 4
Testing the HCM Data Loader File 5
Designing the HCM Extract 5
Data Groups 5
Records 5
Attributes 6
Defining the Extract 7
Fast Formulae 7
Creating the Extract 8
Defining a Data Group 8
Delivery Option 14
Validate the Extract 16
Submitting the HCM Extract 16
Review the HCM Extract Output 17
Define the eText Template 18
Template Shape 18
Uploading the eText Template 21
Worked Example – Retention and Disposal of Worker 25
Designing the HCM Data Loader File 25
Worker Components that can be Purged 25
Worker Components to Obfuscate 26
DISPOSAL OF EMPLOYEE DATA IN ORACLE FUSION HCM

Defining the HCM Data Loader File 26
HCM Data Loader Attributes 28
Creating Fast Formulae 38
Designing the HCM Extract 40
Data Groups 40
Data Group Process Flow 41
Identify the User Entities and Attributes 42
Defining the HCM Extract 42
Create an HCM Extract 42
Create the Root Data Group 43
Create Component Data Group: Person 43
Create Component Data Group: Person Address 44
Create Component Data Group: Person Legislative Data 45
Create Component Data Group: Name 46
Create Component Data Group: Work Relationship 47
Create Component Data Group: Employment Terms 47
Create Component Data Group: Assignment 48
Create Component Data Group: Citizenship 49
Create Component Data Group: Person Delivery Method 50
Create Component Data Group: Person Drivers License 50
Create Component Data Group: Email 51
Create Component Data Group: Person Ethnicity 51
Create Component Data Group: Person National Identifier 52
Create Component Data Group: Person Passport 53
Create Component Data Group: Person Phone 53
Create Component Data Group: Person Religion 54
Create Component Data Group: Person Visa 54
Create XML Delivery Option 55
Define the eText Template 55
Define the Template Type 56
Define the level for the Extract 56
Define all HCM Data Loader commands 56

Define the METADATA records 56
Define the Root Data Group Level 57
Define the Data Line Records 57
Close the Root Data Group Level 59
Close the Extract Level 59
Appendix: Deleting Users 60
Define the METADATA Records 60
Define the Data Line Records 60
Table of Figures
Figure 1: Steps to Dispose Ex-employee Records ................................................................................................... 2
Figure 2: Fast Formula - Example: Format Start Date .............................................................................................. 6
Figure 3: Fast Formula - Example: Mask Date of Birth ............................................................................................. 7
Figure 4: Fast Formula - Manage Fast Formulas ...................................................................................................... 7
Figure 5: Fast Formula - Create Fast Formula.......................................................................................................... 7
Figure 6: Fast Formula - Formula Text ..................................................................................................................... 8
Figure 7: HCM Extract - Creating an Extract............................................................................................................. 8
Figure 8: HCM Extract - Creating a Data Group ....................................................................................................... 9
Figure 9: HCM Extract - Creating Filter Conditions ................................................................................................... 9
Figure 10: HCM Extract - Creating a Record .......................................................................................................... 10
Figure 11: HCM Extract - Creating a Detail Record ................................................................................................ 10
Figure 12: HCM Extract - Detail Record ................................................................................................................. 10
Figure 13: HCM Extract - Selecting attributes ......................................................................................................... 11
Figure 14: HCM Extract - Reviewing Attribute Properties ....................................................................................... 11
Figure 15: HCM Extract - Changing the Attribute Short Code ................................................................................. 12
Figure 16: HCM Extract - Creating an Attribute ...................................................................................................... 12
Figure 17: HCM Extract - Creating a Rule Attribute ................................................................................................ 13
Figure 18: HCM Extract - Creating the Data Group Connection ............................................................................. 13
Figure 19: HCM Extract - Creating a Hierarchy traversal record ............................................................................. 14
Figure 20: HCM Extract - Delivery Options ............................................................................................................. 15
Figure 21: HCM Extract - Creating an Inbound Interface Delivery Option ............................................................... 15
Figure 22: HCM Extract - Compile All Formula ....................................................................................................... 16
Figure 23: Submitting a HCM Extract ..................................................................................................................... 16
Figure 24: HCM Extract Results - Search ............................................................................................................... 17
Figure 25: HCM Extract Results - Task Details....................................................................................................... 17
Figure 26: HCM Extract Results - Processes and Reports ..................................................................................... 18
Figure 27: HCM Extract Results - View Results...................................................................................................... 18
Figure 28: Define the METADATA definition line for each component of the business object ................................ 19
Figure 29: Business Intelligence - globalReportsDataModel ................................................................................... 22
Figure 30: Business Intelligence - Create Report ................................................................................................... 23
Figure 31: Business Intelligence - Use Report Editor.............................................................................................. 23
Figure 32: Business Intelligence - Naming the Report ............................................................................................ 23
Figure 33: Business Intelligence - Uploading the eText template ........................................................................... 24

Introduction
Organizations are required to adhere to information retention and disposal policies for data stored in
Oracle Fusion HCM. The retention schedule can vary based on factors such as country, type and age
of information, industry and so on. Corporations need a mechanism to implement rules that can
interrogate, identify, and dispose of information.
This white paper describes an approach that enables companies to implement their own unique and
specific data retention and disposal policies, and to achieve data privacy whilst preserving the integrity
of data stored in Oracle Fusion HCM.
1 | DISPOSAL OF EMPLOYEE DATA IN ORACLE FUSION HCM

Approach
To dispose of data from Oracle Fusion HCM, the following approach is recommended:
 Identify the records that must be disposed, based on various data retention and disposal policies.
 Delete records that can be safely purged.
 Obfuscate records that must be retained to preserve referential integrity. Obfuscation is achieved as follows:
o Remove attribute values for non-mandatory attributes.
o Mask personal identifiable values for mandatory attributes.
HCM Extracts
In order to identify each record to be disposed, it is recommended that an HCM Extract be defined. Using HCM
Extracts, you can specify rules (filter criteria) to fetch the records to be disposed. For each record, you can retrieve
the attributes that uniquely identify the record as well as the attributes to be obfuscated.
The output of each HCM Extract can be automatically transformed into the HCM Data Loader (HDL) file format. This
is achieved by choosing the “HDL” delivery option and associating an eText template with this delivery option. The
resulting output will be a HDL data file which contains the following:
 HDL delete lines to purge records.
 HDL merge lines to obfuscate records. These lines will contain commands to
o Set non-mandatory attributes to null.
o Mask identifying mandatory attributes.
HCM Data Loader

HCM Data Loader (HDL) must be used to upload the generated file and dispose the data. The existing supported
business objects can be used for this purpose.
Figure 1: Steps to Dispose Ex-employee Records

Best Practices
Before attempting to create an HCM Extract or eText layout, you first need to understand the shape of the data file
(.dat format) required to be uploaded to HDL to dispose data. It is recommended that you first create sample HDL
files to achieve the required disposal and test the results.
Steps to success
1. Analyze the object to dispose and identify what data can be deleted and which data needs obfuscation.
2. Define and test the shape of the HDL file and confirm it achieves the required result.
3. Define and test the HCM Extract to extract records (based on your disposal rules) and to output the attribute
values required to be included in the HDL file.
4. Define the eText template to generate files lines for the HDL file.
5. Update the HCM Extract to utilize the eText template
6. Test the end-to-end process.
Disclaimer
It is not possible to reverse the disposal of data. Ensure you genuinely want to dispose of the data extracted in the
HCM Extract generated file, before uploading it with HDL. You should consider taking a snapshot or baseline of your
environment prior to disposing of employee data.
Designing the HCM Data Loader File

Before designing your eText templates and HCM Extract you need an understanding of the HDL file format and what
actions are supported for each component you want to dispose in the business object hierarchy:
1. Understand the file control commands that should be included.

2. For each business object that must be disposed:
a. Identify which business object components to include. You may not hold data for all supported
components.
3. For each component:
a. Determine if the records for the component can be deleted, or if they must be retained but obfuscated.
b. Identify the HDL attributes to include. This will be driven by the action being performed for each
component.
c. Determine if all date-effective records or a single record spanning the duration of employment must be
included. For example, you can replace date-effective updates to a person name with a single obfuscated
record for the duration of employment.
4. For each attribute included, determine if the attribute value is to be:
a. Extracted and unchanged - typically for attributes used to identify the record to delete or update.
b. Set to null - non mandatory attributes for records that cannot be purged.
c. Updated with a constant or masked value - mandatory personal identifying attributes for records that
cannot be purged.
You should generate a file for your business object and test that your file shape provides the desired results.

The business object documentation, available on My Oracle Support (Doc ID: 2020600.1), details which objects
support being deleted. The worked example provided in this document explains what is possible for the Worker
object.
HCM Data Loader File Control Commands

Whenever you replace the date-effective history for a record, you should include the HDL command:
SET PURGE_FUTURE_CHANGES Y
This command ensures that data existing in the Oracle HCM Cloud will be replaced with the data supplied in the file.
Other HDL commands are available if you need to overwrite the default behavior.
Identifying HCM Data Loader Components and Attributes

Review the documentation provided for the business object, to determine which components of the business object
hierarchy should be disposed of. Identify which records can be purged and which need to be obfuscated.
Understand which attributes need to be specified when updating a record, and which attributes should be masked or
set to null.
Purging Records
For the records that can be purged, usually only the surrogate ID attribute that uniquely identifies the record, and the
surrogate ID attribute that identifies the parent record are required.
Example: Purging Person Email

To purge the PersonEmail records the following definition (METADATA) line would be required in the HDL
Worker.dat file:
METADATA|PersonEmail|EmailAddressId|PersonId
A data line to purge the e-mail record would look something like:
DELETE|PersonEmail|300100074926175|300100074926164
Obfuscating Records
For the records that must be obfuscated, in addition to the surrogate IDs for the local and parent records, other
attributes will be required. These will fall into two categories:
 Attributes used to identify the record to update. These will remain unchanged.
 Attributes to obfuscate.
For each date-effective record type, you must also determine if all date-effective records should be included, or a
single record spanning the duration of employment.
Example: Obfuscating Worker

To obfuscate the Worker records the following definition (METADATA) line would be required:

METADATA|Worker|PersonId|PersonNumber|EffectiveStartDate|DateOfBirth|DateOfDeath|Coun
tryOfBirth|RegionOfBirth|TownOfBirth|ApplicantNumber|BloodType|CorrespondenceLanguage
A data line to obfuscate the worker record would look something like:
MERGE|Worker|300100074926164|10041|1982/02/08|1962/02/13|#NULL|#NULL|#NULL|#NULL|#NUL
L|#NULL|#NULL
The DateofBirth field is mandatory and therefore replaced (masked) with new values. The #NULL tag tells HDL to
remove non-mandatory attribute values.
Testing the HCM Data Loader File

Once you have created a business object file, upload it using HCM Data Loader and ensure the resulting data is
updated as required.
Steps to execute HCM Data Loader are available in the HCM Data Loader User’s Guide (MOS Doc ID: 1664133.1).
Designing the HCM Extract

In order to dispose a record, you need a unique reference to the record. HCM Extracts provides access to this
information for all objects you may need to dispose. A simple extract definition containing just these key values, with
filter criteria to target the population you want to dispose of, is all that is required.
The formatting of the extracted data, along with the data obfuscation can predominantly be achieved by defining an
eText layout for each business object to be obfuscated. The eText layout is a rich text document that allows you to
specify the HCM Data Loader file instruction for each record type including the value and masking criteria for each
attribute.
Data Groups
Data groups are used to extract and filter the required records and attribute values from the Oracle Fusion HCM
database.
Each component to purge or obfuscate will need a data group in the extract. Additionally a root data group is
required to filter the records to be included in the output.
Root Data Group

A root data group is required to filter the records to be included in the output. Determine what criteria should be
applied in order to extract your target population. This will help you determine which user entity the root data group
should be based on. These criteria are usually defined by your information retention and disposal policies.
Component Data Groups

For each component in the business object hierarchy that must be purged or obfuscated, identify the user entity that
can extract the attributes to be included in the Worker.dat data file. Identify how the component data group connects
back to the root data group to restrict the data retrieved by the filter applied to the root data group.
Records
Each data group requires a record. Records are used for two purposes:
Detail Records

Every data group must have a record to group the attributes to extract. These records have a type of ‘Detail record’.
If your data group will return multiple records for the same person, the name of the record will be referenced in your
eText template to repeat the eText record definition for each record extracted.
Hierarchy Traversal Records

Your extract needs to know in which order to process the data groups. This is achieved by creating hierarchy
traversal records. After extracting the attributes in the detail record, the hierarchy traversal record will specify the
next data group to extract data for. Plan the Data Groups you require and define the hierarchy traversal plan.
The connections and flow will follow the same hierarchical shape as the business object you are disposing.
Attributes
There are two types of HCM Extract attributes:
 User entity attributes Attributes selected from the data group user entity, these retrieve the unformatted
value from the database.
 Rule based attributes Manually created to invoke a fast formula to format or mask a user entity attribute.
Having defined your business object file, map the HDL attributes to be included to the user entity attributes. Identify
all rule based attributes to create.
Fast Formulae
HCM Extract outputs dates in a timestamp format incompatible with HDL. The eText template is responsible for
formatting the file shape, but it cannot correctly format date values. Date attributes need to be formatted to the HDL
date format (YYYY/MM/DD). This can be achieved by creating a simple Extract Rule fast formula to perform the
formatting:
INPUTS ARE DATA_ELEMENTS (TEXT_TEXT)
rule_date_value = TO_DATE(substr(DATA_ELEMENTS['Start_Date'], 1, 10),'YYYY/MM/DD')
rule_value = date_to_text(rule_date_value, 'YYYY/MM/DD')
return rule_value
Figure 2: Fast Formula - Example: Format Start Date
A single formula can be used to provide formatting for multiple attributes. The formula uses the user entity attribute’s
short code to determine which attribute value to format.
If you will be retrieving both start and end dates you should create two formulae, one to format the start date, the
other to format the end date. Multiple attributes in the same record cannot have the same short code.
A fast formula can also be used to mask an attribute value. For example, if you want to mask a worker’s date of birth
to be 20 years before their start date, the following formula can be created to adjust the date by 20 years and format
the output to the HDL date format.
INPUTS ARE DATA_ELEMENTS (TEXT_TEXT)
rule_date_value = ADD_YEARS(TO_DATE(substr(DATA_ELEMENTS['Start_Date'], 1,
10),'YYYY/MM/DD'),-20)

return rule_value
Figure 3: Fast Formula - Example: Mask Date of Birth
Defining the Extract

Now that the data groups and attributes have been designed the extract can be created. The section navigates you
through the steps required to create an Inbound Interface extract.
Fast Formulae
First create the fast formula you require for formatting and masking.
Figure 4: Fast Formula - Manage Fast Formulas

Navigation: Payroll Administration - Manage Fast Formulas
1. Click the Create button on the table toolbar
Figure 5: Fast Formula - Create Fast Formula
2. In the Create Fast Formula popup

a. Specify a name, this name will be referenced as the Rule for your manually created Rule attributes
b. Specify a type of Extract Rule
c. Click Continue
3. Specify the Formula Text

Figure 6: Fast Formula - Formula Text
4. Click Save
5. Compile the formula and Refresh to ensure successfully compilation.
Creating the Extract

1. From the Manage Extract Definitions task in the Data Exchange work area, click Create
2. Specify a name
3. Specify a Type of ‘Inbound Interface’ and click OK.
Figure 7: HCM Extract - Creating an Extract
Defining a Data Group

On the Design page, create each data group in turn, specifying any filter criteria, creating a detail record type,
selecting the attributes required, creating the data group connection and the hierarchy traversal record on the parent
data group.
Steps to create a Data Group

1. Click Create Data Group

Figure 8: HCM Extract - Creating a Data Group
2. Specify the name and user entity.
3. Check the Root Data Group checkbox only for the population data group, the data group that identifies who
should be included in the extract.
Adding Filter Criteria

1. Click on the Filter button on the Data Group
2. Click Edit button on the Data Group Filter Criteria popup
3. Use the Edit Filter Criteria Condition popup to specify the filter criteria
Figure 9: HCM Extract - Creating Filter Conditions
4. Click OK.
Creating a Detail Record

1. On the Configure drop down on the Data Group definition, click Create Record

Figure 10: HCM Extract - Creating a Record
2. Specify a Sequence of ‘10’ and provide the name for the record group. You do not need to use the Advanced
options for Detail records.
Figure 11: HCM Extract - Creating a Detail Record
3. Click Save, your record will appear within the Data Group
Figure 12: HCM Extract - Detail Record
Selecting Attributes
1. To add attributes to your record, double click the record name, a list of attributes will appear on the left:

Figure 13: HCM Extract - Selecting attributes
2. Use the Search filter to find the required attributes, clicking an attribute name will add it to the detail record.
Formatting a Date Attribute

1. Click on the date attribute to see the Properties:
Figure 14: HCM Extract - Reviewing Attribute Properties
2. In the fast formula used to format the date, a reference is made to the attribute short code. In order to format
the date with one of the formulae, change the short code to the value used, such as Start_Date, or End_Date

Figure 15: HCM Extract - Changing the Attribute Short Code
3. Save the change
4. Create a new Rule attribute by clicking on the Configure button on the Detail Record, and selecting Create
Attribute:
Figure 16: HCM Extract - Creating an Attribute
5. Provide the details for the new attribute:

Name The value will be displayed in the Detail Record
Short Code An internal code for the attribute
Data Type ‘Text’
Type ‘Rule’
Output Label The value to include in the eText template to retrieve the date value
Output Column A unique column number within the Detail Record
Rule The name of the fast formula

Figure 17: HCM Extract - Creating a Rule Attribute
6. Click Save
Creating a Data Group Connection

Once you have defined your data groups, you need to connect your data groups, so each data group retrieves only
those records filtered by the root data group.
1. Click on the Data Group Connection icon on all but the root data group to connect the data group to its parent:
Figure 18: HCM Extract - Creating the Data Group Connection
Creating a Hierarchy Traversal Record

The hierarchy traversal records tell HCM Extracts in which order to process your data groups. After defining the
Data Group Connection on the child data group, you then create the hierarchy traversal record on the parent data
group.

This step cannot be completed until the Data Group Connection is saved.
1. Click the Create Record action on the parent Data Group, available from the Configure button
2. In the Properties panel, specify:

Sequence A unique record sequence in the Data Group. The detail record will have a sequence on 10, so
this must be higher.
Name A unique name for the record.
Next Data Group Select the name of the data group to connect to
Type ‘Hierarchy traversal only’
Figure 19: HCM Extract - Creating a Hierarchy traversal record
You can repeat the above steps to create all required data groups. However, it is recommended that you define a
delivery option and test each data group as it is added.
Delivery Option
The extract requires an Inbound Interface delivery option in order to associate your eText layout to format the data in
the HDL file format, and deliver your output to a file to the Oracle WebCenter Content server. However, initially it is
recommended that you create a simple ‘Data’ output type, to output the extracted data in XML format. This will allow

you to review and confirm you have correctly extracted the data, and identify the attribute tags that must be included
in the eText template to reference the attribute values.
Defining the XML Delivery Option

1. On the Deliver page, click the Add button on the Extract Delivery Options table.
Figure 20: HCM Extract - Delivery Options
2. Provide a Delivery Option and Output name. The Output Type should remain ‘Data’.
3. Click Save
Defining the Inbound Interface Delivery Option

This delivery option cannot be created until the eText template has been created and uploaded. The inbound
interface delivery option ensures the generated file is placed in the HCM Data Loader inbound directory on the
Oracle WebCenter Content server (hcm/dataloader/import).
The file will be created with a txt file extension. Before you can upload it using HDL you must first change the file
extension to .dat and add this file to a compressed zip file. Whilst compressing the file you can encrypt the zip file.
The individual business object files should not be encrypted separately.
1. On the Deliver page, click the Add button on the Extract Delivery Options table.
Figure 21: HCM Extract - Creating an Inbound Interface Delivery Option
2. Provide a Delivery Option name and specify

Output Type ‘Text’
Report The path and name of the BI Publisher report created to upload your eText template
Template Name The name of the layout created in your eText template
Output Name The name of the business object file being generated, such as Worker
Delivery Type ‘Inbound Interface’
3. The delivery type of Inbound Interface generates parameters that need to be configured in the Additional
Details table. Specify:

Integration Type ‘Data Loader’
Integration Name The business object file name
Override Extension Name ‘.dat’
Encryption Mode Select the mode to encrypt the file whilst it is on the WebCenter Content server.
4. Click Save
Validate the Extract

1. On the Validate page, click the Compile All Formula button
Figure 22: HCM Extract - Compile All Formula
2. Refresh occasionally until green ticks appear against all Fast Formula records in the Status column.
3. Click Submit to validate your extract. You can now submit your extract.
Submitting the HCM Extract

You submit your extract from the Submit Extracts task available in the Data Exchange work area.
Figure 23: Submitting a HCM Extract
1. Search and select your extract using the Query By Example filter
2. Click Next

3. Specify a Payroll Flow name to uniquely identify this extract submission, specify the Effective Date and click
Submit.
Review the HCM Extract Output

You review extract output from the Payroll Checklist work area.
4. Navigate to the Payroll Checklist page in the Checklists work area.
5. You can restrict the search results by specifying your process flow name, or specify the name of your extract in
the Flow Pattern search field.
Figure 24: HCM Extract Results - Search
6. Click on the payroll process flow name to navigate to the task details.
Figure 25: HCM Extract Results - Task Details
7. Click on the Go to Task icon against the row with your extract name. This navigates you to the Processes and
Reports for your test run.

Figure 26: HCM Extract Results - Processes and Reports
8. Click the icon in the View Results column to see the files generated by the extract.
Figure 27: HCM Extract Results - View Results
9. One file will be generated for each delivery option specified. To download the file click the File Name.
Define the eText Template

The eText template is a rich text document which defines the layout of the data output from your HCM Extract. A
separate eText template is required for each of the business objects you want to dispose. A single eText template
will be used to format all file lines required for the HDL business object.
Once you have designed the HDL file format, with respect to components and attributes to include, the eText
template should be straight forward to create.
Template Shape
eText templates adhere to the following shape:
 Template type definition

 DATA_DS level definition
 HCM Data Loader control command records
 HCM Data Loader METADATA records
 Root data group level
 HCM Data Loader data line records, wrapped with a data group level for repeating data groups.
 End Root data group level
 End DATA_DS level
Define Template Type

An eText template must start with a template type definition. This template type definition can be used:

<TEMPLATE TYPE> DELIMITER_BASED
<OUTPUT CHARACTER SET> ASCII
<NEW RECORD CHARACTER> Carriage Return
Define Level DATA_DS

The eText template should have a level definition for the DATA_DS. This is the default tag used to wrap the content
of your HCM Extract:
<LEVEL> DATA_DS
HCM Data Loader Control Command Records

Any HDL commands you want to include in your file must be created first, ensuring they are included before any
definition or data lines. When obfuscating data, you should always include the command:
Example
<NEW RECORD> REPLACE_FUTURE_CHANGES
<DISPLAY 1=1
CONDITION>
<MAXIUMUM <FORMAT> <DATA> <TAG> <COMMENTS>
LENGTH>
100 Alpha 'SET PURGE_FUTURE_CHANGES
Y'
Additional records can be created for each command required.
HCM Data Loader METADATA records

Provide a new record for each METADATA definition line for each component you want to include in your generated
business object file. It must specify the file line instruction, file discriminator for the component, the exact names of
each attribute and a pipe delimiter between each.
Example
<NEW WORKER_HEADER
RECORD>
<DISPLAY 1=1
CONDITION>
LENGTH>
100 Alpha 'METADATA|Worker'
1 Alpha '|'
100 Alpha 'PersonId' PersonId
1 Alpha '|'
100 Alpha 'PersonNumber' PersonNumber
1 Alpha '|'
100 Alpha 'EffectiveStartDate' EffectiveStartDate
1 Alpha '|'
100 Alpha 'DateOfBirth' DateOfBirth
1 Alpha '|'
100 Alpha 'DateOfDeath' DateOfDeath
Figure 28: Define the METADATA definition line for each component of the business object

Root Data Group Level
Create a new level. It must have the same name as your root data group in the extract.
Example
<LEVEL> Terminated_Workers
HCM Data Loader Data Line

The eText template will need a new record for each data line, specifying the correct DELETE or MERGE instruction
and referencing the attribute tags as defined in the XML output for your HCM Extract.
<NEW Worker
RECORD>
<DISPLAY 1=1
CONDITION>
LENGTH>
100 Alpha 'MERGE|Worker'
1 Alpha '|'
100 Alpha Extract_Person_ID PersonId
1 Alpha '|'
100 Alpha Person_Number PersonNumber
1 Alpha '|'
100 Alpha Person_Effective_Start_Date EffectiveStartDate
1 Alpha '|'
100 Alpha Date_Of_Birth DateOfBirth
1 Alpha '|'
10 Alpha '#NULL' DateOfDeath
Specify the data type and maximum length for each row. The comments column can be used to specify which
attribute the file row pertains to.
In the Data column, specify the name of the attribute tag, as seen in the XML output, or a constant value. The HDL
#NULL tag can be used to set non-mandatory attributes to null.
Each attribute value must be delimited with a pipe ‘|’ character to conform to the HDL file line format.
Repeating Records
If the record type repeats you must wrap your record definition with a level definition.
Example
<LEVEL> Email
<NEW RECORD> PersonEmail

<DISPLAY 1=1
CONDITION>
LENGTH>
100 Alpha 'DELETE|PersonEmail'
1 Alpha '|'

<END LEVEL> Email
End Root Data Group Level

End the level created for your root data group
Example
<END LEVEL> Terminated_Workers
End DATA_DS Level

End the level created for your root data group
Example
<END LEVEL> DATA_DS
Uploading the eText Template

To be able to use the eText template within the HCM Extracts delivery option, you must first create a dummy
Business Intelligence (BI) report and upload the eText template as its layout. This BI report will not be extracting
any data, it is simply the mechanism used for applying a format to an HCM Extract.
Create a Business Intelligence Report

1. Access Business Intelligence From the Report and Analytics task.
2. Navigate to the Catalog by clicking the Browse Catalog icon
3. Use the folder hierarchy to find the globalReportsDataModel within the /SharedFolders/Human Capital
Management/Payroll/Data Models folder.

Figure 29: Business Intelligence - globalReportsDataModel
4. Click Edit to open the data model.
5. Click Create Report to create a new report based on this generic data model.

Figure 30: Business Intelligence - Create Report
6. You will create your report using the report editor, so change the radio group to ‘Use Report Editor’ and click
Finish.
Figure 31: Business Intelligence - Use Report Editor
7. Select a folder for your report and specify a name, such as ObfuscateWorker:
Figure 32: Business Intelligence - Naming the Report

8. You will need to supply the path and name of your report in the delivery option, such as: /Custom/Human
Capital Management/ObfuscateData/ObfuscateWorker.xdo. The Shared Folders part of the path is not
required in the delivery option.
9. From the Create Layout page, click Upload
Figure 33: Business Intelligence - Uploading the eText template
10. Define your report layout and click Upload

Layout Name Provide a name for the layout. You will need to specify this within the Inbound
Interface delivery option in the HCM Extract.
Template File Select your eText template file using the Choose File button
Type Specify eText Template
Locale Specify English
11. Save your report.
You can now create the Inbound Interface delivery option for your HCM Extract. See Defining the Inbound
Interface Delivery Option.

Worked Example – Retention and Disposal of
Worker
Designing the HCM Data Loader File
Worker is a complex business object with multiple components. Before defining the HCM Extract or eText template
you need to understand which records can be purged, and for those that can’t, which attribute values can be
removed and which need to be masked. This information is available in the business object documentation provided
on My Oracle Support (Doc ID: 2020600.1) but is explained here as part of the worked example.
Note: The example that follows assumes that the worker was previously employed. For worker records created in
error, other options are available. For example, you can cancel the work relationship, which will purge the
employment-related records. See the HCM Data Loader: Loading Workers white paper (document ID 2022624.1) for
further details of what can be achieved using HCM Data Loader.
Worker Components that can be Purged

The Worker business object comprises a number of components for the person and their employment history. Of
these the following can safely be purged:
Component Functional Description
Person Citizenship State or nation that a person identifies as being a native or naturalized member of and is entitled to its
protection.
Person Delivery Method The types of communication methods for a person. For example IM, web address and so on.
Person Drivers License Driving license details of a person.
Person Email E-mail address of a particular type for a person.
Person Ethnicity Name of the cultural or racial group a person belongs to.
Person Legislative Data Secondary legislative data records. Primary legislative data records cannot be purged.
Person National Identifier String of alpha numeric characters assigned by a legal authority that are used to represent a person.
Person Passport Passport details for a person.
Person Phone Secondary phone details of a particular type for a person. Primary phone numbers cannot be purged.
Person Religion Group that a person belongs to in reference to their fundamental beliefs and practices.
Person Visa Details of a person's visa or work permit.
Person Image Defines the photo of a person.
External Identifier External Identifier enables the ability to capture a third party payroll identifier and time clock badge identifier
for a person assignment.
Worker Extra Information Represents the extensible structure for the worker.
Assignment Grade Steps Identifies an increment within an assignment grade.
Assignment Manager Supervisor for a particular assignment record.
Assignment Work Defines information about the HR budget values for an assignment.
Measure
Assignment Extra Represents the extensible structure for the assignment.

Information
Employment Terms Grade Identifies an increment within an employment terms grade.

Steps

Employment Terms Supervisor for a particular work terms record.
Manager
Employment Terms Work Defines information about the HR budget values for a work terms record.
Measure
Employment Terms Extra Represents the extensible structure for the employment terms.
Information
Worker Components to Obfuscate

For the remaining components, non-mandatory attribute values can be removed, mandatory attributes that include
personal identifying information should be masked:
Component Functional Description Recommendation
Worker Person working for an enterprise, for example, Mask DateOfBirth, remove all non-mandatory attributes
employee or contingent worker.
Person Address Postal address for a person. Remove any date-effective updates, overwrite with a generic
address.
Person Person data specific to a legislation. Remove non-mandatory attributes.

Legislative Data
Person Name Common and legislative-specific name components Remove date-effective updates.
for a person. Remove non-mandatory attributes. Mask Last Name.
Person Phone Primary phone details for a person. Remove non-mandatory attributes. Mask Phone Number.
Work A work relationship is the highest level in the Remove non-mandatory attributes. Mask mandatory.
Relationship employment model and exists for every worker for a Date Start, Actual Termination Date and Worker Type cannot be
Legal Employer. changed.
Employment Second level in the employment model that Remove non-mandatory attributes. Mask mandatory.
Terms captures the terms and conditions associated with Legal Employer cannot be changed.
one or more assignments.
Assignment Lowest level in the employment model, which Remove non-mandatory attributes. Mask mandatory.
identifies the details of the work to be performed. Legal Employer cannot be changed.
Contract Defines the contract associated with employment Remove non-mandatory attributes. Mask mandatory.
terms, for example, contract type and duration.
Defining the HCM Data Loader File

For each component determine the attributes that need to be supplied in order to achieve the required result.
An example Worker.dat file for disposing a single ex-employee could look something like this:
METADATA|Worker|PersonId|PersonNumber|EffectiveStartDate|DateOfBirth|DateOfDeath|CountryOfBirth|RegionOf
Birth|TownOfBirth|ApplicantNumber|BloodType|CorrespondenceLanguage
MERGE|Worker|300100074926164|EJ10041|1982/02/08|1962/02/13|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL
METADATA|PersonAddress|PersonAddrUsageId|PersonId|EffectiveStartDate|AddressType|Country|AddressLine1|Ad
dressLine2|AddressLine3|AddressLine4|TownOrCity|Region1|Region2|PostalCode
MERGE|PersonAddress|300100074926170|300100074926164|1982/02/08|HOME|US|Masked
Address|#NULL|#NULL|#NULL|New York|New York|NY|10130
METADATA|PersonCitizenship|CitizenshipId|PersonId
DELETE|PersonCitizenship|300100074926173|300100074926164
DELETE|PersonCitizenship|300100075017914|300100074926164
METADATA|PersonDeliveryMethod|DeliveryMethodId|PersonId
DELETE|PersonDeliveryMethod|300100074926174|300100074926164

DELETE|PersonDeliveryMethod|300100075017906|300100074926164
METADATA|PersonDriversLicence|DriversLicenseId|PersonId|DateFrom
DELETE|PersonDriversLicence|300100075017915|300100074926164
DELETE|PersonDriversLicence|300100075017917|300100074926164
METADATA|PersonEmail|EmailAddressId|PersonId
DELETE|PersonEmail|300100074926175|300100074926164
METADATA|PersonEthnicity|EthnicityId|PersonId
DELETE|PersonEthnicity|300100075017910|300100074926164
DELETE|PersonEthnicity|300100074926176|300100074926164
METADATA|PersonLegislativeData|PersonLegislativeId|PersonId|EffectiveStartDate|LegislationCode|Sex|Marit
alStatus
MERGE|PersonLegislativeData|300100074926169|300100074926164|1982/02/08|US|#NULL|#NULL
DELETE|PersonLegislativeData|300100075017911|300100074926164|2016/09/28|||
METADATA|PersonName|PersonNameId|PersonId|EffectiveStartDate|NameType|CharSetContext|LegislationCode|Las
tName|FirstName|MiddleNames|Title|PreNameAdjunct|Suffix|KnownAs|PreviousLastName
MERGE|PersonName|300100074926167|300100074926164|1982/02/08|GLOBAL||US|MASKED|#NULL|#NULL|#NULL|#NULL|#N
ULL|#NULL|#NULL
METADATA|PersonNationalIdentifier|NationalIdentifierId|PersonId
DELETE|PersonNationalIdentifier|300100074926177|300100074926164
DELETE|PersonNationalIdentifier|300100075017919|300100074926164
METADATA|PersonPassport|PassportId|PersonId
DELETE|PersonPassport|300100074926320|300100074926164
METADATA|PersonPhone|PhoneId|PersonId|DateFrom|CountryCodeNumber|AreaCode|PhoneNumber|Extension|SpeedDia
lNumber
DELETE|PersonPhone|300100074926178|300100074926164||||||
DELETE|PersonPhone|300100074926179|300100074926164||||||
METADATA|PersonReligion|ReligionId|PersonId
DELETE|PersonReligion|300100074926182|300100074926164
DELETE|PersonReligion|300100075017909|300100074926164
METADATA|PersonVisa|VisaPermitId|PersonId|EffectiveStartDate
DELETE|PersonVisa|300100074926363|300100074926164|2015/01/01
METADATA|PersonImage|ImageId|PersonId
DELETE|PersonImage|300100074926172|300100074926164
METADATA|WorkRelationship|PeriodOfServiceId|PersonId|DateStart|LegalEntityId|ActualTerminationDate|Actio
nCode|ReasonCode
MERGE|WorkRelationship|300100074926166|300100074926164|1982/02/08|300100010401887|2015/04/01|RESIGNATION
|RESIGN_PERSONAL
METADATA|WorkTerms|AssignmentId|PeriodOfServiceId|ActionCode|EffectiveStartDate|EffectiveEndDate|Effecti
veSequence|EffectiveLatestChange|AssignmentName|AssignmentNumber|PrimaryWorkTermsFlag|PeopleGroup|DatePr
obationEnd|WorkerCategory|AssignmentCategory|EstablishmentId|ExpenseCheckSendToAddress|GradeId|GradeLadd
erPgmId|HourlySalariedCode|InternalBuilding|InternalFloor|InternalLocation|InternalMailstop|InternalOffi
ceNumber|JobId|LabourUnionMemberFlag|LocationId|ManagerFlag|NormalHours|Frequency|NoticePeriod|NoticePer
iodUOM|OrganizationId|PositionId|ProbationPeriod|ProbationUnit|ProjectedEndDate|ProjectedStartDate|Propo
sedWorkerType|ProposedUserPersonType|RetirementAge|RetirementDate|SpecialCeilingStepId|TaxAddressId|EndT
ime|StartTime|VendorSiteId|WorkAtHomeFlag|VendorId|CollectiveAgreementId|FullPartTime|PermanentTemporary
MERGE|WorkTerms|300100074926183|300100074926166|HIRE|1982/02/08|2011/05/04|1|Y|MASKED300100074926183|MAS
KED300100074926183|Y|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL
|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#
NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL
MERGE|WorkTerms|300100074926183|300100074926166|ASG_CHANGE|2011/05/05|2015/04/01|1|Y|MASKED3001000749261
83|MASKED300100074926183|Y|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL
NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL
MERGE|WorkTerms|300100074926214|300100074926166|RESIGNATION|2015/04/02|4712/12/31|1|Y|MASKED300100074926
214|MASKED300100074926214|N|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NUL
L|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|
#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL
MERGE|WorkTerms|300100074926183|300100074926166|RESIGNATION|2015/04/02|4712/12/31|1|Y|MASKED300100074926
183|MASKED300100074926183|Y|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NUL
MERGE|WorkTerms|300100074926214|300100074926166|ADD_ASSIGN|2011/05/05|2015/04/01|1|Y|MASKED3001000749262
14|MASKED300100074926214|N|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL
NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL
METADATA|Assignment|AssignmentId|WorkTermsAssignmentId|ActionCode|EffectiveStartDate|EffectiveEndDate|Ef

fectiveSequence|EffectiveLatestChange|AssignmentName|AssignmentNumber|PrimaryAssignmentFlag|PeopleGroup|
DateProbationEnd|WorkerCategory|AssignmentCategory|EstablishmentId|ExpenseCheckSendToAddress|GradeId|Gra
deLadderPgmId|HourlySalariedCode|InternalBuilding|InternalFloor|InternalLocation|InternalMailstop|Intern
alOfficeNumber|JobId|LabourUnionMemberFlag|LocationId|ManagerFlag|NormalHours|Frequency|NoticePeriod|Not
icePeriodUOM|OrganizationId|PositionId|ProbationPeriod|ProbationUnit|ProjectedEndDate|ProjectedStartDate
|ProposedWorkerType|ProposedUserPersonType|RetirementAge|RetirementDate|SpecialCeilingStepId|TaxAddressI
d|EndTime|StartTime|VendorSiteId|WorkAtHomeFlag|VendorId|CollectiveAgreementId|FullPartTime|Permane ntTem
porary
MERGE|Assignment|300100074926218|300100074926214|RESIGNATION|2015/04/02|4712/12/31|1|Y|MASKED30010007492
6218|MASKED300100074926218|N|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NU
LL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL
|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL
MERGE|Assignment|300100074926209|300100074926183|HIRE|1982/02/08|2011/05/04|1|Y|MASKED300100074926209|MA
SKED300100074926209|Y|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NUL
#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL
MERGE|Assignment|300100074926218|300100074926214|ADD_ASSIGN|2011/05/05|2015/04/01|1|Y|MASKED300100074926
218|MASKED300100074926218|N|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NUL
MERGE|Assignment|300100074926209|300100074926183|ASG_CHANGE|2011/05/05|2015/04/01|1|Y|MASKED300100074926
209|MASKED300100074926209|Y|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NUL
MERGE|Assignment|300100074926209|300100074926183|RESIGNATION|2015/04/02|4712/12/31|1|Y|MASKED30010007492
6209|MASKED300100074926209|Y|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NU
LL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL
|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL|#NULL
HCM Data Loader Attributes

Once the HDL file has been designed and tested to confirm it achieves the required results, the next step is to
design the HCM Extract and eText template.
To achieve this:
 Identify the file discriminator to include in the HDL file
 Identify the file instruction; is the record to be updated or deleted.
 List each attribute that needs to be included in the file.
For each attribute:
 Specify the source of the attribute value
 Identify if any additional formatting or masking actions are required for the data being extracted.
For example, if the attribute is non-mandatory and is to be set to null (blank), the source will be the #NULL tag used
by HDL to nullify non-mandatory attribute values. If however, the attribute is used to identify the record to update or
delete, the attribute value needs to be extracted using the HCM Extract. Some attributes may need to be set to a
constant value to mask the existing value. Specify which value will be used to mask the attribute.
HCM Extract outputs dates in a timestamp format not compatible with HDL. When extracting dates you must also
format them to the YYYY/MM/DD format required by HDL. There will be an action required for all date attributes.
Additionally if you want to achieve a masked value by adjusting an existing database value, you will need an action
to generate the masked value. An example would be to adjust the employee’s start date by 20 years to be used to
mask their date of birth.

The following mapping tables describe the components and attributes of the worker object, as mapped from the HDL
file example above.
Worker
Requirement One record spanning employment for the ex-employee
Instruction MERGE
Discriminator Worker
Attributes
Attribute Source Action
PersonId HCM Extract
EffectiveStartDate HCM Extract Format YYYY/MM/DD
PersonNumber HCM Extract
DateOfBirth HCM Extract Subtract 20 years from EffectiveStartDate

and format YYYY/MM/DD
DateOfDeath ‘#NULL’
CountryOfBirth ‘#NULL’
RegionOfBirth ‘#NULL’
TownOfBirth ‘#NULL’
ApplicantNumber ‘#NULL’
BloodType ‘#NULL’
CorrespondenceLanguage ‘#NULL’
Person Address
Requirement One record spanning employment for the parent ex-employee
Instruction MERGE
Discriminator PersonAddress
Attributes
Attribute Source Action
PersonAddrUsageId HCM Extract
AddressType HCM Extract
Country ‘US’
AddressLine1 ‘MASKED’
AddressLine2 ‘#NULL’
TownOrCity ‘New York’
Region1 ‘New York’
Region2 ‘NY’
PostalCode ‘10130’

Person Legislative Data
Requirement All primary legislative data records for the parent ex-employee
Instruction MERGE
Discriminator PersonLegislativeData
Attributes
HDL Attribute Source Action
PersonLegislativeId HCM Extract
LegislationCode HCM Extract
Sex ‘#NULL’
MaritalStatus ‘#NULL’
Requirement All secondary phone records for the parent ex-employee

Instruction DELETE
Discriminator PersonPhone
Attributes
PersonLegislativeId HCM Extract
Person Name
Requirement One record spanning employment for the parent ex-employee
Instruction MERGE
Discriminator PersonName
Attributes
PersonNameId HCM Extract
NameType HCM Extract
CharSetContext HCM Extract Pass null if NameType is GLOBAL
LegislationCode HCM Extract
LastName ‘MASKED’
FirstName ‘#NULL’
MiddleNames ‘#NULL’

Title ‘#NULL’
PreNameAdjunct ‘#NULL’
Suffix ‘#NULL’
KnownAs ‘#NULL’
PreviousLastName ‘#NULL’
Work Relationship
Requirement All work relationship records for the parent ex-employee
Instruction MERGE
Discriminator WorkRelationship
Attributes
PeriodOfServiceId HCM Extract
DateStart HCM Extract Format YYYY/MM/DD
LegalEntityId HCM Extract
ActualTerminationDate HCM Extract Format YYYY/MM/DD
ActionCode ‘RESIGNATION’
ReasonCode ‘RESIGN_PERSONAL’
Employment Terms
Requirement All employment terms records for the parent work relationship
Instruction MERGE
Discriminator WorkTerms
Attributes
AssignmentId HCM Extract
PeriodOfServiceId HCM Extract
ActionCode HCM Extract
EffectiveEndDate HCM Extract Format YYYY/MM/DD
EffectiveSequence HCM Extract
EffectiveLatestChange HCM Extract
PrimaryWorkTermsFlag HCM Extract
AssignmentName ‘MASKED’|| extracted

AssignmentId
AssignmentNumber extracted AssignmentId
PeopleGroup ‘#NULL’

DateProbationEnd ‘#NULL’
WorkerCategory ‘#NULL’
AssignmentCategory ‘#NULL’
EstablishmentId ‘#NULL’
ExpenseCheckSendToAddress ‘#NULL’
GradeId ‘#NULL’
GradeLadderPgmId ‘#NULL’
HourlySalariedCode ‘#NULL’
InternalBuilding ‘#NULL’
InternalFloor ‘#NULL’
InternalLocation ‘#NULL’
InternalMailstop ‘#NULL’
InternalOfficeNumber ‘#NULL’
JobId ‘#NULL’
LabourUnionMemberFlag ‘#NULL’
LocationId ‘#NULL’
ManagerFlag ‘#NULL’
NormalHours ‘#NULL’
Frequency ‘#NULL’
NoticePeriod ‘#NULL’
NoticePeriodUOM ‘#NULL’
OrganizationId ‘#NULL’
PositionId ‘#NULL’
ProbationPeriod ‘#NULL’
ProbationUnit ‘#NULL’
ProjectedEndDate ‘#NULL’
ProectedStartDate ‘#NULL’
PropopsedWorkerType ‘#NULL’
ProposedUserPersonType ‘#NULL’
RetirementAge ‘#NULL’
RetirementDate ‘#NULL’
SpecialCeilingStepId ‘#NULL’
TaxAddressId ‘#NULL’
EndTime ‘#NULL’
StartTime ‘#NULL’
VendorSiteId ‘#NULL’
WorkAtHomeFlag ‘#NULL’
VendorId ‘#NULL’
CollectiveAgreementId ‘#NULL’

FullPartTime ‘#NULL’
PermanentTemporary ‘#NULL’
Assignment
Requirement All assignment records for the parent work term record
Instruction MERGE
Discriminator Assignment
Attributes
AssignmentId HCM Extract
WorkTermsAssignmentId HCM Extract
ActionCode HCM Extract
EffectiveEndDate HCM Extract Format YYYY/MM/DD
EffectiveSequence HCM Extract
EffectiveLatestChange HCM Extract
PrimaryAssignmentFlag HCM Extract
AssignmentName ‘MASKED’|| extracted

AssignmentId
AssignmentNumber Extracted AssignmentId
PeopleGroup ‘#NULL’
DateProbationEnd ‘#NULL’
WorkerCategory ‘#NULL’
AssignmentCategory ‘#NULL’
EstablishmentId ‘#NULL’
ExpenseCheckSendToAddress ‘#NULL’
GradeId ‘#NULL’
GradeLadderPgmId ‘#NULL’
HourlySalariedCode ‘#NULL’
InternalBuilding ‘#NULL’
InternalFloor ‘#NULL’
InternalLocation ‘#NULL’
InternalMailstop ‘#NULL’
InternalOfficeNumber ‘#NULL’
JobId ‘#NULL’
LabourUnionMemberFlag ‘#NULL’
LocationId ‘#NULL’
ManagerFlag ‘#NULL’

NormalHours ‘#NULL’
Frequency ‘#NULL’
NoticePeriod ‘#NULL’
NoticePeriodUOM ‘#NULL’
OrganizationId ‘#NULL’
PositionId ‘#NULL’
ProbationPeriod ‘#NULL’
ProbationUnit ‘#NULL’
ProjectedEndDate ‘#NULL’
ProectedStartDate ‘#NULL’
PropopsedWorkerType ‘#NULL’
ProposedUserPersonType ‘#NULL’
RetirementAge ‘#NULL’
RetirementDate ‘#NULL’
SpecialCeilingStepId ‘#NULL’
TaxAddressId ‘#NULL’
EndTime ‘#NULL’
StartTime ‘#NULL’
VendorSiteId ‘#NULL’
WorkAtHomeFlag ‘#NULL’
VendorId ‘#NULL’
CollectiveAgreementId ‘#NULL’
FullPartTime ‘#NULL’
PermanentTemporary ‘#NULL’
Person Citizenship
Requirement All citizenship records for the parent ex-employee
Instruction DELETE
Discriminator PersonCitizenship
Attributes
CitizenshipId HCM Extract
Person Delivery Method

Requirement All delivery method records for the parent ex-employee
Instruction DELETE
Discriminator PersonDeliveryMethod
Attributes

DeliveryMethodId HCM Extract
Person Drivers License

Requirement All driver license records for the parent ex-employee
Instruction DELETE
Discriminator PersonDriversLicence
Attributes
DriversLicenseId HCM Extract
Person E-mail
Requirement All e-mail records for the parent ex-employee
Instruction DELETE
Discriminator PersonEmail
Attributes
EmailAddressId HCM Extract
Person Ethnicity
Requirement All ethnicity records for the parent ex-employee
Instruction DELETE
Discriminator PersonEthnicity
Attributes
EthnicityId HCM Extract
Person National Identifier

Requirement All national identifier records for the parent ex-employee
Instruction DELETE
Discriminator PersonNationalIdentifier
Attributes
NationalIdentifierId HCM Extract

Person Passport
Requirement All passport records for the parent ex-employee
Instruction DELETE
Discriminator PersonPassport
Attributes
PassportId HCM Extract
Person Phone
Primary phone numbers cannot be purged, whilst secondary phone numbers exist. To provide obfuscation is one
step, mask the primary phone number whilst deleting the secondary phone numbers.
Requirement All primary phone records for the parent ex-employee

Instruction MERGE
Attributes
PhoneId HCM Extract
DateFrom HCM Extract Format YYYY/MM/DD
CountryCodeNumber ‘#NULL’
AreaCode ‘#NULL’
PhoneNumber ‘000000’
Extension ‘#NULL’
SpeedDialNumber ‘#NULL’
Requirement All secondary phone records for the parent ex-employee

Instruction DELETE
Attributes
PhoneId HCM Extract
DateFrom ‘’
CountryCodeNumber ‘’

AreaCode ‘’
PhoneNumber ‘’
Extension ‘’
SpeedDialNumber ‘’
Person Religion
Requirement All religion records for the parent ex-employee
Instruction DELETE
Discriminator PersonReligion
Attributes
ReligionId HCM Extract
Person Visa
Requirement All visa records for the parent ex-employee
Instruction DELETE
Discriminator PersonVisa
Attributes
VisaPermitId HCM Extract
The effective start date is also required when deleting visa records.
Person Image
Requirement All image records for the parent ex-employee
Instruction DELETE
Discriminator PersonImage
Attributes
ImageId HCM Extract
Assignment Supervisor
Requirement All supervisor records for the parent assignment
Instruction DELETE

Discriminator AssignmentSupervisor
Attributes
AssignmentSupervisorId HCM Extract
Assignment Work Measure

Requirement All work measure records for the parent assignment
Instruction DELETE
Discriminator AssignmentWorkMeasure
Attributes
AssignWorkMeasureId HCM Extract
Now that all components, attributes, attribute values and actions have been identified the next steps are:
 Create fast formulae to perform the required actions,
 Map the attributes that need values to be extracted to the user entity and attribute that will provide the
data.
Creating Fast Formulae

Three fast formulae are required to format the dates and mask the date of birth. These must all have a type of
‘Extract Rule’.
Name Formula Text
HDL_START_DATE_FORMAT INPUTS ARE DATA_ELEMENTS (TEXT_TEXT)

rule_date_value = TO_DATE(substr(DATA_ELEMENTS['Start_Date'], 1,
10),'YYYY/MM/DD')
return rule_value
HDL_END_DATE_FORMAT INPUTS ARE DATA_ELEMENTS (TEXT_TEXT)

rule_date_value = TO_DATE(substr(DATA_ELEMENTS['End_Date'], 1,
10),'YYYY/MM/DD')
return rule_value
HDL_MASK_DATE_OF_BIRTH INPUTS ARE DATA_ELEMENTS (TEXT_TEXT)

rule_date_value = ADD_YEARS(TO_DATE(substr(DATA_ELEMENTS['Start_Date'], 1,
10),'YYYY/MM/DD'),-20)
return rule_value

Designing the HCM Extract
Before creating the extract, determine the data groups, population and HCM Data Loader business object
component discriminator. Identify the connections between them and the data group flow:
Data Groups
HDL
Name Data Restriction
Discriminator
Terminated Workers n/a All ex-employees terminated over 6 years ago, that haven’t previously
been obfuscated.
Worker Worker A single person related data record for each Terminated Worker
Address PersonAddress All address records for each Terminated Worker
Legislative Data PersonLegislativeData All legislative data records for each Terminated Worker
Name PersonName A single name record spanning the employment of each Terminated
Worker
Work Relationship WorkRelationship All work relationships for each Terminated Worker
Employment Terms WorkTerms All employment terms for each Work Relationship
Assignment Assignment All assignments for each Employment Terms record
Citizenship PersonCitizenship All citizenship records for each Terminated Worker
Delivery Method PersonDeliveryMethod All delivery methods for each Terminated Worker
Drivers License PersonDriversLicense All driver license records for each Terminated Worker
Ethnicity PersonEthnicity All ethnicity records for each Terminated Worker
National Identifier PersonNationalIdentifier All national identifier records for each Terminated Worker
Passport PersonPassport All passport records for each Terminated Worker
Phone PersonPhone All phone records for each Terminated Worker
Religion PersonReligion All religion records for each Terminated Worker
Visa PersonVisa All visa records for each Terminated Worker

Data Group Process Flow Key
Data Group
Detail Record
Hierarchy Traversal Record

Terminated Workers
(root data group) Worker
Population Worker
Address
Worker Data PersonAddress

Legislative Data
Address Data PersonLegislativeData

Name
Legislative Data PersonName

Work Relationship
Name Data WorkRelationship
Employment Terms
Work Relationship Data Employment Term Data WorkTerms

Assignment
Citizenship Data Assignment Data
Assignment
Citizenship
Delivery Method Data PersonCitizenship

Delivery Method
Drivers License Data PersonDeliveryMethod

Drivers License
Email Data PersonDriversLicence

Email
Ethnicity Data PersonEmail

Ethnicity
National Identifier Data PersonEthinicity

National Identifier
Passport Data PersonNationalIdentifier

Passport
Phone Data PersonPassport

Phone
Religion Data PersonPhone

Religion
Visa Data PersonReligion

Visa
PersonVisa

Identify the User Entities and Attributes
For each data group, identify the user entity (UE) that provides the data and map the HDL attributes to be extracted
to the user entity attributes.
For example:
Worker
User Entity PER_EXT_SEC_PERSON_UE
Attributes
HDL Attribute UE Attribute Action
PersonId Extract Person ID
EffectiveStartDate Extract Person Effective Start Date Formula: HDL_START_DATE_FORMAT
PersonNumber Person Number
DateOfBirth Extract Person Effective Start Date Formula: HDL_MASK_DATE_OF_BIRTH
Person Address
User Entity PER_EXT_PERSON_ADDRESSES_UE
Attributes
HDL Attribute UE Attribute Action
PersonAddrUsageId Extract Person Address Usage Person ID
PersonId Extract Person Address Usage ID
EffectiveStartDate Extract Person Address Effective Start Formula: HDL_START_DATE_FORMAT

Date
AddressType Extract Person Address Usage Address

Type
This mapping example is not extended further as the complete information is provided in the Data Groups section of
Defining the HCM Extract.
Defining the HCM Extract

This section provides the instructions for creating the HCM Extract for the Worker object. It is recommended that
only the root data group and the first component data group are created before creating the XML delivery option and
testing that your extract includes the expected population. Test repeatedly as new data groups are defined.
The Creating the Extract section provides step by step instructions and screen shots on how to create and test a
HCM Extract.
Create an HCM Extract

Create a new Inbound Interface extract, providing a name and start date. The type must be Inbound Interface.

Create the Root Data Group
The root data group identifies the terminated employees to obfuscate for data privacy.
Name Terminated Worker

User Entity PER_EXT_WORK_RELATIONSHIP_ALL_UE
Filter Criteria
Filter Criteria
Extract Relationship Actual Termination Date <= Effective Date
Detail Record
Sequence 10
Name Population
User Entity Attributes
Overridden
Attribute Short Code HDL Attribute
Extract Relationship Person Id PersonId
Person Number
Extract Relationship Date Start
Extract Relationship Actual Termination Date
Person Image ID ImageId
As the image details are available within this user entity, the PersonImage records can be
generated using this data, rather than creating a separate data group.
Create Component Data Group: Person

User Entity PER_EXT_SEC_PERSON_UE
Connect Data Groups
Parent Data Group Parent Data Group Database Item Database Item
Terminated Worker Extract Relationship Person Id Extract Person ID
Detail Record
Sequence 10
Name Worker
Overridden
Extract Person ID PersonId

Extract Person Effective Start Date Start_Date
Person Number PersonNumber
Rule Attributes
Both rule based attributes will use formulae to convert the value extracted for the attribute that has a short
code of Start_Date, namely ‘Extract Person Effective Start Date’.
Two separate rule attributes are required to output the two different converted values of this attribute. ‘Person
Effective Start Date’ will output the value in the HDL date format. ‘Date of Birth’ will output the date 20 years
prior to be used to mask the date of birth.
Output
Attribute Column Rule HDL Attribute
Person Effective Start Date 100 HDL_START_DATE_FORMAT EffectiveStartDate
Date Of Birth 110 HDL_MASK_DATE_OF_BIRTH DateOfBirth
All rule attributes used for formatting dates should have a Data Type of Text.
Hierarchy Traversal
Record
Data Group Sequence Name Next Data Group
Terminated Worker 20 Worker Data Person
All hierarchy traversal records must have a Type of Hierarchy traversal only.
Create Component Data Group: Person Address

User Entity PER_EXT_PERSON_ADDRESSES_UE
Connect Data Groups
Terminated Worker Extract Relationship Person Id Extract Person Address Usage Person ID
Detail Record
Sequence 10
Name PersonAddress
Overridden
Extract Person Address Usage ID PersonId
Extract Person Address Usage Person ID PersonAddrUsageId
Extract Person Address Effective Start Date Start_Date
Extract Person Address Usage Address Type AddressType
Rule Attributes

Output
Person Address Effective Start 100 HDL_START_DATE_FORMAT EffectiveStartDate

Date
Hierarchy Traversal
Record
Terminated Worker 30 Address Data Person Address
Create Component Data Group: Person Legislative Data

User Entity PER_EXT_PER_ALL_LEGISLATIVE_DETAILS_UE
Connect Data Groups
Terminated Worker Extract Relationship Person Id Extract People Legislative Person ID
Detail Record
Sequence 10
Name PersonLegislativeData
Overridden
Extract People Legislative ID PersonLegislativeId
Extract People Legislative Person Id PersonId
Extract People Legislative Effective Start Date Start_Date
Extract People Legislative Effective End Date End_Date
Extract People Legislative Legislation Code LegislationCode
Person Start Date
Person Start Date is required to filter which records are included by the eText template.
Rule Attributes
Output
Legislative Effective Start Date 100 HDL_START_DATE_ FORMAT EffectiveStartDate
Legislative Effective End Date 110 HDL_END_DATE_ FORMAT EffectiveEndDate
Hierarchy Traversal
Record

Terminated Worker 40 Legislative Data Person Legislative Data
Create Component Data Group: Name

User Entity PER_EXT_HISTORY_PERSON_NAMES_UE
Connect Data Groups
Terminated Worker Extract Relationship Person Id Extract Historical Person Name Person
Id
Terminated Worker Extract Relationship Date Start Extract Historical Person Name Effective
Start Date
Detail Record
Sequence 10
Name PersonName
Overridden
Extract Historical Person Name ID PersonNameId
Extract Historical Person Name Person Id PersonId
Extract Historical Person Name Effective Start Date Start_Date
Extract Historical Person Name Character Set Context CharSetContext
Extract Historical Person Name Legislation Code LegislationCode
Extract Historical Person Name Type NameType
Rule Attributes
Output
Person Name Effective Start 100 HDL_START_DATE_ FORMAT EffectiveStartDate

Date
Hierarchy Traversal
Record
Terminated Worker 50 Name Data Name

Create Component Data Group: Work Relationship
User Entity PER_EXT_WORK_RELATIONSHIP_ALL_UE
Connect Data Groups
Terminated Worker Extract Relationship Person Id Extract Relationship Person Id
Terminated Worker Extract Relationship Period Of Service Id Extract Relationship Period Of Service Id
Detail Record
Sequence 10
Name WorkRelationship
Overridden
Extract Relationship Period Of Service Id PeriodOfServiceId
Extract Relationship Person Id PersonId
Extract Relationship Date Start Start_Date
Extract Relationship Legal Entity Id LegalEntityId
Relationship Actual Termination Date End_Date
Rule Attributes
Output
Work Relationship Date Start 100 HDL_START_DATE_FORMAT DateStart
Actual Termination Date 110 HDL_END_DATE_FORMAT ActualTerminationDate
Hierarchy Traversal
Record
Terminated Worker 60 Work Relationship Data Work Relationship
Create Component Data Group: Employment Terms

User Entity PER_EXT_SEC_HISTORY_ASSIGNMENTS_UE
Connect Data Groups
Work Relationship Extract Relationship Period Of Service Id Extract Historical Assignment Period of
service ID

Detail Record
Sequence 10
Name WorkTerms
Overridden
Assignment Effective Start Date Start_Date
Assignment Effective End Date End_Date
Assignment Effective Seqeuence EffectiveSequence
Assignment Effective Latest Change EffectiveLatestChange
Assignment Period Of Service ID PeriodOfServiceId
Assignment Action Code ActionCode
Extract Historical Assignment Work Term ID AssignmentId
Assignment Primary Work Terms Indicator PrimaryWorkTermsFlag
Rule Attributes
Output
Work Terms Effective Start Date 100 HDL_START_DATE_FORMAT EffectiveStartDate
Work Terms Effective End Date 110 HDL_END_DATE_FORMAT EffectiveEndDate
Hierarchy Traversal
Record
Work Relationship 20 Employment Terms Data Employment Terms
Create Component Data Group: Assignment

User Entity PER_EXT_SEC_HISTORY_ASSIGNMENTS_UE
Connect Data Groups
Employment Terms Extract Historical Assignment Work Term Extract Historical Assignment Work Term
ID ID
Employment Terms Extract Historical Assignment Effective Extract Historical Assignment Effective
Start Date - Context Item Start Date - Context Item
Employment Terms Extract Historical Assignment Effective Extract Historical Assignment Effective
Sequence Sequence
Detail Record
Sequence 10

Name Assignment
Overridden
Extract Historical Assignment ID AssignmentId
Assignment Work Terms Assignment ID WorkTermsAssignmentId
Assignment Action Code ActionCode
Assignment Effective Start Date Start_Date
Assignment Effective End Date End_Date
Assignment Effective Sequence EffectiveSequence
Assignment Effective Latest Change EffectiveLatestChange
Assignment Primary Indicator PrimaryAssignmentFlag
Rule Attributes
Output
Asg Effective Start Date 100 HDL_START_DATE_ FORMAT EffectiveStartDate
Asg Effective End Date 110 HDL_END_DATE_ FORMAT EffectiveEndDate
Hierarchy Traversal
Record
Employment Terms 20 Assignment Data Assignment
Create Component Data Group: Citizenship

User Entity PER_PER_CITIZENSHIPS_UE
Connect Data Groups
Terminated Worker Extract Relationship Person Id Extract Person Citizenship Person ID
Detail Record
Sequence 10
Name PersonCitizenship
Overridden
Extract Person Citizenship Id CitizenshipId

Overridden
Citizenship Person ID PersonId
Hierarchy Traversal
Record
Terminated Worker 70 Citizenship Data Citizenship
Create Component Data Group: Person Delivery Method

User Entity PER_PERSON_DLVRY_METHODS_UE
Connect Data Groups
Terminated Worker Extract Relationship Person Id Person Delivery Method Person Id
Detail Record
Sequence 10
Name PersonDeliveryMethod
Overridden
Person Delivery Method Delivery Method Id DeliveryMethodId
Person Delivery Method Person Id PersonId
Hierarchy Traversal
Record
Terminated Worker 80 Delivery Method Data Person Delivery Method
Create Component Data Group: Person Drivers License

User Entity PER_EXT_DRIVING_LICENSE_UE
Connect Data Groups
Terminated Worker Extract Relationship Person Id Extract Driving License Person Id
Detail Record
Sequence 10

Name PersonDriversLicence
Overridden
Extract Driving License Drivers License ID DriversLicenseId
Extract Driving License Person Id PersonId
Hierarchy Traversal
Record
Terminated Worker 90 Drivers License Data Person Drivers License
Create Component Data Group: Email

User Entity PER_PER_EMAIL_ADDRESSES _UE
Connect Data Groups
Terminated Worker Extract Relationship Person Id Person All E-Mail Person All ID
Detail Record
Sequence 10
Name PersonEmail
Overridden
Person All Email Address ID EmailAddressId
Person All Email Person All ID PersonId
Hierarchy Traversal
Record
Terminated Worker 100 Email Data Email
Create Component Data Group: Person Ethnicity

User Entity PER_PER_ETHNICITIES_ALL _UE
Connect Data Groups

Terminated Worker Extract Relationship Person Id Person All Ethnicity Person Id
Detail Record
Sequence 10
Name PersonEthnicity
Overridden
Person All Ethnicity Id EthnicityId
Person All Ethnicity Person Id PersonId
Hierarchy Traversal
Record
Terminated Worker 110 Ethnicity Data Person Ethnicity
Create Component Data Group: Person National Identifier

User Entity PER_PER_NATIONAL_IDENTIFIERS_UE
Connect Data Groups
Terminated Worker Extract Relationship Person Id Person National Identifier Person ID
Detail Record
Sequence 10
Name PersonNationalIdentifier
Overridden
Person National Identifier ID NationalIdentifierId
Person National Identifier Person ID PersonId
Hierarchy Traversal
Record
Terminated Worker 120 National Identifier Data Person National Identifier

Create Component Data Group: Person Passport
User Entity PER_PER_PASSPORT_UE
Connect Data Groups
Terminated Worker Extract Relationship Person Id Extract Person Passport Person Id
Detail Record
Sequence 10
Name PersonPassport
Overridden
Extract Person Passport Id PassportId
Extract Person Passport Person Id PersonId
Hierarchy Traversal
Record
Terminated Worker 130 Passport Data Person Passport
Create Component Data Group: Person Phone

User Entity PER_PER_PHONES_UE
Connect Data Groups
Terminated Worker Extract Relationship Person Id Person All Phone Person ID
Detail Record
Sequence 10
Name PersonPhone
Overridden
Person All Phone ID PhoneId
Person All Phone Person ID PersonId
Person All Phone Date From Start_Date

Rule Attributes
Output
Phone Date From 100 HDL_START_DATE_ FORMAT EffectiveStartDate
Hierarchy Traversal
Record
Terminated Worker 140 Phone Data Person Phone
Create Component Data Group: Person Religion

User Entity PER_EXT_RELIGION_UE
Connect Data Groups
Terminated Worker Extract Relationship Person Id Extract Religion Person ID
Detail Record
Sequence 10
Name PersonReligion
Overridden
Extract Religion ID ReligionId
Extract Religion Person ID PersonId
Hierarchy Traversal
Record
Terminated Worker 150 Religion Data Person Religion
Create Component Data Group: Person Visa

User Entity PER_PER_ALL_VISA_PERMITS_UE
Connect Data Groups

Terminated Worker Extract Relationship Person Id Person All Visa Permit Person Id
Detail Record
Sequence 10
Name PersonVisa
Overridden
Person All Vis Permit Id VisaPermitId
Person All Vis Permit Person Id PersonId
Person All Vis Permit Effective Start Date Start_Date
Rule Attributes
Output
Visa Effective Start Date 100 HDL_START_DATE_ FORMAT EffectiveStartDate
Hierarchy Traversal
Record
Terminated Worker 160 Visa Data Person Visa
Create XML Delivery Option

Create an XML delivery option to test that the expected values have been extracted for each attribute. The XML
attribute tags are the values used to reference the attribute values in the eText template.
Delivery Option Name WorkerTest
Output Type Data

Output Name TestOutput
Define the eText Template

This section describes how to create the eText template to generate the example worker file defined in the Defining
the HCM Data Loader File section.
Note: The ObfuscateWorkerTemplate.rtf file used in this worked example is available on My Oracle Support from the
same document as this white paper.
Create a single rich text format document with the following sections:

Define the Template Type
<TEMPLATE TYPE> DELIMITER_BASED

<OUTPUT CHARACTER SET> ASCII
<NEW RECORD CHARACTER> Carriage Return
Define the level for the Extract

<LEVEL> DATA_DS
Define all HCM Data Loader commands

<NEW RECORD> REPLACE_FUTURE_CHANGES
<DISPLAY 1=1
CONDITION>
LENGTH>
100 Alpha 'SET PURGE_FUTURE_CHANGES
Y'
Define the METADATA records
<NEW WORKER_HEADER
RECORD>
<DISPLAY 1=1
CONDITION>
LENGTH>
100 Alpha 'METADATA|Worker'
1 Alpha '|'
100 Alpha 'PersonId' PersonId
1 Alpha '|'
1 Alpha '|'
100 Alpha 'EffectiveStartDate' EffectiveStartDate
1 Alpha '|'
100 Alpha 'DateOfBirth' DateOfBirth
1 Alpha '|'
100 Alpha 'DateOfDeath' DateOfDeath
1 Alpha '|'
100 Alpha 'CountryOfBirth' CountryOfBirth
1 Alpha '|'
100 Alpha 'RegionOfBirth' RegionOfBirth
1 Alpha '|'
100 Alpha 'TownOfBirth' TownOfBirth
1 Alpha '|'
100 Alpha 'ApplicantNumber' ApplicantNumber
1 Alpha '|'
100 Alpha 'BloodType' BloodType
1 Alpha '|'
100 Alpha 'CorrespondenceLanguage' CorrespondenceLanguage
<NEW RECORD> PERSON_ADDRESS_HEADER

<DISPLAY 1=1
CONDITION>
LENGTH>
100 Alpha 'METADATA|PersonAddress’
1 Alpha '|'
100 Alpha 'PersonAddrUsageId’ PersonAddrUsageId
1 Alpha '|'
100 Alpha 'PersonId’ PersonId
1 Alpha '|'
100 Alpha 'EffectiveStartDate’ EffectiveStartDate
1 Alpha '|'
100 Alpha 'AddressType’ AddressType
1 Alpha '|'
100 Alpha 'Country’ Country
1 Alpha '|'
100 Alpha 'AddressLine1’ AddressLine1
1 Alpha '|'
1 Alpha '|'
1 Alpha '|'
1 Alpha '|'
100 Alpha 'TownOrCity’ TownOrCity
1 Alpha '|'
100 Alpha 'Region1’ Region1
1 Alpha '|'
100 Alpha 'Region2’ Region2
1 Alpha '|'
100 Alpha 'PostalCode’ PostalCode
Repeat for each component to be obfuscated.
Define the Root Data Group Level

The level name should match the root data group
<LEVEL> Terminated_Workers
Define the Data Line Records

Define each data line, with a wrapping level if there is a potential for multiple records for the terminated worker.
If defining a level it must have the same name as the data group name used to extract the attributes referenced in
the record definition.
<NEW Worker
RECORD>
<DISPLAY 1=1
CONDITION>
LENGTH>
100 Alpha 'MERGE|Worker'
1 Alpha '|'
100 Alpha Extract_Person_ID PersonId

1 Alpha '|'
100 Alpha Person_Number PersonNumber
1 Alpha '|'
100 Alpha Person_Effective_Start_Date EffectiveStartDate
1 Alpha '|'
100 Alpha Date_Of_Birth DateOfBirth
1 Alpha '|'
10 Alpha '#NULL' DateOfDeath
1 Alpha '|'
10 Alpha '#NULL' CountryOfBirth
1 Alpha '|'
10 Alpha '#NULL' RegionOfBirth
1 Alpha '|'
10 Alpha '#NULL' TownOfBirth
1 Alpha '|'
10 Alpha '#NULL' ApplicantNumber
1 Alpha '|'
10 Alpha '#NULL' BloodType
1 Alpha '|'
10 Alpha '#NULL' CorrespondenceLanguage
<LEVEL> Person_Address
<NEW PersonAddress
RECORD>
<DISPLAY 1=1
CONDITION
>
<MAXIUMUM <FORMAT <DATA> <TAG <COMMENTS>
LENGTH> > >
100 Alpha 'MERGE|PersonAddress'
1 Alpha '|'
100 Alpha Extract_Person_Address_Usage_ID PersonAddrUsageI
d
1 Alpha '|'
100 Alpha Extract_Person_Address_Usage_Person_ID PersonId
1 Alpha '|'
100 Alpha Person_Address_Effective_Start_Date EffectiveStartDa
te
1 Alpha '|'
100 Alpha Extract_Person_Address_Usage_Address_T AddressType
ype
1 Alpha '|'
100 Alpha 'US' Country
1 Alpha '|'
100 Alpha 'Masked Address' AddressLine1
1 Alpha '|'
100 Alpha '#NULL' AddressLine2
1 Alpha '|'
1 Alpha '|'
1 Alpha '|'
100 Alpha 'New York' TownOrCity
1 Alpha '|'
100 Alpha 'New York' Region1
1 Alpha '|'

100 Alpha 'NY' Region2
1 Alpha '|'
100 Alpha '10130' PostalCode
<END LEVEL> Person_Address
Repeat for each component to be obfuscated.
Close the Root Data Group Level

<END LEVEL> Terminated_Workers
Close the Extract Level

<END LEVEL> DATA_DS
Once you have defined your eText template, follow the instructions provided in the Uploading the eText Template
section. Define the Inbound Interface delivery option and test.
This concludes the worked example for the worker business object.

Appendix: Deleting Users
This appendix discusses an example of user deletion. The User Delete functionality is available in Release 13.
Users can be loaded using HCM Data Loader. These records will then be processed when running the Send
Pending LDAP Requests process. When using the User HDL object to create Users, a Person Number must be
provided for an existing person. The User HDL Object is used to create the User Account records for those person
records that were already created. HDL can also be used to delete users using the person number. Here is an
example:
METADATA|User|PersonNumber
DELETE|User|1111111
Define the METADATA Records

<NEW USER_HEADER
RECORD>
<DISPLAY 1=1
CONDITION
>
<MAXIUMUM <FORMAT <DATA> <TAG> <COMMENTS>
LENGTH> >
100 Alpha 'METADATA|User'
1 Alpha '|'
Define the Data Line Records

<NEW USER
RECORD>
<DISPLAY 1=1
CONDITION
>
<MAXIUMUM <FORMAT <DATA> <TAG> <COMMENTS>
LENGTH> >
100 Alpha 'DELETE|User'
1 Alpha '|'
100 Alpha 'Person_Number' PersonNumber

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. 1117
Disposal of Employee Data in Oracle Fusion HCM

November 2017

Disposal of Employee Data in Oracle Fusion HCM PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Disposal of Employee Data in Oracle Fusion HCM PDF

Загружено:

Авторское право:

Доступные форматы

Implementing Information Retention and Disposal

Policies in Oracle Fusion HCM

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

Implementing Information Retention and Disposal Policies in Oracle Fusion HCM 0

DISPOSAL OF EMPLOYEE DATA IN ORACLE FUSION HCM

DISPOSAL OF EMPLOYEE DATA IN ORACLE FUSION HCM

DISPOSAL OF EMPLOYEE DATA IN ORACLE FUSION HCM

1 | DISPOSAL OF EMPLOYEE DATA IN ORACLE FUSION HCM

 Delete records that can be safely purged.

o Remove attribute values for non-mandatory attributes.

o Mask personal identifiable values for mandatory attributes.

 HDL delete lines to purge records.

o Set non-mandatory attributes to null.

o Mask identifying mandatory attributes.

HCM Data Loader

Figure 1: Steps to Dispose Ex-employee Records

2 | DISPOSAL OF EMPLOYEE DATA IN ORACLE FUSION HCM

5. Update the HCM Extract to utilize the eText template

6. Test the end-to-end process.

Designing the HCM Data Loader File

1. Understand the file control commands that should be included.

3 | DISPOSAL OF EMPLOYEE DATA IN ORACLE FUSION HCM

HCM Data Loader File Control Commands

Identifying HCM Data Loader Components and Attributes

Example: Purging Person Email

Example: Obfuscating Worker

4 | DISPOSAL OF EMPLOYEE DATA IN ORACLE FUSION HCM

Testing the HCM Data Loader File

Designing the HCM Extract

Root Data Group

Component Data Groups

5 | DISPOSAL OF EMPLOYEE DATA IN ORACLE FUSION HCM

Hierarchy Traversal Records

6 | DISPOSAL OF EMPLOYEE DATA IN ORACLE FUSION HCM

Defining the Extract

Figure 4: Fast Formula - Manage Fast Formulas

1. Click the Create button on the table toolbar

Figure 5: Fast Formula - Create Fast Formula

2. In the Create Fast Formula popup

7 | DISPOSAL OF EMPLOYEE DATA IN ORACLE FUSION HCM

Creating the Extract

Figure 7: HCM Extract - Creating an Extract

Defining a Data Group

Steps to create a Data Group

8 | DISPOSAL OF EMPLOYEE DATA IN ORACLE FUSION HCM

2. Specify the name and user entity.

Adding Filter Criteria

2. Click Edit button on the Data Group Filter Criteria popup

Figure 9: HCM Extract - Creating Filter Conditions

Creating a Detail Record

9 | DISPOSAL OF EMPLOYEE DATA IN ORACLE FUSION HCM

Figure 11: HCM Extract - Creating a Detail Record

Figure 12: HCM Extract - Detail Record

10 | DISPOSAL OF EMPLOYEE DATA IN ORACLE FUSION HCM

Formatting a Date Attribute

Figure 14: HCM Extract - Reviewing Attribute Properties

11 | DISPOSAL OF EMPLOYEE DATA IN ORACLE FUSION HCM

3. Save the change

Figure 16: HCM Extract - Creating an Attribute

5. Provide the details for the new attribute:

12 | DISPOSAL OF EMPLOYEE DATA IN ORACLE FUSION HCM

Creating a Data Group Connection

Figure 18: HCM Extract - Creating the Data Group Connection