Oracle 1Z0-1046-25 Online Practice Questions and Exam Preparation

Oracle 1Z0-1046-25 Online Questions & Answers

• Question 171:

  A human resource specialist is promoting an employee. While promoting an employee, the human resource specialist is required to enter the promotion date, promotion action, and promotion reason. However, the promotion reason list of values does not list an appropriate reason.

  Which two options can help the human resource specialist understand the Action framework available in the application? (Choose two.)

  A. Action Reasons are seeded and can be defined by a user
  B. Action Types are seeded and cannot be defined by a user
  C. Actions are seeded and cannot be defined by a user
  D. Action Reasons are seeded and cannot be defined by a user
  A. Action Reasons are seeded and can be defined by a user
  B. Action Types are seeded and cannot be defined by a user

  ---

  The Action framework in Oracle Global Human Resources Cloud governs transactions like promotions. The "Managing Workforce Records" guide explains:

  Action Reasons: Some are seeded (predefined by Oracle), but users can define additional custom Action Reasons to meet specific business needs (e.g., a new promotion reason like "Merit-Based"). This makes Option A correct.

  Action Types: These are seeded (e.g., Promotion, Transfer) and cannot be user-defined, as they are core to the system's structure, making Option B correct.

  Actions: While seeded Actions exist, users can create custom Actions and link them to Action Types, so Option C is incorrect.

  Oracle Global Human Resources Cloud - Managing Workforce Records, "Actions and Action Reasons" section.

