Introduction

Oracle HCM Cloud business objects can be complex and are usually hierarchical, allowing for multiple child records to exist for a business object. Each object within a business object hierarchy supplies multiple attributes, some of which are references to other objects, some are lookup validated, most are optional, while some are required for new records and others are always required.

The View Business Objects task describes the hierarchical shape and provides attribute information for every business object supported for bulk-data loading by HCM Data Loader and HCM Spreadsheet Data Loader.

Tip:

This tutorial assumes you've enabled Redwood. Access the Release 25C version of this tutorial for the navigation and screenshots if this isn't the case.

Objectives

In this tutorial, you will:

• Review available objects, their hierarchical shape, the actions they allow and the attributes they provide.
• Generate METADATA template files.
• Download business object overview spreadsheets.

Prerequisites

To complete this tutorial, you will need:

• Access to the View Business Objects task.
• To download business object spreadsheets, you'll need a Windows machine with the Desktop integration installed.

Task 1: Review Supported Objects

In this step you'll explore the View Business Objects page and use the search capabilities to filter the list of business objects.

Tip:

Product areas group related business objects.

View Business Objects

1. Log into the application and navigate to My Client Groups > Data Exchange > View Business Objects.



The View Business Objects table displays all business objects supported by HCM Data Loader (HDL) and HCM Spreadsheet Data Loader (HSDL).

• The Business Object column displays the name of the business object is your session language. Clicking it displays the object hierarchy.
• The File Name column displays the file name to use when loading data for that business object with HDL.
• The Load Order indicates the order in which you should load business object data.

  Tip:

  You can include multiple business object data files in a single .zip file and HDL will load them in the correct order but if you're loading objects individually, follow the load order to ensure the data that can be referenced by other objects is loaded first.
• HSDL Support indicates if spreadsheets can be used to bulk-load data for the business object and whether this can be performed by the session user or only an elevated (super) user.
• Roll Back Supported indicates if the business object supports loaded data being rolled back.
• Secured by Privilege indicates if the object loads security related data.

  Tip:

  By default, access to security-related objects isn't restricted. However, once enabled, roles that need to load data with these objects require an additional function security privilege. Review the Configure Access to HCM Data Loader and Understand HDL Security Options tutorial for more information.
• Automated Postprocessing indicates if the business object has post processes that are submitted automatically after HDL or HSDL has successfully loaded data for the object.
• Oracle Search Bulk Ingestion Enabled indicates if the business object will bulk update Oracle Search indexes after data is loaded successfully.

Tip:

Use the column management feature to select which columns to display and the order in which to display them.

Filtering Business Objects

There are a number of filters provided by the View Business Objects page.

1. Try each of these in turn:
   • The Product Area filter supplies a list of the product areas used to group related business objects. Select a product area to restrict the list of business objects.

     

     Tip:

     Some business objects have similar names, the product area can help confirm you are looking at the right one.
   • The HSDL Support filter allows you to see the business objects which support business users to load data, and which only allow elevated (super) users.

     

     
     
   • Toggle the Roll Back Supported filter to show only those objects that allow uploaded data to be rolled back.

     

     
     
   • If role-based access to HDL objects is enabled, the Roles Assigned filter can show you which objects have or haven't been assigned to any roles.

     

     Note:

     By default, role-based security isn't enabled.

     Review the Configure Access to HCM Data Loader and Understand HDL Security Options tutorial for more information.

   • Toggle the Secured by Privilege filter to list those objects that roles require the Load HCM Security Data privilege to load data for an object.

     

     Note:

     By default, access to security related objects isn't restricted. Review the Configure Access to HCM Data Loader and Understand HDL Security Options tutorial for more information.

2. Use the search bar to search for business objects that contain the string job.



You can see that there are multiple objects with that include 'job', the Business Object, Description and Product Area will help identify which of these is for loading jobs.

Tip:

The search isn't case-sensitive and will return all objects with the specified string in the business object name or file name.

Task 2: Updating Attributes

