EBS Extraction Toolkit For HDL PDF

E-Business Suite HCM Extraction Toolkit for HCM
Cloud Integration Using HCM Data Loader

E-Business Suite Release 11i and Release R12.1.x
An Oracle White Paper

July 2015
Contents
Contents ........................................................................................................................................ 2
Introduction .................................................................................................................................. 3
What is Extraction Toolkit? ............................................................................................................................................. 3
Process Flow ................................................................................................................................................................... 3
Creating Sample Data ................................................................................................................... 4

Steps for Creating Sample Data ....................................................................................................................................... 4
What does the Sample Data contain? ............................................................................................................................... 4
Extracting Data using Toolkit ....................................................................................................... 6

Extraction Toolkit ........................................................................................................................................................... 6
Mapping Data ................................................................................................................................................................. 8
Steps for Running the Extraction Process ........................................................................................................................ 9
Generating DAT Files ................................................................................................................. 11

Steps for Generating DAT Files .................................................................................................................................... 11
Next Steps ................................................................................................................................... 11

Create Zip file to upload to HCM Cloud ....................................................................................................................... 12
Upload to HCM Cloud .................................................................................................................................................. 13
Validation Scripts ........................................................................................................................ 14
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.
What is Extraction Toolkit?
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.
Important: This is a sample extract implementation for partners, consultants or

implementers to be used a reference implementation only. Users must copy this
reference implementation and modify it to meet their business requirements.
Process Flow
The high-level process flow as illustrated in the diagram below includes:
Creating sample data in EBS system.

Performing 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 in a set of staging tables in EBS.
Extracting the data from staging tables into DAT files.
Generating a zip file containing the DAT files and uploading to HCM Cloud using
HCM Data Loader.
Script to create a sample HCM Reference Data Set
Use SQL Developer to generate

DAT files
Import using HCM

EBS HCM Data Loader to Fusion
Extraction Toolkit to transform the data to Fusion

Object shape
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.
Steps for Creating Sample Data
Use this procedure to create sample data.
1. Download EBS_Sample_Data_For_ExtractionToolkit.sql from My Oracle

Support, Note ID 1942763.1
2. Login as apps database user on your EBS Test instance.
3. Execute the script.
What does the Sample Data contain?
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
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
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
Business Object Group Business Objects

Work Structures Location
Grade
Position
Job
Organization
Talent Management Establishment
Rating Model
Content Item
Person Person Details
Person Name
Person National Identifier
Person Email
Person Address
Person Phone
Person Ethnicity
Person Legislative Information
Person Citizenship
Employment Work Relationship
Work Term
Assignment
Assignment Supervisor
Profile Management Profile
Profile Item
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
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_UPDATE_DATE/CREATION_DATE columns can be used to identify the

changes that were performed after the last successful upload to HCM Cloud.
Column Name Type Null? Description

CREATED_BY NUMBER(15) NOT NULL Keeps track of which user created each row
CREATION_ DATE DATE NOT NULL Stores the date on which each row was created
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.
Follow the steps to download the toolkit.
1. Download XX_DL_EXTRACT_TOOLKIT.zip from My Oracle Support, Note

ID 1942763.1.
2. Unzip the file into a folder. The folder will contain a number of package files.
Package Name Package File Name Description

XX_DL_EXTRACTION_KIT_UTIL xx_dl_extraction_kit_util.pkh/pkb Configuration package for the
extraction process.
XX_ DL_EXTRACTION_KIT_TALENT xx_ dl_extraction_kit_talent.pkh/pkb Extracts the talent structures
such as Rating Models ,
Rating Levels ,
Establishments, Content Item
XX_ DL_EXTRACTION_KIT_JOB xx_ dl_extraction_kit_job.pkh/pkb Extracts Jobs and Job Profiles
XX_ DL_EXTRACTION_KIT_GRADE xx_ dl_extraction_kit_grade.pkh/pkb Extracts Grades
XX_ DL_EXTRACTION_KIT_POSITION xx_ dl_extraction_kit_position.pkh/pkb Extracts Positions and Position
Profiles
XX_ DL_EXTRACTION_KIT_LOCATION xx_ dl_extraction_kit_location.pkh/pkb Extracts Locations
XX_ DL_EXTRACTION_KIT_ORG xx_ dl_extraction_kit_organization.pkh/pkb Extracts Organization and
Organization Profiles
XX_ DL_EXTRACTION_KIT_PERSON xx_ dl_extraction_kit_person.pkh/pkb Extracts Person and Person
Profiles
XX_ DL_EXTRACTION_KIT_WORKER xx_ dl_extraction_kit_worker.pkh/pkb Extracts Worker related entities
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
The Extraction Toolkit contains a package XX_DL_EXTRACT_KIT_UTIL that

