Sysadmin

11i System Administer Oracle
E-Business Suite ed 2.0

Student Guide
n l y
e O
U s
a l
rn
Course Code 14465GC20
nt e
Edition 2.0
e I
Month Year
Part Number D34107
c l
December 2001
r a
O
Copyright © Oracle Corporation, 2001. All rights reserved.
This documentation contains proprietary information of Oracle Corporation. It is provided under a license agreement containing
restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. If this
documentation is delivered to a U.S. Government Agency of the Department of Defense, then it is delivered with Restricted Rights
and the following legend is applicable:
Restricted Rights Legend
Use, duplication or disclosure by the Government is subject to restrictions for commercial computer software and shall be deemed
to be Restricted Rights software under Federal law, as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, Rights in
Technical Data and Computer Software (October 1988).
This material or any portion of it may not be copied in any form or by any means without the express prior written permission of the
Education Products group of Oracle Corporation. Any other copying is a violation of copyright law and may result in civil and/or
criminal penalties.
If this documentation is delivered to a U.S. Government Agency not within the Department of Defense, then it is delivered with
“Restricted Rights,” as defined in FAR 52.227-14, Rights in Data-General, including Alternate III (June 1987).
The information in this document is subject to change without notice. If you find any problems in the documentation, please report
them in writing to Worldwide Education Services, Oracle Corporation, 500 Oracle Parkway, Box SB-6, Redwood Shores, CA 94065.
Oracle Corporation does not warrant that this document is error-free.
Oracle and all references to Oracle Products are trademarks or registered trademarks of Oracle Corporation.
All other products or company names are used for identification purposes only, and may be trademarks of their respective owners.
Author
Leslie Studdard
Technical Contributors and Reviewers
Andrea Auld, Phil Cannon, Anne Carlson, William Curtis, Kathy Helbling, Terri North, Mildred
Wang, John Zerbel
n l y
e O
oracletutor U s
This book was published using:
a l
r n
nt e
e I
c l
r a
O
Table of Contents
Introduction to System Administration............................................................................... 1-1

Introduction to System Administration ............................................................................... 1-2
Course Objectives ............................................................................................................... 1-3
System Administrator Functional Block Diagram............................................................... 1-5
System Administration Functions........................................................................................ 1-7
Managing Application Security ........................................................................................... 2-1
Managing Application Security........................................................................................... 2-2
Objectives ........................................................................................................................... 2-3
Managing Application Security: Overview ........................................................................ 2-4
Using Responsibilities......................................................................................................... 2-6
Defining a New Application User ....................................................................................... 2-8
Practice 1: Creating A New User Signon ............................................................................ 2-9
Practice 1: Solution ............................................................................................................. 2-11
Practice 1: Solution (Continued) ......................................................................................... 2-13
Defining an Application ...................................................................................................... 2-14
Registering an Oracle ID..................................................................................................... 2-15
Data Groups ........................................................................................................................ 2-16
Defining a Data Group ........................................................................................................ 2-17
Relating Data Groups to Forms and Programs................................................................... 2-18
Practice 2: Working with Custom Applications .................................................................. 2-19
Managing Function Security ............................................................................................... 2-23
Using the Navigator ............................................................................................................ 2-25
Excluding Functions and Menus ......................................................................................... 2-26
Responsibility Components................................................................................................. 2-27
Responsibility Creation Process.......................................................................................... 2-28
Defining a New Responsibility ........................................................................................... 2-29
Practice 3: Defining Responsibilities .................................................................................. 2-31
n l y
O
e
Defining a New Menu Structure.......................................................................................... 2-38
U s
Identifying Existing Menu Structures................................................................................. 2-40
Menu Guidelines ................................................................................................................. 2-41
a l
Modifying an Existing Menu Definition ............................................................................ 2-42
Creating a Menu.................................................................................................................. 2-43
r n
The Menu Viewer ............................................................................................................... 2-45
Using the Menu Viewer ...................................................................................................... 2-46
nt e
Menu Tree Display Styles ................................................................................................... 2-47
Viewing Node Properties .................................................................................................... 2-48
e I
Practice 4: Defining Custom Menus.................................................................................... 2-49
c l
Practice 5: Making a Form Query-Only .............................................................................. 2-62
r a
O
Summary ............................................................................................................................. 2-68
Managing Concurrent Programs and Reports................................................................... 3-1
Managing Concurrent Programs and Reports ..................................................................... 3-2
Objectives ........................................................................................................................... 3-3
Concurrent Requests, Programs, and Managers.................................................................. 3-5
11i System Administer Oracle E-Business Suite ed 2.0 Table of Contents

i
Business Needs for Concurrent Processing......................................................................... 3-6
Business Needs for Standard Request Submission.............................................................. 3-7
Definitions........................................................................................................................... 3-8
Submit Request Flow .......................................................................................................... 3-10
Submit a New Request ........................................................................................................ 3-11
Using the Parameters Window............................................................................................ 3-12
Defining a Submission Schedule......................................................................................... 3-13
Defining Completion Options ............................................................................................. 3-15
Request ID .......................................................................................................................... 3-16
Reprinting a Report............................................................................................................. 3-17
Use the Requests Window to View and Change Requests .................................................. 3-18
How to Use the Requests Window...................................................................................... 3-19
Using the Requests Window ............................................................................................... 3-20
Viewer Options Window..................................................................................................... 3-22
Canceling a Request............................................................................................................ 3-23
Holding a Request............................................................................................................... 3-24
Changing Request Options.................................................................................................. 3-25
Four Phases of a Concurrent Request.................................................................................. 3-26
Pending Phase ..................................................................................................................... 3-27
Running Phase..................................................................................................................... 3-28
Completed Phase................................................................................................................. 3-29
Inactive Phase ..................................................................................................................... 3-30
System Administrator Monitoring Privileges ...................................................................... 3-31
Controlling Log File Access................................................................................................ 3-32
Review Log Files ................................................................................................................ 3-33
Managing Log Files and Tables .......................................................................................... 3-34
Purge Request Results......................................................................................................... 3-35
Practice 1: Administering Concurrent Requests.................................................................. 3-36
Grouping Concurrent Programs and Requests .................................................................... 3-43
Creating a Request Group ................................................................................................... 3-44
Practice 2: Defining a Request Group................................................................................. 3-45
n l y
Submitting Requests: Form Compared with Responsibility................................................ 3-50

e O
Using a Request Group with a Code ................................................................................... 3-49
s
Implementing a Coded Request Group ............................................................................... 3-51
Customization Example ...................................................................................................... 3-52
U
Creating the New Form Function ........................................................................................ 3-53
a l
Passable Request Parameters .............................................................................................. 3-54
Adding the Function to the Menu........................................................................................ 3-55
r n
Practice 3: Defining a Coded Request Group ..................................................................... 3-56
nt e
Defining a Request Set........................................................................................................ 3-63
Request Set Stages .............................................................................................................. 3-64
e I
Stage Status ......................................................................................................................... 3-65
Linking of Stages ................................................................................................................ 3-66
c l
Defining Request Sets Step 1: Enter Request Set Name ..................................................... 3-67
Defining Request Sets Step 2: Define a Stage..................................................................... 3-69
r a
Defining Request Sets Step 3: Enter Requests for Stage..................................................... 3-70
Defining Request Sets Step 4: Enter Request Parameter..................................................... 3-71
O
Defining Request Sets Step 5: Link Stages ......................................................................... 3-72
Submitting a Request Set .................................................................................................... 3-73
User Request Set Privileges ................................................................................................ 3-74
System Administrator Request Set Privileges ..................................................................... 3-75
Practice 4: Using Request Sets............................................................................................ 3-76

ii
Summary ............................................................................................................................. 3-79
Practice Prerequisites .......................................................................................................... 3-80
Administering Concurrent Managers ................................................................................. 4-1
Administering Concurrent Managers .................................................................................. 4-2
Objectives ........................................................................................................................... 4-3
Concurrent Requests, Programs, and Processes .................................................................. 4-4
Overview of Concurrent Processing.................................................................................... 4-5
Defining a Concurrent Manager.......................................................................................... 4-6
Defining Work Shifts .......................................................................................................... 4-8
Balancing Process Workload Over Time ............................................................................ 4-9
Work Shift Hierarchy.......................................................................................................... 4-10
Concurrent Managers Window: Program Libraries ............................................................ 4-11
Assigning Workshifts to a Manager .................................................................................... 4-12
Specializing a Concurrent Manager .................................................................................... 4-13
Specializing a Concurrent Manager: Combined Rules........................................................ 4-14
Specialization Rules ............................................................................................................ 4-15
Action Types ....................................................................................................................... 4-16
Combining Multiple Actions Within Rules......................................................................... 4-17
Concurrent Request Types .................................................................................................. 4-18
Using Request Types........................................................................................................... 4-19
Conflicts Domains............................................................................................................... 4-20
Processing Conflicts Domains............................................................................................. 4-22
Control Functions of Concurrent Managers ........................................................................ 4-23
Internal Monitor and ICM................................................................................................... 4-25
Defining a Transaction Manager......................................................................................... 4-26
Viewing Log and Output Files ............................................................................................ 4-27
Managing Parallel Concurrent Processing .......................................................................... 4-28
Oracle Enterprise Manager ................................................................................................. 4-30
Oracle Applications Manager.............................................................................................. 4-31
Management Pack for Oracle Applications......................................................................... 4-32
Advanced Events................................................................................................................. 4-34
Oracle Performance Manager.............................................................................................. 4-35
n
Oracle Capacity Planner...................................................................................................... 4-36 l y
Defining a Concurrent Manager Practice Instructions ........................................................ 4-38
e O
Concurrent Processing Tuning Assistant............................................................................. 4-37
Practice Solutions................................................................................................................ 4-40
U s
Summary ............................................................................................................................. 4-49
Managing Profile Options .................................................................................................... 5-1
a l
Managing Profile Options ................................................................................................... 5-2
Objectives ........................................................................................................................... 5-3
r n
Personal Profile Values....................................................................................................... 5-4
nt e
Profile Hierarchy Levels ..................................................................................................... 5-5
System Profile Options........................................................................................................ 5-6
Using User Profile Values as Defaults ............................................................................... 5-7
e I
Auditing Related Profile Options ........................................................................................ 5-8
Currency-Related Options................................................................................................... 5-9
c l
Flexfield-Related Options ................................................................................................... 5-10
Online Reporting-Related Options...................................................................................... 5-12
r a
Personal Output Viewer Options......................................................................................... 5-14
User-Related Profile Options .............................................................................................. 5-15
O
Security Signon Profile Options.......................................................................................... 5-17
Practice Instructions............................................................................................................ 5-19
Summary ............................................................................................................................. 5-21
Incorporating a Custom Program ....................................................................................... 6-1
Incorporating a Custom Program ........................................................................................ 6-2

iii
Objectives ........................................................................................................................... 6-3
Using Custom Programs in Oracle Applications................................................................. 6-4
Assumptions for Incorporating a New Program................................................................. 6-5
Components of a Concurrent Program ................................................................................ 6-6
Adding a Custom Program to Oracle Applications ............................................................ 6-7
Identifying the Executable................................................................................................... 6-8
Creating the Concurrent Program........................................................................................ 6-10
Concurrent Program Parameters Window........................................................................... 6-12
Associating a Program with a Request Group..................................................................... 6-14
Submitting the Concurrent Program.................................................................................... 6-15
Practice Solution ................................................................................................................. 6-18
Summary ............................................................................................................................. 6-22
Auditing System Resources .................................................................................................. 7-1
Auditing System Resources................................................................................................. 7-2
Objectives ........................................................................................................................... 7-3
Auditing Oracle Applications.............................................................................................. 7-4
Auditing User Activity ........................................................................................................ 7-5
Sign On Audit Profile Option.............................................................................................. 7-6
Interaction of Sign On Audit Values ................................................................................... 7-7
Sign On Audit Reports ........................................................................................................ 7-8
Sign On Audit Forms Report............................................................................................... 7-9
Sign On Audit Concurrent Requests Report........................................................................ 7-10
Sign On Audit Responsibilities Report ............................................................................... 7-11
Sign On Audit Unsuccessful Logins Report........................................................................ 7-12
Sign On Audit Users Report................................................................................................ 7-13
Monitor Users Window....................................................................................................... 7-14
Auditing Database Changes ................................................................................................ 7-15
Steps for Setting Up AuditTrail .......................................................................................... 7-16
Identify Tables and Columns to Audit ................................................................................ 7-17
Creating an Audit Group ..................................................................................................... 7-18
n
Audit Shadow Tables .......................................................................................................... 7-19l y
O
Shadow Table Views........................................................................................................... 7-20
Audit Tables Window ......................................................................................................... 7-21
e
Identifying the Schema to be Audited ................................................................................. 7-22
U s
Enabling Audit Processing .................................................................................................. 7-23
a l
Summary ............................................................................................................................. 7-27
r n
Managing Printers ................................................................................................................ 8-1
nt e
Managing Printers ............................................................................................................... 8-2
Objectives ........................................................................................................................... 8-3
Formatting Information ....................................................................................................... 8-4
e I
Oracle Print Definition Components ................................................................................... 8-6
Relationships of the Printer Components ............................................................................ 8-8
c l
Defining Printers ................................................................................................................. 8-9
Finding Existing Printer Types............................................................................................ 8-10
r a
Registering a New Printer ................................................................................................... 8-11
Defining a New Printer Type .............................................................................................. 8-12
O
Customization Materials for Oracle Applications Printing ................................................. 8-13
Customizing Printer Components........................................................................................ 8-14
Customizing Print Styles ..................................................................................................... 8-15
Customizing Printer Drivers................................................................................................ 8-16
Invoking a Printer Driver .................................................................................................... 8-18
Passing Print Arguments ..................................................................................................... 8-20

iv
Using the Program Driver Method...................................................................................... 8-21
Initiating Printing from a System Shell Script.................................................................... 8-22
Printing from Standard Input Directly to the Printer .......................................................... 8-23
Driver Method Parameters for Spooling ............................................................................. 8-24
Initialization and Reset Field Contents................................................................................ 8-26
Creating a Custom SQL*ReportWriter Driver ................................................................... 8-27
Sample SRW Driver File .................................................................................................... 8-29
Order of Reading Printer Settings ....................................................................................... 8-30
Testing Your Customization ............................................................................................... 8-31
Managing Printers Practice Instructions.............................................................................. 8-33
Practice Solution (Continued) ............................................................................................. 8-36
Summary ............................................................................................................................. 8-41
Applications DBA Duties...................................................................................................... 9-1
Applications DBA Duties.................................................................................................... 9-2
Objectives ........................................................................................................................... 9-3
Resource Consumer Groups Have Similar CPU Usage Requirements ............................... 9-4
Assigning Resource Consumer Groups ............................................................................... 9-5
Hierarchy of Resource Consumer Groups........................................................................... 9-6
Cost-Based Optimization .................................................................................................... 9-7
CBO Statistics Gathering .................................................................................................... 9-8
Using the Network Test Window........................................................................................ 9-10
Summary ............................................................................................................................. 9-12
Assigning Resource Consumer Groups Example ................................................................ 9-13
CBO Review Question ........................................................................................................ 9-14
Using the Network Test Window Review Questions .......................................................... 9-16
Incorporating Custom Help Files ........................................................................................ 10-1
Incorporating Custom Help Files ........................................................................................ 10-2
Objectives ........................................................................................................................... 10-3
Customizing Help................................................................................................................ 10-4
Oracle Applications Help System Utility ............................................................................ 10-5
Help System Utility Setup: Define Directory Paths ............................................................ 10-6
Downloading Help Files...................................................................................................... 10-7
n l y
e O
Identify Help Files for Customization ................................................................................. 10-8
Identify the Language and Product of the Files.................................................................. 10-10
s
Downloading Help Files for Editing ................................................................................... 10-11
Linking Help Files............................................................................................................... 10-13
U
Special Syntax versus Conventional HTML ....................................................................... 10-14
a l
Cross-Application Links ..................................................................................................... 10-15
Related Topics Links .......................................................................................................... 10-16
r n
Related Topics Links Syntax............................................................................................... 10-17
nt e
Uploading Your New or Changed Help Files ..................................................................... 10-18
File Upload Steps................................................................................................................ 10-19
Creating Reports ................................................................................................................. 10-21
e I
Running Reports.................................................................................................................. 10-22
Updating the Search Index .................................................................................................. 10-23
c l
Customizing Help Navigation Trees ................................................................................... 10-24
Help Builder Functions ....................................................................................................... 10-25
r a
The Help Builder................................................................................................................. 10-26
Opening a Tree for Editing ................................................................................................. 10-27
O
Adding New Help Files to a Tree........................................................................................ 10-28
Adding New Nodes to a Tree.............................................................................................. 10-29
For Further Information ...................................................................................................... 10-30
Summary ............................................................................................................................. 10-31
Demonstration: Using the Help Builder .............................................................................. 10-32
Demonstration (Continued)................................................................................................. 10-33

v
Administering Folders .......................................................................................................... 11-1
Administering Folders......................................................................................................... 11-2
Objectives ........................................................................................................................... 11-3
Folders: Definition .............................................................................................................. 11-4
Administering Folders: Topics............................................................................................ 11-5
Assigning a Default Folder to a Responsibility................................................................... 11-6
Assigning a Default Folder to a User .................................................................................. 11-7
Assigning Ownership of a Folder........................................................................................ 11-8
Deleting a Folder Definition ............................................................................................... 11-9
Administering Folders Practice ........................................................................................... 11-10
Folders Practice (Continued)............................................................................................... 11-11
Summary ............................................................................................................................. 11-18
Managing Document Sequences .......................................................................................... 12-1
Managing Document Sequences ......................................................................................... 12-2
Objectives ........................................................................................................................... 12-3
Using Document Sequences................................................................................................ 12-4
Specifying Sequence Information ....................................................................................... 12-6
How to Define a Document Sequence................................................................................. 12-7
Specifying Document Category Information....................................................................... 12-9
Document Categories .......................................................................................................... 12-10
Sequence Assignments ........................................................................................................ 12-11
Using a Sequence in Your Application ............................................................................... 12-12
Document Sequence Practice .............................................................................................. 12-13
Practice Solution (Continued) ............................................................................................. 12-16
Summary ............................................................................................................................. 12-20
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

vi
Preface
Profile
Before You Begin This Course
Before you begin this course, you should have the following qualifications:
• Thorough knowledge of navigating within Oracle Applications
• Working experience with at least one Oracle Applications module
Prerequisites
• 11i Navigate Oracle E-Business Suite
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.
Related Publications
Oracle Publications
Title
n l y
Part Number
Oracle Applications System Administrator’s Guide

e O A75396
Oracle Applications User’s Guide

U s A75394
Additional Publications
a l
• System release bulletins
r n
• Installation and user’s guides
nt e
e I
• read.me files
c l
•
a
Oracle Magazine
r
O

vii
Typographic Conventions
Typographic Conventions in Text
Convention Element Example
Bold italic Glossary term (if The algorithm inserts the new key.
there is a glossary)
Caps and Buttons, Click the Executable button.

lowercase check boxes, Select the Can’t Delete Card check box.
triggers, Assign a When-Validate-Item trigger to the ORD block.
windows Open the Master Schedule window.
Courier new, Code output, Code output: debug.set (‘I”, 300);

case sensitive directory names, Directory: bin (DOS), $FMHOME (UNIX)
(default is filenames, Filename: Locate the init.ora file.
lowercase) passwords, Password: User tiger as your password.
pathnames, Pathname: Open c:\my_docs\projects
URLs, URL: Go to http://www.oracle.com
user input,
User input: Enter 300
usernames
Username: Log on as scott
Initial cap Graphics labels Customer address (but Oracle Payables)

(unless the term is a
proper noun)
Italic Emphasized words

and phrases,
Do not save changes to the database.
n l
For further information, see Oracle7 Server SQL Language
y
titles of books and
courses,
Reference Manual.
e O
Enter user_id@us.oracle.com, where user_id is the
Quotation
variables
Interface elements
name of the user.
s
Select “Include a reusable module component” and click Finish.
U
marks with long names
that have only
a l
This subject is covered in Unit II, Lesson 3, “Working with
initial caps;
lesson and chapter
Objects.”
r n
titles in cross-
references
nt e
Uppercase SQL column
e
names, commands, I Use the SELECT command to view information stored in the
LAST_NAME
c l
functions, schemas, column of the EMP table.
Arrow
r a
table names
Menu paths Select File > Save.
Brackets
Commas O Key names
Key sequences
Press [Enter].
Press and release keys one at a time:
[Alternate], [F], [D]
Plus signs Key combinations Press and hold these keys simultaneously: [Ctrl]+[Alt]+[Del]

viii
Typographic Conventions in Code
Convention Element Example
Caps and Oracle Forms When-Validate-Item
lowercase triggers
Lowercase Column names, SELECT last_name
table names FROM s_emp;
Passwords DROP USER scott

IDENTIFIED BY tiger;
PL/SQL objects OG_ACTIVATE_LAYER
(OG_GET_LAYER (‘prod_pie_layer’))
Lowercase Syntax variables CREATE ROLE role

italic
Uppercase SQL commands and SELECT userid
functions FROM emp;
Typographic Conventions in 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.
n l y
2. (M) From the menu, select Query then Find.
e O
3. (B) Click the Approve button.
U s
Notations:
a l
(N) = Navigator
r n
(M) = Menu
nt e
e I
(T) = Tab
c l
(B) = Button
r a
O
(I) = Icon
(H) = Hyperlink

ix
Typographical Conventions in 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
—represents the following sequence of actions:
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.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

x
Introduction to System
Administration
Chapter 1
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Introduction to System Administration

Chapter 1 - Page 1
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 1 - Page 2
Course Objectives
Course Objectives
After completing this course, you should be able

to do the following:
• Manage security by granting users access and
defining application privileges
• Manage concurrent programs and reports by using
and controlling request options
• Administer concurrent managers to
balance workloads
• Define and manage printers
n l y
Introduction to Course Topics
e O
U s
This course discusses how to perform administrative tasks in an Oracle Applications systems
environment. You will learn to manage security by granting users access and defining their
a l
application privileges, to administer concurrent managers, and to set profile options. You will
also learn to audit users and system processing, manage printers, administer folders, and
perform other applications DBA duties.
r n
nt e
e I
c l
r a
O

Chapter 1 - Page 3
Course Objectives
Course Objectives
After completing this course, you should be able

to do the following:
• Define system and personal profile settings
• Audit and monitor system processing
• Administer and manage folders
• Perform applications DBA duties
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 1 - Page 4
System Administrator Functional Block Diagram
System Administrator Functional Block

Diagram
Oracle System User
Applications Administrator Community
Oracle Financial What forms display
Applications Applications on my screen?
Security What reports and
Oracle Government
programs can I run?
Financial
Applications How is my online
Concurrent
performance versus
Oracle Processing
program and report
Manufacturing Workload
performance?
Applications
User What are my
Oracle Human
application
Resources Preferences
default settings?
Applications
Can I account for every
Custom Extensions Document
transaction, even
to Sequences
transactions that fail?
Oracle Applications
n l y
Importance of This Course
e O
U s
System administrators are responsible to a user community that requires that Oracle
Applications be configured appropriately for application end users. Typical demands of an
applications user community are:
• Matching job descriptions to applications functionality
a l
r n
• Knowing the status of submitted (concurrent) reports and programs
nt e
• Choosing printers and defining print styles and printer drivers
e I
• Changing an application’s default behavior
• Using document sequences to track documents generated by forms transactions
c l
• Creating customized menu prompts and descriptions
r a
This course discusses how to meet these ongoing and changing needs in your user community.
You will learn how to adapt the applications usage for your users over time.
O

Chapter 1 - Page 5
System Administrator Functional Block Diagram
System Administrator Functional Block

Diagram
Peripheral System User

Equipment and Tools Administrator Community
Peripheral Can I use the

Printer Registration new printer down
and Definitions the hall?
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 1 - Page 6
System Administration Functions

Applications Forms and
signon functions
Programs
and
reports
Define
applications privileges
Balance online and Online

concurrent processing Programs
and
reports
Set application
defaults or
user profiles Default
printer Save output
as OS file
n l y
e O
U s
You can increase Oracle Applications benefits to your users by configuring them to meet the
needs of your company’s organizational structure, equipment, and applications usage.
Database Administrator Versus System Administrator
a l
r n
A database management system can be seen as having two sides to it—a front end that the user
sees and works with and a back end where the actual work or data manipulation is performed.
nt e
This natural division between user applications and their underlying data structures lends itself
I
to two job categories—database administrator and system administrator.
An Oracle Applications system administrator manages the user interface or applications side of
e
l
the database management system.
c
r a
An Oracle database administrator (DBA) manages the data that the various applications enter,
update, and use for company business.
O

Chapter 1 - Page 7
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 1 - Page 8
Managing Application
Security
Chapter 2
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Managing Application Security

Chapter 2 - Page 1
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 2
Objectives
Objectives
After completing this lesson, you should be able to

do the following:
• Define an application user and assign
responsibilities
• Create and use responsibilities. Customize
application privileges for individual users or
categories of users
• Restrict access to menu items and functions by
responsibility
• Define custom menus
n l y
Lesson Aim
e O
U s
One of the most important functions of a system administrator is to manage security for the
Oracle Applications environment. In Oracle Applications security is implemented by creating
a l
user signons and relating them to a responsibility. The responsibility specifies the actual access
authorizations. This lesson shows you how to define both user signons and responsibilities.
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 3
Managing Application Security: Overview
Managing Application Security:

Overview
Windows
Oracle
User Responsibility
Reports
Application
n l y
Managing Application Security: Overview
e O
U s
In an Oracle Application, the system administrator manages security by creating user signons
and assigning them to one or more responsibilities. Users then have access to all the
functionality associated with that responsibility.
User Security
a l
r n
You authorize a user to sign on to Oracle Applications by defining an application user. You
nt e
then assign one or more responsibilities to the new user.
Responsibility Security
e I
A responsibility is a collection of authorizations that allow access to:
c l
• A specific application or applications
• A set of books
r a
• A restricted list of windows, functions, and reports
O
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.

Chapter 2 - Page 4
Self-Service Applications Security
Oracle Self-Service Web Applications use columns, rows, and values in database tables to
define what information users can access. Table columns represent “attributes” that can be
assigned to a responsibility. These attributes are defined in the Web Application Dictionary.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 5
Using Responsibilities
Using Responsibilities
Using Predefined Using Custom Responsibility

Responsibility Define Define Define
or modify or modify or modify
data group menu request group
Define
or modify
responsibility
Exclude
functions
and menus
Define Define
application application
user user
n l y
Creating a New Responsibility
e O
U s
Generally you relate new application users to existing predefined responsibilities. However,
you can customize an existing responsibility or create new responsibilities to accommodate the
a l
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:
r
• Extend Privileges That a Responsibility Owns n
nt e
When users require additional reporting and summary information, you can:
e I
• Use request groups to add additional program or report privileges to a responsibility
• Use menus to add windows and tasks to a responsibility
c l
• Restrict Privileges That a Responsibility Owns
you can: r a
Sometimes it is easier to remove authorizations from an existing responsibility. To do this
O
• 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

Chapter 2 - Page 6
After you have defined a new responsibility, you can associate it with an application user.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 7
Defining a New Application User
Defining a New Application User
Enter user
1
name and password
Require password change

2
Limit access attempts
Enter user’s
3
start and end dates
4 Assign one or more

responsibilities
Steps 1, 3, and 4 are required
n l y
Defining a New User
e O
(N) Security > User > Define
U s
Note: All Navigation paths, unless otherwise noted, are from the System Administrator
Responsibility.
a l
r n
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.
nt e
For a complete explanation of the fields on the Users Form see:
e I
(Help) Applied Technology > Oracle Applications System Administration >
Overview of Oracle Applications Security > Users Window
c l
r a
O

Chapter 2 - Page 8
Practice 1: Creating A New User Signon
Practice 1: Creating A New User Signon
• In this practice you will create a new user signon for

yourself to be used for this class
• After you have defined the new user signon, log in
as your new user
n l y
Instructions
e O
1. Use the information below to define your new user signon:
U s
User Name: Your Name (for example: JSMITH or JOHN_SMITH or JOHN_D_SMITH)
Description: Your Name System Administrator
a l
Password: WELCOME (reenter to verify)
r n
Password Expiration: 30 days
nt e
Effective Dates: From: today To: 3 months from today
Responsibility
e I Application
System Administrator
c
System Administrationl System Administration
Oracle Self-Service Web Applications
r a
Application Developer Application Object Library
O
General Ledger Super User Oracle General Ledger
2. Accept the defaults for all other fields.
3. Save your work and exit Oracle Applications.
4. Sign on again using your new login and password.

Chapter 2 - Page 9
5. Verify that all the responsibilities that you defined are available.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 10
Practice 1: Solution
n l y
Solution
e O
U s
1. Log in to Oracle Applications with user name “Operations” and password “welcome”.
2. Select the System Administrator responsibility under the “Applications” heading of the
Navigate region of the Personal Homepage.
a l
r
4. Enter the fields as described in the instructions: n
3. Navigate to the Users form: (N) Security > User > Define.
nt e
I
e
c l
r a
O

Chapter 2 - Page 11
Responsibility Application
System Administrator System Administration
System Administration Oracle Self-Service Web Applications
Application Developer Application Object Library
5. Click the Save icon to save your work. Your completed form should look similar to the
example shown in the slide.
6. Close the Users form. Choose File > Exit Oracle Applications to return to the Personal
Homepage.
7. Click on the Exit icon on the Personal Homepage (arrow pointing through the doorway) to
return to the signon window.
8. Use your new login and password to log in again. You will be prompted to change your
password. Be sure to note your user name and new password for use in later practices.
Your Personal Homepage should appear similar to the screen shown on the following page.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 12
Practice 1: Solution (Continued)
n l y
Solution (continued)
e O
Administrator Responsibility.
U s
9. Verify that you have the correct Responsibilities displayed, and select the System
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 13
Defining an Application
Application Name Application

Object
Library
Application Short Name
Application Basepath
Application Description
n l y
e O
(N) Application > Register
U s
You can protect custom functions, forms, reports, and programs from being lost during
upgrades by registering them.
a l
r n
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.
nt e
• Short Name – Oracle Applications uses this short name to identify forms, menus,
e I
concurrent programs, and other components of your application.
• Basepath – Enter the base path where your custom forms, reports, and program files are
c l
located. Make sure that your base path is unique to prevent other applications from writing
r a
to the same directory.
For a complete explanation of the fields in this form see:
O
Applications DBA > Applications Window

Chapter 2 - Page 14
Registering an Oracle ID
You can provide access to an Oracle account (Oracle

ID) by working with an Oracle database administrator.
Ask the database