View Business Objects displays the attributes available on each business object.

If you've recently configured flexfield attributes, or if the Last Updated On date for your business object is out of date, it's recommended that you update the object's attribute information. Updating the object's attributes also generates the template file and overview spreadsheet for an object. The following tasks in this tutorial will explain what these are and how to access them.

In this step, you will update attributes for an individual business object, then for all business objects in a specific product area.

Update Attributes for a Business Object

1. Click the Actions button for the Job business object and select the Update Attributes action.





2. Click Submit on the Update Business Object Attributes panel.



You'll see a toast message confirming submission.

3. Click Refresh until the Last Updated On is today's date.

Refresh Multiple Objects

To refresh the attributes for all business objects within a specific product area:

1. Click Manage Attribute Updates > Update by Product Area





2. Use the list of values to select the Global HR - Work Structures product area.



Tip:

Select All to refresh all supported business objects but this can take several minutes with around 360 object hierarchies to refresh.
3. Click Submit.
4. Click Manage Attribute Updates > View Update Processes.





5. Find the entry for the Global HR - Work Structures product area.





6. Click Refresh until the process has completed.

The Status indicates when the process is complete, but you can also use the Last Updated On column in the View Business Objects table to see when the business object's attributes were last updated.

Task 3: Understanding the Business Object Hierarchy

Before you can successfully load data, you need to understand the business object's hierarchical shape and identify which objects in the business object hierarchy you want to load data for.

In this step, you'll learn how to review a business object's hierarchy and how to find the details of all objects in the hierarchy.

1. Use the View Business Objects page to search for the Job business object.
2. Click on the Job business object name to navigate to the Business Object Hierarchy page.





3. Review the objects in the Job business object hierarchy and the parent-child relationships.



The job object hierarchy is a simple two-level hierarchy. Some business objects, such as Worker, have many more objects across multiple levels.

Tip:

When you supply data for a child-level object you must reference the parent it's for, so it's important to understand the hierarchical shape of a business object.
4. Click the icon in the Actions column for the Job object to review the object-level details.

   

   On the object details panel, you'll find the following information:

   • The File Discriminator specifies the string to include on METADATA, MERGE, and DELETE lines in HDL files. It identifies the object in the hierarchy the file line is for.
   • Use the Description to confirm you have the correct object. Descriptions often provide guidance on how to load data for the object too.
   • Supported Actions tell you what actions you can perform. Not all objects support data being deleted.
   • Required for New Records indicates if you must supply data for this object when creating a new record.
   • The Integration Object Name is useful when you're using integration keys to identify your records. You'll need to know this when extracting integration key values.
   • In addition to the hierarchical representation of the business object the Parent Object shows the translated name of the parent. This is not seen for the top-level object in the hierarchy.
   • If the object supports attribute values being translated the Translation Object will name the business object used to load translations.
   • HSDL Support indicates which users can bulk-load data for this object using HCM Spreadsheet Data Loader.
   • The Date Type specifies the type of dates used by the object. For date-effective objects, the Supports Updates to First Effective Start Date and Supports Updates to Last Effective End Date detail if you can adjust an existing effective start date or end date. For example, Job is date-effective, but the effective end date can't be adjusted and will always be the end-of-time. To 'end' a job's availability you would instead make the job inactive.
5. Use the navigation buttons to scroll through the details of the other objects in the hierarchy.

   

   
   
6. Review the Job Valid Grade details.



As this is a child object the Parent Object is shown.

Task 4: Reviewing Available Attributes

In this step, you'll learn how to interpret the information provided for attributes.

1. Click on the Name of the object from the Business Object Hierarchy page for the Job object.






All attributes available on the Job object are displayed:



In the attributes table you'll find many columns, some of which aren't displayed by default.

