Oracle Global HR Cloud · Subject 1 · 19 lessons

Configuring Core HCM

The enterprise structures every other part of Oracle Global HR sits on: legal entities, business units, legislative data groups and the reference data that decides which rules apply where.

All 19 lessons, free to read in full. No sign-in required.

What this course covers

Enterprise
Legal Entity
Legal Employer
Legislative Data Group
Payroll Statutory Unit
Business Unit
Division
Reference Data Set
Position Synchronization
Actions & Reasons
Organization Trees
Enterprise Structures Configurator
Department
Job
Grade
Grade Ladder
Position
Geography
Location

Lesson 01

Enterprise

What is the highest-level organizational framework?

Fundamentals

Foundation

Enterprise

What is the highest-level organizational framework?

TechNova story · The expansion decision

Enterprise: learn it through a business decision

TechNova began in India. It now plans operations in Singapore and the UAE, but all companies will use the same Oracle HCM environment. The design team sees countries, offices and business lines and immediately proposes three Enterprises.

First principle: The Enterprise is the top-level organization in an Oracle HCM implementation. It provides the common framework within which legal, operational and workforce structures exist.

Pause, decide, then reveal the reasoning

Answer in your own words before opening each explanation.

Question 1 Does every country require a separate Enterprise?

Answer: No. A country, office, Legal Entity or Business Unit does not by itself justify another Enterprise.

Why: Enterprise is the highest HCM framework. The consultant first asks whether these organizations belong inside one common implementation context—not how many boxes appear on the organization chart.

Question 2 Then what represents TechNova's separately registered companies?

Answer: Legal Entities represent the registered organizations inside the Enterprise.

Why: This keeps the application-wide framework separate from legal registrations and statutory responsibilities.

Question 3 What must the team decide before hiring the first worker?

Answer: It must agree enterprise-level HCM choices such as employment-model and numbering behaviour, plus its position-management approach.

Why: These are foundational decisions. They can influence later work relationships, assignments and master data, so they should not be treated as cosmetic defaults.

Question 4 If TechNova opens a second Bengaluru office, what changes?

Answer: Normally a Location is added or changed—not the Enterprise.

Why: A workplace answers where work occurs. It does not create a new top-level HCM framework.

If the business changes…Ask whether the business has crossed an implementation boundary or merely added a legal, operational or physical structure. Most growth happens inside the existing Enterprise.

Simple mental pictureEnterprise is the common HCM world; the organizations doing business inside that world are modeled below it.

What does Enterprise do in Oracle?

Contains or provides context for legal entities
Supports enterprise-level employment configuration
Sits above operational and workforce structures

Why is it useful, and when do consultants use it?

Why the business needs it

It gives the implementation a single organizational context and holds enterprise-level HCM information and defaults.

Highest organizational framework
Not the same as Legal Entity
One enterprise may contain multiple legal entities

When it is used

Usually established during initial enterprise configuration. Decisions affect later employment and numbering behaviour.

Typical setup task:
Setup and Maintenance → Workforce Deployment offering → Define Enterprise Structures → Manage Enterprise HCM Information

Important distinction

Enterprise
What is the highest-level organizational framework?

Do not confuse

Do not create multiple enterprises merely because a company has several countries, legal entities or business units.

How a consultant reasons

Read the business factsIdentify the questionChoose the objectCheck dependenciesTest the impact

Easy exam definition

The Enterprise is the top-level organization in an Oracle HCM implementation. It provides the common framework within which legal, operational and workforce structures exist.

Memory line: Enterprise is the common HCM world; the organizations doing business inside that world are modeled below it.

Connect it to the TechNova design

Business questionWhat is the highest-level organizational framework?

TechNova recordTechNova Group

Why it existsIt gives the implementation a single organizational context and holds enterprise-level HCM information and defaults.

Certification trapDo not create multiple enterprises merely because a company has several countries, legal entities or business units.

Check your understanding

Highest organizational framework
Not the same as Legal Entity
One enterprise may contain multiple legal entities
Enterprise settings can influence employment processing
Design from business reality, not the organization chart alone

Relationships

Foundation

Enterprise

What is the highest-level organizational framework?

Relationship map

Enterprise

→

Legal & operational structures

→

Enterprise

→

Worker assignment

Direct relationships

Contains or provides context for legal entities
Supports enterprise-level employment configuration
Sits above operational and workforce structures

Think like a consultant: Identify whether the requirement changes the legal, operational, workforce, or sharing layer before creating or editing this object.

Implementation

Foundation

Enterprise

What is the highest-level organizational framework?

Implementation purpose

It gives the implementation a single organizational context and holds enterprise-level HCM information and defaults.

Typical setup route

Setup and Maintenance → Workforce Deployment offering → Define Enterprise Structures → Manage Enterprise HCM Information
Navigation and page names can vary with enabled Redwood experiences and quarterly updates. Learn the setup task and outcome.

Prerequisites

Usually established during initial enterprise configuration. Decisions affect later employment and numbering behaviour.

Implementation checklist

Confirm the business owner and exact requirement.
Check whether an existing record can be reused.
Agree naming, codes, effective dates and sharing.
Configure in a test environment.
Validate transactions, security, reporting and integrations.
Document the design decision and migration method.

Technical Details

Foundation

Enterprise

What is the highest-level organizational framework?

Consultant workspace

Enterprise Technical Details

Configure, migrate, maintain, validate and troubleshoot this object.

Primary technical question

What is the highest-level organizational framework?

Enterprise-level settings can be date-sensitive; treat structural changes as governed setupSet-enabled: No

1Technical Profile

Oracle role in design	Top-level HCM framework
Date behavior	Enterprise-level settings can be date-sensitive; treat structural changes as governed setup
Set-enabled	No
Main setup task	Manage Enterprise HCM Information
Main migration approach	Not a normal HDL master-data load
Used by	Contains or provides context for legal entities; Supports enterprise-level employment configuration; Sits above operational and workforce structures

3Prerequisites and Configuration Sequence

Confirmed implementation boundary and enterprise name
Legal-country roadmap and worker-numbering decisions
Position-management, person-search and enterprise-default decisions

Sequence rule: Complete dependencies and approve stable codes before creating or loading Enterprise.

4Field Dictionary

Field	What it controls	TechNova example	Common mistake
Enterprise name Requireddownstream-sensitive	Identifies the overall HCM framework	TechNova Group	Using a country or BU name as the enterprise
Worker-number generation Enterprise default	Controls person-number creation behavior	Automatic numbering	Changing numbering without integration review
Position management settings Inheriteddownstream-sensitive	Controls enterprise-wide position behavior	Position management enabled	Enabling after worker loads without impact analysis
Effective context Date-sensitive	Determines when enterprise settings apply	Approved conversion date	Using Correction when history should show a change

5UI Configuration Walkthrough

Open the task and select the enterprise record.
Review enterprise information and numbering/default settings.
Review position-management and synchronization decisions with workforce design.
Save in test, then validate hire, search, position and integration behavior.

6HDL, HSDL and REST Availability

Method	Status	Best use
Manual UI	Supported	Governed setup and maintenance
HDL	Not primary	Enterprise record is not a routine HDL load
HSDL	Not primary	Use for supported business objects, not this core setup
REST	Check current metadata	Do not assume update capability for enterprise setup

Before production: Download the current business-object template or inspect current REST metadata. Release, feature and privilege differences can change supported attributes.

7Sample Data Load with Explanation

TECHNICAL DESIGN RECORD
Object: Enterprise
Name: TechNova Group
Decision: One enterprise; country companies represented as Legal Entities
Position management: Enabled before assignment migration

This is a configuration-decision record, not an HDL file. Preserve approval evidence because the enterprise choices influence later data loads.

Source-key ruleKeep SourceSystemOwner and SourceSystemId stable so later MERGE operations update the same record.

Dependency ruleLoad and validate referenced parent records before dependent objects.

8Effective Dating and Maintenance Rules

Use Correction only to fix an error in the same historical record.
Use a dated change when the business rule must differ from a later date.
Do not create another enterprise simply for a new country or business line.
Regression-test worker numbering, position behavior and integrations after changing enterprise defaults.

Create

→

Correct an error

→

Update from a date

→

Inactivate safely

9Security and Required Privileges

Maintenance requires access to enterprise HCM setup. A user may be able to process workers without being allowed to change enterprise-level settings. Separate setup authority from operational HR access.

Diagnostic rule: Separate three questions: Can the user open the function? Can the user maintain this object? Can the user see the relevant secured data?

10Downstream Impact

PeoplePerson numbering, search and worker defaults

PositionsEnterprise position-management and synchronization behavior

IntegrationsIdentifiers and assumptions used by inbound/outbound interfaces

Assess current records, future-dated transactions, reports, approvals and integrations before changing a production value.

11Validation Checklist

Enterprise boundary matches approved organization design
Worker numbering produces expected values
Position settings are established before assignment migration
Hire and person search work for intended users
Integration mappings do not rely on an obsolete default

12Troubleshooting Scenarios

Symptom	Likely cause	What to do
Unexpected person number	Numbering method or starting value	Review enterprise numbering and prior sequence use
Position values do not flow	Synchronization not enabled or attribute not selected	Review enterprise/legal-employer position settings
New country team requests another enterprise	Legal structure confused with HCM boundary	Model the new company as a Legal Entity first

13Technical Consultant Challenge

TechNova adds a Singapore company but will keep one global HCM environment. A designer proposes a second Enterprise. What should you do?

Consultant answer

Reject the proposal unless there is a genuine separate HCM implementation boundary. Add the appropriate Legal Entity, Legal Employer and country structures inside the existing enterprise, then validate statutory and security requirements.

Certification

Foundation

Enterprise

What is the highest-level organizational framework?

Certification trap

Watch for this: Do not create multiple enterprises merely because a company has several countries, legal entities or business units.

How to reason through a scenario

Underline the business question.
Identify the layer: legal, operational, workforce, or control.
Remove options that answer a different business question.
Check effective date, reuse, sharing and dependency clues.
Choose the solution that preserves history and avoids duplication.

Revision

Foundation

Enterprise

What is the highest-level organizational framework?

30-second revision

Enterprise
The Enterprise is the top-level organization in an Oracle HCM implementation. It provides the common framework within which legal, operational and workforce structures exist.

Example: TechNova Group
Main trap: Do not create multiple enterprises merely because a company has several countries, legal entities or business units.

Active recall

What is the highest-level organizational framework?
Which objects depend on or use Enterprise?
What must exist before it is configured?
Which date, status or sharing controls matter?
What configuration mistake would you warn the client about?

Lesson 02

Legal Entity

Which organization is legally registered?

Fundamentals

Legal framework

Legal Entity

Which organization is legally registered?

TechNova story · The registration question

Legal Entity: learn it through a business decision

TechNova Group has a brand name, an Indian private limited company, four offices and several business units. Priya asks, 'Which of these is the company in the eyes of the law?'

First principle: A Legal Entity is an organization recognized by law that can own assets, incur liabilities, enter contracts and have statutory obligations.

Pause, decide, then reveal the reasoning

Answer in your own words before opening each explanation.

Question 1 Which record represents TechNova India Pvt Ltd's legal registration?

Answer: A Legal Entity.

Why: It represents an organization recognized by law that can contract, own assets, incur liabilities and carry statutory obligations.

Question 2 Do the Mumbai and Bengaluru offices need separate Legal Entities?

Answer: Not merely because they are separate offices.

Why: Offices are normally Locations. A separate Legal Entity is driven by a distinct legal registration or legal responsibility, not distance.

Question 3 Can workers be hired as soon as the Legal Entity exists?

Answer: Only when the organization is also classified appropriately as a Legal Employer.

Why: Legal Entity answers 'which registered organization?' Legal Employer answers 'who employs the worker?'

Question 4 TechNova forms a separately incorporated Singapore company. What should be assessed?

Answer: Create and configure the new Legal Entity with the registrations and classifications its business functions require.

Why: The legal facts drive the object. Do not copy every Indian classification without checking Singapore's employment and statutory design.

If the business changes…An address change does not automatically change the legal jurisdiction. First determine whether the registered organization changed or only its address, office or operating unit changed.

Simple mental pictureLegal Entity is the registered organization; classifications tell Oracle which legal roles it performs.

What does Legal Entity do in Oracle?

Belongs within the enterprise
May be classified as Legal Employer or Payroll Statutory Unit
Can be associated with business units

Why is it useful, and when do consultants use it?

Why the business needs it

Oracle needs the registered organization to support legal reporting and statutory responsibilities.

Represents a registered organization
May carry several legal classifications
Not the same as a Business Unit

When it is used

Geography/address information and enterprise framework should be understood first.

Typical setup task:
Setup and Maintenance → Manage Legal Entity

Important distinction

Legal Entity
Which organization is legally registered?

Do not confuse

A Legal Entity does not automatically employ workers; it must have the Legal Employer classification.

How a consultant reasons

Read the business factsIdentify the questionChoose the objectCheck dependenciesTest the impact

Easy exam definition

A Legal Entity is an organization recognized by law that can own assets, incur liabilities, enter contracts and have statutory obligations.

Memory line: Legal Entity is the registered organization; classifications tell Oracle which legal roles it performs.

Connect it to the TechNova design

Business questionWhich organization is legally registered?

TechNova recordTechNova India Pvt Ltd

Why it existsOracle needs the registered organization to support legal reporting and statutory responsibilities.

Certification trapA Legal Entity does not automatically employ workers; it must have the Legal Employer classification.

Check your understanding

Represents a registered organization
May carry several legal classifications
Not the same as a Business Unit
Legal address and registrations matter
Supports statutory obligations

Relationships

Legal framework

Legal Entity

Which organization is legally registered?

Relationship map

Enterprise

→

Legal & operational structures

→

Legal Entity

→

Worker assignment

Direct relationships

Belongs within the enterprise
May be classified as Legal Employer or Payroll Statutory Unit
Can be associated with business units

Think like a consultant: Identify whether the requirement changes the legal, operational, workforce, or sharing layer before creating or editing this object.

Implementation

Legal framework

Legal Entity

Which organization is legally registered?

Implementation purpose

Oracle needs the registered organization to support legal reporting and statutory responsibilities.

Typical setup route

Setup and Maintenance → Manage Legal Entity
Navigation and page names can vary with enabled Redwood experiences and quarterly updates. Learn the setup task and outcome.

Prerequisites

Geography/address information and enterprise framework should be understood first.

Implementation checklist

Confirm the business owner and exact requirement.
Check whether an existing record can be reused.
Agree naming, codes, effective dates and sharing.
Configure in a test environment.
Validate transactions, security, reporting and integrations.
Document the design decision and migration method.

Technical Details

Legal framework

Legal Entity

Which organization is legally registered?

Consultant workspace

Legal Entity Technical Details

Configure, migrate, maintain, validate and troubleshoot this object.

Primary technical question

Which organization is legally registered?

Effective setup with registrations and classificationsSet-enabled: No

1Technical Profile

Oracle role in design	Registered legal organization
Date behavior	Effective setup with registrations and classifications
Set-enabled	No
Main setup task	Manage Legal Entity
Main migration approach	Controlled legal setup; do not treat ordinary workforce HDL as the default migration route
Used by	Belongs within the enterprise; May be classified as Legal Employer or Payroll Statutory Unit; Can be associated with business units

3Prerequisites and Configuration Sequence

Registration evidence, country and legal address
Legal name, identifier and fiscal/statutory requirements
Decision on Legal Employer and Payroll Statutory Unit classifications

Sequence rule: Complete dependencies and approve stable codes before creating or loading Legal Entity.

4Field Dictionary

Field	What it controls	TechNova example	Common mistake
Legal name Requireddownstream-sensitive	Name recognized by law	TechNova India Pvt Ltd	Using a marketing brand
Legal-entity identifier Requiredintegration-sensitive	Stable statutory or internal identifier	TN-IN-LE	Changing the identifier with the display name
Registration and address Country-controlled	Supports country and statutory identity	India registration and registered office	Entering a work location instead of registered address
Classifications Downstream-sensitive	Defines whether the entity employs or reports payroll	Legal Employer + PSU where justified	Creating duplicate entities instead of classifications

5UI Configuration Walkthrough

Confirm legal evidence and country before data entry.
Create the legal entity using the legal name, identifier and registered address.
Add only the classifications supported by the real responsibility model.
Validate legal-employer availability, registrations and downstream payroll/worker setup.

6HDL, HSDL and REST Availability

Method	Status	Best use
Manual UI	Supported	Primary governed setup route
FSM migration	Check setup offering	Move supported setup between environments
HDL	Not primary	Do not assume Organization.dat creates the legal registration
REST	Check current metadata	Legal setup resources are release and privilege sensitive

Before production: Download the current business-object template or inspect current REST metadata. Release, feature and privilege differences can change supported attributes.

7Sample Data Load with Explanation

LEGAL ENTITY DESIGN
Legal name: TechNova India Pvt Ltd
Country: India
Identifier: TN-IN-LE
Classifications: Legal Employer; Payroll Statutory Unit
Evidence: incorporation and statutory registrations

Create from approved legal evidence. Classifications may share one Legal Entity when the same registered company performs both responsibilities.

Source-key ruleKeep SourceSystemOwner and SourceSystemId stable so later MERGE operations update the same record.

Dependency ruleLoad and validate referenced parent records before dependent objects.

8Effective Dating and Maintenance Rules

Correct spelling or registration data only when the historical record was wrong.
Use effective changes when an attribute genuinely changes from a given date.
Do not delete or recreate an entity that already owns worker or statutory history.
Evaluate work relationships, payroll registrations and integrations before inactivation.

Create

→

Correct an error

→

Update from a date

→

Inactivate safely

9Security and Required Privileges

Legal-structure setup needs dedicated implementation privileges. Data-security access to workers does not grant authority to maintain registered-company setup.

Diagnostic rule: Separate three questions: Can the user open the function? Can the user maintain this object? Can the user see the relevant secured data?

10Downstream Impact

EmploymentLegal Employer classification enables work relationships

PayrollPSU classification and registrations support statutory reporting

ReportingLegal company is a major statutory and analytics dimension

Assess current records, future-dated transactions, reports, approvals and integrations before changing a production value.

11Validation Checklist

Legal name matches registration evidence
Country and registered address are correct
Identifier is stable and unique
Classifications match actual responsibilities
Hire and statutory setup reference the expected entity

12Troubleshooting Scenarios

Symptom	Likely cause	What to do
Entity absent in hire flow	Legal Employer classification missing or ineffective	Review classification and dates
Duplicate legal companies	Separate records created for separate classifications	Consolidate design before transactional use
Payroll setup cannot reference entity	PSU classification or registration incomplete	Review payroll statutory design

13Technical Consultant Challenge

The same Indian company signs employment contracts and reports payroll taxes. The team proposes two Legal Entities. What should you do?

Consultant answer

Use one Legal Entity with both classifications when that matches the legal evidence and country design. Do not duplicate the registered company merely to separate labels.

Certification

Legal framework

Legal Entity

Which organization is legally registered?

Certification trap

Watch for this: A Legal Entity does not automatically employ workers; it must have the Legal Employer classification.

How to reason through a scenario

Underline the business question.
Identify the layer: legal, operational, workforce, or control.
Remove options that answer a different business question.
Check effective date, reuse, sharing and dependency clues.
Choose the solution that preserves history and avoids duplication.

Revision

Legal framework

Legal Entity

Which organization is legally registered?

30-second revision

Legal Entity
A Legal Entity is an organization recognized by law that can own assets, incur liabilities, enter contracts and have statutory obligations.

Example: TechNova India Pvt Ltd
Main trap: A Legal Entity does not automatically employ workers; it must have the Legal Employer classification.

Active recall

Which organization is legally registered?
Which objects depend on or use Legal Entity?
What must exist before it is configured?
Which date, status or sharing controls matter?
What configuration mistake would you warn the client about?

Lesson 03

Legal Employer

Who legally employs the worker?

Fundamentals

Legal framework

Legal Employer

Who legally employs the worker?

TechNova story · Who signs the employment contract?

Legal Employer: learn it through a business decision

Priya will work in Bengaluru for the Software BU. Her manager sits in Mumbai. The project team must decide which value owns her employment relationship.

First principle: A Legal Employer is a Legal Entity classification for an organization that employs workers.

Pause, decide, then reveal the reasoning

Answer in your own words before opening each explanation.

Question 1 Is Priya employed by the Bengaluru Location or Software BU?

Answer: No. She is employed by the Legal Employer named in her employment relationship.

Why: Location says where; Business Unit says operational context; Legal Employer establishes the legal employment boundary.

Question 2 What Oracle record connects Priya to that employer?

Answer: A Work Relationship.

Why: Assignments sit within that relationship and record Priya's actual working placement and details.

Question 3 Priya moves from Software BU to Cloud Services BU under the same employer. Is this automatically a new Work Relationship?

Answer: No. A BU change within the same Legal Employer can normally be handled as an assignment-level change or transfer.

Why: The legal-employer boundary did not change, although other transaction consequences still require assessment.

Question 4 What if Priya moves to a different TechNova Legal Employer?

Answer: Use the appropriate legal-employer transfer process, commonly a global transfer, rather than simply overwriting an assignment field.

Why: Crossing the employer boundary affects employment history and can affect payroll, benefits, seniority and statutory processing.

If the business changes…Always start a movement scenario by asking, 'Did the Legal Employer change?' That single question separates ordinary assignment movement from an employment-boundary transaction.