administrator to create a
new Oracle username and
password that connects to
an existing Oracle account
(Oracle ID).
n l y
e O
(N) Security > ORACLE > Register
• Only database administrators can create Oracle accounts.
U s
l
• The install group designates which data group the application is associated with. For
a
r n
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.
nt e
e I
c l
r a
O

Chapter 2 - Page 15
Data Groups
Data Groups
A data group is a collection of pairings of

an application with an Oracle ID.
Responsibility XYZ
Standard Data Group
Application Oracle ID
Can appear AOL APPS Can appear
only once GL APPS multiple times,
but only once
AP1 APPS with each
AP2 APPS application
n l y
What Is a Data Group?
e O
U s
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
a l
that an application connects to a unique application database account.
Note: The installation process automatically defines data groups for Oracle Applications,
r n
so you only need to define additional data groups based on your specific requirements.
Application-Oracle ID Pairs
nt e
e I
• An application can be listed only once in a data group.
• An Oracle ID can be paired with more than one application.
c l
• A custom application registered with Oracle Applications can be included in a data group.
r a
Data Groups and Application Object Library
Application Object Library owns the database tables referred to during concurrent processing
O
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
application Application Object Library is automatically included. The Application Object
Library’s Oracle ID cannot be updated or deleted.

Chapter 2 - Page 16
Defining a Data Group
Define Oracle ID
1
(DBA task)
2 Enter name for new data group
3 Model new data group from

existing data group
4 Associate application with

appropriate Oracle ID
n l y
e O
(N) Security > ORACLE > DataGroup
U s
By defining a data group, you can determine which Oracle account (Oracle ID) an
a l
application’s windows, reports, or concurrent programs connect to. Use data groups to grant
application database account privileges to a responsibility and the requests that it submits.
Data Groups Serve Two Purposes
r n
nt e
• Identify the Oracle ID to which forms connect when users select the responsibility. Choose
windows.
e I
one application-Oracle ID pair from the data group to associate with your responsibility’s
l
• Concurrent managers use a data group to match the application that owns a report or
c
r a
concurrent program with a unique Oracle ID.
Additionally, you can incorporate custom applications by granting application database access
O
to custom applications that you develop. Alternatively, use custom applications to name
customized versions of concurrent programs, responsibilities, and concurrent managers to
protect your customizations during an upgrade.

Chapter 2 - Page 17
Relating Data Groups to Forms and Programs
Relating Data Groups

to Forms and Programs
Form
Responsibility XYZ
SERVER
Standard Data Group
database
Application Oracle ID
Program
AOL APPS
GL APPS table
AP1 APPS
AP2 APPS
n l y
Relating Data Groups to Forms and Programs
e O
defining a data group.
U s
You can control the relationship among applications, forms, and concurrent programs by
Applications, Forms, and Programs

a l
associated with the application.
r n
• A window connects to the application database account designated by the responsibility
nt e
• A data group determines the pairing of an application with a unique application database
account or Oracle ID.
e I
• A program connects to the application database account associated with the application that
owns the program.
c l
r a
Application-Oracle ID Pairs
• An Oracle ID is a username and password that allows access to application tables in an
O
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.

Chapter 2 - Page 18
Practice 2: Working with Custom Applications
Practice 2: Working with Custom

Applications
In this practice you will:

• Register a custom application for your organization
• Create a new data group
• Associate your new application with your new data
group
n l y
Instructions
e O
For Your Custom Application
U s
Substitute your initials for “XXX” to keep your data unique to the database.
Application: XXX Custom Application

a l
Short Name: XXXCA
r n
Basepath: FND_TOP
nt e
Note: For class purposes, we are using a predefined basepath; if you were truly defining a
I
custom application for your organization, this would be a unique basepath.
e
Description:
For Your Data Group l
XXX Custom Application
c
Name:
r a XXX Data Group
O
Description:
Application:
XXX Data Group
XXX Custom Application
Oracle ID: APPS

Chapter 2 - Page 19
Use the “Copy Applications From” button to copy the Applications from the Oracle standard
data group to your custom data group. Insert a new record to add your custom application.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 20
n l y
Practice Solution
e O
Register Your Custom Application
1. Navigate to (N) Application > Register
U s
2. Enter your Application: XXX Custom Application.
a l
3. Enter your Short Name: XXXCA.
r n
4. Enter the Basepath: FND_TOP.
nt e
5. Enter your description: XXX Custom Application.
I
6. Save your work and close the form (M) File > Close Form.
e
l
Your completed form should appear similar to the example shown in the slide.
c
r a
O

Chapter 2 - Page 21
n l y
Solution (Continued)
e O
Create Your Data Group
1. Navigate to (N) Security > ORACLE > DataGroup.
U s
2. Enter your Data Group: XXX Data Group.
a l
3. Enter your Description: XXX Data Group.
r n
button.
nt e
4. Place your cursor in the Application field and click the Copy Applications From
custom data group.

e I
5. Select “Standard” to copy the applications from the Oracle-provided data group to your
c l
6. Ensure that your cursor is in the Application field and click the New icon or choose New
r a
from the File menu to add a row for your custom application.
7. Select your custom application name from the list of values for the Application field.
O
8. Select APPS from the list of values for the Oracle ID field.
9. Save your work. Your completed form should appear similar to the example shown in the
slide.

Chapter 2 - Page 22
Managing Function Security
Managing Function Security
Menu Level 1 Function: A set of

Function executable code
Menu Level 2
Function
available as a menu
Function option
Menu Level 3
Subfunction
Subfunction
Function
Menu Level 2 Subfunction: A subset
Subfunction of a form’s functionality
– Menu Level 2
Function
Function
n l y
Function Security
e O
definitions.
U s
You can manage security by controlling access to individual functions through menu
About Functions
a l
r n
• 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.
nt e
• There are two types of functions: a form function and a nonform function or subfunction. A
Web Regions
e I
subfunction represents a securable subset of a form’s functionality.
c l
The fields in the Web regions are required only if your function will be accessed from Oracle
r a
Self-Service Web Applications.
Adding Functions to or Removing Functions from a Responsibility
O
• 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.

Chapter 2 - Page 23
• Exclude groups of functions by excluding a menu from a responsibility.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 24
Using the Navigator
Using the Navigator

What is built into the menu?
Menu Level 1 Menu Level 1

Function Function
Menu Level 2 Menu Level 2
Function Function
Function Function
Menu Level 3 Function
Subfunction Menu Level 2
Subfunction Function
Function Function
Menu Level 2
Subfunction What is seen in the Navigator?
– Menu Level 2
Function
Function
n l y
Navigator Menu Displays
e O
U s
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.
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 25
Excluding Functions and Menus
Excluding Functions and Menus
Menu Level 1
Function-A Excluding a function affects the
Menu Level 2 function regardless of level.
Function-B
Function-C
Menu Level 3
Function-A
Function-D
Function-E
Menu Level 2
Function-D
Menu Level 2 Excluding a menu excludes all
Function-F its child functions.
Function-G
Function-H
n l y
Exclusion of Functions and Menus
e O
U s
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.
a l
r n
• When you exclude a function from a responsibility, all occurrences of that function
throughout the menu structure of a responsibility are excluded.
nt e
e I
c l
r a
O

Chapter 2 - Page 26
Responsibility Components
Responsibility Components
Data group Request security

group
Menu
Exclusions
n l y
Components of a Responsibility
e O
A responsibility has two required components and two optional components.
Required Components
U s
l
• Data group: A data group specifies the Oracle Application database accounts to which a
a
r n
responsibility’s forms and concurrent programs connect.
• Menu: A menu specifies the forms that a responsibility can display and the functions it can
access.
nt e
Optional Components
e I
• Request security group: A request group lists the concurrent programs that a responsibility
c l
can run. When a request group is assigned to a responsibility, it is referred to as a request
security group.
r a
• Exclusions: Exclusions modify a responsibility’s access to the forms and functions
O
specified by a menu.

Chapter 2 - Page 27
Responsibility Creation Process
Data groups Users
Security Security
ORACLE Responsibilities User
DataGroup Define
Security
Responsibility
Request groups Define Menus
Security Application
Responsibility Menu
Requests
n l y
e O
the System Administrator responsibility.
U s
There are five forms involved in the responsibility creation process. These are available under
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 28
Defining a New Responsibility
Enter application and

1 responsibility name
2 Enter start and end dates
3 Select data group
4 Select menu
5 Select request group
6 Enter menu or function exclusions
n l y
e O
U s
• Assemble the components of application privileges to create a responsibility.
• Define the responsibility by assembling a menu, report security group, and data group and
l
defining any function security (any menu or function exclusions).
a
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 29
You must assign the following to your new

responsibility:
• A data group to supply the form, report, and
program connect privileges
• A menu to supply access to forms within an
application
• Any function or menu exclusions to control
access to the functionality of the application
• A report security group to control access to
reports and concurrent programs
n l y
Defining a Responsibility
e O
(N) Security > Responsibility > Define
U s
A responsibility determines if the user accesses Oracle Applications or Oracle Self-Service
a l
Web Applications, 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.
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 30
Practice 3: Defining Responsibilities
Practice 3: Defining Responsibilities

• Define a new Responsibility for your Assistant System
Administrator.
• Modify the privileges of the responsibility using menu
Exclusions allowing the following:
– Define Users
– Define Request Security Groups
– Submit Requests
– View Completed Requests
– Define Standard Request Sets
– Monitor Running Jobs
• Assign your new responsibility to a user for testing
• Assign your new responsibility to an existing user
n l y
Instructions
e O
U s
Use the information in the chart below to define the new responsibility. Replace the XXX with
your initials. Use the Data Group and Custom Application you created in the previous
practices.
Responsibility Name: XXX Assistant System Administrator
a l
Application:
r
Application Object Library n
Responsibility Key:
nt e
XXX_Asst_SysAdmin
Description:
Effective Dates:
e I
Assistant System Administrator
(accept the default system date)
Available From:
c l Oracle Applications
Data Group:
r a Standard
O
Data Group Application: Application Object Library
Menu:
Request Group:
Navigator Menu - System Administrator GUI
(leave blank)

Chapter 2 - Page 31
Excluding Menus and Functions from a Responsibility
Modify access to certain menus and functions for your new Responsibility by excluding the
items below. You can use the Function Security Menu Report as a guide to determine what
needs to be excluded.
Menu or Function Name to EXCLUDE:
Type Name
Function Monitor Application Users
Function Responsibilities
Function Web Enabled PL/SQL
Menu NAVSECVAL4.0
Menu ORACLE Menu – System Administrator GUI
Menu AuditTrail Menu – System Administrator GUI
Menu Concurrent Menu – System Administrator GUI
Menu Profile Menu – System Administrator GUI
Menu Application Menu – System Administrator GUI
Menu Install Menu – System Administrator GUI
Menu Workflow Administrator
Function Oracle Support MetaLink
The following Menu and Function Names will remain:

• Users (Function)
• Request Groups (Function)
• Standard Report Submission and View Report (privileged) 4.0 (Menu)
• Running Jobs (Function) n l y
e O
Test Your New Responsibility by Assigning it to a New User
U s
In order to test this new responsibility, create a new user signon for your assistant system
the listed below.

a l
administrator and assign your newly created responsibility to this user. Use the information in
User Name: XXXAssistSA

r n
Description:
nt e
XXX Assistant System Administrator
Password:
Password Expiration:
e I
WELCOME
90 days
Responsibility:
c l XXX Assistant System Administrator
r a
Once you have defined it, sign off and back on using the new signon. Check that all the
specialized responsibilities and exclusions that you intended apply to this new user.
O
Add Your New Responsibility to an Existing User
Query-up your user you created in Lab 1 and add this responsibility to that user.

Chapter 2 - Page 32
n l y
Practice Solution
e O
Create Your New Responsibility
1. Navigate to (N) Security > Responsibility > Define.
U s
2. Enter the Responsibility Name: l
a
3. Select the Application:
n
Application Object Library
r
4. Enter the Responsibility Key:
5. Enter the Description:
nt e
XXX_ASST_SYSADMIN
Assistant System Administrator
6. Accept the Effective Date:
e I (accept the default system date)
c l
7. Check Available From:
8. Select the Data Group:
Oracle Applications
Standard
r a
9. Select the Data Group Application: Application Object Library
O
10. Select the Menu:
Define Your Exclusions
Navigator Menu – System Administration GUI
1. Navigate to the Menu Exclusions tab of the window.

Chapter 2 - Page 33
2. Click on Type of exclusion – Function or Menu – then use the list of values to select the
appropriate function or menu to exclude in the name column. Continue until all items
listed are excluded.
Type Name
Function Monitor Application Users
Function Responsibilities
Function Web Enabled PL/SQL
Menu NAVSECVAL4.0
Menu ORACLE Menu – System Administrator GUI
Menu AuditTrail Menu – System Administrator GUI
Menu Concurrent Menu – System Administrator GUI
Menu Profile Menu – System Administrator GUI
Menu Application Menu – System Administrator GUI
Menu Install Menu – System Administrator GUI
Menu Workflow Administrator
Function Oracle Support MetaLink
The following items will be left:

• Users (Function)
• Request Groups (Function)
• Standard Report Submission and View Report (privileged) 4.0 (Menu)
• Running Jobs (Function)
n l y
slide.
e O
3. Save your work. Your completed form should look similar to the example shown in the
4. Close the Responsibilities form.

U s
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 34
n l y
Practice Solution (continued)
e O
Test your new Responsibility by Assigning it to a New User
1. Navigate to (N) Security > User > Define
U s
2. Enter the User Name: XXXAssistSA
a l
3. Enter Description:
n
r
4. Enter Password:
e
Welcome
nt
5. Enter Password Expiration: 90 days
6. Select Responsibility:
e I XXX Assistant System Administrator
c l
7. Leave all other fields blank, or accept the defaults.
8. Save your work. Your new Users form should look similar to the example shown on the
slide.
r a
O
9. Close the Users form.

Chapter 2 - Page 35
n l y
e O
Sign On as Your New User
U s
1. Exit Oracle Applications (M) File > Exit Oracle Applications and exit the Personal
Homepage (click the Exit icon).
a l
change your password.
r n
2. In the signon window enter your new user name and password. You will be prompted to
nt e
3. From the Personal Homepage select your XXX Assistant System Administrator
responsibility.
e I
4. Review the menu items for your new responsibility and verify that only the correct items
l
appear. The menu should appear similar to the example shown in the slide.
c
r a
O

Chapter 2 - Page 36
n l y
e O
Assign your new Responsibility to your existing user from Practice 1
1. Navigate to the Users form (N) Security > User > Define.
U s
l
2. Put the form in query mode by pressing F11 or by selecting (M) View > Query by
a
Example > Enter.
r n
3. Enter the user name you created in Lab 1 in the Name field and execute your query by
nt e
pressing Ctrl-F11 or by selecting (M) View > Query by Example > Run.
e I
4. Navigate to the Responsibilities tab.
5. Insert a new record by clicking the New icon on the toolbar. Select your XXX Assistant
c l
System Administrator from the LOV for the Responsibility field.
6. Save your work.
r a
Your completed form should look similar to the example in the slide.
O

Chapter 2 - Page 37
Defining a New Menu Structure
Defining a New Menu Structure
Identify menu needs
Print function security report for

similar existing menus
Plan the menu structure
Start with a blank menu form
Build the menu from bottom to top
Assign to the responsibility
Print a function security report set to

document the new menu
n l y
New Menu Structure
e O
new responsibility.
U s
Use the Menus form to define menus pointing to functions that you want to make available to a
Make New Responsibilities, Not New Menus

a l
constructing an entirely new menu structure.
r n
If possible, apply exclusion rules to existing menus to customize a responsibility rather than
nt e
Determine the Application Functionality Required
e I
• Different jobs require access to different function groups.
• Identify predefined menus, forms, and form subfunctions to use as entries when defining a
new menu.
c l
r a
Plan Your Menu Structure
• Start with a blank Menus form (blank screen). Menus cannot be copied. A menu saved
O
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.

Chapter 2 - Page 38
• Assign the menu structure to the new responsibility by using the responsibilities form.
• Document your menu structure by printing the Function Security Menu Report.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 39
Identifying Existing Menu Structures
Identifying Existing Menu

Structures
Function Security Report Set
Function Security Menu Report
Function Security Navigator Report
Function Security Function Report
n l y
Designing a New Menu Structure
e O
U s
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
a l
r
• Lists the full menu name of the responsibility n
nt e
• Indicates any excluded menu items, with the rules that exclude them
Function Security Navigator Report
e I
• Lists the menu as it appears in the Navigator for the responsibility specified
c l
• Does not include items excluded by function security rules
r a
Function Security Function Report
O
• Lists the functions accessible by the responsibility specified
• Does not include items excluded by function security rules

Chapter 2 - Page 40
Menu Guidelines
Menu Guidelines
• Design prompts with unique first letters (typing the

first letter will automatically select it).
• Sequence the prompts with the most frequently
used functions first.
• Entries cannot be copied from one menu definition
to another.
• Use acronyms only when an industry term or
company word is so capitalized—for example, WIP
or COGS.
• Use integers in numbering.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 41
Modifying an Existing Menu Definition
Modifying an Existing Menu

Definition
• Menus are called by their user menu name.

• Any change to a user menu name takes effect
immediately.
• Any existing menus that call the modified menu use
the new name.
• The previous name no longer appears.
• Any menu entry modifications take effect
immediately.
n l y
Modifying a Menu
e O
You can modify predefined menus to suit specific job functions.
Overwrite a User Menu Name
U s
l
When you change a menu’s user menu name, the menu entries are not affected. The menu’s
a
r n
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.
nt e
The old user menu name is no longer valid. When you are defining menus, or if you are
displayed in any list of values.

e I
selecting main menus when defining a responsibility, the previously named menu is no longer
Modify a Menu Entry

c l
r a
When you are modifying a predefined menu, all other menus that call that menu display the
menu’s modifications. For example, if you modify GL_SUPERUSER4.0 by adding another
O
prompt that calls a form, all menus that call GL_SUPERUSER4.0 display the additional
prompt when GL_SUPERUSER4.0 is displayed.

Chapter 2 - Page 42
Creating a Menu
Creating a Menu
Use the following guidelines as you build your menu:

• Build your menus from the bottom. A menu
structure must already exist for a menu at a higher
level to reference it.
• Give your menu both an internal and user name.
• The sequence number specifies the order in which
your options are displayed on the menu.
• The Navigator prompt is the prompt that the user
sees to invoke this function or menu.
• Each entry on the menu definition form refers to
either a function or another submenu.
n l y
Creating a Menu
e O
Use the Menus window to create a menu:
(N) Application > Menu
U s
l
After you save your changes in this form, the Compile Security concurrent program is
a
r n
automatically submitted to compile the menu data. Compiling your menu data allows for the
system to determine more quickly during a user’s session whether a function is available to a
particular responsibility or menu.
nt e
New Menus form fields:
e I
• Menu Type – used to specify the purpose of the menu. The possible values are:
c l
- Standard – for menus that would be used in the Navigator form
r a
- Tab – for menus used in Self-Service applications
- Security – for menus that are used to aggregate functions for data security or specific
O
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:

Chapter 2 - Page 43
Function Security > Menus Window
Note: If a menu entry has both a submenu and a function defined for it, then the
behavior depends on whether or not the function is executable. It 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. For example, an Oracle Applications form using Oracle Forms
is an executable function from within Oracle Forms, but not within Self-Service
Applications.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 44
The Menu Viewer
The Menu Viewer
• The Menu Viewer is a read-only window that

provides a hierarchical view of the submenus and
functions of a menu, and also lists properties of the
menus and functions.
• When you create a new menu, your changes must
be committed to the database before you can see
them in the Menu Viewer.
n l y
The Menu Viewer
e O
(N) Application > Menu > (B) View Tree...
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 45
Using the Menu Viewer
n l y
e O
(N) Application > Menu > (B) View Tree...
U s
• To view the menu tree, click on the plus (+) sign next to the menu name. You will see a
your main menu.

a l
hierarchical tree with a number of nodes. Each node represents a function or submenu of
r n
• The menu tree displays the user menu name for the main menu, and displays the prompts
nt e
from the Menus form for submenus and functions. If no prompt has been specified, then no
label will appear for the node.
Printing the Menu Tree
e I
l
To print a menu tree, choose Print from the File menu.
c
r a
O

Chapter 2 - Page 46
Menu Tree Display Styles
n l y
e O
(N) Application > Menu (B) View Tree…
U s
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.
a l
r n
• Vertical – Menu entries are displayed vertically, similar to how they appear in the
Navigator window when you log on to Oracle Applications.
nt e
• Org-Chart – Menu entries are displayed horizontally as in an organizational chart.
I
• Interleaved – Menu entries are displayed horizontally and vertically.
e
c l
r a
O

Chapter 2 - Page 47
Viewing Node Properties
Viewing Node Properties
Use one of the following methods to view a node’s

sequence number, prompt, and description:
• Highlight the node in the menu tree to view the
properties in the properties pane.
• Create a separate Properties window by clicking the
“push pin” button at the top of the Properties pane.
• Select Properties from the View menu.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 48
Practice 4: Defining Custom Menus
Practice 4: Defining Custom Menus
In this practice you will

• Plan and create a customized menu allowing access
to specific System Administrator tasks
• Associate the new menu with a new responsibility
• Create a user of the new responsibility
• Use the new user signon to test the menu
n l y
Practice Instructions
e O
• Create a submenu to allow access to set up Flexfield Value Security
U s
l
• Create a submenu to allow access to Define Responsibilities, Request Groups, and setup
a
Flexfield Value Security
r n
• Create a TOP level menu allowing access to Define and Monitor Users, Define
nt e
Responsibilities and Request Groups, setup Flexfield Value Security, View/Update
e I
Personal Profile options, Run and View Requests, and Define Request Sets
• View the new menu using the Menu Viewer
c l
• Associate the new menu with a new responsibility for the System Auditor
r
Create Your Menu:
a
• Assign the new Responsibility to a new and an existing user
Menu Name:
O
Level Three Menu
XXX_FLEX_SECURITY
User Menu Name: XXX_FLEX_SECURITY
Description: Define and Assign Flexfield Security Rules

Chapter 2 - Page 49
Seq Prompt Submenu Function Description
10 Define Flexfield Security Rules Define Flex Security
Rule
20 Assign Assign Flexfield Security Assign Flex Security
Rule Rule
Level Two Menu
Menu Name: XXX_RESPONSIBILITY
User Menu Name: XXX_RESPONSIBILITY
Description: Define Responsibilities, Request Groups, and Security Rules

10 Define Responsibilities Define Responsibilities
20 Request Request Groups Define Request Group

Group
30 Flexfield XXX_FLEX_SECURITY Define and Assign Flex

Security (your level three menu) Security Rules
Level One Menu

Menu Name: XXX_TOP_SYSTEM_AUDITOR
User Menu Name: XXX_TOP_SYSTEM_AUDITOR
Description: Custom System Auditor Menu
n l y
Seq Prompt
10 Users
Submenu
User Menu - System
Function
e O Description
Define and Monitor
Administrator GUI
U s Users
20 Responsibilities XXX_RESPONSIBILITY
a l Define Responsibility,
(your level two menu)
r n Request Group,
nt e Security Rules
30 Personal Profile
e I Profile User Values View/Update Personal
c l Profile Options
40 Requests
r a Requests Menu – Run and View Requests,
O Other Responsibilities Define Request Sets

Chapter 2 - Page 50
Create the New Responsibility
Name: XXX System Auditor
Application: Application Object Library
Responsibility Key: XXX_SYSTEM_AUDITOR
Description: XXX System Auditor
Effective Date: From: Today’s Date To: Leave Blank
Available From: Oracle Applications (default)
Data Group Name: Standard
Menu: XXX_TOP_SYSTEM_AUDITOR
Request Group: leave blank
Assign the Responsibility to a New User

User Name: XXX_SYS_AUDITOR
Description: System Auditor
Password: WELCOME
Responsibility: XXX System Auditor
Test that the new user, responsibility, and newly created and assigned menu work properly.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 51
n l y
Practice Solution
e O
Create Your Menu:
U s
1. Log on as the user you created in Practice 1 and select your System Administrator
responsibility.
a l
2. Navigate to (N) Application > Menu.
r n
3. Enter the data for your level 3 menu into the appropriate fields on the form:
Level Three Menu
nt e
Menu Name:
I
XXX_FLEX_SECURITY
e
c l
r a
Seq Prompt
10 Define O Submenu Function
Flexfield Security Rules
Description
Define Flex Security
Rule
20 Assign Assign Flexfield Security Assign Flex Security
Rule Rule

Chapter 2 - Page 52
3. Save your work. Your form should appear similar to the example shown in the slide.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 53
n l y
Practice Solution (Continued)
e O
U s
4. Clear the form: (M) Edit > Clear > Form, or with your cursor in the Menu field, click New.
5. Enter the data for your Level 2 menu into the appropriate fields on the form:
Level Two Menu
a l
r n
nt e
Seq Prompt Submenu
e I Function Description
10 Define
c l Responsibilities Define Responsibilities
20 Request
r a Request Groups Define Request Group
Group
30 Flexfield
O XXX_FLEX_SECURITY Define and Assign Flex
6. Save your work. Your form should appear similar to the example shown in the slide.

Chapter 2 - Page 54
n l y
e O
U s
7. Clear the form: (M) Edit > Clear > Form or with your cursor in the Menu field, click New.
8. Enter the data for your TOP or Level 1 menu in the appropriate fields on the form:
a l
Level One Menu
r n
nt
User Menu Name: XXX_TOP_SYSTEM_AUDITOR e
I
e
c l
r a
O

Chapter 2 - Page 55
10 Users User Menu - System Define and Monitor
Administrator GUI Users
20 Responsibilities XXX_RESPONSIBILITY Define Responsibility,

(your level two menu) Request Group,
Security Rules
30 Personal Profile Profile User Values View/Update Personal

Profile Options
40 Requests Requests Menu – Run and View Requests,

Other Responsibilities Define Request Sets
slide.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 56
n l y
e O
10. Click the View Tree… button to see your new menu in the Menu Viewer.
U s
Your menu tree should appear similar to the example shown in the slide.
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 57
n l y
e O
Assign Your Custom Menu to a New Responsibility
11. Navigate to (N) Security > Responsibility > Define.
U s
l
12. Enter the data below into the appropriate fields of the form:
a
r n
Application:
e
nt
Description: I
XXX System Auditor
e
Effective Date:
Available From:
c l From: Today’s Date To: Leave Blank
Oracle Applications (default)
r
Data Group Name: a Standard
Menu:
O
XXX_TOP_SYSTEM_AUDITOR
Request Group: leave blank

Chapter 2 - Page 58
slide.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 59
n l y
e O
14. Navigate to (N) Security > User > Define.
U s
l
15. Enter the Data below into the appropriate fields of the form:
a
r n
Description:
Password: WELCOME
nt e
XXX System Auditor
e I
Responsibility:
c l XXX System Auditor
16. Save your work. Your completed form should appear similar to the example shown on the
slide.
r a
O

Chapter 2 - Page 60
n l y
e O
Test Your New User, Responsibility, and Menu
U s
17. Exit Oracle Applications: (M) File > Exit Oracle Applications, and return to your Personal
Homepage.
a l
18. Click on the Exit icon to open the login screen.
r n
19. Sign on again using your new login. You will be required to change your password. Note
nt e
your user name and password for future access.
e I
20. From the Personal Homepage click on your XXX System Auditor responsibility.
21. Verify that your Navigator menu contains the correct items. Your screen should appear
c l
similar to the example shown in the slide.
r a
O

Chapter 2 - Page 61
Practice 5: Making a Form Query-Only
Practice 5: Making a Form Query-Only
Your System Auditor needs to view System Profile

Options without update capability.
• Make the Update System Profile Values form query-
only
• Attach your query-only form to your System Auditor
menu
n l y
e O
Create Your Query-Only Form:
In the Form Functions form enter the following on the Description tab:
U s
Function: XXX_FNDPOMPV
a l
User Function Name: View System Profile Values
r n
Type:
Description:
Form
nt e
View System Profile Values
I
Click the Form tab and enter the following:
e
Function:
Form:
c l
XXX_FNDPOMPV
Update System Profile Values
Application:
r a
Parameters:
O QUERY_ONLY=YES

Chapter 2 - Page 62
Attach Your Function To Your TOP LEVEL Menu
Query up your XXX_TOP_SYSTEM_AUDITOR menu in the Menu form. Enter the
following for your new function
Sequence: 35
Prompt: View System Profiles
Function: View System Profiles
Test Your Query-Only Form

Log in as your System Auditor and test your query-only form.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 63
n l y
Practice Solution
e O
Create Your Query-Only Form:
U s
1. Log in as your user you created in Practice 1 and choose your System Administrator
responsibility.
a l
3. Enter the following information:
r n
2. Navigate to the Form Functions form (N) Application > Function.
nt e
In the Form Functions form enter the following on the Description tab:
Function:
I
XXX_FNDPOMPV
e
Type:
c l
User Function Name: View System Profile Values
Form
Description:
r a View System Profile Values
Function: O
Click the Form tab and enter the following:
XXX_FNDPOMPV
Form: Update System Profile Values

Chapter 2 - Page 64
Parameters: QUERY_ONLY=YES
slide.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 2 - Page 65
n l y
e O
Attach Your Function To Your TOP LEVEL Menu
1. Navigate to the Menus form (N) Application > Menu.
U s
l
2. Query up your XXX_TOP_SYSTEM_AUDITOR menu in the Menu form.
a
3. Enter the following for your new function
r n
Sequence:
Prompt:
35
nt
View System Profiles e
Function: I
View System Profile Values
e
slide.
c l
r a
O

Chapter 2 - Page 66
n l y
e O
Test Your Query-Only Form
1. Exit Oracle Applications and the Personal Homepage.
U s
2. Log in as your XXX_SYS_AUDITOR.
a l
n
3. Your menu should be similar to the example shown in the slide.
r
4. Test your query-only form.
nt e
For example, open View System Profiles and in the Find System Profile Values window
e I
enter “FND%” in the Profile field and click Find. This will display all the Site-level
profile options that begin with “FND.” Note that you cannot update any fields.
c l
r a
O

Chapter 2 - Page 67
Summary
Summary
You should now be able to do the following:

• Control access to applications by defining
signons
• Control access to database accounts by defining
data groups
• Control access to functionality by defining menus
• Combine data group and menu definitions into
custom responsibilities
n l y
Lesson Summary
e O
U s
One of the most important functions of the system administrator is controlling applications
security. The system administrator specifies which users have access to which functions. User
a l
signons provide the user access to an application. Responsibilities control that user’s access to
various functions of the application. Online access is controlled through the use of menus and
r n
menu exclusions. Report and concurrent program access is controlled through the use of
request groups.
nt e
e I
c l
r a
O

Chapter 2 - Page 68
Managing Concurrent
Programs and Reports
Chapter 3
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Managing Concurrent Programs and Reports

Chapter 3 - Page 1
Managing Concurrent Programs

