Oracle Apps System Admin Student Guide1

Volume 1 - Student Guide
D49195GC10
Edition 1.0
July 2007
D51749
THESE eKIT MATERIALS ARE FOR YOUR USE IN THIS CLASSROOM ONLY. COPYING eKIT MATERIALS FROM THIS
COMPUTER IS STRICTLY PROHIBITED
Oracle University and Egabi Solutions use only
R12 Oracle Applications System

Administrator Fundamentals
Copyright 1996, 2007, Oracle. All rights reserved.

This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and
print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way.
Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display,
perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization
of Oracle.
The information contained in this document is subject to change without notice. If you find any problems in the document, please
report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.
If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United
States Government, the following notice is applicable:
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.
Author
Mildred Wang, Robert Farrington, Clara Jaeckel, Melody Yang
Technical Contributors and Reviewers
Donna Johnson, Leta Davis, Barbara Waddoups, Gary Lemmons, Roman Kratochvil, Roger
Wigenstam, Venkata Vengala, Biju Mohan, Gursat Olgun, Maxine Zasowski, Sunil Ghosh
This book was published using:
oracletutor
U.S. GOVERNMENT RIGHTS

The U.S. Governments rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted
by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.
Table of Contents
Introduction to Oracle Applications Security ...............................................................................................2-1

Introduction to Oracle Applications Security ................................................................................................2-3
Objectives ......................................................................................................................................................2-4
Successive Layers of Access Control ............................................................................................................2-5
Increasing Flexibility and Scalability ............................................................................................................2-6
Function Security...........................................................................................................................................2-8
Data Security .................................................................................................................................................2-9
Oracle User Management Layers of Access Control.....................................................................................2-11
Role Based Access Control (RBAC) .............................................................................................................2-12
Delegated Administration..............................................................................................................................2-14
Registration Processes ...................................................................................................................................2-16
Self Service and Approvals ...........................................................................................................................2-18
Summary........................................................................................................................................................2-19
Function Security.............................................................................................................................................3-1
Objectives ......................................................................................................................................................3-4
Overview of Function Security......................................................................................................................3-5
Defining a New Application User .................................................................................................................3-7
Custom Applications .....................................................................................................................................3-8
Defining an Application ................................................................................................................................3-9
Registering an Oracle ID ...............................................................................................................................3-10
Data Groups...................................................................................................................................................3-11
Securing Functions ........................................................................................................................................3-13
Defining a Menu............................................................................................................................................3-14
Identifying Existing Menu Structures...........................................................................................................3-16
Menu Guidelines ...........................................................................................................................................3-17
Creating a Menu ............................................................................................................................................3-18
Modifying an Existing Menu Definition ......................................................................................................3-20
Navigator Menus ...........................................................................................................................................3-21
The Menu Viewer..........................................................................................................................................3-22
Viewing Node Properties in the Menu Viewer..............................................................................................3-23
Adding a Custom Form Function ..................................................................................................................3-24
Using Responsibilities ...................................................................................................................................3-25
Responsibility Components ...........................................................................................................................3-27
Defining a New Responsibility......................................................................................................................3-28
Responsibility Creation Process ....................................................................................................................3-29
Defining a New Responsibility......................................................................................................................3-30
Excluding Functions and Menus ...................................................................................................................3-31
Summary........................................................................................................................................................3-32
Introduction to Data Security.........................................................................................................................4-1
Objectives ......................................................................................................................................................4-4
Copyright Oracle Corporation, 2006. All rights reserved.
R12 System Administrator Fundamentals Table of Contents

i
THESE eKIT MATERIALS ARE FOR YOUR USE IN THIS CLASSROOM
ONLY. COPYING eKIT MATERIALS FROM THIS
Introduction .....................................................................................................................................................1-1
Introduction ...................................................................................................................................................1-3
Course Objectives..........................................................................................................................................1-4
Overview .......................................................................................................................................................1-5
Oracle Applications System Administration .................................................................................................1-6
Oracle Workflow Component........................................................................................................................1-7
Oracle Applications Flexfields Component...................................................................................................1-8
Additional Material........................................................................................................................................1-9
Introduction to Oracle User Management ....................................................................................................5-1

Introduction to Oracle User Management .....................................................................................................5-3
Objectives ......................................................................................................................................................5-4
What Is Oracle User Management? ...............................................................................................................5-5
Access Control Model ...................................................................................................................................5-6
Successive Layers of Access Control ............................................................................................................5-7
Increased Flexibility and Scalability..............................................................................................................5-8
Responsibilities..............................................................................................................................................5-10
Data Security .................................................................................................................................................5-11
Role Based Access Control (RBAC) .............................................................................................................5-12
Delegating to Proxy Users .............................................................................................................................5-15
Provisioning Services ....................................................................................................................................5-16
Self-Service and Approvals ...........................................................................................................................5-18
Login Assistance ...........................................................................................................................................5-19
Summary........................................................................................................................................................5-20
Implementing Oracle User Management.......................................................................................................6-1
Objectives ......................................................................................................................................................6-4
Steps for Implementing Oracle User Management........................................................................................6-6
Configuring and Testing Oracle User Management ......................................................................................6-9
Introduction to Roles .....................................................................................................................................6-10
Examples of Roles .........................................................................................................................................6-11
Defining Roles: Data Security Policies .........................................................................................................6-12
Defining Roles: Assigning a Single Responsibility and All Its Functions to a Role .....................................6-13
Assigning a Single Responsibility to a Role and Granting Specific Functions to a Role ..............................6-14
Defining Roles: Assigning Multiple Responsibilities to a Role ....................................................................6-15
Role Inheritance Hierarchies .........................................................................................................................6-16
Role Categories .............................................................................................................................................6-17
Assigning Permissions to Roles.....................................................................................................................6-18
Advantages of Roles Over Responsibilities...................................................................................................6-20
Phase II: Define Roles ...................................................................................................................................6-22
Steps for Creating Roles: Define a Role Category ........................................................................................6-23
Steps for Creating Roles: Create a Role within the Role Category ...............................................................6-24
Steps for Creating Roles: Place Role in Role Inheritance Hierarchy.............................................................6-25
Steps for Creating Roles: Assign Permissions to Roles.................................................................................6-26
Steps for Creating Roles: Assign Role to a New Person ...............................................................................6-27
Steps for Creating Roles: Test Role as Customer Administrator...................................................................6-28
What Is Delegated Administration?...............................................................................................................6-30
User Administration Privileges......................................................................................................................6-31
User Administration Privileges (cont.) ..........................................................................................................6-32
Role Administration Privileges......................................................................................................................6-33
Seeded Permissions for User Administration ................................................................................................6-34
Managing Roles with Role Administration ...................................................................................................6-35
Seeded Permissions for Role Administration ................................................................................................6-36
Organization Administration Privileges ........................................................................................................6-37
Seeded Permissions for Organization Administration ...................................................................................6-38

ii
Data Security Components - Objects.............................................................................................................4-7

Grants ............................................................................................................................................................4-8
Permissions and Permission Sets...................................................................................................................4-9
Data Security Policies....................................................................................................................................4-10
Example of a Data Security Policy ................................................................................................................4-11
Summary........................................................................................................................................................4-12
Profile Options .................................................................................................................................................7-1

Managing Profile Options..............................................................................................................................7-3
Objectives ......................................................................................................................................................7-4
Personal Profile Values .................................................................................................................................7-5
System Profile Options - Profile Hierarchy Types ........................................................................................7-6
Profile Hierarchy Levels - Security ...............................................................................................................7-7
Profile Hierarchy Levels Organization .......................................................................................................7-8
Profile Hierarchy Levels - Server ..................................................................................................................7-9
System Profile Options..................................................................................................................................7-10
Using User Profile Values as Defaults .........................................................................................................7-11
Profile Categories ..........................................................................................................................................7-12
Auditing Related Profile Options ..................................................................................................................7-13
Currency-Related Options .............................................................................................................................7-15
Flexfield-Related Options..............................................................................................................................7-16
Online Reporting-Related Options ................................................................................................................7-18
Personal Output Viewer Options ...................................................................................................................7-19
User-Related Concurrent Request Profile Options ........................................................................................7-20
Security Signon Profile Options ....................................................................................................................7-22
Summary........................................................................................................................................................7-24
Auditing System Resources.............................................................................................................................8-1
Auditing System Resources...........................................................................................................................8-3
Objectives ......................................................................................................................................................8-4
Auditing Oracle Applications ........................................................................................................................8-5
Auditing User Activity ..................................................................................................................................8-6
Signon Audit Profile Option..........................................................................................................................8-7
Signon Audit Reports ....................................................................................................................................8-8
Signon Audit Forms Report...........................................................................................................................8-9
Signon Audit Concurrent Requests Report....................................................................................................8-10
Signon Audit Responsibilities Report............................................................................................................8-11
Signon Audit Unsuccessful Logins Report....................................................................................................8-12
Signon Audit Users Report............................................................................................................................8-13
Purge Audit Records......................................................................................................................................8-14
Monitor Users Window .................................................................................................................................8-15
Auditing Database Changes...........................................................................................................................8-16
Steps for Setting Up AuditTrail.....................................................................................................................8-17

iii
Delegated Administration vs. Traditional System Administration ................................................................6-39

Phase III: Setting Up Delegated Administration ...........................................................................................6-40
Steps for Implementing Delegated Administration: Set Up User Administration for a Role ........................6-41
Steps for Implementing Delegated Administration .......................................................................................6-42
Registration Processes ...................................................................................................................................6-45
Registration Processes: Core Components ....................................................................................................6-47
Self-Service Account Requests......................................................................................................................6-48
Requests for Additional Access.....................................................................................................................6-49
Account Creation by Administrators .............................................................................................................6-50
Phase IV: Creating Registration Processes ....................................................................................................6-51
Steps for Creating Registration Processes: Provide Required Description Information................................6-52
Steps for Creating Registration Processes: Enter Runtime Execution Information.......................................6-54
Steps for Creating Registration Processes: Enter Eligibility Information......................................................6-55
Steps for Creating Registration Processes: Register Subscriptions to Business Events ................................6-56
Steps for Creating Registration Processes: Optionally Set Profile Options...................................................6-57
Steps for Creating Registration Processes: Optionally Set Login Page UI Attributes...................................6-59
Steps for Creating Registration Processes: Test as Customer Administrator ................................................6-61
Managing Proxy Users ..................................................................................................................................6-62
Self-Service Features.....................................................................................................................................6-64
Login Assistance ...........................................................................................................................................6-66
Summary........................................................................................................................................................6-67
Managing Printers...........................................................................................................................................9-1
Managing Printers..........................................................................................................................................9-3
Objectives ......................................................................................................................................................9-4
Oracle Print Definition Components .............................................................................................................9-5
Relationships of the Printer Components ......................................................................................................9-7
Formatting Information .................................................................................................................................9-8
Defining Printers............................................................................................................................................9-10
Finding Existing Printer Types......................................................................................................................9-11
Registering a New Printer..............................................................................................................................9-12
Defining a New Printer Type.........................................................................................................................9-13
Printing with Pasta.........................................................................................................................................9-14
Setup for Basic Printing with Pasta ...............................................................................................................9-15
The pasta.cfg file ...........................................................................................................................................9-16
Modifying an Existing Printer Type to Use Pasta .........................................................................................9-17
Generating Other Formats using the Preprocessing Option...........................................................................9-19
Using Pasta with XML Publisher ..................................................................................................................9-20
Other Customization Materials for Oracle Applications Printing..................................................................9-22
Summary........................................................................................................................................................9-23
Introduction to Oracle Applications Manager..............................................................................................10-1
Introduction to Oracle Applications Manager (OAM) ..................................................................................10-3
Objectives ......................................................................................................................................................10-4
What is Oracle Applications Manager? .........................................................................................................10-5
Benefits of Oracle Applications Manager......................................................................................................10-6
Oracle Applications Manager Integrates with ..........................................................................................10-7
Application Management Pack for Oracle E-Business Suite.........................................................................10-9
Navigation in OAM .......................................................................................................................................10-10
Applications Dashboard ................................................................................................................................10-11
Site Map.........................................................................................................................................................10-13
Administration...............................................................................................................................................10-14
Monitoring.....................................................................................................................................................10-15
Maintenance ..................................................................................................................................................10-16
Diagnostics and Troubleshooting ..................................................................................................................10-17
Setting Up Oracle Applications Manager......................................................................................................10-18
Summary........................................................................................................................................................10-19
System Monitoring in Oracle Applications Manager...................................................................................11-1
System Monitoring in Oracle Applications Manager ....................................................................................11-3
Objectives ......................................................................................................................................................11-4
System Status Overview................................................................................................................................11-5
System Status Configuration Changes........................................................................................................11-7
System Status Web Components Status .....................................................................................................11-8
System Status System Alerts ......................................................................................................................11-10
System Status User Initiated Alerts ............................................................................................................11-12
Performance...................................................................................................................................................11-13
Critical Activities...........................................................................................................................................11-15
Critical Activities Setup.................................................................................................................................11-16
System Alerts, Metrics, Logs.........................................................................................................................11-17
Database Initialization (init.ora) Parameters..................................................................................................11-19

iv
Identify Tables and Columns to Audit...........................................................................................................8-18

Create an Audit Group...................................................................................................................................8-19
Audit Tables Window....................................................................................................................................8-20
Identifying the Schema to be Audited ...........................................................................................................8-21
Enabling Audit Processing ............................................................................................................................8-22
Audit Shadow Tables.....................................................................................................................................8-23
Shadow Table Views .....................................................................................................................................8-24
Summary........................................................................................................................................................8-25
Diagnostics and Troubleshooting with Oracle Applications Manager .......................................................12-1

Oracle Applications Manager - Diagnostics and Troubleshooting ................................................................12-3
Objectives ......................................................................................................................................................12-4
Diagnostics and Troubleshooting in Oracle Applications Manager ..............................................................12-5
Applications Dashboard - Diagnostics ..........................................................................................................12-7
Troubleshooting Wizards...............................................................................................................................12-9
Concurrent Manager Recovery Wizard .........................................................................................................12-11
Service Infrastructure Wizard........................................................................................................................12-13
Generic Collection Service (GCS) and Forms Monitoring Wizard ...............................................................12-14
CP Signature..................................................................................................................................................12-15
Dashboard Collection Wizard........................................................................................................................12-17
Support Cart...................................................................................................................................................12-18
Summary........................................................................................................................................................12-20
Managing Concurrent Programs and Reports .............................................................................................13-1
Managing Concurrent Requests.....................................................................................................................13-3
Objectives ......................................................................................................................................................13-4
Concurrent Requests, Programs, and Managers ............................................................................................13-6
Business Needs for Concurrent Processing ...................................................................................................13-7
Business Needs for Standard Request Submission........................................................................................13-8
Definitions .....................................................................................................................................................13-9
Submit Request Flow.....................................................................................................................................13-11
Submit a New Request ..................................................................................................................................13-12
Using the Parameters Window ......................................................................................................................13-13
Defining a Submission Schedule ...................................................................................................................13-14
Defining Completion Options........................................................................................................................13-16
Request ID .....................................................................................................................................................13-17
Reprinting a Report .......................................................................................................................................13-18
Use the Requests Window to View and Change Requests ............................................................................13-19
How to Use the Requests Window ................................................................................................................13-20
Using the Requests Window..........................................................................................................................13-21
Viewer Options Window ...............................................................................................................................13-23
Canceling a Request ......................................................................................................................................13-24
Holding a Request .........................................................................................................................................13-25
Changing Request Options ............................................................................................................................13-26
Four Phases of a Concurrent Request ............................................................................................................13-27

v
Business Flows ..............................................................................................................................................11-20

Monitoring Oracle E-Business Suite Security ...............................................................................................11-22
Monitoring E-Business Suite Security Setup - Diagnostic Tests...................................................................11-24
Applications Dashboard - Security ................................................................................................................11-25
Database Status Details .................................................................................................................................11-26
Application Services......................................................................................................................................11-27
Monitoring Forms..........................................................................................................................................11-28
Forms Runaway Processes ............................................................................................................................11-29
Forms Sessions ..............................................................................................................................................11-31
Forms Runtime Processes..............................................................................................................................11-33
Host Management..........................................................................................................................................11-35
Host Management - Status.............................................................................................................................11-37
Host Management - Configuration ................................................................................................................11-38
Setting Up Oracle Applications Manager......................................................................................................11-39
Dashboard Configuration and Alerting Setup................................................................................................11-40
Setting Up Dashboard Configuration and Alerting .......................................................................................11-41
OracleMetaLink Credentials Setup................................................................................................................11-43
Knowledge Base Setup..................................................................................................................................11-44
Concurrent Requests Setup............................................................................................................................11-45
Signon Audit Setup........................................................................................................................................11-46
Summary........................................................................................................................................................11-47
Administering Concurrent Managers............................................................................................................14-1

Administering Concurrent Managers.............................................................................................................14-3
Objectives ......................................................................................................................................................14-4
Concurrent Requests, Programs, and Processes ............................................................................................14-5
Overview of Concurrent Processing ..............................................................................................................14-6
Generic Service Management (GSM)............................................................................................................14-7
Defining a Concurrent Manager ....................................................................................................................14-8
Defining Work Shifts.....................................................................................................................................14-10
Balancing Process Workload Over Time.......................................................................................................14-11
Work Shift Hierarchy ....................................................................................................................................14-12
Concurrent Managers Window: Program Libraries.......................................................................................14-13
Assigning Workshifts to a Manager ..............................................................................................................14-14
Specializing a Concurrent Manager...............................................................................................................14-15
Specializing a Concurrent Manager: Combined Rules ..................................................................................14-16
Specialization Rules ......................................................................................................................................14-17
Action Types .................................................................................................................................................14-18
Combining Multiple Actions Within Rules ...................................................................................................14-19
Concurrent Request Types.............................................................................................................................14-20
Using Request Types .....................................................................................................................................14-21
Conflicts Domains .........................................................................................................................................14-22
Processing Conflicts Domains.......................................................................................................................14-24
Control Functions of Concurrent Managers ..................................................................................................14-25
Internal Monitor and ICM .............................................................................................................................14-27
Defining a Transaction Manager ...................................................................................................................14-28
Viewing Log and Output Files ......................................................................................................................14-29
Managing Parallel Concurrent Processing.....................................................................................................14-30

vi
Pending Phase................................................................................................................................................13-28
Running Phase ...............................................................................................................................................13-29
Completed Phase ...........................................................................................................................................13-30
Inactive Phase................................................................................................................................................13-31
System Administrator Monitoring Privileges ................................................................................................13-32
Review Log Files...........................................................................................................................................13-33
Managing Log Files and Tables ....................................................................................................................13-34
Purge Request Results ...................................................................................................................................13-35
Grouping Concurrent Programs and Requests...............................................................................................13-36
Creating a Request Group..............................................................................................................................13-38
Using a Request Group with a Code..............................................................................................................13-39
Submitting Requests: Form Compared with Responsibility..........................................................................13-40
Implementing a Coded Request Group..........................................................................................................13-41
Customization Example.................................................................................................................................13-42
Creating the New Form Function ..................................................................................................................13-43
Passable Request Parameters.........................................................................................................................13-44
Adding the Function to the Menu..................................................................................................................13-45
Defining a Request Set ..................................................................................................................................13-46
Request Set Stages.........................................................................................................................................13-47
Stage Status ...................................................................................................................................................13-48
Linking of Stages...........................................................................................................................................13-50
Defining Request Sets Step 1: Enter Request Set Name ...............................................................................13-51
Defining Request Sets Step 2: Define a Stage ...............................................................................................13-53
Defining Request Sets Step 3: Enter Requests for Stage ...............................................................................13-54
Defining Request Sets Step 4: Enter Request Parameter...............................................................................13-55
Defining Request Sets Step 5: Link Stages ...................................................................................................13-56
Submitting a Request Set...............................................................................................................................13-57
User Request Set Privileges...........................................................................................................................13-58
System Administrator Request Set Privileges ...............................................................................................13-59
Summary........................................................................................................................................................13-60
Introduction to Oracle Workflow ..................................................................................................................15-1

Introduction to Oracle Workflow ..................................................................................................................15-3
Objectives ......................................................................................................................................................15-4
Enabling E-Business......................................................................................................................................15-5
Inter-Enterprise Business Processes ..............................................................................................................15-6
Traditional Workflow ....................................................................................................................................15-7
Workflow-Driven Business Processes...........................................................................................................15-8
Sample Workflow Process.............................................................................................................................15-10
Event-Based Workflow .................................................................................................................................15-11
Subscription-Based Processing......................................................................................................................15-12
System Integration with Oracle Workflow ....................................................................................................15-13
Business Process-Based Integration ..............................................................................................................15-14
Supported System Integration Types.............................................................................................................15-15
Designing Applications for Change...............................................................................................................15-16
Designing Applications for Integration .........................................................................................................15-19
Oracle Workflow in Oracle E-Business Suite ...............................................................................................15-21
Summary........................................................................................................................................................15-22
Oracle Workflow Components.......................................................................................................................16-1
Oracle Workflow Components ......................................................................................................................16-3
Objectives ......................................................................................................................................................16-4
Oracle Workflow Architecture ......................................................................................................................16-5
Oracle Workflow Components ......................................................................................................................16-9
Workflow Engine ..........................................................................................................................................16-10
Workflow Processes ......................................................................................................................................16-11
Supported Process Constructs........................................................................................................................16-13
Oracle Workflow Builder ..............................................................................................................................16-17
Business Event System Architecture .............................................................................................................16-18
Business Event System Components.............................................................................................................16-19
Advanced Queuing, an Enabling Technology ...............................................................................................16-20
Oracle Database Communication Alternatives..............................................................................................16-21
Accessing Oracle Workflow Web Pages .......................................................................................................16-23
Oracle Workflow Home Pages ......................................................................................................................16-24
Notification System .......................................................................................................................................16-25
Worklist Web Pages ......................................................................................................................................16-26
E-Mail Notifications ......................................................................................................................................16-27
Directory Services .........................................................................................................................................16-28
Status Monitor Web Pages.............................................................................................................................16-29
Workflow Definitions Loader........................................................................................................................16-30
Workflow XML Loader.................................................................................................................................16-31
Workflow Manager........................................................................................................................................16-32
Service Components ......................................................................................................................................16-33
Oracle Workflow Documentation..................................................................................................................16-34
Review Questions ..........................................................................................................................................16-36
Summary........................................................................................................................................................16-37
Setting Up Oracle Workflow ..........................................................................................................................17-1
Setting Up Oracle Workflow .........................................................................................................................17-3
Objectives ......................................................................................................................................................17-4
Required Setup Steps.....................................................................................................................................17-5
Step 1 Setting Global Workflow Preferences ................................................................................................17-6
Step 2 Setting Up an Oracle Workflow Directory Service ............................................................................17-9
Step 3 Running Background Engines ............................................................................................................17-13
Step 4 Configuring the Business Event System.............................................................................................17-16
Step 4 Event Message Communication .........................................................................................................17-17
Step 4 Setting Up Database Links and Queues..............................................................................................17-18

vii
Summary........................................................................................................................................................14-32
Overview of Flexfields .....................................................................................................................................18-1

Overview of Flexfields ..................................................................................................................................18-3
Objectives ......................................................................................................................................................18-4
Overview .......................................................................................................................................................18-5
Customizing Oracle Applications..................................................................................................................18-6
Flexfield Structures and Flexfield Segments .................................................................................................18-7
Segment Prompts and Value Descriptions.....................................................................................................18-8
Validating Input Using Value Sets ................................................................................................................18-9
Key and Descriptive Flexfields .....................................................................................................................18-10
Key Flexfields ...............................................................................................................................................18-11
Intelligent Keys .............................................................................................................................................18-12
Key Flexfield Example: Accounting Flexfield ..............................................................................................18-14
Oracle Applications Key Flexfields...............................................................................................................18-15
Descriptive Flexfields....................................................................................................................................18-16
Using Reference Fields..................................................................................................................................18-17
Using Different Contexts: Asset Category Flexfield .....................................................................................18-18
Oracle Applications Descriptive Flexfields (Partial) .....................................................................................18-19
Standard Request Submission (SRS) and Flexfields .....................................................................................18-20
Benefits of Flexfields.....................................................................................................................................18-21
Storing Flexfield Data Internally ...................................................................................................................18-22
Implementing a Flexfield Steps ....................................................................................................................18-23
Summary........................................................................................................................................................18-24
Using Value Sets...............................................................................................................................................19-1
Using Value Sets ...........................................................................................................................................19-3
Objectives ......................................................................................................................................................19-4
Overview .......................................................................................................................................................19-5
Validating Input Using Value Sets ................................................................................................................19-6
Planning a Value Set......................................................................................................................................19-7
Types of Value Sets.......................................................................................................................................19-8
Validation Type None ...................................................................................................................................19-10
Independent Value Sets .................................................................................................................................19-11
Dependent Value Sets....................................................................................................................................19-12
Table-Validated Value Sets ...........................................................................................................................19-13
Specialized Validation Types ........................................................................................................................19-14
Translatable Independent Value Sets.............................................................................................................19-15

viii
Step 4 Checking Database Parameters...........................................................................................................17-19

Step 4 Scheduling Agent Listeners................................................................................................................17-20
Step 4 Scheduling Propagation......................................................................................................................17-23
Step 4 Synchronizing License Statuses .........................................................................................................17-27
Step 4 Cleaning Up the WF_CONTROL Queue...........................................................................................17-28
Step 4 Tuning Performance ...........................................................................................................................17-29
Step 4 Specifying the BPEL Server...............................................................................................................17-31
Optional Setup Steps .....................................................................................................................................17-32
Optional Step 1 Partitioning Workflow Tables .............................................................................................17-34
Optional Step 2 Setting Up Additional Languages........................................................................................17-36
Optional Step 3 Implementing Notification Mailers .....................................................................................17-38
Optional Step 4 Customizing Message Templates ........................................................................................17-41
Optional Step 5 Adding Worklist Functions to User Responsibilities...........................................................17-44
Optional Step 6 Setting the Notification Reassign Mode ..............................................................................17-46
Optional Step 7 Setting Up Notification Handling Options ..........................................................................17-47
Optional Step 8 Setting Up for Electronic Signatures ...................................................................................17-49
Optional Step 9 Customizing the Workflow Web Page Logo .......................................................................17-51
Optional Step 10 Adding Custom Icons ........................................................................................................17-52
Version Compatibility ...................................................................................................................................17-53
Review Questions ..........................................................................................................................................17-54
Summary........................................................................................................................................................17-56
Defining Descriptive Flexfields .......................................................................................................................20-1