Simple mental pictureLegal Employer owns the Work Relationship; Assignment records the worker's placement inside it.

What does Legal Employer do in Oracle?

Is a classified Legal Entity
Owns work relationships
Participates in hire, transfer and termination transactions

Why is it useful, and when do consultants use it?

Why the business needs it

A worker’s work relationship is created with a Legal Employer. This establishes the legal employment boundary.

A Legal Entity classification
Owns employment relationships
Required for worker hiring

When it is used

The Legal Entity must exist and the legislative design must be understood.

Typical setup task:
Setup and Maintenance → Manage Legal Entity → Legal Employer classification

Important distinction

Legal Employer
Who legally employs the worker?

Do not confuse

Location answers where work occurs; Legal Employer answers who employs.

How a consultant reasons

Read the business factsIdentify the questionChoose the objectCheck dependenciesTest the impact

Easy exam definition

A Legal Employer is a Legal Entity classification for an organization that employs workers.

Memory line: Legal Employer owns the Work Relationship; Assignment records the worker's placement inside it.

Connect it to the TechNova design

Business questionWho legally employs the worker?

TechNova recordTechNova India Pvt Ltd

Why it existsA worker’s work relationship is created with a Legal Employer. This establishes the legal employment boundary.

Certification trapLocation answers where work occurs; Legal Employer answers who employs.

Check your understanding

A Legal Entity classification
Owns employment relationships
Required for worker hiring
Changing employer may require global transfer
Not every Legal Entity is a Legal Employer

Relationships

Legal framework

Legal Employer

Who legally employs the worker?

Relationship map

Enterprise

→

Legal & operational structures

→

Legal Employer

→

Worker assignment

Direct relationships

Is a classified Legal Entity
Owns work relationships
Participates in hire, transfer and termination transactions

Think like a consultant: Identify whether the requirement changes the legal, operational, workforce, or sharing layer before creating or editing this object.

Implementation

Legal framework

Legal Employer

Who legally employs the worker?

Implementation purpose

A worker’s work relationship is created with a Legal Employer. This establishes the legal employment boundary.

Typical setup route

Setup and Maintenance → Manage Legal Entity → Legal Employer classification
Navigation and page names can vary with enabled Redwood experiences and quarterly updates. Learn the setup task and outcome.

Prerequisites

The Legal Entity must exist and the legislative design must be understood.

Implementation checklist

Confirm the business owner and exact requirement.
Check whether an existing record can be reused.
Agree naming, codes, effective dates and sharing.
Configure in a test environment.
Validate transactions, security, reporting and integrations.
Document the design decision and migration method.

Technical Details

Legal framework

Legal Employer

Who legally employs the worker?

Consultant workspace

Legal Employer Technical Details

Configure, migrate, maintain, validate and troubleshoot this object.

Primary technical question

Who legally employs the worker?

Classification and employment use are effective-datedSet-enabled: No

1Technical Profile

Oracle role in design	Legal Entity classification that owns work relationships
Date behavior	Classification and employment use are effective-dated
Set-enabled	No
Main setup task	Manage Legal Entity / Manage Legal Employer
Main migration approach	Configure the legal classification before loading worker relationships
Used by	Is a classified Legal Entity; Owns work relationships; Participates in hire, transfer and termination transactions

3Prerequisites and Configuration Sequence

Existing Legal Entity
Country and employment-law requirements
Payroll relationship, PSU and LDG design where payroll is in scope

Sequence rule: Complete dependencies and approve stable codes before creating or loading Legal Employer.

4Field Dictionary

Field	What it controls	TechNova example	Common mistake
Legal Employer name Inherited from legal entity	Selectable employer for work relationships	TechNova India Pvt Ltd	Creating a separate employer record without a legal entity
Employer classification date Date-effective	First date employment can use the classification	Approved operating date	Starting after worker hire dates
Position synchronization override Inheriteddownstream-sensitive	Can refine enterprise behavior where supported	Use enterprise default	Assuming all position attributes synchronize
Employment defaults Tenant-dependent	Controls configured employer-level behavior	Country-approved defaults	Copying settings from another country

5UI Configuration Walkthrough

Open the existing legal entity.
Enable and date the Legal Employer classification.
Review country and employer-level HCM settings.
Create a test work relationship and confirm payroll, assignment and security behavior.

6HDL, HSDL and REST Availability

Method	Status	Best use
Manual UI	Supported	Create and maintain classification
Worker HDL	Supported downstream	Worker loads reference the Legal Employer after setup
HSDL	Supported by worker templates	Not the creation mechanism for the employer
REST	Supported downstream	Worker REST resources reference a valid employer

Before production: Download the current business-object template or inspect current REST metadata. Release, feature and privilege differences can change supported attributes.

7Sample Data Load with Explanation

WORKER LOAD DEPENDENCY
LegalEmployerName=TechNova India Pvt Ltd
WorkerType=Employee
StartDate=<effective date>
Rule: Legal Employer must exist and be effective before the work relationship

The Legal Employer is normally referenced by worker loads; it is not created inside the worker file.

Source-key ruleKeep SourceSystemOwner and SourceSystemId stable so later MERGE operations update the same record.

Dependency ruleLoad and validate referenced parent records before dependent objects.

8Effective Dating and Maintenance Rules

Do not end-date a Legal Employer while active or future work relationships depend on it.
A transfer to another Legal Employer crosses a work-relationship boundary.
A location or department change within the same employer is not a global transfer.
Preserve employer history for statutory, service and reporting purposes.

Create

→

Correct an error

→

Update from a date

→

Inactivate safely

9Security and Required Privileges

Users require both functional access to employment transactions and data access to the relevant Legal Employer population. Failure to see workers can be security-related even when the employer setup is correct.

Diagnostic rule: Separate three questions: Can the user open the function? Can the user maintain this object? Can the user see the relevant secured data?

10Downstream Impact

Work relationshipsDefines who employs the worker

TransfersEmployer change drives global-transfer behavior

SecurityOften participates in worker data access profiles

Assess current records, future-dated transactions, reports, approvals and integrations before changing a production value.

11Validation Checklist

Classification starts before first hire
Test user can select the employer
Work relationship is created under the correct company
Country and payroll defaults are consistent
Security population includes the intended employer

12Troubleshooting Scenarios

Symptom	Likely cause	What to do
Employer not selectable	Classification inactive or future-dated	Review classification status and start date
User cannot see employer workers	Data role excludes Legal Employer	Review security profile and role assignment
Simple move creates new relationship	Location/department change misread as employer change	Use the appropriate assignment transaction

13Technical Consultant Challenge

Priya moves from Bengaluru to Delhi but remains employed by TechNova India Pvt Ltd. What should you do?

Consultant answer

Keep the same work relationship. Process the location or assignment change; do not perform a Legal Employer transfer unless the employing registered organization actually changes.

Certification

Legal framework

Legal Employer

Who legally employs the worker?

Certification trap

Watch for this: Location answers where work occurs; Legal Employer answers who employs.

How to reason through a scenario

Underline the business question.
Identify the layer: legal, operational, workforce, or control.
Remove options that answer a different business question.
Check effective date, reuse, sharing and dependency clues.
Choose the solution that preserves history and avoids duplication.

Revision

Legal framework

Legal Employer

Who legally employs the worker?

30-second revision

Legal Employer
A Legal Employer is a Legal Entity classification for an organization that employs workers.

Example: TechNova India Pvt Ltd
Main trap: Location answers where work occurs; Legal Employer answers who employs.

Active recall

Who legally employs the worker?
Which objects depend on or use Legal Employer?
What must exist before it is configured?
Which date, status or sharing controls matter?
What configuration mistake would you warn the client about?

Lesson 04

Legislative Data Group

How is payroll-related legislative data partitioned?

Fundamentals

Legal framework

Legislative Data Group

How is payroll-related legislative data partitioned?

TechNova story · The legislation boundary

Legislative Data Group: learn it through a business decision

TechNova is designing payroll-related information for India and Singapore. The team wants one global container because both countries use the same corporate HR policies.

First principle: A Legislative Data Group (LDG) partitions payroll and related data for a country or legislation.

Pause, decide, then reveal the reasoning

Answer in your own words before opening each explanation.

Question 1 Can corporate policy replace legislative partitioning?

Answer: No. Legislative Data Groups partition payroll and related data by legislation.

Why: Corporate policy may be global, but payroll and statutory rules operate within country-specific legislative contexts.

Question 2 Does an LDG employ workers?

Answer: No. The Legal Employer employs workers.

Why: An LDG is a legislative data partition, not an employing organization or workplace.

Question 3 Why does payroll configuration refer to an LDG?

Answer: It gives payroll-related objects and processing the relevant legislative context and data boundary.

Why: Without that context, country-specific statutory data could be mixed or applied incorrectly.

Question 4 What must be reviewed before adding another LDG?

Answer: The country/legislation, payroll partitioning requirement and relationship to payroll statutory structures.

Why: Do not create LDGs simply to mirror departments or business lines.

If the business changes…When TechNova enters a new country, reassess legislative and payroll structures. When it adds a department in the same legislation, an LDG change is normally irrelevant.

Simple mental pictureLDG answers 'under which legislation is payroll-related data partitioned?'—not 'who employs?'

What does Legislative Data Group do in Oracle?

Associated with a legislation/country
Related to payroll statutory structures
Used by payroll-related configuration and processing

Why is it useful, and when do consultants use it?

Why the business needs it

It provides the legislative context for payroll-related information while supporting appropriate data separation.

Country/legislation context
Partitions payroll-related data
Supports statutory processing

When it is used

Country and payroll statutory design must be known.

Typical setup task:
Setup and Maintenance → Manage Legislative Data Groups

Important distinction

Legislative Data Group
How is payroll-related legislative data partitioned?

Do not confuse

An LDG is not a Legal Employer and does not itself employ workers.

How a consultant reasons

Read the business factsIdentify the questionChoose the objectCheck dependenciesTest the impact

Easy exam definition

A Legislative Data Group (LDG) partitions payroll and related data for a country or legislation.

Memory line: LDG answers 'under which legislation is payroll-related data partitioned?'—not 'who employs?'

Connect it to the TechNova design

Business questionHow is payroll-related legislative data partitioned?

TechNova recordTechNova India LDG

Why it existsIt provides the legislative context for payroll-related information while supporting appropriate data separation.

Certification trapAn LDG is not a Legal Employer and does not itself employ workers.

Check your understanding

Country/legislation context
Partitions payroll-related data
Supports statutory processing
Not an organizational team
Coordinate with payroll design

Relationships

Legal framework

Legislative Data Group

How is payroll-related legislative data partitioned?

Relationship map

Enterprise

→

Legal & operational structures

→

Legislative Data Group

→

Worker assignment

Direct relationships

Associated with a legislation/country
Related to payroll statutory structures
Used by payroll-related configuration and processing

Think like a consultant: Identify whether the requirement changes the legal, operational, workforce, or sharing layer before creating or editing this object.

Implementation

Legal framework

Legislative Data Group

How is payroll-related legislative data partitioned?

Implementation purpose

It provides the legislative context for payroll-related information while supporting appropriate data separation.

Typical setup route

Setup and Maintenance → Manage Legislative Data Groups
Navigation and page names can vary with enabled Redwood experiences and quarterly updates. Learn the setup task and outcome.

Prerequisites

Country and payroll statutory design must be known.

Implementation checklist

Confirm the business owner and exact requirement.
Check whether an existing record can be reused.
Agree naming, codes, effective dates and sharing.
Configure in a test environment.
Validate transactions, security, reporting and integrations.
Document the design decision and migration method.

Technical Details

Legal framework

Legislative Data Group

How is payroll-related legislative data partitioned?

Consultant workspace

Legislative Data Group Technical Details

Configure, migrate, maintain, validate and troubleshoot this object.

Primary technical question

How is payroll-related legislative data partitioned?

Effective setup aligned to country operationsSet-enabled: No

1Technical Profile

Oracle role in design	Country legislation and payroll-data partition
Date behavior	Effective setup aligned to country operations
Set-enabled	No
Main setup task	Manage Legislative Data Groups
Main migration approach	Core legislative setup; create before payroll-dependent data and worker payroll relationships
Used by	Associated with a legislation/country; Related to payroll statutory structures; Used by payroll-related configuration and processing

3Prerequisites and Configuration Sequence

Country legislation in scope
Enterprise and payroll implementation strategy
PSU and payroll statutory-reporting design

Sequence rule: Complete dependencies and approve stable codes before creating or loading Legislative Data Group.

4Field Dictionary

Field	What it controls	TechNova example	Common mistake
Name Required	Identifies the legislative partition	TechNova India LDG	Using a global name that hides the country
Country Requiredcountry-controlled	Determines legislation	India	Combining different legislations
Currency Country-sensitive	Supports payroll context where applicable	INR	Assuming enterprise currency is sufficient
Related statutory structures Downstream-sensitive	Links payroll data to the correct country design	TechNova India PSU	Linking a PSU from another legislative design

5UI Configuration Walkthrough

Confirm the country legislation and payroll scope.
Create the LDG with a governed name and country.
Associate the correct statutory structures and defaults required by payroll design.
Validate that payroll-related records resolve within the intended LDG.

6HDL, HSDL and REST Availability

Method	Status	Best use
Manual UI	Supported	Primary setup route
FSM migration	Check support	Move supported setup data
HDL	Not a routine workforce load	Create LDG before worker/payroll files reference it
REST	Check current metadata	Do not assume maintenance support

Before production: Download the current business-object template or inspect current REST metadata. Release, feature and privilege differences can change supported attributes.

7Sample Data Load with Explanation

LDG DESIGN
Name: TechNova India LDG
Country: India
Currency: INR
Boundary: India payroll and legislative data only

An LDG is country-specific. It is a prerequisite boundary, not a shared global container for different legislations.

Source-key ruleKeep SourceSystemOwner and SourceSystemId stable so later MERGE operations update the same record.

Dependency ruleLoad and validate referenced parent records before dependent objects.

8Effective Dating and Maintenance Rules

Create a separate LDG when a different country legislation requires it.
Do not repurpose an in-use LDG for another country.
Review payroll calendars, elements and statutory records before changing associations.
Preserve history and test country-specific processing after dated changes.

Create

→

Correct an error

→

Update from a date

→

Inactivate safely

9Security and Required Privileges

Payroll and legislative setup commonly needs specialist privileges. Access to general HR transactions does not automatically provide access to LDG-scoped payroll information.

Diagnostic rule: Separate three questions: Can the user open the function? Can the user maintain this object? Can the user see the relevant secured data?

10Downstream Impact

PayrollPartitions legislative and payroll data

Statutory reportingKeeps country-specific obligations separate

IntegrationsProvides a legislative context for payroll interfaces

Assess current records, future-dated transactions, reports, approvals and integrations before changing a production value.

11Validation Checklist

Country matches the payroll population
PSU association is correct
Currency and country defaults are reviewed
Payroll users have LDG access
Test payroll records resolve in the intended partition

12Troubleshooting Scenarios

Symptom	Likely cause	What to do
Payroll value not available	Record belongs to another LDG	Review legislative context and associations
Two countries share one LDG	Country boundary misunderstood	Create country-specific LDGs
User cannot access payroll setup	Role lacks LDG/payroll privileges	Review payroll data access

13Technical Consultant Challenge

TechNova wants India and Singapore payroll data in one LDG because corporate policies are global. What should you do?

Consultant answer

Use separate LDGs because the governing legislation differs. Share corporate policies through appropriate configuration, not by collapsing statutory country boundaries.

Certification

Legal framework

Legislative Data Group

How is payroll-related legislative data partitioned?

Certification trap

Watch for this: An LDG is not a Legal Employer and does not itself employ workers.

How to reason through a scenario

Underline the business question.
Identify the layer: legal, operational, workforce, or control.
Remove options that answer a different business question.
Check effective date, reuse, sharing and dependency clues.
Choose the solution that preserves history and avoids duplication.

Revision

Legal framework

Legislative Data Group

How is payroll-related legislative data partitioned?

30-second revision

Legislative Data Group
A Legislative Data Group (LDG) partitions payroll and related data for a country or legislation.

Example: TechNova India LDG
Main trap: An LDG is not a Legal Employer and does not itself employ workers.

Active recall

How is payroll-related legislative data partitioned?
Which objects depend on or use Legislative Data Group?
What must exist before it is configured?
Which date, status or sharing controls matter?
What configuration mistake would you warn the client about?

Lesson 05

Payroll Statutory Unit

Which legal entity is responsible for payroll statutory reporting?

Fundamentals

Legal framework

Payroll Statutory Unit

Which legal entity is responsible for payroll statutory reporting?

TechNova story · Who reports payroll to the authorities?

Payroll Statutory Unit: learn it through a business decision

TechNova India employs workers and must report payroll taxes and statutory information. The same registered company may perform both employment and payroll-reporting responsibilities.

First principle: A Payroll Statutory Unit (PSU) is a Legal Entity classification representing the organization responsible for payroll tax and statutory reporting.

Pause, decide, then reveal the reasoning

Answer in your own words before opening each explanation.

Question 1 Which classification identifies statutory payroll responsibility?

Answer: Payroll Statutory Unit.

Why: The PSU represents the Legal Entity responsible for payroll tax and statutory reporting.

Question 2 If the same company is also the Legal Employer, are the terms interchangeable?

Answer: No. One Legal Entity may carry both classifications, but each classification answers a different question.

Why: Legal Employer owns employment relationships; PSU owns payroll statutory responsibility.

Question 3 Must there always be one PSU for every Legal Employer?

Answer: Not as a universal design rule.

Why: Country legislation and the organization's statutory reporting structure determine the relationship. A PSU can support one or more Legal Employers where the design permits.

Question 4 What evidence should a consultant obtain?

Answer: Registrations, statutory reporting responsibilities, effective dates and the relationship to the relevant employers and payroll structures.

Why: A familiar company name is not enough evidence for a statutory design.

If the business changes…A new department or office does not create a PSU. A change in the legal organization responsible for statutory payroll reporting may.

Simple mental picturePSU is a legal classification for payroll reporting responsibility; it is not the employing relationship.

What does Payroll Statutory Unit do in Oracle?

Is a classified Legal Entity
Works with payroll statutory structures
Can serve one or more legal employers according to design

Why is it useful, and when do consultants use it?

Why the business needs it

It establishes the legal payroll reporting responsibility.

Legal Entity classification
Payroll statutory responsibility
Not necessarily one-to-one with employer

When it is used

Legal Entity and payroll statutory requirements.

Typical setup task:
Setup and Maintenance → Manage Legal Entity → Payroll Statutory Unit classification

Important distinction

Payroll Statutory Unit
Which legal entity is responsible for payroll statutory reporting?

Do not confuse

PSU and Legal Employer may be the same legal entity, but they answer different responsibilities.

How a consultant reasons

Read the business factsIdentify the questionChoose the objectCheck dependenciesTest the impact

Easy exam definition

A Payroll Statutory Unit (PSU) is a Legal Entity classification representing the organization responsible for payroll tax and statutory reporting.

Memory line: PSU is a legal classification for payroll reporting responsibility; it is not the employing relationship.

Connect it to the TechNova design

Business questionWhich legal entity is responsible for payroll statutory reporting?

TechNova recordTechNova India PSU

Why it existsIt establishes the legal payroll reporting responsibility.

Certification trapPSU and Legal Employer may be the same legal entity, but they answer different responsibilities.

Check your understanding

Legal Entity classification
Payroll statutory responsibility
Not necessarily one-to-one with employer
Country rules drive design
Coordinate with payroll implementation

Relationships

Legal framework

Payroll Statutory Unit

Which legal entity is responsible for payroll statutory reporting?

Relationship map

Enterprise

→

Legal & operational structures

→

Payroll Statutory Unit

→

Worker assignment

Direct relationships

Is a classified Legal Entity
Works with payroll statutory structures
Can serve one or more legal employers according to design

Think like a consultant: Identify whether the requirement changes the legal, operational, workforce, or sharing layer before creating or editing this object.

Implementation

Legal framework

Payroll Statutory Unit

Which legal entity is responsible for payroll statutory reporting?

Implementation purpose

It establishes the legal payroll reporting responsibility.

Typical setup route

Setup and Maintenance → Manage Legal Entity → Payroll Statutory Unit classification
Navigation and page names can vary with enabled Redwood experiences and quarterly updates. Learn the setup task and outcome.

Prerequisites

Legal Entity and payroll statutory requirements.

Implementation checklist

Confirm the business owner and exact requirement.
Check whether an existing record can be reused.
Agree naming, codes, effective dates and sharing.
Configure in a test environment.
Validate transactions, security, reporting and integrations.
Document the design decision and migration method.

Technical Details

Legal framework

Payroll Statutory Unit

Which legal entity is responsible for payroll statutory reporting?

Consultant workspace

Payroll Statutory Unit Technical Details

Configure, migrate, maintain, validate and troubleshoot this object.

Primary technical question

Which legal entity is responsible for payroll statutory reporting?

Effective classification and registrationsSet-enabled: No

1Technical Profile

Oracle role in design	Legal Entity classification for payroll statutory responsibility
Date behavior	Effective classification and registrations
Set-enabled	No
Main setup task	Manage Legal Entity
Main migration approach	Governed legal/payroll setup; complete before payroll relationships and statutory records
Used by	Is a classified Legal Entity; Works with payroll statutory structures; Can serve one or more legal employers according to design

3Prerequisites and Configuration Sequence