• Question 172:

  Manage Business Unit

  Scenario

  An additional business unit is required for the newly acquired company to reflect the business rules and policies that must be enforced within the organization.

  Task

  Create a Business Unit for the technician group, where:

  1. The Code is x Tech Business Unit

  2. The Default set is COMMON

  A. See the solution in explanation below.
  B. PlaceHolder
  C. PlaceHolder
  D. PlaceHolder
  A. See the solution in explanation below.

  ---

  This task requires creating a business unit in Oracle Global Human Resources Cloud for the technician group of a newly acquired company. The business unit must have a Code of x Tech Business Unit and a Default Set of COMMON. Below is a verified, step-by-step solution based on Oracle's official documentation, ensuring accuracy and compliance with the system's functionality as of the latest releases.

  Step-by-Step Solution

  Step 1: Log in to Oracle Fusion Applications

  Action: Log in to Oracle Fusion Applications using a user account with privileges such as Application Implementation Consultant or HCM Application Administrator. These roles grant access to the Setup and Maintenance work area.

  The Setup and Maintenance work area is the central hub for configuration tasks, including managing business units. The user must have permissions to access the Workforce Structures functional area and the Manage Business Unit task. Roles like Application Implementation Consultant include the necessary privileges (e.g., Manage Business Unit duty role).

  Verification: Oracle documentation confirms that setup tasks require specific security roles, and the Manage Business Unit task is restricted to authorized users.

  Oracle Global Human Resources Cloud: Implementing Global Human Resources, Section: Security for Setup Tasks.

  Step 2: Navigate to Setup and Maintenance

  Action:

  From the Oracle Fusion Applications home page, click the Navigator icon (hamburger menu) in the top-left corner.

  Under the Tools section, select Setup and Maintenance.

  The Setup and Maintenance work area provides access to all implementation and configuration tasks, organized by functional areas. This is the entry point for accessing the Manage Business Unit task.

  Verification: Oracle's user interface consistently places Setup and Maintenance under the Navigator's Tools section, as confirmed in both Redwood and responsive interfaces.

  Oracle Global Human Resources Cloud: Implementing Global Human Resources, Section: Setup and Maintenance Overview.

  Step 3: Select the Workforce Structures Functional Area and Locate the Task

  Action:

  In the Setup and Maintenance work area, click the Functional Area dropdown and select Workforce Structures.

  In the task list, locate Manage Business Unit by scrolling or using the search bar (type "Manage Business Unit").

  Click the Go to Task icon (typically a play button or arrow) next to Manage Business Unit to open the task.

  The Workforce Structures functional area includes tasks related to organizations, including business units. The Manage Business Unit task is designed to create and manage business units, which enforce business rules and policies. Using the search bar ensures quick access if the task list is extensive.

  Verification: Oracle documentation lists Manage Business Unit under Workforce Structures, accessible via the Setup and Maintenance UI in both Redwood and responsive interfaces.

  Oracle Global Human Resources Cloud: Using Global Human Resources, Section: Manage Business Unit.

  Step 4: Initiate Creation of a New Business Unit

  Action:

  On the Manage Business Unit page, click the Create button (typically a plus sign (+) or labeled "Create" in the Redwood interface).

  This opens the Create Business Unit page for entering the business unit details.

  The Manage Business Unit page displays a searchable list of existing business units. The Create action starts the process of adding a new business unit, opening a form where the code, name, and default set can be specified.

  Verification: Oracle's UI for managing business units includes a Create button, as confirmed in documentation and Redwood interface updates (24C and later).

  Oracle Global Human Resources Cloud: Implementing Global Human Resources, Section:Creating Business Units.

  Step 5: Enter the Business Unit Details

  Action:

  On the Create Business Unit page, enter the following details as provided in the scenario:

  Name: Enter x Tech Business Unit.

  Code: Enter x Tech Business Unit.

  Default Set: Search for and select COMMON.

  Click the Search icon (magnifying glass) in the Default Set field.

  Enter COMMON in the search criteria and click Search.

  Select COMMON and click OK.

  Status: Ensure Active is selected (default setting).

  Effective Start Date: Enter 04/15/2025 (current date, unless a specific date is required for the technician group).

  Description (optional): Enter a description, e.g., "Business unit for x Cloud Vision technician group".

  Country: Select United States (based on the company's location in Michigan, as per prior tasks).

  Name and Code: In Oracle HCM Cloud, the Name and Code for a business unit are often the same forclarity, and the scenario specifies x Tech Business Unit for the code, which is used as the name as well. The code is a unique identifier in the system. Default Set: The COMMON set is a predefined reference data set used to share jobs, departments, locations, and grades across multiple business units. Selecting COMMON ensures the technician group's workforce structures are accessible

  broadly unless restricted later.

  Status: Active ensures the business unit is immediately usable for transactions and policies.

  Effective Start Date: Oracle uses effective dating for business units to track validity. The current date (04/15/2025) is appropriate unless otherwise specified.

  Description: While optional, a description aids in identifying the business unit's purpose, especially for the technician group.

  Country: United States aligns with the company's Michigan location, ensuring compliance with regional settings.

  Verification: Oracle documentation specifies mandatory fields (Name, Code, Default Set, Country) and optional fields (Description) for business unit creation. The COMMON set is a standard option, and the details align with US-based configurations.

  Oracle Global Human Resources Cloud: Using Global Human Resources, Section: Business Unit Fields.

  Step 6: Configure Additional Settings (if prompted)

  Action:

  Reporting Establishment: If prompted, leave blank or select an existing establishment tied to the legal entity, but this is not required by the scenario.

  Manager: If a manager field appears, leave blank, as no manager is specified.

  Payroll Statutory Unit: If prompted, leave blank, as the PSU is handled by the legal entity (x Cloud Vision)

  Reporting Establishment: Business units may link to establishments for reporting, but the scenario does not require this.

  Manager: Assigning a manager is optional and not specified here.

  Payroll Statutory Unit: The PSU is already set at the legal entity level, so no additional PSU configuration is needed for the business unit.

  Verification: Oracle documentation confirms that fields like Reporting Establishment are optional, and PSU settings are typically managed at the legal entity level.

  Oracle Global Human Resources Cloud: Implementing Global Human Resources, Section: Business Unit Configurations.

  Step 7: Save the Business Unit

  Action:

  After entering all details, click Save and Close (or Save if further edits are needed).

  If prompted, confirm the creation of the business unit.

  Saving creates the business unit in the system, making it available for enforcing business rules and policies for the technician group. The Save and Close button finalizes the task, while Save allows additional configurations if needed. Oracle validates mandatory fields before saving.

  Verification: Oracle's UI includes Save and Save and Close options for business unit creation, as confirmed in documentation for both responsive and Redwood interfaces.

  Oracle Global Human Resources Cloud: Implementing Global Human Resources, Section: Saving Business Units.

  Step 8: Verify the Business Unit Creation

  Action:

  Return to the Manage Business Unit page.

  In the search criteria, enter x Tech Business Unit and click Search.

  Confirm that the new business unit appears with the details:

  Name: x Tech Business Unit

  Code: x Tech Business Unit

  Default Set: COMMON

  Status: Active

  Effective Start Date: 04/15/202. Country: United States

  Description (if entered): Business unit for x Cloud Vision technician group

  Verification ensures the business unit was created correctly and is ready to enforce rules for the technician group. Searching by name or code confirms the record's accuracy and checks for errors in data entry.

  Verification: Oracle documentation emphasizes verifying setup tasks by searching created records, and the Manage Business Unit page supports detailed searches.

  Oracle Global Human Resources Cloud: Using Global Human Resources, Section: Searching Business Units.

  Step 9: Prepare for Business Rules and Policies (Optional)

  Action:

  Note that the x Tech Business Unit can now be used in tasks like Manage HCM Role Provisioning Rules, Manage Approval Policies, or Manage Data Access to define specific rules and policies for the technician group.

  For example, assign the business unit to specific departments or jobs in the Manage Departments or Manage Jobs tasks to align with the technician group's scope.

  The scenario mentions enforcing business rules and policies, which occurs after business unit creation in separate tasks. The x Tech Business Unit is now available for these configurations, ensuring the technician group operates under tailored settings (e.g., approval workflows, data access). This step is optional, as the task focuses on creation, but it highlights the business unit's purpose.

  Verification: Oracle documentation confirms that business units are used to scope rules and policies, and the created unit will appear in relevant setup tasks.

  Oracle Global Human Resources Cloud: Implementing Global Human Resources, Section: Using Business Units.

  Detailed

  Purpose of Business Units: Business units organize business functions (e.g., HR, payroll, approvals) and enforce rules and policies. The x Tech Business Unit ensures the technician group operates under specific settings, supporting the acquired company's integration. Default Set (COMMON): The COMMON set allows the business unit to share jobs, departments, locations, and grades across the enterprise, reducing setup complexity unless isolation is needed (e.g., via xTECH from). This aligns with broad

  accessibility for the technician group.

  Code and Name: The Code (x Tech Business Unit) is a unique system identifier, and the Name matches for consistency, as is common in Oracle HCM configurations.

  Country Context: United States ties the business unit to the company's Michigan operations, ensuring compliance with regional settings.

  Redwood Interface: In the Redwood interface (24C and later), the Manage Business Unit page may feature enhanced UI elements (e.g., streamlined forms, inline validation), but the fields and steps remain consistent with the responsive interface.

  Effective Dating: The effective start date ensures the business unit is active, supporting future changes if the technician group's scope evolves.

  Key Considerations

  Accuracy: The Code and Name (x Tech Business Unit) and Default Set (COMMON) must be entered exactly as specified to ensure system recognition and alignment with the scenario.

  Uniqueness: The Code must be unique. If x Tech Business Unit exists, an error occurs, requiring a unique code.

  Default Set Availability: The COMMON set is a standard Oracle set. If not found, it indicates a configuration issue, as COMMON is always available.

  Security: Only users with the Manage Business Unit privilege can perform this task. Role mismatches require administrative intervention.

  Policy Setup: The business unit is ready for rule enforcement, but additional tasks (e.g., approval policies) are needed to fully implement the scenario's intent.

  Potential Challenges and Solutions

  Access Denied: If the user lacks the Manage Business Unit privilege, an error occurs.

  Solution: Assign the Application Implementation Consultant role via Security Console.

  Duplicate Code: If x Tech Business Unit already exists, the system prevents saving. Solution: Search for the code first; if it exists, coordinate with the implementation team to resolve conflicts or use a different code.

  Redwood UI Variations: The Redwood interface may use different button labels (e.g., Add instead of Create) or layouts. Solution: Follow field prompts and ensure Code and Default Set are completed.

  COMMON Set Not Found: If COMMON is missing, it may indicate a corrupted setup. Solution: Verify set availability in Manage Reference Data Sets or contact Oracle Support.

  Country Selection: If United States is not selected, regional settings may misalign. Solution: Confirm United States to match the Michigan context.

  References

  Oracle Global Human Resources Cloud: Implementing Global Human Resources, Document ID: docs.oracle.com, Published: 2023-12-1. Section: Manage Business Unit: "Steps to create business units, including code, name, and default set."

  Section: Business Units in Workforce Structures: "Explains how business units enforce rules and policies."

  Oracle Global Human Resources Cloud: Using Global Human Resources, Document ID: docs.oracle.com, Published: 2024-07-02

  Section: Creating Business Units: "Details on configuring business units for organizational functions."

  Section: Reference Data Sets: "Use of COMMON set for shared data access."

  Oracle Fusion Cloud Human Resources 24C What's New, Document ID: docs.oracle.com, Published:2024-08-2. Section: Redwood Experience for Workforce Structures: "Improved UI for business unit management."

  Oracle Fusion Cloud Human Resources 25A What's New, Document ID: docs.oracle.com, Published:2025-03-2. Section: Workforce Structures: "Enhanced support for business unit configurations.

• Question 173:

  Which statement is true about Work Relationships in Oracle Global Human Resources Cloud?

  A. A worker can have only one work relationship under each enterprise.
  B. Terminating a work relationship automatically deletes all associated assignments.
  C. A person can maintain multiple work relationships under different legal employers.
  D. A contingent worker cannot be converted to an employee.
  C. A person can maintain multiple work relationships under different legal employers.

  ---

  Work relationships define a worker's connection to a legal employer.

  Option C is correct-workers can hold separate work relationships for each legal employer within the enterprise.

  Option A is incorrect-multiple work relationships may exist across legal employers.

  Option B is incorrect-termination does not delete data; it end-dates assignments.

  Option D is incorrect-contingent workers can be converted using the appropriate action.

  Implementing Global Human Resources - Work Relationships.

• Question 174:

  In Global Human Resources, which two options are true about configuring Employment Model at the legal employer level? (Choose two.)

  A. It overrides the enterprise-level employment model if configured.
  B. It determines whether a worker can have multiple assignments under the same legal employer.
  C. It controls whether assignment-level position synchronization is enabled.
  D. It cannot differ from the enterprise-level configuration.
  A. It overrides the enterprise-level employment model if configured.
  B. It determines whether a worker can have multiple assignments under the same legal employer.

  ---

  The employment model defines the structure of work relationships, terms, and assignments.

  Option A is correct because a legal employer can override the enterprise-level setting, allowing different employment structures across legal employers. Option B is correct-employment model determines if a worker can hold multiple concurrent assignments, impacting the Add Assignment action. Option C is incorrect because position synchronization is configured independently in Enterprise HCM Information.

  Option D is incorrect-Oracle permits variations across legal employers for flexibility.

  Oracle Global Human Resources Cloud: Implementing Global Human Resources - Employment Model Configuration.

• Question 175:

  Contextual Journeys are displayed:

  A. Only on Thursdays
  B. When initiating a Quick Action
  C. In page or section headers
  D. Via the employees' "Journeys" tile
  C. In page or section headers

  ---

  Contextual Journeys in Oracle Global Human Resources Cloud provide relevant guidance or tasks based on the user's current context within the application. Per the "Using Journeys" guide, these journeys are displayed in page or section headers, appearing dynamically when a user is on a relevant page (e.g., during a promotion process, a Contextual Journey might appear in the transaction header). This distinguishes them from Guided Journeys, which are accessed via the Journeys tile. Option A (only on

  Thursdays) is nonsensical and incorrect. Option B (Quick Action) relates to transaction initiation, not Contextual Journeys. Option D (Journeys tile) applies to Guided Journeys, not Contextual ones. Thus, Option C is correct.

  Oracle Global Human Resources Cloud - Using Journeys, "Contextual Journeys Overview" section.