Defining Descriptive Flexfields.....................................................................................................................20-3
Objectives ......................................................................................................................................................20-4
Overview .......................................................................................................................................................20-5
Planning a Descriptive Flexfield ...................................................................................................................20-6
Using Descriptive Flexfields .........................................................................................................................20-8
Typical Descriptive Flexfield Information ....................................................................................................20-9
Some Oracle Applications Descriptive Flexfields.........................................................................................20-10
Identifying a Descriptive Flexfield ................................................................................................................20-11
Determining the Descriptive Flexfield Name ................................................................................................20-12
Determining Available Resources .................................................................................................................20-14
Planning Questions ........................................................................................................................................20-15
Identifying Your Information ........................................................................................................................20-16
Grouping Information By Usage ...................................................................................................................20-17
Isolate Common Information.........................................................................................................................20-18
Determine Different Contexts........................................................................................................................20-19
Descriptive Flexfield Components ................................................................................................................20-20
Global Segments............................................................................................................................................20-21
Context-Sensitive Segments ..........................................................................................................................20-22
Distinguishing Between Contexts..................................................................................................................20-23
Reference and Context Fields........................................................................................................................20-24
Using Reference Fields..................................................................................................................................20-25
Identifying Referenceable Columns ..............................................................................................................20-26
Using Context Fields .....................................................................................................................................20-27
Synchronizing the Context Field Value with the Reference Field Value ......................................................20-28
Planning Flexfields: Global Segments Only..................................................................................................20-30
Planning Flexfields: Context Segments Only ...............................................................................................20-31
Planning Flexfields: Global and Context Fields ............................................................................................20-32
Specifying the Flexfield Attributes................................................................................................................20-33

ix
Translatable Dependent Value Sets ...............................................................................................................19-16

Validation Types: Summary ..........................................................................................................................19-17
Planning Value Sets.......................................................................................................................................19-18
Value Set Attributes.......................................................................................................................................19-19
Planning Format Validation...........................................................................................................................19-20
Format Types and Options.............................................................................................................................19-21
Char and Number Format Editing .................................................................................................................19-22
Time, Standard Date, and Standard DateTime Format Editing .....................................................................19-23
Format Interaction .........................................................................................................................................19-24
Formatting Requirements for Translatable Value Sets .................................................................................19-25
Planning Validation Strategy.........................................................................................................................19-26
Planning Value Sets and Their Values ..........................................................................................................19-28
Planning Dependent Value Sets.....................................................................................................................19-29
Defining Value Sets.......................................................................................................................................19-30
Predefined Value Sets....................................................................................................................................19-31
Using Existing Value Sets .............................................................................................................................19-32
Value Set Usage by Key Flexfields ...............................................................................................................19-33
Value Set Usage by Descriptive Flexfields ...................................................................................................19-35
Defining a New Value Set .............................................................................................................................19-36
Defining a Dependent or Translatable Dependent Value Set ........................................................................19-37
Selecting a Value Set for Value Definition ...................................................................................................19-38
Defining Values for a Dependent or Translatable Dependent Value Set.......................................................19-39
Defining Values for a Value Set....................................................................................................................19-40
Modifying Value Definitions.........................................................................................................................19-41
Value Hierarchies ..........................................................................................................................................19-42
Defining Value Hierarchies and Qualifiers....................................................................................................19-44
Summary........................................................................................................................................................19-45
Defining Key Flexfields ...................................................................................................................................21-1

Defining Key Flexfields ................................................................................................................................21-3
Objectives ......................................................................................................................................................21-4
Overview .......................................................................................................................................................21-6
Intelligent Keys .............................................................................................................................................21-8
Key Flexfields' Dual Purpose ........................................................................................................................21-9
Oracle Applications Key Flexfields...............................................................................................................21-10
Implementing Key Flexfields ........................................................................................................................21-11
Key Flexfield Structures................................................................................................................................21-12
Code Combinations .......................................................................................................................................21-13
Storing Code Combinations...........................................................................................................................21-14
Key Flexfield Application Tables..................................................................................................................21-15
Key Flexfield Qualifiers ................................................................................................................................21-16
Types of Qualifiers ........................................................................................................................................21-17
Flexfield Qualifiers........................................................................................................................................21-18
Segment Qualifiers ........................................................................................................................................21-20
Other Key Flexfield Options .........................................................................................................................21-21
Allowing Dynamic Insertion .........................................................................................................................21-22
Cross-Validating Values................................................................................................................................21-23
Using Shorthand Aliases ...............................................................................................................................21-24
Securing Value Set Access ............................................................................................................................21-25
Designing the Key Flexfield Layout..............................................................................................................21-26
Designing Segments ......................................................................................................................................21-27
Specifying Default Values.............................................................................................................................21-28
Planning Decisions ........................................................................................................................................21-30
Planning Key Flexfield Values......................................................................................................................21-32
Definition Procedure......................................................................................................................................21-33
Accessing the Key Flexfield Definition.........................................................................................................21-35
Specifying Flexfield Behavior.......................................................................................................................21-36
Defining Segment Attributes .........................................................................................................................21-37
Defining Validation and Size Attributes........................................................................................................21-38
Defining Flexfield Qualifiers.........................................................................................................................21-39
Freezing and Compiling the Definition .........................................................................................................21-40
Defining Value Set Values ............................................................................................................................21-41
Defining Segment Qualifiers .........................................................................................................................21-42
Cross-Validating Values................................................................................................................................21-43
Cross-Validation Rule Syntax .......................................................................................................................21-44
Data Type Specifications and Cross-Validation Rules ..................................................................................21-45

x
Specifying the Context Field Information .....................................................................................................20-34

Specifying the Segment Attributes ................................................................................................................20-36
Storing Descriptive Flexfield Segments ........................................................................................................20-37
Descriptive Flexfield Application Tables ......................................................................................................20-38
Specifying the Segment Detail Attributes .....................................................................................................20-40
Specifying Default Values.............................................................................................................................20-43
Defining a Descriptive Flexfield ...................................................................................................................20-45
Locating the Flexfield Definition ..................................................................................................................20-47
Defining the Flexfield Header Attributes ......................................................................................................20-48
Defining Segment Attributes .........................................................................................................................20-49
Specifying Validation and Field Sizes...........................................................................................................20-50
Freezing and Compiling the Definition .........................................................................................................20-51
Defining Context Field Information ..............................................................................................................20-52
Defining Context-Sensitive Segments ...........................................................................................................20-54
Defining Values for a Value Set....................................................................................................................20-55
Summary........................................................................................................................................................20-56
Using Advanced Validation Capabilities .......................................................................................................22-1

Using Advanced Validation Capabilities.......................................................................................................22-3
Objectives ......................................................................................................................................................22-4
Overview .......................................................................................................................................................22-5
Advanced Validation Options........................................................................................................................22-6
Table-Validated Value Sets ...........................................................................................................................22-7
Defining a Table-Validated Value Set...........................................................................................................22-8
Restricting Values Retrieved from a Table....................................................................................................22-9
Limitations on Using SQL WHERE Clauses ................................................................................................22-10
Using Multiple Tables for Validation............................................................................................................22-11
Other Advanced Validation Options..............................................................................................................22-12
Using $PROFILES$ ......................................................................................................................................22-13
Using :block.field ..........................................................................................................................................22-14
Using $FLEX$...............................................................................................................................................22-15
Cascading Dependencies Using $FLEX$......................................................................................................22-16
Using Special Value Sets...............................................................................................................................22-17
Using Pair Value Sets ....................................................................................................................................22-18
Summary........................................................................................................................................................22-19
Appendix - Administering Folders.................................................................................................................23-1
Appendix - Administering Folders ................................................................................................................23-3
Objectives ......................................................................................................................................................23-4
Folders: Definition.........................................................................................................................................23-5
Administering Folders: Topics ......................................................................................................................23-6
Assigning a Default Folder to a Responsibility .............................................................................................23-7
Assigning a Default Folder to a User.............................................................................................................23-8
Assigning Ownership of a Folder ..................................................................................................................23-9
Deleting a Folder Definition..........................................................................................................................23-10
Summary........................................................................................................................................................23-11

xi
Preparing for Cross-Validation......................................................................................................................21-46

Defining Cross-Validation Rules...................................................................................................................21-47
Cross-Validation Reports ..............................................................................................................................21-48
Comparing Cross-Validation and Security Rules ..........................................................................................21-49
Using Shorthand Aliases ...............................................................................................................................21-50
Using Full and Partial Aliases .......................................................................................................................21-51
Typical Key Flexfields Using Aliases ...........................................................................................................21-52
Defining an Alias...........................................................................................................................................21-53
Defining an Alias Template...........................................................................................................................21-54
Recompiling the Flexfield Definition ............................................................................................................21-55
Flexfields: Shorthand Entry Profile Option ...................................................................................................21-56
Flexfields: Show Full Value Profile Option ..................................................................................................21-57
Modifying Existing Alias Definitions............................................................................................................21-58
Securing Value Set Access ............................................................................................................................21-59
Security and Value Sets.................................................................................................................................21-60
Constructing Security Rules ..........................................................................................................................21-61
Specifying Acceptable Values.......................................................................................................................21-62
Using Multiple Clauses .................................................................................................................................21-63
Rules with Overlapping Values .....................................................................................................................21-64
Rules Without Overlapping Values ...............................................................................................................21-65
Implementing Flexfield Security ...................................................................................................................21-66
Enabling Security for a Value Set .................................................................................................................21-67
Enabling Security for a Segment ...................................................................................................................21-68
Enabling Security for a Program Parameter ..................................................................................................21-70
Defining Security Rules.................................................................................................................................21-71
Assigning Security Rules...............................................................................................................................21-72
Defining Key Flexfields Summary ...............................................................................................................21-74
Appendix - Incorporating Custom Help Files ...............................................................................................25-1

Appendix - Incorporating Custom Help Files................................................................................................25-3
Objectives ......................................................................................................................................................25-4
Customizing Help ..........................................................................................................................................25-5
Oracle Applications Help System Utility ......................................................................................................25-6
Help System Utility Setup: Define Directory Paths.......................................................................................25-7
Downloading Help Files ................................................................................................................................25-8
Identify Help Files for Customization ...........................................................................................................25-9
Identify the Language and Product of the Files ............................................................................................25-10
Downloading Help Files for Editing..............................................................................................................25-11
Linking Help Files .........................................................................................................................................25-12
Special Syntax versus Conventional HTML..................................................................................................25-13
Cross-Application Links................................................................................................................................25-14
Related Topics Links .....................................................................................................................................25-15
Related Topics Links Syntax .........................................................................................................................25-16
Uploading Your New or Changed Help Files................................................................................................25-17
File Upload Steps...........................................................................................................................................25-18
Updating the Search Index.............................................................................................................................25-20
Creating Reports ............................................................................................................................................25-21
Running Reports ............................................................................................................................................25-22
Customizing Help Navigation Trees..............................................................................................................25-23
Help Builder Functions..................................................................................................................................25-24
The Help Builder ...........................................................................................................................................25-25
Opening a Tree for Editing ............................................................................................................................25-26
Adding New Help Files to a Tree ..................................................................................................................25-27
Adding New Nodes to a Tree ........................................................................................................................25-28
For Further Information.................................................................................................................................25-29
Summary........................................................................................................................................................25-30
Guided Demonstrations and Practices...........................................................................................................26-1
Guided Demonstrations and Practices ...........................................................................................................26-3
Practice - Users..........................................................................................................................................26-4
Solution - Users .........................................................................................................................................26-5
Practice - Data Groups...............................................................................................................................26-9
Solution Data Groups .............................................................................................................................26-11
Practice - Menus ........................................................................................................................................26-13
Solution - Menus .......................................................................................................................................26-16
Practice - Query-Only Forms.....................................................................................................................26-24
Solution - Query-Only Forms ....................................................................................................................26-25
Practice - Responsibilities..........................................................................................................................26-30
Solution - Responsibilities .........................................................................................................................26-32
Guided Demonstration - Data Security Policy Example............................................................................26-36
Guided Demonstration - Creating Role Categories ...................................................................................26-37
Practice - Creating a Role and Placing it in a Role Inheritance Hierarchy ................................................26-38

xii
Appendix - Incorporating a Custom Program..............................................................................................24-1

Appendix - Incorporating a Custom Program................................................................................................24-3
Objectives ......................................................................................................................................................24-4
Using Custom Programs in Oracle Applications ...........................................................................................24-5
Assumptions for Incorporating a New Program ...........................................................................................24-6
Components of a Concurrent Program ..........................................................................................................24-7
Adding a Custom Program to Oracle Applications ......................................................................................24-8
Identifying the Executable.............................................................................................................................24-9
Creating the Concurrent Program ..................................................................................................................24-11
Concurrent Program Parameters Window .....................................................................................................24-13
Associating a Program with a Request Group ...............................................................................................24-15
Submitting the Concurrent Program ..............................................................................................................24-16
Summary........................................................................................................................................................24-17

xiii
Solution Creating a Role and Placing it in a Role Inheritance Hierarchy...............................................26-40

Practice - Assigning Permission Sets to the Role ......................................................................................26-42
Solution Assigning Permission Sets to the Role.....................................................................................26-44
Guided Demonstration - Setting Up Delegated Administration ................................................................26-45
Practice - Testing Delegated Administration.............................................................................................26-47
Solution Testing Delegated Administration............................................................................................26-49
Practice - Creating a Registration Process for the Role .............................................................................26-51
Solution Creating a Registration Process for the Role............................................................................26-53
Practice - Testing the Registration Process for the Role............................................................................26-54
Solution Testing the Registration Process for the Role ..........................................................................26-56
Practice - Profile Options...........................................................................................................................26-58
Solution - Profile Options..........................................................................................................................26-59
Practice - Auditing Resources....................................................................................................................26-61
Solution - Auditing Resources...................................................................................................................26-62
Guided Demonstration - Support Cart .......................................................................................................26-64
Practice - Scheduling Requests..................................................................................................................26-65
Solution - Scheduling Requests .................................................................................................................26-66
Practice - Request Groups .........................................................................................................................26-72
Solution - Request Groups.........................................................................................................................26-74
Practice - Coded Request Groups ..............................................................................................................26-76
Solution - Coded Request Groups .............................................................................................................26-78
Practice - Request Sets Using Wizard .......................................................................................................26-84
Solution - Request Sets Using Wizard.......................................................................................................26-85
Practice - Administering Concurrent Managers.........................................................................................26-87
Solution - Administering Concurrent Managers........................................................................................26-90
Guided Demonstration - Loading and Running a Workflow Process........................................................26-97
Practice - Define a Descriptive Flexfield...................................................................................................26-99
Solution Define a Descriptive Flexfield .................................................................................................26-104
Practice - Define a Descriptive Flexfield with None Validation ...............................................................26-109
Solution Define a Descriptive Flexfield with None Validation ..............................................................26-111
Practice - Define a Descriptive Flexfield with Context-Sensitive Segment ..............................................26-115
Solution Define a Descriptive Flexfield with a Context-Sensitive Segment ..........................................26-118
Practice - Define a Descriptive Flexfield with a Dependent Segment.......................................................26-124
Solution Define a Descriptive Flexfield with a Dependent Segment......................................................26-127
Practice - Define a Key Flexfield ..............................................................................................................26-131
Solution - Define a Key Flexfield..............................................................................................................26-135
Practice - Security Rules............................................................................................................................26-144
Solution Security Rules ..........................................................................................................................26-146
Practice - Cross-Validation Rules..............................................................................................................26-148
Solution - Cross-Validations......................................................................................................................26-150
Practice - Shorthand Aliases ......................................................................................................................26-152
Solution Shorthand Aliases.....................................................................................................................26-153
Practice - Table Validation ........................................................................................................................26-154
Solution Table Validation.......................................................................................................................26-155
Practice - Cascading Dependencies with $FLEX$ ....................................................................................26-157
Solution Cascading Dependencies with $FLEX$...................................................................................26-161
Guided Demonstration - Folders................................................................................................................26-166
Practice - Incorporating Custom Programs................................................................................................26-173
Solution - Incorporating Custom Programs ...............................................................................................26-174

Preface
Profile
Before You Begin This Course
Thorough knowledge of R12 Oracle Applications Navigation
Prerequisites
There are no prerequisites for this course.
How This Course Is Organized

This is an instructor-led course featuring lecture and hands-on exercises. Online demonstrations
and written practice sessions reinforce the concepts and skills introduced.

xv
Related Publications
Oracle Publications
Part Number
Oracle Applications System Administrators Guide Security
B31451
Oracle Applications System Administrators Guide Configuration
B31453
Oracle Applications System Administrators Guide Maintenance
B31454
Oracle Workflow Administrators Guide
B31431
Additional Publications
System release bulletins
Installation and users guides
Read-me files
International Oracle Users Group (IOUG) articles
Oracle Magazine

xvi
Title
Typographic Conventions
Typographic Conventions in Text
Caps and
lowercase
Courier new,
case sensitive
(default is
lowercase)
Initial cap
Element
Glossary term (if
there is a glossary)
Buttons,
check boxes,
triggers,
windows
Code output,
directory names,
filenames,
passwords,
pathnames,
URLs,
user input,
usernames
Arrow
Brackets
Commas
Graphics labels
(unless the term is a
proper noun)
Emphasized words
and phrases,
titles of books and
courses,
variables
Interface elements
with long names
that have only
initial caps;
lesson and chapter
titles in crossreferences
SQL column
names, commands,
functions, schemas,
table names
Menu paths
Key names
Key sequences
Plus signs
Key combinations
Italic
Quotation
marks
Uppercase
Example
The algorithm inserts the new key.
Click the Executable button.
Select the Cant Delete Card check box.
Assign a When-Validate-Item trigger to the ORD block.
Open the Master Schedule window.
Code output: debug.set (I, 300);
Directory: bin (DOS), $FMHOME (UNIX)
Filename: Locate the init.ora file.
Password: User tiger as your password.
Pathname: Open c:\my_docs\projects
URL: Go to http://www.oracle.com
User input: Enter 300
Username: Log on as scott
Customer address (but Oracle Payables)
Do not save changes to the database.

For further information, see Oracle7 Server SQL Language
Reference Manual.
Enter user_id@us.oracle.com, where user_id is the
name of the user.
Select Include a reusable module component and click Finish.
This subject is covered in Unit II, Lesson 3, Working with
Objects.
Use the SELECT command to view information stored in the

LAST_NAME
column of the EMP table.
Select File > Save.
Press [Enter].
Press and release keys one at a time:
[Alternate], [F], [D]
Press and hold these keys simultaneously: [Ctrl]+[Alt]+[Del]

xvii
Convention
Bold italic
Typographic Conventions in Code

Element
Oracle Forms
triggers
Column names,
table names
Example
When-Validate-Item
Passwords
DROP USER scott

IDENTIFIED BY tiger;
OG_ACTIVATE_LAYER
(OG_GET_LAYER (prod_pie_layer))
SELECT last_name
FROM s_emp;
PL/SQL objects
Lowercase
italic
Uppercase
CREATE ROLE role
Syntax variables
SQL commands and SELECT userid

FROM emp;
functions
Typographic Conventions in Oracle Application Navigation Paths

This course uses simplified navigation paths, such as the following example, to direct you
through Oracle Applications.
(N) Invoice > Entry > Invoice Batches Summary (M) Query > Find (B) Approve
This simplified path translates to the following:
1.
(N) From the Navigator window, select Invoice then Entry then Invoice Batches
Summary.
2.
(M) From the menu, select Query then Find.
3.
(B) Click the Approve button.
Notations:
(N) = Navigator
(M) = Menu
(T) = Tab
(B) = Button
(I) = Icon
(H) = Hyperlink
(ST) = Sub Tab

xviii
Convention
Caps and
lowercase
Lowercase
Typographical Conventions in Oracle Application Help System Paths

This course uses a navigation path convention to represent actions you perform to find
pertinent information in the Oracle Applications Help System.
The following help navigation path, for example
(Help) General Ledger > Journals > Enter Journals
1.
In the navigation frame of the help system window, expand the General Ledger entry.
2.
Under the General Ledger entry, expand Journals.
3.
Under Journals, select Enter Journals.
4.
Review the Enter Journals topic that appears in the document frame of the help system
window.

xix
represents the following sequence of actions:


xx
Chapter 1
Introduction
Chapter
1 - Page 1 ONLY. COPYING eKIT MATERIALS FROM THIS
THESE eKIT MATERIALS ARE FOR YOUR USE IN THIS
CLASSROOM
Introduction

Introduction
Chapter
CLASSROOM
Introduction
Introduction
Chapter
CLASSROOM
Course Objectives
Introduction
Chapter
CLASSROOM
Overview
Introduction
Chapter
CLASSROOM
Oracle Applications System Administration
Introduction
Chapter
CLASSROOM
Oracle Workflow Component
Introduction
Chapter
CLASSROOM
Oracle Applications Flexfields Component
Introduction
Chapter
CLASSROOM
Additional Material
Introduction
Chapter
CLASSROOM

Introduction
Chapter
CLASSROOM
Chapter 2
Introduction to Oracle Applications Security

Chapter
CLASSROOM
Introduction to Oracle
Applications Security


Chapter
CLASSROOM

Chapter
CLASSROOM
Objectives

Chapter
CLASSROOM
Layers of Access Control

Access control with User Management is 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 they wish to build upon the existing Function and
Data Security models.
There are six layers of access control. The Core Security layers include:
Function Security
Data Security
The next four layers are part of Oracle User Management:
Role Based Access Control
Delegated Administration
Registration Processes
Self Service and Approvals

Chapter
CLASSROOM
Successive Layers of Access Control
Increasing Flexibility and Scalability

In general, Access Control with Oracle User Management begins with basic system
administration tasks and then progresses to more distributed, local modes of administration,
and ultimately enables users to perform some basic, predefined registration tasks on their own.
Details of the various levels of access control and the increasing level of flexibility and
automation are provided later in the course, however the following general guidelines may be
considered for the time being:
System Administrator
Oracles Function Security and Data Security mechanisms constitute the base layers, and
contain the traditional system administrative capabilities. Organizations can optionally add
more layers to the system depending on the degree of flexibility they require.
By themselves, Function Security and Data Security limit the scope of Oracle User
Management to basic system administration by granting access to specific menus and to the
data that can be accessed from within those menus.
Local Administrators

Chapter
CLASSROOM
When Role Based Access Control and Delegated Administration are added to the Data Security
and Function Security layers system administration tasks can be distributed to local
administrators who manage a subset of the organizations users.
End Users
Registration Processes and Self Service and Approvals further distribute system administration
by automating some registration tasks.

Chapter
CLASSROOM
Function Security
The base layer of access control within Oracle Applications is Function Security. Function
Security restricts user access to the individual menus and menu options within the system. It
can also be used to control access to some specific widget (often, graphical in nature) within a
page. Each of these various elements is represented in the system as a function, which is also
known as a permission. Using the Order Entry page as an example, Function Security could
control whether you have the ability to create a new order, or even access the page.

Chapter
CLASSROOM
Function Security
Data Security
The second layer represents Data Security. Working in conjunction with Function Security,
Data Security provides additional access control on the data a user can see and what actions a
user can perform on that data, within Oracle Applications. Note that Data Security is not used
in all Oracle Applications products. Products that do use data security include Oracle Projects,
Quality, and Cash Management.
Data Security Policies restrict the actions or operations that can be performed on a specific
business object (for example, inventory items). Data Security Policies can reflect access to:
All Instances All instances of an object represents all rows in the database object. For
example, assume that we have an object inventory item in the database. Creating a data
security policy for all instances of our object would result in providing access to every
single inventory item we have catalogued in the database.
An Instance Set An instance set is a related set of instances of an object. This
corresponds to a set of rows for the database object. Using our object example, an
instance set could be constructed to include all inventory items with a shelf life of 7 days.
A Specific Instance A specific instance generally corresponds to a single row in the
database. A specific instance is generally identified by a primary key value for the object.

Chapter
CLASSROOM
Data Security
Using our example, we could enter a unique serial number for the inventory item. This
would return one and only one inventory item from the database.

Chapter
CLASSROOM
Oracle User Management Layers of Access Control

The next four layers of access control are used in Oracle User Management, an optional
component in the implementation of Oracle Applications.

Chapter
CLASSROOM
Oracle User Management Layers of Access Control
Role Based Access Control (RBAC)

A role can be configured to consolidate the responsibilities, permissions, function security and
data security polices 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 based on the roles assigned to the user. When making a mass update in a
production system an organization simply changes the permissions or role inheritance
hierarchy defined for a role. The users assigned that role subsequently inherit the new set of
permissions.
Role Categories
Administrators can create role categories to bundle roles and responsibilities to simplify the
process of searching for roles and responsibilities. For example all sales and marketing related
roles could be included in the Sales & Marketing category.
Role Inheritance Hierarchies
Roles can be included in role inheritance hierarchies that can contain multiple sub-roles and
superior roles. With role inheritance hierarchies a superior role inherits all of the properties of
its sub-role and any of its sub-roles.

Chapter
CLASSROOM
Example
Organizations can define roles that closely mirror their business situation. For example, an
organization can create an "Employee" role and 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.

Chapter
CLASSROOM
With delegated administration, instead of exclusively relying on a centralized administrator to
manage all of its users, an organization can create local administrators with sufficient
privileges to manage a specific subset of the organization's users and roles. This provides
organizations with a tighter, more granular level of security and the ability to easily scale their
administrative capabilities.
Administration Privileges
Administration Privileges determine the users, roles and organization information 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

Chapter
CLASSROOM

Chapter
CLASSROOM
password) for another set. Local administrators cannot query users for which they do not have
administration privileges.
Role Administration Privileges
Role Administration Privileges define the roles local administrators can directly assign to and
revoke from the set of users they manage.
Organization Administration Privileges
Organization Administration Privileges define the organizations a local administrator can view
in the system. This privilege enables an administrator to search for people based on their
organization, if the local administrator has additionally been granted access to view the people
in that organization (User Administration Privileges). Depending on the user administration
privileges, an administrator may have the ability to register new people for that organization.
Example
Organizations can internally designate administrators at division or even department levels,
and then delegate administration of external users to people within those (external)
organizations. These delegation policies are defined as data security policies. The set of data
policies defined as part of delegated administration are known as Administration Privileges.
Oracle User Management contains the following registration processes.
Self-Service Account Requests
Commonly referred to as Self Service Registration, self-service account requests provide a
method for persons to request a new user account. Consider the case where customers may
need to register before they can purchase an item from an online store. Once the customer has
completed the registration process, the customer obtains both a user account and the necessary
role(s) for accessing some portion of the website in which they registered.
Requests for Additional Access
Users can request additional access through the Oracle User Management Access Request Tool
(ART) available in the global preferences menu. Requests for Additional Access uses the same
Oracle User Management infrastructure and processing logic as Self Service Account
Requests.
Account Creation By Administrators
Administrators can benefit from existing registration processes designed to streamline the
process of creating and maintaining user access. Registration Processes of this type are geared
toward administrators, especially delegated administrators, to ensure consistent application of

Chapter
CLASSROOM
the client's user security policies. Each account creation registration process can be made
available to select local administrators. Local administrators can perform these tasks for users
within their own organizations.

Chapter
CLASSROOM

Once registration processes have been configured as required, individuals can subsequently
perform self-service registration tasks such as obtaining new user accounts or requesting
additional access to the system. In addition, organizations can use the Oracle Approvals
Management engine, to create customized approval routing for these requests.
Example
An organization may enable users to request a particularly sensitive role, however before the
user is granted the role, the organization can specify that two approvers, a manager and a vice
president, must first provide their approval.