Existing Legal Entity
Country payroll and tax-reporting obligations
LDG, registrations and Legal Employer-to-PSU design

Sequence rule: Complete dependencies and approve stable codes before creating or loading Payroll Statutory Unit.

4Field Dictionary

Field	What it controls	TechNova example	Common mistake
PSU classification Required for design	Marks the reporting organization	TechNova India PSU	Assuming every employer needs a separate PSU
Registration details Country-controlled	Supports statutory reporting	Country-issued identifiers	Using internal codes as statutory registrations
Effective dates Date-effective	Controls when PSU is usable	First payroll operating date	Starting after payroll relationship dates
Employer association Downstream-sensitive	Determines which employment population reports through the PSU	TechNova India Legal Employer	Cross-country association

5UI Configuration Walkthrough

Confirm which registered organization is responsible to authorities.
Add the PSU classification to the correct Legal Entity.
Enter required registrations and connect the payroll design.
Validate payroll relationships and statutory reporting in the target LDG.

6HDL, HSDL and REST Availability

Method	Status	Best use
Manual UI	Supported	Primary legal/payroll setup
FSM migration	Check support	Move supported configuration
HDL	Not primary	Payroll worker files reference completed setup
REST	Check current metadata	Statutory setup is privilege sensitive

Before production: Download the current business-object template or inspect current REST metadata. Release, feature and privilege differences can change supported attributes.

7Sample Data Load with Explanation

PSU DESIGN
Legal Entity: TechNova India Pvt Ltd
Classification: Payroll Statutory Unit
LDG: TechNova India LDG
Responsibility: India payroll statutory reporting

The PSU may be the same Legal Entity that is also the Legal Employer. The classifications still answer different questions.

Source-key ruleKeep SourceSystemOwner and SourceSystemId stable so later MERGE operations update the same record.

Dependency ruleLoad and validate referenced parent records before dependent objects.

8Effective Dating and Maintenance Rules

Do not end-date a PSU while payroll relationships or reporting periods depend on it.
Add registrations through the country-supported setup rather than free-text substitutes.
Treat mergers or employer realignment as controlled payroll conversion events.
Preserve reporting history after statutory reorganization.

Create

→

Correct an error

→

Update from a date

→

Inactivate safely

9Security and Required Privileges

PSU and payroll-registration maintenance requires payroll setup authority. Worker data access alone is insufficient.

Diagnostic rule: Separate three questions: Can the user open the function? Can the user maintain this object? Can the user see the relevant secured data?

10Downstream Impact

Payroll relationshipsProvides statutory reporting context

Tax reportingOwns applicable registrations and obligations

AuditsSupports traceable employer-to-reporting-unit design

Assess current records, future-dated transactions, reports, approvals and integrations before changing a production value.

11Validation Checklist

PSU matches legal evidence
Registrations are valid
LDG and employer associations are correct
Payroll relationship can be created
Statutory outputs identify the expected reporting unit

12Troubleshooting Scenarios

Symptom	Likely cause	What to do
Payroll relationship error	PSU/LDG association incomplete	Review statutory setup sequence
Incorrect reporting organization	Wrong entity classified as PSU	Reconcile with legal responsibility
Duplicate PSU design	One PSU created per internal BU	Return to statutory evidence, not operations chart

13Technical Consultant Challenge

Software BU and Cloud Services BU use the same employing company and statutory registration. A designer proposes one PSU per BU. What should you do?

Consultant answer

Do not mirror BUs as PSUs. Use the statutory organization required by law; operational transaction units do not create separate payroll-reporting responsibilities by themselves.

Certification

Legal framework

Payroll Statutory Unit

Which legal entity is responsible for payroll statutory reporting?

Certification trap

Watch for this: PSU and Legal Employer may be the same legal entity, but they answer different responsibilities.

How to reason through a scenario

Underline the business question.
Identify the layer: legal, operational, workforce, or control.
Remove options that answer a different business question.
Check effective date, reuse, sharing and dependency clues.
Choose the solution that preserves history and avoids duplication.

Revision

Legal framework

Payroll Statutory Unit

Which legal entity is responsible for payroll statutory reporting?

30-second revision

Payroll Statutory Unit
A Payroll Statutory Unit (PSU) is a Legal Entity classification representing the organization responsible for payroll tax and statutory reporting.

Example: TechNova India PSU
Main trap: PSU and Legal Employer may be the same legal entity, but they answer different responsibilities.

Active recall

Which legal entity is responsible for payroll statutory reporting?
Which objects depend on or use Payroll Statutory Unit?
What must exist before it is configured?
Which date, status or sharing controls matter?
What configuration mistake would you warn the client about?

Lesson 06

Business Unit

Which operational unit processes business transactions?

Fundamentals

Operational structure

Business Unit

Which operational unit processes business transactions?

TechNova story · Who runs the operation?

Business Unit: learn it through a business decision

TechNova India has Software, Cloud Services and Consulting operations. They share one employer, but management needs distinct transaction-processing and operational contexts.

First principle: A Business Unit represents an operational segment that performs business functions and processes transactions.

Pause, decide, then reveal the reasoning

Answer in your own words before opening each explanation.

Question 1 Should each operation become a Legal Entity?

Answer: Not unless it is separately registered and carries distinct legal responsibilities.

Why: Operational separation is commonly modeled with Business Units; legal registration is modeled with Legal Entities.

Question 2 What does Software BU answer on Priya's assignment?

Answer: Which operational unit provides the business-processing context for her assignment.

Why: It does not tell us who legally employs her or where she physically works.

Question 3 Why is Reference Data Set design discussed with Business Units?

Answer: Set assignments determine which shared reference values a BU can use for particular reference-data groups.

Why: A correct Job or Department can still be invisible if its set is not available in the BU's context.

Question 4 TechNova adds a new product team inside Software BU. Is another BU automatically required?

Answer: No. First determine whether the need is a Department, Division or reporting hierarchy rather than a new transaction-processing unit.

Why: Create a BU only when the operating model and transaction responsibilities require it.

If the business changes…Changing BU can alter operational processing and value availability, but it does not by itself mean the Legal Employer changed.

Simple mental pictureBusiness Unit is operational; Legal Entity is legal; Department is the team doing the work.

What does Business Unit do in Oracle?

Associated with enterprise/legal structures as designed
Uses Reference Data Sets
Appears on worker assignments

Why is it useful, and when do consultants use it?

Why the business needs it

It provides transaction-processing context and participates in reference-data sharing.

Operational transaction unit
Can be on assignments
Uses reference-data sets

When it is used

Enterprise structure and reference-data strategy.

Typical setup task:
Setup and Maintenance → Manage Business Unit

Important distinction

Business Unit
Which operational unit processes business transactions?

Do not confuse

A Business Unit is not necessarily a registered company and is not the Legal Employer.

How a consultant reasons

Read the business factsIdentify the questionChoose the objectCheck dependenciesTest the impact

Easy exam definition

A Business Unit represents an operational segment that performs business functions and processes transactions.

Memory line: Business Unit is operational; Legal Entity is legal; Department is the team doing the work.

Connect it to the TechNova design

Business questionWhich operational unit processes business transactions?

TechNova recordSoftware BU

Why it existsIt provides transaction-processing context and participates in reference-data sharing.

Certification trapA Business Unit is not necessarily a registered company and is not the Legal Employer.

Check your understanding

Operational transaction unit
Can be on assignments
Uses reference-data sets
May support multiple business functions
Not a legal organization by definition

Relationships

Operational structure

Business Unit

Which operational unit processes business transactions?

Relationship map

Enterprise

→

Legal & operational structures

→

Business Unit

→

Worker assignment

Direct relationships

Associated with enterprise/legal structures as designed
Uses Reference Data Sets
Appears on worker assignments

Think like a consultant: Identify whether the requirement changes the legal, operational, workforce, or sharing layer before creating or editing this object.

Implementation

Operational structure

Business Unit

Which operational unit processes business transactions?

Implementation purpose

It provides transaction-processing context and participates in reference-data sharing.

Typical setup route

Setup and Maintenance → Manage Business Unit
Navigation and page names can vary with enabled Redwood experiences and quarterly updates. Learn the setup task and outcome.

Prerequisites

Enterprise structure and reference-data strategy.

Implementation checklist

Confirm the business owner and exact requirement.
Check whether an existing record can be reused.
Agree naming, codes, effective dates and sharing.
Configure in a test environment.
Validate transactions, security, reporting and integrations.
Document the design decision and migration method.

Technical Details

Operational structure

Business Unit

Which operational unit processes business transactions?

Consultant workspace

Business Unit Technical Details

Configure, migrate, maintain, validate and troubleshoot this object.

Primary technical question

Which operational unit processes business transactions?

Effective setupSet-enabled: No; consumes set assignments

1Technical Profile

Oracle role in design	Operational transaction-processing organization
Date behavior	Effective setup
Set-enabled	No; consumes set assignments
Main setup task	Manage Business Unit / Manage Business Unit Set Assignment
Main migration approach	Controlled setup object; complete BU and set assignments before loading BU-dependent records
Used by	Associated with enterprise/legal structures as designed; Uses Reference Data Sets; Appears on worker assignments

3Prerequisites and Configuration Sequence

Approved operating model and business functions
Enterprise/legal alignment where required
Reference Data Set strategy and default set

Sequence rule: Complete dependencies and approve stable codes before creating or loading Business Unit.

4Field Dictionary

Field	What it controls	TechNova example	Common mistake
Name and short code Requiredintegration-sensitive	Identifies operational context	Software BU / SWBU	Changing the code to match a new manager
Default set Requireddownstream-sensitive	Controls default reference-data sharing	TechNova Common Set	Assuming it grants data security
Business functions Scoped setup	Enables transaction responsibilities	HR and project functions as designed	Enabling every function without requirement
Effective status Date-effective	Controls use in transactions	Active from operating date	Future-dating after dependent records

5UI Configuration Walkthrough

Confirm why the BU is needed and which transactions it processes.
Create the BU with governed name, code and effective date.
Assign business functions and reference-data sets by group.
Test hire and other relevant transactions using the BU context.

6HDL, HSDL and REST Availability

Method	Status	Best use
Manual UI	Supported	Primary setup route
FSM migration	Check setup support	Promote governed setup
HDL	Not primary	Dependent records can reference the BU
REST	Check current resource	Transaction APIs may consume BU values

Before production: Download the current business-object template or inspect current REST metadata. Release, feature and privilege differences can change supported attributes.

7Sample Data Load with Explanation

BUSINESS UNIT DESIGN
Name: Software BU
Short code: SWBU
Default set: TechNova Common Set
Functions: only approved operational functions

Finish set assignments before loading set-enabled Jobs, Locations or Departments that users must select in the BU context.

Source-key ruleKeep SourceSystemOwner and SourceSystemId stable so later MERGE operations update the same record.

Dependency ruleLoad and validate referenced parent records before dependent objects.

8Effective Dating and Maintenance Rules

Do not inactivate a BU with active/future assignments or transactions without a transition plan.
A management reorganization does not always require a new BU.
Change set assignments only after impact-testing all reference-data groups.
Keep the short code stable for reports and integrations.

Create

→

Correct an error

→

Update from a date

→

Inactivate safely

9Security and Required Privileges

A BU can be part of data-access profiles, but BU setup and user security are separate controls. A value shared to a BU can still be hidden by security.

Diagnostic rule: Separate three questions: Can the user open the function? Can the user maintain this object? Can the user see the relevant secured data?

10Downstream Impact

AssignmentsProvides operational context

Reference dataConsumes set-enabled Jobs, Grades, Locations and organizations

TransactionsScopes enabled business functions

Assess current records, future-dated transactions, reports, approvals and integrations before changing a production value.

11Validation Checklist

Business purpose is documented
Short code is unique and stable
Functions match requirements
Set assignments expose intended values
Hire and reporting use the expected BU

12Troubleshooting Scenarios

Symptom	Likely cause	What to do
Reference value missing	Incorrect set assignment for data group	Review BU set assignments
BU absent in transaction	Inactive/date mismatch or security	Check date, status and access
Duplicate BU proposed	Department or division requirement misunderstood	Reconfirm transaction-processing need

13Technical Consultant Challenge

Consulting BU cannot see Software Engineer, but the Job exists and is active. What should you do?

Consultant answer

Check the Job's set and the Consulting BU set assignment for the Job reference-data group before creating a duplicate Job. Then check security and transaction date.

Certification

Operational structure

Business Unit

Which operational unit processes business transactions?

Certification trap

Watch for this: A Business Unit is not necessarily a registered company and is not the Legal Employer.

How to reason through a scenario

Underline the business question.
Identify the layer: legal, operational, workforce, or control.
Remove options that answer a different business question.
Check effective date, reuse, sharing and dependency clues.
Choose the solution that preserves history and avoids duplication.

Revision

Operational structure

Business Unit

Which operational unit processes business transactions?

30-second revision

Business Unit
A Business Unit represents an operational segment that performs business functions and processes transactions.

Example: Software BU
Main trap: A Business Unit is not necessarily a registered company and is not the Legal Employer.

Active recall

Which operational unit processes business transactions?
Which objects depend on or use Business Unit?
What must exist before it is configured?
Which date, status or sharing controls matter?
What configuration mistake would you warn the client about?

Lesson 07

Division

How can a major line of business be represented for management reporting?

Fundamentals

Operational structure

Division

How can a major line of business be represented for management reporting?

TechNova story · The management lens

Division: learn it through a business decision

TechNova wants to report Software and Cloud Services as major product lines, but both use the same Legal Employer and some shared Business Units.

First principle: A Division can represent a major product line, geography or business segment for managerial and reporting purposes.

Pause, decide, then reveal the reasoning

Answer in your own words before opening each explanation.

Question 1 Which object can represent the product-line management view?

Answer: A Division can represent a major line of business for management and reporting.

Why: Its purpose is organizational analysis, not legal registration or employment ownership.

Question 2 Does a Division process transactions like a Business Unit?

Answer: Not merely because it is a Division.

Why: Business Unit is the operational transaction context; Division is commonly a management/reporting dimension.

Question 3 Can a Division appear in an organization hierarchy?

Answer: Yes, it can group related organizational activity in a hierarchy.

Why: The hierarchy shows relationships; it does not convert the Division into a Legal Entity or BU.

Question 4 Should every executive title result in a new Division?

Answer: No. The consultant should confirm a durable reporting or organizational requirement.

Why: Unnecessary Divisions make structures harder to govern and explain.

If the business changes…If management reorganizes product lines, consider effective hierarchy and reporting impacts without automatically changing worker Legal Employers or Locations.

Simple mental pictureDivision is an optional management structure; use it for a real reporting purpose, not as a substitute for BU.

What does Division do in Oracle?

Can sit in organization hierarchies
May group departments or business activity
Does not replace legal or employment structures

Why is it useful, and when do consultants use it?

Why the business needs it

It gives an additional organizational reporting dimension when the enterprise needs it.

Management/reporting structure
Optional based on design
Can appear in hierarchies

When it is used

Reporting and organization-design requirements.

Typical setup task:
Setup and Maintenance → Manage Divisions / Manage Organizations

Important distinction

Division
How can a major line of business be represented for management reporting?

Do not confuse

Do not create Divisions when the requirement is actually a transaction-processing Business Unit.

How a consultant reasons

Read the business factsIdentify the questionChoose the objectCheck dependenciesTest the impact

Easy exam definition

A Division can represent a major product line, geography or business segment for managerial and reporting purposes.

Memory line: Division is an optional management structure; use it for a real reporting purpose, not as a substitute for BU.

Connect it to the TechNova design

Business questionHow can a major line of business be represented for management reporting?

TechNova recordCloud Services Division

Why it existsIt gives an additional organizational reporting dimension when the enterprise needs it.

Certification trapDo not create Divisions when the requirement is actually a transaction-processing Business Unit.

Check your understanding

Management/reporting structure
Optional based on design
Can appear in hierarchies
Not a Legal Entity
Purpose must be documented

Relationships

Operational structure

Division

How can a major line of business be represented for management reporting?

Relationship map

Enterprise

→

Legal & operational structures

→

Division

→

Worker assignment

Direct relationships

Can sit in organization hierarchies
May group departments or business activity
Does not replace legal or employment structures

Think like a consultant: Identify whether the requirement changes the legal, operational, workforce, or sharing layer before creating or editing this object.

Implementation

Operational structure

Division

How can a major line of business be represented for management reporting?

Implementation purpose

It gives an additional organizational reporting dimension when the enterprise needs it.

Typical setup route

Setup and Maintenance → Manage Divisions / Manage Organizations
Navigation and page names can vary with enabled Redwood experiences and quarterly updates. Learn the setup task and outcome.

Prerequisites

Reporting and organization-design requirements.

Implementation checklist

Confirm the business owner and exact requirement.
Check whether an existing record can be reused.
Agree naming, codes, effective dates and sharing.
Configure in a test environment.
Validate transactions, security, reporting and integrations.
Document the design decision and migration method.

Technical Details

Operational structure

Division

How can a major line of business be represented for management reporting?

Consultant workspace

Division Technical Details

Configure, migrate, maintain, validate and troubleshoot this object.

Primary technical question

How can a major line of business be represented for management reporting?

Date-effective organization classificationSet-enabled: Design-dependent

1Technical Profile

Oracle role in design	Optional management/reporting organization
Date behavior	Date-effective organization classification
Set-enabled	Design-dependent
Main setup task	Manage Divisions / Manage Organizations
Main migration approach	Organization.dat when the current HDL template supports the required classification
Used by	Can sit in organization hierarchies; May group departments or business activity; Does not replace legal or employment structures

3Prerequisites and Configuration Sequence

Documented management-reporting need
Organization hierarchy design
Reference Data Set decision where applicable

Sequence rule: Complete dependencies and approve stable codes before creating or loading Division.

4Field Dictionary

Field	What it controls	TechNova example	Common mistake
Name Required	Business-oriented subdivision	Cloud Services Division	Using a legal-company name
Code Integration-sensitive	Stable reporting identifier	DIV-CLOUD	Changing it during rebranding
Classification Required	Identifies the record as Division	Division	Creating an unclassified organization
Effective dates Date-effective	Controls hierarchy and reporting availability	Approved operating date	Predating the classification incorrectly

5UI Configuration Walkthrough

Confirm that the requirement is a management segment, not a BU or Legal Entity.
Create the organization with Division classification.
Place it in the approved organization-tree version.
Validate reporting without changing legal or transaction processing.

6HDL, HSDL and REST Availability

Method	Status	Best use
Manual UI	Supported	Small-volume setup
HDL	Supported when exposed	Organization.dat plus classification component
HSDL	Check template	Use only if Division is exposed
REST	Check current organization resource	Validate classification support

Before production: Download the current business-object template or inspect current REST metadata. Release, feature and privilege differences can change supported attributes.

7Sample Data Load with Explanation

METADATA|Organization|SourceSystemOwner|SourceSystemId|Name|EffectiveStartDate
MERGE|Organization|EXAMNXT|DIV_CLOUD|Cloud Services Division|<start date>
METADATA|OrgUnitClassification|SourceSystemOwner|SourceSystemId|OrganizationId(SourceSystemId)|ClassificationCode
MERGE|OrgUnitClassification|EXAMNXT|DIV_CLOUD_CLASS|DIV_CLOUD|<division classification code>

Use the current Organization business-object template to confirm classification codes and required keys before loading.

Source-key ruleKeep SourceSystemOwner and SourceSystemId stable so later MERGE operations update the same record.

Dependency ruleLoad and validate referenced parent records before dependent objects.

8Effective Dating and Maintenance Rules

Classification cannot predate the organization.
Use dated tree versions for hierarchy changes.
Inactivate rather than delete an in-use organization.
Changing the Division does not automatically change BUs, employers or departments.

Create

→

Correct an error

→

Update from a date

→

Inactivate safely

9Security and Required Privileges

Division may support reporting or security structures when configured, but a hierarchy node does not itself grant access. Maintain organization and tree privileges separately.

Diagnostic rule: Separate three questions: Can the user open the function? Can the user maintain this object? Can the user see the relevant secured data?

10Downstream Impact

ReportingManagement-segment analysis

TreesParent/child organization views

SecurityMay participate in configured organization profiles

Assess current records, future-dated transactions, reports, approvals and integrations before changing a production value.

11Validation Checklist

Requirement is truly a Division
Organization and classification dates align
Hierarchy version contains the correct node
Reports group departments as expected
No legal or BU behavior changed unintentionally

12Troubleshooting Scenarios

Symptom	Likely cause	What to do
Division missing in tree	Wrong version/date or node not added	Review active tree version
HDL classification failure	Parent organization missing or wrong key	Load parent before classification
Transactions expected to process through Division	Division confused with BU	Use Business Unit for transaction processing

13Technical Consultant Challenge

TechNova wants profit reporting for Cloud Services but already processes transactions through Software BU. What should you do?

Consultant answer

A Division may provide the management lens if reporting requirements support it; do not replace or duplicate the BU unless transaction processing also changes.

Certification

Operational structure

Division

How can a major line of business be represented for management reporting?

Certification trap

Watch for this: Do not create Divisions when the requirement is actually a transaction-processing Business Unit.

How to reason through a scenario

Underline the business question.
Identify the layer: legal, operational, workforce, or control.
Remove options that answer a different business question.
Check effective date, reuse, sharing and dependency clues.
Choose the solution that preserves history and avoids duplication.

Revision

Operational structure

Division

How can a major line of business be represented for management reporting?

