Which two options would you use to restrict the functionality provided by a responsibility? (Choose two.)

Question

Options

• Acreating an appropriate role
• Bcreating an appropriate group
• Cconstructing a new menu hierarchy
• Ddefining rules to exclude specific functions

• A
  13% (2)
• B
  13% (2)
• C
  73% (11)

Explanation

In Oracle E-Business Suite, a responsibility controls user access through its associated menu and function security. Option C is correct because constructing a new menu hierarchy lets you present only the relevant navigation paths to users, effectively hiding entire functional areas. Option D is correct because function exclusion rules let you surgically block specific functions from a responsibility even if they exist on the attached menu - giving you fine-grained control without rebuilding the menu from scratch.

Why the distractors are wrong: Option A (roles) is a concept from Oracle's RBAC/UMX framework and doesn't directly restrict what a responsibility exposes - you assign responsibilities to users, not roles in this context. Option B (groups) refers to request security groups or user groups, which control report/program submission access, not menu-level functionality restriction.

Memory tip: Think "Menu + Rules = Restrict" - you shape what users see (menu hierarchy) and what they can do (exclusion rules). Roles and groups operate at a different layer of the security model and won't trim a responsibility's functionality directly.

No community discussion yet for this question.