contains the necessary code that transforms the EBS HR objects to their equivalent
HCM Cloud formats. The package contains global variables that can be used to map
the reference information such as LEGAL EMPLOYER_NAME,
BUSINESS_UNIT_NAME, etc.
You must modify this package to map the reference data to the global variable values.
For example, the g_legal_employer_name package variable stores the LEGAL

EMPLOYER_NAME. The value stored in this variable is used as a
legal_employer_name throughout the extraction process.
The following table displays the details of the package variables to be modified and the
description of that variable:
Package Variable Name Description Default Value

g_legal_employer_name Provide LEGAL EMPLOYER NAME here Moon Corporation
g_set_code Provide the SET CODE here COMMON
g_business_name Provide the BUSINESS UNIT NAME here Moon Corporation BU
g_legislation_code Provide the LEGISLATION CODE here US
Talent Management Types
g_memb_cnt_typ Provide the MEMBERSHIP content type here MEMBERSHIP
g_ed_lvl_cnt_type Provide the EDUCATION_LEVEL content EDUCATION_LEVEL
type here
g_lang_cnt_typ Provide the LANGUAGE content type here LANGUAGE
g_deg_cnt_typ Provide the DEGREE content type here DEGREE
g_hon_cnt_typ Provide the HONORS content type here DEGREE
g_cert_cnt_typ Provide the CERTIFICATION content type CERTIFICATION
here
g_perf_rat_cnt_typ Provide the PERFORMANCE RATING PERFORMANCE_RATING
content type here
g_cmp_cnt_typ Provide the COMPETENCE content type here COMPETENCY
g_goal_cnt_typ Provide the GOAL content here GOAL
Person Types
g_qualifier Provide the Performance Rating QUALIFIER PR
CODE here
g_comp_qualifier Provide the Competency QUALIFIER CODE R
here
g_comp_qualifier_set_code Provide the Competency QUALIFIER SET EVAL_TYPE
CODE here
g_per_type_emp Provide the EMP person type here Employee
g_per_type_cwk Provide the CWK person type here Contingent Worker
Assignment Status Types
g_astat_active_np Provide the ACTIVE NO PAY type here ACTIVE_NO_PROCESS
g_astat_active_p Provide the ACTIVE PAY type here ACTIVE_PROCESS
g_astat_inactive_np Provide the INACTIVE NO PAY type here INACTIVE_NO_PROCESS
g_astat_inactive_p Provide the INACTIVE PAY type here INACTIVE_PROCESS
g_astat_suspend_np Provide the SUSPEND NO PAY type here SUSPEND_NO_PROCESS
g_astat_suspend_p Provide the SUSPEND PAY type here SUSPEND_PROCESS
Profile Types
g_per_prof_typ Provide the PERSON profile type here PERSON
g_org_prof_typ Provide the ORGANIZATION profile type ORGANIZATION
here
g_job_prof_typ Provide the JOB profile type here JOB
g_pos_prof_typ Provide the POSITION profile type here POSITION
Profile Relation Types
g_pos_prof_reln Provide the POSITION profile relation type POSITION
here
g_org_prof_reln Provide the ORGANIZATION profile relation ORGANIZATION
type here
g_job_prof_reln Provide the JOB profile relation type here JOB
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.
Steps for Running the Extraction Process
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.
Creating Staging Tables

Running the Extraction Process
Creating Staging Tables
1. Download Create_Staging_Tables.sql from My Oracle Support Note ID

1942763.1
3. Execute the script.
Note: All staging tables are created with a prefix XX_DL_EXTRACT, for
example XX_DL_EXTRACT_LOCATIONS.
Running the Extraction Process
After you perform the mapping and creating the staging tables, you can run
the extraction process.
2. Create the packages shown in Extraction Toolkit, by executing the scripts
contained in XX_DL_EXTRACT_TOOLKIT.zip
Package Name Package File Name Description