• Question 176:

  Your organization needs to be able to select the action of Legal Employer Transfer on the employment record to move a worker from one legal employer to another. What configuration will you need to do to make this possible?

  A. Create a new action type of Legal Employer Transfer, and then create a new action of Legal Employer Transfer and associate it with the new action type.
  B. Create a new action called Legal Employer Transfer and associate it with the action type of Global Transfer.
  C. Modify the delivered action of Transfer and associate it with the action type of Global Transfer.
  D. Create a new action called Legal Employer Transfer and associate it with the action type of Legal Entity Transfer.
  B. Create a new action called Legal Employer Transfer and associate it with the action type of Global Transfer.

  ---

  In Oracle Global Human Resources Cloud, transferring a worker between legal employers requires an appropriate action linked to an action type, managed via "Manage Actions."

  Option A: Incorrect. You cannot create new action types; they are seeded (e.g., Transfer, Hire). Only actions can be created under existing types.

  Option B: Correct. Create a new action "Legal Employer Transfer" and associate it with the seeded "Global Transfer" action type, which supports cross-legal-employer movements while retaining the person record.

  Option C: Incorrect. Modifying the delivered "Transfer" action risks affecting its standard behavior; a new action is cleaner.

  Option D: Incorrect. There is no seeded "Legal Entity Transfer" action type; "Global Transfer" is the appropriate type.

  The correct answer is B, per "Implementing Global Human Resources" on employment actions.

  References: Oracle Global Human Resources Cloud - Implementing Global Human Resources, Chapter 6: Actions and Action Types.

