Oracle® Applications: System Administrator's Guide - Security Release 11i
Oracle® Applications: System Administrator's Guide - Security Release 11i
June 2006
Oracle Applications System Administrator’s Guide - Security, Release 11i
Contributor: George Buzsaki, Anne Carlson, Steve Carter, Siu Chang, Kalyani Venkat Chervela, Kenny Tak
Chi Ching, Charles Colt, Elanchelvan Elango, Killian Evers, Saad Fazil, Chirag Mehta, Tom Morrow, Srikanth
Sallaka, Peter Pil Seo, Hope Skinner-Savallisch, Jan Smith, Susan Stratton, Sanjeev P. Topiwala, Roger
Wigenstam
The Programs (which include both the software and documentation) contain proprietary information; they
are provided under a license agreement containing restrictions on use and disclosure and are also protected
by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly,
or decompilation of the Programs, except to the extent required to obtain interoperability with other
independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems
in the documentation, please report them to us in writing. This document is not warranted to be error-free.
Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs
may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on
behalf of the United States Government, the following notice is applicable:
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently
dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup,
redundancy and other measures to ensure the safe use of such applications if the Programs are used for such
purposes, and we disclaim liability for any damages caused by such use of the Programs.
The Programs may provide links to Web sites and access to content, products, and services from third parties.
Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear
all risks associated with the use of such content. If you choose to purchase any products or services from a
third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the
quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third
party, including delivery of products or services and warranty obligations related to purchased products or
services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any
third party.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective owners.
Contents
Preface
1 Introduction
Access Control in Oracle Applications . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Oracle User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Oracle Application Object Library Security . . . . . . . . . . . . . . . . . . . . . . 1-2
User and Data Auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
iii
Unlocking Locked User Accounts . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Assigning Roles to or Revoking Roles from Users. . . . . . . . . . . . . . . . . . 3-21
Registering External Organization Contacts . . . . . . . . . . . . . . . . . . . . 3-22
Self Service Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Self-Service Registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Requesting Additional Application Access. . . . . . . . . . . . . . . . . . . . . 3-23
Reset Forgotten Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
iv
Search Grants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
Create Grant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Define Grant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Select Object Data Context . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
Define Object Parameters and Select Set . . . . . . . . . . . . . . . . . . . . 4-35
Review and Finish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
Update Grant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
View Grant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
Create Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
Update Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
Duplicate Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
View Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
Delete Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Navigation Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Search for Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
Create Navigation Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
Update Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
Duplicate Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
Delete Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
Create Permission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
Update Permission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
Duplicate Permission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
View Permission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42
Delete Permission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42
Permission Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42
Create Permission Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42
Update Permission Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42
Duplicate Permission Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43
View Permission Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43
Delete Permission Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43
Compile Security Concurrent Program. . . . . . . . . . . . . . . . . . . . . . . . 4-43
Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
Function Security Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
Users of a Responsibility Report . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
Report Heading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Column Headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Active Responsibilities Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Report Heading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Column Headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
v
Active Users Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Report Heading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Column Headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Reports and Sets by Responsibility Report . . . . . . . . . . . . . . . . . . . . . 4-47
Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
Report Headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
vi
Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
Report Heading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
Column Headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Signon Audit Users Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Report Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Report Heading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
Column Headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
Purge Signon Audit Data Program . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Index
vii
Send Us Your Comments
Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document.
Your feedback is important, and helps us to best meet your needs as a user of our products. For example:
• Are the implementation steps correct and complete?
• Did you understand the context of the procedures?
• Did you find any errors in the information?
• Does the structure of the information help you with your tasks?
• Do you need different information or graphics? If so, where, and in what format?
• Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us your name, the
name of the company who has licensed our products, the title and part number of the documentation and
the chapter, section, and page number (if available).
Note: Before sending us your comments, you might like to check that you have the latest version of the
document and if any concerns are already addressed. To do this, access the new Applications Release
Online Documentation CD available on Oracle MetaLink and www.oracle.com. It contains the most
current Documentation Library plus all documents revised or released recently.
Send your comments to us using the electronic mail address: [email protected]
Please give your name, address, electronic mail address, and telephone number (optional).
If you need assistance with Oracle software, then please contact your support representative or Oracle
Support Services.
If you require training or instruction in using Oracle software, then please contact your Oracle local
office and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web
site at www.oracle.com.
ix
Preface
Intended Audience
Welcome to Release 11i of the Oracle Applications System Administrator’s Guide - Security.
This guide assumes you have a working knowledge of the principles and customary
practices of your business area. If you have never used Oracle Applications we suggest
you attend one or more of the Oracle Applications System Administration training
classes available through Oracle University. (See Other Information Sources for more
information about Oracle training.)
This guide also assumes you are familiar with the Oracle Applications graphical user
interface. To learn more about the Oracle Applications graphical user interface, read the
Oracle Applications User’s Guide.
See Other Information Sources for more information about Oracle Applications product
information.
See Related Information Sources on page xii for more Oracle Applications product
information.
Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation accessible,
with good usability, to the disabled community. To that end, our documentation
includes features that make information available to users of assistive technology.
This documentation is available in HTML format, and contains markup to facilitate
access by the disabled community. Accessibility standards will continue to evolve over
time, and Oracle is actively engaged with other market-leading technology vendors to
address technical obstacles so that our documentation can be accessible to all of our
customers. For more information, visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/ .
xi
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations
that Oracle does not own or control. Oracle neither evaluates nor makes any
representations regarding the accessibility of these Web sites.
Structure
1 Introduction
2 Access Control with Oracle User Management
3 Oracle User Management Setup and Administration
4 Oracle Application Object Library Security
5 User and Data Auditing
A Security Conguration and Maintenance
Online Documentation
All Oracle Applications documentation is available online (HTML or PDF).
• PDF Documentation - See the Oracle Applications Documentation Library CD
for current PDF documentation for your product with each release. The Oracle
Applications Documentation Library is also available on OracleMetaLink and is
updated frequently.
• Online Help - Online help patches (HTML) are available on OracleMetaLink.
• About Documents - Refer to the About document for the mini-pack or family pack
that you have installed to learn about feature updates, installation information, and
new documentation or documentation patches that you can download. About
documents are available on OracleMetaLink.
Related Guides
You can read the guides online by choosing Library from the expandable menu on your
HTML help window, by reading from the Oracle Applications Documentation Library
CD included in your media pack, or by using a Web browser with a URL that your
system administrator provides.
If you require printed guides, you can purchase them from the Oracle Store at
http://oraclestore.oracle.com.
xii
Catalog (and any other Oracle Applications products). This guide also includes
information on setting user profiles, as well as running and reviewing reports and
concurrent processes.
You can access this user’s guide online by choosing ”Getting Started with Oracle
Applications” from any Oracle Applications help file.
xiii
This guide contains the user interface (UI) standards followed by the Oracle Applications
development staff. It describes the UI for the Oracle Applications products and how to
apply this UI to the design of an application built by using Oracle Forms.
xiv
write custom reports for Oracle Applications products. Oracle eTRM is available on
OracleMetaLink.
Oracle Applications Message Reference Manual
This manual describes Oracle Applications messages. This manual is available in HTML
format on the documentation CD-ROM for Release 11i.
xv
1
Introduction
Introduction 1-1
Administration, Registration Processes, and Self Service & Approvals. Part of this setup
includes defining local administrators primarily by creating administrative roles and
assigning them to individuals who serve as an organization’s local administrators. Once
this is accomplished, local administrators use Oracle User Management to manage a
subset of an organization’s users.
Overview
This chapter introduces the Core Security and Administrative Features of Oracle User
Management. Core Security includes Oracle’s Function and Data Security models, as
well as Role Based Access Control. Administrative Features build upon Core Security
and include Delegated Administration, Registration Processes, and Self Service and
Approvals.
Core Security and Administrative Features are implemented in successive layers and
each builds upon the one that precedes it. Organizations can optionally uptake the
various layers, depending on the degree of automation and scalability that they wish to
build upon the existing Function and Data Security models.
In general, Access Control with Oracle User Management begins with basic system
administration tasks, progresses to more distributed, local modes of administration, and
ultimately enables users to perform some basic, predefined registration tasks on their
own. The following diagram illustrates how the layers build upon each other.
Oracle User Management provides support for legacy and application-specific security
mechanisms through workflow business events. Oracle User Management raises
Function Security
Function Security is the base layer of access control in Oracle Applications. It restricts
user access to individual menus and menu options within the system, but does not
restrict access to the data contained within those menus. For example, an organization
could use Function Security to provide its sales representatives with the required menus
and menu options for querying customers. It could also control access to specific
components of those pages such as a button on a sales forecasting page. For a more
comprehensive explanation of function security, see the Oracle Application Object
Library Security chapter, page 4-1.
Data Security
Data Security is the next layer of access control. Building on Function Security, Data
Security provides access control within Oracle Applications on the data a user can
access, and the actions a user can perform on that data. Oracle Applications restricts
access to individual data that is displayed on the screen once the user has selected a
menu or menu option. For example, Data Security restricts the set of users that a local
administrator can access within Oracle User Management. Data Security policies can
only be defined for applications that have been written to utilize the Data Security
Framework. For a more comprehensive explanation of data security, see the Oracle
Application Object Library Security chapter, page 4-1.
RBAC is the next layer and builds upon Data Security and Function Security. With
RBAC, access control is defined through roles, and user access to Applications is
determined by the roles granted to the user. Access control in Oracle Applications
closely follows the RBAC ANSI standard (ANSI INCITS 359-2004) originally proposed
by the National Institute of Standards & Technology (NIST), which defines a role as
"a job function within the context of an organization with some associated semantics
regarding the authority and responsibility conferred on the user assigned to the role."
A role can be configured to consolidate the responsibilities, permissions, function
security and data security polices that users require to perform a specific function. This
is accomplished with a one-time setup, in which permissions, responsibilities, and other
roles are assigned to the role. Users are not required to be assigned the lower-level
permissions directly, since permissions are implicitly inherited on the basis of the
roles assigned to the user. This simplifies mass updates of user permissions, since an
organization need only change the permissions or role inheritance hierarchy defined
for a given role, and the users assigned that role will inherit the new set of permissions
automatically.
Organizations can define roles that closely mirror their business situation. For
example, an organization can create an "Employee" role and then assign that role to all of
its employees. It can also create an "External" role and assign that role to customers and
suppliers. Further examples may include specific roles such as "Support Agent", "Sales
Rep", "Sales Managers". In these examples, each role contains a specific level of access
privileges that restricts its assignees to the scope of their job functions. Some members of
the organization will probably be assigned more than one role. A sales representative
would be assigned the Employee and Sales Representative roles, and a Sales Manager
would be assigned the Employee, Sales Representative, and Sales Manager roles. Roles
and role assignments are stored in the workflow directory, which is interpreted by the
security system at runtime.
Role Categories
As part of the Oracle Applications RBAC model, Oracle User Management introduces
Role Categories. Administrators can create role categories to bundle roles and
responsibilities to make the process of searching for roles and responsibilities easier. For
example, all sales and marketing related roles could be included in the Sales & Marketing
category.
In the above figure, the arrows on each side of the diagram indicate membership
inheritance and permission inheritance. Text in the rounded boxes indicates roles. An
arrow pointing from an individual to a role indicates that this individual is assigned the
role. An arrow pointing from one role to another indicates that the role from which
the arrow points is the superior role, and the role to which it points is the subordinate
role. Permissions associated with a role are inherited by all of its superior roles and the
individuals to which any of these roles are assigned.
In this example, some roles such as "Employee" or "Manager" are assigned general
permissions for a given function. For example, the Employee role may provide access
to menus generally available to all employees, while the Manager role provides access
to menus that should only be viewed by managers. Because the Employee role is a
subordinate role of the Manager role, anyone assigned the Manager role automatically
obtains the permissions associated with the Employee role. Other roles in this example
pertain to more specific job functions, such as Sales Manager and Sales Representative, or
Support Manager and Support Agent. These roles may provide access to job-specific
menus and data such as the Sales Forecasting menu, or the Support application.
Administration Privileges
Administration Privileges determine the users, roles and organization information that
delegated administrators (local administrators) can manage. Each privilege is granted
separately, yet the three work in conjunction to provide the complete set of abilities
for the delegated administrator.
User Administration Privileges. A local administrator must be granted User
Administration Privileges to determine the users and people the local administrator can
manage. Local administrators can be granted different privileges for different subsets
of users. For example, a local administrator can be granted privileges only to query
one set of users, and granted full privileges (including update and reset password)
for another set. Local administrators cannot query users for which they do not have
administration privileges.
Note: Please note that Oracle Applications continues to support
the traditional “System Administrator” level of administration
privileges, where a designated group of people manages all users and
access privileges. Oracle User Management ships a predefined Security
Administrator role, which gives the administrator the privileges to
manage all users including system accounts and all roles in the system.
Registration Processes
Registration processes are predefined registration components that enable end users
to perform some of their own registration tasks, such as requesting new accounts or
additional access to the system. They also provide administrators with a faster and more
efficient method of creating new user accounts, as well as assigning roles. Registration
processes accomplish this by encapsulating core components of registration, including:
• The role(s) assigned after the user successfully completes the process.
• An optional registration user interface for collecting account or additional
information.
• A workflow for approval, confirmation, rejection, and identity verification
notifications.
• The Approval Management Transaction Type. A transaction type represents a set of
approval routing rules that are interpreted at runtime.
• The set of users that are eligible to sign up for additional access (only applicable for
Request for Additional Access registration processes).
• Whether identity verification is required. Identity verification confirms the identity
of a requester before the registration request is processed, by sending an email
Depending on the context, the event parameters listed in the following table are set
automatically by the Oracle User Management registration engine when business
events are raised. Any additional information captured in the registration UI, approval
notifications, or programmatically through business logic is also available as event
parameters.
Registration Status
Users can check registration status of requests through the Access Request Tool
(ART) and administrators can do so using the Administration screens. For any
pending requests, the Show Info icon shows the current approver and confirmation
number. The confirmation number represents the number (ITEM_KEY) of the Oracle
User Management Registration Workflow (UMXREGWF) workflow process handling
the request.
Notication Workows
Notification workflows enable an organization to define its own email notifications that
are specific to each Role or Registration Process. Notifications include:
Approval confirmation notifications Individual for whom the request was filed.
Identity verification notifications Individual for whom the request was filed.
For each request that requires approval as determined by the Oracle Approval
Management Engine, Oracle User Management invokes the notification workflow to
request approval. Notification workflows can be written to allow approvers to review
the information submitted in the registration process, make changes, and provide
additional information if required.
Any changes or additional information provided can be passed back to the Oracle
User Management registration engine for further processing. For example, if Oracle
User Management is used to provide self service registration capability for iSP
(Internet Supplier Portal), then approvers can provide additional information about
Setup Tasks
This section discusses the setup tasks for Oracle User Management. The implementor or
system administrator sets up access control and security policies in Oracle Applications
by defining roles, role inheritance hierarchies, role categories, and registration
processes. These components specify the different levels of access to various application
menus and data that are available to administrators.
Steps
1. Log on as a user that is assigned the Security Administrator role (typically as
sysadmin), select the User Management responsibility in the navigator and then
click the Role Categories subtab.
2. Go to the editable table, click the Update button and then click the Create Lookup
Code button.
3. Enter the required information in the Create Lookup Code fields and click the
Apply button.
Steps
1. Log on as a user that is assigned the Security Administrator role (typically as
sysadmin), select the User Management responsibility in the navigator and then
click the Roles & Role Inheritance subtab.
Guidelines
The Save button saves your changes and continues to display them in the current
page. The Apply button saves your changes and returns to the previous page. You can
optionally organize your roles using role categories during the process of creating and
updating roles, otherwise they will be stored under the "Miscellaneous" role category
by default. For more information, see role categories, page 3-1. You can also define
any required subordinate roles or superior roles through role inheritance hierarchies,
page 3-7.
Steps
1. Log on as a user that is assigned the Security Administrator role (typically as
sysadmin), select the User Management responsibility in the navigator and then
click the Roles & Role Inheritance subtab.
2. In the Role Inheritance Hierarchy, access the role to which you want to assign a
permission and click the Update icon.
Steps
1. Log on as a user that is assigned the Security Administrator role (typically as
sysadmin), select the User Management responsibility in the navigator and then
click the Roles & Role Inheritance subtab.
2. In the navigation menu access the role to which you want to define organization
administration and click the Update icon.
3. Click the Organization Administration link and then click the Assign Organization
Privileges button. The drop down list contains various data security policies that
pertain to the User Management Person Object (UMX_PERSON_OBJECT). Oracle
User Management ships with sample data security policies for organization
administration privileges. Organizations can use these policies to create their own.
Steps
1. Log on as a user with the Functional Developer responsibility, click the Functional
Developer responsibility in the navigator, navigate to the Security tab and then
click the Objects subtab.
2. Search for and access the object for which you want to create data security
policies. For example, to locate the User Management Person business object
(UMX_PERSON_OBJECT), enter "UMX%" in the Code field, click the Go button, and
then click User Management Person object (UMX_PERSON_OBJECT) in the search
results list. For any object for which you are creating a policy, ensure that the SQL
statement returns the primary key value for that object. In this example, this is a
list of person party IDs.
3. Click the Object Instance Sets subtab. Click the Create Instance Set button to create a
new object instance set or click the Update icon to modify an existing one.
4. Enter the required information and then click the Apply button.
Caution: For performance reasons, ensure that SQL predicates are tuned
properly. For security reasons, ensure that they are tested and that they
return the correct result. Oracle is not responsible for the performance
or correctness of data security policies defined by organizations.
With Role Inheritance Hierarchies, roles inherit the permissions assigned to their sub
roles.
Steps
1. Log on as a user that is assigned the Security Administrator role (typically as
sysadmin), select the User Management responsibility in the navigator and then
click the Roles & Role Inheritance subtab.
2. Locate the role for which you want to create a role inheritance hierarchy by using
the Search fields or by expanding the appropriate nodes in the Role Inheritance
Hierarchy menu. If you are building a role inheritance hierarchy that contains
several roles, start with highest level role to which you want to add inherited
subordinate roles.
3. Click the Add Node icon next to this role.
4. In the resulting menu, search for the role either by using the Search fields or by
locating it in the Role Inheritance Hierarchy menu.
5. Select the role and then click the Select button or the Quick Select icon.
6. Repeat this process until you have added all of the required subordinate roles to
their corresponding super roles. You can optionally verify the results by expanding
the nodes for all super roles within your role inheritance hierarchy. You can also
remove any subordinate roles by clicking the Remove Node icon.
Steps
1. Create roles representing the required job functions such as Manager and Employee.
Note: A user cannot access any of the menu items (functions) within
the application if you assign the responsibility to the user at this
stage.
4. Create roles representing the people with various job functions that require access
to the application, for example, a Manager role and an Employee role. For more
information, see Creating and Updating Roles, page 3-1
5. Define role inheritance relationships. For more information, see Defining Role
Inheritance Hierarchies, page 3-7 For example, the Manager role should inherit the
Employee role, and the Employee role should inherit the Expenses and Human
Resources responsibilities. The following figure illustrates a role inheritance
Figure 3-4 Role Inheritance Relationship in Which a Role Inherits the Responsibilities
Inherited by its Subordinate Role
6. Assign permissions to each role. For more information, see Assign permissions to
each role, page 3-2. Each permission maps to a menu item (function) within the
application (responsibility) that should be available to the users to whom the role is
assigned. For example, an organization will grant the employee-related permissions
from the Expenses and Human Resources responsibilities to the Employee role, and
will grant the manager-related permissions for these responsibilities to the Manager
role. Consequently, the manager role will have access to all the menu items
within these responsibilities, but the Employee role will only have access to the
Employee-related functions.
• Setup screens.
Steps
Registration processes all use the same infrastructure and processing logic. Steps for
defining a registration process will vary depending on the type of registration process
you are creating.
1. Log on as a user that is assigned the Security Administrator role (typically as
sysadmin), select the User Management responsibility in the navigator and then
click the Registration Processes subtab.
2. Click the Create Registration Process button.
3. Enter the required information for the Registration Process Description and click the
Next button. This information specifies:
• Role. The role with which you optionally associate the registration process
and that is assigned to the user at the end of the registration process once the
request has been processed.
• Type. The type of registration process you wish to create.
• Registration Process Code. The unique identifier for the registration process.
• Display Name. The display name for the registration process.
Additional Requirements
• In all the three of the stages above, the values set must correspond to the same user
name policy.
• The Listener and JVMs must be restarted after the user name policy is changed.
Common Prerequisites
The following are prerequisites for performing any delegated administration task listed
in the preceding section. Each task may have additional prerequisites:
• A role that is granted the User Maintenance UIs (UMX_USER_ADMIN_UI_PERMS)
permission set. The role must also inherit the User Management responsibility.
• Appropriate privileges for User Administration, Role Administration, and
Organization Administration.
• The Query Person Details (UMX_PERSON_OBJECT) permission for the set of people
and administrator can manage.
• Optionally, the Edit Person Details (UMX_OBJECT_EDIT_PERSON) permission for
the set of people that the administrator can manage.
• For system administrators, the Maintain System Accounts (UMX_SYSTEM_
ACCOUNT_ADMINISTRATION) permission.
Steps
1. Navigate to the User Management responsibility and then click the Users subtab.
2. Use the search fields to locate the required people or users.
3. Manage the generated list of people or users by clicking the required icon
and performing the necessary steps in the resulting window. Options for
managing people and users vary depending on the permissions assigned to the
administrator. Oracle User Management ships with the following basic and
advanced options for maintaining people and users:
• Query users
• Edit personal information
• Reset password
• Maintain account information (create, inactivate, reactivate accounts)
Prerequisites
To create, inactivate, and reactivate user accounts, an administrator must be assigned
the following:
• Common prerequisites, as detailed in the Maintain People and Users
section, Common Prerequisites, page 3-19.
• The Create, Inactivate, Reactivate User Account (UMX_OBJ_ACTIVATE_ACCT)
permission for the set of people that the administrator can manage.
By default, user names are derived from the person’s email address.
Steps
1. Log in as a user with a role granting you access to the User Management
responsibility, select the User Management responsibility in the navigator and click
the Users subtab.
2. Search for the person for whom you wish to create an account and then click the
Create Account icon next to the person’s name if the account does not already
exist. Your search will only generate results for the subset of users that you are
eligible to manage.
3. Enter or modify the required information and click the Submit button.
Guidelines
Oracle recommends that you base user names on the person’s email address.
Prerequisites
To reset user passwords, an administrator must be assigned the following:
• In the Maintain People and Users section, see the Common Prerequisites, page 3-19.
• The Reset Password (UMX_OBJ_PASSWD_MGMT) permission for the users that
the administrator can manage
Steps
1. Log in as a user with a role granting you access to the User Management
responsibility, select the User Management responsibility in the navigator and click
the Users subtab.
2. Use the Search field to locate the user whose password you wish to change and then
click the Reset Password icon next to the user.
Prerequisites
To unlock an account, an administrator must be assigned the following:
• In the Maintain People and Users section, see Common Prerequisites, page 3-19.
• The Reset Password (UMX_OBJ_PASSWD_MGMT) permission for the users that
the administrator can manage.
Steps
1. Log in as a user with a role granting access to the User Management responsibility.
2. Select the User Management responsibility in the navigator, and click the Users
subtab.
3. Use the Search field to locate the user whose account you wish to unlock. The user
account is locked if the Account Status column displays a padlock icon along with
status "Locked".
4. Click the "Reset Password" icon next to that user and follow the steps mentioned
in the section above to reset the user’s password. As a result of resetting the
password, the user account will be unlocked.
Prerequisites
To assign roles to or revoke roles from users, an administrator must be assigned the
following:
• Common prerequisites from the Maintain People and Users section, Common
Prerequisites, page 3-19.
• The appropriate administrative privileges for the role the administrator assigns
or revokes. For more information, see Defining Role Administration Privileges
for Roles, page 3-5.
Guidelines
The administrator can only grant or revoke roles for which he has the appropriate
privileges. When granting or revoking roles, the administrator bypasses any approval
processes. If a registration process exists for the role, it will be invoked and the request
will be handled by the Oracle User Management registration engine. If not, then the role
is assigned directly. If the role is associated with a registration process for existing users
and the registration process has a reference for capturing additional information, then the
"Additional Information Required" link is rendered. The administrator must click on this
link and provide any required additional information before the request is processed.
Prerequisites
To register new people, an administrator must be assigned the following:
• The common prerequisites detailed in the Maintain People and Users
section, Common Prerequisites, page 3-19.
• The necessary privileges to invoke the specific administrative account creation
registration processes; these are defined as part of the registration process definition.
• Organization Administration privileges for all organizations for which an
administrator needs to be able to register new people.
Steps
1. Log in as a user with a role granting you access to the User Management
responsibility, select the User Management responsibility in the navigator and click
the Users subtab.
2. In the Register dropdown list, select administrative account registration process you
wish to invoke, and click the Go button.
3. Enter the information required by the registration process as defined by the
registration UI for the registration process, click the Submit button and then click
the OK button in the resulting page.
Self-Service Registration
Oracle User Management enables users to register for access to applications without
requiring assistance from administrators. To register for application access, users must
provide information in the required fields and click the Submit button.
Oracle User Management ships with the following sample self-service registration
processes:
• Employee Self-Service Registration
• Customer Self-Service Registration (external individuals)
Organizations can use these registration processes in their existing form, or can use them
as references for developing their own registration processes.
Steps
1. After logging into the system, click the Preferences link in the upper right
corner, and click the Access Requests link in the sidebar menu. The Access Requests
page displays the roles you have been assigned. Click the Request Access button to
request one or more additional roles.
2. Most roles are organized according to role categories: roles that are not categorized
appear under the Miscellaneous node. Select the role category that contains the role
you want to request. If you do not see the required role, then either you are not
eligible for the role or it has not been set up to for additional access requests.
3. Select the role or roles you require for additional access to the system, and click on
the Add to List button. You can optionally remove roles from your list by clicking
on the Remove Roles button.
4. When you have selected all your required roles, click on the Next button.
5. Enter a justification for your request and click on the Next button. You can remove
any pending roles or check their status in the page that appears next.
Guidelines
Some roles may require you to provide additional information. In such cases, the system
will prompt you for additional information before you can complete the process for
requesting a role.
HRMS Security
The Human Resources Management Systems (HRMS) products have an additional
feature using Security Groups. For more information, see: Customizing, Reporting, and
System Administration in Oracle HRMS.
Dening a Responsibility
When you define a responsibility, you assign to it some or all of the components
described below.
Menu (Required)
A menu is a hierarchical arrangement of application functions (forms). In the definition
of a responsibility, the specified menu defines what is displayed in the navigator. The
specified menu does not necessarily define the functions that can be accessed by the
responsibility, which are granted. See: Overview of Function Security, page 4-6.
Predened Responsibilities
All Oracle Applications products are installed with predefined responsibilities. Consult
the reference guide for your Oracle Applications product for the names of those
predefined responsibilities.
Additionally, instances of the major components that help define a responsibility (data
groups, request security groups, menus, and functions) are predefined for Oracle
Applications.
ICX:Session Timeout
Use this profile option to enforce an inactivity time-out. If a user performs no Oracle
Applications operation for a time period longer than the time-out value (specified
in minutes), the user’s session is disabled. The user is provided an opportunity to
re-authenticate and re-enable a timed-out session. If re-authentication is successful, the
session is re-enabled and no work is lost. Otherwise, Oracle Applications exits without
saving pending work.
If this profile option to 0 or NULL, then user sessions will never time out due to inactivity.
Terms
Function
A function is a part of an application’s functionality that is registered under a unique
name for the purpose of assigning it to, or excluding it from, a responsibility.
There are two types of functions: executable functions (formerly called form
functions), and non-executable functions (formerly called subfunctions).
Executable Function
Executable functions have the unique property that you may navigate to them using the
Navigate window.
Non-executable Function
A non-executable function) is a securable subset of a form’s functionality: in other
words, a function executed from within a form.
A developer can write a form to test the availability of a particular non-executable
function, and then take some action based on whether the non-executable function
is available in the current responsibility.
Non-executable functions are frequently associated with buttons or other graphical
elements on forms. For example, when a non-executable function is enabled, the
corresponding button is enabled.
However, a non-executable function may be tested and executed at any time during a
form’s operation, and it need not have an explicit user interface impact. For example, if a
non-executable function corresponds to a form procedure not associated with a graphical
element, its availability is not obvious to the form’s user.
Menu
A menu is a hierarchical arrangement of functions and menus of functions. Each
responsibility has a menu assigned to it.
Menus can map to permission sets as well.
Menu Entry
A menu entry is a menu component that identifies a function or a menu of functions. In
some cases, both a function and a menu of functions correspond to the same menu
entry. For example, both a form and its menu of subfunctions can occupy the same
menu entry.
Responsibility
A responsibility defines an application user’s current privileges while working with
Oracle Applications. When an application user signs on, they select a responsibility
that grants certain privileges, specifically:
Related Topics
How Function Security Works, page 4-9
Form Functions, page 4-21
Forms and Subfunctions , page 4-8
Functions, Menus, and the Navigate Window, page 4-8
Overview of Oracle Applications Security, page 4-1
Implementing Function Security, page 4-10
Related Topics
Overview of Function Security, page 4-6
Functions, Menus, and the Navigate Window, page 4-8
How Function Security Works, page 4-9
Registering Functions
• Developers can require parts of their Oracle Forms code to look up a unique function
name, and then take some action based on whether the function is available in the
current responsibility. Function names are unique.
• Developers can register functions. They can also register parameters that pass values
to a function. For example, a form may support data entry only when a function
parameter is passed to it.
Warning: In general, you should not modify names, parameters, or
other material features of predefined functions for Oracle
Applications products. The few exceptions are documented in the
relevant manuals or product notes.
Excluding Functions
Each Oracle Applications product is delivered with one or more predefined menu
hierarchies. System Administrators can assign a predefined menu hierarchy to a
responsibility. To tailor a responsibility, System Administrators exclude functions or
menus of functions from that responsibility using exclusion rules.
Note: The ability to exclude functions is to be used for backward
compatibility only. Menu exclusions do not apply to grants.
Menu Compilation
The Compile Security (FNDSCMPI) concurrent program is used to compile menus so
that the system can more quickly check if a particular function is available to a particular
responsibility/menu.
You should compile your menus after you make changes to your menu data. A request
for this concurrent program is automatically submitted after you make changes using
the Menus form.
Related Topics
Menus Window, page 4-25
Compile Security Concurrent Program, page 4-43
Related Topics
Overview of Oracle Applications Security, page 4-1
Overview of Function Security, page 4-6
Implementing Function Security, page 4-10
Form Functions, page 4-21
Function Security Reports, page 4-44
Objects
Data Security uses the concept of an Object to define the data records that are secured.
Object
Data security permissions are managed on objects. Business entities such as Projects
and Users are examples of objects. Only a securable business-level concept should be
registered as an object.
An object definition includes the business name of the object and identifies the main
table and primary key columns used to access the object.
Object Instance
An object instance is a specific example of an object, such as Project Number 123 or User
JDOE. An object instance generally corresponds to a row in the database. An instance is
identified by a set of one or more primary key values as defined by the object.
In addition, "All Rows" for an object indicates all data rows of the object.
The predicate can also be parameterized, so that the logic can define instance sets as a
function of one or more input parameters. An example is:
COLOR = :PARAM1
Groups
Users can belong to Groups. The grouping can come from position or
organization relationships modeled in applications such as Oracle Human
Resources. Alternatively, ad-hoc groups can be created explicitly for security purposes. A
group is sometimes referred to as a role.
Security Context
Security context refers to the context of the data in which the user is working. For
example, data context could be the organization or responsibility with which the user is
logged in.
Responsibilities Window
Use this window to define a responsibility. Each application user is assigned at least
one responsibility.
Prerequisites
❒ Use the Data Groups window to list the ORACLE username your responsibility’s
concurrent programs reference on an application-by-application basis.
❒ Use the Request Groups window to define the Request Group you wish to make
available with this responsibility.
❒ Use the Menus window to view the predefined Menu you can assign to this
responsibility.
Responsibilities Block
An application name and a responsibility name uniquely identify a responsibility.
Effective Dates
From/To
Enter the start/end dates on which the responsibility becomes active/inactive. The
default value for the start date is the current date. If you do not enter an end date, the
responsibility is valid indefinitely.
You cannot delete a responsibility, because its information helps to provide an audit
trail. You can deactivate a responsibility at any time by setting the end date to the current
date. If you wish to reactivate the responsibility later, either change the end date to a
date after the current date, or clear the end date.
Available From
This is the navigator from which the responsibility will be available (Oracle Applications
forms navigator, mobile navigator).
A responsibility may be associated with only one Applications system.
Data Group
Note: Data groups are used for backward compatibility only. Oracle
Applications Framework does not support the data groups feature.
Name/Application
The data group defines the pairing of application and ORACLE username.
Select the application whose ORACLE username forms connect to when you choose
this responsibility. The ORACLE username determines the database tables and table
privileges accessible by your responsibility. Transaction managers can only process
requests from responsibilities assigned the same data group as the transaction manager.
Menu
The menu whose name you enter must already be defined with Oracle
Applications. See: Menus, page 4-25.
Request Group
Name/Application
If you do not assign a request security group to this responsibility, a user with this
responsibility cannot run requests, request sets, or concurrent programs from the
Define function and menu exclusion rules to restrict the application functionality
accessible to a responsibility.
Type
Select either Function or Menu as the type of exclusion rule to apply against this
responsibility.
• When you exclude a function from a responsibility, all occurrences of that function
throughout the responsibility’s menu structure are excluded.
• When you exclude a menu, all of its menu entries, that is, all the functions and
menus of functions that it selects, are excluded.
Name
Select the name of the function or menu you wish to exclude from this responsibility. The
function or menu you specify must already be defined in Oracle Applications.
Once defined, a new application user can sign on to Oracle Applications and access data
through Oracle Applications windows.
Note: If you have upgraded from a previous release of Oracle
Applications, ensure that you have run the Party Merge concurrent
program to update your user data. If you have not run this program, you
may receive errors in querying your user data.
For more information, see the Oracle Trading Community Architecture
documentation.
Users Block
User Name
An application user enters this username to sign on to Oracle Applications.
The username should only contain characters allowed by Oracle Single Sign-On.
Tip: We recommend that you define meaningful usernames, such as
the employee’s first initial followed by their last name. Or, for a group
Password
Enter the initial password of an application user. An application user enters this
password along with his username to sign on to Oracle Applications.
• A password must be at least five (5) characters and can be up to thirty (30) characters.
• All characters are allowed except control characters, which are non-printable. Oracle
encourages the use of non-alphanumeric characters because they add
complexity, making passwords harder to guess.
This window does not display the password you enter. After you enter a password, you
must re-enter it to ensure you did not make a typing error.
If the application user already exists and the two entries do not match, the original
password is not changed and an error message is displayed.
If you are defining a new application user and the two entries do not match, you are
required to enter the password again. For a new user, you cannot navigate to the next
field until the two entries match.
The first time an application user signs on, he must change his password. If a user
forgets his password, you can reassign a new password in this field.
As System Administrator, you can set an initial password or change an existing
password, but you cannot access the user’s chosen password.
You can set the minimum length of Oracle Applications user passwords using the profile
option Signon Password Length. If this profile option is left unset, the minimum length
defaults to 5.
You can set the minimum number of days that a user must wait before being allowed to
reuse a password with the Signon Password No Reuse profile option.
You can use the profile option Signon Password Hard to Guess to set rules for choosing
passwords to ensure that they will be "hard to guess." A password is considered
hard-to-guess if it follows these rules:
• The password contains at least one letter and at least one number.
• The password does not contain the username.
• The password does not contain repeating characters.
The Signon Password Failure Limit profile option determines the maximum number of
login attempts before the user’s account is disabled.
For information on case sensitivity in passwords, see: Case Sensitivity in Oracle
Applications User Passwords, page 4-5.
Person, Customer, and Supplier
Use these fields to enter the name of an employee (person), customer, or supplier
contact. Enter the last name and first name, separated by a comma, of the
employee, customer, or supplier who is using this application username and
password. Use the List of Values to select a valid name.
For more information on using these fields, see the Oracle Trading Community
Architecture documentation.
Password Expiration
Days
Enter the maximum number of days between password changes. A pop-up window
prompts an application user to change his password after the maximum number of days
you specify has elapsed.
Accesses
Enter the maximum allowed number of sign-ons to Oracle Applications allowed
between password changes. A pop-up window prompts an application user to change
his password after the maximum number of accesses you specify has elapsed.
Tip: We recommend that you require application users to make regular
password changes. This reduces the likelihood of unauthorized access
to Oracle Applications.
Effective Dates
From/To
The user cannot sign onto Oracle Applications before the start date or after the end
date. The default for the start date is the current date. If you do not enter an end date, the
username is valid indefinitely.
You cannot delete an application user from Oracle Applications because this information
helps to provide an audit trail. You can deactivate an Oracle Applications user at any
time by setting the End Date to the current date.
If you wish to reactivate a user, change the End Date to a date after the current date, or
clear the End Date field.
Direct Responsibilities
Direct responsibilities are responsibilities assigned to the user directly.
Responsibility
Select the name of a responsibility you wish to assign to this application user. A
responsibility is uniquely identified by application name and responsibility name.
Security Group
This field is for HRMS security only. See: Customizing, Reporting, and System
Administration in Oracle HRMS.
This field is enabled only if the profile Enable Security Groups is enabled.
From/To
You cannot delete a responsibility because this information helps to provide an audit
trail. You can deactivate a user’s responsibility at any time by setting the End Date
to the current date.
If you wish to reactivate the responsibility for the user, change the End Date to a date
after the current date, or clear the End Date.
Securing Attributes
Securing attributes are used by some Oracle HTML-based applications to allow rows
(records) of data to be visible to specified users or responsibilities based on the specific
data (attribute values) contained in the row.
You may assign one or more values for any of the securing attributes assigned to the
user. If a securing attribute is assigned to both a responsibility and to a user, but the
user does not have a value for that securing attribute, no information is returned for
that attribute.
For example, to allow a user in the ADMIN responsibility to see rows containing a
CUSTOMER_ID value of 1000, assign the securing attribute of CUSTOMER_ID to the
ADMIN responsibility. Then give the user a security attribute CUSTOMER_ID value of
1000.
When the user logs into the Admin responsibility, the only customer data they have
access to has a CUSTOMER_ID value of 1000.
Attribute
Select an attribute you want used to determine which records this user can access. You
can select from any of the attributes assigned to the user’s responsibility.
Value
Enter the value for the attribute you want used to determine which records this user
can access.
Related Topics
Defining a Responsibility, page 4-2
Overview of Function Security, page 4-6
Responsibilities, page 4-14
Description
Function
Users do not see this unique function name. However, you may use this name when
calling your function programmatically. You should follow the naming conventions
for functions.
User Function Name
Enter a unique name that describes your function. You see this name when assigning
functions to menus. This name appears in the Top Ten List of the Navigator window.
Properties
Type
A function’s type describes its use. A function’s type is passed back when a developer
tests the availability of a function. The developer can write code that takes an action
based on the function’s type.
Standard function types include the following:
FORM
Oracle Applications form functions are registered with a type of FORM.
SUBFUNCTION
Subfunctions are added to menus (without prompts) to provide security functionality
for forms or other functions.
JSP
Functions used for some products in the Oracle Self-Service Web Applications. These are
typically JSP functions.
Form
Form /Application
If you are defining a form function, select the name and application of your form.
Parameters
Enter the parameters you wish to pass to your function. Separate parameters with a
space.
For an executable (form) function:
• If you specify the parameter QUERY_ONLY=YES, the form opens in query-only
mode. Oracle Application Object Library removes this parameter from the list of
form parameters before opening the form in query-only mode.
Web HTML
The fields in the Web HTML and Web Host are only required if your function will be
accessed from Oracle Applications Framework. You do not need to enter any of these
fields for functions based on Oracle Developer forms.
HTML Call
The last section of your function URL is the HTML Call. The HTML Call is used to
activate your function. The function may be either a static web page or a procedure.
The syntax for this field depends on the function type.
For functions used with Mobile Application Server, enter the full name of your java class
file, including <package name>.<class name>. The class name and package name are case
sensitive. Mobile Application Server will try to load this class from the classpath as it
is. For example, ’oracle.apps.mwa.demo.hello.HelloWorld’.
Web Host
The fields in the Web HTML and Web Host are optional and only enabled for some types
of functions. These fields apply only to Oracle Applications Framework functions.
Host Name
The URL (universal resource locator) or address required for your function consists of
three sections: the Host Name, Agent Name, and the HTML Call. The Host name is the
IP address or alias of the machine where the Web server is running.
Agent Name
The second section of your function URL is the Oracle Web Agent. The Oracle Web
Agent determines which database is used when running your function. Defaults to
the last agent used.
Secured
Secured is only required when your function is accessed by Oracle Workflow. Checking
Secured enables recipients of a workflow email notification to respond using email.
Menus Window
Used to define a new menu or modify an existing menu.
Menus Block
Menu entries detail the options available from your menu.
Menu
Choose a name that describes the purpose of the menu. Users do not see this menu name.
Note: Once the menu is saved, this menu name cannot be updated.
View Tree...
Once you have defined a menu, you can see its hierarchical structure using the "View
Tree..." button. See: Menu Viewer, page 4-27.
User Menu Name
You use the user menu name when a responsibility calls a menu or when one menu
calls another.
Menu Type
Specify a menu type to describe the purpose of your menu. Options include:
• Standard - for menus that would be used in the Navigator form
• Tab - for menus used in self service applications tabs
• Security - for menus that are used to aggregate functions for data security or specific
function security purposes, but would not be used in the Navigator form
In addition, see the section on Oracle Applications Framework menu types, page 4-38..
A menu entry with a lower sequence number appears before a menu entry with a higher
sequence number.
You cannot replace a menu entry sequence number with another sequence number that
already exists. If you want to add menu entries to a menu entry sequence, carefully
renumber your menu entries to a sequence range well outside the sequence range you
want, ensuring that you do not use existing sequence numbers. Once you save this
work, you can go back and renumber each entry to have the final sequence number
you want.
Submenu
Call another menu and allow your user to select menu entries from that menu.
Function
Call a function you wish to include in the menu. A form function (form) appears
in the Navigate window and allows access to that form. Other non-form functions
(subfunctions) allow access to a particular subset of form functionality from this menu.
Description
Descriptions appear in a field at the top of the Navigate window when a menu entry
is highlighted.
Grant
The Grant check box should usually be checked. Checking this box indicates that this
menu entry is automatically enabled for the user. If this is not checked then the menu
entry must be enabled using additional data security rules.
For more information on grants, see Overview of Data Security, page 4-11 and Grants,
page 4-33.
Menu Viewer
The Menu Viewer is a read-only window that provides a hierarchical view of the
submenus and functions of a menu, and also lists properties of the menus and functions.
You can launch the viewer from the Menus form by clicking on the "View Tree..."
button. The viewer will appear for the menu specified in the Menus form.
Note: When you are creating or editing a new menu, your changes must
be committed to the database before you will be able to see them in the
Menu Viewer.
Functionality
Menu Tree
To view the menu tree, click on the plus (+) sign next to the menu. You will see a
hierarchical tree with a number of nodes. Each node represents a function or submenu of
your main menu.
Note: The menu tree displays the user menu name for the main
menu, and displays the prompts from the Menus form for submenus
and functions. If no prompt has been specified, then no label will appear
for the node.
View Options
The View menu provides options on how the viewer displays your menu.
You can specify whether the Node Properties pane, the toolbar, or the status bar are
displayed. You can also choose the display style in which you view your menu tree.
Display Styles
There are three styles for viewing your menu tree. You can select one from the View
menu or from the buttons on the toolbar.
Vertical
Menu entries are displayed vertically, similar to how they appear in the Navigator
window when you log on to Oracle Applications.
Interleaved
Menu entries are displayed horizontally and vertically.
Org-Chart
Menu entries are displayed horizontally as in an organizational chart.
Edit Menu
From the Edit menu you can bring up a Properties window for the node you have
highlighted in the menu tree.
Note: You can view the properties for your menu or function here, but
you cannot edit them.
You can view and edit your Preferences for the Menu Viewer. You can choose colors for
your menu tree pane as well as the text font and size.
Objects
Use these pages to find, create, and edit data objects. You define objects to be secured in
the Data Security system.
Objects can be tables or views. An object must be queryable in SQL, and the combination
of primary key columns specified must be a unique key.
In these pages, objects are described with the following
• The Name is the name that appears in the Object Instance Set and Grants pages. This
name should be user-friendly.
• The Code is the internal name of the object.
• The Application Name is the owning application.
• The Database Object Name is the name of the underlying database object.
Find Objects
Use this page to find an existing object.
Simple Search
Name
The display name of the object.
Code
The object name.
Application Name
The object’s owning application.
Advanced Search
Use the Advanced Search screen to find data that meet a set of criteria. With the
Advanced Search screen, you can enter in special conditions based on the given
fields, and the search results will consist of all data that match the conditions.
For example, for a specified application, you can search for all objects whose name
begins with a letter before "P". (Note: all uppercase letters precede all lowercase letters
for this type of search).
Search Results
The search results are shown in a table with the following columns:
• Name - click on the object name to view details on the object.
• Code
• Application Name
• Database Object
• Description
• Last Update
To update an object, click on the icon under the Update column.
Update Object
Use this page to update the fields listed below for an object. You cannot change the
internal Object Name of an existing object.
Application Name
The owning application for the object. This application owns the database table on
which the object is based.
Description
Enter a description for the object.
Create Object
Use this page to create a new object. Enter the following information:
Name
Enter a user-friendly name for the object.
Code
Enter a code that will be used as an internal name for the object. This name cannot
include spaces and can include underscores and hyphens. You cannot update the object
name after the object is created and saved.
Application Name
The owning application for the object. This application owns the database table on
which the object is based.
Database Object
Typically this is a table in the database.
Description
Enter a description for the object.
Columns
You can also view details on columns that comprise the primary key (n below indicates
an integer between 1 and 5):
• PKn Column Name
• PKn Column Type
Instances of an object can be grouped together into an object instance set. For
example, you may want to create a group of projects or a group of items. To create and
manage objects instance sets, click on the "Manage Object Instance Sets" button.
Click on the "Return to Object Search" link to go back to the main Objects page.
Delete Object
Confirm the deletion of an object from this page. Review the information shown, and
click the "Delete" button.
Related Topics
Object Details, page 4-31
Related Topics
Objects, page 4-28
Code
Enter a name that will be used internally for the object instance set. This name cannot
include spaces and can include underscores and hyphens. The Object Instance Set Name
cannot be updated once the object instance set has been created and saved.
Name
Enter a user-friendly, descriptive name to appear in the Grants pages.
Description
Enter a description for the object instance set.
Predicate
This predicate determines which object instances are included in the set. Do not include
"WHERE" in your entry, but only the body of the WHERE clause.
Display Name
Enter a user-friendly, descriptive name to appear in the Grants pages.
Description
Enter a description for the object instance set.
Predicate
This predicate determines which object instances are included in the set. Do not include
"WHERE" in your entry, but only the body of the WHERE clause.
Related Topics
Object Instance Set Details, page 4-33
Related Topics
Object Instance Sets, page 4-31
Grants
Search Grants
Use this page to search for grants.
You can search using the following criteria:
• Name
• Grantee Type - Select from one of the following:
Create Grant
Use these pages to create a grant. Grants are used to manage user access to product
functionality. In these pages you give access to functions to specified users.
Related Topics
Overview of Data Security, page 4-11
Dene Grant
In this page you specify basic information for the grant.
To define a grant:
1. Enter a name and description for your grant.
2. Enter effective dates for your grant.
3. Enter the security context information.
The security context defines the circumstances in which the grant is active.
For Grantee, you can select a single user, a role, or global (all users and roles).
4. For Operating Unit, specify an operating unit if you want your grant to apply to a
specific one.
5. For Responsibility, specify a responsibility if you want your grant to apply to a
specific one.
6. Enter the Data Security information if you are creating a data security policy for an
object. The grant applies to the object you specify.
If you are not creating a data security policy, you will skip the next step.
Note: You cannot change a data security policy once it has been
saved. You can delete it or provide an end date to a data security
policy.
Update Grant
Use this page to update the definition of your grant.
View Grant
Use this page to view details for a grant, including:
• Security Context
• Object information, if applicable
• Set information
You can update or delete a grant from this page.
Function Types
When you define a function, you assign it one of the following types:
• Form - an Oracle Forms form function
• Mobile Application - a function used in an Oracle mobile application
• Database Provider Portlet
• JSP Interoperable with OA
• Generic Plug
• Plug
• Process
• SSWA JSP function
• SSWA PL/SQL function
• SSWA PL/SQL function that opens a new window (kiosk mode)
• SSWA servlet function
• Web Provider portlet
Related Topics
Form Functions Window, page 4-21
Search
Using Simple Search, You can search for functions using the following criteria:
• Name
• Code
• Type
Advanced Search
Using Advanced Search, you can be more flexible with your criteria, as well as search
on the description field.
Create Function
Use these pages to create a function.
1. Specify a name for the function.
2. Specify a code for the function. The code is the internal name for the function. Once
the function has been saved, the code cannot be updated.
Update Function
Use this page to update an existing function. Note that you cannot update the code
for an existing function.
To update a function:
1. Specify a name for the function.
2. If this function applies to a specific object, specify the object.
3. Specify a type for the function.
4. For context dependence, specify ’None’ or Responsibility.
To update function details:
1. If this is a form function, select the name and application of your form.
2. If the function applies to a specific object, you can update the object name and
specify parameters.
In updating menus,
• You can remove the function from menus containing it using the Menus subtab.
• You can also update menu prompts and descriptions for the function here.
Note: Maintenance Mode Support is reserved for future use only.
Duplicate Function
Use this page to duplicate an existing function.
Note that you must enter a unique code for the new function you are creating.
To duplicate a function:
1. Specify a name for the function.
2. Specify a code for the function. The code is the internal name for the function. Once
the function has been saved, the code cannot be updated.
3. Specify a type for the function.
4. Specify the level of maintenance mode support for the function.
5. For context dependence, specify ’None’ or Responsibility.
6. If you are defining a form function, select the name and application of your form. If
the function applies to a specific object, select the object name and specify parameters.
View Function
Use this page to view details on an existing function.
Delete Function
Use this page to delete a function.
Navigation Menus
Define a new menu or modify an existing menu.
A menu is a hierarchical arrangement of functions and menus of functions. Each
responsibility has a menu assigned to it.
You can build a custom menu for that responsibility using predefined
forms. However, we recommend that you do not disassociate a form from its
developer-defined menus.
Before creating a menu, perform the following:
• Register your application with Oracle Application Object Library using the
Forms-based Applications window.
• Define any menus that you intend to call from your menu. Define the lowest-level
submenus first. A submenu must be defined before it can be called by another menu.
Tip: By calling submenus from your menu, you can group related
windows together under a single heading on your menu. You can
reuse your menu on other menus.
Terms
Terms used in defining menus include:
• Name - The display name for the menu
• Code - The internal name for the menu
• Type - The purpose of the menu
• Permission Set - For menus that are used to aggregate functions for data security
or specific function security purposes, but would not be used in the Navigator
form.
• Standard - For menus used in the Navigator form
• App Pref Menu Container - For preferences
• Global Menu - For providing access to tasks and content that are applicable to
the entire application
• HTML Side Navigator Menu
• HTML SideBar
• HTML SideList
• HTML Sub Tab - A tab-like control for switching content or action views in
the page’s content area. Sub tabs can be used with a horizontal navigation
element, with a tab and horizontal navigation elements, or with a side navigation
• HTML Tab
2. If this menu entry is a menu itself (a submenu), enter in the menu name.
You can call another menu and allow your user to select menu entries from that
menu.
3. If this menu entry is a function, enter in the function name.
Call a function you wish to include in the menu.
4. Specify the function type.
5. Apply your changes.
If you want to reorder the menu entries, click the Reorder button.
Menu Manager
Once you have your menu defined, you can update its list of entries in the Menu
Manager tab.
Direct Parents
The Direct Parents subtab allows the user to see the direct parent(s), if any, of the
navigation menu. A direct parent is a menu that contains this menu directly as a
submenu. This feature is useful in identifying the direct impact of any changes that
may be made to this menu.
For each parent, the prompt and internal menu name is shown.
Grants
The Grants subtab displays the associated grants that secure the navigation menu.
For each associated grant the following is shown: name, grantee type, grantee, valid
dates, data context type, object, and instance set.
Update Menu
Use this page to update an existing navigation menu.
All fields can be updated except for the menu code.
The direct parents of a menu can be deleted in the Direct Parents tab.
You cannot update a parent menu from this tab. You must navigate to the parent menu
record itself to update it.
Note: You cannot replace an existing parent menu with another
menu, as the parent menu is used as the primary key of the hierarchy
mapping. Instead, you have to delete this existing (child) menu and add
a new menu. Also, the sequence number cannot be updated since it is
the primary key. You can update the prompt and description.
Duplicate Menu
Use this page to duplicate a menu and copy its hierarchy of children. You must give the
duplicate menu and new code (internal name).
View Menu
Use this page to view details of a menu.
Delete Menu
Use this page to delete a menu.
Note that you cannot delete a referenced menu. A menu can be referenced by any of
the following:
• Children (menu or function)
• Menu parents
Permissions
A permission is the smallest unit of securable action that can be performed on the
system. A permission can either be abstract permissions or executable functions
(menu). It can either be a system level permission or be sensitive to a data context. For
example, a particular JSP page may be an executable permission and "View Person"
may be an abstract permission.
You can search for permissions from the main page. You can update, duplicate, or
remove a permission found in your search results. You can also create a new permission
from this page.
Search for permissions using the following criteria:
• Name
• Code
• Object Name
Create Permission
Use these pages to create a permission.
1. Specify a name for the permission.
2. Specify a code for the permission. The code is the internal name for the
permission. Once the permission has been saved, the code cannot be updated.
3. If this permission applies to a specific object, specify the object.
4. If you want to add this permission to a permission set now, select a permission set.
Update Permission
Use this page to update an existing permission.
Note that you cannot update the code (internal name) for the permission.
1. You can specify a new name for the permission.
2. You can specify a new object if the permission applies to a specific object.
You can update the permission set information as well:
1. To add this permission to a permission set, select a permission set from the list of
values for "Add this to a Permission Set".
2. To delete this permission from a permission set, select the permission set in the table
and click the Remove button.
Select the Apply button to save your changes.
Duplicate Permission
Use this page to duplicate an existing permission.
Note that you must enter a unique code for the new permission you are creating.
1. Specify a name for the permission.
View Permission
Use this page to view details on an existing permission.
You can update or duplicate a permission from this page. You can delete a permission
from this page if it does not belong to a permission set.
Delete Permission
Use this page to delete a permission.
Permission Sets
Permission sets provide a way to group related permissions together. You can create a
new permission set from this page.
You can search for permission sets using the following criteria:
• Name
• Code
You can update, duplicate, or delete permission sets found in your search.
Direct Parents
The Direct Parents subtab allows you to see the permission sets, if any, that include the
current permission set. This feature is useful in identifying the direct impact of any
changes that may be made to this permission set.
Grants
The Grants subtab displays the associated grants that secure the navigation menu.
For each associated grant, the name, grantee type, grantee, valid dates, data context
type, object name, and instance set name is displayed.
Everything
This parameter takes the value Yes or No. "No" is used to recompile only those entities
that are marked as needing recompilation. "Yes" is used to recompile all entities, and can
take a long time. "No" is the default value.
Report Parameters
Application Name
Choose the name of the application to which the responsibility you want in your report
belongs.
Report Heading
The report heading indicates the application name and responsibility for which you
requested a report.
Column Headings
User Name
The name of the user who is assigned to the responsibility.
Start Date
The date the responsibility became active for the user.
End Date
The date the responsibility either becomes inactive or became inactive for the user. If no
end date appears for a user, then this responsibility is always enabled for the user.
Description
The description of the user who is assigned to the responsibility.
Related Topics
Overview of Oracle Applications Security, page 4-1
Defining a Responsibility, page 4-2
Overview of Function Security, page 4-6
Responsibilities field help, page 4-14
Users field help, page 4-18
Report Parameters
None.
Report Heading
This displays the name of the report, the date and time the report was run, and the
page number.
Application Name
The name of the application associated with the responsibility.
Responsibility Name
The name of the currently active responsibility.
User Name
The name of the user who can currently access the responsibility.
Start Date
The date when the user can begin accessing the responsibility.
End Date
The date when the user can no longer access the responsibility. See: Overview of Oracle
Applications Security, page 4-1.
Related Topics
Overview of Oracle Applications Security, page 4-1
Defining a Responsibility, page 4-2
Responsibilities field help, page 4-14
Users field help, page 4-18
Report Parameters
None.
Report Heading
The report heading displays the name of the report, the date that the report was run, and
the page number.
Column Headings
User Name
The Oracle Applications name of the currently active user. The start and end dates that
you specify in the Users window determine whether a username is currently active.
Responsibility Name
The name of the currently active responsibility.
Start Date
The date when the user can begin accessing the responsibility. You can specify a start
date when you assign the responsibility to the user in the Responsibilities block of the
Users window.
End Date
The date when the user can no longer access the responsibility. You specify an end date
when you assign the responsibility to the user in Responsibilities block of the Users
window.
Report Parameters
If you enter no parameters, the report documents all reports and report sets accessible
from each responsibility.
Responsibility Name
Choose the name of a responsibility whose available reports and report sets you wish
to report on. You must enter a value for Application Short Name before entering a
value for Responsibility Name.
Report Headings
The report headings list the report parameters you specify, and provide you with general
information about the contents of the report.
Related Topics
Overview of Oracle Applications Security, page 4-1
Defining a Request Security Group, page 4-3
Responsibilities field help, page 4-14
Related Topics
Auditing User Activity, page 5-2
Setting Up Sign-On Audit, page 5-2
Sign-On Audit Reports, page 5-5
Monitor Users, page 5-20
Reporting on AuditTrail Data, page 5-6
Setting Up AuditTrail, page 5-7
AuditTrail Tables, Triggers and Views, page 5-7
Reporting on Audit Information, page 5-14
Disabling AuditTrail and Archiving Audit Data, page 5-14
Audit Installations, page 5-21
Major Features
Selective Auditing
Sign-On Audit lets you choose who to audit and what type of user information to
track. You can selectively determine what audit information you need, to match your
organization’s needs.
After you set or change audit levels, the new audit levels for a user take effect the next
time the user signs onto Oracle Applications from the operating system.
Related Topics
Overview of User and Data Auditing, page 5-1
Auditing User Activity, page 5-2
Setting Up Sign-On Audit, page 5-2
Sign-On Audit Reports, page 5-5
Monitor Users, page 5-20
AuditTrail
Oracle Applications Releases 10.4 and above provide a mechanism based on Oracle
database triggers. AuditTrail stores change information in a "shadow table" of the
audited table. This mechanism saves audit data in an uncompressed but "sparse"
format, and you enable auditing for particular tables and groups of tables ("audit
groups").
Related Topics
Overview of User and Data Auditing, page 5-1
Reporting on AuditTrail Data, page 5-6
Setting Up AuditTrail, page 5-7
Reporting on Audit Information, page 5-14
Disabling AuditTrail and Archiving Audit Data, page 5-14
Audit Installations, page 5-21
Audit Groups, page 5-23
Audit Tables, page 5-25
Its shadow table is as the following (assuming you audit all your table columns):
SQL> DESCRIBE AUDIT_DEMO_A
Views
After a shadow table is created, views onto the shadow table are created to allow easier
access to the data in the "sparse" rows. These views simplify tasks such as querying a
row/column’s value on a given date and tracking changes to a row/column over time.
The view name contains the first 24 characters of the audited table name plus "_AC#"
or "_AV#" where C or V indicates the type of view and # indicates a number. Due to
limitations in creation size, the shadow table columns may need to be broken into
multiple views, which are numbered sequentially.
Each view allows slightly different access to the data. One allows the user to reconstruct
the value for a row at a given time (_AC), while the other provides simple access to
when a value was changed (_AV).
For our example table, the _AV1 and _AC1 views are created as follows:
SQL> DESCRIBE AUDIT_DEMO_AV1
After our two inserts and six updates, the final values in the audited table are:
KEY VAL_1 VAL_2 VAL_3
---- ----- ----- -----
1 C B B
2 Y X X
The final values in the corresponding shadow table are as follows. A row in the shadow
table represents the state of the audited row before the audited row was changed. Note
that if a value in a row doesn’t change during the transaction, the shadow table records
a null for that value in that transaction.
In our example, the first two rows in the shadow table represent the state where there
was no data for our two audited rows before they were inserted. The "prior values" are
null values for the two insert transaction (type I) rows. Similarly, when we update the
first value of row 1 to be the value B instead of A, the shadow table records the value
A in its third row:
SQL> SELECT TO_CHAR(AUDIT_TIMESTAMP, ’HH24:MI:SS’) TIME,
AUDIT_TRANSACTION_TYPE TYPE, AUDIT_USER_NAME NAME,
PRIMARY_KEY KEY, VALUE_ONE VAL_1, VALUE_TWO VAL_2,
VALUE_THREE VAL_3, AUDIT_TRUE_NULLS FROM AUDIT_DEMO_A;
8 rows selected.
10 rows selected.
Important: If the changes to your audited table occur faster than one
change per second (that is, more frequently than the one-second
granularity provided by SYSDATE), you may see "blurring" of records
(i.e. more than one record per transaction) in the _AC view, because
of joins used in this view. However, the shadow table itself remains
correct, and you can resolve the relevant transactions by referring to
the shadow table directly.
The _AV1 view provides a more sparse view of the audit data, ordered by timestamp:
10 rows selected.
Here is an example of how you might use a view to determine who changed a particular
value and when:
SQL> SELECT TO_CHAR(AUDIT_TIMESTAMP, ’HH24:MI:SS’) TIME,
AUDIT_TRANSACTION_TYPE TYPE, AUDIT_USER_NAME NAME
FROM AUDIT_DEMO_AV1
WHERE PRIMARY_KEY = 1
AND VALUE_ONE = ’B’;
Similarly, you might want to determine who changed a value to null and when:
SQL> SELECT TO_CHAR(AUDIT_TIMESTAMP, ’HH24:MI:SS’) TIME,
AUDIT_TRANSACTION_TYPE TYPE, AUDIT_USER_NAME NAME
FROM AUDIT_DEMO_AV1
WHERE PRIMARY_KEY = 1
AND VALUE_ONE IS NULL
AND SUBSTR(AUDIT_TRUE_NULLS,2,1) = ’Y’;
Related Topics
Overview of User and Data Auditing, page 5-1
Reporting on AuditTrail Data, page 5-6
Setting Up Release AuditTrail, page 5-7
AuditTrail Tables, Triggers and Views, page 5-7
Disabling AuditTrail and Archiving Audit Data, page 5-14
Audit Installations, page 5-21
Audit Groups, page 5-23
Audit Tables, page 5-25
Related Topics
Overview of User and Data Auditing, page 5-1
Reporting on AuditTrail Data, page 5-6
Setting Up AuditTrail, page 5-7
AuditTrail Tables, Triggers and Views, page 5-7
Reporting on Audit Information, page 5-14
Audit Installations, page 5-21
Audit Groups, page 5-23
Audit Tables, page 5-25
Template Name
Enter the name of the desired Audit Template.
Functional Areas
• Functional Group - Enter the functional group associated with this template. This
is the same as the Audit Group field on the Audit Group window in System
Administration.
Auditing Navigation
In addition to the standard menu and toolbar, a navigator tree provides a hierarchical
display of the objects in a treelike framework.
Functional Group
Specify the name of the functional group for the report. This is the same as the Audit
Group field on the Audit Group window in System Administration.
Transacted By (Optional)
Specify the user who is requesting the report.
To Date (Optional)
Specify the end date for the date range the report will run.
As well as seeing which users are signed on, you can see:
• Which responsibilities, forms (windows), and terminals they are using
• How long they have been logged in
• What Oracle database processes they are using
In addition, you can monitor all users at a site, all users accessing a specific application
or a specific responsibility, or individual users.
Note: You can only monitor those users for whom you have activated
Sign-On Audit. See: Overview of User and Data Auditing, page 5-1
Prerequisites
• Select a value for the Sign-On:Audit Level profile option, using the Update System
Profile Options window.
Related Topics
Overview of User and Data Auditing, page 5-1
Auditing User Activity, page 5-2
Setting Up Sign-On Audit, page 5-2
Sign-On Audit Reports, page 5-5
For auditing to take effect, you must also define one or more audit groups and run the
Audit Trail Update Tables report. See: Reporting on AuditTrail Data, page 5-6.
Prerequisites
❒ Register your Oracle username. See: ORACLE Users, Oracle Applications System
Administrator's Guide - Configuration.
Related Topics
Overview of User and Data Auditing, page 5-1
Reporting on AuditTrail Data, page 5-6
Setting Up AuditTrail, page 5-7
AuditTrail Tables, Triggers and Views, page 5-7
Reporting on Audit Information, page 5-14
Disabling AuditTrail and Archiving Audit Data, page 5-14
First, identify the tables you want to audit, then, using the Audit Tables window, select
which columns in each table you wish to audit. Or, select which columns in a particular
table you wish to audit (using the Audit Tables window), then define your audit group
(using this window).
To enable or disable auditing for the tables in your audit group, run the Audit Trail
Update Tables program using the Submit Requests window. If you change the definition
or audit state of your group later, you must rerun this program.
Ensure you have done the following before defining your audit groups:
• Define an audit installation using the Audit Installations window.
Important: Your tables and their primary key information must
already be registered and defined for successful auditing. If the table
you want to audit is a custom table (not shipped as part of Oracle
Applications), you should also perform the following two steps:
To disable auditing for a group, choose one of the following options and then run the
Audit Trail Update Tables report to have your changes take effect.
Disable - Prepare for
Archive
Copies the current values of all rows in the audited table into the shadow table, and then
disables the auditing triggers. This option requires the most space, since there is at least
one row in the shadow table for every row in the audited table (and another row in the
shadow table for each transaction on the original row in the audited table). You should
then archive the table before you empty the shadow table.
Disable - Interrupt Audit
Modifies the triggers to store one final row in the shadow table as the audited row is
modified in the audit table (remember that a given row in the shadow table represents
the data in the audited row before an update). Inserts or further changes are no longer
audited. The shadow table then grows slowly, and the data may be accessed by the
existing audit views.
Disable - Purge Table
Drops the auditing triggers and views and deletes all data from the shadow table.
Related Topics
Overview of User and Data Auditing, page 5-1
Reporting on AuditTrail Data, page 5-6
Setting Up AuditTrail, page 5-7
AuditTrail Tables, Triggers and Views, page 5-7
Reporting on Audit Information, page 5-14
Disabling AuditTrail and Archiving Audit Data, page 5-14
Audit Installations, page 5-21
Audit Tables, page 5-25
First, identify the columns in a table you want to audit. Then, using the Audit Groups
window, include the table as part of an audit group. Or, you may define your audit
group first (using the Audit Groups window), and then select which columns in the table
you want to audit (using this window).
To enable or disable auditing for the tables in your audit group (i.e., the columns you
have selected here), you must run the Audit Trail Update Tables program using the
Submit Requests window. If you select additional columns to audit, or change the
definition or audit state of your group later, you must rerun this program.
Ensure the following is done before defining your audit tables:
• Define an audit installation using the Audit Installations window.
Important: Your tables and their primary key information must
already be registered and defined for successful auditing. If the table
you want to audit is a custom table (not shipped as part of Oracle
Applications), you should also perform the following two steps:
• Register your table and its primary key columns using Oracle Application Object
Library’s Tables window (Application Developer Responsibility).
• Run the Register Tables concurrent program from the Submit Requests window.
Related Topics
Overview of User and Data Auditing, page 5-1
Report Parameters
Sort By
Sort the information in your report by operating system login name, the requested start
date, and/or application username.
Login Name
Search for a specific login name that meets your other search criteria. If you leave this
parameter blank, your report contains all login names that meet your other search
criteria.
User Name
Search for a specific application username that meets your other search criteria. If you
leave this parameter blank, your report contains all application usernames that meet
your other search criteria.
Report Heading
The report heading displays the search criteria you entered as parameter values.
Login Name
The operating system login name of the user who submitted the concurrent request.
Request ID
The concurrent request ID of the submitted concurrent request. Use the Concurrent
Requests form to view completion information for a concurrent request ID.
User Name
The Oracle Applications username of the user who submitted the concurrent request. Use
the Users form to view detail information about an application user. See: Users, page
4-18.
Responsibility Name
The name of the responsibility from which the user submitted the concurrent
request. The responsibility displays only if you audited the user at the responsibility or
form Sign-on Audit level. Use the Responsibilities form to view detailed information
about a responsibility. See: Responsibilities, page 4-14.
Form Name
The name of the form from which the user submitted the concurrent request. The form
name displays only if you audited the user at the form Sign-On Audit level.
Related Topics
Overview of User and Data Auditing, page 5-1
Auditing User Activity, page 5-2
Setting Up Sign-On Audit, page 5-2
Sign-On Audit Reports, page 5-5
Monitor Users field help, page 5-20
Sort By
Sort the information in your report by the time users entered or left a form, the name of
the form that users access, the operating system login name of the user, the responsibility
users access, the terminal that users are on, and/or the application username.
Login Name
Search for information about a specific login name that meets your other search
criteria. If you leave this parameter blank, your report contains all login names that
meet your other search criteria.
User Name
Search for information about a specific application username that meets your other
search criteria. If you leave this parameter blank, your report contains all application
usernames that meet your other search criteria.
Terminal Name
Search for information about a specific terminal that meets your other search criteria. If
you leave this parameter blank, your report contains all terminal names that meet your
other search criteria.
Responsibility Name
Search for information about a specific responsibility that meets your other search
criteria. If you leave this parameter blank, your report contains all responsibilities that
meet your other search criteria.
Form Name
Search for information about a specific form that meets your other search criteria. If you
leave this parameter blank, your report contains all forms that also meet your other
search criteria.
Report Heading
The report heading displays the search criteria you entered as parameter values.
Column Headings
Username
The Oracle Applications username of the user who accessed the form. Use the Users
form to view detailed information about an application user. See: Users, page 4-18.
Terminal Name
The operating system ID of the terminal from which the user accessed the form.
Responsibility Name
The name of the responsibility from which the user accessed the form. The
responsibility displays only if you audited the user at the responsibility or form Sign-on
Audit level. Use the Responsibilities form to view detailed information about a
responsibility. See: Responsibilities, page 4-14.
Form Name
The name of the form that the user accessed. The form name displays only if you audited
the user at the form Sign-on Audit level.
Related Topics
Overview of User and Data Auditing, page 5-1
Auditing User Activity, page 5-2
Setting Up Sign-On Audit, page 5-2
Sign-On Audit Reports, page 5-5
Monitor Users field help, page 5-20
Report Parameters
Sort By
Sort the information in your report by the time users entered or left a responsibility, the
operating system login name of the user, the responsibility name, the terminal that users
are on, and/or the application username.
Login Name
Search for information about a specific login name that meets your other search
criteria. If you leave this parameter blank, your report contains all login names that
meet your other search criteria.
Terminal Name
Search for information about a specific terminal that meets your other search criteria. If
you leave this parameter blank, your report contains all terminal names that meet your
other search criteria.
Responsibility Name
Search for information about a specific responsibility that meets your other search
criteria. If you leave this parameter blank, your report contains all responsibilities that
meet your other search criteria.
Report Heading
The report heading displays the search criteria you entered as parameter values.
Column Headings
Username
The Oracle Applications username of the user who selected the form. Use the Users form
to view detail information about an application user. See: Users, page 4-18.
Login Name
The operating system login name of the user who selected the responsibility.
Terminal Name
The operating system ID of the terminal from which the user selected the responsibility.
Responsibility Name
The name of the responsibility the user used. The responsibility displays only if you
audited the user at the responsibility or form Sign-on Audit level. Use the Responsibilities
form to view detailed information about a responsibility. See: Responsibilities, page 4-14.
Report Parameters
Sort By
Sort the information in your report by the time users attempt to login, operating system
login name of the user, the terminal that users are on, and/or the application username.
Login Name
Search for information about a specific login name that meets your other search
criteria. If you leave this parameter blank, your report contains all login names that
meet your other search criteria.
User Name
Search for information about a specific application username that meets your other
search criteria. If you leave this parameter blank, your report contains all application
usernames that meet your other search criteria.
Terminal Name
Search for information about a specific terminal that meets your other search criteria to
make your report as brief as you need. If you leave this parameter blank, your report
contains all terminal names that meet your other search criteria.
Report Heading
The report heading displays the search criteria you entered as parameter values.
Username
The Oracle Applications username of the user who unsuccessfully tried to sign on. Use
the Users form to view detail information about an application user. See: Users, page
4-18.
Login Name
The operating system login name of the user who unsuccessfully tried to sign on.
Terminal
The operating system ID of the terminal from which the user unsuccessfully tried
to sign on.
Attempt Time
The date and time when the user unsuccessfully tried to sign on. See: Monitor Users,
page 5-20.
Related Topics
Overview of User and Data Auditing, page 5-1
Auditing User Activity, page 5-2
Setting Up Sign-On Audit, page 5-2
Sign-On Audit Reports, page 5-5
Report Parameters
Sort By
Sort the information in your report by the time users start or finish using an application
username, the operating system login name of the user, the terminal that users are
on, and/or the application username.
Login Name
Search for information about a specific login name that meets your other search criteria
to make your report as brief as you need. If you leave this parameter blank, your report
contains all login names that meet your other search criteria.
Terminal Name
Search for information about a specific terminal that meets your other search criteria to
make your report as brief as you need. If you leave this parameter blank, your report
contains all terminal names that meet your other search criteria.
Report Heading
The report heading displays the search criteria you entered as parameter values.
Column Headings
Session Number
The Oracle Applications session number that uniquely identifies each application user
sign-on.
User Name
The Oracle Applications username of the user who signed on. Use the Users form to
view detailed information about an application user. See: Users, page 4-18.
Login Name
The operating system login name of the user who signed on.
Terminal Name
The operating system ID of the terminal from which the user signed on.
Oracle Process
The Oracle database process ID used during the user’s sign-on. Consult your database
administrator for more information concerning Oracle processes.
Related Topics
Overview of User and Data Auditing, page 5-1
Auditing User Activity, page 5-2
Setting Up Sign-On Audit, page 5-2
Sign-On Audit Reports, page 5-5
Monitor Users field help, page 5-20
Parameters
Audit Date
The Sign-On Audit information creation date. This program will delete all Sign-On
Audit information created before this date.
A D
Access Control with Oracle User Management, Data Security, 4-11
2-1 Access Control with Oracle User Management,
Account Creation by Administrators 2-2
Access Control with Oracle User Management, Data Security Policies
2-6 Defining Data Security Policies, 3-7
Application users Delegated Administration
assigning one or more responsibilities, 4-1 Access Control in Oracle Applications, 2-5
changing passwords, 4-20 Defining Delegated Administration Privileges
defining, 4-18 for Roles
disabling application password, 4-20 Organization Administration, 3-3
reporting on active users, 4-46 Role Administration, 3-3
start dates, 4-20 User Administration, 3-3
username characteristics, 4-18
Applications security
defining a responsibility, 4-14 F
Audit Groups Window, 5-23 Forgot Password
Audit Installations Window, 5-21 Setting Up the Forgot Password Feature, 3-17
Audit reports Form Functions Window, 4-21
brief explanation, 5-5 Forms
listing, 5-1 Define Menu, 4-21, 4-25
Audit Tables Window, 5-25 Monitor Application Users, 5-20
Auditing database row changes Responsibility, 4-14
AuditTrail, 5-1 Function Security
Auditing user activity Access Control with Oracle User Management,
Sign-On Audit, 5-1 2-2
AuditTrail implementation, 4-10
archiving data, 5-15 Function Security Function Report, 4-44
audit groups, 5-6 Function Security Menu Report, 4-44
audit set, 5-6 Function Security Menu Viewer
changing audit tables, 5-6 Menu Viewer, 4-27
description, 5-6 Function Security Navigator Report, 4-44
introduction, 5-1
reporting, 5-14 H
setting up, 5-7
tables, 5-7 HRMS Security, 4-1
views, 5-9
M
C Menu Viewer, 4-27
Case sensitivity Menus
in user passwords, 4-5 compiling, 4-11, 4-43
configurable user name policy, 3-17 defining, 4-25
defining a menu entry, 4-26
entering arguments, 4-23
menu prompts, 4-27
Index-1
Menu Viewer, 4-27 reporting on active responsibilities, 4-45
role in function security, 4-1 reporting on reports and report sets, 4-47
sequence numbers, 4-26 reporting on users of, 4-44
Menus Window, 4-25 Start date, 4-16
Monitor Users Window, 5-20 Responsibilities Window, 4-14
Monitoring users Role Administration Privileges
Sign-On Audit, 5-4 Access Control in Oracle Applications, 2-5
Role Based Access Control (RBAC)
Access Control with Oracle User Management,
O 2-3
ORACLE ID Role Categories
assigning to responsibility, 4-16 Access Control with Oracle User Management,
Oracle User Management Setup Tasks 2-3
Defining Role Categories, 3-1 Defining Role Categories, 3-1
Organization Administration Privileges Role Inheritance Hierarchies
Access Control in Oracle Applications, 2-5 Access Control with Oracle User Management,
Organization Contacts 2-3
Registering External Organization Contacts, Defining Role Inheritance Hierarchies
3-22 Deployment Options, 3-7
Roles
P Assigning Permissions to Roles, 3-2
Assigning Roles to and Revoking Roles From
Password Users, 3-21
Reset Forgotten Password, 3-23 Creating and Updating Roles, 3-1
Resetting User Passwords, 3-20 Defining Delegated Administration Privileges
Passwords for Roles
case-sensitive, 4-5 Organization Administration, 3-3
People Role Administration, 3-3
Maintaining People and Users, 3-19 User Administration, 3-3
Permissions
Assigning Permissions to Roles, 3-2
S
R Security Groups
defining (for HRMS only), 4-17
Registration Processes Security groups, 4-6
Access Control with Oracle User Management, Security Groups Window, 4-17
2-6 Security in HRMS, 4-1
Creating and Updating Registration Processes, seeded user name policies, 3-17
3-14 Self Service Account Requests
Reports Access Control with Oracle User Management,
Active Responsibilities, 4-45 2-6
Active Users, 4-46 Self-Service and Approvals
Reports and Sets by Responsibility, 4-47 Access Control in Oracle Applications, 2-12
Signon Audit Concurrent Requests, 5-28 Self-Service Registration, 3-23
Signon Audit Forms, 5-29 Session time-out, 4-5
Signon Audit Responsibilities, 5-31 Sign-On Audit
Signon Audit Unsuccessful Logins, 5-33 audit levels, 5-3
Signon Audit Users, 5-34 examples using, 5-3
Users of a Responsibility, 4-44 introduction, 5-1
Requests for Additional Access, 3-23 monitoring users, 5-4, 5-20
Access Control with Oracle User Management, purging obsolete data, 5-36
2-6 reporting on users, 5-34
Responsibilities, 4-1 reporting on users and forms, 5-29
Application name, 4-15 reporting on users and requests, 5-28
deactivating, 4-16 reporting on users and responsibilities, 5-31
defining, 4-14 reporting on users and unsuccessful logins,
major components, 4-2 5-33
predefined, 4-2 reports, 5-5
Index-2
setting up, 5-2 Access Control in Oracle Applications, 2-5
using, 5-2 User session limits, 4-5
Users, 4-1
Assigning Roles to and Revoking Roles From
U Users, 3-21
Upgrading case-sensitive passwords, 4-5
preserving custom menus, 4-11 Maintaining People and Users, 3-19
User Accounts Resetting User Passwords, 3-20
Creating, Inactivating, and Reactivating User Users Window, 4-18
Accounts, 3-20
User Administration Privileges
Index-3