Chapter
CLASSROOM
Summary

Chapter
CLASSROOM


Chapter
CLASSROOM
Chapter 3
Function Security
Chapter
CLASSROOM
Function Security

Function Security
Chapter
CLASSROOM
Function Security
Function Security
Chapter
CLASSROOM
Lesson Aim
Function Security restricts user access to individual menus of functions, such as forms, HTML
pages, or widgets (such as buttons in a form) within an application. Function Security allows
you to define a user and assign the user one or more responsibilities, where each responsibility
has a menu associated with it. Function Security by itself restricts access to various functions,
but it does not restrict access to the data a user can see or what actions a user can perform on
that data. This lesson discusses defining users, responsibilities, and menus.
Function Security
Chapter
CLASSROOM
Objectives
Overview of Function Security

In Oracle Applications, the system administrator manages security on a number of levels.
Oracle User Accounts
Oracle User accounts (also known as Oracle IDs) provide access to specific tables in the Oracle
database. These are typically set up by the Oracle database administrators.
Applications
An application is a collection of functions, forms, programs, and reports.
Functions
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. A function can be
assigned to a responsibility through a menu, or excluded from a responsibility via a menu
exclusion. An example of a function is an Oracle Form or an HTML page.
Reports
Reports can be grouped together into request groups, which are in turn assigned to
responsibilities.
Responsibility
Function Security
Chapter
CLASSROOM
Overview of Function Security
Function Security
Chapter
CLASSROOM
A responsibility is a collection of authorizations that allow access to:

A specific application or applications.
A set of books.
A restricted list of windows, functions, and reports. These may be associated to the
responsibility through menus.
Each user has one or more responsibilities, and several users can share the same responsibility.
A system administrator can assign users any of the standard responsibilities provided with
Oracle Applications or create new custom responsibilities as needed.
Users
A user is defined as a human being. Although the concept of a user can be extended to include
machines, networks, or intelligent autonomous agents, the definition is limited to a person in
this document.
You authorize a user to sign on to Oracle Applications by defining an application user. You
then assign one or more responsibilities to the new user.
Defining a New User

(N) Security > User > Define
Note: All Navigation paths, unless otherwise noted, are from the System Administrator
Responsibility.
Although defining user accounts may be the last task you complete in setting up function
security for your installation, we will cover this task first so that you can complete the
following sections by logging into Oracle Applications with your own user account.
Define an authorized user of Oracle Applications by specifying a username and password.
Grant application privileges by assigning one or more responsibilities to the user. The user will
be able to access functions and reports via the assigned responsibilities. Responsibilities will be
covered later in this chapter.
Note that in previous releases of Oracle Applications, user passwords were treated as case
insensitive. Now, Oracle Applications user passwords can optionally be treated as case
sensitive. Case-sensitivity is controlled by the site-level profile option Signon Password Case.
For a complete explanation of the fields on the Users Form see:
(Help) Applied Technology > Oracle Applications System Administration > Security >
Overview of Oracle Applications Security > Users Window
Function Security
Chapter
CLASSROOM
Defining a New Application User
Custom Applications
An application is composed of components such as forms, menus, and concurrent programs.
An application serves as a unique context for these components. The next three slides discuss
necessary steps in implementing security for a custom application.
Function Security
Chapter
CLASSROOM
Custom Applications
Defining an Application
(N) Application > Register
You can protect custom functions, forms, reports, and programs from being lost during
upgrades by registering them under a custom application.
In the Applications window you will supply the following information:
Application Enter a user-friendly name that will appear in lists seen by the user.
Short Name Oracle Applications uses this short name to identify forms, menus,
concurrent programs, and other components of your application.
Basepath Enter the base path where the forms, reports, and program files are located.
Make sure your base path is unique to prevent other applications from writing to the same
directory.
For a complete explanation of the fields in this form see:
(Help) Applied Technology > Oracle Applications System Administration > Configuration >
Applications DBA > Applications Window
Function Security
Chapter
CLASSROOM
Defining an Application
Registering an Oracle ID
(N) Security > ORACLE > Register
You need to register an Oracle ID if you create a custom application using Oracle Application
Object Library.
Note that:
Only database administrators can create Oracle accounts.
Only create a new Oracle ID for a custom extension to Oracle Applications.
The install group designates which data group the application is associated with. For
applications that span all data groups, the install group is 0. Install groups numbered 1 or
greater are associated with one specific data group. Your database administrator can
supply the correct install group number.
Function Security
Chapter
CLASSROOM
Registering an Oracle ID
What Is a Data Group?

A data group is a collection of pairings of an application with an Oracle ID. Data groups
automatically support concurrent processing and cross-application reporting. They guarantee
that an application connects to a unique application database account.
Note: The installation process automatically defines data groups for Oracle Applications. For
custom applications, you should use the the standard data groups as well. Information on data
groups is given for legacy purposes.
Application-Oracle ID Pairs
An application can be listed only once in a data group.
An Oracle ID can be paired with more than one application.
A custom application registered with Oracle Applications can be included in a data group.
Data Groups and Application Object Library
Application Object Library owns the database tables referred to during concurrent processing
and the standard submission of reports by any Oracle Application. Therefore all applications
need access to the Application Object Library tables. When you are defining a data group, the
Function Security
Chapter
CLASSROOM
Data Groups
Function Security
Chapter
CLASSROOM
application Application Object Library is automatically included. The Application Object

Librarys Oracle ID cannot be updated or deleted.
Relating Data Groups to Forms and Programs
You can control the relationship among applications, forms, and concurrent programs by
defining a data group.
Applications, Forms, and Programs
A window connects to the application database account designated by the responsibility
associated with the application.
A data group determines the pairing of an application with a unique application database
account or Oracle ID.
A program connects to the application database account associated with the application
that owns the program.
Application-Oracle ID Pairs
An Oracle ID is a username and password that allows access to application tables in an
Oracle database.
A data group lists the Oracle ID assigned to each Oracle application.
A custom application registered with Oracle Applications can be included in a data group
and paired with an Oracle ID.
Securing Functions
You can manage security by controlling access to individual functions through menu
definitions.
About Functions
A function is a set of code in Oracle Applications that is executed only if the name of the
function is present in a list maintained within a responsibility.
There are two types of functions: a form function and a nonform function or subfunction.
A subfunction represents a securable subset of a forms functionality.
Adding Functions to or Removing Functions from a Responsibility
Maintain menu structures while eliminating specific functionality.
Exclude individual functions from a responsibility.
Adding or Removing Menus of Functions
Use menus to group functions together.
Exclude groups of functions by excluding a menu from a responsibility.
Function Security
Chapter
CLASSROOM
Securing Functions
Menus Link Functions to Responsibilities

Use the Menus form to define menus pointing to functions that you want to make available to a
new responsibility.
Make New Responsibilities, Not New Menus
If possible, apply exclusion rules to existing menus to customize a responsibility rather than
constructing an entirely new menu structure.
Determine the Application Functionality Required
Different jobs require access to different functions.
Identify predefined menus, forms, and form subfunctions to use as entries when defining a
new menu.
Plan Your Menu Structure
Start with a blank Menus form (blank screen). Menus cannot be copied. A menu saved
under a different name overwrites the original menu (there is no Save As feature).
Start with the lowest-level menus. A menu must be defined before it can be selected as an
entry on another menu.
Assign menus and functions to higher-level menus.
Function Security
Chapter
CLASSROOM
Defining a Menu
Assign the menu structure to the new responsibility by using the responsibilities form.
Document your menu structure by printing the Function Security Menu Report.
Function Security
Chapter
CLASSROOM
Designing a New Menu Structure

Before designing a new menu structure, identify any possible existing menu structures that can
be modified or modeled from, and document custom menus by using reports in the Function
Security Report Set.
Function Security Menu Report
Lists the full menu name of the responsibility
Indicates any excluded menu items, with the rules that exclude them
Function Security Navigator Report
Lists the menu as it appears in the Navigator for the responsibility specified
Does not include items excluded by function security rules
Function Security Function Report
Lists the functions accessible by the responsibility specified
Does not include items excluded by function security rules
Function Security
Chapter
CLASSROOM
Identifying Existing Menu Structures
Menu Guidelines
Function Security
Chapter
CLASSROOM
Creating a Menu
Use the Menus window to create a menu:
(N) Application > Menu
After you save your changes in this form, the Compile Security concurrent program is
automatically submitted to compile the menu data. Compiling your menu data allows for the
system to determine more quickly, during a users session, whether a function is available to a
particular responsibility or menu.
New Menus form fields:
Menu Type used to specify the purpose of the menu. The possible values are:
- Standard for menus that would be used in the Navigator form
- Tab for menus used in Self-Service applications
- Security for menus used to aggregate functions for data security or specific function
security purposes, but would not be used in the Navigator form.
Grant check box checking this box indicates that this function is automatically enabled
for the user.
For a complete explanation of the fields on this form see:
Function Security
Chapter
CLASSROOM
Creating a Menu
(Help) Applied Technology > Oracle Applications System Administration > Security >
Function Security > Menus Window
Note: If a menu entry has both a submenu and a function defined, then the behavior depends
on whether or not the function is executable. If it is executable, then the submenu is treated as
content to be rendered by the function. The submenu will not appear on the navigation tree, but
will be available in function security tests (FND_FUNCTION.TEST calls). If the function is
not executable, then it is treated as a tag for enforcing exclusion rules, and the submenu is
displayed on the navigation tree.
A function is considered executable if it can be executed directly from the current running user
interface.
Function Security
Chapter
CLASSROOM
Modifying a Menu
You can modify existing custom menus to suit specific job functions.
Overwrite a User Menu Name
When you change a menus user menu name, the menu entries are not affected. The menus
definition still exists, but under a new name. Other menus that call the menu by its old user
menu name now call the same menu by its new (revised) user menu name.
The old user menu name is no longer valid. When you are defining menus, or if you are
selecting main menus when defining a responsibility, the previously named menu is no longer
displayed in any list of values.
Modify a Menu Entry
When you are modifying a previously defined menu, all other menus that call that menu
display the menus modifications. For example, if you modify XXX_GL_USER by adding
another prompt that calls a form, all menus that call GL_SUPERUSER4.0 display the
additional prompt when XXX_GL_USER is displayed.
Note: Modifying shipped menu definitions is not supported. The customized definitions may
be overwritten during an upgrade process.
Function Security
Chapter
CLASSROOM
Modifying an Existing Menu Definition
Navigator Menu Displays

The Navigator displays only the menu items needed for navigation. Because you cannot choose
subfunctions from a menu, they are not displayed. Submenus consisting only of subfunctions
are also not displayed.
Function Security
Chapter
CLASSROOM
Navigator Menus
The Menu Viewer

(N) Application > Menu > (B) View Tree...
To view the menu tree, click on the plus (+) sign next to the menu name. You will see a
hierarchical tree with a number of nodes. Each node represents a function or submenu of
your main menu.
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.
There are three styles for viewing your menu tree. You can select the style from the View
menu or by clicking the appropriate toolbar icon.
Vertical Menu entries are displayed vertically, similar to how they appear in the
Navigator window when you log on to Oracle Applications.
Org-Chart Menu entries are displayed horizontally as in an organizational chart.
Interleaved Menu entries are displayed horizontally and vertically.
Function Security
Chapter
CLASSROOM
The Menu Viewer
Viewing Node Properties in the Menu Viewer
Function Security
Chapter
CLASSROOM
Procedure for incorporating a custom form function

Use the following procedure to incorporate a custom form function.
1. The application developer (using the Application Developer responsibility) registers the
form in the Forms window.
2. The application developer or system administrator creates a function that accesses the
new form in the Form Functions window.
3. The application developer or system administrator adds the form function to a menu in
the Menus window.
Function Security
Chapter
CLASSROOM
Adding a Custom Form Function
Creating a New Responsibility

Generally you relate new application users to existing predefined responsibilities. However,
you can customize an existing responsibility or create new responsibilities to accommodate the
needs of different users or different categories of users. When creating a new responsibility, it
is generally easier to modify an existing responsibility in one of two ways:
Extend Privileges a Responsibility Owns
When users require additional reporting and summary information, you can:
Use request groups to add additional program or report privileges to a responsibility
Use menus to add windows and tasks to a responsibility
Restrict Privileges a Responsibility Owns
Sometimes it is easier to remove authorizations from an existing responsibility. To do this
you can:
Use exclusions against a responsibility to limit menu and function access privileges to
those required for job duties
Use request groups to limit program or report privileges for a responsibility that
requires only data entry privileges
Function Security
Chapter
CLASSROOM
Using Responsibilities
After you have defined a new responsibility, you can associate it with an application user.
Function Security
Chapter
CLASSROOM
Components of a Responsibility
A responsibility has two required components and two optional components.
Required Components
Data group: specifies the Oracle Application database accounts to which a responsibilitys
forms and concurrent programs connect.
Menu: specifies the forms that a responsibility can display and the functions it can access.
Optional Components
Request security group: lists the concurrent programs that a responsibility can run. When a
request group is assigned to a responsibility, it is referred to as a request security group.
Exclusions: modify a responsibilitys access to the forms and functions specified by a
menu.
Function Security
Chapter
CLASSROOM
Responsibility Components
Defining a New Responsibility

Assemble the components of application privileges to create a responsibility.
Define the responsibility by assembling a menu, report security group, and data group and
defining any function security (any menu or function exclusions).
Function Security
Chapter
CLASSROOM
Responsibility Creation Process

There are five forms involved in the responsibility creation process. These are available under
the System Administrator responsibility. This slide displays the navigation paths for these
functions.
Function Security
Chapter
CLASSROOM
Responsibility Creation Process
Defining a Responsibility
(N) Security > Responsibility > Define
A responsibility determines the type of applications a user accesses, which application
functions a user can use, which reports and concurrent programs the user can run, and which
data those reports and concurrent programs can access. Most responsibilities are available
from Oracle Applications (the Forms navigator or the HTML-based E-Business Suite Home
page), others may be accessible from Oracle Self-Service Web Applications or Oracle Mobile
Applications.
Function Security
Chapter
CLASSROOM
Exclusion of Functions and Menus

Use exclusion rules to customize a responsibility. You can exclude functions at any level.
When you exclude a menu item from a responsibility, all menus and functions that are
nested in that menu are also excluded.
When you exclude a function from a responsibility, all occurrences of that function
throughout the menu structure of a responsibility are excluded.
Function Security
Chapter
CLASSROOM
Excluding Functions and Menus
Lesson Summary
Function Security provides you with the ability to control Oracle Applications Security. The
system administrator specifies which users have access to which functions. User accounts
provide the user access to an application. Responsibilities control that users access to various
functions of the application. Online access is controlled through the use of menus and menu
exclusions. Report and concurrent program access is controlled through the use of request
groups.
Function Security
Chapter
CLASSROOM
Summary
Chapter 4
Introduction to Data Security

Chapter
CLASSROOM


Chapter
CLASSROOM

Chapter
CLASSROOM
Data Security
In this section, references to specific applications are used as examples only. Data Security is
not implemented in all Oracle Applications products. Some applications may require
organizations to create multiple responsibilities to operate with their existing security models.
For more information, please consult the application-specific documentation.
This section is meant to introduce data security and its concepts only. Custom implementation
of data security or modification of shipped data security policies is not covered and is beyond
the scope of this course. Extreme care should be taken if any customization or modification is
done with data security implementations.

Chapter
CLASSROOM
Objectives
Introduction
Working in conjunction with Function Security, Data Security provides additional access
control on the data a user can see and what actions a user can perform on that data. Using Data
Security, for example, you could control access to the set of orders that an order administrator
can update within the Order Management application.
Data Security Policies restrict the actions or operations that can be performed on a specific
business object (for example, inventory items). Data Security Policies can reflect access to:
All Instances All instances of an object represents all rows in the database table or view.
For example, assume that we have an object inventory item in the database. Creating a
data security policy for all instances of our object would result in providing access to
every single inventory item we have catalogued in the database.
An Instance Set An instance set is a related set of instances of an object. This
corresponds to a set of rows in the database. Using our object example, an instance set
could be constructed to include all inventory items with a shelf life of 7 days.
A Specific Instance A specific instance generally corresponds to a single row in the
database. A specific instance is generally identified by a primary key value for the object.

Chapter
CLASSROOM
Using our example, we could enter a unique serial number for the inventory item. This
would return one and only one inventory item from the database.

Chapter
CLASSROOM
Objects
(N) Functional Developer responsibility > Objects
An object is a system entity on which an operation can be performed. In Oracle Applications,
an object typically maps to records in relational tables/views, Forms/HTML pages, and UI
widgets. Examples in Oracle Applications include: a person, an machine, and a file.
Examples of operations include: Create, Update, Escalate, Approve, and Reject. In Oracle
Applications, operations are implied by a permission definition. Permission has been defined
as an operation on a object; for example, Invoke Service Request Form, Update Order,
Approve Expense Report, and Query Customers.
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, and is identified by
a set of one or more primary key values as defined by the object.
Related object instances can be grouped together into an object instance set.

Chapter
CLASSROOM
Data Security Components - Objects
Grants
(N) Functional Administrator Responsibility > Grants
Grants are used to provide specified users access to specific objects or functions.
Grants that deal with business objects are called Data Security Policies.
Grants can also be used to control access to an application's functionality. For example, you
could use a grant to secure an aspect of a menu, page, or other widget within the application.
For example, you want to provide access to a set of administrative menus to a select group of
users.
The grantee defines who is being granted access. The grantee can be one of three types:
A group of users
A specific user for example, Joe Smith
All users (global) all users of the system, except the Guest account

Chapter
CLASSROOM
Grants
Permissions
The Role Based Access Control (RBAC) Model defines permission as "an approval to perform
an operation on one or more RBAC-protected objects." This definition maps to what has been
referred to as functions earlier. Permissions can be grouped into permission sets.
Permission sets can be granted to users or roles independently of menus or responsibilities.
Permission assignments, or Grants, reflect the access granted to users through roles.
Permissions are discussed more in the User Management lessons.

Chapter
CLASSROOM
Permissions and Permission Sets
Data Security Policies

Using Data Security, access to a specific object can be specified using a data security policy.
A data security policy restricts operations so that these operations can only be performed on a
subset of instances of the corresponding database object (an object instance set). Data security
policies can reflect access to:
All Instances (rows) of an object
An Instance Set, which is defined as a SQL predicate (WHERE clause), and can
optionally be implemented as a VPD (Virtual Private Database) policy
A Specific Instance, identified by a primary key value

Chapter
CLASSROOM
Data Security Policies
Example of a Data Security Policy

The Customer Administrator role includes a grant to users with this role that gives customer
administrators the ability to perform some basic administration privileges (All User
Administration Privileges, defined by UMX_OBJ_ADV_ADMIN_PERMS) through a
permission set.
This grant specifies these permissions can be performed on the object (User Management
Person, UMX_PERSON_CODE), but only on the instance set composed of people in the
customers own organization.

Chapter
CLASSROOM
Example of a Data Security Policy
Summary

Chapter
CLASSROOM
Chapter 5
Introduction to Oracle User Management

Chapter
CLASSROOM
Introduction to Oracle User

Management


Chapter
CLASSROOM

Chapter
CLASSROOM
Objectives

Chapter
CLASSROOM
What Is Oracle User Management

Note: This section introduces concepts that will be discussed in greater detail in the subsequent
sections of this course.
The system administrator is a trusted individual who manages an organizations access
policies and administers its users. The system administrator is sometimes also known as
the security administrator.
Oracle User Management enables organizations to define local administrators that manage
a subset of the organizations users. Local administrators are only granted sufficient
enough privileges to manage a specific subset of the organizations users, and they
generally have a closer relationship to those users than the system administrator does.
End Users
Organizations can configure Oracle User Management to enable end users to perform
some of their own registration tasks such as registration, requesting additional access to
the system, or resetting passwords.

Chapter
CLASSROOM
What Is Oracle User Management?
Access Control Model

Core Security
Core Security includes Oracles Function and Data Security models as well as a new Role
Based Access Control (RBAC) model.
Administrative Features
Administrative Features build upon Core Security, and include Delegated Administration,
Registration Processes, and Self-Service and Approvals.

Chapter
CLASSROOM
Access Control Model
Layers of Access Control

Access control with Oracle User Management is implemented in successive layers, each
building 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.

Chapter
CLASSROOM
Successive Layers of Access Control

Access control with Oracle User Management begins with basic system administration tasks
and progresses to more distributed, local modes of administration, ultimately enabling users to
perform some basic, predefined registration tasks on their own. Details of the various levels of
access control and the increasing levels of flexibility they provide are described later in the
course. The following general definitions may be considered for now:
The system administrator is responsible for defining the core of the security system, including
permissions, data security policies, responsibilities, and menus. The system administrator
defines setup for all core security administrative features.
When Role Based Access Control and Delegated Administration are added to the Data Security
and Function Security layers, system administration tasks can be distributed to local
administrators, who manage a subset of the organizations users.
End Users
Registration Processes and Self Service and Approvals further distribute system administration,
by automating some registration tasks so that end users can perform them.

Chapter
CLASSROOM
Increased Flexibility and Scalability
Example
An organization can use Function Security to provide its sales representatives with the required
pages, menus, and menu options for querying customers. It can also control access to specific
components of those pages, such as a "Generate Sales Forecast" button on a sales forecasting
page.

Chapter
CLASSROOM
Function Security
Responsibilities
Responsibilities have a menu tree in which available menus are defined with a grant flag. On
being assigned a responsibility, a user gains access to all menus on the menu tree except those
for which an exclusion has been defined. In the above example, Menu 2 has been excluded
from the menu tree. When the user is assigned the corresponding responsibility, the user can
access Menu 1, Menu 3, and Menu 4.

Chapter
CLASSROOM
Responsibilities
Example
Data Security restricts the set of users that a local administrator can manage and administer
within Oracle User Management. Data Security policies can only be defined for applications
that have been written to utilize the Data Security Framework.

Chapter
CLASSROOM
Data Security

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 inherited implicitly, based on the roles assigned to the user. When making a
mass update in a production system, an organization simply needs to change the permissions or
role inheritance hierarchy defined for a role. The users assigned that role subsequently inherit
the new set of permissions.
Example
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 Manager. 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. In the above example, the manager is assigned the Manager
role and the Employee role, while the employee is only assigned the Employee role.

Chapter
CLASSROOM
Delegated Administration is a privilege model that builds on the RBAC system. With
delegated administration, instead of exclusively relying on a centralized administrator to
manage all of its users, an organization can create local administrators and grant them
sufficient privileges to manage a specific subset of the organization's users and roles. This
provides organizations with a tighter, more granular level of security and the ability to easily
scale their administration.
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 he can manage. Local
administrators can be granted different privileges for different subsets of users.
Role Administration Privileges: Role Administration Privileges define the roles that
local administrators can directly assign to and revoke from the set of users they manage.

Chapter
CLASSROOM
(Optional) Organization Administration Privileges: Organization Administration

Privileges define the organizations a local administrator can view in the system.

Chapter
CLASSROOM
Delegating to Proxy Users

Traditionally, delegation was done by a user supplying his password for specific applications
to another user, who could assume the delegators identity and privileges in those applications.
However, if E-Business Suite is integrated with Oracle Single Sign-On (SSO), this means the
delegate can access every SSO-enabled application to which the delegator has access.
The proxy user mechanism provides a more sophisticated mechanism that enables controlled,
auditable delegation of privilege from delegators to delegates.
Examples of Delegating to Proxy Users
Executives allowing their assistants to access selected business applications on their behalf
Users may need to grant help-desk staff limited duration access to their E-Business Suite
accounts, so that help desk staff can investigate problems and provide assistance
Companies may be subject to audits that require granting a specific user (the auditor)
access to employees' E-Business Suite accounts, typically on a read-only basis.
The ability for users to access the proxy feature is controlled by a Security Administrator
role. Users with this role determine which set of users can create delegates who can act on
their behalf.

Chapter
CLASSROOM
Delegating to Proxy Users
Provisioning Services
Oracle User Management includes the following provisioning services, implemented as
registration processes:
Commonly referred to as Self Service Registration, self-service account requests provide a
method for persons to request a new user account. For example, customers may need to register
before they can purchase an item from an online store. After completing the registration
process, the customer obtains both a user account and the necessary roles for access to the
store.
(ART) available in the global preferences menu. Requests for Additional Access uses the same
Oracle User Management infrastructure and processing logic as Self Service Account
Requests.

Chapter
CLASSROOM
Provisioning Services

available to select administrators.

Chapter
CLASSROOM

Once registration processes have been configured as required, individuals can subsequently
perform self-service registration tasks such as obtaining new user accounts or requesting
additional access to the system. In addition, organizations can use the Oracle Approvals
Management engine to create customized approval routing for these requests.
Example
An organization may enable a small set of users to request a particularly sensitive role;
however, before the user is granted the role, the organization can require that specified
individuals approve the request.

Chapter
CLASSROOM
Self-Service and Approvals
Login Assistance
System administrators often have to reset a user's forgotten password, or even advise a user of
the account's user (login) name. This is unproductive for both the user and the administrator. In
addition, a user may request the password to be reset, when it is actually the user name that has
been forgotten, or vice versa.
A new feature in Release 12 helps reduce the time spent on such administrative activities, by
implementing a login help mechanism on the E-Business Suite Login Page. A user simply
clicks on the "Login Assistance" link located below the Login and Cancel buttons. On the
screen that appears, the user can choose between the Forgot Password and Forgot Username
sections.

Chapter
CLASSROOM
Login Assistance
Summary

Chapter
CLASSROOM
Chapter 6
Implementing Oracle User Management

Chapter
CLASSROOM
Implementing Oracle User

Management


Chapter
CLASSROOM

Chapter
CLASSROOM
Objectives

Chapter
CLASSROOM

Chapter
CLASSROOM
Steps for Implementing Oracle User Management

For the purposes of this course, Phase I: Define Core Security Features has already been
completed, and students will begin with Phase II: Define Roles. When implementing Oracle
User Management, however, you must begin by defining core security features.
You do not have to implement User Management in the exact sequence described here.
However, this is probably the most common implementation flow.
You will test many of the implementation steps by logging on as an administrator or as a user,
and viewing the results of your configuration.

Chapter
CLASSROOM

Chapter
CLASSROOM

Chapter
CLASSROOM
Configuring and Testing Oracle User Management

As system administrator (security administrator), you define roles, role inheritance hierarchies,
delegated administration, registration processes and self-service features. You also designate
local administrators and assign them roles, and optionally allow them to perform self-service
registration. Depending on how those roles are configured, local administrators manage a
subset of the organizations users and roles, as well as designated external contact information.
As a local administrator, you test the delegated administration features defined for the role you
are assigned. These features enable you to manage a subset of your organizations users and
roles, and to manage designated external contact information.
End Users
As an end user, you test the available self-service features such as requesting access (or
additional access) to the system.

