[Maintaining Customer Information] Where would an implementation configure the system to prevent duplicate persons from being added?

In Oracle Fusion Cloud Applications, system-wide behaviors like duplicate person prevention are configured at a high, central level. This configuration involves enabling the feature and defining the matching rules the system will use (e.g., based on name, date of birth, national identifiers). The option "Installation Options" is the most appropriate generic term for this type of enterprise-level setup page. In practice, this corresponds to tasks such as "Manage Enterprise HCM Information" for employees or "Manage Enterprise Data Quality Matching Configurations" for customer data, which govern the entire application's behavior for identifying duplicates.

A. Person: This is the user interface for creating or managing individual person records, not for configuring system-wide rules.
B. Person Contact Type: This setup defines types of relationships (e.g., Emergency Contact) and is not related to duplicate entity prevention.
C. Person Identifier Type: This defines types of identifiers (e.g., National ID). While these identifiers are used by the duplicate check logic, this screen is not where the overall system feature is enabled or its matching rules are configured.
E. Person Type: This is used to classify a person (e.g., Employee, Contingent Worker) and has no role in the configuration of duplicate prevention.

1. Oracle Fusion Cloud HCM

Implementing Global Human Resources (Release 24B)

Chapter: Enterprise and Workforce Structures

Section: Duplicate Person Validation.

Reference Details: This section states

"You enable duplicate person validation on the Manage Enterprise HCM Information page. On this page

you can also specify the person-matching criteria for your enterprise." This confirms that the configuration is at a high

enterprise level

which is conceptually represented by "Installation Options".

2. Oracle Fusion Cloud Customer Data Management

Implementing Customer Data Management (Release 24B)

Chapter: Set Up Data Quality

Section: How Data Quality Is Processed.

Reference Details: This chapter explains that duplicate identification for parties (including persons) is managed by Data Quality Management (DQM). The setup requires configuring matching rules in the "Manage Enterprise Data Quality Matching Configurations" task. This is a system-wide configuration

not specific to an identifier type.

3. Oracle Fusion Cloud Applications Common

Implementing Common Features for SCM (Release 24B)

Chapter: Application Common Components

Section: Define Application Taxonomy.

Reference Details: This guide discusses foundational setups. While not using the exact term "Installation Options" (which is more common in PeopleSoft)

it describes the hierarchy of setup tasks

with enterprise-level configurations being the highest level for controlling application-wide behavior

reinforcing the correctness of option D's concept.