and Reports
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 2
Objectives
Objectives

do the following:
• Use Standard Request Submission (SRS) to submit
requests
• Monitor the processing of a request
• Define a request group to control user access to
reports
• Customize the standard SRS processing of reports
by defining a request group with a code
• Set default parameter values and share values
among multiple reports by defining a request set
n l y
Lesson Aim
e O
U s
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
a l
how the system administrator creates and uses these request groups.
Similar to request groups are request sets – collections of programs along with their parameters
r n
and options. Request sets can be created by users, but they are still managed by the system
administrator.
nt e
e I
c l
r a
O

Chapter 3 - Page 3
Objectives
Objectives

do the following:
• Control the behavior and update of report
parameters by defining a request set
• Control user access to reports and programs by
specifying the ownership of a request set
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 4
Concurrent Requests, Programs, and Managers
Concurrent Requests, Programs, and

Managers
Request Table
Run program ...
Run program ...
User submits Run program ... Concurrent
request to run Run program abc manager
program abc Run program ...
Concurrent
manager
starts
program abc
n l y
Concurrent Requests, Programs, and Managers
e O
with online operations.
U s
Concurrent processing allows long-running, data-intensive programs to run simultaneously
programs; they are referred to as concurrent programs.

a l
• Oracle Applications programs can run concurrently with each other as well as with other
r n
• Requests to run Oracle Applications programs—for example, to run an Oracle General
nt e
Ledger report—are concurrent requests. Each concurrent request inserts a row into a
database table maintained by the Oracle Application Object Library.
I
• Concurrent managers read requests from the requests table and start concurrent programs.
e
c l
r a
O

Chapter 3 - Page 5
Business Needs for Concurrent Processing
Business Needs for Concurrent

Processing
Concurrent processing helps you satisfy the following

business needs:
• Continue working at your computer while running
data-dependent reports and programs.
• Fully use the capacity of your hardware by
executing many application tasks at once.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 6
Business Needs for Standard Request Submission
Business Needs for Standard Request

Submission
Standard Request Submission enables you to:

• Use a standard interface to run your programs and
reports
• Control access to different reports and programs
• View report output online
• Automatically run programs, reports, or request sets
at specific time intervals
• View a log file that summarizes the completion
information about all the reports and programs in a
request set
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 7
Definitions
Definitions
• Concurrent Request
• Concurrent Manager
• Request Set
• Stage
n l y
Concurrent Processing Definitions
e O
Concurrent Request
U s
A concurrent request is a request that you submit to run a concurrent program as a concurrent
a l
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.
r n
Concurrent Manager
nt e
I
A concurrent manager is a component of concurrent processing that monitors and runs
requests without tying up your computer.
e
Request Set
c l
r a
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
O
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 3 - Page 8
Definitions
Definitions
• Parameter
• Concurrent Processing Options
• Online Request Review
n l y
Concurrent Processing Definitions (continued)
e O
Parameter
U s
In SRS, a parameter is a report variable whose value you can change each time you run a
a l
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
r n
nt e
You can control and change certain run options for each of your concurrent requests. Not only
I
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
e
file format.
c l
or time to start a request, or choose to save the results of your concurrent request in a standard
r a
Online Request Review
O
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 3 - Page 9
Submit Request Flow
Submit Request Flow
Select Request
Enter Information
May be required Enter Parameters

Optional Define Submission
Schedule
Optional
Completion Options
Submit Request
Record Request ID
n l y
Using Standard Request Submission (SRS)
e O
request sets.
U s
Using Standard Request Submission gives you control over how you can run your requests and
a l
• 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.
r n
• Defining a schedule can be as simple as submitting As Soon as Possible, or it can involve
nt e
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.
I
• Completion options enable you to deliver notification to others using Oracle Workflow, as
e
for each request.
c l
well as specifying which printers and how many copies of the output you want to produce
r a
• You can submit as many requests as you like from the Submit Request window. You can
O
even submit a request more than once if you want to run the same request with different
parameter values.

Chapter 3 - Page 10
Submit a New Request
1. Navigate to the Submit a New Request Window:

2. Check the option for Single Request or Request
Set.
3. Click OK.
4. Use the Copy a Prior Request button to use a
previously entered request submission
or
Select the name of the request that you want to run
from the list of values.
n l y
e O
(N) Requests > Run
U s
The responsibility that you are using determines the request group and the requests that will
appear in the list of available requests.
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 11
Using the Parameters Window
Using the Parameters Window
• A Parameters window automatically appears if you

select a request that requires parameter values.
• The Prompts in the Parameters window are specific
to the request that you select.
• The parameters you enter are concatenated and
displayed in the Parameters field of the Submit
Requests window.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 12
Defining a Submission Schedule
1. From the Submit Request window, click Schedule…

2. In the Schedule window you can either Apply a
Saved Schedule or establish a schedule by
choosing one of the scheduling options.
3. To apply a saved schedule, click the button to
display the Predefined Schedules find window.
4. Find the schedule you want to apply and click OK.
5. A message describing the schedule or further
scheduling options for you to define will appear in
the window.
n l y
Submitting Requests
e O
(N) Concurrent > Requests > Submit a New Request > (B) Schedule...
The Schedule Window
U s
l
The scheduling window provides you with several scheduling options. You can choose to reuse
a
r n
a schedule that 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
nt e
intervals, or on specific days of the week or month.
I
When saving your schedule you must provide a unique name. You can also provide additional
information in the Description field.
e
c l
r a
O

Chapter 3 - Page 13
6. To define your own schedule, choose one of the

Run the Job… options.
7. The option you choose determines the type of
calendar that appears for you to define your
schedule.
8. If you wish to save your schedule for future use,
click the “Save this schedule” check box.
9. The Save Schedule window appears. Enter a name
and description for your schedule.
n l y
Define Submission Schedule (continued)
e O
(N) Concurrent > Requests > Submit a New Request > (B) Schedule...
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 14
Defining Completion Options
Defining Completion Options
1. Check the Save all Output Files check box to write

your request to a file. If you want to view your
report online, you must enable this box.
2. Click the Options… button.
3. Specify additional people to notify using Oracle
Workflow, upon completion of this report.
4. Select a print style, a printer, and a number of
copies.
5. Click OK.
6. Click Submit Request to submit your request.
n l y
Submitting Requests
e O
(N) Concurrent > Requests > Submit a New Request > (B) OK > (B) Options...
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 15
Request ID
Request ID
• Oracle Applications assigns a request

est # ID to each request submission so that
Requ 5
12 4
3 you can identify your request.
• Use the request ID to query for your
request output in the Requests
window.
• Oracle Applications assigns a new
request ID to each resubmission of a
request and displays the request ID of
the previous request in the log file.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 16
Reprinting a Report
Reprinting a Report
1. Use the Find Requests window to enter criteria

about the report.
2. Requests matching your criteria will display in the
Requests window.
3. Select your request.
4. From the Tools menu select Reprint...
n l y
The Find Requests Window appears when you navigate to (N) Requests > View.
e O
Note: The Profile Option Concurrent:Save Output must be set to Yes.
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 17
Use the Requests Window to View and Change Requests
Use the Requests Window to View and

Change Requests
Use the Requests window to perform the following

functions:
• View all submitted concurrent requests
• Check the status of requests
• Change aspects of a request’s processing options
• Diagnose Errors
• Find the position of a request in the queues of
available concurrent managers
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 18
How to Use the Requests Window
How to Use the Requests Window
1. Navigate to the Find Requests window.

2. Enter specific criteria in the Find Requests
window
or
Click Find to display all your submitted requests.
n l y
Display the Find Requests window by navigating to (N) Requests > View.
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 19
Using the Requests Window
Use the various buttons to perform tasks related to

concurrent processing:
• Refresh Data - Requeries the lines in the request
table.
• Find Requests - Displays the Find Request window
to perform a search.
• Submit a New Request… - Displays the Submit a
New Request window.
• Hold Request - Puts a request on hold if the request
has not started running.
• Cancel Request - Cancels a request
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 20
Use the various buttons to perform tasks related to

concurrent processing:
• View Details... - Displays the Request Detail window.
If the request has not already run, you can change
selected fields.
• Diagnostics - Displays diagnostic information about
a request.
• View Output - Displays an online format of the
report.
• View Log… - Displays information about the request
such as arguments used and other technical
information.
n l y
Using the Requests Window (continued)
e O
U s
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
use to view your output.

a l
View Output button will display a window prompting you to select the MIME type you wish to
r n
For more information on associating file formats with MIME types see:
nt e
How to View Request Status and Output > Defining the Reports Viewer.
e I
c l
r a
O

Chapter 3 - Page 21
Viewer Options Window
Viewer Options Window
• Use this window to define the MIME types for the

output formats of your concurrent requests.
• These MIME types are used in viewing the reports.
• For each file format, you can associate one or more
MIME types.
n l y
Use the Viewer Options Window to Define MIME Types
e O
(N) Install > Viewer Options
U s
You can use one MIME type to view reports of a certain format. For example, you can view all
are set by several profile options. Seeded MIME types are:

a l
text format reports in Microsoft Word. MIME types for supported formats for a particular user
• Viewer: Application for HTML

r n
• Viewer: Application for PCL
nt e
e I
• Viewer: Application for PDF
• Viewer: Application for PostScript
c l
• Viewer: Application for Text
r a
• Viewer: Application for XML
O
This MIME type is sent to a browser window when the user views a report of that file format.

Chapter 3 - Page 22
Canceling a Request
Canceling a Request

2. Select the request you want to cancel and click
Cancel Request.
3. A decision window will prompt you to verify your
action. Click Yes.
The status of the request will change immediately
to Cancelled.
n l y
Canceling a Request That Has Not Yet Completed
e O
(N) Requests > View (B) Find
U s
If you cancel a request set, then Oracle Applications automatically cancels all requests in the
set.
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 23
Holding a Request
Holding a Request

2. Select the request you want to put on hold and
click Hold Request.
3. The button will change to a “Remove Hold” button
and the status of the request will change to On
hold.
4. To remove the hold, select the request and click
Remove Hold.
n l y
Holding a Request That Has Not Started Running
e O
Only requests that have not started running can be put on hold.
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 24
Changing Request Options
Changing Request Options
If your request has not started running, you can

change how it runs and prints its output by using the
Requests window.
1. Navigate to the Find Requests window

2. Put your request on Hold.
3. Click View Details to display the Request Details
window.
4. Change the desired options and click OK.
n l y
Changing Request Option
e O
U s
Note: You can change the following only if the request or request set is Pending or
Scheduled:
a l
- Start Date and Time
- Printer and number of copies r n
- Save output
nt e
- Resubmission options
e I
c l
r a
O

Chapter 3 - Page 25
Four Phases of a Concurrent Request
Inactive
Pending
Running
Completed
n l y
e O
U s
The system administrator must periodically review the status of Oracle Applications programs
to determine what a particular program’s status is in the lifecycle of a request.
l
A concurrent request has a lifecycle of either three or possibly four phases:
a
• Pending: The request is waiting to be run.
• Running: The request is running. r n
nt e
• Completed: The request has finished execution.
I
• Inactive: The request cannot yet be run.
e
c l
r a
O

Chapter 3 - Page 26
Pending Phase
Pending Phase
Normal Waiting Standby Scheduled
Logical
database
n l y
Pending Phase
e O
A program in the Pending phase can be in one of four statuses:
• Normal: The program is waiting for an available manager.
U s
l
• Waiting: A child program is waiting for a parent to mark it ready to run.
a
database to complete. r n
• Standby: A program is waiting for another incompatible program in the same logical
nt e
• Scheduled: A program’s scheduled start time has not yet elapsed.
e I
c l
r a
O

Chapter 3 - Page 27
Running Phase
Running Phase
Normal Paused Resuming Terminating
n l y
Running Phase
e O
A program in the Running phase can be in one of four statuses:
• Normal: Program is in progress.
U s
l
• Paused: A parent program is waiting for one or more child programs to complete.
a
programs. r n
• Resuming: A parent program is continuing after the completion of one or more child
nt e
• Terminating: The program is being terminated.
e I
c l
r a
O

Chapter 3 - Page 28
Completed Phase
Completed Phase
Normal Warning Error Terminated Canceled
n l y
Completed Phase
e O
A program in the Completed phase can be in one of five statuses:
• Normal: Program completed successfully.
U s
l
• Warning: Program completed successfully but with warning messages.
a
• Error: Program failed to complete successfully.
r n
nt e
• Terminated: A running program was terminated.
• Canceled: A pending or inactive program was canceled before it started.
e I
c l
r a
O

Chapter 3 - Page 29
Inactive Phase
Inactive Phase
Disabled On Hold No Manager
n l y
Inactive Phase
e O
A program in the Inactive phase can be in one of three statuses:
• Disabled: The requested program has not been enabled for execution.
U s
• On Hold: The requested program has been placed on hold.
a l
n
• No Manager: There is no manager defined to run this type of request.
r
nt e
e I
c l
r a
O

Chapter 3 - Page 30
System Administrator Monitoring Privileges
System Administrator Monitoring

Privileges
• Place any pending request on hold.

• Take any request off hold.
• Terminate any request.
• Change the priority of a request.
• View the log file and the manager log
file.
n l y
Monitoring Privileges of the System Administrator
e O
U s
The system administrator’s privileges extend beyond those of the end user. The system
administrator can perform all the operations shown on the slide. However, the system
l
administrator cannot view the actual output of another user’s report.
a
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 31
Controlling Log File Access
Controlling Log File Access
User Profile Option Request

Concurrent: Report Access Level Log
User
Manager
Users can view only their
Log
own requests.
Responsibility
Internal
Users can view any request Manager
for their responsibility. Log
n l y
Log File Access
e O
access privileges for end users.
U s
The user profile option Concurrent: Report Access Level determines the report and log file
l
User: Access to reports and diagnostic log files is limited to the user who submitted the reports.
a
user is currently using.
r n
Responsibility: Access to reports and diagnostic log files is based on the responsibility that the
nt e
A user’s report and log file access privileges include:
e I
• Viewing the completed report output online
• Viewing the diagnostic log file online (also a system administrator privilege)
c l
• Reprinting a completed report (if Concurrent: Save Output profile is Yes; also a system
r a
administrator privilege)
For pending requests, only the submitter of the request or the system administrator can view
O
the details of the request.

Chapter 3 - Page 32
Review Log Files
Review Log Files
Request Internal Manager

Log Log
Manager
Log
n l y
Log File Descriptions
e O
U s
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
a l
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
r n
the user and the system administrator can access this file.
nt e
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
I
descending order by start date and time. This file is accessible by both the user and the system
e
administrator.
c l
Internal Manager Log File This file documents the performance of the Internal Concurrent
r a
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
O
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 3 - Page 33
Managing Log Files and Tables
To conserve space you should periodically delete log

and output files.
Use the Purge Concurrent Request and/or the

Manager Data program to purge Request Log files,
Concurrent Manager Log Files, and report output
files.
n l y
e O
U s
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
a l
delete Oracle Applications log files and output files. Your company’s MIS department and
application users should agree on an archiving and file retention policy that is appropriate for
your organization.
r n
nt e
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
I
by the operating system, as well as records from Application Object Library tables that contain
e
c l
history information about concurrent requests and concurrent manager processes.
Scheduling Purge Submissions Run the Purge Concurrent Request and/or Manager Data
r a
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
O
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 3 - Page 34
Purge Request Results
Purge Request Results
Database Tables Operating System Files

Product_TOP
LOG OUT
FND_ CONC_REQUEST IrequestID.req Username.requestID

_ARGUMENTS IrequestID.req Username.requestID
IrequestID.req Username.requestID
FND_RUN_REQUESTS IrequestID.req Username.requestID
FND_CONCURRENT IrequestID.req Username.requestID
_REQUESTS Request
FND_DUAL
FND_CONCURRENT WprocessID.mgr
Manager
_PROCESSES WprocessID.mgr
n l y
Results of Purge Requests
e O
U s
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
a l
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
r n
nt e
• FND_CONC_REQUEST_ARGUMENTS: This table records arguments passed by the
concurrent manager to each program it starts running.
I
• FND_RUN_REQUESTS: For submitted report sets, this table stores information about the
e
l
reports in the report set and the parameter values for each report.
c
r a
• FND_CONCURRENT_REQUESTS: This table contains a complete history of all
concurrent requests.
O
• 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 3 - Page 35
Practice 1: Administering Concurrent Requests
Practice 1: Administering Concurrent

Requests
As system administrator you have been assigned

to submit the following user requests:
1. Submit the Active Responsibilities report to run
now and not again.
2. Submit the Active Users report to run at a one-
minute interval.
3. Submit the Report Sets report to run one week from
today.
4. Submit the Work Shifts report to run once a day at
2:00 PM for one week only.
n l y
Instructions
e O
processing was completed.
U s
Submit the requests listed above and perform the following checks to ensure that
l
1. View the Active Responsibilities report and verify that it has completed.
a
r n
2. View the Report Diagnostics of a report that completed successfully.
3. Review the Request Log of a report that completed successfully.
nt e
4. View the Output of a report that completed successfully.
Additional tasks:
e I
c l
1. Cancel one of your pending requests.
2. Put a request on hold and take it off hold.
r a
3. Reprint one of the completed reports with 0 copies defined.
O
4. Cancel the request that was submitted to run once every minute.

Chapter 3 - Page 36
n l y
Practice Solution
e O
Submit the Active Responsibilities report to run now and not again.
1. Navigate to (N) Requests > Run.
U s
2. Click OK to accept the default “Single Request.”
a l
n
3. Select Active Responsibilities from the list of values for the Name field.
r
4. Click Submit.
nt e
5. Note the Request ID displayed in the Decision window and click Yes to submit another
request.
e I
c l
r a
O

Chapter 3 - Page 37
n l y
e O
Submit the Active Users report to run at a one-minute interval.
1. Select Active Users from the list of values for the Name field.
U s
2. Click the Schedule… button.
a l
n
3. Select Periodically from the Run this Job… option group.
r
nt e
4. In the Re-run every fields, enter 1 and select Minute(s) from the list of values.
5. Select From the Completion of the prior run from the Apply the Interval… option
I
group. Your Schedule screen should appear similar to the example shown in the slide.
e
6. Click OK.
7. Click Submit.
c l
r a
O
request.
Submit the Reports and Sets by Responsibility report to run one week from today.
1. Select Reports and Sets by Responsibility from the list of values for the Name field.
2. You will be prompted for parameters. Select Application Object Library from the
Application list of values.

Chapter 3 - Page 38
3. Click OK to close the Parameters window.
5. Select Once from the Run this Job… option group.
6. In the Run At field change the date to one week from today by using the popup calendar
or by typing in the date.
7. Click OK.
8. Click Submit.
request.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 39
n l y
e O
U
1. Select Work Shifts Report from the list of values for the Name field.s
Submit the Work Shifts Report to run once a day at 2:00 PM for one week only.

a l
n
3. Select Periodically from the Run this Job… option group.
r
nt e
4. In the Start At field keep the current date, but change the time to 2:00 PM (14:00:00) by
using the popup calendar or by typing it in.
e I
5. In the End At field change the date to one week from today and the time to 2:00 PM
(14:00:00) by using the popup calendar or by typing it in.
6. Click OK.
c l
r
7. Click Submit.
a
O
8. Note the Request ID displayed in the Decision window and click No.

Chapter 3 - Page 40
n l y
e O
View Your Requests
• Navigate to (N) Requests > View.
U s
• Click Find to view all your requests.
a l
n
• Use the appropriate buttons on this form to perform each of the tasks listed:
r
nt e
Verify that the Active Responsibilities request has completed.
• Find the Active Responsibilities report. The Phase should be Completed and the Status
should be Normal.
e I
c l
View the Diagnostics of a report that completed successfully.
• Select a report with Phase Completed and Status Normal (for example, the Active
r a
Responsibilities report).
O
• Click the Diagnostics button. The Request Diagnostics window will appear.
• Review the entries and click OK to close the window.
Review the Request Log of a report that completed successfully.
• Select a report with Phase Completed and Status Normal (for example, the Active Users
report).

Chapter 3 - Page 41
• Click the View Log… button. The log file will appear in a separate browser window.
• Review the entries for the log and close the browser window.
View the Output of a report that completed successfully.
• Select a report with Phase Completed and Status Normal (for example, the Active Users
report).
• Click the View Output button. The report will appear in a separate browser window.
• Review the report and close the browser window.
Additional Tasks
1. Cancel the Active Users request.
• Click Refresh Data to verify that your display is current.
• Select the Active Users request that is Running.
• Click Cancel Request. A Decision window will warn you: “Cancelling a request
cannot be undone. Continue?” Click Yes.
• The Phase will be updated to Completed and the Status will be set to Cancelled.
2. Put the Reports and Sets by Responsibility report on hold.
• Select the Reports and Sets by Responsibility report.
• Click Hold Request. The Phase of the request will be updated to Inactive and the
Status will be set to On Hold.
• Click Remove Hold to take the request off hold.
3. Reprint the Active Users report.
• Select one of the Active Users reports that completed with a Normal status.
• From the Tools menu select Reprint…
• With 0 copies selected, click OK.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 42
Grouping Concurrent Programs and Requests
Grouping Concurrent Programs and

Requests
Request Group Request Set

Report Run option
Report Run option
Program Print option
Report Report parameter
Program Print option
Report Report parameter
Programs and reports Programs and reports

available to a responsibility available for submission
In a single transaction
n l y
Grouping Concurrent Programs and Requests
e O
U s
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 l
r n
A request group is a collection of reports and other concurrent programs. You use request
nt e
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.
I
Any user of a responsibility has access to the reports in that responsibility’s request security
e
group.
c l
Additionally, you can define a request group to have an access code. Users must supply this
r a
code to access the reports in the coded request group.
Request Sets
O
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
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 3 - Page 43
Creating a Request Group
Creating a Request Group
Request groups can include:

• All the reports and concurrent programs owned by
an application
• Individual concurrent requests
• Request sets
• Stage Functions
n l y
Request Group Creation
e O
(N) Security > Responsibility > Request
U s
An application name is required when defining the request set. This application name and the
a l
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:
r n
nt e
Request Groups Window.
e I
c l
r a
O

Chapter 3 - Page 44
Practice 2: Defining a Request Group
Practice 2: Defining a Request Group
In the practice you will:

• Create a Request Group to be used by the Assistant
System Administrator Responsibility
• Limit access to programs by Application, Program,
or Set as specified
• Assign the Request Group to the appropriate
responsibility
• Test your Request Group
n l y
e O
Replace “XXX” with your initials.
1. Create a Request Group using data below:
U s
Group Name: XXX Assistant SysAdmin Group
a l
r n
Code:
Description:
leave blank
nt e
XXX Assistant SysAdmin Group
Requests
e I
Type
Application
c l Name
Application
Program
r a
Employee Listing Oracle Payables
Set
O Period End Oracle Payables
2. Assign the new Request Group to your Assistant System Administrator Responsibility.

Chapter 3 - Page 45
3. Verify your work by selecting the Assistant System Administrator Responsibility and
viewing the LOV for both Single Request and Request Set.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 46
n l y
Practice Solution
e O
Define a Request Group
1. (N) Navigate to Security > Responsibility > Request.
U s
l
2. Enter the data from the instructions in the appropriate fields in the window.
a
r n
Application:
Code:
nt
leave blank e
Description: I
XXX Assistant SysAdmin Group
e
Requests
Type
c l Name Application
r
Application a Application Object Library Application Object Library
Program
Set
O Employee Listing
Period End
Oracle Payables
Oracle Payables

Chapter 3 - Page 47
3. Save your work. Your completed form should appear similar to the example shown in
the slide.
4. Close the form (M) File > Close Form.
Attach the Request Group to Your Assistant System Administrator Responsibility
5. Navigate to (N) Responsibility > Define.
6. Query to find your XXX Assistant System Administrator responsibility. Choose your
request group from the list of values for the Request Group Name field.
7. Save your work.
Test Your Request Group
Test that the request group has been appropriately assigned and that the reports now exist
under your Assistant System Administrator responsibility.
8. Exit and sign on again as your XXX Assistant System Administrator.
9. Navigate to (N) Requests > Run. Click OK to accept the default.
10. Note the reports that now exist in the list of available reports for you to run.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 48
Using a Request Group with a Code
Using a Request Group with a Code
Supplying a code for your request group allows you to

implement form-level security:
• Reports in a coded request group are run using a
customized Submit Request form function.
• The menu calls a Submit Request form function that
passes a request group code as an argument.
• The programs for the coded request group are
displayed in the Submit Request form list of values.
n l y
The code must not contain any spaces. The combination of the application and the code
e O
identify the request group.
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 49
Submitting Requests: Form Compared with Responsibility
Submitting Requests: Form Compared

with Responsibility
Specialized function
passes code and
submits report
using request group
with corresponding
code.
Normal report
submission uses
request security group.
n l y
Submitting Requests: Form Versus Responsibility
e O
or a coded request group.
U s
The request processing is different depending on whether you are using a normal request group
Responsibility-Based Access
a l
r n
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.
nt e
The list of values includes all the programs in the responsibility’s request security group.
Form-Based Access
e I
This type of access uses a coded request group. In this method, when a modified menu prompt
c l
is chosen, it calls a form function to pass an argument (the code) to the Submit Requests form.
r a
The only programs displayed in the Submit Requests list of values are those defined to the
coded request group.
O

Chapter 3 - Page 50
Implementing a Coded Request Group
Implementing a Coded Request Group
To implement a request group with a code:
1. Create the request group supplying a code.

2. Create a new form function.
3. Add the new function to an existing menu.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 51
Customization Example
Function name:
MRP_FNDRSRUN_LOAD_COPY_MPS
Function user name:

Load/Copy/Merge MPS Schedule
Menu prompt:
Load/Copy/Merge
Request group code:

MRP_LOAD_COPY_MPS
n l y
e O
The slide shows the values that are used in the following example.
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 52
Creating the New Form Function
Creating the New Form Function
1. Navigate to the Form Functions window:

2. Enter a Function Name. This is the name used by
the application.
3. Enter a User Function Name. The user name will
appear in the list of values when adding the
function to the menu.
4. On the Form tab, choose Run Reports from the
Form field list of values.
5. Enter the arguments to pass to the Submit Request
form in the Parameters field. Select Edit Field from
the Edit menu to open the editor.
n l y
Creating the Form Function
e O
(N) Application > Function
U s
Type is a nonvalidated field used to enter a description of the function’s use.
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 53
Passable Request Parameters
REQUEST_GROUP_CODE
REQUEST_GROUP_APPL_SHORT_NAME
CONCURRENT_PROGRAM_NAME
PROGRAM_APPL_SHORT_NAME
REQUEST_SET_NAME
SET_APPL_SHORT_NAME
SUBMIT_ONCE
LOOKUP
TITLE
USER_ORG, ORG_ID, ORG_NAME, ORG_CODE,
CHART_OF_ACCOUNTS
n l y
e O
U s
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
a l
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.
r
For a complete explanation of these parameters, see: n
nt e
e I
Overview of Concurrent Programs and Requests >
Organizing Programs into Request Groups >
c l
Customizing the Submit Requests Window,
a
Customizing the Submit Requests Window using Codes.
r
O

Chapter 3 - Page 54
Adding the Function to the Menu
Adding the Function to the Menu
1. Navigate to the Menus window.

2. Enter a sequence number for the new item.
3. Enter a navigator prompt. Make the first letter of
the prompt unique in the menu. This enables
AutoReduction to work more efficiently.
4. Choose the user function name of your function
from the list of values.
5. Click Save.
6. Click View Tree… to see your new menu structure
in the Menu Viewer.
n l y
(N) Application > Menu
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 55
Practice 3: Defining a Coded Request Group
Practice 3: Defining a Coded Request

Group

• Create a coded Request Group for special access to a
program
• Create a new function to call your coded request group
• Add the new function to your System Auditor menu
• Test your coded Request Group
n l y
Instructions
e O
Substitute your initials for “XXX.”
U s
Define the Request Group
a l
Group Name: XXX Journal Entries
r n
Application:
Code: XXXJE
nt e
Description: I
XXX Journal Entries
e
Request Type: Program
c l
Request Name: Journal Entries Report
Application:
r a Oracle Receivables
Function:
O
Define the New Function
XXX_FNDRSRUN_JOURNAL_ENTRIES
User Function Name: XXX Journal Entries
Type: Form

Chapter 3 - Page 56
Description: XXX Journal Entries
Form: Run Reports
Parameters: TITLE = “XXX Journal Reports”
REQUEST_GROUP_CODE = “XXXJE”
REQUEST_GROUP_APPL_SHORT_NAME = “FND”
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 57
n l y
Practice Solution
e O
1. Navigate to (N) Security > Responsibility > Request.
U s
Define the Request Group
a l
Group Name: XXX Journal Entries
r n
Application:
Code: XXXJE
nt e
Description: I
XXX Journal Entries
e
Request Type: Program
c l
Request Name: Journal Entries Report
Application:
r a Oracle Receivables
O
the slide.
4. Close the Request Groups form (M) File > Close Form.

Chapter 3 - Page 58
n l y
e O
5. Navigate to (N) Application > Function.
6. Define the function using the data listed below:
U s
a l
Define the New Function
r n
Description Tab:
Function:
nt e
XXX_FNDRSRUN_JOURNAL_ENTRIES
User Function Name:
e IXXX Journal Entries

Type:
Description:
c l Form
XXX Journal Entries
Form Tab:
r a
Form:
O
Parameters:
Run Reports
TITLE = “XXX Journal Reports”
REQUEST_GROUP_CODE = “XXXJE”
REQUEST_GROUP_APPL_SHORT_NAME =“FND”

Chapter 3 - Page 59
The parameter names must be typed as shown in all capital letters and the parameter
values must be typed using double quotes.
Hint: Use the Edit Field icon or select Edit Field… from the Edit menu to enter the
parameters.
the slide.
8. Close the Form Functions window: (M) File > Close Form.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 60
n l y
e O
Add the New Function to the Menu.
9. Navigate to (N) Application > Menu.
U s
l
8. Query up your first-level custom menu: XXX_TOP_SYSTEM_AUDITOR
a
9. Add your function as sequence number 50.
r n
nt e
10. Enter “Journal Entries Report” in the Prompt field.
11. Select your new function from the LOV for the Function field (XXX Journal Entries).
I
12. Enter XXX Journal Entries for your description.
e
the slide.
c l
r a
14. Close the form.
O

Chapter 3 - Page 61
n l y
e O
Test Your Changes
U s
15. Exit Oracle Applications and the Personal Homepage. Sign on again as the System
a l
Auditor (XXX_SYS_AUDITOR) to see your new function on the menu. Your request
group Journal Entries Report will appear on the Navigator for this responsibility.
r
16. Navigate to (N) Journal Entries Report. n
nt e
17. Click OK to accept “Single Request.”
e I
18. When the submit request form appears, note the window title – it will be the value
entered for your parameter TITLE. The title of the form defaults to the request title
l
because it is the only request on the list.
c
r a
O