• The Name and Description are displayed in your session language.
• The METADATA Attribute displays the string that you must include in the METADATA line within your file when uploading data for the attribute.
• The Data Type indicates the type of data to supply to the attribute and can control the format data should be supplied in. For example, you supply data to an attribute with a Date data type in the format YYYY/MM/DD.
• The Key Type indicates how the attribute is used to identify records for this object and records that are referenced by this object.
2. Click on the Required filter.

   

   • The Required column indicates if the attribute is always required or required for new records.
   • The Lookup column names the lookup type used to validate this attribute.
3. Click on the Lookup link for the Active Status attribute.

   A panel displays the values for the lookup, this can be maximised in size and the content of the table exported.

   

   
   

Note:

When supplying values for lookup validated attributes in an HDL file you can supply either the lookup code or the meaning. It's recommended that you supply the lookup code as this isn't translated. When you supply translated values such as lookup meanings you need to supply them in the base language for your environment, usually US, as it's the elevated user that is used to load your data, not the session user.

Task 5: Uniquely Identifying Records

HDL supports four key types to uniquely identify a record:

• Surrogate ID - a numeric value that's system-generated when a record is created and is unique across records for the object.
• Globally Unique ID - a hexadecimal value that's also system-generated when a record is created but is unique across all records in the application.
• Source Key - a name and value pair that you define to uniquely identify a record.
• User Key - a combination of one or more attributes, visible in the application, that uniquely identify a record.

  Tip:

  Globally Unique IDs and Source Keys are collectively referred to as integration keys. Not every object supports integration keys.

  Note:

  Surrogate IDs and Globally Unique IDs can only be used to reference existing records. When creating new records, supply a user key or source key.

In this step, you'll learn how to find the attributes to supply for each of the supported key types.

1. Click on the page header to change the object in focus to Job Valid Grade.

   

   
   
2. Use the Key Type filter to fine the attribute that has a Key Type of Surrogate ID.





3. Click the Surrogate ID link to open the Attributes to Uniquely Identify the Record panel.

   

   
   

   This panel displays the details of the key types available to uniquely identify records for the object, along with the attributes to use for each key type:

   • The first row provides the details of the surrogate ID attribute and the object that it references.
   • The second row provides details of the integration keys:
     • Referenced Object Integration Name - the integration object name of the object.
     • Source Key Attributes - the attributes to supply when using a source key.
     • Globally Unique ID - the attributes to supply when using the Globally Unique ID.
   • The User Keys section lists the user keys that uniquely identify records for the object. For Job Valid Grade there are two user keys.

   Note:

   The Create and Load New Hires with HCM Data Loader (HDL) tutorial shows you how to create files with source keys and user keys.
4. Close the panel and review the other columns in the table for the surrogate ID attribute.

   

   Tip:

   A Required value of Yes indicates that either the surrogate ID is required or one of the supported alternative keys, i.e., Source Key, Globally Unique ID, or User Key.
5. Click the 2 user keys link in the User Key column.

   

   
   

   This also opens the Attributes to Uniquely Identify the Record panel.

   

   The User Keys section displays the attribute names in your session language, along with the METADATA attribute names for each of the two user keys:

   Tip:

   When only one user key combination is available, it's displayed directly in the User Key column in the main attributes table.
6. Having closed the panel, search for the attribute that has a Key Type of Parent Surrogate ID.



The parent surrogate ID attribute uniquely identifies the parent record for a child object in the object hierarchy.

7. Click on the Parent Surrogate ID link to display the attributes for each of the key types that can be used to uniquely identify the parent record.

   

   
   

   For Job Valid Grade the parent object is Job and to supply a surrogate ID value you use the attribute JobId.

   The reference to the parent Job can also be made with an integration key, seen from the Referenced Object Integration Name, Source Key Attributes and Globally Unique ID Attribute. There is one user key shown in the User Keys section.

8. Search for attributes that have a Key Type of Foreign Object Reference.






The GradeId attribute provides the reference to the Grade object. This is confirmed by the Description (not shown here).

