Oracle Fusion HCM provides a specific configuration setting to control the number of personal payment methods an employee can create. This is managed through the "Manage Default Payment Method Preferences" task. Within this setup, an administrator can define the "Maximum Number of Personal Payment Methods" at either the enterprise or legislative data group (LDG) level. Setting this value to '1' directly enforces the business requirement described in the question.

B. This is incorrect because the application has a standard, built-in feature to configure this specific restriction.

C. This would prevent employees from creating or managing any personal payment methods, which contradicts the requirement to allow one.

D. Information elements are used to capture and process payroll data for calculations (e.g., earnings, deductions), not to configure application behavior or user interface limits.

1. Oracle Fusion Cloud HCM

Implementing Payroll for the United States

24B

Chapter 6: Payment Methods

Section: Payment Method Preferences.

This section details the configuration options available on the "Manage Default Payment Method Preferences" page. It explicitly states: "You can specify the maximum number of personal payment methods an employee can have." This directly supports the functionality described in option A.

2. Oracle Fusion Cloud HCM

Implementing Global Payroll

24B

Chapter 6: Banks and Payment Methods

Section: Set Up Payment Method Preferences.

This document confirms the functionality is part of the global payroll framework. It describes the "Manage Default Payment Method Preferences" task and its parameters

including the ability to set a maximum number of personal payment methods

which applies globally unless overridden at a more specific level.