Chapter
CLASSROOM
Configuring and Testing Oracle User Management
Introduction to Roles
In previous releases of Oracle Applications, access to individual functions within an
application could only be defined through responsibilities, menu hierarchies, and menu
exclusions. New responsibilities had to be defined for each set of users (with different job
functions) that needed access to a set of pages within an application. These responsibilities
required either:
Completely new menu hierarchies for each responsibility
A common menu covering the superset of all functions within the application, and menu
exclusion rules defined for each responsibility
An example is the Human Resources product, which typically has at least two responsibilities
defined, one for employees and one for managers.
In essence, responsibilities have been used not only to define the application navigation menus,
but also the privileges and permissions within an application. Cost of ownership and
management has increased with the number of responsibilities, as multiple complex menu
hierarchies and/or exclusion rules must be maintained.
Oracle User Management provides new alternatives for defining access to an application,
allowing organizations to separate navigation menus from access control.

Chapter
CLASSROOM
Introduction to Roles
Examples of Roles
In this example, the manager is granted both the employee role and the manager role, since the
manager effectively functions as both.

Chapter
CLASSROOM
Examples of Roles
Defining Roles: Data Security Policies

Data security policies determine what data users can access, and return only that set of data to
those users at runtime.
Example
Data security policies determine to which department a manager belongs, and returns only the
correct set of data for that manager. In the above example, the Manager role is assigned to
Managers X and Y. At runtime, data security policies determine that Manager X should only
view Department X data, and Manager Y should only view Department Y data.

Chapter
CLASSROOM
Defining Roles: Data Security Policies
Defining Roles: Assigning a Single Responsibility that Includes all Functions to a

Role
Organizations can define a single responsibility that includes all functions and assign it to a
role. For example, instead of having a Manager Expenses and Employee Expenses
responsibility, an organization can define an Expenses responsibility that contains all employee
and manager Expenses functions. The grant flag is turned off for all menus defined for this
role.

Chapter
CLASSROOM
Defining Roles: Assigning a Single Responsibility and All Its

Functions to a Role
Defining Roles: Assigning a Single Responsibility to a Role with Some Functions

Included
When a role is assigned, the relevant user is granted the appropriate functions. For example,
the employee is granted employee expenses functions, but the manager expenses functions
remain excluded.

Chapter
CLASSROOM
Assigning a Single Responsibility to a Role and Granting Specific

Functions to a Role
Defining Roles: Assigning Responsibilities to a Role

Organizations can define multiple responsibilities for a single role. With the grant flag on for
all menus in the menu tree, assigning the role to a user gives that user access to all the menus
defined for the role.
In this example, the Manager Expenses and Employee Expenses responsibilities are defined for
the Manager role. When the Manager role is assigned to the manager, the manager has access
to all functions defined for these responsibilities.

Chapter
CLASSROOM
Defining Roles: Assigning Multiple Responsibilities to a Role

Oracle User Management enables you to link roles together in role inheritance hierarchies.
With role inheritance hierarchies, a role can contain sub-roles. When a user is assigned a role,
the user inherits the privileges defined for that role and for all its sub-roles.
Role inheritance means that the permission to access a new page only has to be granted once,
at the lowest-level sub-role in the role inheritance hierarchy; the relevant permissions will then
be inherited automatically by all superior roles in the hierarchy. Equally, revoking access to a
page (or an entire application) is as simple as granting access.
Example
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 sub-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
or Sales Representative.

Chapter
CLASSROOM
Role Categories

Chapter
CLASSROOM
Assigning Permissions to Roles

You can configure permissions for a role.
Data Security: You must select a business object when you create Data Security policies.
Specifying the object data context (data scope) provides an additional level of access
granularity for the object. Choose one of the following from the Data Context menu:
- All Rows: Provides access to all rows (instances) for the database object.
- Instance: Provides access to an instance (single row in the database) of the object.
- Instance Set: Provides access to a related set of instances of the object. This set is
specified as a predicate on the attributes of the object. The predicate is expressed as a
SQL WHERE clause.
Activation Context: Restricts the availability of the permissions being assigned. If you do
not define the activation (security) context, permissions are available to users in all
contexts.
- Operating Unit: Many organizations consist of several different operating units. You
can limit your grant to be active only in the context of an individual operating unit.

Chapter
CLASSROOM
Assigning Permissions to Roles
- Responsibility: Responsibilities determine the applications that can be accessed by

users. You can optionally limit your grant to be available only in the context of an
individual responsibility, or with all responsibilities.

Chapter
CLASSROOM
Advantage of Roles Over Responsibilities

A role can be associated with multiple responsibilities
Because a single role can be associate with multiple responsibilities, multiple responsibilities
can be assigned to a single role, then assigned to users as required. This is more efficient than
assigning or revoking individual responsibilities to each user. When updating menu access or
permissions, organizations can simply add new menu items to the responsibility with the grant
flag off, then switch the grant flag on for a role if the role needs to have access to that menu.
Roles can inherit the properties of other roles
With role inheritance hierarchies, roles can inherit the permissions of roles. This simplifies the
process of defining roles: when defining a higher-level role such as manager, there is no need
to include access to employee menus and responsibilities, since these are inherited from the
lower-level employee role.
Navigation menus and security functions can be separated
As noted in the introduction to this section, RBAC and role inheritance allows organizations to
separate navigation menus from access control: a responsibility can be defined to represent a
single application, and a menu can be tailored for each application. Access to the application

Chapter
CLASSROOM
Advantages of Roles Over Responsibilities
(responsibility) and its menu hierarchy are controlled by different roles, each representing a
specific job function or set of people.

Chapter
CLASSROOM
Phase II: Define Roles

Chapter
CLASSROOM
Steps for Creating Roles: Define a Role Category

In this scenario, an organization is creating a Customer Administrator role. It will require a role
category to contain this or similar roles.

Chapter
CLASSROOM
Steps for Creating Roles: Define a Role Category
Steps for Creating Roles: Create a Role within the Role Category
Create a role and include it within the role category. In this scenario, the role is Customer
Administrator. This role is created for an external organization, and is assigned to individuals
who manage the external organizations users.
Oracle User Management ships with three seeded roles, Partner Administrator, Customer
Administrator, and Security Administrator. The business scenarios and practices in this course
assume that the Customer Administrator role must be created and configured to function with
the other two.
Note: Many of the practices in this course involve creating, configuring, and testing the
Customer Administrator role. Since Oracle User Management already ships with this role, the
practices require students to create a Course Administrator role that is essentially an exact copy
of the seeded Customer Administrator role. Students can compare their Course Administrator
role to the seeded Customer Administrator role; the two should be identical.

Chapter
CLASSROOM
Steps for Creating Roles: Create a Role within the Role Category
Steps for Creating Roles: Place Role in Role Inheritance Hierarchy

Place the Customer Administrator role in a role inheritance hierarchy. In this case, the Partner
Administrator role inherits permissions from the Customer Administrator role, and from the
User Management Responsibility.

Chapter
CLASSROOM
Steps for Creating Roles: Place Role in Role Inheritance

Hierarchy
Steps for Creating Roles: Assigning Permissions to Roles

You can use roles to enable or disable the permissions that the Customer Administrator role
inherits from the User Management responsibility. In this example, User Maintenance UIs
is the only permission enabled for the Customer Administrator role when it inherits the User
Management responsibility.
As a result, when an individual who is assigned the Customer Administrator role logs on to
the system, that person will be able to access User Maintenance UIs, but not be able to query
users unless assigned user administration privileges.

Chapter
CLASSROOM
Steps for Creating Roles: Assign Permissions to Roles
Steps for Creating Roles: Assign Role to a New Person

The system administrator creates a new person and assigns the Customer Administrator Role to
that user.

Chapter
CLASSROOM
Steps for Creating Roles: Assign Role to a New Person
Steps for Creating Roles: Test Role as Customer Administrator

Log on as the newly created Customer Administrator (person assigned the Customer
Administrator role) and test your capabilities.

Chapter
CLASSROOM
Steps for Creating Roles: Test Role as Customer Administrator

Chapter
CLASSROOM
What Is Delegated Administration?

Chapter
CLASSROOM

To grant a local administrator user administration privileges, you must configure the role
assigned to the local administrator. When configuring the role, you must choose which of the
available people and users you want the local administrator to manage, and which permissions
you want to grant the role for managing those people and users.
People and Users
People are any individuals in the system; users are those individuals for whom an account has
been created.
Permissions
Permissions determine the actions that the role assignee (the local administrator) can perform
on the people and users selected for that role. These permissions must be granted with a data
security policy on the User Management Person (UMX_PERSON_OBJECT) business object.

Chapter
CLASSROOM
Configuring Roles for User Administration

Local administrators can be granted different privileges for different subsets (groups) 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.
Example
In this example, assignees of the Local Administrator Role can manage two subsets of their
organizations users and people, Subset A and Subset B. They have permissions to query and
edit person details, manage user accounts, and reset passwords for all users of Subset A.
However, they can only query person details for all users of Subset B.

Chapter
CLASSROOM
User Administration Privileges (cont.)

A role can specify a subset of roles that the assignee can manage. To grant a local
administrator role administration privileges, you must configure the role assigned to the local
administrator.
When configuring the role, you must choose which of the available roles in the system you
want the local administrator to manage. There is a single seeded permission available for
defining role administration privileges for roles, which has a function code of
UMX_OBJ_ADMIN_ROLE. To enable role administration, this permission must be granted
with a data security policy on the User Management Role (UMX_ACCESS_ROLE) business
object.

Chapter
CLASSROOM
Seeded Permissions for User Administration

All user administration privileges must be granted with a data security policy on the User
Management Person (UMX_PERSON_OBJECT) business object.
The Query Person Details (UMX_OBJ_VIEW_PERSON) permission is the minimum
permission required by any security administrator who wishes to manage people and users in
Oracle User Management.
The Maintain System Accounts (UMX_SYSTEM_ACCT_ADMINSTRATION ) permission is
only granted to system administrators.

Chapter
CLASSROOM
Seeded Permissions for User Administration
Managing Roles with Role Administration

In this example, the local administrator can assign roles to (or revoke roles from) the users in
Subsets (groups) A and B.

Chapter
CLASSROOM
Managing Roles with Role Administration
Seeded Permissions for Role Administration

All role administration privileges must be granted with a data security policy on the User
Management Role (UMX_ACCESS_ROLE) business object.

Chapter
CLASSROOM
Seeded Permissions for Role Administration

This privilege enables local administrators to search for people based on their organization,
assuming the local administrator has also been granted access to view the people in that
organization (User Administration Privileges). Depending on the administration account
registration process has been granted, the administrator may have the ability to register new
people for that organization.

Chapter
CLASSROOM
Seeded Permissions for Organization Administration Privileges

All role administration privileges must be granted with a data security policy on the User
Management Organization (UMX_OBJ_VIEW_RLTNSHPS) business object.

Chapter
CLASSROOM
Seeded Permissions for Organization Administration
Advantages of Delegated Administration Over Traditional System Administration

With traditional system administration, one or more trusted individuals manage access control
and users for the entire organization. The system administrator must assign access privileges to
a potentially large number of people and users.
With delegated administration, local administrators manage a specific subset of the
organizations users and roles. Because they can only assign a specific set of roles to a specific
set of users, local administrators ensure that security is maintained along functional areas.
Generally, local administrators will have a working relationship with the set of users they
manage.

Chapter
CLASSROOM
Delegated Administration vs. Traditional System Administration
Phase III: Setting Up Delegated Administration

Chapter
CLASSROOM
Set Up User Administration for a Role

The system administrator sets up user administration for the Customer Administrator role by
determining the users it enables the assignee to manage and the manner (permissions) in which
those users can be managed.

Chapter
CLASSROOM
Steps for Implementing Delegated Administration: Set Up User

Administration for a Role
Steps for Implementing Delegated Administration

Chapter
CLASSROOM

Chapter
CLASSROOM

Chapter
CLASSROOM
Oracle User Management contains the following registration processes:
Commonly referred to as Self-Service Registration, self-service account requests provide a
means for people to request a new user account. For example, customers may need to register
before they can purchase an item from an online store. After completing the registration
process, the customer obtains both a user account and the necessary role(s) to access the store.
(ART), available on the global preferences menu. Requests for Additional Access uses the
same Oracle User Management infrastructure and processing logic as Self-Service Account
Requests.

Chapter
CLASSROOM
available to select administrators.

Chapter
CLASSROOM
Registration Process Core Components

Roles are assigned after the user successfully completes the registration process:
The registration user interface is optional, and is used for collecting account or additional
information.
The workflow is used for approval, confirmation, rejection, and identity verification
notifications.
The approval management transaction type represents a set of approval routing rules that
are interpreted at runtime.
The set of users eligible to request additional access are only applicable for the Request
for Additional Access registration processes.
Identity verification confirms the identity of a requester before the registration request is
processed. An email notification is sent to the submitting email address. If the recipient
does not reply within a predetermined amount of time, the request will be automatically
rejected.
The set of local administrators should be able to register people and/or create users through the
Account Creation by Administrators registration process.

Chapter
CLASSROOM
Registration Processes: Core Components

Self-service account requests provide a method for persons to request a new user account.
Recall the earlier example where customers need to register before they can purchase an item
from an online store: after completing the registration process, the customer obtains both a user
account and the necessary role(s) for access to the store.
Accounts and user accounts (person party in TCA) in this course refer to an individual's login
account, stored in the FND_USER table.
This release of Oracle User Management provides sample Self-Service registration UIs for
internal employees and for new, external individuals. Organizations can copy these sample
Self-Service registration and extend them based on their own requirements. In addition,
organizations wishing to support other types of users, or capture additional user information,
can create their own registration UIs and business logic.

Chapter
CLASSROOM

When users request additional access to the system, they are in effect making a request to be
granted additional roles. The availability of additional roles depends on the users current roles.
For example, an organizations employees could request roles that further define their job
functions, while customers of that organization would not be able to request those same roles.
For example, an employee could request the Support Rep role, but a customer could not.

Chapter
CLASSROOM
Account Creation by Administrators

Each account creation registration process can be made available to selected administrators.

Chapter
CLASSROOM
Account Creation by Administrators
Steps for Creating Registration Processes

The following slides describe the steps in the creation of registration processes.

Chapter
CLASSROOM
Phase IV: Creating Registration Processes
Steps for Creating Registration Processes: Provide Required Description

Information
The System Administrator creates the request for additional access registration process and
assigns it to one of the roles managed by the Customer Administrator. The Customer
Administrator subsequently logs on and assigns that role to a new user.
You must provide the following information for the registration process description:
Role: The role with which you optionally associate the registration process, and which is
assigned to the user at the end of the registration process.
Type: Type of registration process you wish to create.
Registration Process Code. Unique identifier for the registration process.
Display Name: Display name for the registration process.
Description: Description of the registration process.
Application: Application with which the registration process is classified, which can be
used for querying the registration process.
Active From: Date from which the registration process is first active.

Chapter
CLASSROOM
Steps for Creating Registration Processes: Provide Required

Description Information
Active To: Date you can (optionally) specify to terminate the registration process.

Chapter
CLASSROOM
Steps for Creating Registration Processes: Enter Runtime Execution Information

Enter the runtime execution information for the registration process and click the Next button.
This information specifies:
Registration Start Page: The first page (represented as a function) in the registration
process, which captures any additional user registration information. This page is optional,
unless you are creating a Self-Service Account Request registration process.
Notification Event: The workflow business event that invokes a workflow. The
notification workflow subscribes to the event, and subsequently sends notifications to the
approver or to the user.
Approval Transaction Type: The set of approval routing rules that is interpreted at
runtime by the Oracle Approval Management rules engine. Based on the user transaction
types you have defined specifically for use with Oracle User Management, the rules
determine whether approval is required, and if so, by which set of users.

Chapter
CLASSROOM
Steps for Creating Registration Processes: Enter Runtime

Execution Information
Steps for Creating Registration Processes: Enter Eligibility Information

Enter the eligibility information for the registration process by selecting the appropriate roles
or groups. In this case, eligibility will be everyone. For Requests for Additional Access,
eligibility defines the users who are able to register for the role associated with the registration
process. For Account Creation by Administrators, eligibility determines which administrators
can register new users through the registration process. Oracle User Management ships with
the following seeded permissions for defining eligibility policies:
Administrator Assisted Account Creation (UMX_OBJ_ADMIN_CRTN_FLOW )
Permission representing "Administrator Assisted Account Creation" registration processes.
Must be granted as a data security policy on the Registration Process (UMX_REG_SRVC)
business object.
Self-Service Eligibility (UMX_OBJ_ROLE_ELGBLTY)
Permission representing registration processes for additional access determines the set of end
users who are eligible to register for a given role/registration process. Must be granted as a data
security policy on the Registration Process (UMX_REG_SRVC) business object.

Chapter
CLASSROOM
Steps for Creating Registration Processes: Enter Eligibility

Information
Steps for Creating Registration Processes: Register Subscriptions to Business

Events
Register subscriptions to the appropriate business events raised by Oracle User Management,
ensuring that your subscription logic writes the registration data to the appropriate destination
schemas.

Chapter
CLASSROOM
Steps for Creating Registration Processes: Register Subscriptions

to Business Events
Steps for Creating Registration Processes: Optionally Set Profile Options

Optionally set the following profile options for registration processes of type Self-Service
Account Request:
Registration Links: Oracle User Management provides support for displaying different
registration links on the login page, based upon the application tier through which the
login page is accessed. Organizations can set the server level profile option, UMX:
Register Here Link: Default Registration Process
(UMX_REGISTER_HERE_REG_SRV) to specify different destinations for the
registration link.
Registration Parameters: The registration link can also contain additional parameters
that are not known at design time. These parameters are available at all stages of the
registration process; for example, for routing approval requests. Organizations can set the
server level profile option, UMX: Register Here Link: Default Registration Parameters
(UMX_REGISTER_HERE_REGPARAMS) for this. The format for this profile option is:
"ParamName1=ParamValue1&ParamName2=ParamValue2.

Chapter
CLASSROOM
Steps for Creating Registration Processes: Optionally Set Profile

Options
UI-specific Parameters: Organizations can additionally specify parameters used to

control the rendering of the registration user interface, such as the menu displayed in the
registration UI. The server level profile option, UMX: Register Here Link: Default Html
Parameters (UMX_REGISTER_HERE_HTMLPARAMS) can be set for this. The format
for this profile option is: "ParamName1=ParamValue1&ParamName2=ParamValue2.

Chapter
CLASSROOM
Steps for Creating Registration Processes: Optionally Set Login Page UI

Attributes
Optionally set the UI attributes for the login page using the profile option, Local Login Mask:
FND_SSO_LOCAL_LOGIN_MASK. For the Login page to display one or more of these
optional attributes, add the numeric values of all desired attributes and set the value of the
profile option to that value:
USERNAME_HINT = 01
PASSWORD_HINT = 02
CANCEL_BUTTON = 04
FORGOT_PASSWORD_URL = 08
REGISTER_URL = 16
LANGUAGE_IMAGES = 32
SARBANES_OXLEY_TEXT = 64

Chapter
CLASSROOM
Steps for Creating Registration Processes: Optionally Set Login

Page UI Attributes
For example, to show PASSWORD_HINT and FORGOT_PASSWORD_URL only, set the

profile option to 10 (02+08). To show just the LANGUAGE_IMAGES set the value to 32,
which is the default.

Chapter
CLASSROOM
Steps for Creating Registration Processes: Test as Customer Administrator

The Customer Administrator assigns the role associated with the registration process to a
customer. The customer can then request additional access. You perform this test in Phase IV:
Understand and Test the Self-Service Features.

Chapter
CLASSROOM
Steps for Creating Registration Processes: Test as Customer

Administrator
Managing Proxy Users

Proxy users are set up by logging in as System Administrator, navigating to User Management
> Users, querying the user (delegator) who is to grant proxy privileges to other users, clicking
on the Update icon of the results table to navigate to the User Details page, clicking on the
Assign Role button, searching for Manage Proxies role in the list of values, and selecting this
role.
Proxy User privileges are delegated by logging on as a user with the Manage Proxies role,
clicking on the Global Preferences menu, clicking on the Add People button under the Manage
Proxies link, and selecting a user from the list of values. Once the changes have been saved, a
notification is sent to the user who has been granted the proxy privileges.
Acting as a Proxy User
Users permitted to act on behalf of other users will have their names displayed with the
prefix Logged in as in the upper right of the page.
To switch to another user (act as a delegate), a user can choose the Switch User icon and
link to access the Switch User page.
After a delegator has been selected, the application will enter Proxy Mode. While in this
mode, the icon and link will change from Switch User to Return to Self.

Chapter
CLASSROOM
Managing Proxy Users
Using Proxy Mode turns on Page Access Tracking, to enable auditing of pages visited by the
user when acting as a proxy. Go to Preferences > Manage Proxies > Run Proxy Report

Chapter
CLASSROOM
Self-Service Features

Chapter
CLASSROOM
Self-Service Features

Chapter
CLASSROOM
Login Assistance
System administrators often have to reset a user's forgotten password, or even advise a user of
the account's user (login) name. This is unproductive for both the user and the administrator. In
addition, a user may request the password to be reset, when it is actually the user name that has
been forgotten, or vice versa.
A new feature in Release 12 helps reduce the time spent on such administrative activities, by
implementing a login help mechanism on the E-Business Suite Login Page. A user simply
clicks on the "Login Assistance" link located below the Login and Cancel buttons.
On the login assistance screen that appears, the user can either go to the Forgot Password
section and enter the correct user name, or to the Forgot Username section and enter the email
address associated with the account. The user will then either be emailed either password reset
details or the user name, as applicable.
For security, the relevant data is stored securely in workflow tables, and the secure URLs
employed by the mechanism have both an expiration time and a single-use limitation.

Chapter
CLASSROOM
Login Assistance
Summary

Chapter
CLASSROOM


Chapter
CLASSROOM
Chapter 7
Profile Options
Chapter
CLASSROOM
Profile Options

Profile Options
Chapter
CLASSROOM
Managing Profile Options
Profile Options
Chapter
CLASSROOM
Lesson Aim
As a system administrator, you control various options in Oracle Applications that determine
how your applications look and feel. These options can also control how each application
operates. This lesson shows you how to specify these values.
Profile Options
Chapter
CLASSROOM
Objectives
Personal Profile Values

For further information on using the Personal Profile Values window see:
(Help) Oracle Applications Users Guide > Profile Options >
Setting Your Personal User Profile
The table FND_PROFILE_OPTION_VALUES stores values for user profile options. Each
row includes values that identify the profile option; the profile level; and the user,
responsibility, application, organization, server, or site for whom the profile value is set. There
is one row for each profile option setting (at each level, for each user, and so on).
Profile Options
Chapter
CLASSROOM
Personal Profile Values
System Profile Options - Hierarchy Types

Of the three hierarchy types, the Security type is most widely used.
Profile Options
Chapter
CLASSROOM
System Profile Options - Profile Hierarchy Types
Setting Profile Hierarchy Levels

You can set user profiles at different levels, using one of three hierarchies.
Most profile options use the Security hierarchy, in which setting a user profile affects
application users across one of four different levels.
Site Level Site-level settings apply to all users at an installation site. To display the name of
your installation site, select About Oracle Applications from the Help menu.
Application Level Application-level settings apply to all users of the specified application.
For example, a profile could be set that applies to all Oracle General Ledger users. Profile
options that can be set at the application-level override options set at the site level.
Responsibility Level Responsibility-level settings apply to all users currently signed on
under the responsibility. For example, a profile could be set that applies to all users of the
Oracle General Ledger GL budget supervisor responsibility. Profile options that can be set at
the responsibility level override options set at the site and application levels.
User Level User-level settings apply to individual users, identified by their application
usernames. For example, a user profile could be set that applies only to user JDoe. Profile
options set at the user level override all other options.
Profile Options
Chapter
CLASSROOM
Profile Hierarchy Levels - Security
Profile Hierarchy Levels - Organization

The second hierarchy type is Organization, where organization refers to operating unit. For
example, clerks in different organizations may need to have different values for a given profile
option, depending on their organization, but clerks in the same organization would use the
same value. The Organization hierarchy type allows system administrators to set a profile
option at the organization level, so that all users within that organization will use the profile
option value set once at the organization level. Profiles using the Organization type use the
hierarchy Site - Organization User, where a user level option overrides the organization level
option, which overrides the site level option.
An example of a profile option using the hierarchy type Organization is AR: Default Credit
Management Currency (Receivables).
Profile Options
Chapter
CLASSROOM
Profile Hierarchy Levels Organization
Profile Hierarchy Levels - Server

The Server hierarchy type is used when the system needs to determine the server on which the
user's session is running. For example, the profile Applications Web Agent (Application Object
Library) can be defined using the Server type. The setting of this profile option can differ for
an internal server versus an external one. Cookie validation, for example, can then be done
against the value of this profile option. Profiles using the Server type use the hierarchy Site Server - User, where a user level option overrides the server level option, which overrides the
site level option.
Another example of a profile option using the Server hierarchy type is Node Trust Level
(Application Object Library).
Profile Options
Chapter
CLASSROOM
Profile Hierarchy Levels - Server
Setting System Profile Options

For profiles using the Security hierarchy type, if you choose to set a value at the Application,
Responsibility, or User level, you must also specify the particular Application, Responsibility,
or User. Any values defined at a lower level than the level chosen will also be displayed.
Likewise, for profiles using the Organization hierarchy, if you choose to set a value at the
Organization or User level, you must also specify the particular Organization or User. For
profiles using the Server hierarchy, if you choose to set a value at the Server or User level, you
must also specify the particular Server or User. Any values defined at a lower level than the
level chosen will also be displayed.
For a complete description of the fields in the System Profile Values window see:
(Help) Applied Technology > Oracle Applications System Administration >
Setting Profile Options > System Profile Values Window
Profile Options
Chapter
CLASSROOM
System Profile Options
Default User Profile Values

After profile values have been defined, they can be referenced elsewhere in Oracle
Applications. The figure shows the locations where profile values can be used to supply default
processing values.
Enter the setting of a profile option as a default value by selecting Profile as the default
type, and then enter the internal name (not end-user name) of the profile option as the
value in the Default Value field.
Look up the internal name of the profile option in the User Profiles appendix of the Oracle
Applications System Administrators Guide.
Profile Options
Chapter
CLASSROOM
Using User Profile Values as Defaults
Profile Categories
(N) Functional Administrator responsibility > Core Services > Profile Categories
Profile options can be grouped into logical categories based on their functional area. A profile
option can belong to more than one profile category.
You can create new or update existing profile categories.
The following slides describe some of the more commonly-used profile options. They do not
represent all the profile options included in each listed profile category.
Profile Options
Chapter
CLASSROOM
Profile Categories
How to Use Profile Options Related to Auditing

These two profile options are used to enable auditing within Oracle Applications. They belong
to the Security profile category.
AuditTrail: Activate
This option enables auditing of changes to database tables. AuditTrail tracks which rows in a
database table or tables were updated, at what time, and which user was logged in using the
form or forms.
Sign-On: Audit Level
This option allows you to select a level at which to audit users signing on to Oracle
Applications. Choose from four audit levels which increase in functionality:
None default value. No users will be audited.
User tracks who signs on to your system, the times the users log on and off, and the
terminals used.
Responsibility performs the User-level audit as well as tracking the responsibilities the
users choose and how much time spent as each responsibility.
Profile Options
Chapter
CLASSROOM
Auditing Related Profile Options
Form performs the Responsibility-level audit and also tracks the forms the users choose
and how long each form is used.
Profile Options
Chapter
CLASSROOM
How to Use Currency-Related Options