XX_DL_EXTRACTION_KIT_UTIL xx_dl_extraction_kit_util.pkh/pkb Configuration package
for the extraction
process.
XX_ xx_ dl_extraction_kit_location.pkh/pkb Extracts Locations
DL_EXTRACTION_KIT_LOCATION
XX_ DL_EXTRACTION_KIT_GRADE xx_ dl_extraction_kit_grade.pkh/pkb Extracts Grades
XX_ DL_EXTRACTION_KIT_ORG xx_ dl_extraction_kit_organization.pkh/pkb Extracts Organization
and Organization
Profiles
XX_ DL_EXTRACTION_KIT_JOB xx_ dl_extraction_kit_job.pkh/pkb Extracts Jobs and Job
Profiles
XX_ xx_ dl_extraction_kit_position.pkh/pkb Extracts Positions and
DL_EXTRACTION_KIT_POSITION Position Profiles
XX_ DL_EXTRACTION_KIT_PERSON xx_ dl_extraction_kit_person.pkh/pkb Extracts Person and
Person Profiles
XX_ xx_ dl_extraction_kit_worker.pkh/pkb Extracts Worker
DL_EXTRACTION_KIT_WORKER related entities
XX_ DL_EXTRACTION_KIT_TALENT xx_ dl_extraction_kit_talent.pkh/pkb Extracts the talent
structures such as
Rating Models ,
Rating Levels ,
Establishments,
Content Item
3. Execute the procedure xx_dl_extract_kit_util.run_extract with the

appropriate business group parameter.
SQL> EXEC xx_dl_extract_kit_util.run_extract (<provide Business Group
name for which the data need to be extracted>);
For example, the statement given below extracts the data associated with
Moon Corporation and loads them into the staging tables.
exec xx_dl_extraction_kit_util.run_extract('Moon Corporation');
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:
SQL> SPOOL script_output.log;

SQL> EXEC xx_dl_extract_kit_util.run_extract (<provide Business Group
name>);
SQL> SPOOL OFF;
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.
Steps for Generating DAT Files
Use this procedure to generate DAT files.
1. Download DAT_File_Generation_Queries.zip from MOS Note ID

1942763.1.
2. Unzip the file into a folder. The folder will contain a number of SQL files.
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
3. Login to apps database user using SQLDeveloper or any equivalent tool

that can save the query results as a text file.
4. Copy the query from the corresponding .sql file (table above), for the
Business Object for which you want to generate the DAT file.
5. Execute the query and then Copy and paste the query result in to a
notepad or text editor.
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.
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
Upload to HCM Cloud
Refer to Oracle HCM Data Loader : Supported Business Object Templates -

My Oracle Support Note ID 1641619.2.
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.
For additional information, refer to the following links:

Oracle HCM Data Loader: Loading Talent Data My Oracle Support Note
2022627.1
Oracle HCM Data Loader: Loading Workers 2022624.1
Oracle HCM Data Loader: Loading Work Structures 2021212.1
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.
Query Description Query

Identify HR SELECT HR_ORG.ORGANIZATION_ID
Organizations attached , HR_ORG.BUSINESS_GROUP_ID
to inactive locations , HR_ORG.NAME
, HR_ORG.DATE_FROM
, HR_ORG.DATE_TO
, LOC.LOCATION_ID
, LOC.INACTIVE_DATE
FROM HR_ALL_ORGANIZATION_UNITS HR_ORG
, HR_LOCATIONS_ALL LOC
WHERE HR_ORG.LOCATION_ID= LOC.LOCATION_ID
AND NVL(HR_ORG.DATE_TO,TO_DATE('31-DEC-4712','DD-MON-YYYY'))>
NVL(LOC.INACTIVE_DATE,TO_DATE('31-DEC-4712','DD-MON-YYYY'))
ORDER BY 2,1
Identify Valid grades of SELECT GRD.GRADE_ID,GRD.NAME,GRD.DATE_FROM GRD_DATE_FROM ,
Jobs that start earlier JOB.NAME,JOB.DATE_FROM JOB_DATE_FROM,JOB.JOB_ID,
than the Grade V_GRD.VALID_GRADE_ID,V_GRD.DATE_FROM V_GRD_DATE_FROM,V_GRD.GRADE_ID,V_GRD.JOB_ID
FROM PER_GRADES GRD,
PER_VALID_GRADES V_GRD
,PER_JOBS JOB
WHERE JOB.JOB_ID=V_GRD.JOB_ID
AND GRD.GRADE_ID=V_GRD.GRADE_ID
AND V_GRD.DATE_FROM <GRD.DATE_FROM
ORDER BY JOB.JOB_ID,VALID_GRADE_ID
Identify Valid grades of SELECT GRD.GRADE_ID,GRD.NAME,GRD.DATE_FROM GRD_DATE_FROM ,