Chapter 3 - Page 62
Defining a Request Set
Defining a Request Set
Enter Request Set Name
Define a Stage
Enter Requests for Stage
Enter Request Parameter
Link Stages
Save Changes
n l y
Defining Request Sets
e O
U s
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.
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 63
Request Set Stages
Request Set Stages
Stage 1 Stage 2 Stage 3

Request 1 Request 2 Request 3
Stage 1 Stage 3
Stage 2
Request 1 Request 4
Request 3
Request 2 Request 5
n l y
Organizing Requests with Stages
e O
U s
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
a l
parallel (at the same time in any order). For example, in the simplest request set structure, all
requests are assigned to one stage. This allows all requests to run in parallel.
r n
To run requests in sequence, assign requests to different stages and then link the stages in the
nt
order that you want the requests to run.
e
The concurrent manager allows only one stage in a request to run at a time. When one stage is
I
complete, the next stage is submitted. A stage is not considered complete until all of the
e
c l
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. This enables you to create
r a
more versatile and efficient request sets.
O

Chapter 3 - Page 64
Stage Status
Stage Status
Success Stage 2
Request 4
Stage 1
Request 1 Warning Stage 3
Request 2 Request 5
Request 3
Stage 4
Error Request 6
n l y
Using Stage Status
e O
U s
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
based on its completion status.

a l
statuses to structure your request set by defining which stage will follow the current stage
r n
The request set in the slide always starts with Stage 1. If Stage 1 were to complete with the
nt e
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
I
individual requests comprising the stage. Therefore, in order for the stage to complete with a
e
c l
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,
r a
regardless of the statuses of the other requests.
O

Chapter 3 - Page 65
Linking of Stages
Linking of Stages
• No restrictions on linking stages within a set

• Links can point to any other stage in the set
• Two or more links can point to the same stage
• Request set is completed when a stage ends with no
further links to be followed
n l y
Linking of Stages
e O
U s
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
a third stage if the status is Error.

a l
stage can link to another if the completion status of the first is Success or Warning, and link to
r n
You determine the end of a request by not specifying a follow-up stage for each completion
nt e
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.
I
You can use the linking of stages to control your request set. By using the Request Set Wizard
e
c l
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.
r a
• Run Sequentially – creates a separate stage containing the request or requests for each step
O
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 3 - Page 66
Defining Request Sets Step 1: Enter Request Set Name

Step 1: Enter Request Set Name
1. Navigate to the Submit a New Request window

2. Enter the name of the request set.
3. Enter a unique Set Code for your request set.
4. Choose the application with which to associate
your request set from the list of values.
5. Enter a Description for your request set.
n l y
Defining A Request Set
e O
(N) Requests > Set
U s
The Owner field defaults to your user name and can be changed only by your system
administrator.
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 67
Defining Request Sets Step 1: Enter Request Set Name

Step 1: Enter Request Set Name
6. Enter Active Dates From and To fields to define an

effective period.
7. Enable or disable Print Together as appropriate.
8. Enable Allow Incompatibility as appropriate.
9. Click Define Stages to define the stages for your
request set.
n l y
Defining A Request Set (continued)
e O
will not be available in the Submit Requests window.
U s
If the current date is outside the Active Dates From and To range you define, the request set
they complete.
a l
Selecting the Print Together check box will send all your requests to the printer together when
r n
Selecting the Allow Incompatibility check box allows your system administrator to specify
nt e
programs that are incompatible with this request and may not run with it.
e I
c l
r a
O

Chapter 3 - Page 68
Defining Request Sets Step 2: Define a Stage

Step 2: Define a Stage
1. Enter a name for your stage.
2. Enter a description for your stage.
3. Enter a short code for the stage.
4. Use the LOV in the function field to select a
function.
5. Enable the Return Value of this Stage Affects the
Set Outcome check box as appropriate.
6. Enable the Allow Incompatibility check box as
appropriate.
7. Click Requests to display the Stage Requests
window.
n l y
Stages
e O
(N) Requests > Set > (B) Define Stages
Defining Stages
U s
l
The value for the Display Sequence field is defaulted in sequence as you enter your stages.
a
r n
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
nt e
on the normal completion status of the requests it contains.
e I
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.
c l
r a
O

Chapter 3 - Page 69
Defining Request Sets Step 3: Enter Requests for Stage

Step 3: Enter Requests for Stage
1. Select the report or program that you want to
include in this stage.
2. Specify the number of copies of output to print, the
style to print, and the printer to print to.
3. Enable the Save check box as appropriate.
4. Enable the Allow Stage Function to Use This
Program’s Results check box as appropriate.
5. Click Parameters to display the Request
Parameters window.
n l y
Defining Stages (continued)
e O
(N) Requests > Set > (B) Define Stages > (B) Requests
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 70
Defining Request Sets Step 4: Enter Request Parameter