The options shown in the figure control the editing of monetary fields. They belong to the
NLS profile category.
Currency: Negative Format
This option enables the user to select the indicators for a negative amount.
Currency: Positive Format
This option enables the user to select the indicators for a positive amount.
Currency: Thousands Separator
This option enables the user to request that a comma be inserted appropriately within a number
of a thousand or more.
Profile Options
Chapter
CLASSROOM
Currency-Related Options
How to Use Flexfield-Related Options

The options shown on the figure control the behavior of flexfield processing.
These profile options belong to the Flexfields profile category.
AutoSkip
As soon as you enter a valid value into a flexfield segment, AutoSkip automatically positions
your cursor in the next segment.
Shorthand Entry
This option controls the behavior of shorthand entry of flexfields if shorthand entry has been
defined.
Show Full Value
If both shorthand entry and a complete alias have been defined for a flexfield, and this option is
set to no, the complete flexfield window does not open when the alias is entered. If this option
is set to Yes, the window always opens.
Validate on Server
Set this option to Yes to enable server-side validation of key flexfields. This improves
performance when using key flexfields over a wide-area network.
Profile Options
Chapter
CLASSROOM
Flexfield-Related Options
BiDi Direction
This option controls the appearance of the flexfields window in Applications running in
Semitic languages.
LOV Warning Limit
Sometimes an LOV can take a very long time to run if there is a very significant amount of
data in it. Set this option to the number of rows to be returned before you are asked to continue
retrieving the entire list.
Open Descr Window
This option allows you to control whether a descriptive flexfield window automatically opens
when you navigate to a customized descriptive flexfield.
Profile Options
Chapter
CLASSROOM
How to Control Output Processing at the System Level

The options shown in the figure control output processing at the system level.
They belong to the Concurrent Processing File Server profile category.
RRA: Enabled
Set this user profile to Yes to use the Report Review Agent to access files on concurrent
processing nodes.
RRA: Delete Temporary Files
When users use a custom editor to view a concurrent output or log file, the Report Review
Agent makes a temporary copy of the file on the client. Setting this option to Yes automatically
deletes these files when the user exits Oracle Applications.
RRA: Maximum Transfer Size
Specify, in bytes, the maximum allowable size of files transferred by the Report Review Agent.
If you enter no value, there is no size limit.
RRA: URL
Specify a URL that points to the CGI script on your WebServer to use the Report Review
Agent to access files on concurrent processing nodes.
Profile Options
Chapter
CLASSROOM
Online Reporting-Related Options
How the User Can Control Request Output

A user can set several options to control request output. You can specify different tools to
view different output types, as well as different font sizes. If a user asks to send request
completion notifications to other people, a URL pointing to request results can be sent.
These profile options belong to the Concurrent Processing View Requests profile category.
Profile Options
Chapter
CLASSROOM
Personal Output Viewer Options
How to Use User-Related Concurrent Request Profile Options

These belong to the Concurrent Processing Execution profile category.
Concurrent: Attach URL
Setting this option to Yes causes a URL to be attached to request completion notifications.
When a user submits a request, and specifies people to be notified in the defining completion
options region, a URL is appended to the notification that enables them to view the request online.
Concurrent: Save Output
You can save your request outputs in a file if one is generated. This allows you to reprint a
request.
Concurrent: Active Request Limit
You can limit the number of requests that can be run simultaneously by each user, or for every
user at a site.
Concurrent: Request Priority
This displays the default priority number for your concurrent requests. Priorities range from 1
(highest) to 99 (lowest). The default is 50.
Profile Options
Chapter
CLASSROOM
User-Related Concurrent Request Profile Options
Concurrent: Sequential Requests

Setting this option to Yes forces requests to run sequentially in the order in which they were
submitted.
Profile Options
Chapter
CLASSROOM
How to Use Security Signon Profile Options

These profile options belong to Security profile category.
Sign-On:Notification
Setting this option to Yes displays a message at login that indicates:
Concurrent request failures since your last session
How many times someone tried to log on to Oracle Applications with your username and
an incorrect password
When the default printer identified in your user profile is unregistered or not specified
Signon Password Hard to Guess
This profile option sets 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:
It contains at least one letter and at least one number
It does not contain the username
It does not contain repeating characters
Signon Password Length
Profile Options
Chapter
CLASSROOM
Security Signon Profile Options
Signon Password Length sets the minimum length of an Applications signon password. If no
value is entered, the minimum length defaults to 5.
Signon Password No Reuse
This profile option specifies the number of days that a user must wait before being allowed to
reuse a password.
Profile Options
Chapter
CLASSROOM
Lesson Summary
An important function of the system administrator is to control the default behavior and
appearance of Oracle Applications. This is done by specifying profile values. In this lesson you
saw how to display and update profile values. You also learned how to reference previously
defined profile values elsewhere in Oracle Applications.
Profile Options
Chapter
CLASSROOM
Summary
Chapter 8
Auditing System Resources

Chapter
CLASSROOM


Chapter
CLASSROOM

Chapter
CLASSROOM
Lesson Aim
As system administrator you may audit application users and the changes they make to
application data. You will learn how both of these options are set and why you use them.

Chapter
CLASSROOM
Objectives
Changes to Audit in Oracle Applications

Within Oracle Applications, you can audit user activity and database row changes.
SignOn Audit Feature
The SignOn Audit feature enables you to monitor user activity. You can audit at the user,
responsibility, or form level. When you enable Signon Audit, you specify the desired level of
auditing. Signon Audit provides two methods for viewing audit data:
The Monitor Users form provides online access to audit data.
Various Signon Audit reports are available.
AuditTrail Feature
With the AuditTrail feature you can keep a history of changes to your important data: what
changed, who changed it, and when it changed. With AuditTrail, you can easily determine how
any data row or element obtained its current value. The audit data is stored in database tables
that can be queried by using any standard Oracle SQL tool.

Chapter
CLASSROOM
Auditing Oracle Applications
Signon Audit Feature

You can audit and monitor user activity by enabling the Oracle Applications Signon Audit
feature, enabling you to track the activity of users signed on to Oracle Applications. Implement
the Signon Audit feature by updating the Sign-On: Audit Level system profile.
With Signon Audit you can choose whom to audit and what type of user information to track.
You can selectively determine what audit information you need to match the needs of your
organization.
Signon Audit Reports
Signon Audit reports give you historical, detailed information on what your users do in your
application. You control the data selected for the reports as well as how the data is presented.
Monitor Users Window
The Monitor Users window gives you online, real-time information about who is using Oracle
Applications and for what purpose.
You can see which users are signed on and which responsibilities and forms they are using.

Chapter
CLASSROOM
Auditing User Activity
Signon Audit Levels

The Sign-On: Audit Level profile option enables you to select a level at which to audit users
who sign on to Oracle Applications. The four possible audit levels increase in functionality and
detail of auditing.
None: Is the default value and disables the Signon Audit feature.
User: Auditing at the user level tracks who signs on to your system and the times that
users log on and off.
Responsibility: Auditing at the responsibility level tracks all the information tracked at
the user level, including the responsibility the user is using and how much time the user
used the responsibility.
Form: Auditing at the form level tracks all the information tracked at the user and
responsibility levels as well as which forms the user chooses and how long he or she uses
those forms.
The recommended setting is Form to enable as much auditing as possible. At this setting, the
system logs all user sign-ons, responsibility selections and instances of access to forms.
Note: This profile option can be set in the Oracle Applications Manager Signon Audit Setup
page.

Chapter
CLASSROOM
Signon Audit Profile Option
Reports
The Signon Audit feature can generate several reports detailing information gathered by
Signon Audit. These reports are shown in the figure.
Signon Audit Forms
Signon Audit Users
Signon Audit Responsibilities
Signon Audit Concurrent Requests Report
Signon Audit Unsuccessful Logins Report

Chapter
CLASSROOM
Signon Audit Reports
Using the Signon Audit Forms Report

Use the Signon Audit Forms Report to view who is navigating to what form and when. You
can use this report to check for bottlenecks in the system. The report contains the following
columns:
User Name: Oracle Applications username of the user who accessed the form
Responsibility Name: Name of the responsibility from which the user accessed the form.
(The responsibility is displayed only if you audited the user at the responsibility or form
Signon Audit level.)
Start Active Time/End Active Time: Dates and times when the user accessed and exited
the form (This information is displayed only if you audited at the form level.)
Form Name: Name of the form the user accessed. (The form name is displayed only if you
audited the user at the form level.)

Chapter
CLASSROOM
Signon Audit Forms Report
Using the Signon Concurrent Requests Report

You can use this report to view information about concurrent requests.
Login Name: Operating system login name of the user who submitted the concurrent
request.
Request ID: Concurrent request ID of the submitted concurrent request.
Concurrent Program Name: Name of the concurrent program the user submitted.
User Name: Oracle Applications username of the user who submitted the concurrent
request.
Responsibility Name: Name of the responsibility from which the user submitted the
concurrent request. (The responsibility is displayed only if you audited the user at the
responsibility or form level.)
Form Name: Name of the form from which the user submitted the concurrent request.
(This information is displayed only if you audited the user at the form level.)
Requested Start Time: Date and time when the request started running.

Chapter
CLASSROOM
Signon Audit Concurrent Requests Report
Using the Signon Audit Responsibilities Report

You can use this report to view who is selecting what responsibility and when. The report
contains the following columns:
User Name: Oracle Applications username of the user who selected the form.
Responsibility Name: Name of the responsibility that the user used. (The responsibility is
displayed only if you audited the user at the responsibility or form level.)
Start Active Time/End Active Time: Dates and times when the user selected or exited the
responsibility. The start active time and end active time are displayed only if you audited
the user at the responsibility or form level.

Chapter
CLASSROOM
Signon Audit Responsibilities Report
Using the Signon Audit Unsuccessful Logins Report

You can use this report to view who attempted unsuccessfully to sign on to Oracle
Applications as another user. An unsuccessful login occurs when a correct username is entered
with an incorrect password. The report contains the following columns:
Username: Oracle Application username of the user who unsuccessfully signed on.
Attempt Time: Date and time when the user unsuccessfully tried to sign on.

Chapter
CLASSROOM
Signon Audit Unsuccessful Logins Report
Using the Signon Audit Users Report

You can use this report to view who signs on and for how long. The report contains the
following columns:
Session Number: Oracle Applications session number uniquely identifying each
application user sign-on.
User Name: Oracle Applications username of the user who signed on.
Start Active Time/End Active Time: Dates and times when the user accessed/ exited
Oracle Applications. (The start active time and end active time display only if you audited
the user at the user Signon Audit level.)
ORACLE Process: Oracle Process ID used during the users sign-on.

Chapter
CLASSROOM
Signon Audit Users Report
Purge Signon Audit Data

Purge end-user access data using the Purge Signon Audit Data concurrent program. This
concurrent program purges all audit records older than a user-supplied date. Run this
concurrent program between once a week and once a month, retaining thirty to ninety days of
records. This concurrent program purges the following tables:
FND_LOGIN_RESP_FORMS
FND_LOGIN_RESPONSIBILITIES
FND_LOGINS
FND_UNSUCCESSFUL_LOGINS
Purge concurrent request data using the Purge Concurrent Request and/or Manager Data
concurrent program. Run this concurrent program at least once a week and retain 14 to 90
days of records.
Note: This concurrent program can be scheduled and monitored through Oracle Applications
Manager, from the Critical Activities tab on the Applications Dashboard.

Chapter
CLASSROOM
Purge Audit Records

(N) Security > User > Monitor

Chapter
CLASSROOM
Auditing Important Data

AuditTrail enables you to keep a history of changes to your important data. You can track what
changed, who changed it, and when it was changed. Using AuditTrail, you can easily
determine how any data row or column obtained its current value.
When you enter or update data through your forms, you change the underlying database tables.
AuditTrail tracks which rows in the database were updated. Audit information for each of these
changes is stored in audit tables that can then be queried and reported upon.

Chapter
CLASSROOM
Auditing Database Changes
How to Set Up the AuditTrail

The figure shows the steps involved in implementing AuditTrail. These steps are covered in the
subsequent slides.
Because there is overhead involved in recording audit information, it is important to
determine which columns of which tables should be audited; not all changes to all tables
need to be tracked.
After you have identified what to audit, you can begin setting up AuditTrail definitions.
You should select tables for auditing that are functionally related. Create an Audit Group
containing these related tables.
For each of the tables in the audit group, you must define which columns are to be audited.
The primary key columns for these tables are automatically included.
Enable auditing of a particular Oracle ID (schema) by defining audit installations, thus
enabling you to audit across multiple application installations.
After your definitions are complete, run the AuditTrail Update Tables Report program to
create your audit tables and enable auditing for your audit group.
There are no predefined audit reports. You can use any SQL tool to retrieve information
from your audit tables.

Chapter
CLASSROOM
Steps for Setting Up AuditTrail
Determining Columns and Tables to Audit

You should select columns from tables that are functionally related. For example, if the
accounting department wants to audit changes to any customer transactions involving cash
receipts, columns from the Customer Transactions Lines table, the Cash Receipts table, and the
Adjustments table would be good candidates for auditing.

Chapter
CLASSROOM
Identify Tables and Columns to Audit
Audit Groups
(N) Security > AuditTrail > Groups
Once you have your tables and columns identified, you should group those tables into an audit
group. In the figure, the three tables mentioned have been placed together in a Receivables
Internal Control audit group.

Chapter
CLASSROOM
Create an Audit Group
Audit Tables Window

(N) Security > AuditTrail > Tables
For further descriptions of the Audit Tables window see:
(Help) Applied Technology > Oracle Applications System Administration >
User and Data Auditing > Audit Tables Window

Chapter
CLASSROOM
Audit Tables Window
(N) Security > AuditTrail > Install

Chapter
CLASSROOM
Identifying the Schema to be Audited
Enabling Audit Processing
(N) Requests > Run

Chapter
CLASSROOM
What Audit Shadow Tables Identify

For each table being audited, an audit shadow table is created. This table contains audit
processing data such as the transaction type (for instance, INSERT) and time-stamp data, the
primary key columns of the audited table, and whatever columns are being audited. In the
example above, the CUSTOMER_TRX_ID, APPROVED_BY, CREATED_BY, and
ACCT._AMOUNT of the AR_ADJUSTMENTS_ALL table are being audited so the shadow
table includes these columns as well as the other columns required by the audit process.

Chapter
CLASSROOM
Audit Shadow Tables
Using Shadow Table Views

Two views are created for a shadow table. These views are called Shadow_Table_Name_Avn
and Shadow_Table_Name_Acn where n is a number. If the number of columns being audited is
very large, multiple views are created and numbered sequentially. The presentation of the audit
table data is different depending on whether you are querying the AV view or the AC view.
The AC view enables you to reconstruct the value for a row at a given time while the AV view
provides simple access to when a value was changed.

Chapter
CLASSROOM
Shadow Table Views
Summary

Chapter
CLASSROOM


Chapter
CLASSROOM
Chapter 9
Managing Printers
Chapter
CLASSROOM
Managing Printers

Managing Printers
Chapter
CLASSROOM
Managing Printers
Managing Printers
Chapter
CLASSROOM
Lesson Aim
Installing a new printer is a typical responsibility of the system administrator. A less common
need is to customize the software that supports printers. This lesson covers the basics of
printer setup and the Pasta printing utility. References for additional information on
customizing your printer setup are also provided.
To set up your printers, you can either use the Pasta utility, in which you enter configuration
data in a file called pasta.cfg, and use predefined components. Alternatively, you can use the
printing setup windows to define your components and enter configuration information.
Managing Printers
Chapter
CLASSROOM
Objectives
Required Formatting Information for Components

The formatting information required by your printer is specified by the components shown on
this figure.
Printer Type
Describes what kind of a printer you have. This is the manufacturer and modelfor example, a
DEC LN03 printer or an HP LaserJet III printer.
Printer Style
Describes how a report should be printed
Determines the number of lines (rows) per page
Determines the width of each line (number of columns)
Controls whether to print a header page
Printer Driver
Contains the set of commands that tell a printer how to print in the print style chosen
Initializes printing orientation
Resets printer drivers instructions for next print job
Managing Printers
Chapter
CLASSROOM
Oracle Print Definition Components
Printer Drivers Versus SRW

A printer driver formats the destination printer.
An SRW driver formats text and sets page breaks in an Oracle Reports file.
Managing Printers
Chapter
CLASSROOM
How the Print Components Are Related

Oracle Applications uses the components shown on the previous figure to store the information
necessary to print a report. This figure shows how the components are related to provide a
flexible method of defining your print environment. The printer type is at the heart of your
print definitions. The above figure displays:
A printer is registered as a printer type.
A printer style is associated with a printer type.
A printer driver is assigned to a printer type.
Managing Printers
Chapter
CLASSROOM
Relationships of the Printer Components
Formatting Information
For a printer to produce a report, it requires three basic types of formatting instructions: text,
document, and printer.
Text Formatting
Oracle Reports generates reports for the various Oracle Applications.
When Oracle Reports formats text as bold or underlined, and sets page breaks, formatting
codes are used.
A SQL*ReportWriter (SRW) driver defines text formatting codes used by Oracle Reports.
Document Formatting
The dimensions for a report output file are predefined as the number of rows and columns
(height and width).
A print style defines the dimensions for a report output file.
Printer Formatting
A printer prints in a certain orientation, portrait or landscape.
A printer can also start printing with a specific font and type size. These instructions are
contained in an initialization string.
Managing Printers
Chapter
CLASSROOM
Formatting Information
A printer driver defines initialization and reset strings.
Managing Printers
Chapter
CLASSROOM
How to Define Printers

The figure shows the sequence of operations to define printers. Generally, you simply register
a new printer by using existing definitions as shown in the path on the left. However, in some
cases you must modify existing definitions or create new definitions to accommodate a new
printer as shown on the right.
This lesson focuses on printing with the Pasta printing utility, which greatly simplifies your
configuration. Custom configurations not using Pasta (those that would follow the illustration
on the right) are covered in the Oracle Applications System Administrators Guide
Configuration.
Managing Printers
Chapter
CLASSROOM
Defining Printers
Printer Types Window

(N) Install > Printer > Types
(Help) Applied Technology > Oracle Applications System Administration > Printers > Printer
Types Window
Managing Printers
Chapter
CLASSROOM
Finding Existing Printer Types
Registering a New Printer

(N) Install > Printer > Register
(Help) Applied Technology > Oracle Applications System Administration > Printers > Printers
Window
Managing Printers
Chapter
CLASSROOM
Registering a New Printer
Defining a New Printer Type

(N) Install > Printer > Types
(Help) Applied Technology > Oracle Applications System Administration > Printers > Printer
Types Window
Managing Printers
Chapter
CLASSROOM
Defining a New Printer Type
Overview of Printing with Pasta

Pasta is an Oracle Applications utility that converts text report files to PostScript and also
enables the printing of custom PostScript reports from Oracle Applications. The reports can
then be directed to any PostScript printer.
Setting up your system to use Pasta is simpler than the standard Oracle Applications printer
setup procedure. The Printer Type, Printer Driver, and SRW driver files are provided. The only
setup required to begin printing is the registration of the printer with Oracle Applications.
Many printing options can be defined using the Pasta configuration file (pasta.cfg). You no
longer need to maintain multiple drivers and styles for each printer.
Pasta is provided as an executable named FNDPSTAX.
For updates and more details, see the Pasta 3.0.4.0 Users Guide for Release 12 available from
OracleMetaLink Note 239196.1.
Managing Printers
Chapter
CLASSROOM
Printing with Pasta
Setup for Basic Printing with Pasta

Use the following Steps to enable any PostScript printer to print text or PostScript reports in
the following styles: Landscape, Landwide, Portrait, or Dynamic.
Use the Printers window to register your printer:
1. Enter your printers name as defined in the operating system and applications.
2. Select Pasta Universal Printer from the list of values for the printer Type.
You are now ready to print text and PostScript reports from your PostScript printer using the
default Pasta configuration.
Managing Printers
Chapter
CLASSROOM
Setup for Basic Printing with Pasta
The pasta.cfg file

The pasta.cfg file controls many printing options, such as margins, or output type.
The pasta.cfg file is an ASCII text file that is shipped in the $FND_TOP/resource/ directory.
Special options are included to support Arabic, Hebrew, and Thai data.
If you have printers that require special setup, you can customize these options by creating a
configuration file for each printer. Copy the pasta.cfg file to pasta_<printer name>.cfg. Make
the necessary changes to the file. Pasta automatically looks for a printerspecific file name. If it
does not find one, Pasta then uses the default file, pasta.cfg.
Managing Printers
Chapter
CLASSROOM
The pasta.cfg file
Modifying an Existing Printer Type to use Pasta

If your printer is already assigned to a printer type that contains styles and drivers you want to
maintain, you can add Pasta to the existing printer type.
To do so, associate one of the Pasta printer drivers with a print style on the Printer Types
window.
The seeded Pasta printer drivers are:
PASTA_LANDSCAPE
PASTA_PORTRAIT
PASTA_LANDWIDE
PASTA_DYNAMIC
You can associate a Pasta driver with an existing print style, or you can create a new print
style.
Steps
1. Query your existing printer type in the Printer Types window.
Managing Printers
Chapter
CLASSROOM
Modifying an Existing Printer Type to Use Pasta
Managing Printers
Chapter
CLASSROOM
2. In the Style field, select the style to which you want to assign a Pasta driver. Or, if you are
assigning Pasta to a style already defined for the printer type, delete the driver in the
Driver Name field currently associated with the style.
3. In the Driver Name field, select the appropriate Pasta driver.
Adding a New Printer Type to Use Pasta
If you want to add a new printer type, you can also add Pasta to your new printer type.
1. Navigate to the Printer Types window.
2. Enter the Type of printer.
3. In the Style field use the list of values to select the style to which you want to assign a
Pasta driver.
4. In the Driver Name field, select the appropriate Pasta driver from the list of values:
- PASTA_LANDSCAPE
- PASTA_PORTRAIT
- PASTA_LANDWIDE
- PASTA_DYNAMIC
Generating Other Formats using the Preprocessing Option

Pasta can use a preprocessing option to generate output in formats other than those that Pasta
natively supports. For example, by invoking Ghostscript, you can generate PDF output. With
this option, Pasta invokes a filter program to preprocess preprocess the Pasta output before
passing it to the printing command.
Managing Printers
Chapter
CLASSROOM
Generating Other Formats using the Preprocessing Option
Using Pasta with XML Publisher

Oracle XML Publisher is a template-based publishing solution. It provides a new approach to
report design and publishing by integrating familiar desktop word processing tools with
existing Oracle E-Business Suite data reporting. XML Publisher leverages standard, wellknown technologies and tools, so you can rapidly develop and maintain custom report formats.
For more information on XML Publisher, see the Oracle XML Publisher Administration and
Developer's Guide and the Oracle XML Publisher Report Designer's Guide.
If you are using XML Publisher to format and generate your report output then the easiest
method to get report output to your printers is to use the Pasta print driver.
XML Publisher generates PDF output. Typically the PDF must be converted to a format the
printer can understand, such as Postscript (PS) or Printer Command Language (PCL).
Currently XML Publisher does not natively support these output formats and you need to use a
converter to print within the Pasta printing framework.
The flow of command is the concurrent manager calls XML Publisher to create PDF output for
the given report. The output is then sent to the Pasta driver which preprocesses it through a
converter program. Its output is sent to the printer.
Managing Printers
Chapter
CLASSROOM
Using Pasta with XML Publisher
To use a converter, change the Pasta configuration file to call a third party package to convert
the PDF to PS or PCL. Pasta can use a preprocessing command to invoke any executable that
supports an input file and an output file (a filter program). The third party package can be an
open source solutions such as Ghostscript and XPdf.
Pasta invokes the filter program to preprocess the XML Publisher output before passing it to
the printing command. By using the preprocess option, you can generate output formats other
than the formats currently supported by Pasta.
For more information, see the Pasta 3.0.4.0 User's Guide for Release 12 in OracleMetaLink
Note 239196.1.
Managing Printers
Chapter
CLASSROOM
Customization Considerations
You can customize Oracle Applications printer support components to use custom print styles
and custom print programs. For information on how to do customize these components, use
the references below.
Materials Needed
Manual for your specific printer to look up control codes required by a printer type
Installing Oracle Applications for your platform to look up control codes required by an
operating system platform
Oracle Applications System Administrators Guide Configuration
Pasta 3.0.4.0 User's Guide for Release 12 in OracleMetaLink Note 239196.1
Managing Printers
Chapter
CLASSROOM
Other Customization Materials for Oracle Applications Printing
Summary
Managing Printers
Chapter
CLASSROOM

Managing Printers
Chapter
CLASSROOM
Chapter 10
Introduction to Oracle Applications Manager

Chapter
CLASSROOM
Introduction to Oracle
Applications Manager


Chapter
CLASSROOM
Introduction to Oracle Applications Manager (OAM)

Chapter
CLASSROOM
Objectives

Chapter
CLASSROOM
Introduction
Oracle Applications Manager is a system management console. It provides a wide variety of
features related to system management for use by DBAs, System Administrators, and
Technical Support personnel.
Oracle Applications Manager allows you to monitor and control E-Business Suite system
components. It can help you to understand how the performance and availability of those
components affects your business. When problems arise, Oracle Applications Manager
provides a variety of features to help you diagnose and resolve those problems quickly to
reduce any necessary downtime. Oracle Applications Manager helps you manage your system
configuration by enabling you to make and track configuration changes as well as identify
potential configuration problems. Additionally, Oracle Applications Manager helps you track
periodic maintenance activities and facilitates the patching process.
The pre-defined Oracle Applications Manager Administrator Menu is available from the
System Administration responsibility.

Chapter
CLASSROOM
What is Oracle Applications Manager?
Benefits
Oracle Applications Manager provides features to manage all aspects of the Oracle E-Business
Suite.
During system implementation, Oracle Applications Manager automates configuration tasks
and enables you to tighten security on the system. OAM can also help in keeping the system
up-to-date with the latest E-Business Suite patches.
Oracle Applications Manager automates system monitoring, facilitates daily administration,
and helps speed problem resolution.
For maintenance or upgrades, OAM helps identify necessary updates, provides an analysis of
the potential impact of those updates, and delivers tools to facilitate and minimize any required
downtime.

Chapter
CLASSROOM
Benefits of Oracle Applications Manager
OAM Integration Points