Positions that start V_GRD.VALID_GRADE_ID,V_GRD.DATE_FROM
earlier than the Grade V_GRD_DATE_FROM,V_GRD.GRADE_ID,V_GRD.POSITION_ID
FROM PER_GRADES GRD,
PER_VALID_GRADES V_GRD
WHERE GRD.GRADE_ID=V_GRD.GRADE_ID
AND V_GRD.POSITION_ID IS NOT NULL
AND V_GRD.DATE_FROM <GRD.DATE_FROM
ORDER BY VALID_GRADE_ID
Person Address start SELECT ADR.ADDRESS_ID,ADR.DATE_FROM
date should be later than ,PPF.EFFECTIVE_START_DATE,PPF.FULL_NAME,PPF.PERSON_ID,PPF.ORIGINAL_DATE_OF_HIRE
the hire date of the FROM PER_ADDRESSES ADR, PER_ALL_PEOPLE_F PPF
WHERE ADR.PRIMARY_FLAG='Y'
Person.
AND DATE_FROM > (SELECT MIN(EFFECTIVE_START_DATE) FROM PER_ALL_PEOPLE_F WHERE
PERSON_ID=ADR.PERSON_ID AND CURRENT_EMPLOYEE_FLAG='Y')
AND EFFECTIVE_START_DATE=(SELECT MIN(EFFECTIVE_START_DATE) FROM PER_ALL_PEOPLE_F
WHERE PERSON_ID=ADR.PERSON_ID AND CURRENT_EMPLOYEE_FLAG='Y')
AND ADR.PERSON_ID=PPF.PERSON_ID;
Identify Assignment
records referencing an SELECT ASSGN.ASSIGNMENT_ID,ASSGN.EFFECTIVE_START_DATE,ASSGN.EFFECTIVE_END_DATE,
end dated Grade GRD.GRADE_ID,GRD.DATE_FROM,GRD.DATE_TO
FROM PER_ALL_ASSIGNMENTS_F ASSGN, PER_GRADES GRD WHERE
ASSGN.GRADE_ID=GRD.GRADE_ID AND
ASSGN.EFFECTIVE_START_DATE>=GRD.DATE_FROM
AND ASSGN.EFFECTIVE_END_DATE>
NVL(DATE_TO,TO_DATE('31-DEC-4712','DD-MON-YYYY'))
Identify the Assignment SELECT ASSGN.ASSIGNMENT_ID,ASSGN.EFFECTIVE_START_DATE,ASSGN.EFFECTIVE_END_DATE,
records referencing an JOB.JOB_ID,JOB.DATE_FROM,JOB.DATE_TO
end dated Job FROM PER_ALL_ASSIGNMENTS_F ASSGN, PER_JOBS JOB WHERE
ASSGN.JOB_ID=JOB.JOB_ID AND
ASSGN.EFFECTIVE_START_DATE>=JOB.DATE_FROM
NVL(DATE_TO,TO_DATE('31-DEC-4712','DD-MON-YYYY'))
Identify the assignment

records referencing an SELECT ASSGN.ASSIGNMENT_ID,ASSGN.EFFECTIVE_START_DATE,ASSGN.EFFECTIVE_END_DATE,
end dated HR ORG.ORGANIZATION_ID,ORG.DATE_FROM,ORG.DATE_TO
FROM PER_ALL_ASSIGNMENTS_F ASSGN,HR_ALL_ORGANIZATION_UNITS ORG WHERE
Organization
ASSGN.ORGANIZATION_ID=ORG.ORGANIZATION_ID AND
ASSGN.EFFECTIVE_START_DATE>=ORG.DATE_FROM
NVL(DATE_TO,TO_DATE('31-DEC-4712','DD-MON-YYYY'));
Identify assignments SELECT ASSIGN.ASSIGNMENT_ID,ASSIGN.EFFECTIVE_START_DATE,
with terminated ASSIGN.EFFECTIVE_END_DATE,ASSIGN.SUPERVISOR_ID,
supervisors PPF.EFFECTIVE_START_DATE,PPF.EFFECTIVE_END_DATE,PPF.CURRENT_EMPLOYEE_FLAG
FROM PER_ALL_ASSIGNMENTS_F ASSIGN, PER_ALL_PEOPLE_F PPF
WHERE SUPERVISOR_ID IS NOT NULL AND PPF.PERSON_ID=ASSIGN.SUPERVISOR_ID
AND CURRENT_EMPLOYEE_FLAG IS NULL
AND (ASSIGN.EFFECTIVE_END_DATE BETWEEN PPF.EFFECTIVE_START_DATE AND
PPF.EFFECTIVE_END_DATE
OR ASSIGN.EFFECTIVE_START_DATE BETWEEN PPF.EFFECTIVE_START_DATE AND
PPF.EFFECTIVE_END_DATE )
ORDER BY 1,2
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;
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;
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
, 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 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 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 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
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