• This attribute also supports integration keys, identified by the Integration Object Name column, and provides two user keys to uniquely identify the grade.
• The Required column indicates that you must supply a reference to a grade when creating new records, but this can be using the surrogate ID, an integration key, or a user key.
9. Click the Foreign Object Reference link to open the Attributes to Uniquely Identify the Record panel to review the key types supported and attributes to use to identify the grade.

   

   
   

Tip:

Always read the information message on this panel. It summarises the type of reference and the key types supported.
10. Having closed the panel, search for attributes with a Key Type of User Key.






These are the attributes that are included in the user keys for the surrogate ID, parent surrogate ID and foreign surrogate ID attributes.

Tip:

The Required column value may be No for most user keys because you may supply another key type to identify the record being referenced, such as the source key or surrogate ID value.

Task 6: Reviewing Flexfield Attributes

In this step you'll learn how to interpret the information provided for flexfield attributes.

Refer to the Loading Flexfield Segments, Images and Attachments with HCM Data Loader (HDL) tutorial for detailed information on how to load data into flexfield segments.

1. Change the page context to Job Legislative Extract Information.

   

   
   
2. Click on the Flexfield Attributes tab.






Tip:

The Flexfield Attributes tab is only seen when the object selected in the hierarchy supports flexfield segments.
3. Use the filters to display attributes for the Job Legislation Data category and United States Job Information context.

   

   
   
4. Search for the attribute that starts FLEX.

   

   
   

   The FLEX:{flexfield code} attribute is always needed when you supply data for any flexfield segment.

   • The attribute name tells HDL the flexfield code that data is being supplied for. For example, PER_JOBS_LEG_EFF.
   • For each data line containing flexfield segments, you supply this attribute with the flexfield context code of the data supplied on the line.

     Tip:

     You can refer to the METADATA Attribute to determine the flexfield context code or use the Manage Columns functionality to add the Context Code to the table.
5. Search for the EFF_CATEGORY_CODE attribute.



The EFF_CATEGORY_CODE attribute is always needed when you supply data for extensible flexfield segments. You supply the extensible flexfield category code to this attribute, such as JOB_LEG.

Tip:

Use Manage Columns panel to add the Category Code to your table.

Note:

Descriptive flexfields don't have categories so this field isn't available for descriptive flexfields.
6. Review the other attributes listed:






Flexfield METADATA attribute names always have a hint, in the format:

{flexfield attribute name}({flexfield code}={context code})

For example, _EEO1_CATEGORY(PER_JOBS_LEG_EFF=HRX_US_JOBS). This format tells HDL that the EEO-1 Category segment belongs to the PER_JOBS_LEG_EFF flexfield in the HRX_US_JOBS context.

Some flexfield segments offer two attributes, one that accepts a code, the other accepts the meaning, or display value. The attributes that accept the display value will always have the format:

{flexfield attribute name}_Display({flexfield code}={context code})

For example, _EEO1_CATEGORY_Display(PER_JOBS_LEG_EFF=HRX_US_JOBS).

Tip:

For lookup validated flexfield segments, it is recommended that you supply the code value to the base attribute, to avoid translation issues. Use the Manage Value Sets task to review the value set used to validate the flexfield segment and identify valid values.

Task 7: Understanding Source Reference Attributes

Data loaded by HCM Data Loader is held in generic staging tables, the values supplied for a business object will not always be stored in the same database column.

WARNING:

You should not attempt to read data directly from the HDL staging tables. Instead, supply attribute values that you want to report, total, or reconcile on, to the source reference attributes.

Source reference attributes are displayed in the Object Status, Message Details, and Object Hierarchy pages of the Import and Load Data user interface and can be extracted using HCM Extracts and OTBI reporting.

1. Review the attributes available to any business object.
2. Search for attributes that have a label starting Reference.



There are 10 reference attributes and a single reference context attribute.

Tip:

These attributes are common across all objects supported by HCM Data Loader.

In the METADATA line you specify prompts to name each of your source reference columns using this format:

SourceRefTableName={context value}|SourceRef001={source-column-001}|SourceRef002={source-column-002}|SourceRef003={source-column-003}