OAM integrates with other Oracle products and provides features that manage or extend those
products. For example, the Oracle Workflow Manager within OAM manages Oracle Workflow
functionality. OAM provides the patch history database and patch wizard for AutoPatch. It
provides the context editor for AutoConfig and monitoring for in-progress AutoPatch and AD
Administration tasks. It can download patches from OracleMetaLink and automatically merge
them using AD Merge Patch. It provides management interfaces for Rapid Clone, Generic
Service Management, Oracle Workflow,and other Oracle Applications features. It also
provides access to tests run through Oracle Diagnostics. OAM also provides a way to run
custom SQL scripts (as well as seeded scripts) via the SQL Extensions feature.
Note: The integration of only some of these features will be covered in this course. For more
information on Oracle Workflow Manager, see the course R12 Implement Oracle Workflow".
For more information on using features related to AD Utilities such as AutoConfig, cloning,
Patch Wizard, Timing Reports, see the course R12 Install, Patch and Maintain Oracle
Applications". Also, refer to the following manuals:
Oracle Workflow Administrators Guide
Oracle Applications Maintenance Utilities

Chapter
CLASSROOM
Oracle Applications Manager Integrates with
Oracle Applications Patching Procedures

Chapter
CLASSROOM
Application Management Pack for Oracle E-Business Suite

Application Management Pack for Oracle E-Business Suite extends Enterprise Manager 10g
Grid Control to help monitor and manage an Oracle E-Business Suite system more effectively.
The pack integrates Oracle Applications Manager with Grid Control to provide a consolidated,
end-to-end E-Business Suite management solution.
The Application Management Pack is released and installed separately from the Oracle EBusiness Suite, and is not covered in this lesson. For more information on the Application
Management Pack, see OracleMetaLink Note 394448.1.

Chapter
CLASSROOM
Application Management Pack for Oracle E-Business Suite
Navigation
You can access OAM from the System Administration responsibility or the System
Administrator responsibility. A seeded menu, Oracle Applications Manager Administrator
Menu (OAM_ADMIN_MENU) is available from these responsibilities. In addition, individual
OAM functions can be added to custom menus. Direct links to specific Oracle Applications
Manager features are possible from the E-Business Suite Home Page.
The OAM console includes:
The Applications Dashboard, which includes tabs and a dropdown list for quick access to
commonly-used features
The Site Map, which contains links to all features within OAM
Global buttons/links for setup, the Support Cart, your home page, and online help

Chapter
CLASSROOM
Navigation in OAM
Applications Dashboard
The Applications Dashboard provides a comprehensive summary of the Oracle E-Business
Suite components including:
An overview of configuration changes and the status of infrastructure components
Performance information
Required critical maintenance activities
Diagnostic test results
The status of key business flows
Potential security issues
Software updates
In addition, a dropdown list provides quick access to commonly-used pages and features,
including:
Configuration Overview
Forms Sessions
Database Status

Chapter
CLASSROOM
Applications Dashboard
Applied Patches
Patch Wizard
Workflow Manager

Chapter
CLASSROOM
Site Map
The Site Map provides links to most pages in OAM, in these categories:
Administration
Monitoring
Maintenance
Diagnostics and Repair

Chapter
CLASSROOM
Site Map
Administration

Chapter
CLASSROOM
Monitoring

Chapter
CLASSROOM
Maintenance Features
Patching utilities are available from the Site Map > Monitoring tab. These are described in the
12 Install, Patch, and Maintain Oracle Applications course.
Critical activities are activities that must be run periodically. They are monitored to ensure they
are being run. Examples include refreshing an Employee Directory or purging obsolete data.

Chapter
CLASSROOM
Maintenance
Diagnostics and Troubleshooting

Chapter
CLASSROOM
Setting Up Oracle Applications Manager

Many of the features in OAM require special setup. Use the OAM Setup global link to
navigate to the OAM Setup pages.
Dashboard Setup Enable and set up the frequency and thresholds of metric
collections for the Dashboard. Enable alerts for the status of services.
OracleMetaLink Credentials Define your credentials for accessing
OracleMetaLink.
Business Flows Update or view business flows, either seeded or custom.
Knowledge Base Use this page to retrieve documents from OracleMetaLink.
Concurrent Requests Use this page to set up alerts for concurrent requests,
such as long-running requests or pending requests.
Signon Audit Setup Set up and enable Signon Audit.
Each features setup page is covered in the general discussion of the feature in
another lesson.

Chapter
CLASSROOM
Summary

Chapter
CLASSROOM


Chapter
CLASSROOM
Chapter 11
System Monitoring in Oracle Applications Manager

Chapter
CLASSROOM
System Monitoring in Oracle



Chapter
CLASSROOM

Chapter
CLASSROOM
Objectives

Chapter
CLASSROOM
System Overview
(N) Applications Dashboard > Overview (T)
The Overview tab of the Applications Dashboard provides an overview of the general status of
your system.
Applications System Status
The status of each host is shown.
Platform - the host's operating system.
Host Status indicates whether the host is up or down.
Admin - indicates whether the Admin server has been installed on the host machine.
Database - indicates the status of the database instance installed on the host machine.
Concurrent Processing- indicates the status of the Internal Concurrent Manager and the
services managed by the ICM.
Forms - indicates the status of the Forms Server components: Forms Listener, Metrics
Server, Metrics Client, and OAM Generic Collection Service.
Web - indicates the status of the Apache Web Listener.

Chapter
CLASSROOM
System Status Overview
For the Database column, you can click on the icon(s) in the column to drill down to more
information on the database status.
For Concurrent Processing, you can click on the icon(s) in column to drill down to more details
on the status of concurrent managers and their concurrent processes.
Other regions are discussed on the following slides.

Chapter
CLASSROOM
Configuration Changes
This region shows system-level changes that were made in the last 24 hours. Use this data to
help diagnose sudden changes in the functioning of your applications system.
To see the list of Patches Applied, click on the number to drill down to the Patch Summary
page.
To see the list of Site Level Profile Options, click on the number to drill down to the Site Level
Profile Settings page.
To see the list of Applications Context Files Edited, click on the number to drill down to the
Applications Configuration Parameters page. Changes made to context files can impact your
overall processing configuration and the functioning of business processes.

Chapter
CLASSROOM
System Status Configuration Changes
Web Components Status

This region lists the status of the web components. Status values may be "Up, Down,
"Warning, and Unmonitored.
The status of each Web component is determined by testing the corresponding URL as defined
in the component's Web agent profile option. The Warning status will be displayed if the
profile option is not set. Otherwise, a status of Up or Down will be returned based on the
success of the URL test. The profile options are listed with their corresponding components
below.
PL/SQL Agent - Uses profile option APPS_WEB_AGENT (Applications Web Agent). If
down, you will not be able to log in to any Web-based Self-Service Applications,
including the Personal Homepage. Look for errors or access issues in the Apache logs in
$LOG_HOME/ora/10.1.3/Apache.
Servlet Agent - Uses profile option APPS_SERVLET_AGENT (Apps Servlet Agent). If
down, the Self-Service Framework-based Applications will not function, as well as all
other servlet-based features. Look for errors in the Apache error and access logs above,
and also the mod_jserv log (<iAS_HOME>/Apache/Jserv/logs/mod_jserv.log). Also,
execute the Servlet Ping from the System Administration Diagnostics menu.

Chapter
CLASSROOM
System Status Web Components Status
JSP Agent - Uses profile option APPS_SERVLET_AGENT (Apps Servlet Agent). If

down, execute the JSP Ping from the System Administration Diagnostics menu.
Discoverer (if installed) - Uses profile option
ICX_DISCOVERER_VIEWER_LAUNCHER (ICX: Discoverer Viewer Launcher). If
down, you will not be able to run BIS reports.
Personal Homepage - Uses profile option APPS_SERVLET_AGENT (Apps Servlet
Agent). If down, you cannot log on through the Personal Homepage.
TCF - Uses profile option APPS_SERVLET_AGENT (Apps Servlet Agent). If down, try
running the AOL/J Diagnostic or the Servlet Ping utilities from the System Administration
Diagnostics menu.

Chapter
CLASSROOM
System Alerts
Use the System Alerts region to find out about critical events to your system. Examples of such
events are a halted process or a program that returned an error.
This region lists the number of system alerts in the categories listed below.
If your system is functioning well, there should be no new alerts reported. When an alert of a
particular type first occurs, it is counted as a new alert. It remains new until the status is
manually changed by the administrator. If an alert of the same type occurs again while the
original alert is still in open or new status, it is counted as a new occurrence.
New Alerts - alerts that have not yet been acknowledged by the administrator. An alert is
acknowledged when it is manually moved from a status of "New" to a status of "Open" or
"Closed."
New Occurrences - additional occurrences of alerts that are in new status.
Open Alerts - all alerts that are in an open status. An alert must be manually moved from
the new to open status.
Open Occurrences - all occurrences of alerts that are currently open.
Click on the number for any of these to drill down to the System Alerts and Metrics page.

Chapter
CLASSROOM
System Status System Alerts
(Help) Applied Technology > Oracle Applications System Administration > Maintenance >
Overview of Monitoring Oracle Applications > System Alerts, Metrics, and Logs

Chapter
CLASSROOM
User Initiated Alerts

The User Initiated Alerts region is similar to the System Alerts region. You can define
additional alerts to be raised for events of your choosing. These alerts will be listed in this
region.
This region lists the number of alerts in these categories:
New Alerts - alerts that have not yet been acknowledged by the administrator. An alert is
acknowledged when it is manually moved from a status of "New" to a status of "Open" or
"Closed." See System Alerts for more information.
New Occurrences - additional occurrences of alerts that are in new status.
Open Alerts - all alerts that are in an open status. An alert must be manually moved from
the new to open status.
Open Occurrences - all occurrences of alerts that are currently open.
Click on the number for any of these to drill down to the Alerts and Metrics page.

Chapter
CLASSROOM
System Status User Initiated Alerts
Performance
(N) Applications Dashboard > Performance (T)
Application Tier Hosts
Database Sessions - the number of active database sessions. Clicking the value link returns
a page showing all active database sessions.
Running Requests - drills down to the Search for Requests Results page showing
information on all currently running requests.
Forms Sessions - the number of running Forms sessions. Drills down to the Forms
Sessions page.
- The Forms Sessions page shows information including the following: username,
auditing session ID or AUDSID (from which you can drill down for database session
information), CPU usage, and duration.
- The Active Database Sessions includes the following information - AUDSID,
machine, program, and module.
Service Processes - drills down to the System Activity page. Service processes include all
concurrent manager processes and all processes managed by the ICM. If you have set up

Chapter
CLASSROOM
Performance

Chapter
CLASSROOM
your system to have other services managed by Generic Service Management (GSM),
those services are included as well.
- GSM is an extension of concurrent processing and provides a framework for
managing processes on multiple host machines. With GSM, the Internal Concurrent
Manager manages various service processes across multiple hosts.
Database Instances
Database Sessions - the number of active database sessions. Clicking the value link returns
a page showing all active database sessions.
Running Requests - drills down to the Search for Requests Results page showing
information on all currently running requests.
Forms Sessions - the number of running Forms sessions. Drills down to the Forms
Sessions page.
- The Forms Sessions page shows information including the following: username,
auditing session ID or AUDSID (from which you can drill down for database session
information), CPU usage, and duration.
- The Active Database Sessions includes the following information - AUDSID,
machine, program, and module.
Activity
Services Up - the number of service instances whose target services match the actual
services.
Services Down - the number of service instances whose target services do not match the
actual services.
Unsent Workflow E-mail
Monitoring Critical Activities

(N) Applications Dashboard > Critical Activities (T)
The Critical Activities page allows you to monitor periodic maintenance activities, such as data
purge programs, that are required to keep your system running smoothly.
The information on this page can help you understand historical success rates and gauge the
current needs for purging activity.
From this page you can specify the purge programs you wish to monitor using the Modify
Monitored Program List button. You can specify how frequently they are run using the
Update Frequency button.

Chapter
CLASSROOM
Critical Activities
Critical Activities Setup

Chapter
CLASSROOM
System Alerts, Metrics, and Logs

(N) Site Map > Monitoring (T) > System Alerts [or Logs] (under Current Activity)
The System Alerts, Metrics, and Logs tab pages provide information that can help you
diagnose potential problems. E-Business Suite applications can report these potential problems
as system alerts to Oracle Applications Manager. These alerts can then be tracked in OAM,
and administrators can classify alerts as open or closed, as well as keep notes on the steps taken
to resolve underlying problems.
Alerts
This page shows a summary of the system alerts as well as a list of new alerts.
Alerts are classified by Severity level of Critical (an important business flow is impeded or a
large number of users is affected), Error (a less severe, more isolated issue), or Warning (there
may be a negative impact on users or business processes). Alerts are also marked as New or
Open. "New" indicates that the alert has just been posted in the system. "Open" indicates the
alert is being resolved.
In the Summary region, Alerts are grouped according to their severity and status of New or
Open. The New or Open column indicates how many alerts of the given severity exist. You
can click on the number to drill down to details on the alerts. You can change the state of alerts

Chapter
CLASSROOM
System Alerts, Metrics, Logs

Chapter
CLASSROOM
(along with the associated occurrences) in OAM.. You can also add notes to alerts; for
example, to indicate how the problem was resolved.
Metrics
Not all exception conditions can be immediately detected directly within an Oracle
Applications component, but are best detected through external analysis. Some are detected by
measuring certain criteria, such as decreasing transaction throughput for a component or
excessive completion times for a business process. External analysis allows for easier
comparison of current and historical metric values, consideration of metrics from multiple
products and components., and end-user defined exception triggers. These exceptions are
analogous to "events" in Oracle Enterprise Manager where the use specifies the specific
conditions that will trigger an alert.
Logs
System Logs are general log messages that are logged by the various components in an
Applications System. These log messages can be logged by the developer of the components at
the following levels:
Unexpected
Error
Exception
Event
Procedure
Statement
Database Initialization (init.ora) Parameters

(N) Site Map > Monitoring (T) > Database init.ora Setting (under System Configuration)
This page shows you the database init.ora parameters and their current values for the
installation. You can compare the current values with the recommended values, as well as see
if a given parameter is mandatory. You can also access the current bulletin on OracleMetaLink
on these parameters.

Chapter
CLASSROOM
Database Initialization (init.ora) Parameters
Monitoring Business Flows

(N) Applications Dashboard > Business Flows (T)
Business Flow Monitoring in Oracle Applications Manager helps you to understand the effects
that system component issues and availability have on your business. This type of monitoring
has several benefits. Traditionally, system management tools have focused on monitoring
system components without regard to the effect those components have on the business. This
release of Oracle Applications Manager allows you to look at system issues from a different
perspective, helping you to understand the effects that system issues have on the business,
allowing you to prioritise accordingly. This solution is customisable, allowing you to define
flows specific to your own business, and map those flows to the system components upon
which they depend.
You can monitor system components within the context of the business flows that are
comprised of those components. These components include Oracle Workflow item types,
concurrent programs, forms, Oracle Applications Framework functions, and services. Flows
and sub-flows and their related system components are presented in a hierarchical format,
allowing you to see the ripple effects of a failed component.

Chapter
CLASSROOM
Business Flows

Chapter
CLASSROOM
You can define your own custom business flows. Once you have identified the flows that you
would like to monitor, Oracle Applications Manager allows you to control monitoring at the
flow, sub-flow, and system component levels.
Business Flow Details
When you drill down to the monitoring details for a flow, you see the hierarchical
representation of that flow and the associated system components. For each system component
you can see the number of system alerts, concurrent request errors, and Oracle Workflow work
item errors where applicable. You can drill down on the links for more information on the
individual alerts or errors. Also, you can see that the alert and error statistics are rolled up
through sub-flows and flows to show the ripple effects of each on your business flows.
You can also edit a custom flow. You are able to update the name or description of a flow or
sub-flow, and add or delete a new sub-flow or system component to the hierarchy. This page
allows you to define and edit your custom flows. Your custom flows show as type User
Defined and will have an link in the edit column to take you to the editing page. To create a
new flow, click on the Create button.
See the Oracle Applications System Administrators Guide Maintenance for more
information on business flows.
Monitoring Oracle E-Business Security in Oracle Applications Manager

OAM enables you to monitor failed security tests, posted security alerts, and also provides
links to online security-related documents and notices from Oracle. This page serves as your
starting point for detecting and resolving potential E-Business Suite security issues.
Security threats can come from a variety of sources including poorly configured systems, weak
user passwords, and external attacks. Oracle has developed a set of diagnostics tests that help
detect such conditions on your system. Additionally, you can integrate your own security
related tests tailored for your specific system.
You can schedule security tests to execute periodically. Whenever a security test fails, it posts
a system alert. Other components of the E-Business Suite may also post security-related
system alerts based on certain metrics or events. You can subscribe to be notified via Oracle
Workflow whenever a security related alert is posted. This allows you to continuously monitor
the security of your system, even when you are not in the office. You can be proactively
notified of any potential vulnerabilities that appear. You will be automatically notified of
conditions such as risky configuration changes, sudden increases in login failures, and users
that have been locked out of their accounts. Additionally, if you have a need for security
related tests beyond those provided by Oracle, you can integrate your own tests using Oracle
Diagnostics. Your custom tests can be executed periodically, post alerts, and appear in the

Chapter
CLASSROOM
Monitoring Oracle E-Business Suite Security
Security tab of the Applications Dashboard. For more information, see the Oracle
Applications Supportability Guide.

Chapter
CLASSROOM
Diagnostic Tests for Security

To get the most out of security monitoring, schedule the security diagnostic tests to run
periodically. To do this from Oracle Applications Manager, choose Submit New from the
Concurrent Requests section in the Administration tab of the Site Map. In the request
submission page, choose the Run Diagnostic Tests concurrent program. For parameters,
enter Application Object Library for the Application Name, and EbusinessSecurity for the
Group Name. Leave the TESTNAME field blank to run all of the tests in the group. Later,
when you are familiar with the various tests, you can schedule specific tests to run at different
intervals.

Chapter
CLASSROOM
Monitoring E-Business Suite Security Setup - Diagnostic Tests
Applications Dashboard - Security

(N) Applications Dashboard > Security (T)
Once you have completed the setup, the Security page of the Applications Dashboard serves as
your starting point for detecting and resolving security issues.
The Security Alerts table shows a summary of all of the security related system alerts that have
been posted for failed security diagnostic tests and other events. You can drill down to view
details of the system alerts.
The Security Test Failures table displays recent failures of security related diagnostic tests.
This table includes both tests that were scheduled using the Run Diagnostic Tests concurrent
program and tests that were run manually through Oracle Diagnostics or Oracle Applications
Manager. The test failures are grouped by the severities of Critical, Error, and Warning.
From this table, you can drill down on the Failure Time to obtain the diagnostic test report, or
you can rerun the test by clicking on the icon in the Diagnose column.
The final section of the Security page is the Resources section. This provides links to security
related documents and notices on OracleMetaLink. You can use these links to stay up-to-date
on the latest developments and best practices for E-Business Suite system security.

Chapter
CLASSROOM
Applications Dashboard - Security
Database Status Details

(N) Site Map > Monitoring (T) > Database (under Availability)
This page displays details on the database. Form more information on the entities listed, refer
to the Oracle database documentation.
Instance Status
Wait Events
Memory Statistics
System Statistics
Tablespaces and Status
Rollback Segments and Extents

Chapter
CLASSROOM
Database Status Details
Application Services
(N) Site Map > Administration Tab > Application Services > Generic Services
You can configure, monitor, and control application services from the System Activity page for
services. These services are managed under Generic Service Management (GSM). GSM
allows you to manage a variety of services using a fault-tolerant framework. The Application
Services lets you drill down to details for instances of each service and view the instances'
statuses and processes.

Chapter
CLASSROOM
Application Services
Monitoring Forms

Chapter
CLASSROOM
Forms Runaway Process Detection

(N) Site Map > Monitoring (T) > Forms Runaway Processes (under Current Activity)
The Forms Runaway Process Detection feature can help you reduce wasted system resources
by proactively notifying you when Forms runtime processes cross the thresholds that you set.
For potential runaway processes, Oracle Applications Manager provides critical details such as
the Oracle E-Business Suite user that owns the process. This data allows you to more
efficiently collect the information that you need for deciding on whether or not to kill a
process. If you do decide to kill a process, then it can be done directly from within Oracle
Applications Manager.
The term runaway process refers to processes that are no longer serving their intended
purpose or are consuming an inordinate amount of resources. Oracle Applications Manager
can now help you detect Forms runtime processes that have likely become runaways. You can
set thresholds for memory usage, CPU usage, and elapsed runtime, and be alerted if any Forms
runtime process crosses these thresholds. Additionally, Oracle Applications Manager can
detect Forms runtime processes that have continue to run even though they have lost their
database connections.

Chapter
CLASSROOM
Forms Runaway Processes

Chapter
CLASSROOM
When a potential runaway process is detected, a System Alert will be posted. As with any
system alerts, you can subscribe to receive notifications via Workflow, so that you dont have
to keep checking back in Oracle Applications Manager for new alerts.
Oracle Applications Manager provides you with a list of the possible runaway processes, and
gives you the option of terminating individual processes once you have confirmed that they are
indeed runaways.
Forms Runaway Processes Page
The Forms Runaway Processes page allows you to configure the thresholds for the feature, and
view the current list of potential runaway processes. Here you can set the values for the
maximum amount of memory that a process should allocate, the maximum percentage of
server CPU that a process should consume, and the maximum amount of time that a process
should every stay alive.
When a runaway process is discovered, a system alert will be posted, and the process will
appear in the table. The table will list middle tier details, including host, PID, memory size,
CPU percentage, and total runtime. You can also see the E-Business Suite user who owns the
process, and the IP address of the client connected to the process.
Once you have confirmed that a process is truly a runaway, you can use the Terminate button
to kill the process.
Forms Sessions
(N) Site Map > Monitoring (T) > Forms Sessions (under Performance or Current Activity)
This page shows information on the current forms sessions. Every open form has its own
database session, or "Forms session." The profile option "Sign-On:Audit Level" should be set
to 'Form' to use this feature. If this profile option is not set to 'Form', the Forms Sessions table
will show an empty table even when there are active forms sessions.
The following data is shown for each session:
Form Name
AUDSID - The auditing session ID. Click on the value to drill down to the Database
Session information page.
RTI_PID - The runtime instance process ID. Click on the value to drill down to the Forms
Sessions for Process ID page.
Username
Responsibility
Application

Chapter
CLASSROOM
Forms Sessions

Chapter
CLASSROOM
LRs (Session Logical Reads) - Input/output (I/O) is one of the most expensive operations
in a database system. SQL statements that are I/O-intensive can monopolize memory and
disk use and cause other database operations to compete for these resources. To prevent
single sources of excessive I/O, Oracle lets you limit the logical data block reads per call
and per session. Logical data block reads include data block reads from both memory and
disk. The limits are set and measured in number of block reads performed by a call or
during a session.
PRs (Physical Reads) - The total number of data blocks read from the disk for the session.
CPU
PGA (Session Program Global Area memory) - The PGA is a memory buffer that contains
data and control information for a server process. A PGA is created by Oracle when
a server process is started. The information in a PGA depends on the configuration
of Oracle.
UGA - User Global Area memory used by the session.
Duration - in HH:MM:SS
Click on the Session Details button or the AUDSID to view database information for the
selected forms session.
Use the Diagnostics ON/OFF button to turn on or off the Forms Runtime Diagnostics (FRD)
for the runtime process.
Forms Sessions for Process ID
If you click on the RTI_PID from the Forms Sessions page, or if you click on the PID from the
Forms Runtime Processes page, you will see the fields described above as well as the
following data for the Process ID:
Client IP Address
Server Host Name
CPU Time
Memory Usage (KB)
Diagnostics (On/Off)
Log File Name
Forms Runtime Processes

(N) Site Map > Monitoring (T) > Forms Runtime Processes (under Performance or Current
Activity)
This page shows information about Forms runtime processes. You must first register and start
a service instance of the OAM Generic Collection Service to collect this information. The
Generic Collection Service must be running for the information to be collected.
The following columns are shown for each session:
PID - The ID of the runtime process for the user session. Click this value to drill down to
the Forms Sessions for Process ID page.
Node
Port - The Apache port of the servlet listener, if any.
Memory (KB) - The memory used by the runtime process in kilobytes. For HP and AIX
platforms, this is the virtual memory size. For all other platforms, this is the resident set
size.
CPU
Duration

Chapter
CLASSROOM
Forms Runtime Processes

Chapter
CLASSROOM
Client IP Address - The IP address of the client machine used to connect to the Forms
Services.
Username - The database username used by the Forms application for the user session.
Diagnostics - On/Off
Last Update Time
Click on the Sessions button or click on the PID to view the Forms Sessions for Process ID
page.
This page also shows the runtime processes from the Forms Servlet Listener, if any. The Port
column for such processes indicates the Apache Listener port.
Forms Listener versus Forms Listener Servlet
The Forms Listener is a process running on a specific port on the server machine. When the
connection between the client and the Forms runtime process is established, the client and the
runtime process requires that the connection be persistent.
The Forms Listener Servlet is a Java servlet running in a servlet engine. The Web server routes
the client requests for the Forms Listener Servlet directly to the servlet instance. Because the
web server acts like the end point for the client, the other server machines and ports are no
longer exposed to the firewall.
In the Forms Runtime Processes page, the node name and the port are shown for each runtime
process. You can distinguish between the Forms Listener process and Forms Listener Servlet
process by examining the port numbers. For the Forms Listener process, the port is the Forms
server machine port. For the Forms Listener Servlet process, the port is the web server port.
Host Management
(N) Site Map > Administration (T) > Hosts (under System Configuration)
Oracle Applications Manager provides a list of host machines that are employed by the
Applications and Database Tiers of the E-Business Suite system. For each host, you can view
the host status, and you can drill down to see the status of the individual E-Business Suite
processes on that host. You can also view the E-Business Suite configuration details for that
specific host, including the installed server types, and port allocations.
Oracle Applications Manager allows you to change the state of a given host to make that host
available or unavailable to Generic Service Management (GSM). Under GSM, the Internal
Concurrent Manager manages the various service processes across multiple hosts. If you need
to take a host down for maintenance, you can first mark that host as offline in OAM, which
will ensure that concurrent mangers and other service processes are migrated to a secondary
node as appropriate. Later, when you set the node back to online, the processes will be
migrated back.
The new host-oriented interfaces allow you to track more easily which service processes are
running on which hosts, and you can more easily identify the services that would be affected
by a planned or unplanned outage for the host. For planned outages, OAM enables you to

Chapter
CLASSROOM
Host Management