,HR_LOCATIONS_ALL LOC
AND PAF.LOCATION_ID IS NOT NULL
AND PAF.LOCATION_ID = LOC.LOCATION_ID(+)
AND LOC.LOCATION_ID IS NULL
Identifying assignment SELECT PEO.FULL_NAME
records with invalid ,PAF.ASSIGNMENT_NUMBER
Organizations , PAF.EFFECTIVE_START_DATE

,HR_ALL_ORGANIZATION_UNITS HOU
AND PAF.ORGANIZATION_ID IS NOT NULL
AND PAF.ORGANIZATION_ID = HOU.ORGANIZATION_ID(+)
AND HOU.ORGANIZATION_ID IS NULL
Phone records should SELECT DISTINCT PPF.PERSON_ID,PHN.PHONE_ID,DATE_FROM PHONE_DATE_START,START_DATE
start date should be later PERSON_START_DATE
than the person start FROM PER_ALL_PEOPLE_F PPF,PER_PHONES PHN
WHERE PPF.PERSON_ID=PHN.PARENT_ID
date (hire date).
AND PHN.PARENT_TABLE='PER_ALL_PEOPLE_F'
AND DATE_FROM<START_DATE ORDER BY PERSON_ID;
Identifying Competence SELECT PPF.PERSON_ID,ELE.EFFECTIVE_DATE_FROM,
element records COMP.DATE_FROM COMP_DATE_FROM ,COMP.COMPETENCE_ID ,ELE.COMPETENCE_ELEMENT_ID
(assigned to Person ) FROM
PER_COMPETENCE_ELEMENTS ELE,PER_COMPETENCES COMP,PER_ALL_PEOPLE_F PPF
started prior to
WHERE ELE.PERSON_ID IS NOT NULL
competence record AND PPF.PERSON_ID=ELE.PERSON_ID
AND COMP.COMPETENCE_ID=ELE.COMPETENCE_ID
AND ELE.EFFECTIVE_DATE_FROM<DATE_FROM
Identify position records SELECT POS.POSITION_ID,POS.EFFECTIVE_START_DATE,POS.EFFECTIVE_END_DATE
that have gaps in date FROM HR_ALL_POSITIONS_F POS
track. WHERE POS.EFFECTIVE_END_DATE <> HR_GENERAL.END_OF_TIME
AND NOT EXISTS ( SELECT 'N'
FROM HR_ALL_POSITIONS_F POS1
WHERE POS1.POSITION_ID = POS.POSITION_ID
AND POS1.EFFECTIVE_START_DATE = (POS.EFFECTIVE_END_DATE + 1))
Identify if there exist a SELECT JOB.NAME JOB_NAME
non-unique combination ,GRD.NAME GRADE_NAME
of job-grade in valid ,VALID_GRADE1.VALID_GRADE_ID VALID_GRADE1
,VALID_GRADE2.VALID_GRADE_ID VALID_GRADE2
grades.
,VALID_GRADE1.DATE_FROM VALID_GRADE1_DATE_FROM
,NVL(VALID_GRADE1.DATE_TO,TO_DATE('31-12-4712','DD-MM-YYYY')) VALID_GRADE1_DATE_TO
FROM PER_VALID_GRADES VALID_GRADE1
,PER_VALID_GRADES VALID_GRADE2
,PER_JOBS JOB
,PER_GRADES GRD
WHERE VALID_GRADE1.VALID_GRADE_ID<> VALID_GRADE2.VALID_GRADE_ID
AND VALID_GRADE1.JOB_ID = VALID_GRADE2.JOB_ID
AND VALID_GRADE1.GRADE_ID = VALID_GRADE2.GRADE_ID
AND VALID_GRADE1.JOB_ID = JOB.JOB_ID
AND VALID_GRADE1.GRADE_ID = GRD.GRADE_ID
AND
(
(VALID_GRADE1.DATE_FROM
BETWEEN VALID_GRADE2.DATE_FROM
AND NVL(VALID_GRADE2.DATE_TO,TO_DATE('31-12-4712','DD-MM-YYYY'))
)
OR
)
)
ORDER BY 1,2
Identify if there exists a SELECT POS.NAME POSITION_NAME
non-unique combination ,GRD.NAME GRADE_NAME
of position-grade in valid ,VALID_GRADE1.VALID_GRADE_ID VALID_GRADE1
,VALID_GRADE2.VALID_GRADE_ID VALID_GRADE2
grades
FROM PER_VALID_GRADES VALID_GRADE1
,PER_VALID_GRADES VALID_GRADE2
,HR_ALL_POSITIONS_F POS
,PER_GRADES GRD
WHERE VALID_GRADE1.VALID_GRADE_ID <> VALID_GRADE2.VALID_GRADE_ID
AND VALID_GRADE1.JOB_ID = VALID_GRADE2.JOB_ID
AND VALID_GRADE1.GRADE_ID = VALID_GRADE2.GRADE_ID
AND VALID_GRADE1.POSITION_ID = POS.POSITION_ID
AND VALID_GRADE1.GRADE_ID = GRD.GRADE_ID
AND POS.EFFECTIVE_START_DATE = (SELECT MIN(EFFECTIVE_START_DATE) FROM
HR_ALL_POSITIONS_F WHERE POSITION_ID = VALID_GRADE1.POSITION_ID)
AND
(
)
OR
)
)
ORDER BY 1,2
Identify if Ship to SELECT LOCATION_ID
Location has a non null ,LOCATION_CODE
value if the Ship to Site FROM HR_LOCATIONS_ALL
WHERE SHIP_TO_SITE_FLAG = 'Y'
flag is set
AND SHIP_TO_LOCATION_ID <> LOCATION_ID ORDER BY 1
Positions having SELECT POSITION_ID, NAME
working hours but not FROM HR_ALL_POSITIONS_F
having a valid frequency WHERE ((FREQUENCY IS NULL AND WORKING_HOURS IS NOT NULL) OR
(WORKING_HOURS IS NULL AND FREQUENCY IS NOT NULL))
ORDER BY 1
Identify if Grade SELECT POS.NAME POSITION_NAME
associated with Position ,POS.ENTRY_GRADE_ID
is active ,GRD.NAME GRADE_NAME
,POS.EFFECTIVE_START_DATE POS_ESD
,POS.EFFECTIVE_END_DATE POS_EED
,GRD.DATE_FROM GRD_DATE_FROM
,NVL(GRD.DATE_TO,TO_DATE('31-12-4712','DD-MM-YYYY')) GRD_DATE_TO
FROM HR_ALL_POSITIONS_F POS
,PER_GRADES GRD
WHERE POS.ENTRY_GRADE_ID = GRD.GRADE_ID
AND
(
(NOT
(POS.EFFECTIVE_START_DATE
BETWEEN GRD.DATE_FROM
AND NVL(GRD.DATE_TO,TO_DATE('31-12-4712','DD-MM-YYYY'))
)
)
OR
(NOT
(POS.EFFECTIVE_END_DATE
)
)
)
ORDER BY 1,4
Identify whether Grade SELECT
Rate does not refer to a (
Grade that is end dated SELECT NAME
FROM PAY_RATES
WHERE RATE_ID = RATE_VALUES.RATE_ID
) GRADE_RATE
,RATE_VALUES.RATE_ID
,RATE_VALUES.GRADE_RULE_ID
,RATE_VALUES.EFFECTIVE_START_DATE
,RATE_VALUES.EFFECTIVE_END_DATE
,GRD.GRADE_ID
,GRD.NAME GRADE_NAME
,GRD.DATE_FROM GRADE_DATE_FROM
,NVL(GRD.DATE_TO,TO_DATE('31-12-4712','DD-MM-YYYY')) GRADE_DATE_TO
FROM PAY_GRADE_RULES_F RATE_VALUES
,PER_GRADES GRD
WHERE RATE_VALUES.RATE_TYPE = 'G'
AND GRD.GRADE_ID = RATE_VALUES.GRADE_OR_SPINAL_POINT_ID
AND NOT
(RATE_VALUES.EFFECTIVE_START_DATE
)
ORDER BY 2,6
Identifying Competence SELECT JOB.JOB_ID,ELE.EFFECTIVE_DATE_FROM,

