-
-
-
HDL – Loading Local Person Names
By default, PersonName child object of Worker.dat loads GLOBAL name type. PersonName object can be used to load local name as well. Two most important attributes of PersonName object for local name upload are: Name Type – Legislation Code CharSetContext – Short code for language. Below is a sample HDL file to upload local names…
-
HDL – Load Worker Images
HCM Data Loader can be used to mass upload worker images. The actual image file should be put in a BlobFiles folder and should be referenced in actual Worker.dat file. Post this, Worker.dat will be zipped together with BlobFiles folder and uploaded into HCM using Import and Load.
-
HDL – Script to DELETE positions data
In your test environments, you may encounter issues where you want to DELETE positions data. You can use below script for that:
-
-
HDL – Mask Candidate email addresses
Post P2T, there is always a requirement to mask the candidate email addresses in lower environments. Below SQL can be used to generate data masked email data in HDL format: You can update the email address as per your requirement.
-
HDL – Sample HDL file to upload DoR for a specific country
Please note that under attribute country, you will need to pass the full country name. Passing country code like GB, will throw below error: The values GB aren’t valid for the attribute LegislationCode.
-
HDL – Sample HDL to delete schedule assignment data
Below HDL file can be used to DELETE the schedule assignment data in a Fusion environment: This data can be extracted from Fusion HCM using a simple BIP query:
-
BIP – How to check Termination version on your environment?
You can use per_empl_configurations table to verify the versions of Seniority dates/ Termination dates. Below is an example to check the version for Termination dates: If the version code value is NULL that means you are still on version V2. Same table can be used to query Seniority Dates version.
-
HDL – Assignment Working Hour Pattern
Oracle has provided a new feature where working hours for each day can be stored against assignment working hours. The data is stored in PER_WORKING_HOUR_PATTERNS_F table. Use below query to extract the data: Query to extract data in HDL format:
-
Purge Worker/Person Records from Test Environment
Oracle provides a process Purge Person Data in Test Environments to remove Person/Contact/Worker records from a test environment of Oracle HCM. Please note that HDL for core worker object doesn’t support DELETE, so there is no other option to purge the Person/Contact/Worker information from Oracle HCM once a record is created. In this case, Purge…
-
HDL – Source values for Candidate HDL
When loading Candidate data using HDL, the values of Source attributes (Source and Source Medium) are required. These values are configured in UI using task ‘Manage Candidate Dimension Source Names’. Use below SQL to get the values:
-
HDL – Sample HDL to load HCM Group Members
Oracle provides HCMGroup.dat which can be used to assign members against HCM Group. However, the business object has a major limitation (till release version 22A) that it can be used only for below two seeded Oracle HCM Groups: Manually Maintained Excluded Members Manually Maintained Audit Members Below is the sample HDL file to add members…
-
HDL – Upload Criticality at Position Model Profile
Criticality at position model profile can be loaded using TalentProfile.dat file. Use the below HDL file: ItemText3015 – “Requires Succession Plan” radio box on UI Screen shot from UI of uploaded data: Useful queries: Uploaded data will be stored in HRT_PROFILE_ITEMS. Content Type – select * from HRT_CONTENT_TYPES_TLwhere content_type_id=127 Section ID –
-
HDL – Sample file to upload Talent Pool
Use below sample HDL file to create talent pool and add members to it:
-
HDL – Talent Profile HDL related useful queries
Loading the profile data against a worker/job/position is little tricky one. One has to understand the templates thoroughly before uploading any data. Below are some of the most commonly used queries to extract some of the required information for loading Talent profiles data. Extract Person Profile Code: Extract Profile Type Id:
-
HDL – Sample HDL to load Succession Plans
Sample HDL for succession plan bulk upload:
-
HDL – DELETE Person External Identifier
Person External Identifier information can be deleted easily using HDL. Under Worker use ExternalIdentifier to delete this data. Run the below query to extract required data in HDL format: Sample HDL File:
-
BIP – Query to DELETE Salary data using HDL
There may be a requirement to delete salary data while doing HDL iterations for the first time. You can use below query for the same purpose