For example:

METADATA|ElementEntry|...|SourceRefTableName=ElementEntry|SourceRef001=PersonNumber|SourceRef002=ElementName|SourceRef003=Amount
MERGE|ElementEntry|...||892334|Travel Allowance|200

Don't supply a value for the SourceRefTableName attribute in your MERGE lines, this attribute allows you to supply a context for the reference attributes in the METADATA line only.

Task 8: Downloading METADATA Template Files

When you supply data to be bulk-loaded using HCM Data Loader, your file must use the name defined for the business object and must include METADATA lines for the objects and attributes you are supplying data for.

Instead of generating this manually, you can download a template file which includes all METADATA lines for the business object hierarchy.

1. On the View Business Objects page, select the Job business object and click the Download METADATA Template action.






A file named for the business object is downloaded, in this case Job.dat.

2. Open the downloaded file, it will look something like this:

COMMENT Data for Business Object: Job Version: V2 Created on: 14-01-2026
METADATA|Job|FLEX:PER_JOBS_DFF|FBLJG(PER_JOBS_DFF=Global Data Elements)|_ATT1_UK_001_SIMPLE(PER_JOBS_DFF=Global Data Elements)|_job_global(PER_JOBS_DFF=Global Data Elements)|dffCol1(PER_JOBS_DFF=Global Data Elements)|ghrJobBpad87211(PER_JOBS_DFF=Global Data Elements)|ghrJobBpad87212(PER_JOBS_DFF=Global Data Elements)|incrDffCol2(PER_JOBS_DFF=Global Data Elements)|jobAttr1(PER_JOBS_DFF=Global Data Elements)|jobglobal(PER_JOBS_DFF=Global Data Elements)|FBLJL(PER_JOBS_DFF=JobContext1)|joblocal(PER_JOBS_DFF=JobContext1)|zperJobSegment(PER_JOBS_DFF=ZPER_JOB_CONTEXT)|JobId|JobCode|JobFamilyId|ActiveStatus|FullPartTime|JobFunctionCode|ManagerLevel|MedicalCheckupRequired|StandardWorkingHours|StandardWorkingFrequency|StandardAnnualWorkingDuration|AnnualWorkingDurationUnits|RegularTemporary|BenchmarkJobFlag|BenchmarkJobId|ProgressionJobId|SetId|EffectiveStartDate|EffectiveEndDate|Name|ApprovalAuthority|SchedulingGroup|SetCode|BenchmarkJobCode|ProgressionJobCode|JobFamilyName|JobFamilyCode|ActionReasonCode|SourceSystemOwner|SourceSystemId|GUID|CategoryCode|GradeLadderId|GradeLadderName|RequisitionTemplateId|RequisitionNumber|SourceRefTableName=|SourceRef001=|SourceRef002=|SourceRef003=|SourceRef004=|SourceRef005=|SourceRef006=|SourceRef007=|SourceRef008=|SourceRef009=|SourceRef010=
METADATA|JobEvaluation|FLEX:PER_EVALUATION_CRITERIA_DFF|_EVC(PER_EVALUATION_CRITERIA_DFF=Global Data Elements)|JobId|DateEvaluated|Knowhow|Accountability|EvaluationSystem|JobEvaluationId|MeasuredIn|ProblemSolving|WorkingConditions|JobCode|SetCode|SourceSystemOwner|SourceSystemId|GUID|SourceRefTableName=|SourceRef001=|SourceRef002=|SourceRef003=|SourceRef004=|SourceRef005=|SourceRef006=|SourceRef007=|SourceRef008=|SourceRef009=|SourceRef010=
METADATA|JobGrade|GradeId|JobId|EffectiveStartDate|EffectiveEndDate|ValidGradeId|GradeCode|SetCode|JobCode|SourceSystemOwner|SourceSystemId|GUID|GradeSetCode|SourceRefTableName=|SourceRef001=|SourceRef002=|SourceRef003=|SourceRef004=|SourceRef005=|SourceRef006=|SourceRef007=|SourceRef008=|SourceRef009=|SourceRef010=
METADATA|JobExtraInfo|FLEX:PER_JOBS_EIT_EFF|EFF_CATEGORY_CODE|jobEffSegment1(PER_JOBS_EIT_EFF=job-eff-context)|EffectiveEndDate|EffectiveStartDate|InformationType|JeiInformationCategory|JobExtraInfoId|JobId|LegislationCode|SequenceNumber|SourceSystemOwner|SourceSystemId|GUID|JobCode|SetCode|SetId|SourceRefTableName=|SourceRef001=|SourceRef002=|SourceRef003=|SourceRef004=|SourceRef005=|SourceRef006=|SourceRef007=|SourceRef008=|SourceRef009=|SourceRef010=
METADATA|JobLegislative|FLEX:PER_JOBS_LEG_EFF|EFF_CATEGORY_CODE|_EEOG(PER_JOBS_LEG_EFF=CA)|_EEOG_Display(PER_JOBS_LEG_EFF=CA)|_NOC_CODE(PER_JOBS_LEG_EFF=CA)|_NOC_CODE_Display(PER_JOBS_LEG_EFF=CA)|employmentEquityEligible(PER_JOBS_LEG_EFF=CA)|employmentEquityEligible_Display(PER_JOBS_LEG_EFF=CA)|_POSITION_TYPE(PER_JOBS_LEG_EFF=CH)|_POSITION_TYPE_Display(PER_JOBS_LEG_EFF=CH)|seg1(PER_JOBS_LEG_EFF=Context1)|seg2(PER_JOBS_LEG_EFF=Context2)|_ECAP_JOB(PER_JOBS_LEG_EFF=FR)|_ECAP_JOB_Display(PER_JOBS_LEG_EFF=FR)|_INSEE_PCS_CODE(PER_JOBS_LEG_EFF=FR)|_INSEE_PCS_CODE_Display(PER_JOBS_LEG_EFF=FR)|_INSEE_PCS_EXT_CODE(PER_JOBS_LEG_EFF=FR)|_INSEE_PCS_EXT_CODE_Display(PER_JOBS_LEG_EFF=FR)|_EEO1_CATEGORY(PER_JOBS_LEG_EFF=HRX_US_JOBS)|_EEO1_CATEGORY_Display(PER_JOBS_LEG_EFF=HRX_US_JOBS)|_FLSA_STATUS(PER_JOBS_LEG_EFF=HRX_US_JOBS)|_FLSA_STATUS_Display(PER_JOBS_LEG_EFF=HRX_US_JOBS)|_JOB_GROUP(PER_JOBS_LEG_EFF=HRX_US_JOBS)|_JOB_GROUP_Display(PER_JOBS_LEG_EFF=HRX_US_JOBS)|_LINE_OF_PROGRESSION(PER_JOBS_LEG_EFF=HRX_US_JOBS)|eeo4Category(PER_JOBS_LEG_EFF=HRX_US_JOBS)|eeo4Category_Display(PER_JOBS_LEG_EFF=HRX_US_JOBS)|eeo4Function(PER_JOBS_LEG_EFF=HRX_US_JOBS)|eeo4Function_Display(PER_JOBS_LEG_EFF=HRX_US_JOBS)|standardOccupationalClassifica(PER_JOBS_LEG_EFF=HRX_US_JOBS)|_ORA_HRX_BR_JOBS_CBO(PER_JOBS_LEG_EFF=ORA_HRX_BR_JOBS)|_ORA_HRX_BR_JOBS_CBO_Display(PER_JOBS_LEG_EFF=ORA_HRX_BR_JOBS)|oraHrxCaWcJobClUnit(PER_JOBS_LEG_EFF=ORA_HRX_CA_WC_JOBS)|oraHrxCaWcJobClUnit_Display(PER_JOBS_LEG_EFF=ORA_HRX_CA_WC_JOBS)|oraHrxCaWcJobProv(PER_JOBS_LEG_EFF=ORA_HRX_CA_WC_JOBS)|oraHrxCaWcJobProv_Display(PER_JOBS_LEG_EFF=ORA_HRX_CA_WC_JOBS)|oraHrxCaWcJobPsu(PER_JOBS_LEG_EFF=ORA_HRX_CA_WC_JOBS)|oraHrxCaWcJobPsu_Display(PER_JOBS_LEG_EFF=ORA_HRX_CA_WC_JOBS)|oraHrxCaWcJobUniqueSeg(PER_JOBS_LEG_EFF=ORA_HRX_CA_WC_JOBS)|_ORA_HRX_MX_SI_SALARY_TYPE(PER_JOBS_LEG_EFF=ORA_HRX_MX_JOBS)|_ORA_HRX_MX_SI_SALARY_TYPE_Display(PER_JOBS_LEG_EFF=ORA_HRX_MX_JOBS)|perjobmrnuk(PER_JOBS_LEG_EFF=PER_JOB_TEST_MR)|perjobmruk(PER_JOBS_LEG_EFF=PER_JOB_TEST_MR)|JobId|JobLegId|EffectiveStartDate|EffectiveEndDate|InformationCategory|LegislationCode|SourceSystemOwner|SourceSystemId|GUID|JobCode|SetCode|SetId|SequenceNumber|SourceRefTableName=|SourceRef001=|SourceRef002=|SourceRef003=|SourceRef004=|SourceRef005=|SourceRef006=|SourceRef007=|SourceRef008=|SourceRef009=|SourceRef010=