30-second revision

Division
A Division can represent a major product line, geography or business segment for managerial and reporting purposes.

Example: Cloud Services Division
Main trap: Do not create Divisions when the requirement is actually a transaction-processing Business Unit.

Active recall

How can a major line of business be represented for management reporting?
Which objects depend on or use Division?
What must exist before it is configured?
Which date, status or sharing controls matter?
What configuration mistake would you warn the client about?

Lesson 08

Reference Data Set

Which business units can use shared reference data?

Fundamentals

Control & sharing

Reference Data Set

Which business units can use shared reference data?

TechNova story · Why can one user see the Job and another cannot?

Reference Data Set: learn it through a business decision

Software BU can select 'Software Engineer,' but Consulting BU cannot. An implementer is about to create a duplicate Job called 'Software Engineer - Consulting.'

First principle: Reference Data Sets group and share reference data across Business Units.

Pause, decide, then reveal the reasoning

Answer in your own words before opening each explanation.

Question 1 What should be checked before creating the duplicate?

Answer: Check the Job's set, the BU's set assignment for the relevant reference-data group, status and effective date.

Why: Visibility can be a sharing-context problem even when the master-data value already exists.

Question 2 Does the Common Set mean every secured user can automatically see everything?

Answer: No. Set sharing and data security answer different questions.

Why: Reference Data Sets control availability of set-enabled values by BU context; security controls who may access data and functions.

Question 3 Can one BU use Common values for Jobs and a BU-specific set for Departments?

Answer: Yes, where the relevant reference-data groups and set assignments support that design.

Why: Assignments can differ by reference-data group; sharing is not necessarily one all-or-nothing choice.

Question 4 When is a BU-specific value justified?

Answer: When the value is genuinely different and should be restricted to the consuming BU—not merely because a user cannot currently see it.

Why: Poor diagnosis creates duplicates, inconsistent reporting and difficult integrations.

If the business changes…When a value disappears, trace BU context → reference-data group → assigned set → value's set/status/date. Recreate only after proving a genuine business difference.

Simple mental pictureSets control reuse and availability of selected reference data; they do not replace security.

What does Reference Data Set do in Oracle?

Assigned to Business Units by reference-data group
Controls availability of set-enabled objects
Can support common and BU-specific values

Why is it useful, and when do consultants use it?

Why the business needs it

They prevent unnecessary duplication while allowing values to be shared broadly or restricted to selected BUs.

Controls sharing, not security
Common Set enables broad reuse
Assignments can vary by data group

When it is used

BU design and sharing requirements.

Typical setup task:
Setup and Maintenance → Manage Reference Data Sets / Manage Business Unit Set Assignment

Important distinction

Reference Data Set
Which business units can use shared reference data?

Do not confuse

If a value is missing in a transaction, do not recreate it immediately—check set assignment, status and date.

How a consultant reasons

Read the business factsIdentify the questionChoose the objectCheck dependenciesTest the impact

Easy exam definition

Reference Data Sets group and share reference data across Business Units.

Memory line: Sets control reuse and availability of selected reference data; they do not replace security.

Connect it to the TechNova design

Business questionWhich business units can use shared reference data?

TechNova recordTechNova Common Set

Why it existsThey prevent unnecessary duplication while allowing values to be shared broadly or restricted to selected BUs.

Certification trapIf a value is missing in a transaction, do not recreate it immediately—check set assignment, status and date.

Check your understanding

Controls sharing, not security
Common Set enables broad reuse
Assignments can vary by data group
Avoid duplicate master data
Design before loading set-enabled objects

Relationships

Control & sharing

Reference Data Set

Which business units can use shared reference data?

Relationship map

Enterprise

→

Legal & operational structures

→

Reference Data Set

→

Worker assignment

Direct relationships

Assigned to Business Units by reference-data group
Controls availability of set-enabled objects
Can support common and BU-specific values

Think like a consultant: Identify whether the requirement changes the legal, operational, workforce, or sharing layer before creating or editing this object.

Implementation

Control & sharing

Reference Data Set

Which business units can use shared reference data?

Implementation purpose

They prevent unnecessary duplication while allowing values to be shared broadly or restricted to selected BUs.

Typical setup route

Setup and Maintenance → Manage Reference Data Sets / Manage Business Unit Set Assignment
Navigation and page names can vary with enabled Redwood experiences and quarterly updates. Learn the setup task and outcome.

Prerequisites

BU design and sharing requirements.

Implementation checklist

Confirm the business owner and exact requirement.
Check whether an existing record can be reused.
Agree naming, codes, effective dates and sharing.
Configure in a test environment.
Validate transactions, security, reporting and integrations.
Document the design decision and migration method.

Technical Details

Control & sharing

Reference Data Set

Which business units can use shared reference data?

Consultant workspace

Reference Data Set Technical Details

Configure, migrate, maintain, validate and troubleshoot this object.

Primary technical question

Which business units can use shared reference data?

Set memberships and records are effective in their own contextsSet-enabled: This is the sharing mechanism

1Technical Profile

Oracle role in design	Sharing control for set-enabled reference data
Date behavior	Set memberships and records are effective in their own contexts
Set-enabled	This is the sharing mechanism
Main setup task	Manage Reference Data Sets / Manage Business Unit Set Assignment
Main migration approach	Create sets and BU assignments before loading set-enabled records
Used by	Assigned to Business Units by reference-data group; Controls availability of set-enabled objects; Can support common and BU-specific values

3Prerequisites and Configuration Sequence

Business Unit design
Inventory of common versus BU-specific values
Reference-data group mapping and naming convention

Sequence rule: Complete dependencies and approve stable codes before creating or loading Reference Data Set.

4Field Dictionary

Field	What it controls	TechNova example	Common mistake
Set code Requiredintegration-sensitive	Stable key used by integrations and loads	TN_COMMON	Encoding a temporary project phase
Set name Required	User-facing sharing label	TechNova Common Set	Using an unclear generic name
BU assignment Downstream-sensitive	Determines which set supplies a reference-data group	Software BU → TN_COMMON	Assigning only the default set and ignoring groups
Record set code Set-controlled	Places each Job/Location/Department in a set	TN_COMMON	Loading the value into the wrong set

5UI Configuration Walkthrough

Classify each reference-data group as common or BU-specific.
Create governed sets with stable codes.
Assign sets to every BU for the relevant data groups.
Load or create reference records, then test LOV visibility in each BU.

6HDL, HSDL and REST Availability

Method	Status	Best use
Manual UI	Supported	Sets and assignments
HDL	Supported for dependent objects	Pass valid SetCode on set-enabled records
HSDL	Template-dependent	Spreadsheet loads must use the correct set
REST	Resource-dependent	Supply correct reference keys

Before production: Download the current business-object template or inspect current REST metadata. Release, feature and privilege differences can change supported attributes.

7Sample Data Load with Explanation

SHARING DESIGN
Set: TN_COMMON - TechNova Common Set
Software BU / Jobs = TN_COMMON
Consulting BU / Jobs = TN_COMMON
Cloud BU / Locations = TN_CLOUD

The same BU can use different sets for different reference-data groups. Sharing is not the same as user security.

Source-key ruleKeep SourceSystemOwner and SourceSystemId stable so later MERGE operations update the same record.

Dependency ruleLoad and validate referenced parent records before dependent objects.

8Effective Dating and Maintenance Rules

Avoid changing a set code after integrations use it.
Move or recreate set-enabled data only through a planned conversion.
Test all consuming BUs before changing an assignment.
Keep inactive records for history rather than creating uncontrolled duplicates.

Create

→

Correct an error

→

Update from a date

→

Inactivate safely

9Security and Required Privileges

Sets determine availability by BU context; they do not grant a user permission to access a page or secured population. Diagnose sharing and security separately.

Diagnostic rule: Separate three questions: Can the user open the function? Can the user maintain this object? Can the user see the relevant secured data?

10Downstream Impact

LOVsControls which values users can select

LoadsSetCode is a key dependency for set-enabled objects

Data qualityReduces duplicate Jobs, Grades, Locations and organizations

Assess current records, future-dated transactions, reports, approvals and integrations before changing a production value.

11Validation Checklist

Every BU has assignments for required data groups
Common values use the intended common set
BU-specific values are restricted intentionally
LOVs work on the correct transaction date
Security is tested separately from sharing

12Troubleshooting Scenarios

Symptom	Likely cause	What to do
Value missing in one BU	Set assignment mismatch	Trace BU → reference-data group → set
Duplicate master records	New value created instead of fixing sharing	Retire duplicate and correct set strategy
HDL reference error	Invalid or unavailable SetCode	Load set/setup first and use governed code

13Technical Consultant Challenge

A Job is visible in Software BU but not Cloud Services BU. It is active and effective. What should you do?

Consultant answer

Trace its SetCode and the Cloud Services BU assignment for the Jobs reference-data group. Only after sharing is correct should you investigate user security or transaction context.

Certification

Control & sharing

Reference Data Set

Which business units can use shared reference data?

Certification trap

Watch for this: If a value is missing in a transaction, do not recreate it immediately—check set assignment, status and date.

How to reason through a scenario

Underline the business question.
Identify the layer: legal, operational, workforce, or control.
Remove options that answer a different business question.
Check effective date, reuse, sharing and dependency clues.
Choose the solution that preserves history and avoids duplication.

Revision

Control & sharing

Reference Data Set

Which business units can use shared reference data?

30-second revision

Reference Data Set
Reference Data Sets group and share reference data across Business Units.

Example: TechNova Common Set
Main trap: If a value is missing in a transaction, do not recreate it immediately—check set assignment, status and date.

Active recall

Which business units can use shared reference data?
Which objects depend on or use Reference Data Set?
What must exist before it is configured?
Which date, status or sharing controls matter?
What configuration mistake would you warn the client about?

Lesson 09

Position Synchronization

Which position values should flow to assignments?

Fundamentals

Control & sharing

Position Synchronization

Which position values should flow to assignments?

TechNova story · Why did Priya's assignment change?

Position Synchronization: learn it through a business decision

Priya is placed in Position BE-BLR-01. The Position contains Software Engineer, Backend Development and Bengaluru. The team expects those values to appear automatically on her Assignment.

First principle: Position Synchronization controls whether selected position attributes are copied or synchronized to worker assignments.

Pause, decide, then reveal the reasoning

Answer in your own words before opening each explanation.

Question 1 Do all Position values flow merely because a Position is selected?

Answer: No. Only attributes enabled and supported for synchronization flow according to the configuration.

Why: The Position's existence alone is not a synchronization rule.

Question 2 Where is the synchronization strategy controlled?

Answer: Through enterprise-level position-management settings and related configuration for the relevant attributes.

Why: The consultant must know which source controls each Assignment value.

Question 3 What if a synchronized Department on the Position changes?

Answer: Assess the effective-dated impact and synchronization processing on incumbent Assignments.

Why: A Position change can affect multiple workers; testing only the Position page is insufficient.

Question 4 Can manual Assignment entry safely contradict a synchronized Position?

Answer: That depends on the attribute and override rules; it must be tested, not assumed.

Why: The design should make the source of truth clear and prevent silent inconsistency.

If the business changes…When data differs between Position and Assignment, inspect synchronization settings, effective dates, override behavior and the relevant process before correcting records.

Simple mental picturePosition Synchronization is an attribute-by-attribute flow from Position to Assignment—not a blanket copy.

What does Position Synchronization do in Oracle?

Connects Position attributes to Assignment values
Depends on enterprise/position configuration
Impacts change and transfer behaviour

Why is it useful, and when do consultants use it?

Why the business needs it

It keeps position-managed assignments aligned with the approved position design.

Controls Position → Assignment flow
Attribute-specific
Reduces inconsistent data

When it is used

Position management strategy and clean position data.

Typical setup task:
Setup and Maintenance → Manage Enterprise HCM Information / position management settings

Important distinction

Position Synchronization
Which position values should flow to assignments?

Do not confuse

Values do not flow merely because a position exists; the attribute must be configured for synchronization.

How a consultant reasons

Read the business factsIdentify the questionChoose the objectCheck dependenciesTest the impact

Easy exam definition

Position Synchronization controls whether selected position attributes are copied or synchronized to worker assignments.

Memory line: Position Synchronization is an attribute-by-attribute flow from Position to Assignment—not a blanket copy.

Connect it to the TechNova design

Business questionWhich position values should flow to assignments?

TechNova recordPosition defaults Department, Job and Location to Priya’s assignment

Why it existsIt keeps position-managed assignments aligned with the approved position design.

Certification trapValues do not flow merely because a position exists; the attribute must be configured for synchronization.

Check your understanding

Controls Position → Assignment flow
Attribute-specific
Reduces inconsistent data
Requires clean position master data
Test change scenarios

Relationships

Control & sharing

Position Synchronization

Which position values should flow to assignments?

Relationship map

Enterprise

→

Legal & operational structures

→

Position Synchronization

→

Worker assignment

Direct relationships

Connects Position attributes to Assignment values
Depends on enterprise/position configuration
Impacts change and transfer behaviour

Think like a consultant: Identify whether the requirement changes the legal, operational, workforce, or sharing layer before creating or editing this object.

Implementation

Control & sharing

Position Synchronization

Which position values should flow to assignments?

Implementation purpose

It keeps position-managed assignments aligned with the approved position design.

Typical setup route

Setup and Maintenance → Manage Enterprise HCM Information / position management settings
Navigation and page names can vary with enabled Redwood experiences and quarterly updates. Learn the setup task and outcome.

Prerequisites

Position management strategy and clean position data.

Implementation checklist

Confirm the business owner and exact requirement.
Check whether an existing record can be reused.
Agree naming, codes, effective dates and sharing.
Configure in a test environment.
Validate transactions, security, reporting and integrations.
Document the design decision and migration method.

Technical Details

Control & sharing

Position Synchronization

Which position values should flow to assignments?

Consultant workspace

Position Synchronization Technical Details

Configure, migrate, maintain, validate and troubleshoot this object.

Primary technical question

Which position values should flow to assignments?

Current and future synchronization behavior is date-sensitiveSet-enabled: Not applicable

1Technical Profile

Oracle role in design	Configuration and process aligning Position to Assignment
Date behavior	Current and future synchronization behavior is date-sensitive
Set-enabled	Not applicable
Main setup task	Manage Enterprise HCM Information / Synchronize Person Assignment from Position
Main migration approach	Enable before assignment loads; Position.dat and Worker.dat/REST carry the relevant source values and flags
Used by	Connects Position attributes to Assignment values; Depends on enterprise/position configuration; Impacts change and transfer behaviour

3Prerequisites and Configuration Sequence

Clean Position master data
Enterprise or Legal Employer synchronization decision
Mapped attributes and controlled override policy

Sequence rule: Complete dependencies and approve stable codes before creating or loading Position Synchronization.

4Field Dictionary

Field	What it controls	TechNova example	Common mistake
Enabled level Inheriteddownstream-sensitive	Enterprise or Legal Employer setting	Enterprise enabled	Conflicting levels
Synchronized attributes Attribute-specific	Controls what flows	Job, Department, Location	Assuming all Position values flow
Synchronize from Position flag Required for load behavior	Enables assignment inheritance for loaded records	Yes	Omitting on HDL assignment
Action reason/process Audit-sensitive	Controls recorded update and batch behavior	Approved synchronize reason	Running without review

5UI Configuration Walkthrough

Decide enterprise versus Legal Employer scope.
Select only governed attributes for synchronization.
Enable before loading position-based assignments and set required assignment flags.
Change a test Position, run the process where required, and verify assignment history.

6HDL, HSDL and REST Availability

Method	Status	Best use
Setup UI	Supported	Enable and choose attributes
Scheduled process	Supported	Synchronize affected assignments
HDL	Supported downstream	Load Positions and position-based assignments correctly
REST	Supported downstream	Worker APIs can synchronize when settings/flags allow

Before production: Download the current business-object template or inspect current REST metadata. Release, feature and privilege differences can change supported attributes.

7Sample Data Load with Explanation

MIGRATION ORDER
1. Enable Position synchronization
2. Load Jobs, Departments, Locations and Positions
3. Load position-based Assignments with Synchronize from Position = Yes
4. Run/monitor synchronization process where required
5. Compare Position and Assignment values

Training guidance recommends enabling before worker assignment migration; enabling later may limit historical synchronization and requires careful remediation.

Source-key ruleKeep SourceSystemOwner and SourceSystemId stable so later MERGE operations update the same record.

Dependency ruleLoad and validate referenced parent records before dependent objects.

8Effective Dating and Maintenance Rules

Do not enable broadly without cleansing Position attributes.
New configuration generally affects current/future processing; historical behavior needs explicit assessment.
Use a controlled process and action reason for mass synchronization.
Retest overrides and manager hierarchy after any attribute-list change.

Create

→

Correct an error

→

Update from a date

→

Inactivate safely

9Security and Required Privileges

Setup privileges control synchronization configuration; scheduled-process access controls execution; worker data security controls which assignments a user can inspect.

Diagnostic rule: Separate three questions: Can the user open the function? Can the user maintain this object? Can the user see the relevant secured data?

10Downstream Impact

AssignmentsKeeps selected attributes aligned

ManagersPosition hierarchy can synchronize line manager

Audit/historyMass changes create effective-dated assignment updates

Assess current records, future-dated transactions, reports, approvals and integrations before changing a production value.

11Validation Checklist

Enabled at intended scope
Attribute list matches policy
Loaded assignments carry correct flag
Process completes without rejects
Overrides and history behave as designed

12Troubleshooting Scenarios

Symptom	Likely cause	What to do
Assignment unchanged	Attribute not selected or flag is No	Review configuration and assignment override flag
Wrong manager	Position hierarchy/parent incumbent incorrect	Validate hierarchy and rerun controlled sync
Only current dates update	Feature enabled after historical loads	Plan current/future remediation explicitly

13Technical Consultant Challenge

Positions were loaded first, then workers, but Department and Location did not copy to assignments. What should you do?

Consultant answer

Verify synchronization was enabled before worker load, the attributes were selected, each assignment referenced the Position, and Synchronize from Position was set correctly. Then use the supported synchronization process for remediation.

Certification

Control & sharing

Position Synchronization

Which position values should flow to assignments?

Certification trap

Watch for this: Values do not flow merely because a position exists; the attribute must be configured for synchronization.

How to reason through a scenario

Underline the business question.
Identify the layer: legal, operational, workforce, or control.
Remove options that answer a different business question.
Check effective date, reuse, sharing and dependency clues.
Choose the solution that preserves history and avoids duplication.

Revision

Control & sharing

Position Synchronization

Which position values should flow to assignments?

30-second revision

Position Synchronization
Position Synchronization controls whether selected position attributes are copied or synchronized to worker assignments.

Example: Position defaults Department, Job and Location to Priya’s assignment
Main trap: Values do not flow merely because a position exists; the attribute must be configured for synchronization.

Active recall

Which position values should flow to assignments?
Which objects depend on or use Position Synchronization?
What must exist before it is configured?
Which date, status or sharing controls matter?
What configuration mistake would you warn the client about?

Lesson 10

Actions & Reasons

Why did a workforce change occur?

Fundamentals

Control & sharing

Actions & Reasons

Why did a workforce change occur?

TechNova story · What happened—and why?

Actions & Reasons: learn it through a business decision

Priya moves from Backend Development to Cloud Services because of a reorganization. HR wants the transaction and the business reason reported separately.

First principle: Actions classify workforce transactions; Action Reasons provide a more specific explanation.

Pause, decide, then reveal the reasoning

Answer in your own words before opening each explanation.

Question 1 Which value says what happened?

Answer: The Action, such as Transfer.

Why: Actions classify workforce transactions and can support processing, reporting and approval logic.

Question 2 Which value says why it happened?

Answer: The Action Reason, such as Business Reorganization.

Why: Reasons provide controlled detail beneath the applicable Action.

Question 3 Can any Reason be used with any Action?

Answer: No. Reasons must be valid and associated with the relevant Action/context.

Why: A controlled relationship prevents meaningless combinations and inconsistent reporting.

Question 4 Why not create a new Reason for every sentence managers type?

Answer: Use governed categories and capture free-text detail separately where appropriate.

Why: Too many near-duplicate Reasons destroy analytics and complicate approvals.

If the business changes…Inactivation affects future availability but historical transactions must remain understandable. Never rename codes casually when integrations and reports depend on them.

Simple mental pictureAction = what happened. Action Reason = why it happened.

What does Actions & Reasons do in Oracle?

Used by hire, change, transfer and termination transactions
Can influence workflows and reporting
Reasons belong to relevant actions

Why is it useful, and when do consultants use it?

Why the business needs it

They support processing rules, approvals, reporting, analytics and audit history.

Classifies transactions
Reasons add detail
Important for audit/reporting

When it is used

Transaction and reporting requirements.

Typical setup task:
Setup and Maintenance → Manage Actions / Manage Action Reasons

Important distinction

Actions & Reasons
Why did a workforce change occur?

Do not confuse

An Action says what happened; an Action Reason says why it happened.

How a consultant reasons

Read the business factsIdentify the questionChoose the objectCheck dependenciesTest the impact

Easy exam definition

Actions classify workforce transactions; Action Reasons provide a more specific explanation.

Memory line: Action = what happened. Action Reason = why it happened.

Connect it to the TechNova design

Business questionWhy did a workforce change occur?

TechNova recordAction: Transfer · Reason: Business Reorganization

Why it existsThey support processing rules, approvals, reporting, analytics and audit history.