Step 4: Enter Request Parameter
1. Select the Display check box as appropriate.
2. Select the Modify check box as appropriate.
3. Use the Shared Parameter field to set a default
value for a parameter that occurs in more than one
report or program of a request set.
4. Save your work.
n l y
Request Parameters
e O
((N) Requests > Set > (B) Define Stages > (B) Requests > (B) Parameters
Request Parameters Window
U s
l
Use the Request Parameters window to customize the parameter values of a specific request in
a
r n
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 multirow
nt e
portion of the window lists the parameters for that request.
e I
• The Sequence and Prompt fields are display only.
• Selecting the Display check box specifies that you can see a request parameter at
submission time.
c l
r a
• Selecting the Modify check box to specifies that you can insert or change the value for a
request parameter at submission time.
O
• 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 that you can avoid typing the
same value all over again for every occurrence of the parameter.

Chapter 3 - Page 71
Defining Request Sets Step 5: Link Stages

Step 5: Link Stages
1. Navigate to the Link Stages window.

2. Choose the start stage from the LOV of the stages
you defined for your set.
3. Enter the stages that you want to run in the
Success, Warning, and Error columns.
4. Click Done when you are finished.
n l y
Linking Stages in a Request Set
e O
(N) Requests > Set > (B) Link Stages
U s
Success, Warning, and Error columns - To ensure that a particular stage follows the preceding
a l
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
r n
specifically indicate which stage should follow for a completion status, the request set will exit
on that completion status.
nt e
e I
c l
r a
O

Chapter 3 - Page 72
Submitting a Request Set
Submitting a Request Set
1. Navigate to the Submit Request Set window.
2. Follow the instructions for Submitting Requests

presented earlier.
n l y
Who Can Use a Request Set
e O
(N) Requests > Run > (Option) Request Set > (B) OK
U s
After you define a request set, it becomes your private request set. You can run it as long as
requests.
a l
you have access to a standard Submit Request window that does not limit access to specific
r n
Other users can run the request set only if your system administrator assigns the request set to
nt e
their responsibility’s request group. It is possible to have a request set in your request group
that contains individual requests that are not in your request group, but you can only edit
I
request sets that you own. You can add any requests in your request group to the request set.
e
c l
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,
r a
the request set must be in your request group.
O

Chapter 3 - Page 73
User Request Set Privileges
User Request Set Privileges
Own
Sets Change
Privilege: Create Edit Created
Contain Owners
Sets
Request
User: Yes Own Group’s Yes No
Reports
n l y
Request Set Privileges
e O
Application User Editing Privileges
U s
You can control request set ownership to manage request set editing and run privileges.
l
• Application users define a request set by selecting reports or other concurrent programs
a
r n
from their current responsibility’s request security group.
• Application users automatically own the sets that they create.
nt e
• Application users can always edit the sets that they own. They cannot edit a request set that
they do not own.
e I
Request Sets and Request Security Groups
c l
• After changing responsibilities, application users can add reports from their current (new)
r a
responsibility’s request security group to a request set that they own.
• After changing responsibilities, application users can delete reports from a request set that
O
they own, regardless of whether the report is in the new responsibility’s request security
group.

Chapter 3 - Page 74
System Administrator Request Set Privileges
Request Set Privileges
Own Change
Sets
Privilege: Create Edit Created Set
Contain
Sets Owners
Any
System: Yes All No Yes
Reports
n l y
System Administrator Request Set Privileges
e O
System administrators can edit and assign ownership of any request set.
System Administrator Editing Privileges
U s
l
• System administrators can define or edit a request set to include any standard submission
a
report or concurrent program.
r n
• System administrators do not automatically own the request sets that they define. Request
nt e
sets defined by a system administrator initially do not have an owner.
e I
• System administrators can assign or change ownership of any request set.
• If a request set is assigned to an owner but not to the owner’s request security group as
c l
well, the reports contained in the request set are available only to the owner.
r a
• 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
O
request set contains individual reports that are 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 3 - Page 75
Practice 4: Using Request Sets
Practice 4: Using Request Sets

• Create a simple Request Set using the Request Set
Wizard
• View and Test your Request Set (you must be
logged in as the “owner” of the set)
n l y
Instructions
e O
Substitute your initials for XXX.
Set Name: XXX Assistant System Administrator
U s
Set Code: will be assigned by Wizard
a l
r n
Description:
Owner:
nt e
will be assigned by the Wizard
I
Use the Requests Set Wizard to complete the setup for your request set; accept all of the
e
default values.
c l
Include the following programs in your request set:
r a
• Users of a Responsibility
O
• Reports and Sets by Responsibility
• Report Group Responsibilities

Chapter 3 - Page 76
n l y
Practice Solutions
e O
1. Navigate to (N) Requests > Set.
U s
2. Click the Request Set Wizard button (DO NOT enter any other information – the
Wizard will prompt you).
a l
3. Accept the following default values:
r n
• Run your set Sequentially. Click Next (this will create three stages).
nt e
• Abort your set when the status of the stage ends in Error. Click Next (this will link
the stages).
4. Enter the following:
e I
• Set:
c l XXX Assistant System Administrator
r
• Application:
a Application Object Library
O
• Description:
Click Next.
5. Accept the default As Each Request in the Set Completes. Click Next.
6. Select the following programs to be included in your set:

Chapter 3 - Page 77
• Users of a Responsibility
• Reports and Sets by Responsibility
• Report Group Responsibilities
7. Click Finish. A note appears telling you that your request set has been created and
saved. Click OK.
8. Verify the Owner field has the user name of the user you are currently logged in as.
Click Save. The window should appear similar to the example shown in the slide.
Verify and Run Your Request Set
9. Sign on as your XXX Assistant System Administrator.
10. Navigate to (N) Requests > Run. Select the Request Set option.
11. Click the list of values icon for the Request Set field. Your request set will
automatically display because it is the only set available to your Assistant System
Administrator responsibility.
12. Supply the required parameters by clicking in the Parameters field for each request.
13. Submit your set.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 78
Summary
Summary

• Submit and monitor a request
• Create a request group and assign it to a
responsibility
• Create a coded request group
• Create a request set
• Manipulate ownership of a request set
n l y
Lesson Summary
e O
U s
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
multiple reports.
a l
processing by setting default values for parameters and sharing parameter values among
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 79
Practice Prerequisites
The practices in this lesson assume that you have

completed the System Administration lesson “Managing
Application Security” and set up the following:
• Assistant System Administrator User
• Assistant System Administrator Responsibility
• System Auditor User
• System Auditor Responsibility
• System Auditor Custom Menu
n l y
Setup for Practice 2
e O
Responsibility, if necessary.
U s
Use the following data to create the Assistant System Administrator User and
l
Enter the following in the Responsibilities form (N) Security > Responsibility > Define.
a
Responsibility Name:
Application:
r n
Responsibility Key:
nt e
XXX_Asst_SysAdmin
Description:
e I Assistant System Administrator

Effective Dates:
Available From:
c l (accept the default system date)
Oracle Applications
Data Group:
r a Standard
Menu: O
Navigator Menu - System Administrator GUI
Request Group: (leave blank)

Chapter 3 - Page 80
Next create a user for the new responsibility. Enter the following information into the
Users form (N) Security > User > Define.
Description: XXX Assistant System Administrator
Password: WELCOME
Responsibility: XXX Assistant System Administrator
Setup for Practice 3

Use the following data to create the System Auditor menu, User, and Responsibility
required for this practice.
Create Your Menu:
Navigate to (N) Application > Menu and enter the data for your level 3 menu into the
appropriate fields on the form:
Level Three Menu
Menu Name: XXX_FLEX_SECURITY

10 Define Flexfield Security Rules Define Flex Security
Rule
20 Assign Assign Flexfield Security
Rule l y
Assign Flex Security
Rule
n
e O
Clear the form: (M) Edit > Clear > Form, or with your cursor in the Menu field, click New.
Level Two Menu

U s
Enter the data for your Level 2 menu into the appropriate fields on the form:

a l
r n
e
nt
Seq Prompt Submenu
e I Function Description
10 Define
c l Responsibilities Define Responsibilities
20 Request
r a Request Groups Define Request Group
Group
O
30 Flexfield XXX_FLEX_SECURITY Define and Assign Flex

Chapter 3 - Page 81
Clear the form: (M) Edit > Clear > Form or with your cursor in the Menu field, click New.
Enter the data for your TOP or Level 1 menu in the appropriate fields on the form:
Level One Menu

User Menu Name: XXX_TOP_SYSTEM_AUDITOR

10 Users User Menu - System Define and Monitor
Administrator GUI Users
20 Responsibilities XXX_RESPONSIBILITY Define Responsibility,

(your level two menu) Request Group,
Security Rules
30 Personal Profile Profile User Values View/Update Personal

Profile Options
40 Requests Requests Menu – Run and View Requests,

Other Responsibilities Define Request Sets
Assign Your Custom Menu to a New Responsibility

Navigate to (N) Security > Responsibility > Define and enter the data below into the
appropriate fields of the form: n l y
e O
U s
a l
Effective Date:
n
From: Today’s Date To: Leave Blank
r
Available From:
Data Group Name: Standard
nt e
Oracle Applications (default)
I
e
Menu:
Request Group:
c l XXX_TOP_SYSTEM_AUDITOR
leave blank
r a
O
Navigate to (N) Security > User > Define and enter the Data below into the appropriate
fields of the form:

Chapter 3 - Page 82
Password: WELCOME
Responsibility: XXX System Auditor
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 83
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 3 - Page 84
Administering Concurrent
Managers
Chapter 4
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Administering Concurrent Managers

Chapter 4 - Page 1
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 4 - Page 2
Objectives
Objectives

do the following:
• Define managers and their work shifts
• Specialize managers to run only certain programs
• Classify a program as a request type
• Control concurrent managers
• Manage parallel concurrent processing
• Use conflicts domains to maximize throughput
n l y
Lesson Aim
e O
U s
The Oracle system administrator is the end user’s first point of contact for system questions.
The system administrator should be able to monitor the processing of requests and deal with
a l
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
r
processing and also how to plan and schedule your workload.
n
nt e
e I
c l
r a
O

Chapter 4 - Page 3
Concurrent Requests, Programs, and Processes
Concurrent Requests, Programs, and

Processes
User requests System maintains Concurrent Managers

Concurrent List of requests to Read applicable
program Start concurrent programs Requests and start
Concurrent programs
Request Table
Run program ...
Run program X Concurrent Program X
Run program ... manager Started
n l y
Concurrent Requests, Programs, and Processes
e O
U s
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
l
program. Concurrent programs are started by a concurrent manager.
a
r n
nt e
e I
c l
r a
O

Chapter 4 - Page 4
Overview of Concurrent Processing
Request Table
Run program ...
Run program ...
User submits Run program ... Concurrent
request to run Run program abc manager
program abc Run program ...
Concurrent
manager
starts
program abc
n l y
e O
U s
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
table and start programs running.

a l
into a database table that lists all of the requests. Concurrent managers read requests from the
r n
Part of a manager’s definition is how many operating system processes it can devote to running
nt e
requests. This number is referred to as the manager’s number of target processes.
e I
c l
r a
O

Chapter 4 - Page 5
Defining a Concurrent Manager
Concurrent
Manager
Definition
Specialization Rules Program

Work Shifts
Run Program A Libraries
Define
Run Program B when a manager
reads requests
Define which requests (is enabled).
a manager can read.
Target Processes
For each work shift,
the maximum number
of programs the manager
can run simultaneously.
n l y
e O
during certain times of the day.
U s
Concurrent managers can be defined to process only certain types of requests and to operate
work shifts and associating the manager with a work shift.

a l
Scheduling Requests You can schedule when a manager operates by defining one or more
r n
Segregating Requests You can define specialization rules to identify the kinds of requests
nt e
that a manager will read. Specialize managers so that they only read requests to start certain
kinds of programs.
e I
c l
r a
O

Chapter 4 - Page 6
You can define as many concurrent managers as you

want. To define a manager:
• Assign a predefined library of immediate concurrent
programs to your manager
• Assign work shifts to your manager, which
determine what days and times the manager works
• For each workshift, define the maximum number of
operating system processes the manager can run
concurrently to read requests during the work shift
• Specialize your manager to read only certain kinds of
requests
n l y
e O
(N) Concurrent > Manager > Define
U s
The Parallel Concurrent Processing Details region of this window is discussed in a later lesson.
a l
r n
nt e
e I
c l
r a
O

Chapter 4 - Page 7
Defining Work Shifts
A work shift is a labeled duration of time:

• Hours in a day
• Days in a week
• Specific days in the year
n l y
e O
(N) Concurrent > Manager > Workshifts
U s
A concurrent manager operates only during its specified work shift. Use military time notation
to define a work shift—that is, use 24 hours rather than 12.
a l
r n
nt e
e I
c l
r a
O

Chapter 4 - Page 8
Balancing Process Workload Over Time
Balancing Process Workload

Over Time
12 AM 6 AM 12 PM 6 PM 11:59
00:00 06:00 12:00 18:00 23:59
Day work shift

three processes
Night work shift

six processes
Graveyard
work shift
six processes
n l y
Balancing Process Workload
e O
U s
You can create multiple work shifts for a concurrent manager to regulate the number of
operating system processes that the manager starts up at different times of the day and different
days of the week.
a l
r n
nt e
e I
c l
r a
O

Chapter 4 - Page 9
Work Shift Hierarchy
Work Shift Hierarchy
Hierarchy Work Shift Definition Example

Level
Specific date and April 15, 2001
1
range of times 8:00am–5:00pm
Specific date but April 15, 2002
2
no range of times
Range of days and Monday–Friday
3 8:00am–5:00pm
range of times
Range of days but Monday–Friday
4
no range of times
Range of times but
5 8:00am–5:00pm
no date and no range of days
Standard work shift; no date, 24 hours a day
6 days, or time defined 365 days a year
n l y
Overlapping Work Shifts
e O
U s
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.
a l
When work shifts with the same hierarchy level overlap, the work shift with the largest number
of target processes takes effect.
r n
nt e
e I
c l
r a
O

Chapter 4 - Page 10
Concurrent Managers Window: Program Libraries
Concurrent Managers Window: Program

Libraries
• A program library contains immediate concurrent
programs that can be called by your manager.
• Each manager can only run the immediate programs
included in its program library.
• An immediate concurrent program must be
registered with a program library before it can be run
by a manager.
• Application developers using Oracle Application
Object Library can register concurrent programs with
a program library, system administrators cannot.
n l y
Concurrent Managers
e O
Immediate Programs and Spawned Programs
U s
l
Immediate concurrent programs are C or PRO*C subroutines linked with concurrent managers.
a
r n
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
nt e
spawned program rather than as an immediate program.
Examples of these are:
e I
• FNDLIBR: Contains immediate concurrent programs used by Oracle Applications Object
Library.
c l
r a
• INVLIBR: Contains immediate concurrent programs used by Oracle Inventory.
• MFCLIBR: Contains immediate concurrent programs used by Oracle Manufacturing.
O
• PALIBR: Contains immediate concurrent programs used by Oracle Projects.

Chapter 4 - Page 11
Assigning Workshifts to a Manager
Assigning Workshifts to a Manager
• You can define the maximum number of programs

that a concurrent manager can run simultaneously
by assigning a number of target processes to a
work shift.
• Balance program processing across different time
periods by assigning your manager a different
number of target processes during different work
shifts.
n l y
Assigning Work Shifts to a Manager
e O
(N) Concurrent > Manager > Define > (B) Workshifts
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 4 - Page 12
Specializing a Concurrent Manager
You can use specialization rules to restrict a

concurrent manager to process only certain types of
requests:
• Define specialization rules to identify the types of
requests that a manager will read.
• Without specialization rules, a manager reads
requests to start any concurrent program.
n l y
e O
(N) Concurrent > Manager > Specialization Rules
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 4 - Page 13
Specializing a Concurrent Manager: Combined Rules
Specializing a Concurrent Manager:

Combined Rules
Whenever you have a generalized rule that is

appropriate for many different concurrent managers,
you should consider turning the rule into a combined
rule.
• A combined rule is a specialization rule with its own
name.
• Combined rules provide easy maintenance.
n l y
Combined Rules
e O
(N) Concurrent > Manager > Rule
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 4 - Page 14
Specialization Rules
Specialization Rules
Action
Action
Action Action Type
Type Application
Application Name
Name
Include
Include Combined
Combined RuleRule Application
Application Varies
Varies
Exclude Oracle
Exclude Oracle ID ID name
N/A Varies
Program
Program Name Varies
request
Request Type
type Name Varies
User
User N/A Varies
Example Rules:
Include Oracle ID Oracle Purchasing
Exclude Request Type Oracle Purchasing Month-End Rep
n l y
Defining Specialization Rules
e O
manager’s behavior toward the request.
U s
Use actions and qualifications to define specialization rules. An action defines a concurrent
Include and Exclude Actions

a l
• The manager runs requests that are included.
r
• The manager does not run requests that are excluded. n
nt
• Exclusion rules override inclusion rules.e
Example Rules
e I
c l
The example rules would result in a manager’s reading requests for all programs assigned to
Oracle Purchasing except programs defined with the request type Month-End Rep.
r a
O

Chapter 4 - Page 15
Action Types
Action Types
Combined rule Program
Oracle ID Request type
User
n l y
Action Types
e O
request to which an action refers.
U s
Use action types to specify the actions of a manager. An action type specifies the type of
a l
• 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.
r n
nt e
• 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
I
specify the application and the program name.
e
c l
• Certain request types. For example, you could include for processing all programs that
had been defined as a request type of Month-End Reports.
r a
• Programs requested by certain users. For example, you could include for processing all
O
programs requested by the user Sysadm.
• Combined rule. A combined rule combines more than one action to generate a single rule.

Chapter 4 - Page 16
Combining Multiple Actions Within Rules
Combining Multiple Actions

Within Rules
Relationship
Effects of to Similar
Rule Type Action Multiple Actions Actions
More requests
Specialization INCLUDE read OR
rule
Fewer requests
EXCLUDE AND
read
Fewer requests
Combined INCLUDE AND
read
rule
Fewer requests
EXCLUDE AND
read
n l y
Combining Multiple Actions in Rules
e O
actions in a specialization rule.
U s
• Multiple include actions in a combined rule behave differently from other multiple include
a l
• A specialized include rule is associated with a specific concurrent manager. A combined
include rule is an independent rule possibly associated with multiple managers.
r n
• Multiple specialized include rules create OR clauses, allowing more requests to be read by
the manager.
nt e
reading the request.
e I
• Multiple combined include rules create AND clauses, further restricting a manager from
c l
r a
O

Chapter 4 - Page 17
Concurrent Request Types
Concurrent Request Types
You can classify as request types programs that users

request at the same time or that require similar
processing times:
• Use request types to save time when defining the
specialization rules of a concurrent manager.
• Use request types to let certain programs run
without having to wait for other types of programs
to finish processing.
n l y
Defining Request Types
e O
(N) Concurrent > Program > Types
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 4 - Page 18
Using Request Types
Using Request Types
Define a request type.
Assign the request type to the

appropriate concurrent programs.
Use the request type in

a specialization rule.
n l y
How to Define and Use Request Types
e O
There are three steps in defining and using request types:
U s
1. Identify a category of programs according to some criterion. Define a request type
for that category of programs.
a l
r n
2. Identify a concurrent program according to the new request type.
3. Use the new request type in a manager’s specialization rule.
nt e
e I
c l
r a
O

Chapter 4 - Page 19
Conflicts Domains
Conflicts Domains
Program A Program B Program A Program B
Domain 1 Domain 2
Logical Logical
database database
The concept of separate domains attempts to

maximize concurrency and thereby, the throughput of
the system in the suite of applications.
n l y
The Purpose of Conflicts Domains
e O
U s
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
within D2, they may run concurrently.

a l
submitted within the same domain. But, if A is submitted within domain D1 and B is submitted
Defining Conflicts Domains

r n
(N) Concurrent > Conflicts Domains
nt e
I
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
e
l
creates the incompatibility.
c
r a
In Oracle Applications data is stored in database tables that belong to a particular application.
Each table may also contain information used to determine what conditions need to be met to
O
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 4 - Page 20
• 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
hurt performance.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 4 - Page 21
Processing Conflicts Domains
Processing Conflicts Domains
• All programs are assigned to a conflict domain when

they are submitted.
• The concurrent manager assigns a conflict domain
based on the following hierarchy:
– A program parameter
– The profile option Concurrent: Conflicts Domain
– Standard default domain
n l y
Processing Conflict Domains
e O
U s
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
a l
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
r n
program parameter and the Concurrent: Conflicts Domain profile option has not been defined,
nt e
the Standard domain is used. The Standard domain is the default for all requests.
Each request submitted uses parameters that identify the records that it will access. For
I
programs that are defined with incompatibility rules the conflict domain parameter is used
e
c l
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
a
in some cases be selected in the parameters field of the Submit Requests form.
r
O

Chapter 4 - Page 22
Control Functions of Concurrent Managers
Control Functions of Concurrent Managers
Control concurrent managers by activating or

deactivating one or all of the managers:
• Activate All Managers Simultaneously
• Deactivate All Managers Simultaneously
• Activating and Deactivating Individual Managers
n l y
Activating and Deactivating Concurrent Managers
e O
(N) Concurrent > Manager > Administer
U s
You can control concurrent managers by activating or deactivating one or all of the managers.
l
Activate All Managers Simultaneously When you activate the Internal Concurrent Manager,
a
from the operating system.
r n
it starts up all the concurrent managers. You can activate the Internal Concurrent Manager
nt e
Deactivate All Managers Simultaneously When you deactivate the Internal Concurrent
I
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
e
system.
c l
r a
Activating and Deactivating Individual Managers You can activate individual concurrent
managers by using the Administer Concurrent Managers window. The Internal Concurrent
O
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 4 - Page 23
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. Cancels Deactivate Concurrent Manager and Terminate Requests and
Deactivate Manager Requests.
Restart Concurrent Manager Internal manager rereads the manager’s definition and the
rules for concurrent program incompatibilities.
Deactivate Concurrent Manager Deactivates the manager. All requests (concurrent
programs) currently running are allowed to complete 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.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 4 - Page 24
Internal Monitor and ICM
Internal Monitor and ICM
Concurrent
manager
Internal
Concurrent
Manager
Concurrent Concurrent
manager manager
Internal
Concurrent
Monitor
manager
Process
n l y
Internal Monitor Processes
e O
Processes.
U s
You can provide fault tolerance for the Internal Concurrent Manager by using Internal Monitor
a l
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
r n
must be active at all times, it needs high fault tolerance. To provide this fault tolerance, parallel
nt e
concurrent processing uses Internal Monitor Processes.
The sole job of an Internal Monitor Process is to monitor the Internal Concurrent Manager and
I
to restart that manager if it fails. The first Internal Monitor Process to detect the failure of the
e
c l
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
r a
have an Internal Monitor Process when you configure your system. You can also assign each
O
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 4 - Page 25
Defining a Transaction Manager
Defining a Transaction Manager
• Some forms require synchronous processing of

particular requests. Transaction managers handle
these synchronous requests.
• Each transaction manager is associated with a
particular data group. Transaction managers can run
requests submitted only from a responsibility
associated with the same data group.
• Use the Concurrent Managers window to define a
transaction manager.
n l y
Creating Custom Transaction Managers
e O
U s
Because forms must be precoded to submit synchronous requests, you do not usually need to
a l
create custom transaction managers. If you create custom data groups, you should create
custom transaction managers that use your custom data group. This applies only if the
r n
responsibilities using your custom data group access the forms submitting synchronous
nt e
requests. Consult your product documentation. In general, you should create custom
transaction managers whenever your custom data groups prevent your seeded transaction
managers from operating.
e I
c l
r a
O

Chapter 4 - Page 26
Viewing Log and Output Files

Log and output
files
Concurrent
manager
Internal
Concurrent
Manager
Concurrent Concurrent
manager manager
Internal
Concurrent
Monitor
manager
Process
n l y
e O
U s
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
a l
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
r n
install time. For more information, refer to the installation documentation for your platform.
nt e
• INVLIBR: Contains immediate concurrent programs used by Oracle Inventory.
• MFCLIBR: Contains immediate concurrent programs used by Oracle Manufacturing.
I
• PALIBR: Contains immediate concurrent programs used by Oracle Projects.
e
c l
r a
O

Chapter 4 - Page 27
Managing Parallel Concurrent Processing
Node Node Client
Database
Node Node
n l y
e O
or homogeneous networked environment.
U s
You can distribute concurrent processing across multiple nodes in a cluster, massively parallel,
Benefits of Parallel Concurrent Processing

a l
r n
• 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.
nt e
e I
• Adaptability: Integrate with platform-specific batch queue and load-balancing systems to
maximize concurrent processing performance on a particular platform.
c l
• Single Point of Control: Managers can be administered from any node.
Nodes
r a
• Each node consists of one or more processors (CPUs) and its associated memory.
O
• Each node has its own memory that is not shared with other nodes.
• Each node operates independently of other nodes except when sharing resources.

Chapter 4 - Page 28
Nodes and Concurrent Managers
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.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 4 - Page 29
Oracle Enterprise Manager
Console
Oracle
Management
Repository
Server
Node
Agent
n l y
e O
U s
Oracle Applications has integrated its concurrent manager administrative interface with Oracle
Enterprise Manager, thus enabling administrators to better manage their systems. Oracle
Applications instances on a system.

a l
Enterprise Manager provides a single point of administration for all available Oracle
r n
Oracle Enterprise Manager combines a central console, agents, common services, and tools to
nt e
provide an integrated, comprehensive system management platform for managing Oracle
products.
e I
c l
r a
O

Chapter 4 - Page 30
Oracle Applications Manager
Oracle Applications Manager
• Provides an Applications DBA-

oriented subset of the current
Oracle Applications System
Administration functions in a
new Oracle Applications
console.
• Allows the performance of many tasks for
several Oracle Applications instances from a
single Oracle Applications Manager console.
n l y
The Oracle Applications Manager
e O
U s
The Oracle Applications Manager is integrated with the Oracle Enterprise Manager. The
Oracle Applications Manager provides an Applications DBA-oriented subset of the current
of concurrent managers, processes, and requests.

a l
Oracle Applications System Administration functions. These functions include administration
r n
Note that this new functionality is in addition to the multi-window Oracle Applications forms,
nt e
and administrators can choose which tools they wish to use. Requests submitted within the
standard Oracle Applications windows can be viewed from the Oracle Applications Manager
I
console. Likewise, concurrent managers defined in the console can be accessed from within the
e
c l
Oracle Applications windows.
r a
Oracle Enterprise Manager Concepts Guide
O
Oracle Enterprise Manager Configuration Guide
Oracle Enterprise Manager Administrator’s Guide

Chapter 4 - Page 31
Management Pack for Oracle Applications
Extends Oracle Enterprise Manager to enable the

monitoring, diagnosing, and capacity planning of the
multitiered Oracle Applications environment.
Features include:
• Discovery and graphical representation of services
to be monitored.
• Automated data collection and management
services.
• Central monitoring and administration of remote
systems using intelligent agents.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 4 - Page 32

The Oracle
Applications
Manager applet
allows
administrators to
perform all
Concurrent
Manager
administration
tasks from the
Enterprise
Manager console.
Applications Manager features the same tree and

detail view as other Enterprise Manager tools.
n l y
Management Pack Tools
e O
Oracle Applications Manager Console
U s
The Oracle Enterprise Manager console is extended to discover concurrent managers and to
a l
notify you should any of the servers go down. You can also define jobs for any of the Oracle
Applications subsystems, allowing central administration of a distributed Oracle Applications
system.
r n
nt e
e I
c l
r a
O

Chapter 4 - Page 33
Advanced Events
Advanced Events
The Management Pack for Oracle Applications

adds nine Advanced Events to monitor
Concurrent Managers for specific conditions
that may require action.
n l y
e O
Advanced Events
U s
Oracle Applications Advanced Events is a library of events specific to Oracle Applications
a l
provided for lights-out event monitoring and problem detection. Additional lights-out problem
resolution is provided with fix-it jobs that are configured to run automatically when an event
r n
triggers. These fix-it jobs are either custom-built or chosen from a predefined set provided with
the Management Pack.
nt e
e I
c l
r a
O

Chapter 4 - Page 34
Oracle Performance Manager
Oracle
Performance
Manager allows
administrators
to monitor
performance
statistics for
Oracle
Applications
Concurrent Managers and
host operating systems. Administrators can
display this data in different chart formats.
n l y
e O
U s
A new Oracle Applications data gatherer cartridge feeds data to Oracle Performance Manager,
managers and Forms sessions that are used by your instance.

a l
providing you with an extensive array of real-time monitoring charts on all concurrent
r n
nt e
e I
c l
r a
O

Chapter 4 - Page 35
Oracle Capacity Planner
Oracle Capacity
Planner allows
administrators
to collect and
analyze
historical
performance
statistics from
Oracle
Applications
Concurrent Managers and host operating systems
to estimate future capacity requirements.
n l y
e O
U s
Concurrent manager performance data is gathered over time and fed to Oracle Capacity
l
Planner for analysis of resource consumption and detection of performance anomalies.
a
r n
nt e
e I
c l
r a
O

Chapter 4 - Page 36
Concurrent Processing Tuning Assistant
The Concurrent
Processing
Tuning Assistant
reports historical
information
about Oracle
Concurrent
Managers,
Concurrent
Programs, and Concurrent Processing Requests.
You can use these reports to achieve better
throughput and performance.
n l y
e O
U s
Concurrent Processing Tuning Assistant allows you to examine historical processing
l
information about Oracle concurrent processing requests and concurrent managers.
a
r n
nt e
e I
c l
r a
O

Chapter 4 - Page 37
Defining a Concurrent Manager Practice Instructions
Defining a Concurrent Manager Practice

Instructions

• Define a work shift
• Define a concurrent manager
• Assign your work shift to your concurrent manager
• Create Specialization Rules for your concurrent manager
• Activate the concurrent manager
n l y
Instructions
e O
Use your own initials when you see XXX below.
Create Your Workshift
U s
Name: XXX DAYSHIFT
a l
From: 08:00
r n
To: 17:00
From: Monday
nt e
To: Friday
e I
c l
Description: Dayshift 8:00 – 5:00
Define the Concurrent Manager
r a
Use the information below to define your concurrent manager:
O
Manager:
Enabled:
XXX Specialized Manager
(Checked)
Short Name: XXXSPECIAL

Chapter 4 - Page 38
Description: Concurrent Manager to run reports for XXX
Type: Concurrent Manager
Cache Size: 1
Program Library: FNDLIBR
Use the following information to assign the workshift to your manager:

Workshift: XXX DAYSHIFT
Processes: 3
Sleep Seconds: 60
Create Specialization Rules for the Concurrent Manager

Use the information below to define your specialization rules:
Include/Exclude: Include
Type: User
Name: (Your User)
Exclude Your User from the Standard Concurrent Manager

A concurrent program will run in whatever concurrent manager is available unless it has
been explicitly excluded from the manager. Exclude your user from the Standard
Manager by adding the following specialization rules to the Standard Manager:
Include/Exclude: Exclude
Type: User
Name: (Your User)
n l y
Activate Your Concurrent Manager
e O
s
1. In the Administer Concurrent Managers window scroll through the list of managers
until you find the manager you defined. Select your manager and click the Activate
U
button.
The status will update to Activating.
a l
r n
2. Go to the View Requests window to verify that your request to activate your manager
completes successfully.
nt e
I
Submit a Request for your Manager to Run
e
l
1. Go to the Submit Request window and submit the Active Users or Active
c
r a
Responsibilities report to run once every minute for the next five minutes.
2. Go to the Administer Concurrent Managers window. Your concurrent manager will
O
show one request pending.
3. Click on the Requests button to view your request in the Concurrent Requests screen.
4. Return to the Administer Concurrent Managers window and click on the Processes
button to view the Processes window.

Chapter 4 - Page 39
Practice Solutions
Practice Solutions
n l y
Practice Solutions
e O
Define Your Work Shift
1. Navigate to (N) Concurrent > Manager > WorkShifts.
U s
l
2. From the menu, select File > New, or click the New icon on the toolbar.
a
n
r
Name:
From:
XXX DAYSHIFT
08:00
nt e
To: 17:00
e I
From:
To:
c l
Monday
Friday
r a
Description: Dayshift 8:00 – 5:00
O
the slide.

Chapter 4 - Page 40
Practice Solutions
Practice Solutions
n l y
Practice Solutions (continued)
e O
Define the Concurrent Manager
1. Navigate to (N) Concurrent > Manager > Define.
U s
l
a
Manager: XXX Specialized Manager
r n
Enabled: (Checked)
Short Name: XXXSPECIAL
nt e
I
e
Type:
c l
Description: Concurrent Manager to run reports for XXX
Concurrent Manager
r
Cache Size: 1 a
O
Program Library: FNDLIBR
3. Save your work. Your completed form should appear similar to the example in the slide.
4. Click Work Shifts to display the WorkShifts window.

Chapter 4 - Page 41
Practice Solutions
Practice Solutions
n l y
e O
Define the Concurrent Manager (continued)
5. Use the following information to assign the work shift to your manager:
U s
Work Shift: XXX DAYSHIFT
a l
Processes: 3
r n
Sleep Seconds: 60
nt e
6. Save your work. Your completed Work Shifts form should appear similar to the example
shown in the slide.
e I
l
7. Close the Work Shifts window to return to the Concurrent Managers window.
c
r a
O

Chapter 4 - Page 42
Practice Solutions
Practice Solutions
n l y
e O
Create Specialization Rules for the Concurrent Manager
U
1. In the Concurrent Managers window, click the Specialization Rules button.s
2. In the Specialization Rules window enter the following:
a l
Include/Exclude: Include
r n
Type:
Name:
User
(Your User)
nt e
I
e
the slide.
c l
4. Close the Specialization Rules window to return to the Concurrent Managers window.
r
5. Save your work.a
O
Exclude Your User from the Standard Concurrent Manager
A concurrent program will run in whatever concurrent manager is available unless it has
been explicitly excluded from the manager. Exclude your user from the Standard
Manager by adding the following specialization rules to the Standard Manager:

Chapter 4 - Page 43
1. From the Concurrent Managers window, query up the Standard Manager.
2. Click the Specialization Rules button.
3. Enter the following into the Specialization Rules window for the Standard Manager:
Include/Exclude: Exclude
Type: User
Name: (Your User)
4. Save your work. Close the Specialization Rules window.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 4 - Page 44
Practice Solutions
Practice Solutions
n l y
e O
Activate Your Concurrent Manager
U s
1. Navigate to the Administer Concurrent Managers window: (N) Concurrent > Manager >
Administer.
a l
r n
2. In the Administer Concurrent Managers window scroll through the list of managers until
you find the manager you defined. Select your manager and click the Activate button.
nt e
3. The status will update to Activating. The window will appear similar to the example
shown on the slide.
e I
4. Go to the View Requests window (N) Requests > View to verify that your request to
l
activate your manager completes successfully.
c
r a
O

Chapter 4 - Page 45
Practice Solutions
Practice Solutions
n l y
e O
Submit a Request for your Manager to Run
U s
2. Choose Single Request.
a l
n
3. In the Submit Request window choose the Active Users or Active Responsibilities report.
r
4. Click the Schedule button.
nt e
5. Choose Periodically. Leave the Start At time as the current time and enter five minutes
I
from now for the End At time.
e
c l
6. In the Re-run every field select 1 and Minute(s). To run the report once a minute for
the next five minutes.
r a
7. Click OK and then click Submit.
O
8. Go to the Administer Concurrent Managers window (N) Concurrent > Manager >
Administer. Your concurrent manager will show one request pending as shown in the
example above.
Note: You may have to close and reopen the Administer Concurrent Managers
window until you “catch” your process running.

Chapter 4 - Page 46
Practice Solutions
Practice Solutions
n l y
e O
Submit a Request for your Manager to Run (continued)
U s
9. Click on the Requests button to view your request in the Concurrent Requests screen.
l
10. Close this window to return to the Administer Concurrent Managers window.
a
r n
nt e
e I
c l
r a
O

Chapter 4 - Page 47
Practice Solutions
Practice Solutions
n l y
e O
Submit a Request for your Manager to Run (continued)
11. Click the Processes button to view the Processes window.
U s
l
In the Concurrent Processes screen note that you see all of the requests that have run in
a
r
UNIX Process ID (in the System column) that was used. n
your specialized manager, the Oracle Process ID that was used to run the report, and the
nt e
e I
c l
r a
O

Chapter 4 - Page 48
Summary
Summary
• You should now be able to do the following:

• Change the status of requests when necessary
• Review log files to identify problems
• Manage memory usage of concurrent processing
files and tables
• Balance manager processes over different periods
of time to optimize throughput.
n l y
Lesson Summary
e O
of Oracle Applications is a very important job of the system administrator.
U s
In addition to controlling access to Oracle Applications, monitoring the day-to-day processing
a l
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
r n
access to several application log files containing diagnostic information that can be of use in
correcting problems.
nt e
The system administrator is also responsible for balancing workload to maintain optimum
I
performance for users. He or she does this by creating concurrent managers to process user
e
c l
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
r a
managers in a parallel environment.
O

Chapter 4 - Page 49
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 4 - Page 50
Managing Profile Options
Chapter 5
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 5 - Page 1
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 5 - Page 2
Objectives
Objectives

do the following:
• Set profile option values
• Use user profile option settings as defaults for
concurrent program parameters or flexfield
segments
• Identify several typically modified profile options
n l y
Lesson Aim
e O
U s
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
l
operates. This lesson shows you how to specify these values.
a
r n
nt e
e I
c l
r a
O

Chapter 5 - Page 3
Personal Profile Values
Personal Profile Values
Depending on the responsibility, many users can

change their personal options:
• Navigate to (N) Profile > Personal to see a list of the
Profiles already defined.
• If the User Value field is unprotected, you can select
a value for this profile option from the list of values
or enter a value directly.
n l y
For further information on using the Personal Profile Values window see:
e O
(Help) Oracle Applications User’s Guide > Profile Options >
Setting Your Personal User Profile
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 5 - Page 4
Profile Hierarchy Levels
Profile Hierarchy Levels
User level
Responsibility level
Application level
Site level
n l y
Setting Profile Hierarchy Levels
e O
U s
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
l
your installation site, select About Oracle Applications from the Help menu.
a
r n
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
nt e
options that can be set at the application-level override options set at the site level.
I
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
e
c l
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.
r a
User Level User-level settings apply to individual users, identified by their application
O
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.

Chapter 5 - Page 5
System Profile Options
System Profile Options
The system administrator can set profile options at any

level:
• Navigate to (N) Profile > System to see the Find
System Profile Values window.
• You can set a profile value at the user,
responsibility, site, or application level.
n l y
Setting System Profile Options
e O
U s
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.
a l
For a complete description of the fields in the System Profile Values window see:
r n
nt e
Setting Profile Options > System Profile Values Window
e I
c l
r a
O

Chapter 5 - Page 6
Using User Profile Values as Defaults
Using User Profile Values

as Defaults
Form Window Field
Concurrent Parameters Parameter Detail region—

Programs Default Type/Default Value
Request Set Report Default Type/Default Value

Parameters
Key Flexfield Segment Validation Information region—

Segments Default Type/Default Value
Descriptive Segment Validation Information region—

Flexfield Segments Default Type/Default Value
n l y
Default User Profile Values
e O
U s
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.
a l
• Enter the setting of a profile option as a default value by selecting Profile as the default
r n
type, and then enter the internal name (not end-user name) of the profile option as the value
in the Default Value field.
nt e
• Look up the internal name of the profile option in the User Profiles appendix of the Oracle
I
Applications System Administrator’s Guide.
e
c l
r a
O

Chapter 5 - Page 7
Auditing Related Profile Options
Auditing Related Profile Options
Option Values
AuditTrail: Activate Yes/No
Sign-On: Audit Level None

User
Responsibility
Form
n l y
How to Use Profile Options Related to Auditing
e O
AuditTrail: Activate
U s
These two profile options are used to enable auditing within Oracle Applications.
l
This option enables auditing of changes to database tables. AuditTrail tracks which rows in a
a
form or forms.
r n
database table or tables were updated, at what time, and which user was logged in using the
Sign-On:Audit Level
nt e
e I
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:
c l
• None – default value. No users will be audited.
r
terminals used. a
• User – tracks who signs on to your system, the times the users log on and off, and the
O
• Responsibility – performs the User-level audit as well as tracking the responsibilities the
users choose and how much time spent as each responsibility.
• Form – performs the Responsibility-level audit and also tracks the forms the users choose
and how long each form is used.

Chapter 5 - Page 8
Currency-Related Options
Currency-Related Options
Option Value
Currency: Negative Format <>, -, ( ), [ ]
Currency: Positive Format <>, -, ( ), [ ]
Currency: Thousands Separator Yes/No
n l y
How to Use Currency-Related Options
e O
The options shown in the figure control the editing of monetary fields.
Currency: Negative Format
U s
l
This option enables the user to select the indicators for a negative amount.
a
Currency: Thousands Separator
r n
of a thousand or more.
nt e
This option enables the user to request that a comma be inserted appropriately within a number
e I
c l
r a
O

Chapter 5 - Page 9
Flexfield-Related Options
Flexfield-Related Options
Option Value
Flexfields: AutoSkip Yes/No
Flexfields: Shorthand Entry Yes/No

Flexfields: Show Full Value Yes/No
Flexfields: Validate on Server Not Enabled
New Entries Only
Query and New Entry
All Entries
Flexfields: BiDi Direction Left to Right
Right to Left
Flexfields: LOV Warning Limit Number of Rows to Return
Flexfields: Open Descr Window Yes/No
n l y
How to Use Flexfield-Related Options
e O
AutoSkip
U s
The options shown on the figure control the behavior of flexfield processing.
l
As soon as you enter a valid value into a flexfield segment, AutoSkip automatically positions
a
your cursor in the next segment.
Shorthand Entry r n
nt e
This option controls the behavior of shorthand entry of flexfields if shorthand entry has been
defined.
Show Full Value
e I
c l
If both shorthand entry and a complete alias have been defined for a flexfield, and this option is
r a
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.
O
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.

Chapter 5 - Page 10
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.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 5 - Page 11
Online Reporting-Related Options
Online Reporting-Related Options
Option Value
RRA: Enabled Yes/No
RRA: Delete Temporary Files Yes/No
RRA: Maximum Transfer Size Number

of bytes
RRA: URL Valid URL
Concurrent: Attach URL Yes/No
n l y
How to Control Output Processing at the System Level
e O
RRA: Enabled
U s
The options shown in the figure control output processing at the system level.
l
Set this user profile to Yes to use the Report Review Agent to access files on concurrent
a
processing nodes.
RRA: Delete Temporary Files r n
nt e
When users use a custom editor to view a concurrent output or log file, the Report Review
e I
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.
c l
RRA: Maximum Transfer Size
r a
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 O
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.

Chapter 5 - Page 12
Concurrent: Attach URL
When a user submits a request and specifies people to be notified in the Completion Options
region of the Requests window, everyone is sent a notification when the request is finished.
When this option is set to Yes, the recipients also receive a URL that they can access to see the
request results.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 5 - Page 13
Personal Output Viewer Options
Personal Output Viewer Options
Option Value
Viewer: Default Font Size Point size value
Viewer: HTML c:/path/to/browser
Viewer: PDF c:/path/to/viewer
Viewer: PostScript c:/path/to/viewer
Viewer: Text c:/path/to/viewer
Concurrent: URL Lifetime Number of minutes
n l y
How the User Can Control Request Output
e O
U s
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
l
completion notifications to other people, a URL pointing to request results can be sent.
a
r n
nt e
e I
c l
r a
O

Chapter 5 - Page 14
User-Related Profile Options
User-Related Profile Options
Option Value
Concurrent: Report Access Level User/Responsibility
Concurrent: Attach URL Yes/No
Concurrent: Save Output Yes/No

Concurrent: Active Request Limit 3
Concurrent: Request Priority 1–99 (default = 50)
Concurrent: Sequential Requests Yes/No
n l y
How to Use User-Related Profile Options
e O
Concurrent: Report Access Level
U s
This option determines the level of output and log files that are available to a user for online
viewing.
a l
Concurrent: Attach URL
r n
Setting this option to “Yes” causes a URL to be attached to request completion notifications.
nt e
When a user submits a request, and specifies people to be notified in the defining completion
line.
e I
options region, a URL is appended to the notification that enables them to view the request on-
Concurrent: Save Output

c l
request.
r a
You can save your request outputs in a file if one is generated. This allows you to reprint a
O
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.

Chapter 5 - Page 15
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.
Concurrent: Sequential Requests
Setting this option to Yes forces requests to run sequentially in the order in which they were
submitted.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 5 - Page 16
Security Signon Profile Options
Security Signon Profile Options
Option Value
Sign-On:Notification Yes/No
Signon Password Hard to Guess Yes/No
Signon Password Length Minimum number of

Characters allowed
Signon Password No Reuse Number of days before

Reuse allowed
n l y
How to Use Security Signon Profile Options
e O
Sign-On:Notification
U
Setting this option to “Yes” displays a message at login that indicates:s
• Concurrent request failures since your last session
a l
an incorrect password
r n
• How many times someone tried to log on to Oracle Applications with your username and
nt e
• When the default printer identified in your user profile is unregistered or not specified
I
Signon Password Hard to Guess
e
c l
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:
r a
• It contains at least one letter and at least one number
O
• It does not contain the username
• It does not contain repeating characters
Signon Password Length
Signon Password Length sets the minimum length of an Applications signon password. If no
value is entered, the minimum length defaults to 5.

Chapter 5 - Page 17
Signon Password No Reuse
This profile option specifies the number of days that a user must wait before being allowed to
reuse a password.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 5 - Page 18
• Work with profile options at the personal and system
levels
• Modify personal profile option values
n l y
Instructions
e O
U s
In this practice you will deal with profile options at the personal level and higher. In most
cases, you will be only inquiring on existing values, although you can change the profile
option values at the personal level.
Using Profile Options at the Personal Level
a l
1. Navigate to (N) Profile > Personal.
r n
nt e
2. Query up the profile option Concurrent:Request Priority. Note its value here:
e I
__________________ Try to update the value.
(This option cannot be updated at the user level.)
c l
3. Query up the value for Java Color Scheme. Choose a color scheme from User Value list
r a
of values. Click Save.
4. Sign off and back on for your color scheme to take effect.
O
5. Query up the profile option Viewer: Default Font Size. If there is no value specified, set
it to 10 and click Save.
6. Query up the profile option Printer. Use the List of Values to change or add a value.
Click Save.

Chapter 5 - Page 19
7. Query up the option Concurrent:Hold Requests. Change the User Value to Yes. Click
Save.
8. Navigate to the Submit Request screen (N) Requests > Run.
9. Select the Active Users program.
10. Click Options… and verify that the printer you selected for the Printer profile option has
defaulted in the Printer field.
11. Submit your request.
12. Navigate to the View Requests window (N) Requests > View.
13. Your request should show a status of On Hold.
14. Take your request off hold by clicking the Remove Hold button.
15. Cancel your request by clicking Cancel Request.
Using Profile Options at the System Level

1. Navigate to (N) Profile > System.
2. Use the Find System Profile Values window to find Currency:Negative Format a the
Site level.
3. Which of the following monetary displays matches the current setting of
Currency:Negative Format for the Site?
123.45- <123.45> (123.45) [123.45]
4. Use the Find System Profile Values window to find the Flexfields:Shorthand Entry
profile option at the Site and User level.
5. What is the default value at the Site level. At which levels can the System Administrator
change the values?
6. Use the Find System Profile Values window to find the GL Set of Books Name profile
n
option for the Application Oracle General Ledger and the Responsibility General Ledger
l y
Super User.
e O
set?
U s
7. Can this profile be set at the Application level? What is the current value and where is it
a l
r n
nt e
e I
c l
r a
O

Chapter 5 - Page 20
Summary
Summary

• Set user profiles as a convenience for your
application users
• Set user profiles to manage application user activity
• Use user profiles to provide default values for
concurrent program parameters or flexfield
segments
• Identify profile options typically modified by a user
n l y
Lesson Summary
e O
U s
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
defined profile values elsewhere in Oracle Applications.

a l
saw how to display and update profile values. You also learned how to reference previously
r n
nt e
e I
c l
r a
O

Chapter 5 - Page 21
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 5 - Page 22
Incorporating a Custom
Program
Chapter 6
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Incorporating a Custom Program

Chapter 6 - Page 1
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 6 - Page 2
Objectives
Objectives

do the following:
• Identify an executable to Oracle Applications
• Define a concurrent program
• Specify concurrent program parameter information
n l y
Lesson Aim
e O
U s
Oracle Applications uses concurrent programs to process and report on data stored in Oracle
Applications tables. These programs are secured, processed, and managed within the Oracle
a l
Applications environment, using the operations that you have seen in other lessons. However,
you can take your custom applications and programs and integrate them into the Oracle
r n
Applications environment as well. In that environment they can be secured and managed the
nt e
same way as regular Oracle Applications programs.
This lesson covers how to integrate user-developed programs into Oracle Applications.
e I
c l
r a
O

Chapter 6 - Page 3
Using Custom Programs in Oracle Applications
Using Custom Programs in Oracle

Applications
Oracle Applications
Accounts
Receivable Sales User program
n l y
Integrating Custom Programs with Oracle Applications
e O
U s
Although Oracle Applications provides you with a complete range of functionality, you may
need to develop and implement your own custom programs to perform specialized processing.
a l
You can integrate such custom applications into the Oracle Applications environment so that
they are processed like all your other Oracle Applications programs and reports.
r n
For example, a sales table used by Oracle Receivables can also be accessed by a user program
nt e
for special reporting needs. Such a user reporting program can be added to the Oracle
Applications environment.
e I
c l
r a
O

Chapter 6 - Page 4
Assumptions for Incorporating a New Program
Assumptions for Incorporating

a New Program
• The program has been completed

• The program parameters have been documented
• Any value sets needed already exist
• Tokens for Oracle Reports are defined
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 6 - Page 5
Components of a Concurrent Program
Custom application
Concurrent program
Input Parameters
Executable
code
n l y
e O
U s
You need to define several components of a concurrent program when adding your custom
program to the Oracle Applications environment. A concurrent program consists of an
a l
executable module—for example, an Oracle Reports program or a PL/ SQL procedure—and
the input parameters required by the program or procedure. A concurrent program must be
r n
associated with either an existing Oracle application or a custom application. In most cases,
nt e
you will associate any custom concurrent programs with a registered custom application. This
protects your concurrent programs during an upgrade.
e I
c l
r a
O

Chapter 6 - Page 6
Adding a Custom Program to Oracle Applications
Adding a Custom Program

to Oracle Applications
1. Develop the program or report.

2. Identify the program as an executable and register
it with an application.
3. Create a concurrent program containing the
executable and its parameters.
4. Add the concurrent program to a request group or
set for processing.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 6 - Page 7
Identifying the Executable
• The first step in adding a custom program to Oracle

Applications is to identify the program or report as
an executable.
• Use the Concurrent Program Executable window to
identify your executable to Oracle Applications.
n l y
e O
(N) Concurrent > Program > Executable
U s
The Concurrent Program Executable window prompts for the following information:
l
• Executable – enter a name for your concurrent program executable. In the Concurrent
a
r
concurrent program with your executable logic. n
Programs window you assign this name to a concurrent program to associate your
nt e
• Short Name – enter a short name for your concurrent program executable.
e I
• Application – the concurrent managers use the application to determine in which directory
structure to look for your execution file.
c l
• Execution Method – specifies the type of program, such as a PL/SQL procedure or an
r a
Oracle Reports program. The execution method cannot be changed once the concurrent
program executable has been assigned to one or more concurrent programs in the
O
Concurrent Programs window.
• Execution File Name – enter the operating system name of your execution file.
• Subroutine Name – enter the name of your C or Pro*C program subroutine. Only
immediate programs or spawned programs using the Unified C API use this field.

Chapter 6 - Page 8
Note: Defining new immediate concurrent programs is not recommended. Use either a
PL/SQL stored procedure or a spawned C program instead.
• Stage Function Parameters button – opens a window that allows you to enter parameters for
the Request set Stage Function. This button is only enabled when you select Request Set
Stage Function as you Execution Method.
Concurrent Program Executable Window
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 6 - Page 9
Creating the Concurrent Program
Creating the Concurrent Program
Use the Concurrent Programs window to define the details

about your concurrent program.
n l y
Concurrent Programs Window Fields
e O
(N) Concurrent > Program > Define
U s
Program – enter a descriptive name for your concurrent program. This is the name you see
a l
when you view your requests in the Requests window. If this concurrent program runs through
Standard Request Submission, you see this name in the Submit Requests window.
r n
Short Name – enter a short name that Oracle Applications can use to associate your program
with a concurrent program executable.
nt e
I
Application – the program’s application determines what ORACLE username your program
runs in and where to place the log and output files.
e
l
Enabled – indicate whether users will be able to submit requests to run this program and the
c
r a
concurrent managers will be able to run your program. Disabled programs do not display in
users’ lists, and do not appear in any concurrent manager queues.
O
Executable: Name – select the concurrent program executable that can run your program. The
executable is defined using the Concurrent Program Executable window.
Executable: Method – the execution method used by your concurrent program displays in this
field.

Chapter 6 - Page 10
Options – contains options for SQL*Report programs.
Priority – assign a priority for this program. If you do not assign a priority, the user’s profile
option Concurrent:Priority sets the request’s priority at submission time.
Request: Type – associate your program with a request type if desired. Certain concurrent
managers are specialized to run only certain request types.
Incrementor – for use by Oracle Applications internal developers only.
MLS Function – the MLS function used by the program (if applicable). The Multilingual
Concurrent Request feature allows a user to submit a request once to be run multiple tomes,
each time in a different language. If this program utilizes this feature the MLS function
determines which installed languages are needed for the request.
Use in SRS – check this box to indicate that this program can be run using Standard Request
Submission. If this box is checked, you must register the parameters of this program.
Allow Disabled Values – for a program authorized for SRS submission, check this box to
allow a user to enter disabled or outdated parameter values.
Run Alone – check this box if your program is incompatible with other programs in its logical
database and should therefore be run alone.
Enable Trace – turns on SQL tracing when program runs.
NLS Compliant – check this box if the program allows a request to reflect a language and
territory that are different from the language and territory that the user is operating in. This
option should be set only by the developer of the program. The program must be NLS
Compliant to utilize this feature. See: Oracle Applications Developer’s Guide.
Output Fields – use these fields to specify the handling or output from executions of this
program.
Concurrent Programs Window Buttons
Copy to… - choose this button to create another concurrent program using the same
executable, request, and report information. n l y
concurrent program when it is executed.
e O
Session Control – choose this button to specify options for the database session of the
U s
Incompatibilities – choose this button to open the Incompatible Programs window.
For more information see

a l
Parameters – chose this button to open the Program Parameters window.
r n
Concurrent Programs Window
nt e
e I
c l
r a
O

Chapter 6 - Page 11
Concurrent Program Parameters Window
Concurrent Program Parameters Window
• Use the Concurrent Programs Parameters window to

enter and update the program parameters that you want
to pass to the program executable.
• Program parameters defined here should match the
variables in your executable.
n l y
Concurrent Programs Parameters Window Fields
e O
(N) Concurrent > Program > Define > (B) Parameters
U s
Sequence – specify the sequence number for the parameter that you are defining.
Parameter – specify the parameter name.
a l
to your program.
r n
Enabled – disabled parameters are not displayed at request submission time and are not passed
nt e
Validation Information: Value Set – specify an independent, table, or nonvalidated value set
e I
for use in checking values passed for this parameter.
Default Type – if you intend to specify a default for this parameter, declare the default type.
c l
Default Value – for certain types of default, you can specify a default value to use. This
region. r a
default value appears automatically when you enter the parameter fields in the Validation
O
Required – choose this box if a value for this parameter is required by your program.
Enable Security – if the value set for this parameter does not allow security rules, this field is
display only. Otherwise, you can choose to apply any security rules defined for this value set
to affect your parameter list also.

Chapter 6 - Page 12
Range – choose either Low or High if you want to validate your parameter value against the
value of another parameter in this structure.
Display – indicate whether to display this parameter in the Parameters window when a user
submits a request to run this program form the Submit Requests window.
Display Size – enter the field length in characters for this parameter. The user sees and and
fills in the field in the Parameters window launched from the Submit Request window.
Description Size – enter the display length in characters for the parameter value description.
Prompt – enter a prompt to appear in the Parameter window of the Submit Request window.
Concatenated Description Size – enter the length for the parameter value description field.
This field displays all the parameter values as a concatenated string.
Token – this refers to the name of a keyword or parameter for an Oracle Reports program.
Entries in this field are case-sensitive. Any values entered in this field must exactly match the
value expected by the Oracle Reports program.
For a complete description of the fields in this window see
Concurrent Programs Window > Concurrent Program Parameters Window
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 6 - Page 13
Associating a Program with a Request Group
Associating a Program with a Request

Group
• For a concurrent program to be accessible and

eligible for submission, you must define it to a
request group.
• Use the Request Groups window to assign your
program to the appropriate request groups.
n l y
Associate a Program with a Request Group
e O
(N) Security > Responsibility > Request
Request Group Window Fields
U s
For the definition of the fields in this window see
a l
n
r
Request Group Window
nt e
e I
c l
r a
O

Chapter 6 - Page 14
Submitting the Concurrent Program
Submitting the Concurrent Program
Use the Standard Request Submission window to

execute the program.
n l y
(N) Requests > Run
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 6 - Page 15

• Register a Concurrent Program Executable
• Incorporate a program into Oracle Applications using the
Copy function
• Add your program to a Request Group
• Submit your program to run
n l y
Instructions
e O
U s
In this practice you will incorporate a program into Oracle Applications. You will not actually
create a new program but will use an existing Oracle Applications reporting program instead.
a l
Identify the Executable
r n
Your first task is to identify the executable to Oracle Applications. Navigate to the Concurrent
nt e
Program Executable window and use the data below to fill out the window.
Executable:
Short Name:
e I XXXCPCRQ
XXXCPCRQ
Application:
c l Application Object Library
r
Description:
a XXX Custom Completed Concurrent Requests
O
Execution Method:
Execution File Name:
Oracle Reports
FNDCPCRQ
Define the Concurrent Program

Chapter 6 - Page 16
After you have created your executable, you need to create a concurrent program to contain it.
Query up the Completed Concurrent Requests program in the Concurrent Programs window
and use the Copy to button to create your custom program.
Program: XXX Completed Concurrent Requests
Short Name: XXXCPCRQ
Choose to Include Program Parameters when copying
Choose to Include Program Incompatibilities when copying
Add the Program to a Request Group

Add the program to the Request Group for your XXX Assistant System Administrator.
Test Your New Program

Sign on as your XXX System Administrator (XXXASSISTSA) and submit the request.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 6 - Page 17
Practice Solution
Practice Solution
n l y
Practice Solution
e O
Identify the Executable
U s
1. Navigate to the Concurrent Program Executable window (N) Concurrent > Program >
Executable.
a l
Executable: XXXCPCRQ
r n
2. Enter the following information in the appropriate fields:
Short Name:
nt e
XXXCPCRQ
Application:
e IApplication Object Library

Description:
Execution Method:
c l XXX Custom Completed Concurrent Requests
Oracle Reports
r a
Execution File Name: FNDCPCRQ
O
the slide.
4. Close the form.

Chapter 6 - Page 18
Practice Solution
Practice Solution
n l y
e O
Define the Concurrent Program
U s
1. Navigate to the Concurrent Programs window (N) Concurrent > Program > Define.
2. Query up the Completed Concurrent Requests program.
a l
3. Click the Copy to… button.
r n
Program:
nt e
4. In the Copy to window enter the following:
XXX Completed Concurrent Requests
Short Name: I
XXXCPCRQ
e
Application:
c l Application Object Library
Choose to Include Program Parameters when copying
r a
Choose to Include Program Incompatibilities when copying
O
5. Click OK to close the Copy to window.
6. Navigate to the Executable region of the form and replace the executable listed with the
executable you created (XXXCPCRQ).

Chapter 6 - Page 19
7. Click Save. Your completed form should appear similar to the example in the slide.
Close the form.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 6 - Page 20
Practice Solution
Practice Solution
n l y
e O
Add the Program to a Request Group
U s
1. Navigate to the Request Groups window (N) Security > Responsibility > Request.
l
2. Query up your request group XXX Assistant SysAdmin Group.
a
n
3. Insert a new record and the Program XXX Completed Concurrent Requests.
r
Close the form.
nt e
4. Save your work. Your completed form should appear similar to the example in the slide.
e I
Test Your New Program
c l
1. Switch Responsibilities to or log in as your XXX Assistant System Administrator.
r a
2. Navigate to the Submit Request form (N) Requests > Run. Click OK to submit a single
O
request.
3. Submit your new program and watch it run successfully.

Chapter 6 - Page 21
Summary
Summary
You should now be able to:

• Identify an executable to Oracle Applications
• Define a concurrent program
• Specify concurrent program parameter information
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 6 - Page 22
The practices in this lesson assume that you have

completed the System Administration lesson
“Managing Concurrent Programs and Reports” and set
up the following:
• Assistant System Administrator User
• Assistant System Administrator Responsibility
• Assistant SysAdmin Request Group
n l y
Practice Setup
e O
Assistant System Administrator Responsibility
U s
Use the following data to create the Assistant System Administrator User and
Responsibility, if necessary.
a l
Responsibility Name:
r n
Enter the following in the Responsibilities form (N) Security > Responsibility > Define.
Application:
nt e
Responsibility Key:
e IXXX _Asst_SysAdmin
Description:
Effective Dates:
c l Assistant System Administrator
(accept the default system date)
r
Available From: a Oracle Applications
O
Data Group:
Data Group Application:
Standard
Menu: Navigator Menu - System Administrator GUI
Request Group: (leave blank)

Chapter 6 - Page 23
Assistant System Administrator User
Next have your students create a user for the new responsibility. Enter the following
information into the Users form (N) Security > User > Define.
Description: XXX Assistant System Administrator
Password: WELCOME
Responsibility: XXX Assistant System Administrator
Assistant SysAdmin Request Group:

Navigate to (N) Security > Responsibility > Request and enter the data from the
instructions in the appropriate fields in the window.
Code: leave blank
Description: XXX Assistant SysAdmin Group
Requests
Type Name Application
Application Application Object Library Application Object Library
Program Employee Listing Oracle Payables
Set Period End Oracle Payables
Attach the Request Group to Your Assistant System Administrator Responsibility n l y

Navigate to (N) Responsibility > Define and Query up your Assistant System
e O
Administrator responsibility. Choose your request group from the list of values for the
Request Group Name field.
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 6 - Page 24
Auditing System Resources
Chapter 7
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 7 - Page 1
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 7 - Page 2
Objectives
Objectives

do the following:
• Identify different ways of auditing Oracle
Applications performance and resources
• Modify auditing related profile options
• Identify auditing related reports
• Selectively implement auditing as appropriate to
your environment
n l y
Lesson Aim
e O
U s
As system administrator you may audit application users and the changes that they make to
application data. You will learn how both of these options are set and why you use them.
a l
r n
nt e
e I
c l
r a
O

Chapter 7 - Page 3
Auditing Oracle Applications
Auditing Oracle Applications
Auditing user activity (Sign On Audit)
Auditing database row changes (AuditTrail)

Database Table Audit Table
n l y
Changes to Audit in Oracle Applications
e O
Sign-On Audit Feature
U s
Within Oracle Applications, you can audit user activity and database row changes.
l
The Sign-On Audit feature enables you to monitor user activity. You can audit at the user,
a
r n
responsibility, or form level. When you enable Sign-On Audit, you specify the desired level of
auditing. Sign-On Audit provides two methods for viewing audit data:
nt e
• The Monitor Users form provides online access to audit data.
AuditTrail Feature
e I
• Various Sign-On Audit reports are available.
c l
With the AuditTrail feature you can keep a history of changes to your important data: what
r a
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
O
that can be queried by using any standard Oracle SQL tool.

Chapter 7 - Page 4
Auditing User Activity
Auditing User Activity
Sign On Audit
profile option
Sign On Audit reports
Monitor Users form
n l y
Sign-On Audit Feature
e O
U s
You can audit and monitor user activity by enabling the Oracle Applications Sign-On Audit
feature. This enables you to track the activity of users signed on to Oracle Applications.
a l
Implement the Sign-On Audit feature by updating the Sign-On Audit Level system profile.
With Sign-On Audit you can choose whom to audit and what type of user information to track.
r n
You can selectively determine what audit information you need to match the needs of your
organization.
Sign-On Audit Reports
nt e
I
Sign-On Audit reports give you historical, detailed information on what your users do in your
e
Monitor Users Window c l
application. You control the data selected for the reports as well as how the data is presented.
r a
The Monitor Users window gives you online, real-time information about who is using Oracle
O
Applications and for what purpose.
You can see which users are signed on, which responsibilities, forms (windows), and terminals
they are using, as well as other information.

Chapter 7 - Page 5
Sign On Audit Profile Option
Sign On Audit Profile Option
Sign On Audit: None
Sign On Audit: User
Sign On Audit: Responsibility
Sign On Audit: Form
n l y
Sign-On Audit Levels
e O
U s
The Sign-On Audit 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.
a l
None This value is the default and disables the Sign-On Audit feature.
r n
User Auditing at the user level tracks who signs on to your system, the times that users log on
and off, and the terminals they use.
nt e
I
Responsibility Auditing at the responsibility level tracks all the information tracked at the
user level, including the responsibility that the user is using and how much time the user used
e
the responsibility.
c l
Form Auditing at the form level tracks all the information tracked at the user and
r a
responsibility levels as well as which forms the user chooses and how long he or she uses those
forms.
O

Chapter 7 - Page 6
Interaction of Sign On Audit Values
Interaction of Sign On Audit Values
Consultant
manager Sign On Audit: User
level
Consultant
responsibility Sign On Audit: Forms
level
Site level Sign On Audit: User
n l y
Specifying the Sign-On Audit Level
e O
U s
You can specify a Sign-On Audit value at multiple profile levels. A value in effect at a higher
level overrides a value at a lower level. For example, assume a scenario where your business
a l
regularly has independent consultants on-site whose activity you need to document for billing
purposes. In such a situation, you could use the following auditing setup:
r n
• At the site level specify Sign-on Audit: User to implement the minimum auditing level for
all users of Oracle Applications.
nt e
• Set up a custom responsibility to be used by your consultants. Set Sign-On Audit for this
I
responsibility to the responsibility or even the forms level.
e
to the user level.
c l
• At the user profile level for the manager overseeing the consultants, set Sign-on Audit back
r a
O

Chapter 7 - Page 7
Sign On Audit Reports
Sign On Audit Reports
Sign On Audit Forms Report
Sign On Audit Users Report
Sign On Audit Responsibilities
Sign On Audit Concurrent Requests Report
Sign On Audit Unsuccessful Logins Report
n l y
Reports
e O
On Audit. These reports are shown in the figure.
U s
The Sign-On Audit feature can generate several reports detailing information gathered by Sign-
• Sign-On Audit Forms

a l
• Sign-On Audit Users
• Sign-On Audit Responsibilities
r n
nt e
• Sign-On Audit Concurrent Requests Report
I
• Sign-On Audit Unsuccessful Logins Report
e
c l
r a
O

Chapter 7 - Page 8

Username
Login Name
Terminal Name
Responsibility Name
Start Active Time, End Active Time
Form Name
n l y
Using the Sign-On Audit Forms Report
e O
U s
Use the Sign-On 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:
a l
• Username: The Oracle Applications username of the user who accessed the form
r n
• Login Name: The operating system login name of the user who accessed the form
nt e
• Terminal Name: The operating system ID of the terminal from which the user accessed the
form
I
• Responsibility Name: The name of the responsibility from which the user accessed (The
e
Audit level.) c l
responsibility is displayed only if you audited the user at the responsibility or form Sign-On
r a
• Start Active Time/End Active Time: The dates and times when the user accessed and
O
exited the form (This information is displayed only if you audited at the form level.)
• Form Name: The name of the form that the user accessed (The form name is displayed only
if you audited the user at the form level.)

Chapter 7 - Page 9
Sign On Audit Concurrent Requests

Report
Login Name
Request ID
Concurrent Program Name
User Name
Responsibility Name
Form Name
Requested Start Time
n l y
Using the Sign-On Concurrent Requests Report
e O
You can use this report to view information about concurrent requests.
U s
• Login Name: The operating system login name of the user who submitted the concurrent
request
a l
r n
• Request ID: The concurrent request ID of the submitted concurrent request
• Concurrent Program Name: The name of the concurrent program that the user submitted
nt e
• User Name: The Oracle Applications username of the user who submitted the concurrent
request
e I
• Responsibility Name: The name of the responsibility from which the user submitted the
c l
concurrent request (The responsibility is displayed only if you audited the user at the
r a
responsibility or form level.)
• Form Name: The name of the form from which the user submitted the concurrent request.
O
(This information is displayed only if you audited the user at the form level.)
• Requested Start Time: The date and time when the request started running

Chapter 7 - Page 10
Sign On Audit Responsibilities Report
Username
Login Name
Terminal Name
Responsibility Name
Start Active Time/ End Active Time
n l y
Using the Sign-On Audit Responsibilities Report
e O
contains the following columns:
U s
You can use this report to view who is selecting what responsibility and when. The report
l
• Username: The Oracle Applications username of the user who selected the form
a
r n
• Login Name: The operating system login name of the user who selected the responsibility
• Terminal Name: The operating system ID of the terminal from which the user selected the
responsibility
nt e
I
• Responsibility Name: The name of the responsibility that the user used (The responsibility
is displayed only if you audited the user at the responsibility or form level.)
e
c l
• Start Active Time/End Active Time: The dates and times when the user selected or exited
r a
the responsibility. The start active time and end active time are displayed only if you
audited the user at the responsibility or form level.
O

Chapter 7 - Page 11
Sign On Audit Unsuccessful Logins

Report
Username
Login Name
Terminal
Attempt Time
n l y
Using the Sign-On Audit Unsuccessful Logins Report
e O
U s
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
a l
with an incorrect password. The report contains the following columns:
• Username: The Oracle Application username of the user who unsuccessfully signed on
r n
• Login Name: The operating system login name of the user who unsuccessfully tried to sign
on
nt e
to sign on
e I
• Terminal: The operating system ID of the terminal from which the user unsuccessfully tried
l
• Attempt Time: The date and time when the user unsuccessfully tried to sign on
c
r a
O

Chapter 7 - Page 12
Session Number
User Name
Login Name
Terminal Name
Start Active Time / End Active Time
ORACLE Process
System Process
n l y
Using the Sign On Audit Users Report
e O
following columns:
U s
You can use this report to view who signs on and for how long. The report contains the
application user sign-on

a l
• Session Number: The Oracle Applications session number uniquely identifying each
r n
• User Name: The Oracle Applications username of the user who signed on
nt e
• Login Name: The operating system login name of the user who signed on
e I
• Terminal Name: The operating system ID of the terminal from which the user signed on
• Start Active Time/End Active Time: The dates and times when the user accessed/ exited
c l
Oracle Applications (The start active time and end active time display only if you audited
r a
the user at the user Sign-on Audit level.)
• ORACLE Process: The Oracle Process ID used during the user’s sign-on
O
• System Process: The operating system process ID used during the user’s sign-on

Chapter 7 - Page 13
Monitor Users Window
Use this window to monitor what your application

users are currently doing:
• Monitor which users are signed on and what
responsibilities, forms, and terminals they are using.
• Monitor all users, individual users, or only users of a
specific application or responsibility.
n l y
e O
(N) Security > User > Monitor
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 7 - Page 14
Auditing Database Changes
Auditing Database Changes
Database Table Audit Table
INSERT
UPDATE
DELETE
n l y
Auditing Important Data
e O
U s
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
a l
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.
r n
AuditTrail tracks which rows in the database were updated. Audit information for each of these
e
changes is stored in audit tables that can then be queried and reported upon.
nt
e I
c l
r a
O

Chapter 7 - Page 15
Steps for Setting Up AuditTrail
Steps for Setting Up AuditTrail
1. Identify tables and columns to be audited.

2. Create audit group.
3. Specify columns for auditing.
4. Identify Oracle IDs to be audited.
5. Run AuditTrail Update Tables Report.
6. Develop auditing reports.
n l y
How to Set Up the AuditTrail
e O
subsequent slides.
U s
The figure shows the steps involved in implementing AuditTrail. These steps are covered in the
a l
• 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.
r n
nt e
• 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
I
that contains these related tables.
e
c l
• 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.
r a
• Enable auditing of a particular Oracle ID (schema) by defining audit installations. This
O
enables 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 7 - Page 16
Identify Tables and Columns to Audit
Identify Tables and Columns to Audit
RA_Customer_Trx AR_Adjustments_All
_Lines_All
AR_Cash_Receipts_All
n l y
Determining Columns and Tables to Audit
e O
U s
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
a
Adjustments table would be good candidates for auditing. l
receipts, columns from the Customer Transactions Lines table, the Cash Receipts table, and the
r n
nt e
e I
c l
r a
O

Chapter 7 - Page 17
Creating an Audit Group
Creating an Audit Group
Receivables Internal Control
RA_Customer_Trx AR_Adjustments_All
_Lines_All
AR_Cash_Receipts_All
n l y
Audit Groups
e O
U s
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.
a l
r n
nt e
e I
c l
r a
O

Chapter 7 - Page 18
Audit Shadow Tables
Audit Shadow Tables

AR_Adjustments_All AR_Adjustments_All_A
SQL> DESC AR_Adjustments_ALL_A;

NAME NULL? TYPE
AUDIT_TIMESTAMP NOT NULL DATE

AUDIT_TRANSACTION_TYPE NOT NULL VARCHAR2(1)
AUDIT_USER_NAME NOT NULL VARCHAR2(100)
AUDIT_TRUE_NULLS VARCHAR2(250)
PRIMARY KEY NUMBER
CUSTOMER_TRX_ID NUMBER
APPROVED BY NUMBER
CREATED BY NUMBER
ACCTD_AMOUNT NUMBER
n l y
What Audit Shadow Tables Identify
e O
U s
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
a l
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
r n
ACCT._AMOUNT of the AR_ADJUSTMENTS_ALL table are being audited so the shadow
e
table includes these columns as well as the other columns required by the audit process.
nt
e I
c l
r a
O

Chapter 7 - Page 19
Shadow Table Views
Shadow Table Views
Shadow_Table_Name_A
Shadow_Table_Name_Avn Shadow_Table_Name_Acn
Basic table view Table changes view
n l y
Using Shadow Table Views
e O
U s
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
a l
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.
r n
The AC view enables you to reconstruct the value for a row at a given time while the AV view
e
provides simple access to when a value was changed.
nt
e I
c l
r a
O

Chapter 7 - Page 20
Audit Tables Window
Audit Tables Window
Use the Audit Tables window to:

• Identify which table you want to audit
• Identify the columns to be audited from that table
n l y
Audit Tables Window
e O
(N) Security > AuditTrail > Tables
For further descriptions of the Audit Tables window see:
U s
l
a
User and Data Auditing > Audit Tables Window
r n
nt e
e I
c l
r a
O

Chapter 7 - Page 21
Identifying the Schema to be Audited
Identifying the Schema to be Audited
You must enable auditing for the schema that owns

the tables identified in your audit group. Use the Audit
Installations window to specify this information.
1. Navigate to the Audit Installations window.

2. Enable the check box next to the schema that
you want to audit.
n l y
(N) Security > Audit Trail > Install
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 7 - Page 22
Enabling Audit Processing
Enabling Audit Processing
After you have specified all your audit information, you

must run the AuditTrail Update Tables report to enable
audit processing.
1. Navigate to the Submit Requests window.

2. Query up the AuditTrail Update Tables report in
the Submit Request window.
3. Submit the request.
n l y
(N) Requests > Run
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 7 - Page 23

• Use a signon audit report to determine what programs
were running during a specific time period
• Use a signon audit report to determine what
responsibilities were accessed and by whom
• Use a signon audit report to determine what forms were
accessed and by whom
• Monitor users using the Monitor Users window
n l y
Instructions
e O
Using Signon Audit Reports
Run the appropriate reports to determine the following:
U s
• What programs were run in the past week?
a l
n
• What Responsibilities were accessed in the past 2 days?
r
Using the Monitor Users Window
nt e
• What forms were used in the past day?
I
• Query all records in the Monitor Users form.
e
c l
• Note any activity (you must requery the form to update information).
• Change the Sign-On:Audit Level profile option for your specific user to the value
“None.”
r a
O
• Sign on again and query are records in the Monitor Users form.

Chapter 7 - Page 24
Practice Solution
Practice Solution
• Run the Signon Audit Concurrent Requests report

• Run the Signon Audit Responsibilities report
• Run the Signon Audit Forms report
• Monitor users using the Monitor Users window
n l y
Practice Solution
e O
Using Signon Audit Reports
U s
l
2. Click OK to accept the default to submit a single request.
a
n
3. Click the List of Values icon to get a list of all reports available for you to run.
r
Concurrent Requests report.
nt e
4. To determine what programs were run in the last week, select the Signon Audit
I
5. Enter the following in the Parameters window:
e
Sort By:
c l User Name
Request Start Time: one week ago (use the format 01JAN2002)
r
6. Click Submit. a
O
7. Answer “Yes” to submit another request.
8. To determine what responsibilities were accessed in the past 2 days, select the Signon
Audit Responsibilities report.

Chapter 7 - Page 25
Sort By: User Name
Request Start Time: 2 days ago ago (use the format 01JAN2002)
10. Click Submit.
11. Answer “Yes” to submit another request.
12. To determine what forms were used in the past day, select the Signon Audit Forms
report.
Sort By: User Name
Request Start Time: 1 day ago ago (use the format 01JAN2002)
14. Click Submit.
10. Answer “No” to close the Submit Request window.
11. Navigate to the Requests window (N) Requests > View to view your reports.
Using the Monitor Users Window
8. Navigate to the Monitor Users window (N) Security > User > Monitor.
9. Query up your User Name and note the activity.
10. Navigate to the Find System Profile Values window (N) Profile > System.
11. Find the Sign-On Audit Level profile option at the user level for your specific signon.
Change it to NONE.
12. Click Save to save your work.
13. Sign off and on again.
14. Navigate to the Monitor Users window again. (N) Security > User > Monitor.
15. Review the changes of the data in the form.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 7 - Page 26
Summary
Summary

• Identify different ways of auditing Oracle
Applications performance and resources
• Modify auditing-related profile options
• Identify auditing-related reports
• Selectively implement auditing as appropriate to
your environment
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 7 - Page 27
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 7 - Page 28
Managing Printers
Chapter 8
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Managing Printers
Chapter 8 - Page 1
Managing Printers
Managing Printers
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Managing Printers
Chapter 8 - Page 2
Objectives
Objectives

do the following:
• Define printer types
• Register a printer as a specific printer type
• Assign a print style and printer driver to a printer
type
• Create a custom print style and printer driver
• Create a custom SRW driver
n l y
Lesson Aim
e O
U s
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 shows you how to
accomplish both tasks.
a l
r n
nt e
e I
c l
r a
O
Managing Printers
Chapter 8 - Page 3
Formatting Information
Document formatting
(height, width)
Text formatting Printer formatting

(bold, underline) (portrait, landscape)
n l y
e O
document, and printer.
U s
For a printer to produce a report, it requires three basic types of formatting instructions: text,
Text Formatting
a l
r n
• 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.
nt e
Document Formatting
e I
• A SQL*ReportWriter (SRW) driver defines text formatting codes used by Oracle Reports.
c l
• The dimensions for a report output file are predefined as the number of columns and rows
r a
(width and height).
• A print style defines the dimensions for a report output file.
O
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 8 - Page 4
• A printer driver defines initialization and reset strings.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Managing Printers
Chapter 8 - Page 5
Oracle Print Definition Components
Oracle Print Definition Components
Printer type describes printer.
Printer style formats document.
Printer driver formats output.
SRW driver formats text.
n l y
Required Formatting Information for Components
e O
this figure.
U s
The formatting information required by your printer is specified by the components shown on
Printer Type
a l
r
DEC LN03 printer or an HP LaserJet III printer. n
Describes what kind of a printer you have. This is the manufacturer and model—for example, a
Printer Style
nt e
e I
• Describes how a report should be printed
• Determines the number of lines (rows) per page
c l
• Determines the width of each line (number of columns)
r a
• Controls whether to print a header page
O
Printer Driver
• Contains the set of commands that tell a printer how to print in the print style chosen
• Initializes printing orientation
• Resets printer driver’s instructions for next print job
Managing Printers
Chapter 8 - Page 6
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.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Managing Printers
Chapter 8 - Page 7
Relationships of the Printer Components
Relationships of the Printer Components
Print
styles
Page size
orientation Printer
Printers
types
Printer Make Op sys name

Reset drivers
model HP4FL1
LN03
Commands
n l y
How the Print Components Are Related
e O
U s
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
print definitions. The figure shows that:

a l
flexible method of defining your print environment. The printer type is at the heart of your
r
• A printer is registered as a printer type. n
nt e
• A printer style is associated with a printer type.
I
• A printer driver is assigned to a printer type.
e
c l
r a
O
Managing Printers
Chapter 8 - Page 8
Defining Printers
Defining Printers
Using predefined Using custom
components components
Define new type

(if needed)
Define new style

(if needed)
Define new
driver
Register printer Register printer

as predefined type as new type
n l y
How to Define Printers
e O
U s
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
printer as shown on the right.

a l
cases you must modify existing definitions or create new definitions to accommodate a new
r n
nt e
e I
c l
r a
O
Managing Printers
Chapter 8 - Page 9
Finding Existing Printer Types
Finding Existing Printer Types
• Before you can register a new printer, you need to

decide its type.
• Use the Printer Types form to view existing
combinations of print style and printer drivers to
decide whether an existing printer type supports
your new printer.
• Choose (M) View > Find All to see all the existing
definitions.
n l y
Printer Types Window
e O
(N) Install > Printer > Types
U s
l
(Help) Applied Technology > Oracle Applications System Administration > Printers >
a
r n
nt e
e I
c l
r a
O
Managing Printers
Chapter 8 - Page 10
Registering a New Printer
• To add a new printer for an existing printer type,

simply register the printer in the Printers window.
• If you need to define a new printer type, the Printer
Types button opens the appropriate window.
n l y
e O
(N) Install > Printer > Register
U s
l
a
Printers Window
r n
nt e
e I
c l
r a
O
Managing Printers
Chapter 8 - Page 11
Defining a New Printer Type
If an appropriate predefined printer type is not listed

you can define a new type of printer.
• Assign a style and a printer driver to print a report
in a specific style.
• The Style and Driver buttons open the appropriate
windows where you can define these items.
n l y
e O
(N) Install > Printer > Types
U s
l
a
r n
nt e
e I
c l
r a
O
Managing Printers
Chapter 8 - Page 12
Customization Materials for Oracle Applications Printing
Customization Materials for Oracle

Applications Printing
Printer Manual
Installing Oracle Applications
Oracle Applications System

Administrator’s Guide
n l y
Customization Considerations
e O
and custom print programs.
U s
You can customize Oracle Applications printer support components to use custom print styles
Materials Needed:
a l
r n
• 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
nt e
I
• Oracle Applications System Administrator’s Guide
e
c l
r a
O
Managing Printers
Chapter 8 - Page 13
Customizing Printer Components
Customizing Printer Components
Print style
Printer driver
SRW driver
n l y
Ways to Customize Printer Components
e O
You can customize your Oracle Applications printing capabilities by:
• Customizing a print style using the Print Styles window
U s
l
• Customizing a printer driver using the Printer Drivers window
a
n
• Creating or modifying an SRW (SQL*ReportWriter) driver using a text editor
r
nt e
e I
c l
r a
O
Managing Printers
Chapter 8 - Page 14
Customizing Print Styles
Customizing Print Styles
Rows (height)
Columns (width)
n l y
Customizing Print Report Rows and Columns
e O
(N) Install > Printer > Style
U s
You can define a custom print style to change the number of columns (width) and rows
(height) for a report.
a l
Style Requirements
r n
• A print style must satisfy the concurrent program’s definition of minimum and maximum
nt e
number of columns (width) and rows (height).
e I
• A print style must be assigned to the target printer type.
For a complete explanation of the fields in the Print Styles window see:
c l
a
Printer Styles Window
r
O
Managing Printers
Chapter 8 - Page 15
Customizing Printer Drivers
Printer driver
n l y
e O
(N) Install > Printer > Driver
U s
Printer drivers are responsible for communicating to the printer the information necessary to
a l
print the report in the style required by the printer style selected. Create custom printer drivers
to support print styles for new or existing printer types. Here are some other possible situations
r
in which you could need to define a new printer driver.n
nt e
• Customize a printer driver when a printer type requires different control characters.
I
• Customize a printer driver when the control characters have a different meaning because of
your operating system and platform.
e
l
• Customize a printer driver when language translation changes the meaning of the control
c
characters.
r a
• Customize a printer driver when the printer needs special control characters to select
O
different character sets.
• Customize a printer driver to change the printer’s default font for a report (Initialization
string only).
Managing Printers
Chapter 8 - Page 16
Refer to the printer manufacturer’s documentation for the control codes and escape sequences
the printer understands. Refer to the printer’s manual—for example, a PCL or PostScript
manual—for additional information if necessary.
For a complete explanation of the fields in the Printer Drivers window see:
Printer Drivers Window
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Managing Printers
Chapter 8 - Page 17
Invoking a Printer Driver
Print command and arguments Operating

system
Concurrent Custom
manager Arguments
program*
Print Command Operating

subroutine* system
Arguments
*Name specified on Printer Driver window
n l y
e O
There are three methods to invoke a printer driver.
Command
U s
l
• The concurrent manager issues an operating system print command and its arguments.
a
r
Arguments field of the Printer Drivers form. n
• An operating system print command along with all its arguments is entered in the
Program
nt e
program.
e I
• The concurrent manager calls a custom print program and passes arguments to the
c l
• The name of a custom print program is entered in the Name field, and any arguments to be
Subroutine r a
passed to the program are entered in the Arguments field of the Printer Drivers form.
O
• The concurrent manager calls a predefined Oracle Applications subroutine that passes a
print command and arguments to the printer via the operating system.
• A subroutine name appears in the Name field of the Printer Drivers form.
Managing Printers
Chapter 8 - Page 18
• The Arguments field is disregarded. The concurrent manager reads the Initialization and
Reset escape sequences.
• On UNIX systems this method, unlike the command method, does not start an operating
system shell along with the print command.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Managing Printers
Chapter 8 - Page 19
Passing Print Arguments
Passing Print Arguments
Destination of target printer
Number of copies to print
Name of file to print
Header page title
n l y
Types of Print Arguments Passed
e O
U
system print command it issues or a custom print program that it calls.s
You can rely on a concurrent manager to supply four values as arguments to the operating
Print Arguments
a l
• Destination or target printer
• Number of copies to print r n
• Name of the file to print
nt e
I
• Title that appears on the header page
e
Styles window.
c l
• The header page is printed when the Suppress Header Page field is set to No in the Print
Print Commands
r a
same. O
• Print commands vary; however, the tokens for which values are retrieved are always the
• Print commands are operating system-dependent. Refer to Installing Oracle Applications.
Managing Printers
Chapter 8 - Page 20
Using the Program Driver Method
Using the Program Driver Method
Concurrent Custom
manager Arguments
program*
*Name specified on Printer Driver window
n l y
Program Driver Method Considerations
e O
(N) Install > Printer > Driver
Location of Custom Print Programs
U s
l
To call a custom print program by using the Printer Drivers window, enter the program name,
a
r n
including the full path to the program, in the Program Name field. The path to the program
name is not necessary if the program location can be identified by the operating system’s
nt e
PATH environment variable—that is, it is in the $PATH variable name.
I
For platforms where the equivalent of a $PATH variable does not exist, use the full path name.
A path can be up to 255 characters.
e
l
Custom print programs are not registered as concurrent programs with Oracle Application
c
a
Object Library but are called after the concurrent process has completed.
r
O
Managing Printers
Chapter 8 - Page 21
Initiating Printing from a System Shell Script
Initiating Printing
from a System Shell Script
• Use the command

method or the printer
driver method.
• Place the script in the
appropriate directory.
System
Shell Script
n l y
How to Initiate Printing from a System Shell Script
e O
To initiate printing from an operating system shell script:
U s
• For operating system shell scripts, the printer driver method can be either Command or
l
Program, as long as you populate the argument field correctly.
a
should reside in $FND_TOP/$APPLBIN.
r n
• The script for a command shell procedure—for example, a UNIX shell or a VMS dcl—
nt e
e I
c l
r a
O
Managing Printers
Chapter 8 - Page 22
Printing from Standard Input Directly to the Printer
Printing from Standard Input

Directly to the Printer
• Invoke the printer driver

by using the command
method.
• Select the Standard Input
check box.
Command Method
n l y
How to Print from Standard Input
e O
a redirected source such as a file or the output of a program.
U s
Standard input refers typically to data or commands entered from the keyboard. It can be from
Examples of Using Standard Input

a l
r n
• When running a pipe in UNIX such as “cat filename | lpr” rather than just “lpr filename,”
the output file is sent to the stdin (standard input).
nt e
• The UNIX print command lpr accepts standard input when a filename is not specified.
Standard Input Settings
e I
• When you select the Standard Input check box, the printer driver can send standard input to
the printer.
c l
r a
• Clear the Standard Input check box if the driver method is Program or Subroutine or the
operating system print command or print program does not accept standard input.
O
• When the Standard Input check box is cleared, the print command issued by the concurrent
manager runs asynchronously. The concurrent manager issues the command and does not
wait for an operating system response.
Managing Printers
Chapter 8 - Page 23
Driver Method Parameters for Spooling
Driver Method Parameters

for Spooling
Check box cleared Check box selected
Concurrent Print
manager program
Temporary File Temporary File
n l y
Setting Spooling Specifications
e O
U s
A spool file contains a copy of a file to be printed and the initialization and reset strings of the
printer driver. Spooling is the process of sending a spool file to the spooling area of the printer.
Spool files are deleted after printing.
Spool File Check Box Selected
a l
r n
• Spool filing specifications are set on the Printer Drivers window in the Define Method
nt e
Parameters region. (N) Install > Printer > Driver.
I
• The Spool File check box is selected only if the print program creates its own temp file.
Selecting the Spool File check box prevents the concurrent manager from creating its own
e
temp file.
c l
r a
• When you select the Spool File check box, it is recommended that Initialization and Reset
fields are null and the Standard Input check box is cleared.
O
Spool File Check Box Cleared
• When the Spool File check box is clear, the concurrent manager makes a copy of the file to
be printed and sends the copy to the spooling area of the printer.
Managing Printers
Chapter 8 - Page 24
• Clear the Spool File check box when an operating system print command or a print
program does not make a copy of each file to be printed.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Managing Printers
Chapter 8 - Page 25
Initialization and Reset Field Contents
Initialization and Reset Field Contents
• Specified in the Printer Drivers window

• Control print orientation, character set, and line
density
• Nonprintable characters can be specified in octal
n l y
When to Use Initialization and Reset Strings
e O
escape sequences, or instructions.
U s
Edit Initialization and Reset strings when a printer type requires different control characters,
Initialization and Reset Strings

a l
density for your printer.
r n
• Use the Initialization and Reset fields to set and reset the orientation, character set, and line
nt e
• Initialization and Reset strings consist of control characters and escape sequences.
e I
• A control character can be represented by a caret (^) followed by another character.
• An escape sequence can be represented by a slash (/).
c l
Example: Escape Sequence
r a
For nonprintable characters, you can represent their value in octal mode. For example,
represent 0x26 as /046.
O
Managing Printers
Chapter 8 - Page 26
Creating a Custom SQL*ReportWriter Driver
Creating a Custom
SQL*ReportWriter Driver
1. Copy an existing .prt file and save.

2. Modify the new file with new control information.
3. Place the new file in $FND_TOP/$APPLREP.
4. Assign the new driver to a print style or printer
driver.
n l y
Creating a Custom SQL*ReportWriter Driver
e O
U s
Customize Oracle Reports SRW drivers if a printer type does not properly interpret the control
characters that set page breaks, or bold or underlined type in applications reports.
SRW Drivers
a l
r n
• SRW drivers are read by Oracle Reports when a report is generated and insert control
characters that tell the destination printer where to set page breaks and which characters to
format as bold or underlined.
nt e
I
• SRW drivers are designed for the DEC LN03 printer and all printers that understand the
same control characters as the LN03.
e
l
• An SRW driver is used during the generation of a report. A printer driver is used when the
c
r a
completed output file is sent to the printer.
• SRW driver files reside in $FND_TOP/$APPLREP and have the extension .prt.
O
Creating a New SRW Driver
1. Copy an existing SRW Driver (.prt file) and rename the copy before starting any text
editing.
2. Modify the new file with new control characters.
Managing Printers
Chapter 8 - Page 27
3. Place the modified copy of the SRW driver file in $FND_TOP/$APPLREP. Oracle
Reports will use the new driver if it is associated with a print style and/or printer driver
definition.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Managing Printers
Chapter 8 - Page 28
Sample SRW Driver File

srw driver-A.prt
printer”dec LN03 A4 Landscape”
height 62
width 132
between pages control(L)
return ””
linefeed control(J)
code”bold on” esc”[1m”

code”bold off” esc”[0m”
code”underline on” esc”[4m”
code”underline off” esc”[0m”
n l y
e O
typical SRW file.
U s
The slide shows the definition for the A.prt driver file and shows the information contained in a
a l
r n
nt e
e I
c l
r a
O
Managing Printers
Chapter 8 - Page 29
Order of Reading Printer Settings
Order of Reading Printer Settings
Concurrent programs
definition
Report set
definition
Printer user profile

option value
User submits report

to run
n l y
Hierarchy of Printer Assignments
e O
you can provide a default printer.
U s
You can restrict concurrent programs and reports to send their output to a specific printer, or
a l
• At the concurrent program level the system administrator can define a concurrent program
to always direct its output to only one printer. This setting cannot be overridden by users.
r n
• At the request set level, the system administrator can assign a default printer for each report
nt e
in the request set or for the entire request set. If the request set is unowned, no one can
override this setting.
I
• Also at the request set level, an application user can assign a default printer to a report
e
l
within the set or to the entire set. This value can be overridden by the administrator.
c
r a
• At the personal profile level, an application user can assign a default printer for all of his or
her reports. This value overrides any other values.
O
• At the site level, the system administrator can assign a default printer for all reports. This
can be overridden by users.
Managing Printers
Chapter 8 - Page 30
Testing Your Customization
Run report
New
printer
driver
Check
output
n l y
e O
are using.
U s
You can verify printer driver definitions by printing different styles from each printer type you
Initialization String
a l
r n
• Print a short report to verify that the page’s printing orientation is correct. Edit page
orientation instructions in the Initialization string.
nt e
• If you want to change the printer’s default font for the report, include that information in
the Initialization string.
Reset String
e I
c l
• Print two short reports with different printing orientations to verify that the printer is
r a
resetting itself properly.
• For example, print one report that is landscape and another that is portrait. Edit printer reset
O
instructions in the Reset string.
Arguments
• Print a short report to verify that the arguments to the operating system’s print command or
custom print program are being interpreted correctly.
Managing Printers
Chapter 8 - Page 31
• Check that the correct file is being printed at the destination printer and check the number
of copies that are printed. Edit arguments in the Arguments field.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Managing Printers
Chapter 8 - Page 32
Managing Printers Practice Instructions
Managing Printers Practice Instructions

• Define a Print Style
• Define a Printer Driver
• Define a Printer Type
• Register a Printer
n l y
Instructions
e O
initials for XXX.
U s
Use the information in the following charts as you complete the practice. Substitute your
Define a Print Style

a l
r n
Your printer style describes the appearance of your printed pages. This includes the orientation
as well as the number of columns and rows. Use the information below to define a new print
style.
nt e
Style Name:
e IXXX Portrait
Sequence Number: your student number + 300
User Style:
c l XXX Portrait
SRW Driver:
r a
Description:
P-XXX
(your description)
O
Layout Columns:
Rows:
80
66
Suppress Header: enabled
Orientation: Portrait
Managing Printers
Chapter 8 - Page 33
Define a Printer Driver
Use the information below to define a driver to be associated with your new print style. This
driver specifies the initialization and reset strings as well as other system-related information
Driver Name: XXX Printer Driver
User Driver: XXX - Portrait
Description: (your description)
SRW Driver: P–XXX
Platform: Windows - NT
Driver Method: Command
Arguments:
lp -c -d$PROFILES$.PRINTER -n$PROFILES$.CONC_COPIES
Initialization: /e[!p
Reset: /e[!p
Define a Printer Type

Your printer type definition specifies the allowable printer styles and drivers for your printer.
Use the information below and define all the printer styles and drivers listed
Type: XXX - HPLJ5
Description: (your description)
Style: Driver Name:
XXX Portrait XXX - Printer Driver
A4
DYNAMIC
A4PRINTCMDLQ1070
PORTRAITCMDLQ1070 n l y
LANDSCAPE LANDSCAPECMDLQ1070
e O
PORTRAIT PORTRAITCMDLQ1070
U s
Register Your Printers
a l
and associate a printer type with it.
r n
The last step in setting up your printers is to register your new printer with Oracle Applications
Printer:
nt
XXXCustome
Type:
Description:
e IXXX - HPLJ5
Printer for XXX’s office
c l
r a
Testing Your Definitions
O
To test your new printer definition, navigate to the SRS window and select a program for
execution. Go to the Options window and query up a list of available printers. Verify that your
new printer is listed.
Managing Printers
Chapter 8 - Page 34
Practice Solution
Practice Solution
n l y
Practice Solution
e O
Define a Print Style
1. Navigate to (N) Install > Printer > Style.
U s
l
a
Style Name: XXX Portrait
r n
Sequence Number:
User Style:
nt e
your student number + 300
XXX Portrait
SRW Driver:
e IP-XXX
Description:
Layout Columns:
c l (your description)
80
Rows:
r a 66
O
Suppress Header:
Orientation:
enabled
Portrait
3. Click Save to save your work. Your completed form should appear similar to the
Managing Printers
Chapter 8 - Page 35
n l y
e O
Define a Printer Driver
1. Navigate to (N) Install > Printer > Driver.
U s
l
a
Driver Name: XXX Printer Driver
r n
User Driver:
Description:
nt e
XXX - Portrait
(your description)
SRW Driver:
e I
P–XXX
Platform:
Driver Method:
c l Windows - NT
Command
Arguments:
r a
O
lp -c -d$PROFILES$.PRINTER -n$PROFILES$.CONC_COPIES
Initialization: /e[!p
Reset: /e[!p
Managing Printers
Chapter 8 - Page 36
4. Close the Printer Drivers form.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Managing Printers
Chapter 8 - Page 37
n l y
e O
Define a Printer Type
1. Navigate to (N) Install > Printer > Types.
U s
l
a
Type: XXX - HPLJ5
r n
Description:
Style:
nt e
(your description)
Driver Name:
XXX Portrait
e I
XXX - Printer Driver
A4
DYNAMIC
c l A4PRINTCMDLQ1070
PORTRAITCMDLQ1070
LANDSCAPE
r a LANDSCAPECMDLQ1070
PORTRAIT
O PORTRAITCMDLQ1070
Managing Printers
Chapter 8 - Page 38
n l y
e O
Register Your Printer
1. Navigate to (N) Install > Printer > Register.
U s
l
a
Printer: XXXCustom
r n
Type:
Description:
XXX - HPLJ5
nt e
Printer for XXX’s office
e I
c l
r a
O
Test Your Definitions
2. Click OK to submit a single request.
3. Click Copy… to show a list of your previously submitted requests.
Managing Printers
Chapter 8 - Page 39
4. Select one of these requests and click OK.
5. Click Options… to open the Upon Completion… window. Click the list of values icon
for the Printer field to verity that your printer is available.
6. Close this form and cancel the request.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Managing Printers
Chapter 8 - Page 40
Summary
Summary

• Register new printers
• Define new printer types
• Create a custom print style
• Create a custom printer driver
• Assign a print style and printer driver to a printer
type
• Create a custom SRW driver for formatting text and
page breaks
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Managing Printers
Chapter 8 - Page 41
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Managing Printers
Chapter 8 - Page 42
Applications DBA Duties
Chapter 9
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 9 - Page 1
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 9 - Page 2
Objectives
Objectives

do the following:
• Define resource consumer groups
• Assign users, concurrent managers, and concurrent
programs to a resource consumer group
• Run CBO statistics-gathering reports
• Use the Network Test window to evaluate your
network’s performance
n l y
Lesson Topics
e O
U s
The administration of Oracle Applications includes some duties that can fall to either the
Database Administrator or the System Administrator to perform. This lesson describes several
a l
security tasks from different functional areas, which encompass forms from various locations
on the System Administrator menu tree. These tasks are referred to as Applications DBA
duties.
r n
nt e
e I
c l
r a
O

Chapter 9 - Page 3
Resource Consumer Groups Have Similar CPU Usage
Requirements
Resource Consumer Groups Have Similar

CPU Usage Requirements
Users Concurrent
Programs
Concurrent
Managers
n l y
e O
Resource Consumer Groups: Definition
U s
Resource consumer groups and resource plans are tools used to allocate and manage resources
a l
among database users and applications. The database administrator establishes resource
consumer groups to define users, concurrent managers, or concurrent programs that have
r n
similar CPU usage requirements. An overall resource plan is used to specify how resources are
nt e
distributed among the different resource consumer groups.
I
System Administrator Assigns Resource Consumer Groups
Oracle Applications allows the system administrator to assign users, concurrent managers, and
e
l
concurrent programs to existing resource consumer groups.
c
r a
O

Chapter 9 - Page 4
Assigning Resource Consumer Groups
(N) Profile > System > (Check box) User
Users
(N) Concurrent > Program > Define >

(B) Session Control
Concurrent Programs
Concurrent Managers
n l y
Assign a User
e O
(N) Profile >System > (Check box) User
U s
The system administrator can assign a user to a resource consumer group by setting the value
see this profile option but cannot update it.

a l
of the user profile option FND:Resource Consumer Group for that particular user. The user can
Assign a Concurrent Program

r n
nt e
(N) Concurrent > Program > Define > (B) Session Control
e I
The system administrator can assign a concurrent program to a resource consumer group in the
Session Control window of the Concurrent Programs form.
c l
Assign a Concurrent Manager
r a
The system administrator can assign a concurrent manager to a resource consumer group in the
O
Concurrent Managers form.

Chapter 9 - Page 5
Hierarchy of Resource Consumer Groups

Transaction User Running a
Concurrent Manager Form
Program
Program User
Program
Profile Option
Transaction
Concurrent
Manager
Manager Default_Consumer_
Group
Profile option
Default_Consumer_
of submitting
Group
User
Default_Consumer_
Group
n l y
e O
Oracle Applications uses a hierarchy to resolve these conflicts.
U s
Conflicts can arise between the resource consumer groups associated with a single session.
Concurrent Manager Running a Concurrent Program

a l
r n
When a concurrent program is submitted the system first checks for the resource consumer
group assigned to the program. If none is assigned, the system will use the group assigned to
nt e
the manager. If none is assigned to the manager, the system will use the default:
Default_Consumer_Group.
User Performing a Transaction
e I
l
When a user performs a transaction, the system first checks the group assigned to the
c
r a
transaction. If none is assigned, the system checks the transaction manager. If the manager is
not assigned to a group, the system checks the user’s profile option. If the user does not belong
O
to a group, then the system uses the Default_Consumer_Group.
User Running a Form
When a user runs a form, the system first checks the user’s profile option. If the user is not
assigned to a group, the system uses the Default_Consumer_Group.

Chapter 9 - Page 6
Cost-Based Optimization
Cost-Based Optimization
Paths Statistics
Oracle Applications uses cost-

based optimization (CBO) to
choose the most efficient way
to execute SQL statements.
The optimizer determines the

most efficient execution plan
by considering available
access paths and factoring
Optimizer
information based on
statistics for the schema
objects’ SQL statement.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 9 - Page 7
CBO Statistics Gathering
CBO Statistics Gathering
To use cost-based optimization effectively, you must

keep your database statistics current. Oracle
Applications provides a set of concurrent programs to
help you collect these statistics:
• Gather Table Statistics

• Backup Table Statistics
• Restore Table Statistics
• Gather Schema Statistics
• Gather Column Statistics
n l y
CBO Statistics Gathering Reports
e O
U s
Gather Table Statistics – gathers table statistics for a specified table.
Backup Table Statistics – stores the statistics of the given table and backs up related index
and column statistics by default.
a l
r n
Restore Table Statistics – restores the previously backed up table statistics from a given
statistics identifier. All index and column statistics associated with the specified table are
imported as well.
nt e
I
Gather Schema Statistics – gathers specified schema-level statistics. Before gathering the
statistics, this program creates a backup of the existing statistics so that if database
e
status.
c l
performance is slowed after gathering new statistics, you can restore the system to its previous
r a
Gather Column Statistics – this program is actually two procedures that gather column
O
statistics. One procedure gathers the column statistics for all the columns specified in the
SEED data table FND_HISTOGRAM_COLS. The second procedure gathers the column
statistics for a specified column_name in a given table.
For further information on these reports see

Chapter 9 - Page 8
Cost-based Optimization > Concurrent Programs for CBO
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 9 - Page 9
Using the Network Test Window
Use the Network Test window to evaluate the performance of

your network with Oracle Applications.
The window provides the following tests:

• Latency Test - examines the time it takes for a single
packet to make a round trip from your client side
application to the server.
• Bandwidth Test - examines the data rate to see how
many bytes per second your network can transfer
from the server to the client.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 9 - Page 10
n l y
Running Network Tests
e O
(N) Application > Network Test
To Test Latency
U s
l
• Specify the number of Trials and the Iterations for each trial.
a
r n
• For each iteration, a single packet is sent from the client application to the server and back.
A trial consists of the specified number of iterations. The total time for all round trips in a
nt e
trial is divided by the number of iterations to obtain their average latency.
perform the test.

e I
• The default settings are 5 trials of 100 iterations each. Select the Run Test button to
To Test Bandwidth
c l
r a
• Specify the number of Trials and the iterations for each trial. For each iteration, several
kilobytes of data are sent from the client to the server and back. The form measures the
O
average rate at which the data travels.
• The default settings are 5 trials of 10 iterations each.
• Select the Run Test button to perform the test.
• Use the Clear Old Test Data button to purge previous test results from your database.

Chapter 9 - Page 11
Summary
Summary

• Define resource consumer groups
• Assign users, concurrent managers, and concurrent
programs to a resource consumer group
• Use the Network Test window to evaluate your
network’s performance
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 9 - Page 12
Assigning Resource Consumer Groups Example

Example
This example demonstrates how to assign a resource

consumer group to a user and to a concurrent
program.
n l y
Assigning Resource Consumer Groups Example
e O
Assign a User to the DEFAULT_CONSUMER_GROUP Resource Consumer Group
U s
1. Navigate to the System Profile Values find window: (N) Profile > System.
l
2. Check the User check box and select your user from the list of values.
a
Find.
r n
3. Select “FND: Resource Consumer Group” from the Profile list of values and click
nt e
4. The System Profile Values window will display. Select
Save your work.

e I
“DEFAULT_CONSUMER_GROUP” from the list of values under the User column.
c l
Assign a Concurrent Program to a Resource Consumer Group
r a
1. Navigate to the Concurrent Programs window: (N) Concurrent > Program > Define.
2. Find your program.
O
3. Click the Session Control button.
4. Use the list of values to select the consumer group to which you wish to assign the
program.
5. Save your work.

Chapter 9 - Page 13
CBO Review Question
CBO Review Question
Why is it important to keep your database statistics

current?
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 9 - Page 14
CBO Review Question
CBO Review Question
Why is it important to keep your database statistics

current?
• Because the cost-based approach relies on your
database statistics to accurately calculate the most
efficient execution plan for SQL statements.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 9 - Page 15
Using the Network Test Window Review Questions
Using the Network Test Window Review

Questions
Review Questions:
1. The __________ Test examines how long it takes
for a packet of information to make a round trip
from the client application to the server.
2. The __________ Test examines data rate to see how
many bytes per second your network can transfer
from the server to the client.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 9 - Page 16
Using the Network Test Window Review Questions
Using the Network Test Window Review

Questions
Review Questions:
1. The __Latency___ Test examines how long it takes
for a packet of information to make a round trip
from the client application to the server.
2. The __Bandwidth__ Test examines data rate to see

how many bytes per second your network can
transfer from the server to the client.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 9 - Page 17
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 9 - Page 18
Incorporating Custom Help
Files
Chapter 10
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Incorporating Custom Help Files

Chapter 10 - Page 1
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 10 - Page 2
Objectives
Objectives

do the following:
• Use the Help System Utility to download and upload
help files
• Use Oracle Applications special link syntax to link
your help files
• Use the Help Builder to customize Help Navigation
Trees
n l y
Lesson Aim
e O
U s
Oracle Applications uses an extensive network of help files to give users immediate online
assistance. You can customize these help files by manipulating the files supplied by Oracle, or
into Oracle Applications.

a l
by adding your own to the system. This lesson covers how to integrate customized help files
r n
nt e
e I
c l
r a
O

Chapter 10 - Page 3
Customizing Help
Customizing Help
Customizing your Oracle Applications help files

includes the following topics:
• Downloading help files
• Linking help files
• Uploading help files
• Updating the search index
• Customizing the navigation tree
n l y
Overview of Customizing Help Files
e O
U s
In order to customize help files you first must download them into an area for manipulation.
Oracle Applications provides the Help System Utility to download files. Oracle Applications
a l
help files are in HTML format, making them easy to modify using a commercial web
browser/editor such as Netscape Navigator. You can also add HTML and GIF files of your
own.
r n
nt e
Oracle Applications help files use a special link syntax that points the links to anchors within
files rather than to the files themselves. This method ensures that hypertext links will not be
I
broken if files are renamed or split. This lesson explains how to use this syntax, although it is
e
c l
not required for your custom help files.
When your changes are complete, use the Help System Utility to upload the files back to the
r a
appropriate Oracle Applications directory.
O
Rebuild the Search Index and use the Help Builder applet to update the navigation tree with
your new files.

Chapter 10 - Page 4
Oracle Applications Help System Utility
Oracle Applications Help System Utility
• Oracle Applications help files are stored in the

database
• The Help System Utility is provided for retrieving
and replacing them in the course of customization
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 10 - Page 5
Help System Utility Setup: Define Directory Paths
Help System Utility Setup:

Define Directory Paths
Set the directory paths in the following

Profile Options:
• Help Utility Download Path
• Help Utility Upload Path
n l y
Set Profile Options
e O
U s
Before using the Help System Utility you must define the upload and download directory
paths. Oracle Applications provides profile options for you to set these paths.
the Help System Utility will download files.

a l
Use the profile option Help Utility Download Path to define the directory location to which
r n
Use the Help Utility Upload Path to define the directory location from which your
nt e
customized files will be transferred back into the Oracle Applications Help System.
e I
c l
r a
O

Chapter 10 - Page 6
Downloading Help Files
Downloading Help Files
1. Identify the help system files you want

to customize
2. Identify the language and product of the
files
3. Use the Help System Utility to
download the files
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 10 - Page 7
Identify Help Files for Customization
Identify Help Files for Customization
• Open document in help system

• Use your Browser’s “View Source”
feature to view the HTML source
• The file name will be listed in the header
comments section of the HTML source
code
n l y
Identify Help Files
e O
U s
Help files are downloaded by file name. To identify the specific file that you want to
customize, open the document in the Oracle Applications Help System. Use the view source
the file name.

a l
function of your browser to view the HTML source code. The source information will include
r n
For example, this topic in the help system is found by navigating from the Help Library Tree to
nt e
Applied Technology > System Administration > Customizing Help > Downloading and
Uploading.
I
View the source of this file and you will see the following header comments:
e
l
<HTML DIR="LTR">
c
a


Chapter 10 - Page 8
<HEAD>
As you can see in the example, the file name is SYS00032663.htm.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 10 - Page 9
Identify the Language and Product of the Files
Identify the Language and

Product of the Files
• Open document in help system

• View the source of the document
• The final three nodes of the source
document URL are the language, the
product name, and the target
For example, the final three nodes
might be:
/US/FND/@ht_updown
n l y
Identify the Language and Product of the Help Files
e O
U s
To identify the language and product of the help file, use the source document URL. The final
three nodes of the source document URL are the language, the product name, and the anchor or
target name.
a l
Using this help file as an example again, the final three nodes of the URL are
/US/FND/@ht_updown.
r n
nt e
These nodes identify the language as US, the product name as FND, and the target name as
ht_updown.
e I
c l
r a
O

Chapter 10 - Page 10
Downloading Help Files for Editing
1. Open the Oracle Applications Help System

Utility
2. Select “Download Files from Help System”
3. Select the language
4. Select the product
5. Click Finish
n l y
e O
U s
You download help files by language and by product. That is, you select the language (for
example, US for U.S. English) and you select the product (for example, FND for Oracle
a l
Foundation or AR for Oracle Receivables). It is important to note the code for the product
because the product code determines the download directory.
Follow these steps to download help files:
r n
nt e
1. Open the Oracle Applications Help System Utility.
I
From Oracle Self Service Web Applications click on System Administration under
Web Based Applications. Under the Help Administration heading click on Help
e
System Utility.
c l
r a
2. Select “Download Files from Help System” from the Choose Action option group.
3. Select the language from the Choose Language pop list.
O
4. Select the product code from the Choose product pop list. You can only select one
product at a time.
5. Click Finish.

The Help System Utility will download the help files for the product you selected. All files
will be downloaded including graphics files. The files are downloaded following the path
defined in the profile option Help Utility Download Path, to a directory for the chosen
language and product.
For example, if you selected the language US and the product FND, the files will be
downloaded to <server location>\Help Utility Download Path\US\FND.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Linking Help Files
Linking Help Files
Link 1
Oracle Applications help files use
Link 2
Anchor 1 a special link syntax that
Link 3
Anchor 2 dynamically resolves links across
Anchor 3 files and applications.
Links point at a named anchor in a file rather

than the filename itself.
n l y
Oracle Applications Special Link Syntax: Overview
e O
them working even when files are renamed or split into parts.
U s
The Oracle Applications help system supports a special syntax for hypertext links that keeps
a l
Links in Oracle Applications help files point at a named anchor contained in the file rather than
the filename itself. The help system resolves the anchorname to file link dynamically, every
time a link is negotiated.
r n
nt e
Information on which files contain which anchornames is put into the help system
automatically on upload. Authors must ensure that anchornames are unique across an
I
application’s help files to prevent duplicate links.
e
c l
It is not required that you use Oracle’s special syntax for your custom help files. If you prefer,
you can always use conventional hypertext links based on filename.
r a
O

Special Syntax versus Conventional HTML
Special Syntax versus Conventional HTML
Conventional HTML:
For more about widgets, see
<AHREF=“#widgets”>All About Widgets</A>
below.
Special Syntax:
For more about widgets, see
<AHREF=“@widgets#widgets”>All About
Widgets</A> below.
n l y
Using the Special Syntax
e O
anchorname “widgets.”
U s
The conventional HTML example would allow the user to jump forward to a section with the
also between help files.

a l
Oracle Applications help files extend this HTML syntax to create links not only within, but
r n
To link to a file that contains a particular named anchor, you simply place an “@” before the
nt e
anchorname. To link to the precise spot within the file where the anchor appears, you append a
pound sign followed by the anchorname, just as you would in conventional HTML.
e I
c l
r a
O

Cross-Application Links
Cross-Application Links
General Syntax:
<AHREF=“../shortname/@anchorname#anchorname
”>link text</A>
Example:
Use the following link to jump to “All About Widgets”
in the Oracle Payables help directory from another
application help directory:
For more about widgets in Oracle Payables,
see <AHREF=“../AP/@widgets#widgets”>All
About Widgets</A>.
n l y
Using the Special Links Syntax Across Applications
e O
U s
In the Oracle Applications help system, all help files associated with a particular application
exist in the same directory, as far as their URL is concerned. Help files associated with other
directories are at the same level in the help system.

a l
applications exist in directories named after the application’s short name. All these application
r n
To create a link that goes to a help file associated with a different application, you create a
nt e
relative link that goes up a level to the parent of all help application directories, and then back
down through the other application’s directory, before concluding with Oracle Applications’
special link syntax.
e I
c l
r a
O

Related Topics Links
Related Topics links offer

access to pages related to the
current help topic.
n l y
e O
your links at multiple topics and files by using Related Topics links.
U s
Links are not limited to a single target in the Oracle Applications help system. You can point
containing a list of the related page links.

a l
When a user negotiates a Related Topics link, a page headed “Related Topics” appears
r n
nt e
e I
c l
r a
O

Related Topics Links Syntax
Related Topics Links Syntax
Use the following syntax to create a Related Topics

link:
<AHREF=“@anchorname1,anchorname2,anchorname
3”>Related Topics</A>
To include cross-application links, simply prefix the
application short name and a colon to the
anchorname:
<AHREF=“@anchorname1,shortname:anchorname2,
anchorname3”>Related Topics</A>
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Uploading Your New or Changed Help Files
Uploading Your New or Changed Help

Files
Once you have customized the help

files, use the Help System Utility to
upload the documents into the help
system.
Your files are uploaded from the
directory specified in the profile
option Help Utility Upload Path.
n l y
Note:
e O
U s
If you have created a new application with new help files that you are uploading for the first
time, you must use the Generic File Manager Access Utility (FNDGFU) to upload these files.
See
a l
Oracle Applications System Administration > Loaders > Generic File Manage Access Utility
for additional information.
r n
nt e
e I
c l
r a
O

File Upload Steps
File Upload Steps
1. Copy the customized files to

appropriate product folder in the
upload directory.
2. Open the Oracle Applications Help
System Utility.
3. Select “Upload Files from Help
System”
4. Select the language.
5. Select the product.
6. Click Finish.
n l y
File Upload Steps
e O
• HTML files (all HTML files must have a .htm extension)
U s
There are four types of files that can be uploaded to the help system. These are:
• GIF graphics files (must have a .gif extension)

a l
• Adobe Acrobat Files (must have a .pdf extension)
r n
nt e
• Cascading Style Sheets (must have a .css extension)
Follow these steps to upload your customized help files:
I
1. Copy the customized files to the appropriate product folder in the upload directory.
e
c l
- For example, if you customized six help files for Accounts Receivable, copy the six
files to the <server location><Help Utility Upload Path>\US\AR directory. You must
r a
copy the files to the correct product folder for the Oracle Applications Help System
Utility to place the files in the correct location within the Oracle Applications Help
O
System.
2. Open the Oracle Applications Help System Utility.

- From Oracle Self Service Web Applications click on System Administration under
Web Based Applications. Under the Help Administration heading click on Help System
Utility.
3. Select “Upload Files from Help System” from the Choose Action option group.
4. Select the language from the Choose Language pop list.
5. Select the product from the Choose Product pop list.
6. Click Finish.
The Help Utility uploads the help files for the product you selected. All files located in the
directory for the selected language and product will be uploaded.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Creating Reports
Creating Reports
The Help System Utility provides two reports for you to

cross-reference help targets and file names.
• Help Target to File Name Report – lists by target,
each file that contains the target, the document title
of the file, and the product.
• File Name to Help Target Report – lists every file
name and document title by language and product
and all the targets found within each file.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Running Reports
Running Reports
Follow these steps to run the Help System Utility

reports:
1. Open the Help System Utility
2. Select “Create Reports” from the Choose Action
option group.
3. Select the appropriate report from the Create
Reports pop list.
4. Select the language from the Choose Language
pop list.
5. Select the product from the Choose Product pop
list. To build reports for all products, choose “All
Products.”
6. Click Finish.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Updating the Search Index
Updating the Search Index
Run the aflobbod.sql script to rebuild the search

index after uploading your custom help files:
sqlplus <apps/pwd> @$FND_TOP/sql/aflobbld.sql
n l y
Rebuilding the Search Index
e O
U s
Oracle interMedia Text enables the search feature provided by the Oracle Applications help
system. Rebuilding the search index ensures that your custom files will be included in any
searches your users perform.
a l
r n
nt e
e I
c l
r a
O

Customizing Help Navigation Trees
Customizing Help Navigation Trees
Use the Help Builder applet to customize the help

navigation trees.
Trees are composed of a root, branches, and leaves:
• Root - is the top-most level. When expanded, it
reveals a collection of first-level nodes and
documents under it.
• Branch- expands to reveal nodes and documents
the next level down.
• Leaf - expands no further, but simply links to a
document, terminating the hierarchy.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Help Builder Functions
Help Builder Functions
Use the Help Builder to perform the following tasks:

• Open a tree for editing
• Add new help files to a tree
• Add new nodes to a tree
• Add nodes from one tree to another
• Change the organization of a tree
• Create a new navigation tree
n l y
To access the Help Builder navigate to OSSWA > System Administration > Help Builder.
e O
U s
a l
r n
nt e
e I
c l
r a
O

The Help Builder
The Help Builder
n l y
The Help Builder User Interface
e O
U s
The Help Builder window default view consists of three panes. The left pane displays the tree
that is currently selected. Use this area to manipulate your tree by adding nodes, deleting
nodes, and dragging nodes into the positions desired.
a l
The top right pane displays items matching the searches you have performed using the Find
r n
Documents or Find Trees functions. Switch from the Trees to the Documents display by
clicking on the tabs.
nt e
The bottom right pane is the Properties Pane. This area displays the properties of the item
I
(root, node, or document) currently selected. Those properties displaying enabled fields can be
e
updated.
c l
r a
O

Opening a Tree for Editing
Opening a Tree for Editing
1. Enter information on the tree in the Find Trees

window, and click Find.
For example, enter %Payables% in the Prompt field
to find the Oracle Payables tree.
2. Double-click the line in the Trees tab of the main
Help Builder window.
The tree’s top-level node, or root, appears in the
left pane. Expand and contract nodes to display
the part of the tree you want to edit.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Adding New Help Files to a Tree
1. After opening the tree for editing, click Find

Documents on the toolbar.
2. Enter information on the files you want to add,
enable “Exclude documents already on a tree,” and
click Find.
Files corresponding to your search criteria appear
on the Documents tab of the main Help Builder
window.
3. Drag files from the Documents tab and drop them
on the tree in the position desired.
n l y
e O
U s
Documents are listed by Target name. Therefore if a file contains multiple targets the file will
be listed multiple times. Be sure to choose the target or anchorname that corresponds to the
topic you want to add.
a l
If the topic you want to add is not the header target of the file, but a target within the
r n
document, you must supply the special link syntax in the Data field of the Properties Pane.
nt e
For example, the target name might appear in the Data field as @ht_updown. To link directly
I
to this anchor from the tree you will add #ht_updown to the end of the anchorname. The
resulting entry in the Data filed will be @ht_updown#ht_updown.
e
c l
r a
O

Adding New Nodes to a Tree
Adding New Nodes to a Tree
1. After opening the tree for editing, select the node

above the place where you want to add a new node.
2. Click New Node on the toolbar.
3. Enter information for the new node in the
Properties Pane. Be sure to select Node from the
Type list of values.
4. Click Apply.
5. To add a document to your new node, drag and
drop it directly on top of the node.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

For Further Information
For Further Information
For field reference definitions and information on

these topics:
• Copy nodes from one tree to another
• Change the organization of a tree
• Create a new navigation tree
See
(Help) Oracle Applications System Administration >
Customizing Help > …Navigation Trees
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Summary
Summary
You should now be able to:

• Download and upload help files
• Use Oracle Applications special syntax to link help
files
• Use the Help Builder to customize Help Navigation
Trees
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Demonstration: Using the Help Builder
Demonstration: Using the Help Builder
• Opening a Navigation Tree for editing

• Adding a new node to the tree
• Adding a new document to the tree
n l y
Using the Help Builder
e O
U s
This example demonstrates how you would open the Navigation Tree for editing and add a
node and documents to the tree. This example will show you how to access the Oracle
into this node.

a l
Applications AOL root, create a new node called “Personal Homepage” and copy documents
Opening the Tree for Editing

r n
nt e
• Navigate to the Help Builder: OSSWA > System Administration > Help Builder.
I
• In the Find Trees window, enter “Oracle Applications AOL” in the Prompt field and click
Find. The Oracle Applications AOL root will appear in the Trees tab in the upper right
e
l
pane of the Help Builder window.
c
r a
• Double-click “Oracle Applications AOL” on the Trees tab. This will display the tree in the
large left pane of the Help Builder window.
O
• Click on the + to expand the tree. Open the Oracle Applications User’s Guide node of the
tree
• Notice that as you click on various nodes and documents on the tree the Properties of the
selected item are displayed in the Properties pane.

Demonstration (Continued)
n l y
Add a Node to the Tree
e O
U s
• To add a node to the top of the User’s Guide, select the (opened) node “Oracle
Applications User’s Guide” and click the New Node icon. Your new node will be added as
the first child of the selected node.
a l
• In the Properties pane on the lower right, enter the name for the new node in the Prompt
field: “Personal Homepage.”
r n
• Click Apply.
nt e
Find and Add Documents to the Tree
e I
• Click the Find Documents icon on the toolbar to display the Find Documents window.
l
Enter “Getting Started%” in the Title field and check the Exclude documents already on a
c
r a
tree checkbox. Click Find.
- The Documents tab in the upper right pane of the Help Builder window will become
O
enabled and display a list of documents that match your search criteria.
• Select the document with title “Getting Started through the Personal Home Page.”
• Drag and drop the document directly beneath your new node. The document will
immediately appear on the tree.

• Click the Find Documents icon on the toolbar to display the Find Documents window.
Enter “%Personal Homepage%” in the Title field and check the Exclude documents
already on a tree checkbox. Click Find.
- The Documents tab in the upper right pane of the Help Builder window will become
enabled and display a list of documents that match your search criteria.
Note: The same document title will appear multiple times with different targets. This
is because the document contains multiple targets. When you add a document to a tree
the link is made to the file, not the anchor. To link to the anchor, use the special link
syntax in the Data field of the Properties Pane. See below.
• Select the document with Target “@icxphp.”
• Drag and drop the document directly beneath your first document. The document will
immediately appear on the tree.
• Change the “Personal Homepage in Oracle Applications” document to a node by selecting
the document on the tree and changing the Type field to “Node.” Click Apply.
• Click the + of your new node to open it. We will now add two more documents to this
node.
• From the Documents tab, drag the document with the target “@pageadm” beneath
“Personal Homepage in Oracle Applications” to add it as a child.
• In the Properties Pane change the title of the document to “Maintaining Tab Pages” and
click Apply.
• Now drag the document with the target “@custphp” to the position directly beneath
“Maintaining Tab Pages.”
• In the Properties Pane change the title of the document to “Customizing Tab Pages” and
click Apply.
• In the Properties Pane change the Data field to “@custphp#custphp” and click Apply. This
will create a link directly to the anchor in the file. n l y
• Save your tree and close the Help Builder.
e O
U s
a l
r n
nt e
e I
c l
r a
O

n l y
View Your Tree in Online Help
e O
U s
Open online help and click on the Oracle Applications User’s Guide. Click each of the nodes
and documents you created. Note that “Customizing Tab Pages” and “Maintaining Tab Pages”
actually link to different positions of the same file.
a l
r n
nt e
e I
c l
r a
O

n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Administering Folders
Chapter 11
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Chapter 11 - Page 1
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Chapter 11 - Page 2
Objectives
Objectives

do the following:
• Assign default folder definitions to a responsibility
• Assign default folder definitions to a user
• Assign ownership of a folder
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Chapter 11 - Page 3
Folders: Definition
Folders: Definition
A folder is a flexible entry and

display window in which you can
choose the fields you want to see
and where each appears in the
window.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Chapter 11 - Page 4
Administering Folders: Topics
Administering Folders: Topics
• Assigning default folder

definitions
– Responsibility
– Specific user
• Assigning ownership of a folder
• Deleting a folder
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Chapter 11 - Page 5
Assigning a Default Folder to a Responsibility
Assigning a Default Folder to a

Responsibility
1. Navigate to the Administer Folders window.

2. Select “Default folder assignments by
responsibility” and select a responsibility from the
list of values. Click Find.
3. In the Folder field use the list of values to enter the
name of the default folder you wish to assign to the
responsibility.
You can also enter the Folder Set name first to limit
the Folder list of values to those in that set.
n l y
Assign a Default Folder to a Responsibility
e O
(N) Application > Administer Folders
U s
Note: You must create default folders before you can perform the following functions. For
information on creating default folders see
a l
(Help) Oracle Applications User’s Guide > Folders >
r
Customizing the Presentation of Data in a Folder. n
nt e
Note: After you save a default folder definition for a folder set, that folder set no longer
appears in the list of values.
Form Fields
e I
c l
• Folder Set: Every folder set is associated with a particular folder block, and a user or
r a
responsibility can have one default folder within each folder set. The folder set name
generally describes the records shown in the block; some blocks may have multiple sets of
O
folders associated with them.
Chapter 11 - Page 6
Assigning a Default Folder to a User
Assigning a Default Folder to a User

2. Select “Default folder assignments by user” and
select a user from the list of values. Click Find.
3. In the Folder field select the default folder you wish
to assign to the user from the list of values.
You can also enter the Folder Set name first to limit
the Folder list of values to those in that set.
n l y
Assign a Default Folder to a User
e O
U s
Note: After you save a default folder definition for a folder set, that folder set no longer
appears in the list of values.
a l
Form Fields
r n
• Source Type: Enter either User or Responsibility. Records entered in this window use the
nt e
source type of User. If one of the current user’s responsibilities has default folders defined,
e I
the default folders are listed with a source type of Responsibility.
User defaults override Responsibility defaults. You cannot delete Responsibility default
folders in this window.
c l
a
• Responsibility: The Responsibility that uses this default folder definition.
r
O
Chapter 11 - Page 7
Assigning Ownership of a Folder
Assigning Ownership of a Folder

2. Select the Folders option and choose either a
Folder or a Folder Set from the list of values. Click
Find.
3. Select the folder that requires ownership.
4. Click the Change Owner 1 button to display the
Change Owner window or enter the new owner in
the Owner field.
n l y
Form Fields
e O
U s
• Public: This check box governs the availability of the folder to all users.
l
• Anyone’s Default: Indicates whether this folder definition is used as a default by a user or a
a
r n
responsibility. If it is a default definition, use Default Assignments to view the users and
responsibilities for which it is the default folder definition.
nt e
• Default Assignments: The users and responsibilities that use this folder definition as a
default.
e I
c l
r a
O
Chapter 11 - Page 8
Deleting a Folder Definition
Deleting a Folder Definition

2. Select Folders from the Find Folders window to
view general information about folders.
3. Select the folder(s) to delete.
4. From the Edit menu choose Delete.
Deleting folders deletes the folder definition along
with any user and responsibility default
assignments for the folder.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Chapter 11 - Page 9
Administering Folders Practice

• Create a folder
• Set the profile option to disallow modification to the
folder by your user
n l y
e O
Create a Folder
U s
1. Using your General Ledger Super User responsibility navigate to (N) Journals > Enter.
l
The first window you see is the Find Journals window. Note that once you create
a
n
your folder and assign it to your user this window will not appear.
r
nt e
e I
c l
r a
O
Folders Practice (Continued)
n l y
Practice (continued)
e O
Create a Folder (continued)
2. In the Find Journals window enter
U s
Source: Payables
a l
and click the Find button.
r n
nt e
e I
c l
r a
O
n l y
e O
3. In the Enter Journals window choose Save As… from the Folder menu.
U s
4. In the Save Folder window, enter the following:
a l
Folder: XXX Payables Journals
r n
Autoquery: Ask each time
Public: enable check box
nt e
I
Include query: enable check box
e
Click Show Query.
c l
r a
5. The Show Query window displays (JE_SOURCE=‘PAYABLES’). Note that you can
O
view the query here, but you cannot change it. Click OK to close the window.
6. In the Save Folder window click OK.
n l y
e O
U s
7. In the Enter Journals window note that now in the upper left corner next to the Folder
icon is the name you entered for your folder.
a l
r n
8. Click on the Folder icon to launch the Open Folder window. Note the other folders that
are available for your selection. These appear because they are defined as Public. Click
Cancel.
nt e
I
9. Click on the Folder Tools icon on the toolbar (the second icon from the right) to launch
the Folder Tools window palette. Move your cursor over each icon to view its function.
e
l
10. Click the Show Field… icon to launch the Show Field selection window. This allows
c
r a
you to add any of the listed fields to the Enter Journals window display.
11. Choose Category from the Show Field window and click OK. Note that the Category
O
field has been added to the display.
12. Click the Save icon on the Folder Tools window, or choose Save from the Folder menu
to add the Category column to your folder definition.
n l y
e O
Assign the Folder to Your User
1. Switch Responsibilities to your XXX System Administrator.
U s
2. Navigate to (N) Application > Administer Folders.
a l
r
user name from list of values. Click Find. n
3. In the Find Folders screen, select Default folder assignments by user and choose your
nt e
e I
c l
r a
O
n l y
e O
Assign the Folder to Your User
4. In the Default Folders by User window, enter the following:
U s
Folder Set: GL_JE_BATCHES_HEADERS_V
a l
Folder: XXX Payables Journals
r n
5. Click Save.
nt e
e I
c l
r a
O
n l y
e O
Set the Profile Option to disallow modification by your user
U s
2. In the Find System Profile Values window enter:
a l
User: your user
r n
3. Click Find.
nt e
Profile: Folders: Allow Customization
e I
c l
r a
O
n l y
e O
Set the Profile Option to disallow modification by your user
U s
4. In the System Profile Values screen enter “No” as the User value for the profile option.
5. Click Save.
a l
Test Your Changes
r n
2. Navigate to (N) Journals > Enter.
nt e
1. Switch Responsibilities back to your General Ledger Super User.
I
Notice that you see a Decision window that says “Find all records in this folder?”
e
folder.
c l
This window displays because you chose “Ask each time” when you defined the
r
Click Yes.
a
O
3. Notice that the Journal Entries window opens with your folder displayed.
4. Click on the Folder Tools icon on the toolbar. Notice that all the modification icons are
disabled (because you set the Folders: Allow Customization profile option to No).
5. Click on the Folder menu and notice that the only enabled option is Open.
Summary
Summary

• Assign default folder definitions to a responsibility
• Assign ownership of a folder
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
The practice in this lesson assumes that you have

“Managing Application Security” and set up the
following:
• System Administrator User
n l y
Practice Setup
e O
Set up the following user before performing the practice in this lesson:
U s
2. Select the System Administrator responsibility.
a l
n
r
nt e
4. Enter the following data to set up your user:
I
e
c l
r a
O
Responsibility
Application
System Administration
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Managing Document
Sequences
Chapter 12
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O
Managing Document Sequences

Chapter 12 - Page 1
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 12 - Page 2
Objectives
Objectives

do the following:
• Define a document sequence
• Define a document category
• Select a specific document for sequencing
• Assign a sequence to a document
• Set the profile option : Sequential Numbering
n l y
Lesson Aim
e O
U s
A document sequence is an internally managed log of transactions against a particular table.
Sequences enable complete auditing of all transactions, whether successful or not. This lesson
covers creating and implementing document sequences.
a l
r n
nt e
e I
c l
r a
O

Chapter 12 - Page 3
Using Document Sequences
Using Document Sequences
Payments (101) (102) (103)
Invoices (5001) (5002) (5003)
n l y
Why Use Document Sequences?
e O
Transactions Create Documents
U s
• Whenever you enter a transaction, you create a document. For example, when you enter a
invoice document.
a l
payment, you create a payment document. Or when you enter an invoice, you create an
r n
• You can assign unique numbers to the documents that you create by using document
sequences.
nt e
e I
Document Sequences Provide Completeness
• Completeness is proof that every document created by a user’s transaction can be
accounted for.
c l
r a
• By assigning unique numbers to documents, you can use document sequences to account
for all transactions, even those that fail.
O
Sequences, Categories, and Assignments
• Specify sequence information to determine how documents are numbered.
• Define document categories to group documents together.

Chapter 12 - Page 4
• Associate a sequence with a document category to determine which documents the
sequence will number.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 12 - Page 5
Specifying Sequence Information
Specifying Sequence Information
• What should the sequence name be?

• How long should the sequence be in effect?
• How should the sequence numbers be entered?
• What should the beginning number be?
n l y
Using Manual or Automatic Sequence Numbering
e O
U s
Certain information must be specified when a user creates a document sequence. This includes
the document name, its effective dates, and the type of numbering used. The numbers
Manual Numbering of Documents

a l
associated with the documents can be entered manually or generated automatically.
r n
• User assigns a unique number to each document before it is generated.
nt e
• Numerical ordering and completeness are not enforced.
e I
• Users may skip or omit numbers when entering the sequence value.
Automatic Numbering of Documents
c l
• Automatic numbering sequentially assigns a unique number to each document as it is
generated.
r a
• With automatic numbering, documents are numbered in order by date and time of creation.
O
• Numbers are in sequential order with no gaps or omissions.
• The user specifies the initial value for the sequence.
• A message can be sent to the user whenever a sequence number is assigned.

Chapter 12 - Page 6
How to Define a Document Sequence
How to Define a Document Sequence
Use the Document Sequences window to define a new

sequence.
• Define the Name and Application for your
sequence.
• Define when a sequence is valid. Leave the
Effective To field blank to enable a sequence
indefinitely.
• Enter Automatic or Manual to have the numbers
automatically generated or manually assigned.
• Check the Message box if you want each document
to display a message.
• Set the Initial Value of your sequence.
n l y
The Document Sequences Window
e O
(N) Application > Document > Define
• Name – Once entered, the sequence name cannot be changed.
U s
l
• Application – Once selected, the application associated with your sequence cannot be
a
changed.
r n
• Effective From/To – Enter the dates on which your document sequence takes effect/is no
nt e
longer enabled. The From date automatically defaults to the current date. Once a sequence
I
is defined, this date cannot be changed. If you leave the To field blank, your document
sequence does not expire. Once you enter the To date, it cannot be modified.
e
l
• Type – Once defined, you cannot change the type of document numbering sequence.
c
r a
- Automatic – Sequentially assigns, by date and time of creation, a unique number to
each document as it is generated.
O
- Manual – Requires a user to assign a number to each document before it is generated.
You must enter unique values. However, numerical ordering and completeness are not
enforced.
Note: The Gapless numbering type is valid only in the context of certain localizations.

Chapter 12 - Page 7
• Message – Check this box if you want each document to display a message (in the message
line of the screen) informing the user of the sequence name and value. This applies only to
sequences with the Automatic type of numbering. Once a message choice is defined, it
cannot be changed.
• Initial Value – Enter a value for the first document in your sequence. This field applies
only to sequences with Automatic or Gapless numbering type. If left blank, the first
document is automatically assigned a value of 1. Once the sequence is defined, the initial
value cannot be changed.
For further information about the fields in this window, see

(Help) Oracle Applications System Administration > Document Sequences >
Document Sequences Window
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Chapter 12 - Page 8
Specifying Document Category Information
Specifying Document Category

Information
• Which tables should have their transactions

documented?
• Should transactions against the same table be
broken down into logical subsets?
Standard
Accounts
Expense
reimbursement Payable
Interest payment
n l y
Specifying Document Category Information
e O
U s
Sequences track the transactions against a particular application table. The target table is
identified by a document category. In some cases, transactions against a table may need to be
a l
classified into subgroups according to some criterion to obtain important information. For
example, transactions against the Accounts Payable table may need to be divided according to
r
what type of payment each transaction concerned.
n
nt e
Use categories to divide your documents into logical groups. For example, accounts payable
invoices can be divided into the following types:
• Standard invoices
e I
l
• Expense report invoices
c
r a
• Prepayment invoices
• Interest invoices
O
• Credit memo invoices
• Debit memo invoices

Chapter 12 - Page 9
Document Categories
Document Categories
A category identifies a database table where

documents can be numbered by an assigned
sequence.
To define a document category:
• Navigate to the Document Categories window.
• Select an application and one of its tables.
• Assign the category a code and a name.
n l y
Category Code and Name
e O
(N) Application > Document > Categories
U s
• The combination of code and name must be unique within an application.
• Code must be unique. Name does not have to be unique.
a l
n
• After a category is defined, you cannot change the choice of table.
r
nt e
For a complete explanation of the fields in the Document Categories window, see
I
Document Sequences > Document Categories Window.
e
c l
r a
O

Sequence Assignments
Sequence Assignments
Use the Sequence Assignments window to associate a

category with its sequence.
To assign a sequence:
• Navigate to the Sequence Assignments window.
• Identify the applications and the category.
• Enter a starting date and specify which sequence
applies to this category.
n l y
(N) Application > Document > Assign
e O
U s
For a complete explanation of the fields in the Sequence Assignments window, see
Document Sequences > Sequence Assignments Window.

a l
r n
nt e
e I
c l
r a
O

Using a Sequence in Your Application
Using a Sequence in Your Application
After the document sequence has been defined, the

category has been associated with a table, and the
sequence has been assigned to the category, you can
identify the document sequence to be used with a
particular business transaction when you are creating
the transaction.
Example:
(N) Invoices > Standard > Enter
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Document Sequence Practice
Document Sequence Practice

• Define a category of documents that you wish to
sequence
• Assign the document sequence to your journal
entry category
• Enable sequential numbering for an application
n l y
e O
U s
Using the General Ledger Super User Responsibility, perform the following:
Define a Category of Documents
a l
In the Categories window enter the following:
r n
Category:
Description:
XXXDOCSEQ
nt e
XXX Document Sequence
e I
c l
Define the Document Sequence
In the Document Sequences window enter the following:
Name:
r aXXXSEQ
Type:
O
Message:
Automatic
enabled
Initial Value: 1001
Assign the Document Sequence to the Category

In the Sequence Assignments window enter the following:
Application: Oracle General Ledger
Category: XXXDOCSEQ
Set of Books: Vision Operations
Method: Manual
Start Date: 01-JAN-1950
End Date: (Leave Blank)
Sequence: XXXSEQ
Enable Sequential Numbering for Oracle General Ledger
Switch Responsibilities to the System Administrator. Set the profile option Sequential
Numbering to “Partially Used” for the application General Ledger.
Note: Once one student sets this value, it will be set for everyone.
Test Your Sequence
Switch Responsibilities to the General Ledger Super User. In the Find Journals window,
select New Journal. In the Journals window change the value in the category field to
XXXDOCSEQ. A message will display indicating that the number 1001 has been
assigned.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Practice Solution
Practice Solution
n l y
Practice Solution
e O
Define a category of documents that you wish to sequence
U s
1. Using the General Ledger Super User responsibility, go to (N) Setup > Journal >
Categories.
a l
2. In the Categories window enter
Category: XXXDOCSEQ
r n
Description:
nt e
XXX Document Sequence
3. Save your work.
e I
c l
r a
O

n l y
e O
Define a document sequence
4. Navigate to (N) Setup > Financials > Sequences > Define.
U s
5. In the Document Sequences window enter:
a l
Name: XXXSEQ
r n
From: 01-JAN-1950
nt e
I
Note: This date must be prior to the date of the first document created.
e
To:
Type:
c l
Leave blank
Automatic (indicates how the numbers will be generated)
Message:
r a enabled
O
Initial Value: 1001
6. Save your work.

n l y
e O
Assign the document sequence to your journal entry category
7. Navigate to (N) Setup > Financials > Sequences > Assign.
U s
8. In the Sequence Assignments window, enter:
a l
r n
Category: XXXDOCSEQ
nt
Set of Books: Vision Operations e
Method: Manual
e I (indicates how the documents will be created)
End Date:
c l
Start Date: 01-JAN-1950
Leave blank
r
Sequence: a XXXSEQ
O
Enable Sequential Numbering for Oracle General Ledger
9. Switch Responsibilities to the System Administrator responsibility.
11. In the Find System Profile Values window enter:

Profile: Sequential Numbering
12. In the System Profile Option Values window, use the list of values to enter “Partially
Used” for the Application profile value (because you are only numbering your category).
Note: Once one student sets this value, it will be set for everyone. The other students
can verify that it was set correctly.
13. Save your work.
n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

n l y
e O
Test your sequence
14. Switch Responsibilities to the General Ledger Super User.
U s
15. Navigate to (N) Journals > Enter.
a l
n
16. In the Find Journals window, click on the New Journal button.
r
nt e
A message will display indicating that no sequence exists for this category. That is
because the default category (set by a profile option called Journals: Default
e I
Category) is Adjustment, for which no sequence has been defined.
17. Change the value in the category field to XXXDOCSEQ.
c
18. Save your work. l
r a
19. A message will display stating that the number 1001 has been assigned. Note that on the
Journals window the Document Number field has been filled with 1001.
O

Summary
Summary

• Create a document category
• Assign a document sequence to a category
n l y
Summary
e O
U s
Document sequences can be used to track all transactions against a table regardless of
transaction completion. These sequences can provide an audit trail of transactions against a
of transactions can all be tracked.

a l
table. A particular table can have multiple categories defined to it. In this way, different types
r n
nt e
e I
c l
r a
O

The practice in this lesson assumes that you have

“Managing Application Security” and set up the
following:
• System Administrator User
n l y
Practice Setup
e O
Set up the following user before performing the practice in this lesson:
U s
2. Select the System Administrator responsibility.
a l
n
r
nt e
4. Enter the following data to set up your user:
I
e
c l
r a
O
Responsibility
Application
System Administration

n l y
e O
U s
a l
r n
nt e
e I
c l
r a
O

Sysadmin

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sysadmin

Uploaded by

Copyright:

Available Formats

11i System Administer Oracle

E-Business Suite ed 2.0

Restricted Rights Legend

Technical Contributors and Reviewers

Introduction to System Administration............................................................................... 1-1

Copyright © Oracle Corporation, 2001. All rights reserved.

11i System Administer Oracle E-Business Suite ed 2.0 Table of Contents

Submitting Requests: Form Compared with Responsibility................................................ 3-50

Copyright © Oracle Corporation, 2001. All rights reserved.

11i System Administer Oracle E-Business Suite ed 2.0 Table of Contents

Practice Solutions................................................................................................................ 4-40

Copyright © Oracle Corporation, 2001. All rights reserved.

11i System Administer Oracle E-Business Suite ed 2.0 Table of Contents

Copyright © Oracle Corporation, 2001. All rights reserved.

11i System Administer Oracle E-Business Suite ed 2.0 Table of Contents

Copyright © Oracle Corporation, 2001. All rights reserved.

11i System Administer Oracle E-Business Suite ed 2.0 Table of Contents

11i System Administer Oracle E-Business Suite ed 2.0 Table of Contents

• Thorough knowledge of navigating within Oracle Applications

• Working experience with at least one Oracle Applications module

• 11i Navigate Oracle E-Business Suite

How This Course Is Organized

Oracle Applications System Administrator’s Guide

Oracle Applications User’s Guide

11i System Administer Oracle E-Business Suite ed 2.0 Table of Contents

Caps and Buttons, Click the Executable button.

Courier new, Code output, Code output: debug.set (‘I”, 300);

Initial cap Graphics labels Customer address (but Oracle Payables)

Italic Emphasized words

Copyright © Oracle Corporation, 2001. All rights reserved.

11i System Administer Oracle E-Business Suite ed 2.0 Table of Contents

Passwords DROP USER scott

Lowercase Syntax variables CREATE ROLE role

Typographic Conventions in Navigation Paths

This simplified path translates to the following:

Copyright © Oracle Corporation, 2001. All rights reserved.

11i System Administer Oracle E-Business Suite ed 2.0 Table of Contents

The following help navigation path, for example—

(Help) General Ledger > Journals > Enter Journals

—represents the following sequence of actions:

2. Under the General Ledger entry, expand Journals.

3. Under Journals, select Enter Journals.

11i System Administer Oracle E-Business Suite ed 2.0 Table of Contents

Introduction to System Administration

Introduction to System Administration

Introduction to System Administration

After completing this course, you should be able

Introduction to System Administration

After completing this course, you should be able

Introduction to System Administration

System Administrator Functional Block

Introduction to System Administration

System Administrator Functional Block

Peripheral System User

Peripheral Can I use the

Introduction to System Administration

System Administration Functions

Balance online and Online

Introduction to System Administration

Introduction to System Administration

Managing Application Security

Managing Application Security

Managing Application Security