• Question 177:

  Which four objects can be created via the Enterprise Structure Configurator (ESC)?

  A. Divisions
  B. Departments
  C. Legal Entities
  D. Business Units
  E. Reference Data Sets
  A. Divisions
  C. Legal Entities
  D. Business Units
  E. Reference Data Sets

  ---

  The Enterprise Structure Configurator (ESC) in Oracle HCM Cloud is a tool for efficiently creating and managing enterprise structures. It supports the creation of:

  Divisions (A): Organizational units for segmenting the business.

  Legal Entities (C): Entities with legal standing for employment and payroll.

  Business Units (D): Operational units for managing transactions.

  Reference Data Sets (E): Sets for sharing data across business units.

  Oracle HCM Cloud: Implementing Global Human Resources, "Enterprise Structure Configurator".

• Question 178:

  Grade structures (grades, grade rates, and grade ladder) were configured for your customer and the required employee assignment data was migrated to the system. However, there was a change in requirement and the customer decided to delete some grades because they were no longer used. When you try to delete one such grade from the system, the system throws an error. Identify three possible reasons for the system error. (Choose three.)

  A. There are assignment records of one or more employees associated with this grade.
  B. The grade has grade rates defined.
  C. The grade is linked to a grade ladder.
  D. A grade cannot be deleted and can only be made inactive by changing the status to "Inactive".
  E. A grade cannot be deleted and can only be end-dated.
  A. There are assignment records of one or more employees associated with this grade.
  B. The grade has grade rates defined.
  C. The grade is linked to a grade ladder.

  ---

  In Oracle HCM Cloud, grades are part of the compensation and job structure. Deleting a grade is restricted if it's referenced elsewhere in the system.

  Option A ("There are assignment records of one or more employees associated with this grade"): True. If an employee's assignment references the grade, deletion is blocked to maintain data integrity, per the "Implementing Global Human Resources" guide.

  Option B ("The grade has grade rates defined"): True. Grade rates (e.g., salary ranges) linked to the grade prevent deletion until removed.

  Option C ("The grade is linked to a grade ladder"): True. Grades in a grade ladder (progression structure) cannot be deleted until unlinked.

  Option D ("A grade cannot be deleted and can only be made inactive by changing the status to 'Inactive'"):

  False. Grades can be deleted if no dependencies exist; inactivation is an alternative, not a requirement.

  Option E ("A grade cannot be deleted and can only be end-dated"): False. End-dating is an option, but deletion is possible if constraints are cleared.

  References:

  "Oracle Global Human Resources Cloud: Implementing Global Human Resources" - Grade management and dependencies.

  "Oracle Human Resources Cloud: Using Workforce Structures" - Grade deletion rules.