Note:

You should remove METADATA lines for objects you're not including in your file and remove attributes from the remaining METADATA lines that you're not supplying values for.

Task 9: Generating Object Hierarchy Overview Spreadsheets

The overview spreadsheet supplies the same information as the View Business Objects user interface, but in a spreadsheet format. This can be useful for reviewing the business object shape offline and allows you to search for attributes across objects in a business object hierarchy.

1. On the View Business Objects page, select the Job business object and click the Download Overview Spreadsheet action.






A file named Job.xlsx is downloaded.

Tip:

If a file with this name already exists in your Downloads folder, the name is appended with a number to make it unique.
2. Open the downloaded file, you are asked if you want to connect:

   

   
   

   Note:

   You'll only be prompted to log in if the Desktop Integration tool is installed successfully.
3. Click Yes.
4. Log in with your application username.
5. Review the information on the Hierarchy Details worksheet:





6. Click on the Attributes worksheet. The list of supported attributes across all objects in the business object hierarchy is downloaded.





7. Click on the Flexfield Attributes worksheet. If the object hierarchy supports loading into flexfield segments, the list of attributes is downloaded.

Tip:

You can edit and locally save this spreadsheet. To keep your edits though, don't log in when you next open the spreadsheet.

Next Steps

The following tutorials will further expand your HCM Data Loader knowledge:

• Create and Maintain Data with HCM Data Loader (HDL)
• Create and Load New Hires with HCM Data Loader (HDL)
• Make Date-Effective Changes with HCM Data Loader (HDL)
• Loading Flexfield Segments, Images and Attachments with HCM Data Loader (HDL)

Related Links

Links to the latest tutorials for HDL and HSDL are available in this topic on Cloud Customer Connect:

• HCM Data Loader Oracle by Example Tutorials

For further information, refer to this help topic:

• Sources of Business Object Information

Acknowledgements

• Authors - Ema Johnson (Senior Principal Product Manager)

More Learning Resources

Explore other labs on docs.oracle.com/learn or access more free learning content on the Oracle Learning YouTube channel. Additionally, visit education.oracle.com/learning-explorer to become an Oracle Learning Explorer.

For product documentation, visit Oracle Help Center.

---

Title and Copyright Information

Understanding HCM Data Loader (HDL) Business Objects

F85605-08

January 2026

Copyright ©2026,

Oracle and/or its affiliates.