Under responsibility-based security, a user's login responsibility determines which functions the user can perform. Each responsibility limits user access to information within the operating unit(s) with which it is associated, by setting either the MO: Operating Unit profile option or the MO: Security Profile profile option. By setting the MO: Security Profile profile option, you can enter and process transactions in two or more operating units, without changing responsibilities. You assign functions to menus and the menus to responsibilities. Therefore, the responsibility of a user determines what functions the user can perform.
For detailed information about responsibility-based security, see Responsibility-Based Security, Oracle Projects Implementation Guide.
With the following profile options, users can be granted access to projects and resources without having a direct relationship with either of them::
PA: Cross Project User -View: Enables users to view all project information. . It gives view access to all projects across all the operating units.
Note: In Forms applications, it gives view access to projects in the operating units the responsibility has access to.
PA: Cross Project User - Update: Enables users to update all project information. This applies only to the operating units the responsibility has access to through the MO: Operating Unit profile option or the MO: Security Profile profile option.
PA: View All Project Resources: Enables users to view resource information for all resources across multiple operating units. This profile option is typically enabled for people who use Oracle Project Resource Management to staff and schedule resources for projects. For more information, see the Oracle Project Resource Management Implementation Checklist: Oracle Projects Implementation Guide.
Note: Users whose responsibilities are associated with a cross business group access security profile can view and update project and resource information across all business groups in your enterprise. For more information, see Security Profiles, Oracle Projects Implementation Guide.
For more information about providing additional profile options in conjunction with responsibility-based security, see: Defining Additional User-Level Security, Oracle Projects Implementation Guide.