• Question 179:

  Which new field has been added to the Redwood Person Spotlight search and Quick Actions to enhance the person search functionality?

  A. Person Number
  B. Job Title
  C. Department
  A. Person Number

  ---

  The Redwood Person Spotlight search and Quick Actions in Oracle HCM Cloud enhance user experience by improving person search functionality. The question asks which new field has been added to these features to enhance search capabilities.

  Option A: Person NumberThis is the correct answer. Oracle's 24C release notes specify that the Person Number field has been added to the Redwood Person Spotlight search and Quick Actions. This allows users to search for individuals using their unique person number (e.g., EMP12345), improving precision and speed in locating employee records, especially in large organizations. The addition of Person Number enhances the search functionality by providing a direct identifier, complementing existing

  fields like name or email.

  Option B: Job TitleThis option is incorrect. While Job Title is a searchable attribute in some HCM search contexts, Oracle's 24C and 25A release notes do not indicate that it was newly added to the Redwood Person Spotlight search or Quick Actions. Job title may already be part of other search criteria, but it is not highlighted as a new enhancement for this feature.

  Option C: DepartmentThis option is incorrect. Department is a common attribute in HCM searches, but there is no mention in Oracle's recent documentation of it being added as a new field to the

  Redwood Person Spotlight search or Quick Actions. The focus of the enhancement is on Person Number to improve identification accuracy.

  Why this answer?The addition of Person Number to the Redwood Person Spotlight search and Quick Actions directly enhances search precision, as it is a unique identifier for each employee. This aligns with Oracle's goal of streamlining user interactions in the Redwood interface, making A the correct choice.

  References:

  Oracle Fusion Cloud Human Resources 24C What's New, Document ID: docs.oracle.com, Published: 2024-08-27

  Section: Redwood Experience for Person Spotlight: "Added Person Number to search fields in Person Spotlight and Quick Actions to enhance search functionality."

  Oracle Global Human Resources Cloud: Using Global Human Resources, Document ID: docs. oracle.com, Published: 2024-07-02

  Section: Person Search: "Describes search capabilities, including new fields like Person Number in Redwood interfaces."

  Oracle Fusion Cloud Human Resources 25A What's New, Document ID: docs.oracle.com, Published: 2025-03-20

  Section: Search Enhancements: "Continued improvements to Person Spotlight with unique identifiers."

