Professional Documents
Culture Documents
EBS Extraction Toolkit For HDL PDF
EBS Extraction Toolkit For HDL PDF
2 | EBS HCM Extraction Toolkit for HCM Cloud Integration Using HCM Data Loader
Introduction
This document provides details on the Extraction Toolkit that enables users to extract certain HR objects from
an EBS source. The HCM Data Loader uses this extracted information for integrating with HCM Cloud. It
provides the details on the basic flow and functionality of the extraction process.
The Extraction Toolkit is a set of tools to extract HR objects from an EBS source for integrating with HCM
Cloud using HCM Data Loader. This toolkit
Provides a reference point for users to extract data from EBS system for
integrating with HCM Cloud using HCM Data Loader.
Can be extended for your business needs.
Process Flow
3 | EBS HCM Extraction Toolkit for HCM Cloud Integration Using HCM Data Loader
Creating Sample Data
This section describes why you need to create sample data using the data creation
scripts and the steps to create the necessary business objects.
You need to create the sample data to demonstrate how the Extraction Toolkit
transforms and extracts the data that can be consumed by the HCM Data Loader
process.
A database script is provided to create sample data. The database script creates a
business group and related entities such as jobs, position, grade, person, assignment,
etc. You must run the script to create sample data on your EBS Test system.
The sample data creation script creates a new business group named Moon
Corporation with the following business objects:
Locations
HR Organizations
Jobs
Positions
Grade
Persons
Assignments
Qualification Types
Performance Ratings
Qualifications
4 | EBS HCM Extraction Toolkit for HCM Cloud Integration Using HCM Data Loader
The following diagram represents some of the HR Business Objects that are created by
the sample data creation script.
You can find more details on the sample data in the spreadsheet - Sample Data.xls which can be
downloaded from My Oracle Support, Note ID 1942763.1
5 | EBS HCM Extraction Toolkit for HCM Cloud Integration Using HCM Data Loader
Extracting Data using Toolkit
This section explains the steps to perform reference data mapping and extracting the
sample data using the Extraction Toolkit. The Extraction Toolkit transforms the data
into a HCM Cloud format and stores the transformed data in a set of staging tables in
EBS system.
Extraction Toolkit
The Extraction Toolkit contains database packages that perform transformation and
extraction of EBS HR data into HCM Cloud format.
The extraction packages are coded specific for the Sample Setup created in the
previous chapter.
Package procedures contain the transformation logic to generate data to HCM
Cloud Object Shape.
Transformed data is populated into a set of staging tables.
HCM Cloud Objects extracted for the Sample Setup can be loaded to HCM Cloud
without any modifications.
You can extend the transformation logic based on your business need.
The Extraction Toolkit has the sample codes to extract the following Business Objects
The list covers most of the business objects that are required for Talent integration to
HCM Cloud that enables users to implement and start using Talent related functions
like Goal Setting, Performance Management, and Talent Review. Users can extend the
6 | EBS HCM Extraction Toolkit for HCM Cloud Integration Using HCM Data Loader
toolkit to add objects to support Compensation integration such as Salary Basis, Salary,
and Element Entries.
The Extraction program provided as a part of the Toolkit extracts all the business
objects for each run of the extraction process. The extracted data in DAT files can
then be used to load to HCM Cloud using HCM Data Loader. This caters to the initial
load, where a complete set of data is uploaded to HCM Cloud. HCM Data Loader also
supports incremental upload of data to HCM Cloud. The DAT file needs to be
generated to contain only objects that have changes. Users can modify the Extraction
Toolkit to extract only those objects with delta changes from the last upload of data to
HCM Cloud. There are various ways for users to identify the delta changes. You can
use the Record History (WHO columns) to identify who created or updated rows in
Oracle E-Business Suite HCM tables.
LAST_ UPDATED_BY NUMBER(15) NOT NULL Keeps track of who last updated each row
LAST_UPDATE_ DATE DATE NOT NULL Stores the date on which each row was last updated
Another option is to maintain a snapshot of the extracted data that is held in staging
tables and use this snapshot to compare and identify the changes.
7 | EBS HCM Extraction Toolkit for HCM Cloud Integration Using HCM Data Loader
Mapping Data
Business objects that originate in your source system may reference other business
objects defined manually in the HCM Cloud system such as reference data set and
legal employer. For these referenced business objects, you must map them in your
extraction package.
The following table displays the Oracle HCM Cloud business objects for which you
need to map the reference information.
Business Objects
Employment Action Reason
Person Assignment Status Type
Enterprise
Talent Profile Content Item
Talent Profile Content Type
Talent Profile Type
Talent Instance Qualifier Set
Legal Entity
Legislative Data Group
Payroll Element Type
Payroll Element Input Value
Person Type
Reference Data Set
You must modify this package to map the reference data to the global variable values.
The following table displays the details of the package variables to be modified and the
description of that variable:
The Extraction Toolkit accepts the reference information as package level variables.
Users can extend this mapping to provide a custom user interface for end users to
manage this mapping.
The Extraction Process transforms the data and stores it in a set of staging
tables. You must create the staging tables on an EBS Test instance prior to
running the Extraction Process.
Note: All staging tables are created with a prefix XX_DL_EXTRACT, for
example XX_DL_EXTRACT_LOCATIONS.
After you perform the mapping and creating the staging tables, you can run
the extraction process.
9 | EBS HCM Extraction Toolkit for HCM Cloud Integration Using HCM Data Loader
1. Login as apps database user on your EBS Test instance.
2. Create the packages shown in Extraction Toolkit, by executing the scripts
contained in XX_DL_EXTRACT_TOOLKIT.zip
For example, the statement given below extracts the data associated with
Moon Corporation and loads them into the staging tables.
This procedure extracts the data from the HCM source tables onto staging
tables and exits if errors are encountered during the process. If you want to
view the errors, you can redirect the output to file:
10 | EBS HCM Extraction Toolkit for HCM Cloud Integration Using HCM Data Loader
Generating DAT Files
Once the extraction is complete, the transformed data is stored in the staging
tables. This chapter explains the steps required to generate the DAT file
required for data upload to HCM Cloud system from the staging tables.
Data Loader Top Business Object SQL File that contain the query to generate the
DAT file data with | as the separator
Organization Organization.sql
Worker Worker.sql
Profile Profile.sql
RatingModel RatingModel.sql
ContentItem ContentItem.sql
Position Position.sql
EducationEstablishment EducationEstablishment.sql
Job Job.sql
Grade Grade.sql
Location Location.sql
Next Steps
The data that you extract from your source system to upload to Oracle HCM
Cloud must be delivered as a zip file that contains one or more data files (.dat
file). Zip file creation and uploading are explained in the following section.
11 | EBS HCM Extraction Toolkit for HCM Cloud Integration Using HCM Data Loader
Create Zip file to upload to HCM Cloud
The flat file related to a Business Object must be zipped to create a zip file. A
zip file can contain one or more flat files.
Details of Business Objects, and its corresponding top business object names
and the flat file names are specified in the table given below:
Data Loader Business Object Data Loader Top Business Object Data Loader Flat File Name
Organization Organization Organization.dat
OrgUnitClassification Organization Organization.dat
Worker Worker Worker.dat
PersonName Worker Worker.dat
PersonNationalIdentifier Worker Worker.dat
PersonEmail Worker Worker.dat
PersonAddress Worker Worker.dat
PersonPhone Worker Worker.dat
PersonEthnicity Worker Worker.dat
PersonLegislativeData Worker Worker.dat
WorkRelationship Worker Worker.dat
WorkTerms Worker Worker.dat
Assignment Worker Worker.dat
AssignmentSupervisor Worker Worker.dat
PersonCitizenship Worker Worker.dat
TalentProfile Profile Profile.dat
ProfileItem Profile Profile.dat
ProfileRelation Profile Profile.dat
RatingModel RatingModel RatingModel.dat
RatingLevel RatingModel RatingModel.dat
ContentItem ContentItem ContentItem.dat
EducationEstablishment EducationEstablishment EducationEstablishment.dat
Grade Grade Grade.dat
Position Position Position.dat
Job Job Job.dat
Location Location Location.dat
The zip files that have to be uploaded using the HCM Data Loader are shown
in the table given below.
Data Loader Top Business Object Data Loader Zip File Name
Organization Organization.zip
Worker Worker.zip
Profile Profile.zip
RatingModel RatingModel.zip
ContentItem ContentItem.zip
EducationEstablishment EducationEstablishment.zip
Grade Grade.zip
Position Position.zip
Job Job.zip
Location Location.zip
12 | EBS HCM Extraction Toolkit for HCM Cloud Integration Using HCM Data Loader
Upload to HCM Cloud
Refer to Oracle HCM Data Loader: User Guide - My Oracle Support Note
ID 1664133.1 for the steps to upload the zip file to Oracle HCM Cloud.
13 | EBS HCM Extraction Toolkit for HCM Cloud Integration Using HCM Data Loader
Validation Scripts
The data that you extract from your source system to upload to Oracle HCM
Cloud must conform to certain HCM Cloud business rule validations. Prior to
upload, you can use the validation scripts to verify the data in your EBS source
system.
The table provides a list of some of the validations that you can perform on
the data in your source system.
14 | EBS HCM Extraction Toolkit for HCM Cloud Integration Using HCM Data Loader
NVL(DATE_TO,TO_DATE('31-DEC-4712','DD-MON-YYYY'))
Assignments having SELECT * FROM PER_ALL_ASSIGNMENTS_F WHERE NORMAL_HOURS IS NOT NULL AND FREQUENCY IS
value for normal hours NULL
but without frequency
defined.
Identifying Positions SELECT POS.POSITION_ID,POS.EFFECTIVE_START_DATE,POS.EFFECTIVE_END_DATE,POS.NAME,
attached to inactive LOC.LOCATION_ID,LOC.LOCATION_CODE,LOC.INACTIVE_DATE
location FROM HR_ALL_POSITIONS_F POS,HR_LOCATIONS_ALL LOC
WHERE POS.LOCATION_ID=LOC.LOCATION_ID
AND POS.EFFECTIVE_END_DATE>NVL(LOC.INACTIVE_DATE,
TO_DATE('31-DEC-4712','DD-MON-YYYY'))
ORDER BY 1,2;
Identifying Positions SELECT POS.POSITION_ID,POS.EFFECTIVE_START_DATE,POS.EFFECTIVE_END_DATE,POS.NAME,
attached to end dated ORG.ORGANIZATION_ID,ORG.DATE_FROM,ORG.DATE_TO,ORG.NAME ORG_NAME
Organizations FROM HR_ALL_POSITIONS_F POS,HR_ALL_ORGANIZATION_UNITS ORG
WHERE POS.ORGANIZATION_ID=ORG.ORGANIZATION_ID
AND POS.EFFECTIVE_END_DATE>ORG.DATE_TO
ORDER BY 1,2;
Identifying Positions SELECT POS.POSITION_ID,POS.EFFECTIVE_START_DATE,POS.EFFECTIVE_END_DATE,POS.NAME,
attached to end dated JOB.JOB_ID,JOB.DATE_FROM,JOB.DATE_TO,JOB.NAME JOB_NAME FROM HR_ALL_POSITIONS_F
Jobs POS,PER_JOBS JOB
WHERE POS.JOB_ID=JOB.JOB_ID
AND POS.EFFECTIVE_END_DATE>JOB.DATE_TO
ORDER BY 1,2;
Identifying Person SELECT PPF.PERSON_ID,PPF.EFFECTIVE_START_DATE,PPF.EFFECTIVE_END_DATE
records with overlapping FROM PER_ALL_PEOPLE_F PPF
records or gaps in WHERE PPF.EFFECTIVE_END_DATE <> HR_GENERAL.END_OF_TIME
AND NOT EXISTS ( SELECT 'N'
Person date track
FROM PER_ALL_PEOPLE_F PPF1
WHERE PPF1.PERSON_ID = PPF.PERSON_ID
AND PPF1.EFFECTIVE_START_DATE = (PPF.EFFECTIVE_END_DATE + 1)) ;
Identifying SELECT PPF.FULL_NAME ,PPF.PERSON_ID
inconsistencies (incorrect ,PPF.EMPLOYEE_NUMBER ,PPF.EFFECTIVE_START_DATE,PPF.EFFECTIVE_END_DATE
start dates) between ,PDS.DATE_START,PDS.ACTUAL_TERMINATION_DATE
FROM PER_PERIODS_OF_SERVICE PDS
Person and periods of
,PER_ALL_PEOPLE_F PPF
service records WHERE PPF.PERSON_ID = PDS.PERSON_ID
AND ((NVL(PDS.ACTUAL_TERMINATION_DATE, HR_GENERAL.END_OF_TIME)
BETWEEN PPF.EFFECTIVE_START_DATE AND PPF.EFFECTIVE_END_DATE
AND NVL(PDS.ACTUAL_TERMINATION_DATE, HR_GENERAL.END_OF_TIME) <
PPF.EFFECTIVE_END_DATE)
OR
(PDS.DATE_START BETWEEN PPF.EFFECTIVE_START_DATE
AND PPF.EFFECTIVE_END_DATE
AND PPF.EFFECTIVE_START_DATE < PDS.DATE_START)) ;
Identifying assignment
records out of synch SELECT PEO.FULL_NAME
,PAF.ASSIGNMENT_NUMBER
, PAF.EFFECTIVE_START_DATE
, PAF.EFFECTIVE_END_DATE ,PAF.ASSIGNMENT_ID
15 | EBS HCM Extraction Toolkit for HCM Cloud Integration Using HCM Data Loader
, PDS.DATE_START,PDS.ACTUAL_TERMINATION_DATE,PDS.PERIOD_OF_SERVICE_ID,
PEO.EFFECTIVE_START_DATE,PEO.EFFECTIVE_END_DATE,PEO.PERSON_ID
FROM PER_ALL_ASSIGNMENTS_F PAF
,PER_PERIODS_OF_SERVICE PDS
,PER_ALL_PEOPLE_F PEO
WHERE PAF.ASSIGNMENT_TYPE = 'E'
AND PEO.PERSON_ID = PAF.PERSON_ID
AND TRUNC(SYSDATE) BETWEEN PEO.EFFECTIVE_START_DATE AND PEO.EFFECTIVE_END_DATE
AND PDS.PERIOD_OF_SERVICE_ID = PAF.PERIOD_OF_SERVICE_ID
AND (((PDS.ACTUAL_TERMINATION_DATE IS NULL
OR PDS.FINAL_PROCESS_DATE IS NULL)
AND PAF.EFFECTIVE_END_DATE <> HR_GENERAL.END_OF_TIME
AND ((PAF.PRIMARY_FLAG = 'Y'
AND NOT EXISTS (SELECT 'N'
FROM PER_ASSIGNMENTS_F PAF2
WHERE PAF2.BUSINESS_GROUP_ID = PAF.BUSINESS_GROUP_ID
AND PAF2.PERSON_ID = PAF.PERSON_ID
AND PAF2.PRIMARY_FLAG = 'Y'
AND PAF2.EFFECTIVE_START_DATE = PAF.EFFECTIVE_END_DATE+1))
OR ( PAF.PRIMARY_FLAG = 'N'
AND NOT EXISTS (SELECT 'N'
FROM PER_ASSIGNMENTS_F PAF2
WHERE PAF2.BUSINESS_GROUP_ID = PAF.BUSINESS_GROUP_ID
AND PAF2.ASSIGNMENT_ID = PAF.ASSIGNMENT_ID
AND PAF2.EFFECTIVE_START_DATE = PAF.EFFECTIVE_END_DATE+1)) ))
OR
( ( (PDS.ACTUAL_TERMINATION_DATE IS NOT NULL
AND PDS.FINAL_PROCESS_DATE IS NULL
AND PAF.EFFECTIVE_END_DATE <> HR_GENERAL.END_OF_TIME )
OR (PDS.FINAL_PROCESS_DATE IS NOT NULL AND PAF.EFFECTIVE_END_DATE <>
PDS.FINAL_PROCESS_DATE))
AND ((PAF.PRIMARY_FLAG = 'Y'
AND NOT EXISTS (SELECT 'N'
FROM PER_ASSIGNMENTS_F PAF2
WHERE PAF2.BUSINESS_GROUP_ID = PAF.BUSINESS_GROUP_ID
AND PAF2.PERSON_ID = PAF.PERSON_ID
AND PAF2.PRIMARY_FLAG = 'Y'
AND PAF2.EFFECTIVE_START_DATE = PAF.EFFECTIVE_END_DATE+1))
OR ( PAF.PRIMARY_FLAG = 'N'
AND NOT EXISTS (SELECT 'N'
FROM PER_ASSIGNMENTS_F PAF2
WHERE PAF2.BUSINESS_GROUP_ID = PAF.BUSINESS_GROUP_ID
AND PAF2.ASSIGNMENT_ID = PAF.ASSIGNMENT_ID
AND PAF2.EFFECTIVE_START_DATE = PAF.EFFECTIVE_END_DATE+1)) ) ) )
ORDER BY ASSIGNMENT_ID ;
Identifying employees
without primary SELECT DISTINCT PEO.FULL_NAME
assignments ,PEO.EMPLOYEE_NUMBER
, PDS.DATE_START
FROM PER_ALL_PEOPLE_F PEO
,PER_ALL_ASSIGNMENTS_F PAF
,PER_PERIODS_OF_SERVICE PDS
WHERE PAF.ASSIGNMENT_TYPE = 'E'
AND PEO.PERSON_ID = PAF.PERSON_ID
AND TRUNC(SYSDATE) BETWEEN PEO.EFFECTIVE_START_DATE AND PEO.EFFECTIVE_END_DATE
AND PDS.PERIOD_OF_SERVICE_ID = PAF.PERIOD_OF_SERVICE_ID
AND NOT EXISTS (SELECT 'N' FROM PER_ASSIGNMENTS_F PAF2
WHERE PAF2.PERSON_ID = PAF.PERSON_ID
AND PAF2.ASSIGNMENT_TYPE = 'E'
AND PAF2.PRIMARY_FLAG = 'Y')
AND SYSDATE BETWEEN PAF.EFFECTIVE_START_DATE
AND PAF.EFFECTIVE_END_DATE
Identifying assignment SELECT PEO.FULL_NAME
records with invalid ,PAF.ASSIGNMENT_NUMBER
Locations , PAF.EFFECTIVE_START_DATE
16 | EBS HCM Extraction Toolkit for HCM Cloud Integration Using HCM Data Loader
Identifying assignment SELECT PEO.FULL_NAME
records with invalid ,PAF.ASSIGNMENT_NUMBER
Organizations , PAF.EFFECTIVE_START_DATE
18 | EBS HCM Extraction Toolkit for HCM Cloud Integration Using HCM Data Loader
BETWEEN GRD.DATE_FROM
AND NVL(GRD.DATE_TO,TO_DATE('31-12-4712','DD-MM-YYYY'))
)
ORDER BY 2,6
20 | EBS HCM Extraction Toolkit for HCM Cloud Integration Using HCM Data Loader
EBS HCM Extraction Toolkit for HCM Cloud Integration Using HCM Data Loader
July 2015 Copyright 2015, Oracle and/or its affiliates. All rights reserved. This document is
Author: Pardhasaradhirao Veluguleti provided for information purposes only and the contents hereof are subject to change
Vinod Viswanathan 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 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
Oracle Corporation not be reproduced or transmitted in any form or by any means, electronic or mechanical,
World Headquarters for any purpose, without our prior written permission.
500 Oracle Parkway
Redwood Shores, CA 94065 Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names
U.S.A. may be trademarks of their respective owners.
Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com
21 | EBS HCM Extraction Toolkit for HCM Cloud Integration Using HCM Data Loader