Certification trapAn Action says what happened; an Action Reason says why it happened.

Check your understanding

Classifies transactions
Reasons add detail
Important for audit/reporting
Can affect approvals
Use controlled codes

Relationships

Control & sharing

Actions & Reasons

Why did a workforce change occur?

Relationship map

Enterprise

→

Legal & operational structures

→

Actions & Reasons

→

Worker assignment

Direct relationships

Used by hire, change, transfer and termination transactions
Can influence workflows and reporting
Reasons belong to relevant actions

Think like a consultant: Identify whether the requirement changes the legal, operational, workforce, or sharing layer before creating or editing this object.

Implementation

Control & sharing

Actions & Reasons

Why did a workforce change occur?

Implementation purpose

They support processing rules, approvals, reporting, analytics and audit history.

Typical setup route

Setup and Maintenance → Manage Actions / Manage Action Reasons
Navigation and page names can vary with enabled Redwood experiences and quarterly updates. Learn the setup task and outcome.

Prerequisites

Transaction and reporting requirements.

Implementation checklist

Confirm the business owner and exact requirement.
Check whether an existing record can be reused.
Agree naming, codes, effective dates and sharing.
Configure in a test environment.
Validate transactions, security, reporting and integrations.
Document the design decision and migration method.

Technical Details

Control & sharing

Actions & Reasons

Why did a workforce change occur?

Consultant workspace

Actions & Reasons Technical Details

Configure, migrate, maintain, validate and troubleshoot this object.

Primary technical question

Why did a workforce change occur?

Active/status-controlled setupSet-enabled: No

1Technical Profile

Oracle role in design	Controlled transaction classification and explanation
Date behavior	Active/status-controlled setup
Set-enabled	No
Main setup task	Manage Actions / Manage Action Reasons
Main migration approach	Worker loads reference valid action and reason codes; setup migration support must be checked separately
Used by	Used by hire, change, transfer and termination transactions; Can influence workflows and reporting; Reasons belong to relevant actions

3Prerequisites and Configuration Sequence

Transaction catalogue and reporting requirements
Approval/workflow impact assessment
Governed codes and reason-to-action mapping

Sequence rule: Complete dependencies and approve stable codes before creating or loading Actions & Reasons.

4Field Dictionary

Field	What it controls	TechNova example	Common mistake
Action code/name Requiredintegration-sensitive	States what occurred	TRANSFER / Transfer	Encoding the reason in action name
Action type System-sensitive	Connects to transaction behavior	Transfer-related type	Changing seeded meaning
Reason code/name Required for designed reporting	States why it occurred	REORG / Business Reorganization	Creating unrelated reasons
Action association/status Downstream-sensitive	Controls where and when reason is selectable	REORG active for Transfer	Reason mapped to wrong action

5UI Configuration Walkthrough

Inventory transactions and reporting categories.
Reuse seeded actions where appropriate; create only governed additions.
Create reasons and associate them with valid actions.
Test transaction LOVs, approvals, audit and reports.

6HDL, HSDL and REST Availability

Method	Status	Best use
Manual UI	Supported	Primary setup
FSM migration	Check support	Promote governed setup
Worker HDL	Supported downstream	Reference valid action/reason codes
REST	Supported downstream	Transaction payloads require valid values

Before production: Download the current business-object template or inspect current REST metadata. Release, feature and privilege differences can change supported attributes.

7Sample Data Load with Explanation

TRANSACTION REFERENCE
ActionCode=TRANSFER
ActionReasonCode=REORG
Meaning: worker transferred because of business reorganization
Validation: reason must be active and associated with the action

Action says what happened; Action Reason says why. Worker files should reference approved codes rather than free text.

Source-key ruleKeep SourceSystemOwner and SourceSystemId stable so later MERGE operations update the same record.

Dependency ruleLoad and validate referenced parent records before dependent objects.

8Effective Dating and Maintenance Rules

Avoid changing codes once reports and integrations depend on them.
Inactivate obsolete reasons instead of deleting audit history.
Use effective/status changes consistent with transaction dates.
Assess workflow and reporting before adding or consolidating reasons.

Create

→

Correct an error

→

Update from a date

→

Inactivate safely

9Security and Required Privileges

Setup access controls who maintains Actions and Reasons. Transaction privileges and data security separately control who can perform and view workforce changes.

Diagnostic rule: Separate three questions: Can the user open the function? Can the user maintain this object? Can the user see the relevant secured data?

10Downstream Impact

TransactionsControls selectable change classifications

ApprovalsMay influence configured workflow rules

Reporting/auditExplains what happened and why

Assess current records, future-dated transactions, reports, approvals and integrations before changing a production value.

11Validation Checklist

Action type matches intended transaction
Reasons are associated correctly
Codes are stable and unique
LOVs show values on intended dates
Reports and approvals interpret them correctly

12Troubleshooting Scenarios

Symptom	Likely cause	What to do
Reason absent	Inactive or not associated to action	Review mapping and status
HDL transaction fails	Invalid action/reason combination	Use approved codes and valid date
Reports fragment	Too many near-duplicate reasons	Govern and consolidate future use

13Technical Consultant Challenge

HR creates an Action called Transfer Due to Reorganization. What should you do?

Consultant answer

Prefer Action = Transfer and Reason = Business Reorganization. This preserves reusable transaction classification and separately reportable business cause.

Certification

Control & sharing

Actions & Reasons

Why did a workforce change occur?

Certification trap

Watch for this: An Action says what happened; an Action Reason says why it happened.

How to reason through a scenario

Underline the business question.
Identify the layer: legal, operational, workforce, or control.
Remove options that answer a different business question.
Check effective date, reuse, sharing and dependency clues.
Choose the solution that preserves history and avoids duplication.

Revision

Control & sharing

Actions & Reasons

Why did a workforce change occur?

30-second revision

Actions & Reasons
Actions classify workforce transactions; Action Reasons provide a more specific explanation.

Example: Action: Transfer · Reason: Business Reorganization
Main trap: An Action says what happened; an Action Reason says why it happened.

Active recall

Why did a workforce change occur?
Which objects depend on or use Actions & Reasons?
What must exist before it is configured?
Which date, status or sharing controls matter?
What configuration mistake would you warn the client about?

Lesson 11

Organization Trees

How are organizations grouped for reporting and analysis?

Fundamentals

Control & sharing

Organization Trees

How are organizations grouped for reporting and analysis?

TechNova story · The hierarchy changes next quarter

Organization Trees: learn it through a business decision

TechNova wants Technology Division above Backend Development and Cloud Support. A new hierarchy begins next quarter, but prior-period reports must retain the old structure.

First principle: Organization Trees arrange organizations into hierarchies for reporting, security, analytics and other configured uses.

Pause, decide, then reveal the reasoning

Answer in your own words before opening each explanation.

Question 1 Does adding a Department to a tree create the Department?

Answer: No. The organization must exist before the tree references it.

Why: A tree arranges existing organizations; it is not the master-data creation mechanism.

Question 2 How can the future hierarchy coexist with history?

Answer: Create, validate and activate the appropriate future-effective tree version.

Why: Versioning preserves prior parent-child relationships while allowing controlled change.

Question 3 Why not overwrite the current tree?

Answer: It can destroy the hierarchy needed for historical reporting, security or analysis.

Why: Effective periods and versions are part of the business design, not administrative decoration.

Question 4 Does a parent in the tree become a Legal Employer?

Answer: No. Tree placement does not change an organization's classification.

Why: Hierarchy answers 'how are records grouped?' Classification answers 'what role does this record perform?'

If the business changes…Before activating a version, validate dates, node completeness, overlaps, downstream consumers and security/reporting consequences.

Simple mental pictureTrees group existing organizations through effective versions; they do not create or reclassify them.

What does Organization Trees do in Oracle?

References existing organizations
Uses tree versions and effective periods
Can support reporting and security contexts

Why is it useful, and when do consultants use it?

Why the business needs it

They show parent-child relationships without changing the underlying organization records.

Hierarchy of existing organizations
Versioned/effective
Supports analysis

When it is used

Organizations must exist before they are placed in the tree.

Typical setup task:
Setup and Maintenance → Manage Organization Trees

Important distinction

Organization Trees
How are organizations grouped for reporting and analysis?

Do not confuse

A tree groups existing objects; it does not create the organizations themselves.

How a consultant reasons

Read the business factsIdentify the questionChoose the objectCheck dependenciesTest the impact

Easy exam definition

Organization Trees arrange organizations into hierarchies for reporting, security, analytics and other configured uses.

Memory line: Trees group existing organizations through effective versions; they do not create or reclassify them.

Connect it to the TechNova design

Business questionHow are organizations grouped for reporting and analysis?

TechNova recordTechNova Group → Technology Division → Backend Development

Why it existsThey show parent-child relationships without changing the underlying organization records.

Certification trapA tree groups existing objects; it does not create the organizations themselves.

Check your understanding

Hierarchy of existing organizations
Versioned/effective
Supports analysis
Parent-child structure
Not a replacement for BU or Department

Relationships

Control & sharing

Organization Trees

How are organizations grouped for reporting and analysis?

Relationship map

Enterprise

→

Legal & operational structures

→

Organization Trees

→

Worker assignment

Direct relationships

References existing organizations
Uses tree versions and effective periods
Can support reporting and security contexts

Think like a consultant: Identify whether the requirement changes the legal, operational, workforce, or sharing layer before creating or editing this object.

Implementation

Control & sharing

Organization Trees

How are organizations grouped for reporting and analysis?

Implementation purpose

They show parent-child relationships without changing the underlying organization records.

Typical setup route

Setup and Maintenance → Manage Organization Trees
Navigation and page names can vary with enabled Redwood experiences and quarterly updates. Learn the setup task and outcome.

Prerequisites

Organizations must exist before they are placed in the tree.

Implementation checklist

Confirm the business owner and exact requirement.
Check whether an existing record can be reused.
Agree naming, codes, effective dates and sharing.
Configure in a test environment.
Validate transactions, security, reporting and integrations.
Document the design decision and migration method.

Technical Details

Control & sharing

Organization Trees

How are organizations grouped for reporting and analysis?

Consultant workspace

Organization Trees Technical Details

Configure, migrate, maintain, validate and troubleshoot this object.

Primary technical question

How are organizations grouped for reporting and analysis?

Tree versions have effective periodsSet-enabled: Not a sharing mechanism

1Technical Profile

Oracle role in design	Versioned hierarchy of existing organizations
Date behavior	Tree versions have effective periods
Set-enabled	Not a sharing mechanism
Main setup task	Manage Organization Trees
Main migration approach	Use supported tree import/migration; parent organizations must already exist
Used by	References existing organizations; Uses tree versions and effective periods; Can support reporting and security contexts

3Prerequisites and Configuration Sequence

Existing organizations and stable codes
Approved parent-child hierarchy
Version dates, audit and consumer requirements

Sequence rule: Complete dependencies and approve stable codes before creating or loading Organization Trees.

4Field Dictionary

Field	What it controls	TechNova example	Common mistake
Tree code/name Requiredintegration-sensitive	Identifies hierarchy	TN_ORG_TREE	Renaming for every version
Tree structure Required	Defines permitted node type	Organization hierarchy	Mixing unsupported node types
Version dates/status Date-effective	Controls active hierarchy	Next-quarter active version	Overlapping active versions
Nodes/parents Required	Defines relationships	Technology → Backend Development	Adding organization that does not exist

5UI Configuration Walkthrough

Confirm hierarchy purpose and consuming reports/security.
Select the correct tree structure and create a version.
Add existing organizations in validated parent-child order.
Audit, activate and test the version for the intended date.

6HDL, HSDL and REST Availability

Method	Status	Best use
Manual UI	Supported	Build and review hierarchy
Tree import	Check supported mechanism	Bulk node/version migration
HDL	Not ordinary organization creation	Organizations must exist first
REST	Check current tree service	Do not assume activation support

Before production: Download the current business-object template or inspect current REST metadata. Release, feature and privilege differences can change supported attributes.

7Sample Data Load with Explanation

TREE VERSION
Tree: TN_ORG_TREE
Version: NEXT_QTR
Effective: <start> to <end/open>
Root: TechNova Group
Child: Technology Division
Grandchild: Backend Development

The tree references existing organization records. It does not create or reclassify those organizations.

Source-key ruleKeep SourceSystemOwner and SourceSystemId stable so later MERGE operations update the same record.

Dependency ruleLoad and validate referenced parent records before dependent objects.

8Effective Dating and Maintenance Rules

Create a new effective version for a genuine future hierarchy change.
Do not overwrite a historical version used by reporting.
Audit the version before activation.
Avoid gaps or overlaps unless the consuming feature explicitly supports the design.

Create

→

Correct an error

→

Update from a date

→

Inactivate safely

9Security and Required Privileges

A tree can be referenced by security profiles, but tree maintenance and worker access are separate. Activating a version can materially change secured populations when a profile consumes it.

Diagnostic rule: Separate three questions: Can the user open the function? Can the user maintain this object? Can the user see the relevant secured data?

10Downstream Impact

ReportingRolls organizations into management views

SecurityCan define organization populations

AnalyticsPreserves hierarchy by effective period

Assess current records, future-dated transactions, reports, approvals and integrations before changing a production value.

11Validation Checklist

All nodes exist and are effective
Parent-child order is correct
Version dates do not conflict
Audit passes and correct version is active
Reports/security return expected population

12Troubleshooting Scenarios

Symptom	Likely cause	What to do
Organization missing	Node not added or date outside version	Review version and organization dates
Activation fails	Audit errors or overlapping dates	Correct structure/version dates
Users gain/lose access	Security profile consumes changed tree	Test population before activation

13Technical Consultant Challenge

A reorganization starts next quarter, but the team edits the current active tree version. What should you do?

Consultant answer

Create and validate a new future-dated version. Preserve the current version so historical reporting and security remain explainable.

Certification

Control & sharing

Organization Trees

How are organizations grouped for reporting and analysis?

Certification trap

Watch for this: A tree groups existing objects; it does not create the organizations themselves.

How to reason through a scenario

Underline the business question.
Identify the layer: legal, operational, workforce, or control.
Remove options that answer a different business question.
Check effective date, reuse, sharing and dependency clues.
Choose the solution that preserves history and avoids duplication.

Revision

Control & sharing

Organization Trees

How are organizations grouped for reporting and analysis?

30-second revision

Organization Trees
Organization Trees arrange organizations into hierarchies for reporting, security, analytics and other configured uses.

Example: TechNova Group → Technology Division → Backend Development
Main trap: A tree groups existing objects; it does not create the organizations themselves.

Active recall

How are organizations grouped for reporting and analysis?
Which objects depend on or use Organization Trees?
What must exist before it is configured?
Which date, status or sharing controls matter?
What configuration mistake would you warn the client about?

Lesson 12

Enterprise Structures Configurator

How can an initial enterprise structure be generated from guided questions?

Fundamentals

Control & sharing

Enterprise Structures Configurator

How can an initial enterprise structure be generated from guided questions?

TechNova story · The guided setup workshop

Enterprise Structures Configurator: learn it through a business decision

At the start of implementation, TechNova must decide how its countries, registered companies, employers, payroll responsibilities, Business Units and shared reference data fit together. The Configurator acts like an architect's planning tool: it asks connected business questions and turns the answers into a proposed foundational design.

First principle: The Enterprise Structures Configurator (where available in the implementation flow) helps model and generate foundational enterprise structures from guided business information.

Pause, decide, then reveal the reasoning

Answer in your own words before opening each explanation.

Question 1 What is the Configurator useful for?

Answer: It helps the team design, compare, review and load an initial connected Enterprise structure instead of treating every setup object as an isolated decision.

Why: The guided interview exposes dependencies among Enterprise, Divisions, Legal Entities, Legal Employers, Payroll Statutory Units, Legislative Data Groups, Business Units and Reference Data Sets.

Question 2 What can the guided design propose or help establish?

Answer: Depending on the available implementation flow, it can propose foundational structures such as Divisions, Legal Entities and their classifications, Business Units, Legislative Data Groups and Reference Data Set assignments.

Why: The output is an initial model. The exact generated components depend on the answers, offering and enabled features.

Question 3 Does generated mean legally validated?

Answer: No. Consultants must compare the proposal with registrations, payroll obligations and the real operating model.

Why: A guided tool cannot replace evidence or stakeholder decisions.

Question 4 Is the Configurator an HDL file?

Answer: No. It is a guided setup mechanism, not a bulk-load data file.

Why: Migration tooling and guided design serve different purposes.

Question 5 What should happen before finalizing generated structures?

Answer: Compare alternative designs, then review names, classifications, dates, reference-data strategy, dependencies and downstream transaction effects with responsible stakeholders.

Why: Correcting a foundational design later is more disruptive than validating it early.

If the business changes…The Configurator is mainly an initial implementation tool. After implementation, consultants usually maintain individual live objects through their own setup tasks.

Simple mental pictureAsk questions → design structure → compare scenarios → review → load.

What does Enterprise Structures Configurator do in Oracle?

Supports initial enterprise design
Can create or propose multiple foundational objects
Requires review before production use

Why is it useful, and when do consultants use it?

Why the business needs it

It can accelerate initial setup and expose dependencies among enterprise, legal and business structures.

Guided initial setup
Creates connected structures
Requires consultant validation

When it is used

Clear legal and operational design decisions.

Typical setup task:
Setup and Maintenance → Establish Enterprise Structures / Enterprise Structures Configurator, subject to offering and release

Important distinction

Enterprise Structures Configurator
How can an initial enterprise structure be generated from guided questions?

Do not confuse

Do not accept generated structures without validating the real legal, payroll and operating model.

How a consultant reasons

Read the business factsIdentify the questionChoose the objectCheck dependenciesTest the impact

Easy exam definition

The Enterprise Structures Configurator (where available in the implementation flow) helps model and generate foundational enterprise structures from guided business information.

Memory line: Ask questions → design structure → compare scenarios → review → load.

Connect it to the TechNova design

Business questionHow can an initial enterprise structure be generated from guided questions?

TechNova recordModel TechNova enterprise, legal entity and business units before finalizing setup

Why it existsIt can accelerate initial setup and expose dependencies among enterprise, legal and business structures.

Certification trapDo not accept generated structures without validating the real legal, payroll and operating model.

Check your understanding

Guided initial setup
Creates connected structures
Requires consultant validation
Release experience can vary
Start with requirements

Relationships

Control & sharing

Enterprise Structures Configurator

How can an initial enterprise structure be generated from guided questions?

Relationship map

Enterprise

→

Legal & operational structures

→

Enterprise Structures Configurator

→

Worker assignment

Direct relationships

Supports initial enterprise design
Can create or propose multiple foundational objects
Requires review before production use

Think like a consultant: Identify whether the requirement changes the legal, operational, workforce, or sharing layer before creating or editing this object.

Implementation

Control & sharing

Enterprise Structures Configurator

How can an initial enterprise structure be generated from guided questions?

Implementation purpose

It can accelerate initial setup and expose dependencies among enterprise, legal and business structures.

Typical setup route

Setup and Maintenance → Establish Enterprise Structures / Enterprise Structures Configurator, subject to offering and release
Navigation and page names can vary with enabled Redwood experiences and quarterly updates. Learn the setup task and outcome.

Prerequisites

Clear legal and operational design decisions.

Implementation checklist

Confirm the business owner and exact requirement.
Check whether an existing record can be reused.
Agree naming, codes, effective dates and sharing.
Configure in a test environment.
Validate transactions, security, reporting and integrations.
Document the design decision and migration method.

Technical Details

Control & sharing

Enterprise Structures Configurator

How can an initial enterprise structure be generated from guided questions?

Consultant workspace

Enterprise Structures Configurator Technical Details

Configure, migrate, maintain, validate and troubleshoot this object.

Primary technical question

How can an initial enterprise structure be generated from guided questions?

Generated records use their own effective datesSet-enabled: Can propose reference-data choices

1Technical Profile

Oracle role in design	Guided foundational-structure design and generation
Date behavior	Generated records use their own effective dates
Set-enabled	Can propose reference-data choices
Main setup task	Enterprise Structures Configurator / Establish Enterprise Structures
Main migration approach	Guided setup mechanism, not an HDL file
Used by	Supports initial enterprise design; Can create or propose multiple foundational objects; Requires review before production use

3Prerequisites and Configuration Sequence

Legal registrations and country plan
Operational BU/function design
Naming, dates, payroll and reference-data decisions

Sequence rule: Complete dependencies and approve stable codes before creating or loading Enterprise Structures Configurator.

4Field Dictionary

Field	What it controls	TechNova example	Common mistake
Enterprise information Required	Defines top-level proposal	TechNova Group	Entering a brand without boundary analysis
Legal structure answers Evidence-driven	Drives Legal Entity/Employer proposal	India registered company	Guessing registrations
Business Unit choices Downstream-sensitive	Drives operational proposal	Software, Cloud Services, Consulting	Creating BUs for every Department
Reference-data choices Set-controlled	Shapes sharing defaults	Common versus BU-specific	Accepting defaults without data inventory

5UI Configuration Walkthrough

Complete requirements discovery before opening the Configurator.
Answer guided questions using approved evidence.
Review every generated object, classification, code, date and dependency.
Validate transactions and adjust setup before treating the proposal as production design.

6HDL, HSDL and REST Availability