• Question 180:

  A consultant is trying to modify an existing lookup type to add a lookup code. But, they are not able to add lookup code. What could be the possible reason?

  A. The lookup type has been defined as Read Only.
  B. The configuration level of lookup type is set as System.
  C. The configuration level of lookup type is set as User.
  B. The configuration level of lookup type is set as System.

  ---

  In Oracle Global Human Resources Cloud, lookup types are used to define lists of values (lookup codes) for fields, such as drop-down menus or selection lists. The question indicates that a consultant cannot add a lookup code to an existing lookup type, and we need to identify the reason. Lookup types have a configuration level that determines their modifiability: , , or User. System Extensible Option A: The lookup type has been defined as Read Only.This option is incorrect because Oracle HCM Cloud does not use a Read Only designation for lookup types. Instead, modifiability is controlled by the Configuration Level (System, Extensible, or User). A System lookup type is non-editable, an Extensible lookup type allows adding new codes but not modifying predefined ones, and a User lookup type is fully editable. The term Read Only may be confused with System lookup types, but it is not a standard term in Oracle documentation for this context, making this option invalid. Option B: The configuration level of lookup type is set as System.This is the correct answer. Lookup types with a System configuration level are predefined by Oracle and cannot be modified by users, including adding, editing, or deleting lookup codes. For example, a lookup type like PER_PERSON_TYPE (for person types) is set as System, preventing consultants from adding new codes to maintain system integrity. If the consultant is trying to modify such a lookup type, they will be unable to add a lookup code, as the system restricts changes. Oracle documentation confirms that System lookup types are locked for modifications, making this the most likely reason. Option C: The configuration level of lookup type is set as User.This option is incorrect. A lookup type with a User configuration level is fully editable, allowing users to add, edit, or delete lookup codes as needed. For instance, a custom lookup type created for department categories would typically be User level, enabling the consultant to add new codes freely. Since the consultant cannot add a lookup code, a User configuration level does not explain the issue. Why this reason?The inability to add a lookup code points to a restriction on the lookup type's modifiability. The System configuration level explicitly prevents changes to ensure consistency across the application, aligning with Oracle's design for predefined lookup types. Neither Read Only nor User accurately describes the restriction, as Read Only is not a valid term, and User allows modifications. References Oracle Global Human Resources Cloud: Implementing Global Human Resources, Document ID: docs.oracle.com, Published: 2023-12-12 Section: Lookups: "System lookup types are predefined and can't be modified. Extensible lookup types let you add new lookup codes, but you can't modify predefined codes. User lookup types are fully editable." Oracle Global Human Resources Cloud: Using Global Human Resources, Document ID: docs. oracle.com, Published: 2024-07-02 Section: Manage Lookups: "You manage lookups using the Manage Common Lookups task. The configuration level determines whether you can add or modify lookup codes." Oracle Fusion Cloud Human Resources 24C What's New, Document ID: docs.oracle.com, Published: 2024-08-27 Section: Configuration Enhancements: "Clarifications on lookup type management and restrictions."