Element records COMP.DATE_FROM COMP_DATE_FROM ,COMP.COMPETENCE_ID ,ELE.COMPETENCE_ELEMENT_ID
(assigned to job ) started FROM
PER_COMPETENCE_ELEMENTS ELE,PER_COMPETENCES COMP,PER_JOBS JOB
prior to Competence
WHERE ELE.JOB_ID IS NOT NULL
record AND JOB.JOB_ID=ELE.JOB_ID
AND COMP.COMPETENCE_ID=ELE.COMPETENCE_ID
AND ELE.EFFECTIVE_DATE_FROM < COMP.DATE_FROM
Identify competence SELECT JOB.JOB_ID
element records ,JOB.NAME
(assigned to job) for the ,COMP_ELE.COMPETENCE_ID
,
job which is inactive
(
SELECT NAME
FROM PER_COMPETENCES
WHERE COMPETENCE_ID = COMP_ELE.COMPETENCE_ID
) COMPETENCE_NAME ,
COMP_ELE.EFFECTIVE_DATE_FROM ELE_DATE_FROM
,NVL(COMP_ELE.EFFECTIVE_DATE_TO,TO_DATE('31-12-4712','DD-MM-YYYY')) ELE_DATE_TO
,JOB.DATE_FROM JOB_DATE_FROM
,NVL(JOB.DATE_TO,TO_DATE('31-12-4712','DD-MM-YYYY')) JOB_DATE_TO
FROM PER_COMPETENCE_ELEMENTS COMP_ELE
,PER_JOBS JOB
WHERE COMP_ELE.JOB_ID = JOB.JOB_ID
AND COMP_ELE.JOB_ID IS NOT NULL
AND
(
(NOT
(COMP_ELE.EFFECTIVE_DATE_FROM
BETWEEN JOB.DATE_FROM
AND NVL(JOB.DATE_TO,TO_DATE('31-12-4712','DD-MM-YYYY'))
)
)
OR
(NOT
(NVL(COMP_ELE.EFFECTIVE_DATE_TO,TO_DATE('31-12-4712','DD-MM-YYYY'))
BETWEEN JOB.DATE_FROM
AND NVL(JOB.DATE_TO,TO_DATE('31-12-4712','DD-MM-YYYY'))
)
)
)
ORDER BY 1,3,5
Identifying Competence SELECT POS.POSITION_ID
Element records ,POS.NAME
(assigned to position ) ,ELE.EFFECTIVE_DATE_FROM
,COMP.DATE_FROM COMP_DATE_FROM
started prior to
,COMP.COMPETENCE_ID
Competence record ,ELE.COMPETENCE_ELEMENT_ID
FROM PER_COMPETENCE_ELEMENTS ELE
,PER_COMPETENCES COMP
,HR_ALL_POSITIONS_F POS
WHERE ELE.POSITION_ID IS NOT NULL
AND POS.POSITION_ID = ELE.POSITION_ID
AND COMP.COMPETENCE_ID = ELE.COMPETENCE_ID
AND POS.EFFECTIVE_START_DATE =
(
SELECT MIN(EFFECTIVE_START_DATE)
FROM HR_ALL_POSITIONS_F POS1
WHERE POS1.POSITION_ID = POS.POSITION_ID
)
ORDER BY 1,5
Identifying Competence SELECT ORG.ORGANIZATION_ID
Element records ,ELE.EFFECTIVE_DATE_FROM
(assigned to org ) started ,COMP.DATE_FROM COMP_DATE_FROM
,COMP.COMPETENCE_ID
prior to Competence
,ELE.COMPETENCE_ELEMENT_ID
record FROM PER_COMPETENCE_ELEMENTS ELE
,PER_COMPETENCES COMP
,HR_ALL_ORGANIZATION_UNITS ORG
WHERE ELE.ORGANIZATION_ID IS NOT NULL
AND ORG.ORGANIZATION_ID = ELE.ORGANIZATION_ID
AND COMP.COMPETENCE_ID = ELE.COMPETENCE_ID
Identify Competence SELECT ORG.ORGANIZATION_ID