Chapter
CLASSROOM
prevent Generic Service Management processes such as concurrent managers from running on
an offline host without reconfiguring the service definitions.
The Hosts page lists all the hosts that are running components of your Applications and
Database tiers. For each host, the current state and status is given. The status indicates
whether or not the host and the E-Business Suite system processes for that host are up and
running.
The Applications Processes tab of the Host Status page lists the individual Generic Service
Management processes that are running on that host. In most cases, you are also able to see the
database session AUDSID associated with the process. You can drill down on the Application
tier process ID to view more information about the process and obtain the log file for the
process. You can drill down on the database session AUDISD to find session statistics,
current SQL, and control SQL tracing for the database session.
You can update the the state to one of three values. A state of Online means that Generic
Service Management processes such as concurrent managers are able to run on the host. If
you want to make the host unavailable to Generic Service Management temporarily, then you
can change the state to Offline. You can later change the state back from Offline to
Online. The third state, called Disabled is used to remove a host from use by the system.
The primary difference between Disabled and Offline is that a disabled host will be
removed from many system management views and status checks. A disabled host is no
longer considered to be part of the system, whereas an offline host is considered to be a
temporarily unavailable part of the system.
From the Hosts page, you can drill down to a more detailed view of the status of a given host,
or to a configuration summary for a host.
The Applications Services tab on the host status page shows a summary of the E-Business
Suite services on the host. This summary is rolled up by server type. For each service type
shown you can drill down to a more detailed view of individual services, and also the the pages
where you can control services running under Generic Service Management.
The Applications Processes tab on the host status page lists the individual Generic Service
Management processes that are running on that host. In most cases, you will also be able to
see the database session AUDSID associated with the process. You can drill down on the
Application tier process ID to view more information about the process and obtain the log file
for the process. You can drill down on the database session AUDISD to find session statistics,
Host Management - Status

The Applications Services tab on the host status page shows a summary of the E-Business
Suite services on the host. This summary is rolled up by server type. For each service type
shown you can drill down to a more detailed view of individual services, and also the the pages
where you can control services running under Generic Service Management.
The Applications Processes tab on the host status page lists the individual Generic Service
Management processes that are running on that host. In most cases, you will also be able to
see the database session AUDSID associated with the process. You can drill down on the
Application tier process ID to view more information about the process and obtain the log file
for the process. You can drill down on the database session AUDISD to find session statistics,

Chapter
CLASSROOM
Host Management - Status
Host Management - Configuration

The configuration summary shows the different server types installed on that host. These
include Database, Administration, Concurrent Processing, Forms, and Web. The page also
shows a summary of the ports in use by the E-Business Suite on that host. You can press the
Edit Configuration button to edit the AutoConfig parameters for this host.

Chapter
CLASSROOM
Host Management - Configuration

Many of the features described in this chapter require special setup. Use the OAM Setup
global link to navigate to the OAM Setup pages.
Dashboard Setup Enable and set up the frequency and thresholds of metric collections
for the Dashboard. Enable alerts for the status of services.
OracleMetaLink Credentials Define your credentials for accessing OracleMetaLink.
Business Flows Update or view business flows, either seeded or custom.
Knowledge Base Use this page to retrieve documents from OracleMetaLink.
Concurrent Requests Use this page to set up alerts for concurrent requests, such as longrunning requests or pending requests.
In addition, the Signon Audit Setup page is used to enable Signon Audit.

Chapter
CLASSROOM
Dashboard Configuration and Alerting Setup

The metrics shown in the Applications Dashboard are periodically collected by a concurrent
program called the OAM Dashboard Collection Program (short name FNDOAMCOL). The
periodic collection of data allows the Applications Dashboard to show automatically important
system metrics. You can control the frequency of the collections as well as enable or disable
the collection of individual metrics.
You can also configure alerts to trigger when potential system issues arise. You can be notified
of services that are found to be in a specific status, or metrics that have met conditions that you
specify.

Chapter
CLASSROOM
Dashboard Configuration and Alerting Setup
Dashboard Setup
(N) Setup > Dashboard Setup > Update (B)
The landing page from the Setup is the Dashboard Setup page. View the current collection and
alerting settings here. To update these, click on the Update button.
OAM Dashboard Collection Interval
Specify how frequently the collection program should be run.
Metrics Setup
Enable or disable the collection of individual metrics by checking or un-checking the box in
the Enable Collections column.
- If you would like to enable alerts for a given metric, check the appropriate box in the
Enable Alerts column.
- To set the alert condition, you can choose either less than, equal to, or greater
than from the Threshold Operator column, and then enter the desired value in the
Threshold Value column. Click on the Next button to move to the configuration of
monitoring services.
Service Monitoring

Chapter
CLASSROOM
Setting Up Dashboard Configuration and Alerting

Chapter
CLASSROOM
To enable monitoring for any specific service, check the appropriate box in the Enable
Collection column.
You can set up alerts for a given service by checking the Enable Alerts box, and then
choosing the status that you want in the Threshold Value column.
Alert Notification
Alerts flag events that may need your attention.
The OAM Dashboard Overview tab has a System Alerts region, from which you can drill
down to see any new or open alerts (types of alerts) or occurrences of alerts.
Notifications of alerts can be sent out to users via the Notifications Setup button on the
System Alerts page.
For metrics that are displayed in the OAM Dashboard, when metric exceeds a threshold that
you have set, a warning icon will appear next to that metrics value.
OracleMetaLink Credentials Setup

(N) Setup (B) > MetaLink Credentials
You can access OracleMetaLink documents through links in Oracle Applications Manager. For
example, key security-related documents are linked from the Security tab in the Applications
Dashboard.
To set up your credentials for OracleMetalink, from the Setup page, navigate to the Update
MetaLink Credentials page and enter in your OracleMetaLink user ID, password, and e-mail
address.

Chapter
CLASSROOM
OracleMetaLink Credentials Setup
Knowledge Base Setup

(N) Setup (B) > Knowledge Base Setup
Use this page to submit a concurrent request for the Knowledge Base Catalog Refresher
program to retrieve the latest documents from OracleMetaLink (You must have entered in your
OracleMetaLink credentials first).

Chapter
CLASSROOM
Knowledge Base Setup
Concurrent Requests Setup

From this page you can enable alerting for concurrent requests that have been running or
pending for a long time. You can specify the thresholds for which request must reach before
alerts are raised.
Specifically, you can enable the system to do the following:
Raise a general alert for any long-running requests, for any concurrent program.
Raise an alert for a long-running request for a specific program.
Raise a general alert for any requests that have been pending for a long time, for any
concurrent program.
Raise an alert for a request for a specific program that has been pending for a long time.
Raise an alert for a request that has waited longer than a specified time after its requested
start time.

Chapter
CLASSROOM
Concurrent Requests Setup
Signon Audit Setup

Use this page to enable Signon Audit. Select the Enable Auditing button to set the Sign-On:
Audit Level profile option to FORM. Selecting the Disable Auditing button sets the SignOn: Audit Level profile option to NONE.
Use the Enable Alerting/Disable Alerting buttons to turn on/off alerting if the Sign-On:
Audit Level profile option is set to something other than FORM.

Chapter
CLASSROOM
Signon Audit Setup
Summary

Chapter
CLASSROOM


Chapter
CLASSROOM
Chapter 12
Diagnostics and Troubleshooting with Oracle Applications Manager

Chapter
CLASSROOM
Diagnostics and
Troubleshooting with Oracle


Chapter
CLASSROOM
Oracle Applications Manager - Diagnostics and Troubleshooting

Chapter
CLASSROOM
Objectives

Chapter
CLASSROOM
Introduction
Oracle Applications Manager provides features to help you diagnose and resolve system issues.
Oracle Applications Manager integrates with Oracle Diagnostics to provide access to a large
library of diagnostic tests for system technologies, E-Business Suite products, and business
flows.
Oracle Applications Manager also controls Oracle Applications Logging. When issues arise
on your system, you can configure logging to write varying levels of diagnostic information for
specific components into a central repository. Oracle Applications Manager allows you to
view and manage the information logged into this repository.
If you encounter a problem in the system, you can first try to diagnose the problem using
Oracle Diagnostics. Then you can try to correct the problem using the Troubleshooting
Wizards.
Also, if you are unable to diagnose and resolve problems yourself, then Oracle Applications
Manager makes it easier for you to communicate with Support. The Support Cart has been
improved to provide automated collections of the data that Oracle Support requires for
resolving issues.

Chapter
CLASSROOM
Diagnostics and Troubleshooting in Oracle Applications Manager
For more information on Oracle Diagnostics and Oracle Applications Logging, see the Oracle
Applications Supportability Guide.

Chapter
CLASSROOM
Applications Dashboard Diagnostics

(N) Applications Dashboard > Diagnostics (T)
The OAM Applications Dashboard Diagnostics tab provides a summary of the diagnostic tests
that have been run on the environment. From this page, you can:
View results from executed tests
Run Troubleshooting Wizards
Schedule requests to run tests, and view such requests
Configure Diagnostics
- Register applications with Oracle Diagnostics (through Diagnostics Setup)
- Manage users and roles with access to Oracle Diagnostics (through Diagnostics
Configuration)
- View Diagnostics reports
Oracle Diagnostics enables the creation and execution of diagnostic tests. With Oracle
Diagnostics, you can execute tests to help prevent and troubleshoot problems. You can create
your own diagnostic tests. You can be alerted automatically when problems occur through

Chapter
CLASSROOM
Applications Dashboard - Diagnostics
Oracle Diagnostics. For more information on Oracle Diagnostics, see the Oracle Applications
Supportability Guide.

Chapter
CLASSROOM
Troubleshooting Wizards
(N) Applications Dashboard > Diagnostics (T) > [links under Troubleshooting Wizards region]
Troubleshooting Wizards are available for the following:
Concurrent Manager Recovery - Use this wizard when the Internal Concurrent Manager
fails to start.
Service Infrastructure - Using the Service Infrastructure diagnostic wizard, you can
examine existing Generic Service Management data to determine potential problems, and
update the data to eliminate the issues. An example of a potential problem is an active
node without a service manager.
GCS and Forms Monitoring - The GCS and Forms Monitoring wizard helps you
troubleshoot the OAM Generic Collection Service. The GCS, or Generic Collection
Service, is a service managed by Generic Service Management. It performs file
uploading, signaling, purging, and other management tasks for other service runtime
processes such as the Forms Listener runtime process.
CP Signature - This wizard collects information regarding the current status of concurrent
processing on the system.

Chapter
CLASSROOM
Troubleshooting Wizards
Dashboard Collection - The OAM Applications Dashboard Collection program gathers

information on the system that is displayed on the Dashboard under the Overview and the
Performance tabs. This wizard provides a summary of the information regarding its data
collection.

Chapter
CLASSROOM
Concurrent Manager Recovery

Use this wizard when the Internal Concurrent Manager fails to start. This wizard walks you
through several steps that must be completed before restarting the Internal Concurrent
Manager.
Active Managers with a Database Session - these managers must be stopped before
restarting the Internal Concurrent Manager. You may want to wait for any running
requests to complete first.
Managers Deemed Active but without a Database Session - Any processes listed here
must be terminated before continuing. Because these processes have lost their database
sessions, they must be manually terminated from the command line. Refer to your
operating system documentation for instructions on terminating a process from the
command line.
Reset Conflict Resolution - This step lists requests that are waiting for conflict resolution.
Click the Reset button to reset the listed requests for conflict resolution. This action
changes requests that are in a Pending/Normal phase and status to Pending/Standby. Click
the Refresh icon to verify that all requests have been reset.

Chapter
CLASSROOM
Concurrent Manager Recovery Wizard
Requests that are Orphaned - This page lists the requests that do not have a manager. If
any requests have Active Sessions listed, drill down on the session ID and terminate the
session from the Database Session Details screen. Return to the Concurrent Manager
Recovery screen and click the Refresh icon to verify that the session is no longer active.
After you have completed the steps for the above conditions, a summary page is shown listing
the information collected from them. After reaching this page, you should be able to restart
your Internal Concurrent Manager.

Chapter
CLASSROOM
Service Infrastructure
This wizard will list the potential issues with your Generic Service Management setup,
including:
Active nodes without a service manager
Active Concurrent Processing nodes without an Internal Monitor
Service managers without active nodes
Active nodes with inactive service managers
Enabled service instances without workshifts
Nodes that do not have names in uppercase (for service instances)
Nodes that do not have names in uppercase (for processes)

Chapter
CLASSROOM
Service Infrastructure Wizard
Generic Collection Service (GCS) and Forms Monitoring Wizard

This wizard helps you troubleshoot the OAM Generic Collection Service. The OAM Generic
Collection Service is managed by Generic Service Management and performs file uploading,
signaling, purging, and other management tasks for other service runtime processes such as the
Forms Listener runtime process.
The Internal Concurrent Manager must be up and running before this wizard can be run.
The steps within this wizard are:
If necessary, register the OAM Generic Collection Service on all listed nodes.
If necessary, enable the OAM Generic Collection Service on all listed nodes.
If necessary, activate the OAM Generic Collection Service on all listed nodes.
View the registration of the Forms Listener.
If necessary, enable the Forms Listener on all listed nodes.
If necessary, set the Sign-On Audit level to "FORM".
View a Summary page where you can view a log file and add files to the Support Cart if
necessary.

Chapter
CLASSROOM
Generic Collection Service (GCS) and Forms Monitoring Wizard
CP Signature Wizard
The CP Signature wizard collects technical information on Concurrent Processing. This
information is what is most commonly requested by Oracle support analysts, and includes
items such as important configuration settings, code levels, and log files.
This wizard collects information on the following:
Configuration status for Parallel Concurrent Processing, Real Application Clusters, and
Generic Service Management
Registered nodes
Concurrent processing package versions
Concurrent processing package errors
Concurrent processing profile options
Service instances that could be managed by concurrent processing
Concurrent processing processes
Request processing manager specialization rules
Request Conflict Resolution
Concurrent request processing statistics

Chapter
CLASSROOM
CP Signature
Recent requests to run the Purge Concurrent Request and/or Manager Data program
Each step of the Wizard collects a specific set of information listed above. At each step, you
have the option of adding the information to the Support Cart. However, you may want to
wait until the end of the wizard to do so, because at the end you will be presented with a
summary page that shows all of the collected information from all steps, which you can add to
Support Cart all at once. Also note, that you can skip to the summary early by pressing the
Finish button. However, the Summary will only contain the information collected by the steps
that you have executed so far. So, unless told otherwise by Support, you should progress
through every step using the Next button.

Chapter
CLASSROOM
Dashboard Collection Wizard

This wizard collects relevant data concerning the OAM Applications Dashboard Collection
program. Oracle Applications Manager uses this concurrent program to gather the information
displayed on the Applications Dashboard. This wizard collects information regarding the data
collected by this program, including:
Request statistics for the program; for example, how often the Dashboard Collection
program is schedule to run.
Program definition.
Related profile options, if any.
Version information on any Applications Dashboard-related files.
Version information of any Applications Dashboard-related packages.
Information on the live database sessions for the Dashboard Collection program, if any.
Metrics setup information.
Service instances setup information.

Chapter
CLASSROOM
Dashboard Collection Wizard
Support Cart
The Support Cart feature allows you to save Oracle Applications Manager pages with their
data and then zip them up in a file to send to Oracle Support. Oracle Support can then view
your pages in the Oracle Applications Manager display format.
When you click the Add to Support Cart global button, the page is added to the Support Cart.
If you have filtered or sorted the data, your manipulated view is submitted. To view the
contents of the Support Cart, click the Support Cart global button.
Description
You can enter in a TAR number and description of the issue here.
Applications Signature
The Support Cart can collect a standard set of information regarding your E-Business Suite
system. Oracle Support requires this information when logging a technical assistance request
(TAR).
To collect this information, click Collect.
The set of information collected includes:

Chapter
CLASSROOM
Support Cart

Chapter
CLASSROOM
Product Information For each product, the version, current patch level, and status (for
example, Installed) is shown.
Database parameters The init.ora parameter settings.
Patches For each individual patch applied, the patch number, type (for example, Patch
Set or Maintenance Pack), and application timestamp is shown.
Topology - This page includes data about all the nodes of the applications infrastructure.
For each node, the system collects information about the operating system and the
different services running on that node.
Database version
You can specify to include or exclude output and log files for specific nodes as well.
Other Information Collected
Pages that you save using the Add to Support Cart button are listed under this tab.
Summary

Chapter
CLASSROOM
Chapter 13
Managing Concurrent Programs and Reports

Chapter
CLASSROOM
Managing Concurrent
Programs and Reports


Chapter
CLASSROOM
Managing Concurrent Requests

Chapter
CLASSROOM
Lesson Aim
An important area of security involves controlling access to reports and other concurrent
programs. This level of security is provided by request group definitions. This lesson shows
how the system administrator creates and uses these request groups.
Request sets are similar to request groups in that they are both collections of programs along
with their parameters and options. Request sets can be created by users, but they are still
managed by the system administrator.

Chapter
CLASSROOM
Objectives
Objectives

Chapter
CLASSROOM
Concurrent Requests, Programs, and Managers

Concurrent processing allows long-running, data-intensive programs to run simultaneously
with online operations.
Oracle Applications programs can run concurrently with each other as well as with other
programs; they are referred to as concurrent programs.
Requests to run Oracle Applications programsfor example, to run an Oracle General
Ledger reportare concurrent requests. Each concurrent request inserts a row into a
database table maintained by the Oracle Application Object Library.
Concurrent managers read requests from the requests table and start concurrent programs.

Chapter
CLASSROOM
Concurrent Requests, Programs, and Managers
Business Needs for Concurrent Processing

Chapter
CLASSROOM
Business Needs for Standard Request Submission

Chapter
CLASSROOM
Concurrent Processing Definitions

Concurrent Request
A concurrent request is a request that you submit to run a concurrent program as a concurrent
process. You issue a concurrent request when you submit a report or program to run using
Standard Request Submission (SRS) or when you click an action button in a product-specific
submission window.
Concurrent Manager
A concurrent manager is a component of concurrent processing that monitors and runs
requests without tying up your computer.
Request Set
A request set is a collection of reports or programs that you group together. You submit the
reports or programs in a request set all at once, using one transaction.
Stage
A stage is a component of a request set used to group requests within the set. All requests in a
stage are run in parallel, while the stages themselves are run sequentially in the request set.

Chapter
CLASSROOM
Definitions
Concurrent Processing Definitions (continued)

Parameter
In SRS, a parameter is a report variable whose value you can change each time you run a
report. For example, you might run an account balance report and change the account number
whenever you run the report. The account number is the parameter for the report.
Concurrent Processing Options
You can control and change certain run options for each of your concurrent requests. Not only
can you control and change the number of copies to print, which print style to use, and which
printer to use, but you can also choose to hold a request from being run, choose a specific date
or time to start a request, or choose to save the results of your concurrent request in a standard
file format.
Online Request Review
You can review the output and log files from your concurrent requests online. You can see the
results of a concurrent request without the delay of printing out the entire report or log file.

Chapter
CLASSROOM
Definitions
Using Standard Request Submission (SRS)

Using Standard Request Submission gives you control over how you can run your requests and
request sets.
There are three elements involved in submitting a request: selecting the request or request
set to be submitted, defining a submission schedule, and providing completion options.
Defining a schedule can be as simple as submitting As Soon as Possible, or it can involve
using a more complex schedule that you define when you first submit your request. This
schedule can then be used for other requests in the future.
Completion options enable you to deliver notification to others using Oracle Workflow, as
well as specifying which printers and how many copies of the output you want to produce
for each request.
You can submit as many requests as you like from the Submit Request window. You can
even submit a request more than once if you want to run the same request with different
parameter values.

Chapter
CLASSROOM
Submit Request Flow
Submit a New Request

(N) Requests > Run
The responsibility you are using determines the request group and the requests that will appear
in the list of available requests.
Note: Requests can also be run within Oracle Application Framework; for example, navigate
to System Administration responsibility > Schedule Requests.

Chapter
CLASSROOM
Submit a New Request
Using the Parameters Window

Chapter
CLASSROOM
Submitting Requests
(N) Concurrent > Requests > Submit a New Request > (B) Schedule...
The Schedule Window
The scheduling window provides you with several scheduling options. You can choose to reuse
a schedule you previously defined and saved, or define a new schedule. You can define your
schedule to run a request as soon as possible, at a specific time, or repeatedly at specific
intervals, or on specific days of the week or month.
When saving your schedule you must provide a unique name. You can also provide additional
information in the Description field.

Chapter
CLASSROOM
Defining a Submission Schedule
Define Submission Schedule (continued)

(N) Concurrent > Requests > Submit a New Request > (B) Schedule...

Chapter
CLASSROOM
Defining a Submission Schedule
Submitting Requests
(N) Concurrent > Requests > Submit a New Request > (B) OK > (B) Options...

Chapter
CLASSROOM
Defining Completion Options
Request ID

Chapter
CLASSROOM
Reprinting a Report
The Find Requests Window appears when you navigate to (N) Requests > View.
Note: The Profile Option Concurrent:Save Output must be set to Yes.

Chapter
CLASSROOM
Reprinting a Report
Use the Requests Window to View and Change Requests

Chapter
CLASSROOM
How to Use the Requests Window

Display the Find Requests window by navigating to (N) Requests > View.

Chapter
CLASSROOM
How to Use the Requests Window
Using the Requests Window

Chapter
CLASSROOM

In order to use the View Output button, your program must have paper output. If the report file
format you selected for your request has multiple MIME types associated with it, clicking the
View Output button will display a window prompting you to select the MIME type you wish to
use to view your output.
For more information on associating file formats with MIME types see:
(Help) Applied Technology > Oracle Applications System Administration > Maintenance >
Managing Concurrent Processing and Concurrent Programs > How to View Request Status and
Output > Defining the Reports Viewer

Chapter
CLASSROOM
Use the Viewer Options Window to Define MIME Types

(N) Install > Viewer Options
You can use one MIME type to view reports of a certain format. For example, you can view all
text format reports in Microsoft Word. MIME types for supported formats for a particular user
are set by several profile options. Seeded MIME types are:
Viewer: Application for HTML
Viewer: Application for PCL
Viewer: Application for PDF
Viewer: Application for PostScript
Viewer: Application for Text
Viewer: Application for XML
The MIME type selected for a users report is sent to a browser window when the user views a
report of that file format.

Chapter
CLASSROOM
Viewer Options Window
Canceling a Request That Has Not Yet Completed

(N) Requests > View (B) Find
If you cancel a request set, then Oracle Applications automatically cancels all requests in the
set.

Chapter
CLASSROOM
Canceling a Request
Holding a Request That Has Not Started Running

Only requests that have not started running can be put on hold.

Chapter
CLASSROOM
Holding a Request
Changing Request Option

Note: You can change the following only if the request or request set is Pending or
Scheduled:
- Start Date and Time
- Printer and number of copies
- Save output
- Resubmission options

Chapter
CLASSROOM
Changing Request Options
Four Phases of a Concurrent Request

The system administrator must periodically review the status of Oracle Applications programs
to determine a particular requests status in its lifecycle. A concurrent request has a lifecycle of
either three or possibly four phases:
Pending: The request is waiting to be run.
Running: The request is running.
Completed: The request has finished execution.
Inactive: The request cannot yet be run.

Chapter
CLASSROOM
Four Phases of a Concurrent Request
Pending Phase
A program in the Pending phase can be in one of four statuses:
Normal: The program is waiting for an available manager.
Waiting: A child program is waiting for a parent to mark it ready to run.
Standby: A program is waiting for another incompatible program in the same logical
database to complete.
Scheduled: A programs scheduled start time has not yet elapsed.

Chapter
CLASSROOM
Pending Phase
Running Phase
A program in the Running phase can be in one of four statuses:
Normal: Program is in progress.
Paused: A parent program is waiting for one or more child programs to complete.
Resuming: A parent program is continuing after the completion of one or more child
programs.
Terminating: The program is being terminated.

Chapter
CLASSROOM
Running Phase
Completed Phase
A program in the Completed phase can be in one of five statuses:
Normal: Program completed successfully.
Warning: Program completed successfully but with warning messages.
Error: Program failed to complete successfully.
Terminated: A running program was terminated.
Canceled: A pending or inactive program was canceled before it started.

Chapter
CLASSROOM
Completed Phase
Inactive Phase
A program in the Inactive phase can be in one of three statuses:
Disabled: The requested program has not been enabled for execution.
On Hold: The requested program has been placed on hold.
No Manager: There is no manager defined to run this type of request.

Chapter
CLASSROOM
Inactive Phase
Monitoring Privileges of the System Administrator

The system administrators privileges extend beyond those of the end user. The system
administrator can perform all the operations shown on the slide. However, the system
administrator cannot view the actual output of another users report.

Chapter
CLASSROOM
System Administrator Monitoring Privileges
Log File Descriptions

Request Log: When a user submits a request in Oracle Applications, a concurrent manager
processes the request and creates a diagnostic log file. Request Log files document the
execution of a concurrent program running as the result of a concurrent request. The file
contains the program parameters, the start and completion times, and any error messages. Both
the user and the system administrator can access this file.
Manager Log: Manager Log files document the performance of a concurrent manager that is
running a request. The Manager Log lists each request processed by this manager in
descending order by start date and time. This file is accessible by both the user and the system
administrator.
Internal Manager Log File: This file documents the performance of the Internal Concurrent
Manager. It displays parameter values that are loaded when the Internal Concurrent Manager is
started (STARTMGR command) and records the time that each concurrent manager is started
and when each process monitor session (or PMON) cycle is initiated. During each PMON
cycle, the Internal Concurrent Manager verifies the correct operation of each defined
concurrent manager. Only the System Administrator can access the Internal Concurrent
Manager Log file.

Chapter
CLASSROOM
Review Log Files
Managing Log Files and Tables

Purging Log Data: Eventually the tables holding log information consume disk space with
data that may no longer be of use to you. To conserve disk space, you should periodically
delete Oracle Applications log files and output files. Your companys MIS department and
application users should agree on an archiving and file retention policy appropriate for your
organization.
Use the Purge Concurrent Request and/or Manager Data program to purge Request Log files,
Concurrent Manager Log files, and report output files from your product directories maintained
by the operating system, as well as records from Application Object Library tables that contain
history information about concurrent requests and concurrent manager processes.
Scheduling Purge Submissions: Run the Purge Concurrent Request and/or Manager Data
program once and automatically resubmit the program to run at specific time intervals. Use the
Parameters window to specify various criteria with which you can control the timing and
frequency of program execution.
Loss of Audit Data: Be aware that purging concurrent request information loses audit details
used by the Sign-on Audit Concurrent Requests Report.

Chapter
CLASSROOM
Managing Log Files and Tables
Results of Purge Requests

The slide shows the database tables and the operating system files affected by a purge request.
On the Parameters form of the Purge Concurrent request and/or Manager Data program, you
can specify that either request data (Entity=Request) or manager data (Entity=Manager) be
purged. The slide shows the effects of the different requests.
Database Table Descriptions
FND_CONC_REQUEST_ARGUMENTS: This table records arguments passed by the
concurrent manager to each program it starts running.
FND_RUN_REQUESTS: For submitted report sets, this table stores information about the
reports in the report set and the parameter values for each report.
FND_CONCURRENT_REQUESTS: This table contains a complete history of all
concurrent requests.
FND_DUAL: This table records when requests do not update database tables.
FND_CONCURRENT_PROCESSES: This table records information about Oracle
Applications and operating system processes.

Chapter
CLASSROOM
Purge Request Results
Grouping Concurrent Programs and Requests