Method	Status	Best use
Guided UI	Supported where available	Model and generate connected structures
HDL	Not applicable	Configurator is not a data file
FSM migration	Check generated setup support	Promote approved configuration
REST	Not the design mechanism	Use documented APIs only after setup

Before production: Download the current business-object template or inspect current REST metadata. Release, feature and privilege differences can change supported attributes.

7Sample Data Load with Explanation

CONFIGURATOR REVIEW
Enterprise: Does boundary match implementation?
Legal Entity: Does registration evidence match?
Legal Employer/PSU: Are classifications justified?
Business Units: Do they process distinct operations?
Sets: Will intended values be shared?

Treat generated output as a proposal. The Configurator accelerates setup but cannot validate legal evidence or replace consultant design decisions.

Source-key ruleKeep SourceSystemOwner and SourceSystemId stable so later MERGE operations update the same record.

Dependency ruleLoad and validate referenced parent records before dependent objects.

8Effective Dating and Maintenance Rules

Correct generated records before transactional use wherever possible.
Once workers and payroll depend on them, use controlled effective-dated maintenance.
Do not rerun and accept a conflicting structure without reconciliation.
Preserve the approved design record and dependency map.

Create

→

Correct an error

→

Update from a date

→

Inactivate safely

9Security and Required Privileges

Only authorized implementers should generate or alter foundational setup. Restrict access because the output can affect legal, operational and reference-data structures.

Diagnostic rule: Separate three questions: Can the user open the function? Can the user maintain this object? Can the user see the relevant secured data?

10Downstream Impact

Legal setupCan propose entities and classifications

OperationsCan create Business Units and functions

SharingCan establish initial reference-data strategy

Assess current records, future-dated transactions, reports, approvals and integrations before changing a production value.

11Validation Checklist

Every answer is supported by a requirement/evidence
Generated names/codes follow standards
Classifications and dates are correct
Set sharing matches data inventory
Hire and reporting tests pass

12Troubleshooting Scenarios

Symptom	Likely cause	What to do
Generated structure too complex	Questions answered from org chart alone	Return to legal/operational requirements
Wrong classifications	Legal responsibilities not validated	Correct before transactional use
Missing reference values	Set strategy incomplete	Review BU set assignments and dependent setup

13Technical Consultant Challenge

The generated design looks reasonable, and the project manager wants immediate production use. What should you do?

Consultant answer

Pause for consultant validation: reconcile legal evidence, payroll obligations, BU functions, dates, codes, set assignments and downstream tests. Generated does not mean approved or legally correct.

Certification

Control & sharing

Enterprise Structures Configurator

How can an initial enterprise structure be generated from guided questions?

Certification trap

Watch for this: Do not accept generated structures without validating the real legal, payroll and operating model.

How to reason through a scenario

Underline the business question.
Identify the layer: legal, operational, workforce, or control.
Remove options that answer a different business question.
Check effective date, reuse, sharing and dependency clues.
Choose the solution that preserves history and avoids duplication.

Revision

Control & sharing

Enterprise Structures Configurator

How can an initial enterprise structure be generated from guided questions?

30-second revision

Enterprise Structures Configurator
The Enterprise Structures Configurator (where available in the implementation flow) helps model and generate foundational enterprise structures from guided business information.

Example: Model TechNova enterprise, legal entity and business units before finalizing setup
Main trap: Do not accept generated structures without validating the real legal, payroll and operating model.

Active recall

How can an initial enterprise structure be generated from guided questions?
Which objects depend on or use Enterprise Structures Configurator?
What must exist before it is configured?
Which date, status or sharing controls matter?
What configuration mistake would you warn the client about?

Lesson 13

Department

Which organizational unit performs the work?

Fundamentals

Workforce structure

Department

Which organizational unit performs the work?

TechNova story · One team, many offices

Department: learn it through a business decision

Backend Development has 50 workers in Bengaluru and 30 in Mumbai. A designer proposes two Departments because the workers sit in different cities.

First principle: A Department represents an organizational unit in which workers perform work, such as Finance or Backend Development.

Pause, decide, then reveal the reasoning

Answer in your own words before opening each explanation.

Question 1 What does Department identify?

Answer: The organizational unit in which workers perform work.

Why: Backend Development remains the same team even when its members work at different sites.

Question 2 How should the city difference be represented?

Answer: Use the appropriate Locations on positions or assignments while retaining one Department when the team is genuinely one unit.

Why: Location answers where; Department answers which organizational team.

Question 3 Why does the Department matter beyond display?

Answer: It can support assignment organization, reporting, approvals, costing and manager responsibility.

Why: Its downstream use makes naming, codes, hierarchy and effective dates important.

Question 4 The company creates a separate Cloud Support team with its own manager and reporting. What should be assessed?

Answer: Whether it is a distinct Department with its own organizational identity and responsibilities.

Why: The decision is driven by how the work is managed—not merely by employee count.

If the business changes…A move between offices may change Location only; a reorganization between teams changes Department and may affect managers, approvals, costs and reports.

Simple mental pictureDepartment is the team; Location is the workplace. One Department can span multiple Locations.

What does Department do in Oracle?

Used on assignments and positions
May operate across several locations
Can be arranged in organization trees

Why is it useful, and when do consultants use it?

Why the business needs it

It supports assignment organization, reporting, approvals, costs and manager responsibilities.

Organizational team
Set-enabled reference data
Can span locations

When it is used

Reference-data strategy and organization design.

Typical setup task:
Setup and Maintenance → Manage Departments

Important distinction

Department
Which organizational unit performs the work?

Do not confuse

One department operating in two cities does not automatically require two Department records.

How a consultant reasons

Read the business factsIdentify the questionChoose the objectCheck dependenciesTest the impact

Easy exam definition

A Department represents an organizational unit in which workers perform work, such as Finance or Backend Development.

Memory line: Department is the team; Location is the workplace. One Department can span multiple Locations.

Connect it to the TechNova design

Business questionWhich organizational unit performs the work?

TechNova recordBackend Development

Why it existsIt supports assignment organization, reporting, approvals, costs and manager responsibilities.

Certification trapOne department operating in two cities does not automatically require two Department records.

Check your understanding

Organizational team
Set-enabled reference data
Can span locations
Used on assignments
Avoid city-based duplicates

Relationships

Workforce structure

Department

Which organizational unit performs the work?

Relationship map

Enterprise

→

Legal & operational structures

→

Department

→

Worker assignment

Direct relationships

Used on assignments and positions
May operate across several locations
Can be arranged in organization trees

Think like a consultant: Identify whether the requirement changes the legal, operational, workforce, or sharing layer before creating or editing this object.

Implementation

Workforce structure

Department

Which organizational unit performs the work?

Implementation purpose

It supports assignment organization, reporting, approvals, costs and manager responsibilities.

Typical setup route

Setup and Maintenance → Manage Departments
Navigation and page names can vary with enabled Redwood experiences and quarterly updates. Learn the setup task and outcome.

Prerequisites

Reference-data strategy and organization design.

Implementation checklist

Confirm the business owner and exact requirement.
Check whether an existing record can be reused.
Agree naming, codes, effective dates and sharing.
Configure in a test environment.
Validate transactions, security, reporting and integrations.
Document the design decision and migration method.

Technical Details

Workforce structure

Department

Which organizational unit performs the work?

Consultant workspace

Department Technical Details

Configure, migrate, maintain, validate and troubleshoot this object.

Primary technical question

Which organizational unit performs the work?

Date-effective organization and classificationSet-enabled: Yes

1Technical Profile

Oracle role in design	Set-enabled organization with Department classification
Date behavior	Date-effective organization and classification
Set-enabled	Yes
Main setup task	Manage Departments
Main migration approach	Organization.dat with Organization and OrgUnitClassification components
Used by	Used on assignments and positions; May operate across several locations; Can be arranged in organization trees

3Prerequisites and Configuration Sequence

Department design and ownership
Valid Reference Data Set
Codes, dates and any hierarchy/costing design

Sequence rule: Complete dependencies and approve stable codes before creating or loading Department.

4Field Dictionary

Field	What it controls	TechNova example	Common mistake
Name and code Requiredintegration-sensitive	User value and stable key	Backend Development / DEP-BACKEND	Adding city to the name without need
Set Requiredset-controlled	Controls BU availability	TechNova Common Set	Selecting a set not assigned to the BU
Effective start/status Date-effective	Controls transaction availability	Active from approved date	Starting after positions or assignments
Manager Optionaldownstream-sensitive	Identifies department responsibility where used	Head of Backend	Confusing with every worker's line manager

5UI Configuration Walkthrough

Confirm whether one department can serve multiple locations.
Create the organization with code, set and start date.
Apply Department classification and manager/hierarchy attributes.
Test selection on positions and assignments in every intended BU.

6HDL, HSDL and REST Availability

Method	Status	Best use
Manual UI	Supported	Small volumes
HDL	Supported	Organization.dat parent and classification
HSDL	Check available template	Business spreadsheet load where enabled
REST	Check current organizations resource	Validate classification and security

Before production: Download the current business-object template or inspect current REST metadata. Release, feature and privilege differences can change supported attributes.

7Sample Data Load with Explanation

METADATA|Organization|SourceSystemOwner|SourceSystemId|Name|EffectiveStartDate
MERGE|Organization|EXAMNXT|DEP_BACKEND|Backend Development|<start date>
METADATA|OrgUnitClassification|SourceSystemOwner|SourceSystemId|OrganizationId(SourceSystemId)|ClassificationCode|SetCode
MERGE|OrgUnitClassification|EXAMNXT|DEP_BACKEND_CLASS|DEP_BACKEND|<department classification code>|TN_COMMON

Keep source keys stable. Confirm the current template's classification code and SetCode placement; the organization must not start after its classification.

Source-key ruleKeep SourceSystemOwner and SourceSystemId stable so later MERGE operations update the same record.

Dependency ruleLoad and validate referenced parent records before dependent objects.

8Effective Dating and Maintenance Rules

Correct an input error; use Update for a real future change.
Do not delete a Department used by assignments or positions.
Inactivate the classification for future use while preserving history.
Test future-dated hires and position changes before closure.

Create

→

Correct an error

→

Update from a date

→

Inactivate safely

9Security and Required Privileges

Maintenance needs organization setup access. User visibility additionally depends on transaction security, BU context and set sharing.

Diagnostic rule: Separate three questions: Can the user open the function? Can the user maintain this object? Can the user see the relevant secured data?

10Downstream Impact

AssignmentsOrganizational team recorded on workers

PositionsMay default or synchronize to assignments

Reporting/costingSupports team and cost-center analysis

Assess current records, future-dated transactions, reports, approvals and integrations before changing a production value.

11Validation Checklist

Set assignment makes Department visible to intended BUs
Organization and classification dates align
Positions and assignments accept the value
Manager/hierarchy are correct
Reports and integrations use stable code

12Troubleshooting Scenarios

Symptom	Likely cause	What to do
Absent from hire LOV	Set, status or effective-date mismatch	Trace BU set assignment and hire date
HDL classification failed	Parent key/date invalid	Load Organization first and align dates
Duplicate Departments by city	Location confused with team	Keep one Department and use Locations

13Technical Consultant Challenge

Sixty Departments load successfully, but Cloud Services BU sees only forty-two. What should you do?

Consultant answer

Check SetCode and BU set assignment first, then effective date/status and security. A successful HDL status proves ingestion, not transaction visibility.

Certification

Workforce structure

Department

Which organizational unit performs the work?

Certification trap

Watch for this: One department operating in two cities does not automatically require two Department records.

How to reason through a scenario

Underline the business question.
Identify the layer: legal, operational, workforce, or control.
Remove options that answer a different business question.
Check effective date, reuse, sharing and dependency clues.
Choose the solution that preserves history and avoids duplication.

Revision

Workforce structure

Department

Which organizational unit performs the work?

30-second revision

Department
A Department represents an organizational unit in which workers perform work, such as Finance or Backend Development.

Example: Backend Development
Main trap: One department operating in two cities does not automatically require two Department records.

Active recall

Which organizational unit performs the work?
Which objects depend on or use Department?
What must exist before it is configured?
Which date, status or sharing controls matter?
What configuration mistake would you warn the client about?

Lesson 14

Job

What general type of work is performed?

Fundamentals

Workforce structure

Job

What general type of work is performed?

TechNova story · Work type or individual seat?

Job: learn it through a business decision

TechNova needs 100 Software Engineers across several teams. A junior designer proposes 100 Jobs, one for every worker.

First principle: A Job is a reusable definition of work, such as Software Engineer or HR Specialist.

Pause, decide, then reveal the reasoning

Answer in your own words before opening each explanation.

Question 1 How many Job definitions are needed for the same general work?

Answer: Usually one reusable Job definition can support many workers and positions.

Why: Job describes the general nature of work, not a named person or numbered seat.

Question 2 What represents each approved seat when headcount control is required?

Answer: A Position represents a specific occurrence of the Job.

Why: Many Positions can reference one Job while carrying different departments, locations or headcount attributes.

Question 3 Can Software Engineer be used in two Departments?

Answer: Yes, if the sharing design and business taxonomy permit it.

Why: Job is independent of a single worker and can be reused across organizations.

Question 4 When should TechNova create a different Job?

Answer: When the nature or classification of work is materially different—not merely because the manager, city or incumbent changed.

Why: Over-fragmented Jobs weaken reporting and career structures.

If the business changes…A transfer may change Department or Location while Job stays Software Engineer. A promotion may change Job, Grade, Position or a combination depending on the design.

Simple mental pictureJob tells what work; Position tells which seat; Assignment tells who occupies it and under what conditions.

What does Job do in Oracle?

Can be used by many positions and assignments
May connect to grades or job families
Can be set-enabled

Why is it useful, and when do consultants use it?

Why the business needs it

It standardizes work classification across positions and assignments.

Reusable work definition
Many workers can share one job
Different from Position

When it is used

Workforce taxonomy and Reference Data Set design.

Typical setup task:
Setup and Maintenance → Manage Jobs

Important distinction

Job
What general type of work is performed?

Do not confuse

A Job is general work; a Position is a particular seat. Do not create a new Job for each employee.

How a consultant reasons

Read the business factsIdentify the questionChoose the objectCheck dependenciesTest the impact

Easy exam definition

A Job is a reusable definition of work, such as Software Engineer or HR Specialist.

Memory line: Job tells what work; Position tells which seat; Assignment tells who occupies it and under what conditions.

Connect it to the TechNova design

Business questionWhat general type of work is performed?

TechNova recordSoftware Engineer

Why it existsIt standardizes work classification across positions and assignments.

Certification trapA Job is general work; a Position is a particular seat. Do not create a new Job for each employee.

Check your understanding

Reusable work definition
Many workers can share one job
Different from Position
Supports reporting and progression
Set-enabled

Relationships

Workforce structure

Job

What general type of work is performed?

Relationship map

Enterprise

→

Legal & operational structures

→

Job

→

Worker assignment

Direct relationships

Can be used by many positions and assignments
May connect to grades or job families
Can be set-enabled

Think like a consultant: Identify whether the requirement changes the legal, operational, workforce, or sharing layer before creating or editing this object.

Implementation

Workforce structure

Job

What general type of work is performed?

Implementation purpose

It standardizes work classification across positions and assignments.

Typical setup route

Setup and Maintenance → Manage Jobs
Navigation and page names can vary with enabled Redwood experiences and quarterly updates. Learn the setup task and outcome.

Prerequisites

Workforce taxonomy and Reference Data Set design.

Implementation checklist

Confirm the business owner and exact requirement.
Check whether an existing record can be reused.
Agree naming, codes, effective dates and sharing.
Configure in a test environment.
Validate transactions, security, reporting and integrations.
Document the design decision and migration method.

Technical Details

Workforce structure

Job

What general type of work is performed?

Consultant workspace

Job Technical Details

Configure, migrate, maintain, validate and troubleshoot this object.

Primary technical question

What general type of work is performed?

YesSet-enabled: Yes

1Technical Profile

Oracle role in design	Set-enabled, date-effective reusable work definition
Date behavior	Yes
Set-enabled	Yes
Main setup task	Manage Jobs
Main migration approach	Job.dat
Used by	Can be used by many positions and assignments; May connect to grades or job families; Can be set-enabled

3Prerequisites and Configuration Sequence

Job architecture and naming convention
Reference Data Set strategy
Job family/function and valid-grade decisions

Sequence rule: Complete dependencies and approve stable codes before creating or loading Job.

4Field Dictionary

Field	What it controls	TechNova example	Common mistake
Job code/name Requiredintegration-sensitive	Stable work identifier and display name	SE / Software Engineer	Creating a code per worker
Set code Requiredset-controlled	Controls BU availability	TN_COMMON	Loading into an unassigned set
Job family/function Optionalreporting-sensitive	Groups comparable work	Technology / Engineering	Using Department as Job family
Effective dates/status Date-effective	Controls use	Active from taxonomy launch	Inactivating while active positions depend on it

5UI Configuration Walkthrough

Confirm the reusable work definition independent of person and place.
Create the Job with governed code, set and classification attributes.
Associate valid grades or profiles where designed.
Test on positions and assignments in every consuming BU.

6HDL, HSDL and REST Availability

Method	Status	Best use
Manual UI	Supported	Small volumes
HDL	Supported	Job.dat
HSDL	Check available template	Business spreadsheet maintenance
REST	Check current jobs resource	Integration and automation

Before production: Download the current business-object template or inspect current REST metadata. Release, feature and privilege differences can change supported attributes.

7Sample Data Load with Explanation

METADATA|Job|SourceSystemOwner|SourceSystemId|JobCode|Name|EffectiveStartDate|SetCode|ActiveStatus
MERGE|Job|EXAMNXT|JOB_SE|SE|Software Engineer|<start date>|TN_COMMON|A

Confirm exact attribute names in the current Job business-object template. Source keys must remain stable across name changes.

Source-key ruleKeep SourceSystemOwner and SourceSystemId stable so later MERGE operations update the same record.

Dependency ruleLoad and validate referenced parent records before dependent objects.

8Effective Dating and Maintenance Rules

Correct mistaken history; date a real taxonomy change.
Do not delete a Job used by positions or assignments.
Inactivate for future use after checking future-dated records.
Assess profiles, grades, recruiting and reporting before material changes.

Create

→

Correct an error

→

Update from a date

→

Inactivate safely

9Security and Required Privileges

Set sharing controls Job availability by BU. Functional and data security still control who can maintain or use the relevant transactions.

Diagnostic rule: Separate three questions: Can the user open the function? Can the user maintain this object? Can the user see the relevant secured data?

10Downstream Impact

PositionsEvery Position references a Job

AssignmentsDescribes worker's general work

Talent/recruitingCan link profiles, families and requisitions

Assess current records, future-dated transactions, reports, approvals and integrations before changing a production value.

11Validation Checklist

Job is reusable across people/locations
Set makes it available to intended BUs
Valid grades/profiles are correct
Positions can reference it
Code remains consistent in reports/interfaces

12Troubleshooting Scenarios

Symptom	Likely cause	What to do
Job missing in Position page	Set or date mismatch	Check Position BU and Job set
Duplicate Jobs by department	Job confused with organization	Reuse Job and vary Department/Position
HDL update creates new Job	Source key changed	Reuse original source identifiers

13Technical Consultant Challenge

Three departments need Software Engineers. The team proposes three Jobs. What should you do?

Consultant answer

Use one shared Software Engineer Job when responsibilities are materially the same, then distinguish Department and specific seats through assignments or Positions.

Certification

Workforce structure

Job

What general type of work is performed?

Certification trap

Watch for this: A Job is general work; a Position is a particular seat. Do not create a new Job for each employee.

How to reason through a scenario

Underline the business question.
Identify the layer: legal, operational, workforce, or control.
Remove options that answer a different business question.
Check effective date, reuse, sharing and dependency clues.
Choose the solution that preserves history and avoids duplication.

Revision

Workforce structure

Job

What general type of work is performed?

30-second revision

Job
A Job is a reusable definition of work, such as Software Engineer or HR Specialist.

Example: Software Engineer
Main trap: A Job is general work; a Position is a particular seat. Do not create a new Job for each employee.

Active recall

What general type of work is performed?
Which objects depend on or use Job?
What must exist before it is configured?
Which date, status or sharing controls matter?
What configuration mistake would you warn the client about?

Lesson 15

Grade

What level or rank applies to the work?

Fundamentals

Workforce structure

Grade

What level or rank applies to the work?

TechNova story · What level is the work?

Grade: learn it through a business decision

Priya and Arun are both Software Engineers, but Priya is at Professional Grade P2 and Arun is at P3. Their work family is similar; their level differs.

First principle: A Grade represents a level of compensation, responsibility or progression within the organization.

Pause, decide, then reveal the reasoning

Answer in your own words before opening each explanation.

Question 1 Which object represents the level or rank?

Answer: Grade.

Why: Grade can reflect responsibility, compensation level or progression independently of the Job's general work definition.

Question 2 Is Grade the same as Job title?

Answer: No. Job describes work; Grade describes level.

Why: The same Job may have more than one valid Grade where the design allows it.

Question 3 Why validate grade eligibility?

Answer: Assignments or Positions should use Grades valid for the configured Job/Position and compensation design.

Why: An active Grade is not necessarily valid in every context.

Question 4 Priya receives a pay increase within P2. Must her Grade change?

Answer: Not necessarily.

Why: A compensation change can occur within a Grade; change the Grade only when her level/progression changes according to policy.

If the business changes…Changing Grade may affect compensation eligibility, reporting and progression. Check effective date and downstream plans before processing it.