Element records ,ORG.NAME
(assigned to org) for the ,COMP_ELE.COMPETENCE_ID
, ( SELECT NAME
Organization which is
FROM PER_COMPETENCES
inactive WHERE COMPETENCE_ID = COMP_ELE.COMPETENCE_ID
) COMPETENCE_NAME
,COMP_ELE.EFFECTIVE_DATE_FROM ELE_DATE_FROM
,NVL(COMP_ELE.EFFECTIVE_DATE_TO,TO_DATE('31-12-4712','DD-MM-YYYY')) ELE_DATE_TO
,ORG.DATE_FROM ORGANIZATION_DATE_FROM
,NVL(ORG.DATE_TO,TO_DATE('31-12-4712','DD-MM-YYYY')) ORGANIZATION_DATE_TO
FROM PER_COMPETENCE_ELEMENTS COMP_ELE
,HR_ALL_ORGANIZATION_UNITS ORG
WHERE COMP_ELE.ORGANIZATION_ID = ORG.ORGANIZATION_ID
AND COMP_ELE.ORGANIZATION_ID IS NOT NULL
AND ( (NOT (COMP_ELE.EFFECTIVE_DATE_FROM
BETWEEN ORG.DATE_FROM
AND NVL(ORG.DATE_TO,TO_DATE('31-12-4712','DD-MM-YYYY')) ) )
OR (NOT
(NVL(COMP_ELE.EFFECTIVE_DATE_TO,TO_DATE('31-12-4712','DD-MM-YYYY'))
BETWEEN ORG.DATE_FROM
AND NVL(ORG.DATE_TO,TO_DATE('31-12-4712','DD-MM-YYYY')) )
)
) ORDER BY 1,3,5
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