Grouping concurrent programs and other requests together allows you to control access and
streamline processing. In Oracle Applications, you group programs and requests into request
groups and request sets.
Request Groups
A request group is a collection of reports and other concurrent programs. You use request
groups to implement security at the responsibility level. Request groups are normally
associated with a responsibility, in which case they are referred to as request security groups.
Any user of a responsibility has access to the reports in that responsibilitys request security
group.
Additionally, you can define a request group to have an access code. You can then define the
form so that it allows users to select only those reports or concurrent programs belonging to a
request group with an assigned code.
Request Sets
A request set is a collection of concurrent programs set up to run in a specified sequence from
a single transaction. Request sets can also have run and/or print options, which apply to every

Chapter
CLASSROOM
Grouping Concurrent Programs and Requests
member of the set. Programs in a request set can share parameters; therefore a parameter value
needs to be entered only once for multiple programs. Any user can create a request set.

Chapter
CLASSROOM
Request Group Creation

(N) Security > Responsibility > Request
An application name is required when defining the request set. This application name and the
request group name uniquely identify this request set. The application name does not prevent
you from assigning reports and report sets from other applications to this group.
For more information see:
Overview of Concurrent Programs and Requests > Request Groups Window

Chapter
CLASSROOM
Creating a Request Group
The code must not contain any spaces. The combination of the application and the code
identify the request group.

Chapter
CLASSROOM
Using a Request Group with a Code
Submitting Requests: Form Versus Responsibility

The request processing is different depending on whether you are using a normal request group
or a coded request group.
Responsibility-Based Access
This is the typical way a user submits a report. The menu prompt Run does not pass any
arguments to the Submit Requests form when the prompt is chosen.
The list of values includes all the programs in the responsibilitys request security group.
Form-Based Access
This type of access uses a coded request group. In this method, when a modified menu prompt
is chosen, it calls a form function to pass an argument (the code) to the Submit Requests form.
The only programs displayed in the Submit Requests list of values are those defined to the
coded request group.

Chapter
CLASSROOM
Submitting Requests: Form Compared with Responsibility
Implementing a Coded Request Group

Chapter
CLASSROOM
Customization Example
The slide shows the values that are used in the following example.

Chapter
CLASSROOM
Customization Example
Creating the Form Function

(N) Application > Function
Type is a non-validated field used to enter a description of the functions use.

Chapter
CLASSROOM
Creating the New Form Function
Passable Request Parameters

The slide shows the parameters you can pass in your new function. Several of the parameters
are paired; these parameters must be used together. Remember that when the request group was
created, it was associated with an application. You must pass both the code and the short name
of the application for the system to identify the correct request group.
For a complete explanation of these parameters, see:
Overview of Concurrent Programs and Requests >
Organizing Programs into Request Groups >
Customizing the Submit Requests Window,
Customizing the Submit Requests Window using Codes

Chapter
CLASSROOM
Passable Request Parameters
Adding the Function to the Menu
(N) Application > Menu

Chapter
CLASSROOM
Defining Request Sets

By defining request sets, you can submit the same set of requests regularly with a single
transaction. Use the Request Set window to create and edit request sets. You can also use the
Request Set Wizard to create simple request sets.

Chapter
CLASSROOM
Defining a Request Set
Organizing Requests with Stages

Request sets are divided into one or more stages, which are linked to determine the sequence in
which the requests will run. Each stage consists of one or more requests that you want to run in
parallel (at the same time in any order). For example, in the simplest request set structure, all
requests are assigned to one stage thus allowing all requests to run in parallel.
To run requests in sequence, assign requests to different stages and then link the stages in the
order you want the requests to run.
The concurrent manager allows only one stage in a request to run at a time. When one stage is
complete, the next stage is submitted. A stage is not considered complete until all of the
requests in the stage are complete. One advantage of using stages is the ability to run several
requests in parallel and then move sequentially to the next stage, thus enabling you to create
more versatile and efficient request sets.

Chapter
CLASSROOM
Request Set Stages
Using Stage Status

Like request sets and concurrent requests, stages can complete with different statuses. Each
stage can complete with a status of Success, Warning, or Error. You can use these completion
statuses to structure your request set by defining which stage will follow the current stage
based on its completion status.
The request set in the slide always starts with Stage 1. If Stage 1 were to complete with the
status of Warning, then the Warning link would be followed and Stage 3 would be submitted.
The status of a completed stage is set according to the highest error status returned by the
individual requests comprising the stage. Therefore, in order for the stage to complete with a
status of Success, all the requests that make up the stage must have completed with a status of
Success. If one request completes with a status of Error, the status for the stage will be Error,
regardless of the statuses of the other requests.
Restarting Request Sets
If a request set stage completes with a status of Error, you can restart the request set at the
point of the error after fixing the cause of the error. In such an instance, the system captures
information on the first stage that fails. and the Restart button in the Oracle Applications

Chapter
CLASSROOM
Stage Status
Manager - View Completed Requests page is enabled. When you click on the Restart button
the request set can restart from the point of the error.
Once the stage has been identified, the request set program submits the stage program in
resubmit mode. In this mode, the program looks at the same stage from the previous run and
determines which programs need to be rerun, (only those that ended in error), and runs those
programs. If this stage completes successfully or has a Warning status, the system proceeds to
the next stage using the normal mechanism of restarting the request set program.

Chapter
CLASSROOM
Linking of Stages
There are no restrictions on linking stages within a request set. Any stage can be linked to any
other stage, including itself. Two or more links can point to the same stage. For example, one
stage can link to another if the completion status of the first is Success or Warning, and link to
a third stage if the status is Error.
You determine the end of a request by not specifying a follow-up stage for each completion
status. You can end a request set after any stage in the set. When any stage completes with a
status that does not link to another stage, the request set ends.
You can use the linking of stages to control your request set. By using the Request Set Wizard
button in the Request Set window you can create the request set as follows:
Run in Parallel creates one stage containing all of the requests you wish to run in
parallel.
Run Sequentially creates a separate stage containing the request or requests for each step
in the sequence and link in the appropriate order.
Run Sequentially but abort on Error sets up your sequence the same as it did for Run
Sequentially, but when it links the stages, it does not enter a follow-up stage as a link in
the Error completion status field.

Chapter
CLASSROOM
Linking of Stages
Defining A Request Set

(N) Requests > Set
The Owner field defaults to your user name and can be changed only by your system
administrator.

Chapter
CLASSROOM
Defining Request Sets Step 1: Enter Request Set Name
Defining A Request Set (continued)

If the current date is outside the Active Dates From and To range you define, the request set
will not be available in the Submit Requests window.
Selecting the Print Together check box will send all your requests to the printer together when
they complete.
Select the Allow Incompatibility check box to have the system check for incompatible
programs when the request set is run. If this check box is left unchecked, then incompatibility
rules will be ignored.

Chapter
CLASSROOM
Defining Request Sets Step 1: Enter Request Set Name
Defining A Request Set (continued)

(N) Requests > Set > (B) Define Stages
Defining Stages
The value for the Display Sequence field is defaulted in sequence as you enter your stages.
You may change the display order of the stages by modifying the field.
The default value for the Function field is Standard Evaluation that bases its completion status
on the normal completion status of the requests it contains.
If you select the Return Value check box for more than one stage, the completion status of the
request set will equal the completion status of the last of these stages to run.
Select the Allow Incompatibility check box to have the system check for incompatible
programs when the request set is run. If this check box is left unchecked, then incompatibility
rules will be ignored.

Chapter
CLASSROOM
Defining Request Sets Step 2: Define a Stage
Defining Stages (continued)

(N) Requests > Set > (B) Define Stages > (B) Requests

Chapter
CLASSROOM
Defining Request Sets Step 3: Enter Requests for Stage
Request Parameters
((N) Requests > Set > (B) Define Stages > (B) Requests > (B) Parameters
Request Parameters Window
Use the Request Parameters window to customize the parameter values of a specific request in
a request set. The fields at the top of the Request Parameters window list general information
about the current request set for which you can customize the parameter values. The multi-row
portion of the window lists the parameters for that request.
The Sequence and Prompt fields are display only.
Selecting the Display check box specifies visibility of a request parameter at submission
time.
Selecting the Modify check box to specifies you can insert or change the value for a
request parameter at submission time.
Using the Shared Parameter field sets a default value for a parameter that occurs in more
than one report or program of a request set. Use the shared parameter label to set an initial
default value for all occurrences of the same parameter so you can avoid typing the same
value all over again for every occurrence of the parameter.

Chapter
CLASSROOM
Defining Request Sets Step 4: Enter Request Parameter
Linking Stages in a Request Set

(N) Requests > Set > (B) Link Stages
Success, Warning, and Error columns - To ensure a particular stage follows the preceding stage
regardless of the completion status, enter the desired stage in all three columns. To stop the
request set if a stage ends in Error, leave the Error column blank. Any time you do not
specifically indicate which stage should follow for a completion status, the request set will exit
on that completion status.

Chapter
CLASSROOM
Defining Request Sets Step 5: Link Stages
Who Can Use a Request Set

(N) Requests > Run > (Option) Request Set > (B) OK
After you define a request set, it becomes your private request set. You can run it as long as
you have access to a standard Submit Request window that does not limit access to specific
requests.
Other users can run the request set only if your system administrator assigns the request set to
their responsibilitys request group. It is possible to have a request set in your request group
that contains individual requests not in your request group, but you can only edit request sets
you own. You can add any requests in your request group to the request set. You can delete
any request from the request set, regardless of whether that request is in your request group. To
update information about an individual request in the request set, however, the request set must
be in your request group.
Note: Request sets can also be run within Oracle Application Framework; for example,
navigate to System Administration responsibility > Request Set > Schedule.

Chapter
CLASSROOM
Submitting a Request Set
Request Set Privileges

You can control request set ownership to manage request set editing and run privileges.
Application User Editing Privileges
Application users define a request set by selecting reports or other concurrent programs
from their current responsibilitys request security group.
Application users automatically own the sets they create.
Application users can always edit the sets they own. However, they cannot edit a request
set they do not own.
Request Sets and Request Security Groups
After changing responsibilities, application users can add reports from their current (new)
responsibilitys request security group to a request set they own.
After changing responsibilities, application users can delete reports from a request set they
own, regardless of whether the report is in the new responsibilitys request security group.

Chapter
CLASSROOM
User Request Set Privileges
System Administrator Request Set Privileges

System administrators can edit and assign ownership of any request set.
System Administrator Editing Privileges
System administrators can define or edit a request set to include any standard submission
report or concurrent program.
System administrators do not automatically own the request sets they define. Request sets
defined by a system administrator initially do not have an owner.
System administrators can assign or change ownership of any request set.
If a request set is assigned to an owner but not to the owners request security group as
well, the reports contained in the request set are available only to the owner.
System administrators can edit any request set, whether the set is owned or not.
System administrators can assign any request set to any request security group, even if the
request set contains individual reports not in the request security group. However, this
privilege provides the members of a responsibility access to reports and programs outside
their request security group.

Chapter
CLASSROOM
System Administrator Request Set Privileges
Lesson Summary
In this lesson you learned how to use request groups to control access to reports and concurrent
programs. Additionally you learned how individual users can define request sets to streamline
processing by setting default values for parameters and sharing parameter values among
multiple reports.

Chapter
CLASSROOM
Summary
Chapter 14
Administering Concurrent Managers

Chapter
CLASSROOM
Administering Concurrent
Managers


Chapter
CLASSROOM

Chapter
CLASSROOM
Lesson Aim
The Oracle Applications system administrator is the end users first point of contact for system
questions. The system administrator should be able to monitor the processing of requests and
deal with any problems. He or she should also be able to balance workloads to provide the
optimum processing environment for users. This lesson teaches you how to monitor and
control system processing and also how to plan and schedule your workload.

Chapter
CLASSROOM
Objectives
Concurrent Requests, Programs, and Processes

When a user runs a report, a request to run the report is generated. The command to run the
report is a concurrent request. The program that generates the report is a concurrent
program. Concurrent programs are started by a concurrent manager.

Chapter
CLASSROOM
Concurrent Requests, Programs, and Processes
Overview of Concurrent Processing

A concurrent manager is itself a concurrent program that starts other concurrent programs
running. When an application user submits a request to run a program, the request is entered
into a database table that lists all of the requests. Concurrent managers read requests from the
table and start programs running.
Part of a managers definition is how many operating system processes it can devote to running
requests. This number is referred to as the managers number of target processes.

Chapter
CLASSROOM
Overview of Concurrent Processing
Generic Service Management (GSM)

Generic Service Management (also called simply Service Management) provides a powerful
framework for managing processes on multiple host machines. Concurrent managers as well
as other application tier services can be managed under GSM. Managed services besides
concurrent managers include the Oracle Forms Listener, Oracle Reports Server, and the Oracle
Workflow Mailer.
With Generic Service Management, the Internal Concurrent Manager (ICM) manages the
various service processes across multiple hosts. On each host, a Service Manager acts on
behalf of the ICM, allowing the ICM to monitor and control service processes on that host.
You can then configure, monitor, and control services through the Oracle Applications
Manager console.

Chapter
CLASSROOM
Generic Service Management (GSM)
Defining a Concurrent Manager

Concurrent managers can be defined to process only certain types of requests and to operate
during certain times of the day.
Scheduling Requests - You can schedule when a manager operates by defining one or
more work shifts and associating the manager with a work shift.
Segregating Requests - You can define specialization rules to identify the kinds of
requests a manager will read. Specialize managers so they only read requests to start
certain kinds of programs.

Chapter
CLASSROOM

(N) Concurrent > Manager > Define
The Parallel Concurrent Processing Details region of this window is discussed in a later lesson.
Concurrent Managers can also be defined within Oracle Applications Manager, by navigating
to Site Map > Administration (T) > Request Processing Managers (under Application Services)
> Create New (B)

Chapter
CLASSROOM
Defining Work Shifts

(N) Concurrent > Manager > Workshifts
A concurrent manager operates only during its specified work shift. Use military time notation
to define a work shiftthat is, use 24 hours rather than 12.
Work shifts can also be defined within Oracle Applications Manager, by navigating to Site
Map > Administration (T) > Request Processing Managers (under Application Services) >
Create New (B) or Edit (B) for a selected service > Add from Available Shifts (B) > Create
New (B)

Chapter
CLASSROOM
Defining Work Shifts
Balancing Process Workload

You can create multiple work shifts for a concurrent manager to regulate the number of
operating system processes the manager starts up at different times of the day and different
days of the week.

Chapter
CLASSROOM
Balancing Process Workload Over Time
Overlapping Workshifts
When work shifts overlap, the work shift with the more specific time period takes effect for the
overlapping time period. For example, a work shift for January 1 overrides a work shift from
9:00 am to 5:00 PM every Monday through Friday.
When work shifts with the same hierarchy level overlap, the work shift with the largest number
of target processes takes effect.

Chapter
CLASSROOM
Work Shift Hierarchy
Concurrent Managers
Immediate Programs and Spawned Programs
Immediate concurrent programs are C or PRO*C subroutines linked with concurrent managers.
Most concurrent programs are spawned as independent processes at run time instead of running
as subroutines. If you are defining a new concurrent program, you should run the program as a
spawned program rather than as an immediate program.
Examples of these are:
FNDLIBR: Contains immediate concurrent programs used by Oracle Applications Object
Library.
INVLIBR: Contains immediate concurrent programs used by Oracle Inventory.
MFCLIBR: Contains immediate concurrent programs used by Oracle Manufacturing.
PALIBR: Contains immediate concurrent programs used by Oracle Projects.

Chapter
CLASSROOM
Concurrent Managers Window: Program Libraries
Assigning Work Shifts to a Manager

(N) Concurrent > Manager > Define > (B) Workshifts

Chapter
CLASSROOM
Assigning Workshifts to a Manager
Specializing a Concurrent Manager

(N) Concurrent > Manager > Specialization Rules

Chapter
CLASSROOM
Specializing a Concurrent Manager
Combined Rules
(N) Concurrent > Manager > Rule

Chapter
CLASSROOM
Specializing a Concurrent Manager: Combined Rules
Defining Specialization Rules

Use actions and qualifications to define specialization rules. An action defines a concurrent
managers behavior toward the request.
Include and Exclude Actions
The manager runs included requests.
The manager does not run excluded requests.
Exclusion rules override inclusion rules.
Example Rules
The example rules would result in a managers reading requests for all programs assigned to
Oracle Purchasing except programs defined with the request type Month-End Rep.

Chapter
CLASSROOM
Specialization Rules
Action Types
Use action types to specify the actions of a manager. An action type specifies the type of
request to which an action refers.
Programs that connect to a specific Oracle Applications account (Oracle ID). For
example, you could include for processing all programs that connect to the Oracle
Payables account AP1.
Specific programs by name. For example, you could include for processing the Oracle
General Ledger program Trial Balance-Budget. When using an action type of program,
you specify the application and the program name.
Certain request types. For example, you could include for processing all programs
defined as a request type of Month-End Reports.
Programs requested by certain users. For example, you could include for processing all
programs requested by the user Operations.
Combined rule. A combined rule combines more than one action to generate a single
rule.

Chapter
CLASSROOM
Action Types
Combining Multiple Actions in Rules

Multiple include actions in a combined rule behave differently from other multiple include
actions in a specialization rule.
A specialized include rule is associated with a specific concurrent manager. A combined
include rule is an independent rule possibly associated with multiple managers.
Multiple specialized include rules create OR clauses, allowing more requests to be read by
the manager.
Multiple combined include rules create AND clauses, further restricting a manager from
reading the request.

Chapter
CLASSROOM
Combining Multiple Actions Within Rules
Defining Request Types

(N) Concurrent > Program > Types

Chapter
CLASSROOM
Concurrent Request Types
How to Define and Use Request Types

There are three steps in defining and using request types:
Identify a category of programs according to some criterion. Define a request type for
that category of programs.
Identify a concurrent program according to the new request type.
Use the new request type in a managers specialization rule.

Chapter
CLASSROOM
Using Request Types
The Purpose of Conflicts Domains

Concurrent processing resolves and imposes conflicts and constraints within a domain and not
across. That is, two incompatible programs A and B will not run concurrently when they are
submitted within the same domain. But, if A is submitted within domain D1 and B is submitted
within D2, they may run concurrently.
Defining Conflicts Domains
(N) Concurrent > Conflicts Domains
To prevent two programs from concurrently accessing or updating the same data, you have to
know where in terms of data, they are incompatible. A Conflict Domain identifies the data that
creates the incompatibility.
In Oracle Applications data is stored in database tables belonging to a particular application.
Each table may also contain information used to determine what conditions need to be met to
access the individual records. These conditions may consist of one or more of the following
data groupings:
SOB - based on the profile option GL_SET_OF_BOOKS
Multiple installations (referred to as MSOB)

Chapter
CLASSROOM
Conflicts Domains
Multiple Operating units (determined by profile option MO_OPERATING_UNIT)

(referred to as MULTIORG)
Multiple Orgs (determined by profile option INV_ORGANIZATION_ID, used by
Manufacturing applications)
HR may use business group as a conflict domain
FA may use FA book
A conflict domain is an abstract representation of the groupings used to partition your data.
There is no limit to the number of domains that can be defined, but excessive domains may
impact performance.

Chapter
CLASSROOM
Processing Conflict Domains

All programs are assigned a conflict domain when they are submitted. If a domain is defined as
part of a parameter the concurrent manager will use it to resolve incompatibilities. If the
domain is not defined by a parameter, the concurrent manager uses the value defined for the
profile option Concurrent: Conflicts Domain. Lastly, if the domain is not provided by a
program parameter and the Concurrent: Conflicts Domain profile option has not been defined,
the Standard domain is used. The Standard domain is the default for all requests.
Each request submitted uses parameters identifying the records it will access. For programs
defined with incompatibility rules the conflict domain parameter is used additionally. The
conflict domain may be set automatically based on such variables as logon ID, set of books, or
the organization the user is working in. The conflict domain parameter may in some cases be
selected in the parameters field of the Submit Requests form.

Chapter
CLASSROOM
Processing Conflicts Domains
Activating and Deactivating Concurrent Managers

(N) Concurrent > Manager > Administer
You can control concurrent managers by activating or deactivating one or all of the managers.
Activate All Managers Simultaneously: When you activate the Internal Concurrent Manager,
it starts up all the concurrent managers. You can activate the Internal Concurrent Manager
from the operating system.
Deactivate All Managers Simultaneously: When you deactivate the Internal Concurrent
Manager, it shuts down all the concurrent managers. You can deactivate the Internal
Concurrent Manager from either the Administer Concurrent Managers window or the operating
system.
Activating and Deactivating Individual Managers: You can activate individual concurrent
managers by using the Administer Concurrent Managers window. The Internal Concurrent
Manager must be active for an individual manager to be active. Deactivate individual
concurrent managers by using the Administer Concurrent Managers form.
Internal Manager Control Functions
Verify Concurrent Manager Status: Manually executes the process monitoring (PMON)
cycle.

Chapter
CLASSROOM
Control Functions of Concurrent Managers

Chapter
CLASSROOM
Deactivate Concurrent Manager: Deactivates the Internal Concurrent Manager and all other
managers.
Terminate Requests and Deactivate Manager: All running requests running concurrent
programs) are terminated, and all managers are deactivated.
Any Other Manager Control Functions
Activate Concurrent Manager: If the manager is defined to work in the current work shift, it
starts immediately. Restart Concurrent Manager: Internal manager rereads the managers
definition and the rules for concurrent program incompatibilities.
Deactivate Concurrent Manager: Deactivates the manager. All requests (concurrent
programs) currently running are allowed to be completed before the manager shuts down. A
manager will not restart until you select the manager and choose Activate Concurrent Manager.
Terminate Request and Deactivate Manager: All running requests (running concurrent
programs) handled by the manager are terminated. Once deactivated a manager will not restart
until you select the manager and choose Activate Concurrent Manager.
Internal Monitor Processes

You can provide fault tolerance for the Internal Concurrent Manager by using Internal Monitor
Processes.
The Internal Concurrent Manager can run on any node and can activate and deactivate
concurrent managers on the same or other nodes. Because the Internal Concurrent Manager
must be active at all times, it needs high fault tolerance. To provide this fault tolerance, parallel
concurrent processing uses Internal Monitor Processes.
The sole job of an Internal Monitor Process is to monitor the Internal Concurrent Manager and
to restart that manager if it fails. The first Internal Monitor Process to detect the failure of the
Internal Concurrent Manager restarts the Internal Concurrent Manager on its own node.
Only one Internal Monitor Process can be active on a single node. You decide which nodes
have an Internal Monitor Process when you configure your system. You can also assign each
Internal Monitor Process a primary and secondary node to ensure its protection.
Internal Monitor Processes, like concurrent managers, can have assigned work shifts and are
activated and deactivated by the Internal Concurrent Manager.

Chapter
CLASSROOM
Internal Monitor and ICM
Creating Custom Transaction Managers

Because forms must be precoded to submit synchronous requests, you do not usually need to
create custom transaction managers.

Chapter
CLASSROOM
Defining a Transaction Manager
Viewing Log and Output Files

You can review log and output files from any node, regardless of which node the concurrent
process runs on. You do not need to log on to a node to view the log and output files from
requests run on that node. The concurrent log and output files from requests that run on any
node are accessible online from any other node. This capability relies on setup steps taken at
install time. For more information, refer to the installation documentation for your platform.
INVLIBR: Contains immediate concurrent programs used by Oracle Inventory.
MFCLIBR: Contains immediate concurrent programs used by Oracle Manufacturing.
PALIBR: Contains immediate concurrent programs used by Oracle Projects.

Chapter
CLASSROOM
Viewing Log and Output Files
Managing Parallel Concurrent Processing

You can distribute concurrent processing across multiple nodes in a cluster, massively parallel,
or homogeneous networked environment.
Benefits of Parallel Concurrent Processing
High Performance: Processes can run on multiple nodes to improve throughput.
Fault Tolerance: Processes can continue running on available nodes even when one or
more nodes fail.
Adaptability: Integrate with platform-specific batch queue and load-balancing systems to
maximize concurrent processing performance on a particular platform.
Single Point of Control: Managers can be administered from any node.
Nodes
Each node consists of one or more processors (CPUs) and its associated memory.
Each node has its own memory that is not shared with other nodes.
Each node operates independently of other nodes except when sharing resources.
Nodes and Concurrent Managers

Chapter
CLASSROOM
Managing Parallel Concurrent Processing
With parallel concurrent processing, one or more managers can run on one or more nodes. You
decide where concurrent managers run when configuring the system. You can define any set of
specialization rules and apply them across nodes in any way desired.

Chapter
CLASSROOM
Lesson Summary
In addition to controlling access to Oracle Applications, monitoring the day-to-day processing
of Oracle Applications is a very important job of the system administrator.
The system administrator is the first point of contact when users have, or suspect they have, a
problem with either the results or the processing of a request. The system administrator has
access to several application log files containing diagnostic information that can be of use in
correcting problems.
The system administrator is also responsible for balancing workload to maintain optimum
performance for users. He or she does this by creating concurrent managers to process user
requests. Managers can be specialized to operate only during certain times and to process only
certain types of requests. System administrators also monitor and control the activity of
managers in a parallel environment.

Chapter
CLASSROOM
Summary

Oracle Apps System Admin Student Guide1

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Oracle Apps System Admin Student Guide1

Hochgeladen von

Copyright:

Verfügbare Formate

Volume 1 - Student Guide

Oracle University and Egabi Solutions use only

R12 Oracle Applications System

Copyright 1996, 2007, Oracle. All rights reserved.

Oracle University and Egabi Solutions use only

U.S. GOVERNMENT RIGHTS

Introduction to Oracle Applications Security ...............................................................................................2-1

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Introduction to Oracle User Management ....................................................................................................5-1

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Data Security Components - Objects.............................................................................................................4-7

Profile Options .................................................................................................................................................7-1

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Delegated Administration vs. Traditional System Administration ................................................................6-39

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Identify Tables and Columns to Audit...........................................................................................................8-18

Diagnostics and Troubleshooting with Oracle Applications Manager .......................................................12-1

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Business Flows ..............................................................................................................................................11-20

Administering Concurrent Managers............................................................................................................14-1

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Introduction to Oracle Workflow ..................................................................................................................15-1

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Overview of Flexfields .....................................................................................................................................18-1

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Step 4 Checking Database Parameters...........................................................................................................17-19

Defining Descriptive Flexfields .......................................................................................................................20-1

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Translatable Dependent Value Sets ...............................................................................................................19-16

Defining Key Flexfields ...................................................................................................................................21-1

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Specifying the Context Field Information .....................................................................................................20-34

Using Advanced Validation Capabilities .......................................................................................................22-1

Copyright Oracle Corporation, 2006. All rights reserved.

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Preparing for Cross-Validation......................................................................................................................21-46

Appendix - Incorporating Custom Help Files ...............................................................................................25-1

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Appendix - Incorporating a Custom Program..............................................................................................24-1

Copyright Oracle Corporation, 2006. All rights reserved.

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Solution Creating a Role and Placing it in a Role Inheritance Hierarchy...............................................26-40

Oracle University and Egabi Solutions use only

Thorough knowledge of R12 Oracle Applications Navigation

How This Course Is Organized

Copyright Oracle Corporation, 2006. All rights reserved.

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Oracle Applications System Administrators Guide Security

Oracle Applications System Administrators Guide Configuration