Simple mental pictureGrade answers 'what level?'—not 'what work?' or 'which seat?'

What does Grade do in Oracle?

May be valid for jobs or positions
Can be arranged in Grade Ladders
Can carry rate-related configuration

Why is it useful, and when do consultants use it?

Why the business needs it

It standardizes levels and can support compensation eligibility and workforce reporting.

Represents level/rank
May link to jobs or positions
Can support compensation

When it is used

Compensation and workforce-level design.

Typical setup task:
Setup and Maintenance → Manage Grades

Important distinction

Grade
What level or rank applies to the work?

Do not confuse

Grade is a level; Job describes work; Position identifies the seat.

How a consultant reasons

Read the business factsIdentify the questionChoose the objectCheck dependenciesTest the impact

Easy exam definition

A Grade represents a level of compensation, responsibility or progression within the organization.

Memory line: Grade answers 'what level?'—not 'what work?' or 'which seat?'

Connect it to the TechNova design

Business questionWhat level or rank applies to the work?

TechNova recordProfessional Grade P2

Why it existsIt standardizes levels and can support compensation eligibility and workforce reporting.

Certification trapGrade is a level; Job describes work; Position identifies the seat.

Check your understanding

Represents level/rank
May link to jobs or positions
Can support compensation
Can be in grade ladders
Not the same as a job title

Relationships

Workforce structure

Grade

What level or rank applies to the work?

Relationship map

Enterprise

→

Legal & operational structures

→

Grade

→

Worker assignment

Direct relationships

May be valid for jobs or positions
Can be arranged in Grade Ladders
Can carry rate-related configuration

Think like a consultant: Identify whether the requirement changes the legal, operational, workforce, or sharing layer before creating or editing this object.

Implementation

Workforce structure

Grade

What level or rank applies to the work?

Implementation purpose

It standardizes levels and can support compensation eligibility and workforce reporting.

Typical setup route

Setup and Maintenance → Manage Grades
Navigation and page names can vary with enabled Redwood experiences and quarterly updates. Learn the setup task and outcome.

Prerequisites

Compensation and workforce-level design.

Implementation checklist

Confirm the business owner and exact requirement.
Check whether an existing record can be reused.
Agree naming, codes, effective dates and sharing.
Configure in a test environment.
Validate transactions, security, reporting and integrations.
Document the design decision and migration method.

Technical Details

Workforce structure

Grade

What level or rank applies to the work?

Consultant workspace

Grade Technical Details

Configure, migrate, maintain, validate and troubleshoot this object.

Primary technical question

What level or rank applies to the work?

YesSet-enabled: Yes

1Technical Profile

Oracle role in design	Set-enabled, date-effective level or rank
Date behavior	Yes
Set-enabled	Yes
Main setup task	Manage Grades
Main migration approach	Grade.dat
Used by	May be valid for jobs or positions; Can be arranged in Grade Ladders; Can carry rate-related configuration

3Prerequisites and Configuration Sequence

Approved grade architecture
Reference Data Set strategy
Rates, valid-grade and ladder design

Sequence rule: Complete dependencies and approve stable codes before creating or loading Grade.

4Field Dictionary

Field	What it controls	TechNova example	Common mistake
Grade code/name Requiredintegration-sensitive	Stable level identifier	P2 / Professional 2	Embedding temporary salary values
Set code Requiredset-controlled	Controls BU availability	TN_COMMON	Using a set unavailable to the BU
Effective dates/status Date-effective	Controls use	Active from framework launch	Ending before assignments end
Rate/valid-grade links Downstream-sensitive	Connects level to compensation/work structures	P2 salary range	Assuming Grade alone sets salary

5UI Configuration Walkthrough

Approve grade hierarchy and codes with HR/compensation.
Create Grades in the correct set and dates.
Configure related rates, valid grades or ladders in dependency order.
Test assignment and compensation eligibility.

6HDL, HSDL and REST Availability

Method	Status	Best use
Manual UI	Supported	Small volumes
HDL	Supported	Grade.dat
HSDL	Check available template	Spreadsheet maintenance
REST	Check current grades resource	Integration and automation

Before production: Download the current business-object template or inspect current REST metadata. Release, feature and privilege differences can change supported attributes.

7Sample Data Load with Explanation

METADATA|Grade|SourceSystemOwner|SourceSystemId|GradeCode|Name|EffectiveStartDate|SetCode|ActiveStatus
MERGE|Grade|EXAMNXT|GRADE_P2|P2|Professional 2|<start date>|TN_COMMON|A

Grade rates and ladder membership can require related components or separate business objects. Load parents before dependent relationships.

Source-key ruleKeep SourceSystemOwner and SourceSystemId stable so later MERGE operations update the same record.

Dependency ruleLoad and validate referenced parent records before dependent objects.

8Effective Dating and Maintenance Rules

Preserve Grade history for workers and compensation.
Use dated updates for genuine framework changes.
Do not inactivate while future assignments or ladders require the Grade.
Assess rates, eligibility and reporting before renaming or re-coding.

Create

→

Correct an error

→

Update from a date

→

Inactivate safely

9Security and Required Privileges

Grade maintenance and compensation-rate access may require different privileges. Set sharing controls BU availability, not compensation-data permission.

Diagnostic rule: Separate three questions: Can the user open the function? Can the user maintain this object? Can the user see the relevant secured data?

10Downstream Impact

Assignments/PositionsRecords worker or seat level

CompensationCan support ranges, rates and eligibility

LaddersProvides ordered progression values

Assess current records, future-dated transactions, reports, approvals and integrations before changing a production value.

11Validation Checklist

Codes/names match approved framework
Set sharing is correct
Rates and valid-grade links are complete
Assignments accept the Grade
Compensation behavior is tested

12Troubleshooting Scenarios

Symptom	Likely cause	What to do
Grade absent from assignment	Set/date or valid-grade restriction	Check BU, date and job/position constraints
Wrong pay expectation	Grade confused with salary amount	Review grade-rate and compensation setup
Ladder load failure	Grade parent not loaded/effective	Load Grade first and align dates

13Technical Consultant Challenge

P2 is visible in one BU but not another, while both use the same career framework. What should you do?

Consultant answer

Check the Grade's SetCode and BU set assignment, then valid-grade rules and effective dates. Do not clone P2 unless the business truly needs a separate value.

Certification

Workforce structure

Grade

What level or rank applies to the work?

Certification trap

Watch for this: Grade is a level; Job describes work; Position identifies the seat.

How to reason through a scenario

Underline the business question.
Identify the layer: legal, operational, workforce, or control.
Remove options that answer a different business question.
Check effective date, reuse, sharing and dependency clues.
Choose the solution that preserves history and avoids duplication.

Revision

Workforce structure

Grade

What level or rank applies to the work?

30-second revision

Grade
A Grade represents a level of compensation, responsibility or progression within the organization.

Example: Professional Grade P2
Main trap: Grade is a level; Job describes work; Position identifies the seat.

Active recall

What level or rank applies to the work?
Which objects depend on or use Grade?
What must exist before it is configured?
Which date, status or sharing controls matter?
What configuration mistake would you warn the client about?

Lesson 16

Grade Ladder

How are grades organized into progression paths?

Fundamentals

Workforce structure

Grade Ladder

How are grades organized into progression paths?

TechNova story · The progression path

Grade Ladder: learn it through a business decision

TechNova has Grades P1, P2 and P3. HR wants to show the valid order of progression instead of relying on alphabetical codes.

First principle: A Grade Ladder orders grades for progression and can support grade-step or progression structures depending on configuration.

Pause, decide, then reveal the reasoning

Answer in your own words before opening each explanation.

Question 1 What organizes these Grades into a progression sequence?

Answer: A Grade Ladder.

Why: The ladder makes the ordered path explicit and can support grade or grade-step progression structures.

Question 2 Can the ladder exist before its Grades?

Answer: The required Grades must be designed and available before they are placed in the ladder.

Why: The ladder organizes existing grade records; it does not replace them.

Question 3 Is a Grade Ladder an organization hierarchy?

Answer: No. It orders workforce levels, not departments or business units.

Why: An Organization Tree and Grade Ladder are both ordered structures, but their members and business purposes differ.

Question 4 Can P2 appear in every ladder automatically?

Answer: No. Membership and sequence are configured according to the ladder's purpose.

Why: Do not assume that an active Grade belongs to every progression path.

If the business changes…When progression policy changes, assess future-effective structure, active assignments and compensation rules rather than simply reordering history.

Simple mental pictureGrades are levels; a Grade Ladder is their ordered progression path.

What does Grade Ladder do in Oracle?

Contains ordered grades
May support assignments and progression
Works with grade and compensation design

Why is it useful, and when do consultants use it?

Why the business needs it

It makes valid career or compensation progression explicit.

Orders grades
Supports progression
Requires existing grades

When it is used

Grades must be designed and available.

Typical setup task:
Setup and Maintenance → Manage Grade Ladders

Important distinction

Grade Ladder
How are grades organized into progression paths?

Do not confuse

A ladder organizes grades; it does not replace jobs, positions or organization trees.

How a consultant reasons

Read the business factsIdentify the questionChoose the objectCheck dependenciesTest the impact

Easy exam definition

A Grade Ladder orders grades for progression and can support grade-step or progression structures depending on configuration.

Memory line: Grades are levels; a Grade Ladder is their ordered progression path.

Connect it to the TechNova design

Business questionHow are grades organized into progression paths?

TechNova recordProfessional Career Ladder: P1 → P2 → P3

Why it existsIt makes valid career or compensation progression explicit.

Certification trapA ladder organizes grades; it does not replace jobs, positions or organization trees.

Check your understanding

Orders grades
Supports progression
Requires existing grades
Sequence matters
Different from organization hierarchy

Relationships

Workforce structure

Grade Ladder

How are grades organized into progression paths?

Relationship map

Enterprise

→

Legal & operational structures

→

Grade Ladder

→

Worker assignment

Direct relationships

Contains ordered grades
May support assignments and progression
Works with grade and compensation design

Think like a consultant: Identify whether the requirement changes the legal, operational, workforce, or sharing layer before creating or editing this object.

Implementation

Workforce structure

Grade Ladder

How are grades organized into progression paths?

Implementation purpose

It makes valid career or compensation progression explicit.

Typical setup route

Setup and Maintenance → Manage Grade Ladders
Navigation and page names can vary with enabled Redwood experiences and quarterly updates. Learn the setup task and outcome.

Prerequisites

Grades must be designed and available.

Implementation checklist

Confirm the business owner and exact requirement.
Check whether an existing record can be reused.
Agree naming, codes, effective dates and sharing.
Configure in a test environment.
Validate transactions, security, reporting and integrations.
Document the design decision and migration method.

Technical Details

Workforce structure

Grade Ladder

How are grades organized into progression paths?

Consultant workspace

Grade Ladder Technical Details

Configure, migrate, maintain, validate and troubleshoot this object.

Primary technical question

How are grades organized into progression paths?

YesSet-enabled: Design-dependent through member Grades

1Technical Profile

Oracle role in design	Date-effective ordered progression structure
Date behavior	Yes
Set-enabled	Design-dependent through member Grades
Main setup task	Manage Grade Ladders
Main migration approach	Grade Ladder HDL business object when exposed in the current template
Used by	Contains ordered grades; May support assignments and progression; Works with grade and compensation design

3Prerequisites and Configuration Sequence

Existing effective Grades
Approved ladder type and order
Progression and compensation rules

Sequence rule: Complete dependencies and approve stable codes before creating or loading Grade Ladder.

4Field Dictionary

Field	What it controls	TechNova example	Common mistake
Name/code Required	Identifies progression structure	Professional Career Ladder	Using a Job or Department name
Ladder type Requireddownstream-sensitive	Controls grade/step behavior	Grade ladder as designed	Choosing type before compensation design
Ordered members Required	Defines P1 → P2 → P3 sequence	P1, P2, P3	Relying on alphabetical order
Effective dates Date-effective	Controls ladder availability	Framework effective date	Members not effective on ladder start

5UI Configuration Walkthrough

Confirm ladder purpose and type.
Validate every member Grade and date.
Create the ladder and add Grades in approved sequence.
Test progression, assignment and compensation processes that consume it.

6HDL, HSDL and REST Availability

Method	Status	Best use
Manual UI	Supported	Primary setup and review
HDL	Check current template	Load ladder parent then child members
HSDL	Check availability	Use only supported spreadsheet
REST	Check current resource	Validate child-order support

Before production: Download the current business-object template or inspect current REST metadata. Release, feature and privilege differences can change supported attributes.

7Sample Data Load with Explanation

LOAD SEQUENCE
1. Grade.dat: P1, P2, P3
2. Grade Ladder parent: Professional Career Ladder
3. Ladder child members: P1 sequence 10; P2 sequence 20; P3 sequence 30
4. Validate effective dates and ordering

Use the current Grade Ladder template for parent and child component names. Never load members before their Grade records exist.

Source-key ruleKeep SourceSystemOwner and SourceSystemId stable so later MERGE operations update the same record.

Dependency ruleLoad and validate referenced parent records before dependent objects.

8Effective Dating and Maintenance Rules

Use dated ladder versions/changes when progression order changes.
Do not remove Grades that active worker processes still require.
Align member and ladder effective dates.
Regression-test compensation or progression after reordering.

Create

→

Correct an error

→

Update from a date

→

Inactivate safely

9Security and Required Privileges

Ladder maintenance may require workforce or compensation setup privileges. Visibility of ladder-driven pay data can require separate compensation security.

Diagnostic rule: Separate three questions: Can the user open the function? Can the user maintain this object? Can the user see the relevant secured data?

10Downstream Impact

ProgressionDefines valid movement order

CompensationCan support grade/step structures

AssignmentsProvides structured grade context

Assess current records, future-dated transactions, reports, approvals and integrations before changing a production value.

11Validation Checklist

All Grades exist and are effective
Member order matches policy
Ladder type is correct
No duplicate/missing member
Progression test follows expected path

12Troubleshooting Scenarios

Symptom	Likely cause	What to do
Member rejected	Grade missing or date mismatch	Load/activate Grade before membership
Wrong progression order	Sequence values incorrect	Correct member sequence with effective change
Salary expected automatically	Ladder confused with compensation plan	Review rate and compensation configuration

13Technical Consultant Challenge

P3 appears before P2 because codes sort alphabetically in a report. What should you do?

Consultant answer

Use the ladder's explicit member sequence for progression logic and correct the consuming report if it ignores that sequence. Do not rename Grades merely to force sorting.

Certification

Workforce structure

Grade Ladder

How are grades organized into progression paths?

Certification trap

Watch for this: A ladder organizes grades; it does not replace jobs, positions or organization trees.

How to reason through a scenario

Underline the business question.
Identify the layer: legal, operational, workforce, or control.
Remove options that answer a different business question.
Check effective date, reuse, sharing and dependency clues.
Choose the solution that preserves history and avoids duplication.

Revision

Workforce structure

Grade Ladder

How are grades organized into progression paths?

30-second revision

Grade Ladder
A Grade Ladder orders grades for progression and can support grade-step or progression structures depending on configuration.

Example: Professional Career Ladder: P1 → P2 → P3
Main trap: A ladder organizes grades; it does not replace jobs, positions or organization trees.

Active recall

How are grades organized into progression paths?
Which objects depend on or use Grade Ladder?
What must exist before it is configured?
Which date, status or sharing controls matter?
What configuration mistake would you warn the client about?

Lesson 17

Position

Which specific workforce seat exists?

Fundamentals

Workforce structure

Position

Which specific workforce seat exists?

TechNova story · The approved seat

Position: learn it through a business decision

TechNova approves ten Backend Software Engineer seats in Bengaluru. Eight are occupied. Two must remain visible as vacancies, and a seat should survive when its incumbent leaves.

First principle: A Position is a specific occurrence of a Job in an organization, often with department, location, grade, headcount and reporting attributes.

Pause, decide, then reveal the reasoning

Answer in your own words before opening each explanation.

Question 1 Which object represents an individual approved seat?

Answer: Position.

Why: A Position is a specific occurrence of a Job and can hold organization, location, grade, headcount and reporting attributes.

Question 2 What happens to the Position when Priya leaves it?

Answer: The Position can remain as a vacant seat for a replacement.

Why: The seat and the person have separate identities and histories.

Question 3 Why not use Job alone for headcount control?

Answer: Job defines reusable work; it does not by itself identify each controlled seat.

Why: Position management supports seat-level vacancy, incumbency and attribute control.

Question 4 Can two Positions reference Software Engineer but differ in Location or Department?

Answer: Yes.

Why: They share the general Job while representing distinct organizational seats.

If the business changes…Before changing a Position, identify incumbents and synchronized attributes. A master-data change can update or constrain several assignments.

Simple mental pictureJob is the blueprint; Position is the numbered seat; worker is the incumbent.

What does Position do in Oracle?

References a Job
Can carry Department, Location and Grade
Can synchronize attributes to worker assignments

Why is it useful, and when do consultants use it?

Why the business needs it

Position management controls approved workforce seats and allows attributes to be inherited or synchronized to assignments.

Specific seat
Can control headcount
References a job

When it is used

Jobs and relevant organizations/locations/grades.

Typical setup task:
My Client Groups / Workforce Structures → Positions or Setup task, depending on enabled experience

Important distinction

Position
Which specific workforce seat exists?

Do not confuse

When a worker leaves, the Position may remain vacant; the Job and Position do not have to be deleted.

How a consultant reasons

Read the business factsIdentify the questionChoose the objectCheck dependenciesTest the impact

Easy exam definition

A Position is a specific occurrence of a Job in an organization, often with department, location, grade, headcount and reporting attributes.

Memory line: Job is the blueprint; Position is the numbered seat; worker is the incumbent.

Connect it to the TechNova design

Business questionWhich specific workforce seat exists?

TechNova recordBackend Software Engineer–BLR–01

Why it existsPosition management controls approved workforce seats and allows attributes to be inherited or synchronized to assignments.

Certification trapWhen a worker leaves, the Position may remain vacant; the Job and Position do not have to be deleted.

Check your understanding

Specific seat
Can control headcount
References a job
May synchronize assignment values
Can remain after incumbent leaves

Relationships

Workforce structure

Position

Which specific workforce seat exists?

Relationship map

Enterprise

→

Legal & operational structures

→

Position

→

Worker assignment

Direct relationships

References a Job
Can carry Department, Location and Grade
Can synchronize attributes to worker assignments

Think like a consultant: Identify whether the requirement changes the legal, operational, workforce, or sharing layer before creating or editing this object.

Implementation

Workforce structure

Position

Which specific workforce seat exists?

Implementation purpose

Position management controls approved workforce seats and allows attributes to be inherited or synchronized to assignments.

Typical setup route

My Client Groups / Workforce Structures → Positions or Setup task, depending on enabled experience
Navigation and page names can vary with enabled Redwood experiences and quarterly updates. Learn the setup task and outcome.

Prerequisites

Jobs and relevant organizations/locations/grades.

Implementation checklist

Confirm the business owner and exact requirement.
Check whether an existing record can be reused.
Agree naming, codes, effective dates and sharing.
Configure in a test environment.
Validate transactions, security, reporting and integrations.
Document the design decision and migration method.

Technical Details

Workforce structure

Position

Which specific workforce seat exists?

Consultant workspace

Position Technical Details

Configure, migrate, maintain, validate and troubleshoot this object.

Primary technical question

Which specific workforce seat exists?

YesSet-enabled: Consumes set-enabled references

1Technical Profile

Oracle role in design	Date-effective specific occurrence of a Job
Date behavior	Yes
Set-enabled	Consumes set-enabled references
Main setup task	Request a New Position / Manage Positions
Main migration approach	Position.dat
Used by	References a Job; Can carry Department, Location and Grade; Can synchronize attributes to worker assignments

3Prerequisites and Configuration Sequence

Existing Job, Department, Location and BU
Position-management and synchronization settings
Headcount, FTE, hierarchy and approval decisions

Sequence rule: Complete dependencies and approve stable codes before creating or loading Position.

4Field Dictionary

Field	What it controls	TechNova example	Common mistake
Position code/name Requiredintegration-sensitive	Stable seat identifier and display name	BE-BLR-01 / Backend Engineer 01	Using incumbent name
Job/Department/Location Downstream-sensitive	Defines work, team and workplace	Software Engineer / Backend / Bengaluru	Using values unavailable to BU
Headcount/FTE Validation-sensitive	Controls incumbent capacity	1 / 1.0	Ignoring overlap rules
Hiring status/dates Date-effective	Controls recruiting and assignment use	Approved and active	Closing before incumbent exit

5UI Configuration Walkthrough

Confirm that the organization uses position management for this population.
Choose start date and reason, then enter seat attributes.
Set headcount, hiring status, hierarchy and synchronization-relevant values.
Submit approvals where enabled and validate assignment inheritance.

6HDL, HSDL and REST Availability

Method	Status	Best use
Manual UI	Supported	Request/create/change Positions
HDL	Supported	Position.dat
HSDL	Check available template	Bulk business maintenance
REST	Supported for documented flows	Validate synchronization and privileges

Before production: Download the current business-object template or inspect current REST metadata. Release, feature and privilege differences can change supported attributes.

7Sample Data Load with Explanation

METADATA|Position|SourceSystemOwner|SourceSystemId|PositionCode|Name|EffectiveStartDate|BusinessUnitName|JobCode|DepartmentName|LocationCode
MERGE|Position|EXAMNXT|POS_BE_BLR_01|BE-BLR-01|Backend Engineer 01|<start date>|Software BU|SE|Backend Development|BLR-DC