EBS Extraction Toolkit For HDL PDF

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

EBS Extraction Toolkit For HDL PDF

Enviado por

Direitos autorais:

Formatos disponíveis

E-Business Suite HCM Extraction Toolkit for HCM

Cloud Integration Using HCM Data Loader

An Oracle White Paper

Creating Sample Data ................................................................................................................... 4

Extracting Data using Toolkit ....................................................................................................... 6

Generating DAT Files ................................................................................................................. 11

Next Steps ................................................................................................................................... 11

Validation Scripts ........................................................................................................................ 14

What is Extraction Toolkit?

Important: This is a sample extract implementation for partners, consultants or

The high-level process flow as illustrated in the diagram below includes:

Creating sample data in EBS system.

Script to create a sample HCM Reference Data Set

Use SQL Developer to generate

Import using HCM

Extraction Toolkit to transform the data to Fusion

Steps for Creating Sample Data

Use this procedure to create sample data.

1. Download EBS_Sample_Data_For_ExtractionToolkit.sql from My Oracle

What does the Sample Data contain?

Business Object Group Business Objects

LAST_UPDATE_DATE/CREATION_DATE columns can be used to identify the

Column Name Type Null? Description

Follow the steps to download the toolkit.

1. Download XX_DL_EXTRACT_TOOLKIT.zip from My Oracle Support, Note

Package Name Package File Name Description

The Extraction Toolkit contains a package XX_DL_EXTRACT_KIT_UTIL that

For example, the g_legal_employer_name package variable stores the LEGAL

Package Variable Name Description Default Value

Steps for Running the Extraction Process

Creating Staging Tables

Creating Staging Tables

1. Download Create_Staging_Tables.sql from My Oracle Support Note ID

Running the Extraction Process

Package Name Package File Name Description

3. Execute the procedure xx_dl_extract_kit_util.run_extract with the

exec xx_dl_extraction_kit_util.run_extract('Moon Corporation');

SQL> SPOOL script_output.log;

Steps for Generating DAT Files

Use this procedure to generate DAT files.

1. Download DAT_File_Generation_Queries.zip from MOS Note ID

3. Login to apps database user using SQLDeveloper or any equivalent tool

Refer to Oracle HCM Data Loader : Supported Business Object Templates -

For additional information, refer to the following links:

Query Description Query

Identify Valid grades of SELECT GRD.GRADE_ID,GRD.NAME,GRD.DATE_FROM GRD_DATE_FROM ,

Identify the assignment

FROM PER_ALL_ASSIGNMENTS_F PAF

FROM PER_ALL_ASSIGNMENTS_F PAF

Identifying Competence SELECT JOB.JOB_ID,ELE.EFFECTIVE_DATE_FROM,

Identify Competence SELECT ORG.ORGANIZATION_ID

Você também pode gostar