You are designing an approval rule where a specific person is required to approve the journal. Which two list builders should you use to achieve this?

When designing a journal approval rule that requires approval from a specific, named individual, two list builders are suitable. The "Resource" list builder is the most direct method, as it allows you to specify a single user by their name or username. Alternatively, the "Approval Group" list builder can be used. You would first create an approval group containing only the specific person required for approval. Then, in the approval rule, you would select this group. Both methods ensure the approval task is routed exclusively to the intended individual, rather than being dynamically routed through a hierarchy.

A. Supervisory Hierarchy routes approvals up the submitter's management chain, which is dynamic and not for a predefined, specific person.

D. Job Level Hierarchy routes approvals based on the submitter's job level, requiring a higher-level approver, not a specific named individual.

E. Position Hierarchy routes approvals based on a defined position structure, which is also a dynamic routing method, not for a static, specific person.

1. Oracle Fusion Cloud Financials, Implementing Approvals and Notifications, Release 24B, Chapter 2: Approval Rules, Section: List Builders. "Resource: Use a resource list builder to include a specific user in the approval list... Approval Group: Use an approval group list builder to include a predefined group of users in the approval list."

2. Oracle Fusion Cloud Financials, Implementing Enterprise Structures and General Ledger, Release 24B, Chapter 5: Journal Processing, Section: Journal Approval Rules: Explained. "You can route journal approvals to a specific user by using the Resource list builder or to a set of users by using the Approval Group list builder."