Load every referenced object first. Confirm current template keys and whether names, codes or source keys are required for each reference.

Source-key ruleKeep SourceSystemOwner and SourceSystemId stable so later MERGE operations update the same record.

Dependency ruleLoad and validate referenced parent records before dependent objects.

8Effective Dating and Maintenance Rules

A Position can remain vacant after an incumbent leaves.
Use Position change when the seat changes; move the worker when another existing seat is correct.
Deletion is highly constrained once incumbents/history exist; use inactivation/closure.
Validate future incumbents, requisitions and hierarchy before changing dates or capacity.

Create

→

Correct an error

→

Update from a date

→

Inactivate safely

9Security and Required Privileges

Position creation/change can be approval-controlled. Users need functional access plus data access to relevant BUs/organizations; loader access must include the Position business object.

Diagnostic rule: Separate three questions: Can the user open the function? Can the user maintain this object? Can the user see the relevant secured data?

10Downstream Impact

AssignmentsCan synchronize Job, Department, Location and Grade

HeadcountControls approved seats and occupancy

HierarchyCan drive line-manager synchronization

Assess current records, future-dated transactions, reports, approvals and integrations before changing a production value.

11Validation Checklist

All references are effective and visible
Headcount and overlap rules are correct
Approval completed
Synchronization defaults expected attributes
Incumbent validation behaves correctly

12Troubleshooting Scenarios

Symptom	Likely cause	What to do
Position not visible	Approval pending, inactive or security	Check approval, dates and access
Second incumbent rejected	Headcount/overlap rule exceeded	Review capacity and overlap period
HDL reference error	Dependency not loaded or set mismatch	Load valid Job/Department/Location first

13Technical Consultant Challenge

The incumbent resigns, and HR asks to delete the Position. What should you do?

Consultant answer

Keep the Position if the approved seat continues and recruit a replacement. Close/inactivate only when the seat itself is removed, preserving history and validating hierarchy/headcount effects.

Certification

Workforce structure

Position

Which specific workforce seat exists?

Certification trap

Watch for this: When a worker leaves, the Position may remain vacant; the Job and Position do not have to be deleted.

How to reason through a scenario

Underline the business question.
Identify the layer: legal, operational, workforce, or control.
Remove options that answer a different business question.
Check effective date, reuse, sharing and dependency clues.
Choose the solution that preserves history and avoids duplication.

Revision

Workforce structure

Position

Which specific workforce seat exists?

30-second revision

Position
A Position is a specific occurrence of a Job in an organization, often with department, location, grade, headcount and reporting attributes.

Example: Backend Software Engineer–BLR–01
Main trap: When a worker leaves, the Position may remain vacant; the Job and Position do not have to be deleted.

Active recall

Which specific workforce seat exists?
Which objects depend on or use Position?
What must exist before it is configured?
Which date, status or sharing controls matter?
What configuration mistake would you warn the client about?

Lesson 18

Geography

How are countries, states, cities and address boundaries defined?

Fundamentals

Geography & place

Geography

How are countries, states, cities and address boundaries defined?

TechNova story · City or workplace?

Geography: learn it through a business decision

The setup team sees 'Bengaluru' in an address and proposes a Location with the same name. Later, address validation must distinguish country, state, city and the actual TechNova site.

First principle: Geographies define geographical structures and entities used for address entry and validation.

Pause, decide, then reveal the reasoning

Answer in your own words before opening each explanation.

Question 1 What is Bengaluru in the geography model?

Answer: A geographical entity within a country-specific hierarchy.

Why: It helps structure and validate addresses; it is not the employer's named workplace.

Question 2 What represents 'TechNova Bengaluru Development Centre'?

Answer: A Location with an address that uses the configured geography data.

Why: Geography defines the place/boundary; Location represents the business site.

Question 3 Why configure geography structures before many Locations?

Answer: Locations rely on valid, consistent address components and country-specific validation.

Why: A weak geography design causes inconsistent addresses and downstream reporting problems.

Question 4 Does opening a new office create a new city geography?

Answer: Only if the geographical entity is genuinely missing; normally it creates a new Location within an existing geography.

Why: Never duplicate a city to represent different company sites.

If the business changes…A renamed or corrected address component can affect many addresses. Assess shared geography usage before making changes.

Simple mental pictureGeography describes the world; Location describes the organization's site within it.

What does Geography do in Oracle?

Supports Location addresses
Uses country-specific geography structures
Distinct from a business site

Why is it useful, and when do consultants use it?

Why the business needs it

They help Oracle interpret and validate addresses consistently.

Defines areas and boundaries
Supports address validation
Country-specific hierarchy

When it is used

Country/address design.

Typical setup task:
Setup and Maintenance → Manage Geographies

Important distinction

Geography
How are countries, states, cities and address boundaries defined?

Do not confuse

Bengaluru is a geography; TechNova Bengaluru Development Centre is a Location.

How a consultant reasons

Read the business factsIdentify the questionChoose the objectCheck dependenciesTest the impact

Easy exam definition

Geographies define geographical structures and entities used for address entry and validation.

Memory line: Geography describes the world; Location describes the organization's site within it.

Connect it to the TechNova design

Business questionHow are countries, states, cities and address boundaries defined?

TechNova recordIndia → Karnataka → Bengaluru

Why it existsThey help Oracle interpret and validate addresses consistently.

Certification trapBengaluru is a geography; TechNova Bengaluru Development Centre is a Location.

Check your understanding

Defines areas and boundaries
Supports address validation
Country-specific hierarchy
Not a workplace
Often configured before locations

Relationships

Geography & place

Geography

How are countries, states, cities and address boundaries defined?

Relationship map

Enterprise

→

Legal & operational structures

→

Geography

→

Worker assignment

Direct relationships

Supports Location addresses
Uses country-specific geography structures
Distinct from a business site

Think like a consultant: Identify whether the requirement changes the legal, operational, workforce, or sharing layer before creating or editing this object.

Implementation

Geography & place

Geography

How are countries, states, cities and address boundaries defined?

Implementation purpose

They help Oracle interpret and validate addresses consistently.

Typical setup route

Setup and Maintenance → Manage Geographies
Navigation and page names can vary with enabled Redwood experiences and quarterly updates. Learn the setup task and outcome.

Prerequisites

Country/address design.

Implementation checklist

Confirm the business owner and exact requirement.
Check whether an existing record can be reused.
Agree naming, codes, effective dates and sharing.
Configure in a test environment.
Validate transactions, security, reporting and integrations.
Document the design decision and migration method.

Technical Details

Geography & place

Geography

How are countries, states, cities and address boundaries defined?

Consultant workspace

Geography Technical Details

Configure, migrate, maintain, validate and troubleshoot this object.

Primary technical question

How are countries, states, cities and address boundaries defined?

Structure and validation changes require controlled maintenanceSet-enabled: No

1Technical Profile

Oracle role in design	Country address hierarchy and validation data
Date behavior	Structure and validation changes require controlled maintenance
Set-enabled	No
Main setup task	Manage Geographies
Main migration approach	Use the supported geography import process for large country datasets; this is not ordinary workforce HDL
Used by	Supports Location addresses; Uses country-specific geography structures; Distinct from a business site

3Prerequisites and Configuration Sequence

Country and address-style requirements
Authoritative geography source
Decision on validation level and hierarchy

Sequence rule: Complete dependencies and approve stable codes before creating or loading Geography.

4Field Dictionary

Field	What it controls	TechNova example	Common mistake
Geography type Country-controlled	Defines levels such as state/city/postal code	State, City, Postal Code	Inventing levels inconsistent with address style
Name/code Requiredsource-sensitive	Identifies a geography	Karnataka / KA	Using workplace names
Parent geography Required for hierarchy	Builds the hierarchy	Bengaluru under Karnataka	Orphaning a city
Validation level Downstream-sensitive	Controls address enforcement	Validate city and postal code	Turning on strict validation before data cleanup

5UI Configuration Walkthrough

Review the country's geography structure and address style.
Choose an authoritative source and import/configure levels in sequence.
Enable validation appropriate to data quality.
Test valid and invalid Location addresses before production use.

6HDL, HSDL and REST Availability

Method	Status	Best use
Manual UI	Supported	Small corrections
Geography import	Supported	Preferred for large authoritative datasets
HDL	Not primary	Do not use worker-structure templates
REST	Check current service	Use only documented geography resources

Before production: Download the current business-object template or inspect current REST metadata. Release, feature and privilege differences can change supported attributes.

7Sample Data Load with Explanation

GEOGRAPHY LOAD ORDER
1. Country structure
2. State / province records
3. City records
4. Postal codes
5. Address validation test

Use a country-authoritative data source and load parents before children. Geography is not the same object as a business Location.

Source-key ruleKeep SourceSystemOwner and SourceSystemId stable so later MERGE operations update the same record.

Dependency ruleLoad and validate referenced parent records before dependent objects.

8Effective Dating and Maintenance Rules

Assess existing Location addresses before tightening validation.
Do not rename official geographies casually; downstream addresses may depend on them.
Add hierarchy changes through supported geography maintenance.
Retest address entry and integrations after validation changes.

Create

→

Correct an error

→

Update from a date

→

Inactivate safely

9Security and Required Privileges

Geography setup is a specialist setup function. General users may consume address validation without having permission to maintain the geography master.

Diagnostic rule: Separate three questions: Can the user open the function? Can the user maintain this object? Can the user see the relevant secured data?

10Downstream Impact

LocationsValidates business-site addresses

Person addressesSupports consistent address entry

IntegrationsStandardizes country/state/city codes

Assess current records, future-dated transactions, reports, approvals and integrations before changing a production value.

11Validation Checklist

Hierarchy matches country address structure
Parent-child relationships are complete
Valid addresses pass
Invalid combinations are rejected as designed
Existing addresses remain usable

12Troubleshooting Scenarios

Symptom	Likely cause	What to do
City not selectable	Parent level missing or validation not enabled	Review hierarchy and country setup
Valid address rejected	Overly strict or incomplete geography data	Correct source data/validation level
Location duplicates city record	Geography confused with workplace	Create one geography and separate business Location

13Technical Consultant Challenge

After strict validation is enabled, existing worker and Location addresses start failing updates. What should you do?

Consultant answer

Audit existing data against the new hierarchy, correct missing official geographies, and phase validation deliberately. Do not weaken structure blindly or create workplace records as geography substitutes.

Certification

Geography & place

Geography

How are countries, states, cities and address boundaries defined?

Certification trap

Watch for this: Bengaluru is a geography; TechNova Bengaluru Development Centre is a Location.

How to reason through a scenario

Underline the business question.
Identify the layer: legal, operational, workforce, or control.
Remove options that answer a different business question.
Check effective date, reuse, sharing and dependency clues.
Choose the solution that preserves history and avoids duplication.

Revision

Geography & place

Geography

How are countries, states, cities and address boundaries defined?

30-second revision

Geography
Geographies define geographical structures and entities used for address entry and validation.

Example: India → Karnataka → Bengaluru
Main trap: Bengaluru is a geography; TechNova Bengaluru Development Centre is a Location.

Active recall

How are countries, states, cities and address boundaries defined?
Which objects depend on or use Geography?
What must exist before it is configured?
Which date, status or sharing controls matter?
What configuration mistake would you warn the client about?

Lesson 19

Location

Where is the organization, position or worker physically based?

Fundamentals

Geography & place

Location

Where is the organization, position or worker physically based?

TechNova story · Where does Priya work?

Location: learn it through a business decision

Priya works at TechNova Bengaluru Development Centre. The same Department also has workers in Mumbai, and hundreds of assignments reuse each workplace.

First principle: A Location represents a physical business site or workplace with address information.

Pause, decide, then reveal the reasoning

Answer in your own words before opening each explanation.

Question 1 Why not type the address independently on every worker?

Answer: A reusable Location provides a governed workplace value for assignments, positions and organizations.

Why: Reuse improves consistency, reporting and maintenance.

Question 2 Is the Location the same as the Department?

Answer: No. Location answers where; Department answers which team.

Why: One Department may operate from several Locations, and one Location may host several Departments.

Question 3 The Bengaluru office closes. Should the Location be deleted?

Answer: Normally inactivate or end-date it appropriately while preserving historical references.

Why: Used master data supports history. Deleting or overwriting it can damage past reporting and transactions.

Question 4 The office moves to another building. Is this always a simple address overwrite?

Answer: No. Determine whether it is a dated change to the same business site or a distinct new Location needed for history and reporting.

Why: Business identity and historical requirements drive the choice.

If the business changes…Location changes can flow from a synchronized Position or be entered on an Assignment. Check the controlling configuration before assuming manual entry wins.

Simple mental pictureLocation is a reusable physical workplace, built on geography and often shared through a Reference Data Set.

What does Location do in Oracle?

Uses geography/address data
Can be set-enabled
May default from a synchronized position

Why is it useful, and when do consultants use it?

Why the business needs it

It provides a reusable, consistent workplace value for organizations, positions, assignments, schedules and requisitions.

Physical workplace
Reusable by many workers
Different from Geography

When it is used

Valid address/geography and Reference Data Set strategy.

Typical setup task:
Setup and Maintenance → Manage Locations

Important distinction

Location
Where is the organization, position or worker physically based?

Do not confuse

Do not create one Location per worker or one Department per Location.

How a consultant reasons

Read the business factsIdentify the questionChoose the objectCheck dependenciesTest the impact

Easy exam definition

A Location represents a physical business site or workplace with address information.

Memory line: Location is a reusable physical workplace, built on geography and often shared through a Reference Data Set.

Connect it to the TechNova design

Business questionWhere is the organization, position or worker physically based?

TechNova recordTechNova Bengaluru Development Centre

Why it existsIt provides a reusable, consistent workplace value for organizations, positions, assignments, schedules and requisitions.

Certification trapDo not create one Location per worker or one Department per Location.

Check your understanding

Physical workplace
Reusable by many workers
Different from Geography
Set-enabled
Date-effective and normally inactivated, not deleted

Relationships

Geography & place

Location

Where is the organization, position or worker physically based?

Relationship map

Enterprise

→

Legal & operational structures

→

Location

→

Worker assignment

Direct relationships

Uses geography/address data
Can be set-enabled
May default from a synchronized position

Think like a consultant: Identify whether the requirement changes the legal, operational, workforce, or sharing layer before creating or editing this object.

Implementation

Geography & place

Location

Where is the organization, position or worker physically based?

Implementation purpose

It provides a reusable, consistent workplace value for organizations, positions, assignments, schedules and requisitions.

Typical setup route

Setup and Maintenance → Manage Locations
Navigation and page names can vary with enabled Redwood experiences and quarterly updates. Learn the setup task and outcome.

Prerequisites

Valid address/geography and Reference Data Set strategy.

Implementation checklist

Confirm the business owner and exact requirement.
Check whether an existing record can be reused.
Agree naming, codes, effective dates and sharing.
Configure in a test environment.
Validate transactions, security, reporting and integrations.
Document the design decision and migration method.

Technical Details

Geography & place

Location

Where is the organization, position or worker physically based?

Consultant workspace

Location Technical Details

Configure, migrate, maintain, validate and troubleshoot this object.

Primary technical question

Where is the organization, position or worker physically based?

YesSet-enabled: Yes

1Technical Profile

Oracle role in design	Set-enabled, date-effective workplace
Date behavior	Yes
Set-enabled	Yes
Main setup task	Manage Locations
Main migration approach	Location.dat
Used by	Uses geography/address data; Can be set-enabled; May default from a synchronized position

3Prerequisites and Configuration Sequence

Valid country/address and geography design
Reference Data Set assignment
Stable location code and operating date

Sequence rule: Complete dependencies and approve stable codes before creating or loading Location.

4Field Dictionary

Field	What it controls	TechNova example	Common mistake
Location code/name Requiredintegration-sensitive	Stable key and user-facing workplace	BLR-DC / Bengaluru Development Centre	Creating one per employee
Effective start/status Date-effective	Controls availability	Active from office opening	Starting after position dates
Set code Requiredset-controlled	Controls BU sharing	TN_COMMON	Using a BU-specific set unintentionally
Address Country-controlled	Defines the physical site	Validated Bengaluru address	Entering only the city name

5UI Configuration Walkthrough

Validate the physical address and geography first.
Create the Location with stable code, set and effective date.
Add contact or shipping details only when required.
Test visibility on assignments, positions and requisitions in intended BUs.

6HDL, HSDL and REST Availability

Method	Status	Best use
Manual UI	Supported	Small volumes
HDL	Supported	Location.dat
HSDL	Check available template	Spreadsheet load where exposed
REST	Check current locations resource	Integration and automation

Before production: Download the current business-object template or inspect current REST metadata. Release, feature and privilege differences can change supported attributes.

7Sample Data Load with Explanation

METADATA|Location|SourceSystemOwner|SourceSystemId|LocationCode|LocationName|EffectiveStartDate|SetCode|Country
MERGE|Location|EXAMNXT|LOC_BLR_DC|BLR-DC|Bengaluru Development Centre|<start date>|TN_COMMON|IN

Add the current template's required address components. Reuse the same source keys for later updates even if the display name changes.

Source-key ruleKeep SourceSystemOwner and SourceSystemId stable so later MERGE operations update the same record.

Dependency ruleLoad and validate referenced parent records before dependent objects.

8Effective Dating and Maintenance Rules

Use Correction for wrong history and Update for a genuine dated change.
Do not delete an in-use Location; inactivate it for future selection.
Changing an address may affect reporting, taxation, recruiting and integrations.
Validate future positions and assignments before closing a site.

Create

→

Correct an error

→

Update from a date

→

Inactivate safely

9Security and Required Privileges

Location sharing depends on sets and BU context; page/function access and worker data security remain separate.

Diagnostic rule: Separate three questions: Can the user open the function? Can the user maintain this object? Can the user see the relevant secured data?

10Downstream Impact

AssignmentsRecords where work occurs

PositionsCan default/synchronize workplace

Recruiting/schedulesSupports requisitions and work patterns

Assess current records, future-dated transactions, reports, approvals and integrations before changing a production value.

11Validation Checklist

Address passes validation
Set assignment exposes the Location
Code is stable and unique
Position/assignment dates are valid
Reports and integrations receive expected address

12Troubleshooting Scenarios

Symptom	Likely cause	What to do
Location absent from LOV	Set/date/status mismatch	Check BU set assignment and transaction date
HDL duplicate	Source keys changed between loads	Reuse SourceSystemOwner/Id
Address rejected	Geography hierarchy incomplete	Correct geography or address data

13Technical Consultant Challenge

A renamed office was loaded with a new SourceSystemId, creating a duplicate. What should you do?

Consultant answer

Retain the original source keys and MERGE an effective-dated name/address change. Then assess and retire the accidental duplicate without damaging references.

Certification

Geography & place

Location

Where is the organization, position or worker physically based?

Certification trap

Watch for this: Do not create one Location per worker or one Department per Location.

How to reason through a scenario

Underline the business question.
Identify the layer: legal, operational, workforce, or control.
Remove options that answer a different business question.
Check effective date, reuse, sharing and dependency clues.
Choose the solution that preserves history and avoids duplication.

Revision

Geography & place

Location

Where is the organization, position or worker physically based?

30-second revision

Location
A Location represents a physical business site or workplace with address information.

Example: TechNova Bengaluru Development Centre
Main trap: Do not create one Location per worker or one Department per Location.

Active recall

Where is the organization, position or worker physically based?
Which objects depend on or use Location?
What must exist before it is configured?
Which date, status or sharing controls matter?
What configuration mistake would you warn the client about?

Configuring Core HCM

What this course covers

Enterprise

Fundamentals

Enterprise

Enterprise: learn it through a business decision

Pause, decide, then reveal the reasoning

What does Enterprise do in Oracle?

Why is it useful, and when do consultants use it?

Why the business needs it

When it is used

Important distinction

How a consultant reasons

Easy exam definition

Connect it to the TechNova design

Check your understanding

Relationships

Enterprise

Relationship map

Direct relationships

Implementation

Enterprise

Implementation purpose

Typical setup route

Prerequisites

Implementation checklist

Technical Details

Enterprise

Enterprise Technical Details

1Technical Profile

2Setup Navigation

3Prerequisites and Configuration Sequence

4Field Dictionary

5UI Configuration Walkthrough

6HDL, HSDL and REST Availability

7Sample Data Load with Explanation

8Effective Dating and Maintenance Rules

9Security and Required Privileges

10Downstream Impact

11Validation Checklist

12Troubleshooting Scenarios

13Technical Consultant Challenge

Certification

Enterprise

Certification trap

How to reason through a scenario

Revision

Enterprise

30-second revision

Active recall

Legal Entity

Fundamentals

Legal Entity

Legal Entity: learn it through a business decision

Pause, decide, then reveal the reasoning

What does Legal Entity do in Oracle?

Why is it useful, and when do consultants use it?

Why the business needs it

When it is used

Important distinction

How a consultant reasons

Easy exam definition

Connect it to the TechNova design

Check your understanding

Relationships

Legal Entity

Relationship map

Direct relationships

Implementation

Legal Entity

Implementation purpose

Typical setup route

Prerequisites

Implementation checklist

Technical Details

Legal Entity

Legal Entity Technical Details

1Technical Profile

2Setup Navigation

3Prerequisites and Configuration Sequence