Академический Документы
Профессиональный Документы
Культура Документы
Fundamentals
Student Guide
D49195GC10
Edition 1.0
July 2007
D51755
Copyright © 1996, 2007, Oracle. All rights reserved.
This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and
print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way.
Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display,
perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization
of Oracle.
The information contained in this document is subject to change without notice. If you find any problems in the document, please
report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.
If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United
States Government, the following notice is applicable:
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may
be trademarks of their respective owners.
Author
Donna Johnson, Leta Davis, Barbara Waddoups, Gary Lemmons, Roman Kratochvil, Roger
Wigenstam, Venkata Vengala, Biju Mohan, Gursat Olgun, Maxine Zasowski, Sunil Ghosh
Introduction .....................................................................................................................................................1-1
Introduction ...................................................................................................................................................1-3
Course Objectives..........................................................................................................................................1-4
Overview .......................................................................................................................................................1-5
Oracle Applications System Administration .................................................................................................1-6
Oracle Workflow Component........................................................................................................................1-7
Oracle Applications Flexfields Component...................................................................................................1-8
Additional Material........................................................................................................................................1-9
Introduction to Oracle Applications Security ...............................................................................................2-1
Introduction to Oracle Applications Security ................................................................................................2-3
Objectives ......................................................................................................................................................2-4
Successive Layers of Access Control ............................................................................................................2-5
Increasing Flexibility and Scalability ............................................................................................................2-6
Function Security...........................................................................................................................................2-8
Data Security .................................................................................................................................................2-9
Oracle User Management Layers of Access Control.....................................................................................2-11
Role Based Access Control (RBAC) .............................................................................................................2-12
Delegated Administration..............................................................................................................................2-14
Registration Processes ...................................................................................................................................2-16
Self Service and Approvals ...........................................................................................................................2-18
Summary........................................................................................................................................................2-19
Function Security.............................................................................................................................................3-1
Function Security...........................................................................................................................................3-3
Objectives ......................................................................................................................................................3-4
Overview of Function Security......................................................................................................................3-5
Defining a New Application User .................................................................................................................3-7
Custom Applications .....................................................................................................................................3-8
Defining an Application ................................................................................................................................3-9
Registering an Oracle ID ...............................................................................................................................3-10
Data Groups...................................................................................................................................................3-11
Securing Functions ........................................................................................................................................3-13
Defining a Menu............................................................................................................................................3-14
Identifying Existing Menu Structures...........................................................................................................3-16
Menu Guidelines ...........................................................................................................................................3-17
Creating a Menu ............................................................................................................................................3-18
Modifying an Existing Menu Definition ......................................................................................................3-20
Navigator Menus ...........................................................................................................................................3-21
The Menu Viewer..........................................................................................................................................3-22
Viewing Node Properties in the Menu Viewer..............................................................................................3-23
Adding a Custom Form Function ..................................................................................................................3-24
Using Responsibilities ...................................................................................................................................3-25
Responsibility Components ...........................................................................................................................3-27
Defining a New Responsibility......................................................................................................................3-28
Responsibility Creation Process ....................................................................................................................3-29
Defining a New Responsibility......................................................................................................................3-30
Excluding Functions and Menus ...................................................................................................................3-31
Summary........................................................................................................................................................3-32
Introduction to Data Security.........................................................................................................................4-1
Introduction to Data Security.........................................................................................................................4-3
Objectives ......................................................................................................................................................4-4
Introduction to Data Security.........................................................................................................................4-5
Prerequisites
This is an instructor-led course featuring lecture and hands-on exercises. Online demonstrations
and written practice sessions reinforce the concepts and skills introduced.
Additional Publications
• Read-me files
• Oracle Magazine
(N) Invoice > Entry > Invoice Batches Summary (M) Query > Find (B) Approve
1. (N) From the Navigator window, select Invoice then Entry then Invoice Batches
Summary.
Notations:
(N) = Navigator
(M) = Menu
(T) = Tab
(B) = Button
(I) = Icon
(H) = Hyperlink
1. In the navigation frame of the help system window, expand the General Ledger entry.
4. Review the Enter Journals topic that appears in the document frame of the help system
window.
Introduction
Chapter 1 - Page 1
Copyright © Oracle Corporation, 2007. All rights reserved.
Introduction
Chapter 1 - Page 2
Introduction
Introduction
Chapter 1 - Page 3
Course Objectives
Introduction
Chapter 1 - Page 4
Overview
Introduction
Chapter 1 - Page 5
Oracle Applications System Administration
Introduction
Chapter 1 - Page 6
Oracle Workflow Component
Introduction
Chapter 1 - Page 7
Oracle Applications Flexfields Component
Introduction
Chapter 1 - Page 8
Additional Material
Introduction
Chapter 1 - Page 9
Copyright © Oracle Corporation, 2007. All rights reserved.
Introduction
Chapter 1 - Page 10
Introduction to Oracle
Applications Security
Chapter 2
Function Security
The base layer of access control within Oracle Applications is Function Security. Function
Security restricts user access to the individual menus and menu options within the system. It
can also be used to control access to some specific widget (often, graphical in nature) within a
page. Each of these various elements is represented in the system as a function, which is also
known as a permission. Using the Order Entry page as an example, Function Security could
control whether you have the ability to create a new order, or even access the page.
Data Security
The second layer represents Data Security. Working in conjunction with Function Security,
Data Security provides additional access control on the data a user can see and what actions a
user can perform on that data, within Oracle Applications. Note that Data Security is not used
in all Oracle Applications products. Products that do use data security include Oracle Projects,
Quality, and Cash Management.
Data Security Policies restrict the actions or operations that can be performed on a specific
business object (for example, inventory items). Data Security Policies can reflect access to:
• All Instances – All instances of an object represents all rows in the database object. For
example, assume that we have an object “inventory item” in the database. Creating a data
security policy for all instances of our object would result in providing access to every
single inventory item we have catalogued in the database.
• An Instance Set – An instance set is a related set of instances of an object. This
corresponds to a set of rows for the database object. Using our object example, an
instance set could be constructed to include all inventory items with a shelf life of 7 days.
• A Specific Instance – A specific instance generally corresponds to a single row in the
database. A specific instance is generally identified by a primary key value for the object.
Delegated Administration
With delegated administration, instead of exclusively relying on a centralized administrator to
manage all of its users, an organization can create local administrators with sufficient
privileges to manage a specific subset of the organization's users and roles. This provides
organizations with a tighter, more granular level of security and the ability to easily scale their
administrative capabilities.
Administration Privileges
Administration Privileges determine the users, roles and organization information delegated
administrators (local administrators) can manage. Each privilege is granted separately, yet the
three work in conjunction to provide the complete set of abilities for the delegated
administrator.
User Administration Privileges
A local administrator must be granted User Administration Privileges to determine the users
and people the local administrator can manage. Local administrators can be granted different
privileges for different subsets of users. For example, a local administrator can be granted
privileges only to query one set of users, and granted full privileges (including update and reset
Registration Processes
Oracle User Management contains the following registration processes.
Self-Service Account Requests
Commonly referred to as Self Service Registration, self-service account requests provide a
method for persons to request a new user account. Consider the case where customers may
need to register before they can purchase an item from an online store. Once the customer has
completed the registration process, the customer obtains both a user account and the necessary
role(s) for accessing some portion of the website in which they registered.
Requests for Additional Access
Users can request additional access through the Oracle User Management Access Request Tool
(ART) available in the global preferences menu. Requests for Additional Access uses the same
Oracle User Management infrastructure and processing logic as Self Service Account
Requests.
Account Creation By Administrators
Administrators can benefit from existing registration processes designed to streamline the
process of creating and maintaining user access. Registration Processes of this type are geared
toward administrators, especially delegated administrators, to ensure consistent application of
Function Security
Chapter 3 - Page 1
Copyright © Oracle Corporation, 2007. All rights reserved.
Function Security
Chapter 3 - Page 2
Function Security
Function Security
Chapter 3 - Page 3
Objectives
Lesson Aim
Function Security restricts user access to individual menus of functions, such as forms, HTML
pages, or widgets (such as buttons in a form) within an application. Function Security allows
you to define a user and assign the user one or more responsibilities, where each responsibility
has a menu associated with it. Function Security by itself restricts access to various functions,
but it does not restrict access to the data a user can see or what actions a user can perform on
that data. This lesson discusses defining users, responsibilities, and menus.
Function Security
Chapter 3 - Page 4
Overview of Function Security
Function Security
Chapter 3 - Page 5
A responsibility is a collection of authorizations that allow access to:
• A specific application or applications.
• A set of books.
• A restricted list of windows, functions, and reports. These may be associated to the
responsibility through menus.
Each user has one or more responsibilities, and several users can share the same responsibility.
A system administrator can assign users any of the standard responsibilities provided with
Oracle Applications or create new custom responsibilities as needed.
Users
A user is defined as a human being. Although the concept of a user can be extended to include
machines, networks, or intelligent autonomous agents, the definition is limited to a person in
this document.
You authorize a user to sign on to Oracle Applications by defining an application user. You
then assign one or more responsibilities to the new user.
Function Security
Chapter 3 - Page 6
Defining a New Application User
Function Security
Chapter 3 - Page 7
Custom Applications
Custom Applications
An application is composed of components such as forms, menus, and concurrent programs.
An application serves as a unique context for these components. The next three slides discuss
necessary steps in implementing security for a custom application.
Function Security
Chapter 3 - Page 8
Defining an Application
Defining an Application
(N) Application > Register
You can protect custom functions, forms, reports, and programs from being lost during
upgrades by registering them under a custom application.
In the Applications window you will supply the following information:
• Application – Enter a user-friendly name that will appear in lists seen by the user.
• Short Name – Oracle Applications uses this short name to identify forms, menus,
concurrent programs, and other components of your application.
• Basepath – Enter the base path where the forms, reports, and program files are located.
Make sure your base path is unique to prevent other applications from writing to the same
directory.
For a complete explanation of the fields in this form see:
(Help) Applied Technology > Oracle Applications System Administration > Configuration >
Applications DBA > Applications Window
Function Security
Chapter 3 - Page 9
Registering an Oracle ID
Registering an Oracle ID
(N) Security > ORACLE > Register
You need to register an Oracle ID if you create a custom application using Oracle Application
Object Library.
Note that:
• Only database administrators can create Oracle accounts.
• Only create a new Oracle ID for a custom extension to Oracle Applications.
• The install group designates which data group the application is associated with. For
applications that span all data groups, the install group is 0. Install groups numbered 1 or
greater are associated with one specific data group. Your database administrator can
supply the correct install group number.
Function Security
Chapter 3 - Page 10
Data Groups
Function Security
Chapter 3 - Page 11
application Application Object Library is automatically included. The Application Object
Library’s Oracle ID cannot be updated or deleted.
Relating Data Groups to Forms and Programs
You can control the relationship among applications, forms, and concurrent programs by
defining a data group.
Applications, Forms, and Programs
• A window connects to the application database account designated by the responsibility
associated with the application.
• A data group determines the pairing of an application with a unique application database
account or Oracle ID.
• A program connects to the application database account associated with the application
that owns the program.
Application-Oracle ID Pairs
• An Oracle ID is a username and password that allows access to application tables in an
Oracle database.
• A data group lists the Oracle ID assigned to each Oracle application.
• A custom application registered with Oracle Applications can be included in a data group
and paired with an Oracle ID.
Function Security
Chapter 3 - Page 12
Securing Functions
Securing Functions
You can manage security by controlling access to individual functions through menu
definitions.
About Functions
• A function is a set of code in Oracle Applications that is executed only if the name of the
function is present in a list maintained within a responsibility.
• There are two types of functions: a form function and a nonform function or subfunction.
A subfunction represents a securable subset of a form’s functionality.
Adding Functions to or Removing Functions from a Responsibility
• Maintain menu structures while eliminating specific functionality.
• Exclude individual functions from a responsibility.
Adding or Removing Menus of Functions
• Use menus to group functions together.
• Exclude groups of functions by excluding a menu from a responsibility.
Function Security
Chapter 3 - Page 13
Defining a Menu
Function Security
Chapter 3 - Page 14
• Assign the menu structure to the new responsibility by using the responsibilities form.
• Document your menu structure by printing the Function Security Menu Report.
Function Security
Chapter 3 - Page 15
Identifying Existing Menu Structures
Function Security
Chapter 3 - Page 16
Menu Guidelines
Function Security
Chapter 3 - Page 17
Creating a Menu
Creating a Menu
Use the Menus window to create a menu:
(N) Application > Menu
After you save your changes in this form, the Compile Security concurrent program is
automatically submitted to compile the menu data. Compiling your menu data allows for the
system to determine more quickly, during a user’s session, whether a function is available to a
particular responsibility or menu.
New Menus form fields:
• Menu Type – used to specify the purpose of the menu. The possible values are:
- Standard – for menus that would be used in the Navigator form
- Tab – for menus used in Self-Service applications
- Security – for menus used to aggregate functions for data security or specific function
security purposes, but would not be used in the Navigator form.
• Grant check box – checking this box indicates that this function is automatically enabled
for the user.
For a complete explanation of the fields on this form see:
Function Security
Chapter 3 - Page 18
(Help) Applied Technology > Oracle Applications System Administration > Security >
Function Security > Menus Window
Note: If a menu entry has both a submenu and a function defined, then the behavior depends
on whether or not the function is executable. If it is executable, then the submenu is treated as
content to be rendered by the function. The submenu will not appear on the navigation tree, but
will be available in function security tests (FND_FUNCTION.TEST calls). If the function is
not executable, then it is treated as a “tag” for enforcing exclusion rules, and the submenu is
displayed on the navigation tree.
A function is considered executable if it can be executed directly from the current running user
interface.
Function Security
Chapter 3 - Page 19
Modifying an Existing Menu Definition
Modifying a Menu
You can modify existing custom menus to suit specific job functions.
Overwrite a User Menu Name
When you change a menu’s user menu name, the menu entries are not affected. The menu’s
definition still exists, but under a new name. Other menus that call the menu by its old user
menu name now call the same menu by its new (revised) user menu name.
The old user menu name is no longer valid. When you are defining menus, or if you are
selecting main menus when defining a responsibility, the previously named menu is no longer
displayed in any list of values.
Modify a Menu Entry
When you are modifying a previously defined menu, all other menus that call that menu
display the menu’s modifications. For example, if you modify XXX_GL_USER by adding
another prompt that calls a form, all menus that call GL_SUPERUSER4.0 display the
additional prompt when XXX_GL_USER is displayed.
Note: Modifying shipped menu definitions is not supported. The customized definitions may
be overwritten during an upgrade process.
Function Security
Chapter 3 - Page 20
Navigator Menus
Function Security
Chapter 3 - Page 21
The Menu Viewer
Function Security
Chapter 3 - Page 22
Viewing Node Properties in the Menu Viewer
Function Security
Chapter 3 - Page 23
Adding a Custom Form Function
Function Security
Chapter 3 - Page 24
Using Responsibilities
Function Security
Chapter 3 - Page 25
After you have defined a new responsibility, you can associate it with an application user.
Function Security
Chapter 3 - Page 26
Responsibility Components
Components of a Responsibility
A responsibility has two required components and two optional components.
Required Components
• Data group: specifies the Oracle Application database accounts to which a responsibility’s
forms and concurrent programs connect.
• Menu: specifies the forms that a responsibility can display and the functions it can access.
Optional Components
• Request security group: lists the concurrent programs that a responsibility can run. When a
request group is assigned to a responsibility, it is referred to as a request security group.
• Exclusions: modify a responsibility’s access to the forms and functions specified by a
menu.
Function Security
Chapter 3 - Page 27
Defining a New Responsibility
Function Security
Chapter 3 - Page 28
Responsibility Creation Process
Function Security
Chapter 3 - Page 29
Defining a New Responsibility
Defining a Responsibility
(N) Security > Responsibility > Define
A responsibility determines the type of applications a user accesses, which application
functions a user can use, which reports and concurrent programs the user can run, and which
data those reports and concurrent programs can access. Most responsibilities are available
from Oracle Applications (the Forms navigator or the HTML-based E-Business Suite Home
page), others may be accessible from Oracle Self-Service Web Applications or Oracle Mobile
Applications.
Function Security
Chapter 3 - Page 30
Excluding Functions and Menus
Function Security
Chapter 3 - Page 31
Summary
Lesson Summary
Function Security provides you with the ability to control Oracle Applications Security. The
system administrator specifies which users have access to which functions. User accounts
provide the user access to an application. Responsibilities control that user’s access to various
functions of the application. Online access is controlled through the use of menus and menu
exclusions. Report and concurrent program access is controlled through the use of request
groups.
Function Security
Chapter 3 - Page 32
Introduction to Data Security
Chapter 4
Data Security
In this section, references to specific applications are used as examples only. Data Security is
not implemented in all Oracle Applications products. Some applications may require
organizations to create multiple responsibilities to operate with their existing security models.
For more information, please consult the application-specific documentation.
This section is meant to introduce data security and its concepts only. Custom implementation
of data security or modification of shipped data security policies is not covered and is beyond
the scope of this course. Extreme care should be taken if any customization or modification is
done with data security implementations.
Introduction
Working in conjunction with Function Security, Data Security provides additional access
control on the data a user can see and what actions a user can perform on that data. Using Data
Security, for example, you could control access to the set of orders that an order administrator
can update within the Order Management application.
Data Security Policies restrict the actions or operations that can be performed on a specific
business object (for example, inventory items). Data Security Policies can reflect access to:
• All Instances – All instances of an object represents all rows in the database table or view.
For example, assume that we have an object “inventory item” in the database. Creating a
data security policy for all instances of our object would result in providing access to
every single inventory item we have catalogued in the database.
• An Instance Set – An instance set is a related set of instances of an object. This
corresponds to a set of rows in the database. Using our object example, an instance set
could be constructed to include all inventory items with a shelf life of 7 days.
• A Specific Instance – A specific instance generally corresponds to a single row in the
database. A specific instance is generally identified by a primary key value for the object.
Objects
(N) Functional Developer responsibility > Objects
An object is a system entity on which an operation can be performed. In Oracle Applications,
an object typically maps to records in relational tables/views, Forms/HTML pages, and UI
widgets. Examples in Oracle Applications include: a person, an machine, and a file.
Examples of operations include: Create, Update, Escalate, Approve, and Reject. In Oracle
Applications, operations are implied by a permission definition. Permission has been defined
as an operation on a object; for example, Invoke Service Request Form, Update Order,
Approve Expense Report, and Query Customers.
An object instance is a specific example of an object, such as Project Number 123 or User
JDOE. An object instance generally corresponds to a row in the database, and is identified by
a set of one or more primary key values as defined by the object.
Related object instances can be grouped together into an object instance set.
Grants
(N) Functional Administrator Responsibility > Grants
Grants are used to provide specified users access to specific objects or functions.
Grants that deal with business objects are called Data Security Policies.
Grants can also be used to control access to an application's functionality. For example, you
could use a grant to secure an aspect of a menu, page, or other widget within the application.
For example, you want to provide access to a set of administrative menus to a select group of
users.
The grantee defines who is being granted access. The grantee can be one of three types:
• A group of users
• A specific user – for example, Joe Smith
• All users (global) – all users of the system, except the Guest account
Permissions
The Role Based Access Control (RBAC) Model defines permission as "an approval to perform
an operation on one or more RBAC-protected objects." This definition maps to what has been
referred to as functions earlier. Permissions can be grouped into permission sets.
Permission sets can be granted to users or roles independently of menus or responsibilities.
Permission assignments, or Grants, reflect the access granted to users through roles.
Permissions are discussed more in the User Management lessons.
Example
An organization can use Function Security to provide its sales representatives with the required
pages, menus, and menu options for querying customers. It can also control access to specific
components of those pages, such as a "Generate Sales Forecast" button on a sales forecasting
page.
Responsibilities
Responsibilities have a menu tree in which available menus are defined with a grant flag. On
being assigned a responsibility, a user gains access to all menus on the menu tree except those
for which an exclusion has been defined. In the above example, Menu 2 has been excluded
from the menu tree. When the user is assigned the corresponding responsibility, the user can
access Menu 1, Menu 3, and Menu 4.
Example
Data Security restricts the set of users that a local administrator can manage and administer
within Oracle User Management. Data Security policies can only be defined for applications
that have been written to utilize the Data Security Framework.
Delegated Administration
Delegated Administration is a privilege model that builds on the RBAC system. With
delegated administration, instead of exclusively relying on a centralized administrator to
manage all of its users, an organization can create local administrators and grant them
sufficient privileges to manage a specific subset of the organization's users and roles. This
provides organizations with a tighter, more granular level of security and the ability to easily
scale their administration.
Administration Privileges
Administration Privileges determine the users, roles and organization information that
delegated administrators (local administrators) can manage. Each privilege is granted
separately, yet the three work in conjunction to provide the complete set of abilities for the
delegated administrator.
• User Administration Privileges: A local administrator must be granted User
Administration Privileges to determine the users and people he can manage. Local
administrators can be granted different privileges for different subsets of users.
• Role Administration Privileges: Role Administration Privileges define the roles that
local administrators can directly assign to and revoke from the set of users they manage.
Provisioning Services
Oracle User Management includes the following provisioning services, implemented as
registration processes:
Self-Service Account Requests
Commonly referred to as Self Service Registration, self-service account requests provide a
method for persons to request a new user account. For example, customers may need to register
before they can purchase an item from an online store. After completing the registration
process, the customer obtains both a user account and the necessary roles for access to the
store.
Requests for Additional Access
Users can request additional access through the Oracle User Management Access Request Tool
(ART) available in the global preferences menu. Requests for Additional Access uses the same
Oracle User Management infrastructure and processing logic as Self Service Account
Requests.
Account Creation By Administrators
Administrators can benefit from existing registration processes designed to streamline the
process of creating and maintaining user access. Registration Processes of this type are geared
Login Assistance
System administrators often have to reset a user's forgotten password, or even advise a user of
the account's user (login) name. This is unproductive for both the user and the administrator. In
addition, a user may request the password to be reset, when it is actually the user name that has
been forgotten, or vice versa.
A new feature in Release 12 helps reduce the time spent on such administrative activities, by
implementing a login help mechanism on the E-Business Suite Login Page. A user simply
clicks on the "Login Assistance" link located below the Login and Cancel buttons. On the
screen that appears, the user can choose between the Forgot Password and Forgot Username
sections.
Introduction to Roles
In previous releases of Oracle Applications, access to individual functions within an
application could only be defined through responsibilities, menu hierarchies, and menu
exclusions. New responsibilities had to be defined for each set of users (with different job
functions) that needed access to a set of pages within an application. These responsibilities
required either:
• Completely new menu hierarchies for each responsibility
• A common menu covering the superset of all functions within the application, and menu
exclusion rules defined for each responsibility
An example is the Human Resources product, which typically has at least two responsibilities
defined, one for employees and one for managers.
In essence, responsibilities have been used not only to define the application navigation menus,
but also the privileges and permissions within an application. Cost of ownership and
management has increased with the number of responsibilities, as multiple complex menu
hierarchies and/or exclusion rules must be maintained.
Oracle User Management provides new alternatives for defining access to an application,
allowing organizations to separate navigation menus from access control.
Examples of Roles
In this example, the manager is granted both the employee role and the manager role, since the
manager effectively functions as both.
Steps for Creating Roles: Create a Role within the Role Category
Create a role and include it within the role category. In this scenario, the role is Customer
Administrator. This role is created for an external organization, and is assigned to individuals
who manage the external organization’s users.
Oracle User Management ships with three seeded roles, Partner Administrator, Customer
Administrator, and Security Administrator. The business scenarios and practices in this course
assume that the Customer Administrator role must be created and configured to function with
the other two.
Note: Many of the practices in this course involve creating, configuring, and testing the
Customer Administrator role. Since Oracle User Management already ships with this role, the
practices require students to create a Course Administrator role that is essentially an exact copy
of the seeded Customer Administrator role. Students can compare their Course Administrator
role to the seeded Customer Administrator role; the two should be identical.
Registration Processes
Oracle User Management contains the following registration processes:
Self-Service Account Requests
Commonly referred to as Self-Service Registration, self-service account requests provide a
means for people to request a new user account. For example, customers may need to register
before they can purchase an item from an online store. After completing the registration
process, the customer obtains both a user account and the necessary role(s) to access the store.
Requests for Additional Access
Users can request additional access through the Oracle User Management Access Request Tool
(ART), available on the global preferences menu. Requests for Additional Access uses the
same Oracle User Management infrastructure and processing logic as Self-Service Account
Requests.
Account Creation By Administrators
Administrators can benefit from existing registration processes designed to streamline the
process of creating and maintaining user access. Registration Processes of this type are geared
toward administrators, especially delegated administrators, to ensure consistent application of
Login Assistance
System administrators often have to reset a user's forgotten password, or even advise a user of
the account's user (login) name. This is unproductive for both the user and the administrator. In
addition, a user may request the password to be reset, when it is actually the user name that has
been forgotten, or vice versa.
A new feature in Release 12 helps reduce the time spent on such administrative activities, by
implementing a login help mechanism on the E-Business Suite Login Page. A user simply
clicks on the "Login Assistance" link located below the Login and Cancel buttons.
On the login assistance screen that appears, the user can either go to the Forgot Password
section and enter the correct user name, or to the Forgot Username section and enter the email
address associated with the account. The user will then either be emailed either password reset
details or the user name, as applicable.
For security, the relevant data is stored securely in workflow tables, and the secure URLs
employed by the mechanism have both an expiration time and a single-use limitation.
Profile Options
Chapter 7 - Page 1
Copyright © Oracle Corporation, 2007. All rights reserved.
Profile Options
Chapter 7 - Page 2
Managing Profile Options
Profile Options
Chapter 7 - Page 3
Objectives
Lesson Aim
As a system administrator, you control various options in Oracle Applications that determine
how your applications look and feel. These options can also control how each application
operates. This lesson shows you how to specify these values.
Profile Options
Chapter 7 - Page 4
Personal Profile Values
Profile Options
Chapter 7 - Page 5
System Profile Options - Profile Hierarchy Types
Profile Options
Chapter 7 - Page 6
Profile Hierarchy Levels - Security
Profile Options
Chapter 7 - Page 7
Profile Hierarchy Levels – Organization
Profile Options
Chapter 7 - Page 8
Profile Hierarchy Levels - Server
Profile Options
Chapter 7 - Page 9
System Profile Options
Profile Options
Chapter 7 - Page 10
Using User Profile Values as Defaults
Profile Options
Chapter 7 - Page 11
Profile Categories
Profile Categories
(N) Functional Administrator responsibility > Core Services > Profile Categories
Profile options can be grouped into logical categories based on their functional area. A profile
option can belong to more than one profile category.
You can create new or update existing profile categories.
The following slides describe some of the more commonly-used profile options. They do not
represent all the profile options included in each listed profile category.
Profile Options
Chapter 7 - Page 12
Auditing Related Profile Options
Profile Options
Chapter 7 - Page 13
• Form – performs the Responsibility-level audit and also tracks the forms the users choose
and how long each form is used.
Profile Options
Chapter 7 - Page 14
Currency-Related Options
Profile Options
Chapter 7 - Page 15
Flexfield-Related Options
Profile Options
Chapter 7 - Page 16
BiDi Direction
This option controls the appearance of the flexfields window in Applications running in
Semitic languages.
LOV Warning Limit
Sometimes an LOV can take a very long time to run if there is a very significant amount of
data in it. Set this option to the number of rows to be returned before you are asked to continue
retrieving the entire list.
Open Descr Window
This option allows you to control whether a descriptive flexfield window automatically opens
when you navigate to a customized descriptive flexfield.
Profile Options
Chapter 7 - Page 17
Online Reporting-Related Options
Profile Options
Chapter 7 - Page 18
Personal Output Viewer Options
Profile Options
Chapter 7 - Page 19
User-Related Concurrent Request Profile Options
Profile Options
Chapter 7 - Page 20
Concurrent: Sequential Requests
Setting this option to Yes forces requests to run sequentially in the order in which they were
submitted.
Profile Options
Chapter 7 - Page 21
Security Signon Profile Options
Profile Options
Chapter 7 - Page 22
Signon Password Length sets the minimum length of an Applications signon password. If no
value is entered, the minimum length defaults to 5.
Signon Password No Reuse
This profile option specifies the number of days that a user must wait before being allowed to
reuse a password.
Profile Options
Chapter 7 - Page 23
Summary
Lesson Summary
An important function of the system administrator is to control the default behavior and
appearance of Oracle Applications. This is done by specifying profile values. In this lesson you
saw how to display and update profile values. You also learned how to reference previously
defined profile values elsewhere in Oracle Applications.
Profile Options
Chapter 7 - Page 24
Auditing System Resources
Chapter 8
Lesson Aim
As system administrator you may audit application users and the changes they make to
application data. You will learn how both of these options are set and why you use them.
Reports
The Signon Audit feature can generate several reports detailing information gathered by
Signon Audit. These reports are shown in the figure.
• Signon Audit Forms
• Signon Audit Users
• Signon Audit Responsibilities
• Signon Audit Concurrent Requests Report
• Signon Audit Unsuccessful Logins Report
Audit Groups
(N) Security > AuditTrail > Groups
Once you have your tables and columns identified, you should group those tables into an audit
group. In the figure, the three tables mentioned have been placed together in a Receivables
Internal Control audit group.
Managing Printers
Chapter 9 - Page 1
Copyright © Oracle Corporation, 2007. All rights reserved.
Managing Printers
Chapter 9 - Page 2
Managing Printers
Managing Printers
Chapter 9 - Page 3
Objectives
Lesson Aim
Installing a new printer is a typical responsibility of the system administrator. A less common
need is to customize the software that supports printers. This lesson covers the basics of
printer setup and the Pasta printing utility. References for additional information on
customizing your printer setup are also provided.
To set up your printers, you can either use the Pasta utility, in which you enter configuration
data in a file called pasta.cfg, and use predefined components. Alternatively, you can use the
printing setup windows to define your components and enter configuration information.
Managing Printers
Chapter 9 - Page 4
Oracle Print Definition Components
Managing Printers
Chapter 9 - Page 5
Printer Drivers Versus SRW
• A printer driver formats the destination printer.
• An SRW driver formats text and sets page breaks in an Oracle Reports file.
Managing Printers
Chapter 9 - Page 6
Relationships of the Printer Components
Managing Printers
Chapter 9 - Page 7
Formatting Information
Formatting Information
For a printer to produce a report, it requires three basic types of formatting instructions: text,
document, and printer.
Text Formatting
• Oracle Reports generates reports for the various Oracle Applications.
• When Oracle Reports formats text as bold or underlined, and sets page breaks, formatting
codes are used.
• A SQL*ReportWriter (SRW) driver defines text formatting codes used by Oracle Reports.
Document Formatting
• The dimensions for a report output file are predefined as the number of rows and columns
(height and width).
• A print style defines the dimensions for a report output file.
Printer Formatting
• A printer prints in a certain orientation, portrait or landscape.
• A printer can also start printing with a specific font and type size. These instructions are
contained in an initialization string.
Managing Printers
Chapter 9 - Page 8
• A printer driver defines initialization and reset strings.
Managing Printers
Chapter 9 - Page 9
Defining Printers
Managing Printers
Chapter 9 - Page 10
Finding Existing Printer Types
Managing Printers
Chapter 9 - Page 11
Registering a New Printer
Managing Printers
Chapter 9 - Page 12
Defining a New Printer Type
Managing Printers
Chapter 9 - Page 13
Printing with Pasta
Managing Printers
Chapter 9 - Page 14
Setup for Basic Printing with Pasta
Managing Printers
Chapter 9 - Page 15
The pasta.cfg file
Managing Printers
Chapter 9 - Page 16
Modifying an Existing Printer Type to Use Pasta
Managing Printers
Chapter 9 - Page 17
2. In the Style field, select the style to which you want to assign a Pasta driver. Or, if you are
assigning Pasta to a style already defined for the printer type, delete the driver in the
Driver Name field currently associated with the style.
3. In the Driver Name field, select the appropriate Pasta driver.
Adding a New Printer Type to Use Pasta
If you want to add a new printer type, you can also add Pasta to your new printer type.
1. Navigate to the Printer Types window.
2. Enter the Type of printer.
3. In the Style field use the list of values to select the style to which you want to assign a
Pasta driver.
4. In the Driver Name field, select the appropriate Pasta driver from the list of values:
- PASTA_LANDSCAPE
- PASTA_PORTRAIT
- PASTA_LANDWIDE
- PASTA_DYNAMIC
Managing Printers
Chapter 9 - Page 18
Generating Other Formats using the Preprocessing Option
Managing Printers
Chapter 9 - Page 19
Using Pasta with XML Publisher
Managing Printers
Chapter 9 - Page 20
To use a converter, change the Pasta configuration file to call a third party package to convert
the PDF to PS or PCL. Pasta can use a preprocessing command to invoke any executable that
supports an input file and an output file (a filter program). The third party package can be an
open source solutions such as Ghostscript and XPdf.
Pasta invokes the filter program to preprocess the XML Publisher output before passing it to
the printing command. By using the preprocess option, you can generate output formats other
than the formats currently supported by Pasta.
For more information, see the “Pasta 3.0.4.0 User's Guide for Release 12” in OracleMetaLink
Note 239196.1.
Managing Printers
Chapter 9 - Page 21
Other Customization Materials for Oracle Applications Printing
Customization Considerations
You can customize Oracle Applications printer support components to use custom print styles
and custom print programs. For information on how to do customize these components, use
the references below.
Materials Needed
• Manual for your specific printer to look up control codes required by a printer type
• Installing Oracle Applications for your platform to look up control codes required by an
operating system platform
• Oracle Applications System Administrator’s Guide – Configuration
• “Pasta 3.0.4.0 User's Guide for Release 12” in OracleMetaLink Note 239196.1
Managing Printers
Chapter 9 - Page 22
Summary
Managing Printers
Chapter 9 - Page 23
Copyright © Oracle Corporation, 2007. All rights reserved.
Managing Printers
Chapter 9 - Page 24
Introduction to Oracle
Applications Manager
Chapter 10
Introduction
Oracle Applications Manager is a system management console. It provides a wide variety of
features related to system management for use by DBAs, System Administrators, and
Technical Support personnel.
Oracle Applications Manager allows you to monitor and control E-Business Suite system
components. It can help you to understand how the performance and availability of those
components affects your business. When problems arise, Oracle Applications Manager
provides a variety of features to help you diagnose and resolve those problems quickly to
reduce any necessary downtime. Oracle Applications Manager helps you manage your system
configuration by enabling you to make and track configuration changes as well as identify
potential configuration problems. Additionally, Oracle Applications Manager helps you track
periodic maintenance activities and facilitates the patching process.
The pre-defined Oracle Applications Manager Administrator Menu is available from the
System Administration responsibility.
Benefits
Oracle Applications Manager provides features to manage all aspects of the Oracle E-Business
Suite.
During system implementation, Oracle Applications Manager automates configuration tasks
and enables you to tighten security on the system. OAM can also help in keeping the system
up-to-date with the latest E-Business Suite patches.
Oracle Applications Manager automates system monitoring, facilitates daily administration,
and helps speed problem resolution.
For maintenance or upgrades, OAM helps identify necessary updates, provides an analysis of
the potential impact of those updates, and delivers tools to facilitate and minimize any required
downtime.
Navigation
You can access OAM from the System Administration responsibility or the System
Administrator responsibility. A seeded menu, Oracle Applications Manager Administrator
Menu (OAM_ADMIN_MENU) is available from these responsibilities. In addition, individual
OAM functions can be added to custom menus. Direct links to specific Oracle Applications
Manager features are possible from the E-Business Suite Home Page.
The OAM console includes:
• The Applications Dashboard, which includes tabs and a dropdown list for quick access to
commonly-used features
• The Site Map, which contains links to all features within OAM
• Global buttons/links for setup, the Support Cart, your home page, and online help
Applications Dashboard
The Applications Dashboard provides a comprehensive summary of the Oracle E-Business
Suite components including:
• An overview of configuration changes and the status of infrastructure components
• Performance information
• Required critical maintenance activities
• Diagnostic test results
• The status of key business flows
• Potential security issues
• Software updates
In addition, a dropdown list provides quick access to commonly-used pages and features,
including:
• Configuration – Overview
• Forms Sessions
• Database Status
Site Map
The Site Map provides links to most pages in OAM, in these categories:
• Administration
• Monitoring
• Maintenance
• Diagnostics and Repair
Maintenance Features
Patching utilities are available from the Site Map > Monitoring tab. These are described in the
“12 Install, Patch, and Maintain Oracle Applications” course.
Critical activities are activities that must be run periodically. They are monitored to ensure they
are being run. Examples include refreshing an Employee Directory or purging obsolete data.
System Overview
(N) Applications Dashboard > Overview (T)
The Overview tab of the Applications Dashboard provides an overview of the general status of
your system.
Applications System Status
The status of each host is shown.
• Platform - the host's operating system.
• Host Status – indicates whether the host is up or down.
• Admin - indicates whether the Admin server has been installed on the host machine.
• Database - indicates the status of the database instance installed on the host machine.
• Concurrent Processing- indicates the status of the Internal Concurrent Manager and the
services managed by the ICM.
• Forms - indicates the status of the Forms Server components: Forms Listener, Metrics
Server, Metrics Client, and OAM Generic Collection Service.
• Web - indicates the status of the Apache Web Listener.
Configuration Changes
This region shows system-level changes that were made in the last 24 hours. Use this data to
help diagnose sudden changes in the functioning of your applications system.
To see the list of Patches Applied, click on the number to drill down to the Patch Summary
page.
To see the list of Site Level Profile Options, click on the number to drill down to the Site Level
Profile Settings page.
To see the list of Applications Context Files Edited, click on the number to drill down to the
Applications Configuration Parameters page. Changes made to context files can impact your
overall processing configuration and the functioning of business processes.
System Alerts
Use the System Alerts region to find out about critical events to your system. Examples of such
events are a halted process or a program that returned an error.
This region lists the number of system alerts in the categories listed below.
If your system is functioning well, there should be no new alerts reported. When an alert of a
particular type first occurs, it is counted as a new alert. It remains new until the status is
manually changed by the administrator. If an alert of the same type occurs again while the
original alert is still in open or new status, it is counted as a new occurrence.
• New Alerts - alerts that have not yet been acknowledged by the administrator. An alert is
acknowledged when it is manually moved from a status of "New" to a status of "Open" or
"Closed."
• New Occurrences - additional occurrences of alerts that are in new status.
• Open Alerts - all alerts that are in an open status. An alert must be manually moved from
the new to open status.
• Open Occurrences - all occurrences of alerts that are currently open.
Click on the number for any of these to drill down to the System Alerts and Metrics page.
Performance
(N) Applications Dashboard > Performance (T)
Application Tier Hosts
• Database Sessions - the number of active database sessions. Clicking the value link returns
a page showing all active database sessions.
• Running Requests - drills down to the Search for Requests Results page showing
information on all currently running requests.
• Forms Sessions - the number of running Forms sessions. Drills down to the Forms
Sessions page.
- The Forms Sessions page shows information including the following: username,
auditing session ID or AUDSID (from which you can drill down for database session
information), CPU usage, and duration.
- The Active Database Sessions includes the following information - AUDSID,
machine, program, and module.
• Service Processes - drills down to the System Activity page. Service processes include all
concurrent manager processes and all processes managed by the ICM. If you have set up
Application Services
(N) Site Map > Administration Tab > Application Services > Generic Services
You can configure, monitor, and control application services from the System Activity page for
services. These services are managed under Generic Service Management (GSM). GSM
allows you to manage a variety of services using a fault-tolerant framework. The Application
Services lets you drill down to details for instances of each service and view the instances'
statuses and processes.
Forms Sessions
(N) Site Map > Monitoring (T) > Forms Sessions (under Performance or Current Activity)
This page shows information on the current forms sessions. Every open form has its own
database session, or "Forms session." The profile option "Sign-On:Audit Level" should be set
to 'Form' to use this feature. If this profile option is not set to 'Form', the Forms Sessions table
will show an empty table even when there are active forms sessions.
The following data is shown for each session:
• Form Name
• AUDSID - The auditing session ID. Click on the value to drill down to the Database
Session information page.
• RTI_PID - The runtime instance process ID. Click on the value to drill down to the Forms
Sessions for Process ID page.
• Username
• Responsibility
• Application
Host Management
(N) Site Map > Administration (T) > Hosts (under System Configuration)
Oracle Applications Manager provides a list of host machines that are employed by the
Applications and Database Tiers of the E-Business Suite system. For each host, you can view
the host status, and you can drill down to see the status of the individual E-Business Suite
processes on that host. You can also view the E-Business Suite configuration details for that
specific host, including the installed server types, and port allocations.
Oracle Applications Manager allows you to change the state of a given host to make that host
available or unavailable to Generic Service Management (GSM). Under GSM, the Internal
Concurrent Manager manages the various service processes across multiple hosts. If you need
to take a host down for maintenance, you can first mark that host as “offline” in OAM, which
will ensure that concurrent mangers and other service processes are migrated to a secondary
node as appropriate. Later, when you set the node back to “online”, the processes will be
migrated back.
The new host-oriented interfaces allow you to track more easily which service processes are
running on which hosts, and you can more easily identify the services that would be affected
by a planned or unplanned outage for the host. For planned outages, OAM enables you to
Dashboard Setup
(N) Setup > Dashboard Setup > Update (B)
The landing page from the Setup is the Dashboard Setup page. View the current collection and
alerting settings here. To update these, click on the Update button.
OAM Dashboard Collection Interval
Specify how frequently the collection program should be run.
Metrics Setup
Enable or disable the collection of individual metrics by checking or un-checking the box in
the “Enable Collections” column.
- If you would like to enable alerts for a given metric, check the appropriate box in the
“Enable Alerts” column.
- To set the alert condition, you can choose either “less than”, “equal to”, or “greater
than” from the “Threshold Operator” column, and then enter the desired value in the
“Threshold Value” column. Click on the Next button to move to the configuration of
monitoring services.
Service Monitoring
Introduction
Oracle Applications Manager provides features to help you diagnose and resolve system issues.
Oracle Applications Manager integrates with Oracle Diagnostics to provide access to a large
library of diagnostic tests for system technologies, E-Business Suite products, and business
flows.
Oracle Applications Manager also controls Oracle Applications Logging. When issues arise
on your system, you can configure logging to write varying levels of diagnostic information for
specific components into a central repository. Oracle Applications Manager allows you to
view and manage the information logged into this repository.
If you encounter a problem in the system, you can first try to diagnose the problem using
Oracle Diagnostics. Then you can try to correct the problem using the Troubleshooting
Wizards.
Also, if you are unable to diagnose and resolve problems yourself, then Oracle Applications
Manager makes it easier for you to communicate with Support. The Support Cart has been
improved to provide automated collections of the data that Oracle Support requires for
resolving issues.
Troubleshooting Wizards
(N) Applications Dashboard > Diagnostics (T) > [links under Troubleshooting Wizards region]
Troubleshooting Wizards are available for the following:
• Concurrent Manager Recovery - Use this wizard when the Internal Concurrent Manager
fails to start.
• Service Infrastructure - Using the Service Infrastructure diagnostic wizard, you can
examine existing Generic Service Management data to determine potential problems, and
update the data to eliminate the issues. An example of a potential problem is an active
node without a service manager.
• GCS and Forms Monitoring - The GCS and Forms Monitoring wizard helps you
troubleshoot the OAM Generic Collection Service. The GCS, or Generic Collection
Service, is a service managed by Generic Service Management. It performs file
uploading, signaling, purging, and other management tasks for other service runtime
processes such as the Forms Listener runtime process.
• CP Signature - This wizard collects information regarding the current status of concurrent
processing on the system.
Service Infrastructure
This wizard will list the potential issues with your Generic Service Management setup,
including:
• Active nodes without a service manager
• Active Concurrent Processing nodes without an Internal Monitor
• Service managers without active nodes
• Active nodes with inactive service managers
• Enabled service instances without workshifts
• Nodes that do not have names in uppercase (for service instances)
• Nodes that do not have names in uppercase (for processes)
CP Signature Wizard
The CP Signature wizard collects technical information on Concurrent Processing. This
information is what is most commonly requested by Oracle support analysts, and includes
items such as important configuration settings, code levels, and log files.
This wizard collects information on the following:
• Configuration status for Parallel Concurrent Processing, Real Application Clusters, and
Generic Service Management
• Registered nodes
• Concurrent processing package versions
• Concurrent processing package errors
• Concurrent processing profile options
• Service instances that could be managed by concurrent processing
• Concurrent processing processes
• Request processing manager specialization rules
• Request Conflict Resolution
• Concurrent request processing statistics
Copyright © Oracle Corporation, 2007. All rights reserved.
Support Cart
The Support Cart feature allows you to save Oracle Applications Manager pages with their
data and then zip them up in a file to send to Oracle Support. Oracle Support can then view
your pages in the Oracle Applications Manager display format.
When you click the Add to Support Cart global button, the page is added to the Support Cart.
If you have filtered or sorted the data, your manipulated view is submitted. To view the
contents of the Support Cart, click the Support Cart global button.
Description
You can enter in a TAR number and description of the issue here.
Applications Signature
The Support Cart can collect a standard set of information regarding your E-Business Suite
system. Oracle Support requires this information when logging a technical assistance request
(TAR).
To collect this information, click Collect.
The set of information collected includes:
Lesson Aim
An important area of security involves controlling access to reports and other concurrent
programs. This level of security is provided by request group definitions. This lesson shows
how the system administrator creates and uses these request groups.
Request sets are similar to request groups in that they are both collections of programs along
with their parameters and options. Request sets can be created by users, but they are still
managed by the system administrator.
Submitting Requests
(N) Concurrent > Requests > Submit a New Request > (B) Schedule...
The Schedule Window
The scheduling window provides you with several scheduling options. You can choose to reuse
a schedule you previously defined and saved, or define a new schedule. You can define your
schedule to run a request as soon as possible, at a specific time, or repeatedly at specific
intervals, or on specific days of the week or month.
When saving your schedule you must provide a unique name. You can also provide additional
information in the Description field.
Submitting Requests
(N) Concurrent > Requests > Submit a New Request > (B) OK > (B) Options...
Reprinting a Report
The Find Requests Window appears when you navigate to (N) Requests > View.
Note: The Profile Option Concurrent:Save Output must be set to Yes.
Pending Phase
A program in the Pending phase can be in one of four statuses:
• Normal: The program is waiting for an available manager.
• Waiting: A child program is waiting for a parent to mark it ready to run.
• Standby: A program is waiting for another incompatible program in the same logical
database to complete.
• Scheduled: A program’s scheduled start time has not yet elapsed.
Running Phase
A program in the Running phase can be in one of four statuses:
• Normal: Program is in progress.
• Paused: A parent program is waiting for one or more child programs to complete.
• Resuming: A parent program is continuing after the completion of one or more child
programs.
• Terminating: The program is being terminated.
Completed Phase
A program in the Completed phase can be in one of five statuses:
• Normal: Program completed successfully.
• Warning: Program completed successfully but with warning messages.
• Error: Program failed to complete successfully.
• Terminated: A running program was terminated.
• Canceled: A pending or inactive program was canceled before it started.
Inactive Phase
A program in the Inactive phase can be in one of three statuses:
• Disabled: The requested program has not been enabled for execution.
• On Hold: The requested program has been placed on hold.
• No Manager: There is no manager defined to run this type of request.
The code must not contain any spaces. The combination of the application and the code
identify the request group.
Customization Example
The slide shows the values that are used in the following example.
Linking of Stages
There are no restrictions on linking stages within a request set. Any stage can be linked to any
other stage, including itself. Two or more links can point to the same stage. For example, one
stage can link to another if the completion status of the first is Success or Warning, and link to
a third stage if the status is Error.
You determine the end of a request by not specifying a follow-up stage for each completion
status. You can end a request set after any stage in the set. When any stage completes with a
status that does not link to another stage, the request set ends.
You can use the linking of stages to control your request set. By using the Request Set Wizard
button in the Request Set window you can create the request set as follows:
• Run in Parallel – creates one stage containing all of the requests you wish to run in
parallel.
• Run Sequentially – creates a separate stage containing the request or requests for each step
in the sequence and link in the appropriate order.
• Run Sequentially but abort on Error – sets up your sequence the same as it did for Run
Sequentially, but when it links the stages, it does not enter a follow-up stage as a link in
the Error completion status field.
Request Parameters
((N) Requests > Set > (B) Define Stages > (B) Requests > (B) Parameters
Request Parameters Window
Use the Request Parameters window to customize the parameter values of a specific request in
a request set. The fields at the top of the Request Parameters window list general information
about the current request set for which you can customize the parameter values. The multi-row
portion of the window lists the parameters for that request.
• The Sequence and Prompt fields are display only.
• Selecting the Display check box specifies visibility of a request parameter at submission
time.
• Selecting the Modify check box to specifies you can insert or change the value for a
request parameter at submission time.
• Using the Shared Parameter field sets a default value for a parameter that occurs in more
than one report or program of a request set. Use the shared parameter label to set an initial
default value for all occurrences of the same parameter so you can avoid typing the same
value all over again for every occurrence of the parameter.
Lesson Summary
In this lesson you learned how to use request groups to control access to reports and concurrent
programs. Additionally you learned how individual users can define request sets to streamline
processing by setting default values for parameters and sharing parameter values among
multiple reports.
Lesson Aim
The Oracle Applications 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 any problems. He or she should also be able to balance workloads to provide the
optimum processing environment for users. This lesson teaches you how to monitor and
control system processing and also how to plan and schedule your workload.
Overlapping Workshifts
When work shifts overlap, the work shift with the more specific time period takes effect for the
overlapping time period. For example, a work shift for January 1 overrides a work shift from
9:00 am to 5:00 PM every Monday through Friday.
When work shifts with the same hierarchy level overlap, the work shift with the largest number
of target processes takes effect.
Concurrent Managers
(N) Concurrent > Manager > Define
Immediate Programs and Spawned Programs
Immediate concurrent programs are C or PRO*C subroutines linked with concurrent managers.
Most concurrent programs are spawned as independent processes at run time instead of running
as subroutines. If you are defining a new concurrent program, you should run the program as a
spawned program rather than as an immediate program.
Examples of these are:
• FNDLIBR: Contains immediate concurrent programs used by Oracle Applications Object
Library.
• INVLIBR: Contains immediate concurrent programs used by Oracle Inventory.
• MFCLIBR: Contains immediate concurrent programs used by Oracle Manufacturing.
• PALIBR: Contains immediate concurrent programs used by Oracle Projects.
Combined Rules
(N) Concurrent > Manager > Rule
Action Types
Use action types to specify the actions of a manager. An action type specifies the type of
request to which an action refers.
• Programs that connect to a specific Oracle Applications account (Oracle ID). For
example, you could include for processing all programs that connect to the Oracle
Payables account AP1.
• Specific programs by name. For example, you could include for processing the Oracle
General Ledger program Trial Balance-Budget. When using an action type of program,
you specify the application and the program name.
• Certain request types. For example, you could include for processing all programs
defined as a request type of Month-End Reports.
• Programs requested by certain users. For example, you could include for processing all
programs requested by the user “Operations”.
• Combined rule. A combined rule combines more than one action to generate a single
rule.
Lesson Summary
In addition to controlling access to Oracle Applications, monitoring the day-to-day processing
of Oracle Applications is a very important job of the system administrator.
The system administrator is the first point of contact when users have, or suspect they have, a
problem with either the results or the processing of a request. The system administrator has
access to several application log files containing diagnostic information that can be of use in
correcting problems.
The system administrator is also responsible for balancing workload to maintain optimum
performance for users. He or she does this by creating concurrent managers to process user
requests. Managers can be specialized to operate only during certain times and to process only
certain types of requests. System administrators also monitor and control the activity of
managers in a parallel environment.
Traditional Workflow
Traditional applications-based workflow processes are launched from a business application
through APIs hard-coded within the application. These processes model the business rules in
the individual local application and are made up of activities executed by the Workflow Engine
only in that application’s system. For example, the modeling of an approval hierarchy is a
common use of Oracle Workflow in this scenario.
Event-Based Workflow
With the Business Event System, Oracle Workflow supports both traditional applications-
based workflows and event-based integration workflows.
For e-business, there is a requirement to integrate with external systems, such as sending a
document to a business-to-business exchange, or other systems external to the local
application. Oracle Workflow supports e-business integration workflows by allowing business
analysts and developers to model business processes spanning different systems using a
graphical drag-and-drop designer—the Workflow Builder—and run those processes using the
Workflow Engine and the Business Event System. This support enables Oracle Workflow
customers to deal with business objects in comprehensive e-business integration flows with
minimal intrusion into the core application.
The Business Event System and the Workflow Engine can function independently of each
other. However, you can achieve the most powerful and flexible processing by using the
Business Event System and the Workflow Engine together to execute cross-system processes
for e-business integration.
Subscription-Based Processing
The Business Event System provides increased flexibility through subscription-based
processing: you raise a business event from an application, but specify the processing to
perform for that event as a subscription in Oracle Workflow. For example, you can launch a
workflow process when an event is raised by specifying that process in a subscription to the
event. You can also define multiple subscriptions to the same event to perform additional
processing for different purposes without intruding any further on the core application.
Workflow Processes
A workflow process definition must be saved to the same database as the Workflow Engine. A
process definition is composed of activities and the transitions between them.
• A completed application transaction or event can initiate a workflow process by raising an
event or by calling a series of Workflow Engine APIs.
• The Workflow Engine locates the “Start” activity in the process definition.
• The Workflow Engine drives through the process, performing all automated steps such as
function activities and Raise and Send event activities, until an asynchronous activity such
as a notification, Receive event activity, or blocking activity occurs.
- The Workflow Engine calls the Notification System to deliver a notification message
to an appropriate role. Once a user of that role completes the notification response,
the Workflow Engine continues to drive through the remaining activities in the
process.
- If a blocking activity is encountered, the Workflow Engine waits for an external
program to complete and call the appropriate Workflow Engine API before
proceeding to the next activity.
Notification System
The Notification System:
• Routes notifications to a role, which can be a single user or group of users
• Enables users to receive and respond to notifications using an e-mail application or Web
browser of choice
• Sends e-mail notifications and processes e-mail responses using the JavaMail API
• Allows any users with access to the Internet to be included in a workflow process
• Provides access to the Worklist from Oracle E-Business Suite through the Worklist web
pages
• Enables users to drill down from a notification in the Worklist web pages to any URL or
Oracle E-Business Suite form to respond to the notification
Directory Services
Users can be associated with more than one role, and a role may contain more than one user.
The Workflow Engine and Notification System use the directory service to determine who
should receive notifications and in what format. Notifications can be delivered to an individual
user or to all members of a particular role.
Note: Oracle Workflow uses a directory service model in which denormalized information is
maintained in the Workflow local tables for performance gain. You should maintain
synchronization between the user and role information stored in application tables by the
source modules and the information stored in the Workflow local tables.
Workflow Monitor
Oracle Workflow includes both administrator and self-service versions of the Status Monitor in
the Oracle Application Framework user interface format.
Workflow Manager
Administrators can use Workflow Manager to perform the following tasks:
• Run Workflow service components, such as notification mailers and agent listeners.
• Control other Workflow system services, including background engines, purging obsolete
Workflow data, and cleanup of the Workflow control queue.
• Monitor work item processing by viewing the distribution of all work items by status and
drilling down to additional information.
• Monitor event message processing for local Business Event System agents by viewing the
distribution of event messages by status and drilling down to additional agent information
and individual event messages, as well as by viewing queue propagation details.
With this ability to monitor work items and event messages, a system administrator can
identify possible bottlenecks easily.
Service Components
Oracle Workflow uses the Generic Service Component Framework (GSCF) to simplify and
automate the management of background Java services. A service component is an instance of
a Java program that has been defined according to the GSCF standards so that it can be
managed through this framework.
Use Oracle Workflow Manager to configure and run service components.
Note: Oracle Workflow Manager also lets you manage Web services outbound components,
which process outbound Web service messages for Oracle XML Gateway. For more
information, see the Oracle XML Gateway User’s Guide.
Scheduling Propagation
If you want to use the standard WF_OUT and WF_JMS_OUT agents or custom agents for
event message propagation, ensure that you schedule propagation for those agents.
Scheduling Propagation
For information about using Oracle Enterprise Manager to schedule Oracle Advanced Queuing
propagation, refer to Oracle Enterprise Manager Support, Oracle Streams Advanced Queuing
User's Guide and Reference and the Oracle Enterprise Manager online help.
Scheduling Propagation
The Schedule_Propagation API parameters are:
• queue_name: The queue associated with the local outbound agent for which you want to
schedule propagation. Specify the queue name prefaced by the schema that owns the
queue, in the following format: <schema>.<queue>
The standard Workflow queues are usually owned by the APPLSYS schema.
• destination: The database link to the remote system to which you want to propagate
messages. To propagate messages to another queue on the local system, enter the
destination NULL. The default value is NULL.
• start_time: The initial start time for the propagation window.
• duration: The duration of the propagation window, in seconds
• next_time: A date function to compute the start of the next propagation window from the
end of the current window. For example, to start the window at the same time every day,
next_time should be specified as 'SYSDATE + 1 - duration/86400'. If this value is NULL,
then propagation is stopped at the end of the current window and is not run repeatedly.
The default value is NULL.
Tuning Performance
Changing the Maximum Cache Size for the Business Event System
The Business Event System caches event, subscription, and agent definitions to enhance
performance during subscription processing. The default maximum size of the cache is 50
records. You can optionally increase the maximum cache size to reduce the database queries
performed by the Business Event System, or decrease the maximum cache size to reduce the
amount of memory used by the cache.
The maximum cache size is determined by the value for the WFBES_MAX_CACHE_SIZE
resource token. To change this value, you must first create a .msg source file specifying the
new size as the value for the WFBES_MAX_CACHE_SIZE resource token. Then use the
Workflow Resource Generator program to upload the new seed data from the source file to the
database table WF_RESOURCES. See: To Run the Workflow Resource Generator, Oracle
Workflow API Reference.
Enabling Static Function Calls for Custom PL/SQL Functions
If you use custom PL/SQL functions within the Business Event System, including event data
generate functions, event subscription rule functions, and queue handler enqueue and dequeue
Overview of Flexfields
Chapter 18 - Page 1
Copyright © Oracle Corporation, 2007. All rights reserved.
Overview of Flexfields
Chapter 18 - Page 2
Overview of Flexfields
Overview of Flexfields
Chapter 18 - Page 3
Objectives
Lesson Topics
This lesson describes how to use modifiable fields called flexfields to tailor Oracle
Applications to reflect your business needs and practices.
You can use flexfields to define the structure of certain data identifiers required by Oracle
Applications. You can also gather, store and process additional data that may be required by
your business.
After completing this lesson, you should be able to:
• Explain flexfields and how they are used by Oracle Applications
• Distinguish between key and descriptive flexfields
• Identify key and descriptive flexfields used by Oracle Applications
• List the benefits provided by flexfields
Overview of Flexfields
Chapter 18 - Page 4
Overview
Lesson Overview
This lesson describes how Oracle Applications uses customizable fields called flexfields to
modify and expand processing. Specifically it covers:
• How flexfields operate
• The two types of flexfields
• Flexfield terminology
• Flexfield benefits
Overview of Flexfields
Chapter 18 - Page 5
Customizing Oracle Applications
Overview of Flexfields
Chapter 18 - Page 6
Flexfield Structures and Flexfield Segments
Flexfield Components
A flexfield is composed of segments. The segments of a flexfield contain the flexfield values.
Flexfield segments are combined in a grouping called a structure. The segments that make up a
particular structure are logically or functionally related. A single flexfield can have more than
one structure.
When you implement a flexfield, you decide how many segments you need for a particular
structure and whether you need multiple structures. Being able to define different structures for
the same flexfield allows you to tailor the same flexfield to the needs of different end users.
The example on the slide shows three segments:
• Category
• Item
• Color
These three segments together form a structure.
Overview of Flexfields
Chapter 18 - Page 7
Segment Prompts and Value Descriptions
Overview of Flexfields
Chapter 18 - Page 8
Validating Input Using Value Sets
Overview of Flexfields
Chapter 18 - Page 9
Key and Descriptive Flexfields
Overview of Flexfields
Chapter 18 - Page 10
Key Flexfields
Key Flexfields
In Oracle Applications you use key flexfields as identifiers for entities. Generally, the identifier
you create using a key flexfield is required by the application (for example, the Accounting
Flexfield builds the account number used by Oracle General Ledger).
A key flexfield appears as a normal field on a form. Any existing value for the key appears in
the field as a concatenated value having segment separators.
You can use the Flexfields: Open Key Window profile option to specify whether you want the
key flexfield window to be opened automatically when you navigate to the key flexfield on the
base form. This profile option is visible and updatable at the user level.
A key flexfield structure usually consists of multiple segments, each of which contains
meaningful information. The resulting combinations of values from these segments therefore
function as intelligent keys.
Overview of Flexfields
Chapter 18 - Page 11
Intelligent Keys
Overview of Flexfields
Chapter 18 - Page 12
Intelligent Keys
Overview of Flexfields
Chapter 18 - Page 13
Key Flexfield Example: Accounting Flexfield
Overview of Flexfields
Chapter 18 - Page 14
Oracle Applications Key Flexfields
Overview of Flexfields
Chapter 18 - Page 15
Descriptive Flexfields
Descriptive Flexfields
You use descriptive flexfields to collect information beyond what is collected by Oracle
Applications. Using descriptive flexfields allows you to gather additional specialized
information required by your business. The use of descriptive flexfields is optional.
A descriptive flexfield appears on a form as a double-character field enclosed by brackets. You
can use the Flexfields: Open Descr Window profile option to specify whether you want the
descriptive flexfield window to be opened automatically when you navigate to the bracketed
field, if the flexfield is enabled. This profile option is visible and updatable at the user level.
A descriptive flexfield typically uses multiple structures. You can:
• Define a basic structure that gathers additional information for all entities.
• Define several different structures that gather specialized information for different types of
the same general entity.
• Define a combination of the preceding two. This structure can gather general information
about all entities and then optionally gather certain information about certain types of
entities.
The example shows a descriptive flexfield that gathers different payment information based on
the type of payment: check (CK) or credit card (CC).
Overview of Flexfields
Chapter 18 - Page 16
Using Reference Fields
Overview of Flexfields
Chapter 18 - Page 17
Using Different Contexts: Asset Category Flexfield
Overview of Flexfields
Chapter 18 - Page 18
Oracle Applications Descriptive Flexfields (Partial)
Overview of Flexfields
Chapter 18 - Page 19
Standard Request Submission (SRS) and Flexfields
Overview of Flexfields
Chapter 18 - Page 20
Benefits of Flexfields
Benefits of Flexfields
You should now have a basic understanding of how flexfields are used by Oracle Applications.
The ease of configuring flexfields provides many benefits to users. The main benefits are listed
on the slide.
Overview of Flexfields
Chapter 18 - Page 21
Storing Flexfield Data Internally
Overview of Flexfields
Chapter 18 - Page 22
Implementing a Flexfield Steps
Overview of Flexfields
Chapter 18 - Page 23
Summary
Summary
Flexfields are Oracle Applications fields that you can configure. You can define the content
and layout of the flexfield to reflect your own business needs.
There are two types of flexfields:
• Key flexfields are used to create entity identifiers required by Oracle Applications. You
can use key flexfields to structure these identifiers according to your business
environment. The definition of many key flexfields is required by the application.
• You use descriptive flexfields to gather additional information for storage or processing.
You can define descriptive flexfields in multiple ways to accommodate the needs of many
different groups of users. The use of descriptive flexfields is optional.
Overview of Flexfields
Chapter 18 - Page 24
Using Value Sets
Chapter 19
Lesson Topics
This lesson describes planning and using value sets to control input with flexfields. At the end
of this lesson, you should be able to:
• List options for validating flexfield segment values and report parameters
• Choose the appropriate validation option to use with a particular segment
• Identify issues for consideration when planning a validation strategy
• Define new value sets
• Define allowable values for a value set
Lesson Overview
Value sets are definitions of allowable values for use with a flexfield segment or report
parameter. This lesson covers the different types of value sets and how each is used. It also
describes how to plan the value set as well as the actual values for those sets that require a list
of values. Finally, it covers the definition process itself.
Formatting Types
You can require one of several types of data formatting. When you declare a value set a
particular format type, all data entered in the segment that uses this value set must match the
requirements of the format.
For some format types, there are additional options.
The various format types and options are discussed on the following pages.
Lesson Topics
This lesson describes the process required to plan a descriptive flexfield.
At the end of this lesson, you should be able to:
• Identify the descriptive flexfield to be used and the information to be gathered
• Organize the information according to usage
• Plan the layout of the descriptive flexfield
• Plan the behavior of the descriptive flexfield
• Define the descriptive flexfield structure
• Define global segments
• Define context-sensitive segments as appropriate
Lesson Overview
Descriptive flexfields allow the user to gather additional information beyond that gathered by
Oracle Applications. The information gathered by a descriptive flexfield and the structure of
that information can vary between different users. This lesson covers analyzing and organizing
the additional data, designing the different flexfields layouts, and specifying how the
descriptive flexfield will behave.
This lesson also covers the mechanics of defining a descriptive flexfield. Flexfields consisting
of only global segments as well as both global and context-sensitive segments are covered.
Context-Sensitive Segments
Context sensitive segments occur depending on the context.
The slide shows sample contexts and the segments that are unique to each of them.
Synchronizing the Context Field Value with the Reference Field Value
You can optionally set up your flexfield so that the context field value is synchronized with the
reference field value. You may have instances where, when querying existing records, you
want the context field value to match the original reference field value, but with new records,
you want the context field value to be derived from the current reference field value.
For example, say the context field is Country Code (IN for India, AU for Australia, and so on).
This information should be constant for the lifetime of a given record, such as an Expense
Report; that is, it remains constant from the original data entry (and saving of the record) to
subsequent queries on the record.
In this example, the Country Code value could be captured as a profile option value specific to
the user (the reference field). The desired behavior of which Country Code value is used by the
descriptive flexfield may depend on the action at runtime. For example, say an expense report
is created by an employee in India, with a Country Code of IN. If payment processing is done
in Australia and the Australian (Country Code: AU) Payables Approver queries the Indian
employee's expense report, the expected default Country Code context field value is IN; it is
not derived from the Australian Payables Approver's profile option value of AU. However, if
Summary
This lesson discussed how to plan a descriptive flexfield. Descriptive flexfields gather
additional information beyond that gathered by Oracle Applications. Not all users of the same
descriptive flexfield need the same information. Descriptive flexfields can be customized so
that each user sees only the information needed.
Once you have planned the structure of your descriptive flexfield, the actual definition process
is straightforward. If this flexfield uses any new value sets, plan those first. Define the flexfield
header attributes. Define all global segments for the Global Data Elements structure.
If you are using multiple contexts, define either a reference field on the base window, or a
context field on the flexfield itself to control which context structure appears. For each context,
define a structure containing the segments appropriate for that context.
When you have finished defining all your structures and segments, freeze your definition and
compile the flexfield. This makes the flexfield available for others to use.
Lesson Topics
At the end of this lesson, you should be able to:
• Explain intelligent keys and provide examples
• Identify key flexfields that are required by Oracle Applications
• Explain the purpose of flexfield qualifiers and optional key flexfield features
• Design a key flexfield structure
• Define the key flexfield structure and segment attributes
• Define flexfield qualifiers and segment qualifiers
Lesson Topics
At the end of this lesson, you should be able to:
• Explain the purpose for cross-validation
• Define cross-validation rules and control the interaction between multiple rules
• Identify candidates for shorthand entry
• Plan and define useful shorthand aliases
• Enable shorthand entry
• Explain how flexfield security is accomplished
• Identify which flexfields are candidates for security
• Design a security plan
• Control interactions between security rules
• Define and assign security rules
• Enable security
Overview
Key flexfields create unique identifiers for use internally by Oracle Applications. The
combinations of values for the segments of a key flexfield identify entities. These code
combinations are used throughout Oracle Applications.
Depending on which key flexfield you are defining, you might need to specify flexfield
qualifiers and segment qualifiers. There are also several optional features of key flexfields you
may wish to implement.
This lesson covers the mechanics of the definition process.
Overview, continued
This lesson describes additional flexfield options, including:
• Cross-validation - Cross-validation rules let you control the combination of values
entered for a key flexfield.
• Shorthand aliases - Shorthand aliases let you label certain groupings of values for a
multi-segment flexfield. Whenever you need one of these groupings of values, you can use
the alias for that grouping to enter the entire group.
• Security rules - Security rules let you control flexfield access to data. You create and tie
security rules to a value set to specify which entries in a list of values are available to a
user of a specific responsibility. This allows you to control that user’s access to data. You
create security rules by defining inclusion or exclusion statements. You combine these
statements to create a security rule. You must carefully consider the interaction of multiple
rules when planning your security.
Securing Values
You may want to allow users to only enter or view specific values for flexfields.
You can create a security rule to restrict values available to a given responsibility. Once you
associate that rule to the appropriate responsibility, all users of that responsibility are restricted
to the values allowed by that security rule.
For example, a company has assigned its sales force to different responsibilities according to
the type of items they sell. Two of these responsibilities are Electronic Sales and Household
Sales. A value set called Item Type lists all the types of items the company sells. In this case,
you can define a security rule to restrict the users of a particular responsibility to only access
item types appropriate for their responsibility. For example, the Household Goods Only
security rule allows access only to the FURN and APPL item types.
Security rules are discussed in more detail later in this lesson.
Planning Decisions
Application Question: Does the application support different segment structures?
Related Question: How many structures are needed?
Application Question: What flexfield qualifiers does this flexfield use or need?
Related Question: Do segments correspond to each needed qualifier?
Summary
Key flexfields are used to build identifiers required by Oracle Applications. Key flexfields
allow the user to provide information needed by Oracle Applications while still structuring that
information to reflect a particular business environment.
The procedure for defining a key flexfield is similar to that for defining a descriptive flexfield.
However, there are additional attributes for key flexfields that may also need to be defined.
Additionally, key flexfields have several optional features that should be implemented where
appropriate.
The additional requirements and options for key flexfields include:
• By using qualifiers in key flexfields you can require that certain segments and certain
values be identified for processing.
• You can allow security checking and integrity checking.
• You can define aliases to speed data entry.
• You can enter key flexfield value combinations from different windows, if allowed.
Summary, continued
Cross-validation rules are used to restrict invalid combinations of segment values. Rules are
defined by specifying the value combinations that are either allowed (included) or disallowed
(excluded). Cross-validation rules are not tied to a responsibility like security rules. You can
combine cross-validation rules as needed.
Short aliases provide a way to speed entry of frequently used value combinations. Any key
flexfield is a candidate for shorthand alias entry.
You can control the access to data by defining value security rules. These rules list the
allowable values for display or selection through a flexfield segment. The rules are applied to
the value set defined for that flexfield segment. Once you have defined the rules, you assign
them to a responsibility. All users of that responsibility are then restricted to the approved
values when using the flexfield’s segment.
Lesson Topics
A previous lesson discussed creating and using value sets to check user input. You performed
practices in which you defined value sets of the validation types None, Independent, and
Dependent.
In this lesson, you learn how to use values stored in applications tables for validation. You also
learn how to restrict the set of values returned from the table.
At the end of this lesson, you should be able to:
• Use values retrieved from application tables for validating input
• Reference profile option values when validating input
• Use a value from another field on the same form for validation
• Use the value from a previously used value set for validation
Overview
There are several advanced techniques you can use when defining value sets for validating
input. These techniques use values obtained from a location other than a list specifically
defined for the value set. These locations include:
• Values retrieved from an application table
• The current value for a particular profile option
• A value used earlier in a field on the form
• A value used earlier in another value set
Summary
Some value sets (for example, Independent and Dependent) have lists of approved values
explicitly defined. Other types of value sets, however, can use values from other locations for
validation. Using values from an application table is one example of these alternate locations.
Also, the current value of a profile option can be used. The value from a previously appearing
field on a form can be referenced as well. Finally, the value from a previously used value set
can be used by all subsequent value sets.
Form Fields
(N) Application > Administer Folders
• Public: This check box governs the availability of the folder to all users.
• Anyone’s Default: Indicates whether this folder definition is used as a default by a user or
a responsibility. If it is a default definition, use Default Assignments to view the users and
responsibilities for which it is the default folder definition.
• Default Assignments: The users and responsibilities that use this folder definition as a
default.
Lesson Aim
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
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
Applications environment as well. In that environment they can be secured and managed the
same way as regular Oracle Applications programs.
This lesson covers how to integrate user-developed programs into Oracle Applications.
Lesson Aim
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
by adding your own to the system. This lesson covers how to integrate customized help files
into Oracle Applications.
Note
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 (Help) Applied Technology > Oracle Applications System Administration > Configuration
> Loaders > Generic File Manage Access Utility for additional information.
Help Builder
To access the Help Builder, you can use the System Administration responsibility and select
Help Builder under Help Administration.
Your task is to create an Application user that you will utilize over the course of your testing.
In order to facilitate all the testing you will accomplish over this week, you will preface ALL
your exercises with your initials (e.g., JSCS for Jane S.C. Smith). This will help you find the
specific data you have created.
Tasks
Create the User
Assign Responsibilities
• System Administrator
• System Administration
• Application Developer
• Functional Developer
3. Accept the defaults for all other fields. Use the Security Group "Standard" for a
responsibility if none defaults in.
5. Change the password when prompted. You change the password by typing the old password,
(WELCOME), and then assigning a new password. You will re-type the new password to
verify.
1. Log in to Oracle Applications with user name “SYSADMIN” and password “SYSADMIN”.
2. Select the System Administrator responsibility under the “Applications” heading of the
Navigate region of the Personal Home Page.
3. Navigate to the Users form: (N) Security > User > Define.
• System Administrator
• System Administration
• Application Developer
• Functional Administrator
• Functional Developer
Note: Use the Direct Responsibilities tab. The Indirect Responsibilities are assigned via
Oracle User Management.
6. Click the Save icon to save your work. Your completed form should look similar to the
example shown in the slide.
7. Close the Users form. Choose File > Exit Oracle Applications to return to the home page.
9. Use your new login and password (WELCOME) 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.
10. Verify that you have the correct Responsibilities displayed, and select the System
Administrator Responsibility. (Note: Depending on your setup, the Home Page may differ
from the illustration).
Tasks
Register your Custom Application
1. Create your new custom application. Remember to put your initials at the front of your data
entries to keep your data unique.
• Base Path: FND_TOP (Note: For class purposes we are using a predefined basepath. If
you were defining a true custom application, this would be a unique basepath.)
1. If not currently logged in, log in to Oracle Applications with your user.
3. Enter your Application: YourInitials Custom Application (e.g., JSCS Custom Application)
9. Place your cursor in the Data Group field and query the Standard data group by selecting
View from the application menu > Query By Example > Enter.
10. Enter “Standard” in the Data Group field and then execute the query by selecting View from
the application menu > Query By Example > Run.
11. Ensure your cursor is in the Application field and click the New toolbar icon or select New
from the File menu to add a row.
12. Select your custom application name from the list of values for the Application field.
13. Select APPS from the list of values for the Oracle ID field.
14. Save your work. Your window should look like the example shown below.
• Create a System Auditor responsibility, and associate your new menu to that
responsibility
• Assign the System Auditor to a new user and test the user and responsibility.
Tasks
Create your Level 3 Menu
Menus in Oracle Applications must be created bottom-up. Your first task is to create your lowest
level menu.
1. Create a new menu. Remember to put your initials at the front of your data entries to keep
your data unique.
• User Menu Name: YourInitials Flexfield Security (e.g., JSCS Flexfield Security)
2. Create a new menu. Remember to put your initials at the front of your data entries to keep
your data unique.
3. Create a new menu. Remember to put your initials at the front of your data entries to keep
your data unique.
5. Create a new responsibility. Remember to put your initials at the front of your data entries to
keep your data unique.
6. Create a new user. Remember to put your initials at the front of your data entries to keep
your data unique.
• Password: WELCOME
7. Test the new user, new responsibility, and new menu to ensure that they are working
properly.
• User Menu Name: YourInitials Flexfield Security (e.g., JSCS Flexfield Security)
4. Save your work. You should see a note indicating that your request has been submitted to
recompile your menu. Click (B) OK to acknowledge the note. Your work should look
similar to the following.
7. Save your work and click (B) OK to the note window indicating that your request has been
submitted to recompile your menu in the database. Your work should look similar to the
following.
10. Save your work and click (B) OK to the note window indicating that your request has been
submitted to recompile your menu in the database. Your work should look similar to the
following.
12. If necessary, log in to Oracle Applications and select the System Administrator
responsibility.
15. Save your work. Your work should look similar to the following.
16. If necessary, log in to Oracle Applications and select the System Administrator
responsibility.
• Password: WELCOME
19. Save your work. Your work should look similar to the following.
20. Test the new user, new responsibility, and new menu to ensure that they are working
properly. Exit Oracle Applications and return to your home page.
23. From the home page, click on YourInitials System Auditor responsibility.
24. Verify that your Navigator menu contains the correct items. Your screen should appear
similar to the example shown in the slide.
• Replace the Define Responsibilities function with this query-only function on your
existing System Auditor menu
Tasks
Create your Query-Only Function
1. Create a new Form Function. Remember to put your initials at the front of your data entries
to keep your data unique.
• Type: Form
• Parameters: QUERY_ONLY=YES
1. Query the YourInitials_RESPONSIBILITY menu in the Menu form. Replace the prompt,
function and description for Seq 10 Define Responsibilities.
Description tab:
− Function: YourInitials_ FNDSCRSP (e.g., JSCS_FNDSCRSP)
− User Function Name: YourInitials View Responsibilities
− Description: View Responsibilities
Properties tab:
− Type: Form
− Maintenance Mode Support: None
− Context Dependence: Responsibility
4. Save your work. Your work should look similar to the following.
• Put the form in query mode by pressing F11 or by selecting (M) View > Query by
Example > Enter.
• Enter YourInitials_RESPONSIBILITY in the Menu Name field and execute your query
by pressing Ctrl-F11 or by selecting (M) View > Query by Example > Run.
8. Replace the prompt, function and description for Seq 10 Define Responsibilities.
9. Save your work. Your work should look similar to the following.
12. Your menu should be similar to the example shown in the slide.
• Modify the responsibility by excluding functions and menus from its menu
Tasks
Create New Responsibility
1. Create a new responsibility. Remember to put your initials at the front of your data entries to
keep your data unique.
2. Modify access to certain menus and functions for your new Responsibility by excluding the
items below. Menu or Function Names to exclude:
• Menu, NAVSECVAL4.0
3. In order to test this new responsibility, create a new user signon for your assistant system
administrator and assign your newly created responsibility to this user. Use the information
listed below.
4. 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.
5. Query your user (YourInitialsUser) you created, and add this responsibility to that user.
1. If not currently logged in, log in to Oracle Applications with your user.
6. 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.
Note: For each of the responsibilities shown below, ignore the Excluded Items and
Security Attributes tabbed regions.
• Function, Responsibilities
• Menu, NAVSECVAL4.0
10. Use the information listed below to create your new assistant system administrator user:
14. Enter your new user name and password. You will be prompted to change your password.
15. From the home page, select YourInitials Assistant System Administrator responsibility.
16. Review the menu items for your new responsibility and verify the correct items appear.
17. Navigate to the Users form (N) Security > User > Define.
19. Enter the user name you created in the Name field (i.e., YourInitialsUser) and execute your
query by pressing Ctrl-F11 or by selecting (M) View > Query by Example > Run.
21. Insert a new record by clicking the New icon on the toolbar, and select YourInitials
Assistant System Administrator.
This guided demonstration shows a data security policy implementation and its definition.
You must log in as the SYSADMIN user to access the User Management responsibility.
5. Click on the “User Administration privileges” link to show details for the grant defined for
the set of users shown, “People in the Administrator's own Organization”.
2. In the Objects page, perform a search for the object with the code
UMX_PERSON_OBJECT.
5. Click on the name “People in the Administrator’s own Organization” to view the details of
this object instance set.
6. Note the predicate. The SQL statement queries the set of users based upon the party
relationships defined in TCA (the organization).
3. Enter the required information in the Lookup Codes fields. In this case, the name is
“Administration” and the description can be something about a general category for
administration roles.
5. Click the Role Categories tab to view the newly created “Administration” role category.
Business Scenario:
Vision Inc. is a computer systems company. The company offers its customers a full range of
computer systems and office equipment. Additionally, the company offers an array of services to
support its customers' products. Vision has decided to implement Oracle User Management to
have a flexible and scalable system for managing access privileges and user accounts.
The company wants to distribute some of its security and administrative tasks to local
administrators instead of having the system administrator retain them exclusively. To accomplish
this, the company will create roles for a partner administrator, a security administrator, and a
customer administrator. Individuals who are assigned these roles will manage a discrete subset
of the company’s users, roles, and external contacts.
As part of the implementation team, you need to perform the following tasks:
• Grant the appropriate permissions for the role so that assignees can perform specific
actions on the users they manage
• Create a registration process for the role so that users can request it via self service
Assumptions
• Some parts of Oracle User Management have already been implemented, including the
Partner Administrator and Security Administrator roles as well as the User Management
responsibility and several permissions.
• Oracle User Management ships with seeded roles including Partner Administrator,
Security Administrator, and Customer Administrator. Assume for the purposes of this
course, the Customer Administrator role does not exist, and the students must create it.
Assign the Security Administrator Role to the “YourInitialsUser” to enable the User
Management responsibility for your user.
Create a customer administrator role called “YourInitials Course Administrator” within the
Security Administration Role Category.
After creating your Course Administrator role, you will need to place it in a role inheritance
hierarchy so that it is inherited by the Partner Administrator role and it inherits the User
Management Responsibility.
Login: sysadmin/sysadmin
• Click (B) Go
• Click (B) Go
6. Login as YourInitialsUsers (e.g., JSCSUSER), verify you have the User Management
responsibility
13. Select the Add Node icon on the “Partner Administrator” role.
18. Select the Add Node icon on “YourInitials Course Administrator” role beneath the “Partner
Administrator” role.
19. Enter “FND%UMX” into the Code field under the Search region, and then select (B) Go.
21. Verify “YourInitials Course Administrator” role inherits the User Management
responsibility which is inherited by the Partner Administrator role by viewing it in the Role
& Responsibility Hierarchy area.
Business Scenario:
Vision Inc. is a computer systems company. The company offers its customers a full range of
computer systems and office equipment. Additionally, the company offers an array of services to
support its customers' products. Vision has decided to implement Oracle User Management to
have a flexible and scalable system for managing access privileges and user accounts.
The company wants to distribute some of its security and administrative tasks to local
administrators instead of having the system administrator retain them exclusively. To accomplish
this, the company will create roles for a partner administrator, a security administrator, and a
customer administrator. Individuals who are assigned these roles will manage a discrete subset
of the company’s users, roles, and external contacts.
As part of the implementation team, you need to perform the following tasks:
• Grant the appropriate permissions for the role so that assignees can perform specific
actions on the users they manage
• Create a registration process for the role so users can make a self service request
Assumptions
• Some parts of Oracle User Management have already been implemented, including the
Partner Administrator and Security Administrator roles as well as the User Management
responsibility and several permissions.
• Oracle User Management ships with seeded roles including Partner Administrator,
Security Administrator, and Customer Administrator. Assume for the purposes of this
course, the Customer Administrator role does not exist, and the students must create it.
4. Click the Update icon next to “YourInitials Course Administrator” role and then click (B)
Create Grant.
5. Enter a name and description for the grant (for example, UMX Menus) and click (B) Next.
6. In the Set field, enter “User Maintenance UIs”, and then click (B) Next.
9. Click (B) OK to the confirmation message to acknowledge that the grant has been
successfully created.
Business Scenario:
Vision Inc. is a computer systems company. The company offers its customers a full range of
computer systems and office equipment. Additionally, the company offers an array of services to
support its customers' products. Vision has decided to implement Oracle User Management to
have a flexible and scalable system for managing access privileges and user accounts.
The company wants to distribute some of its security and administrative tasks to local
administrators instead of having the system administrator retain them exclusively. To accomplish
this, the company will create roles for a partner administrator, a security administrator, and a
customer administrator. Individuals who are assigned these roles will manage a discrete subset
of the company’s users, roles, and external contacts.
As part of the implementation team, you need to perform the following tasks:
• Grant the appropriate permissions for the role so that assignees can perform specific
actions on the users they manage
• Create a registration process for the role so users can make a self service request
Tasks
Assigning the User Maintenance UIs to the Course Administrator Role
2. Locate “YourInitials Course Administrator” role and click the Update icon.
Define the users that can be managed through this role by performing the following:
4. Click the Run Wizard icon for "User Management: Security Administration Setup".
5. Verify User Administration tab is selected and click (B) Add More Rows.
Define the Roles that can be managed by this role by performing the following:
8. Select Organization Administration tab and then click (B) Assign Organization Privileges.
9. Perform a wildcard search in the Search By Organization Privileges, select “View the
Administrator’s Own Organization”
Define the Roles that can be managed through this role by performing the following:
11. In the Available Roles area, search for “YourInitials Course Administrator” role and place it
in the Selected Roles area. Assignees of “YourInitials Course Administrator” role will be
able to grant “YourInitials Course Administrator” role to other users.
12. Optionally perform a wildcard search (e.g., %Support%) on Miscellaneous in the Type field.
Then select one or more roles from the search results, move them to the Select Roles area.
Following is an example:
13. Click (B) Apply. The assignee of “YourInitials Course Administrator” role will be able to
assign the selected roles to the users that he or she can manage.
Business Scenario:
Vision Inc. is a computer systems company. The company offers its customers a full range of
computer systems and office equipment. Additionally, the company offers an array of services to
support its customers' products. Vision has decided to implement Oracle User Management to
have a flexible and scalable system for managing access privileges and user accounts.
The company wants to distribute some of its security and administrative tasks to local
administrators instead of having the system administrator retain them exclusively. To accomplish
this, the company will create roles for a partner administrator, a security administrator, and a
customer administrator. Individuals who are assigned these roles will manage a discrete subset
of the company’s users, roles, and external contacts.
As part of the implementation team, you need to perform the following tasks:
• Grant the appropriate permissions for the role so that assignees can perform specific
actions on the users they manage
• Create a registration process for the role so that users can self service request it
Tasks
Assigning the Course Administrator Role to a User
Query a user in the system and assign the user “YourInitials Course Administrator” role.
View Role Capabilities by Logging on as the User to Whom the Role is Assigned
Log on as the user to whom the role is assigned and view that user’s administrative capabilities.
Over the course of the next two practices, each workstation team will need to have individual
accounts that they (and only they) use. Without this exclusivity, students will collide during the
exercise. Please use the following email addresses to locate the user accounts assigned to your
workstation.
1. (N) Users
2. In the Email field within the search area enter “<your assigned email address per list>” and
click (B) Go.
3. The person with your assigned email address is displayed in the result set. Click the Create
User icon for this person.
Note: The name displayed in the search result is a person in the system and not a user. As
part of this procedure you will assign this person a user account that includes your Course
Administrator role.
5. Reset the user’s password by typing “welcome1” in the Password and Confirm Password
fields and click (B) Submit.
6. Query the user again by searching for your assigned user’s email address such as
‘jsnyder@cds.com’.
7. Click the Update icon next to the user and then click the (B) Assign Roles.
8. In the search window, search for “YourInitials Course Administrator” role. Select this role
and click (B) Select.
9. Enter a justification in the Justification filed and click (B) Apply. You will see a
confirmation message indicating you have successfully updated the role.
Logging on as the User to Whom the Course Administrator Role is Assigned and
Viewing that User’s Administrative Capabilities
10. Log out of the system and log on as your assigned user’s address by entering the following:
11. When prompted, reset the user’s password from “welcome1” to “welcome”.
12. You should be able to view and use the User Maintenance UIs upon logging in.
Observe: The Organization field is populated with the name of the organization to which
your user is associated. If your assigned user is associated with more than one organization,
you will see a drop-down allowing you to select which organization’s user you want to
manage. Following is an example of what you would see:
Business Scenario:
Vision Inc. is a computer systems company. The company offers its customers a full range of
computer systems and office equipment. Additionally, the company offers an array of services to
support its customers' products. Vision has decided to implement Oracle User Management to
have a flexible and scalable system for managing access privileges and user accounts.
The company wants to distribute some of its security and administrative tasks to local
administrators instead of having the system administrator retain them exclusively. To accomplish
this, the company will create roles for a partner administrator, a security administrator, and a
customer administrator. Individuals who are assigned these roles will manage a discrete subset
of the company’s users, roles, and external contacts.
The company has created the Customer Administrator Role (referred to here as Course
Administrator), defined its delegated administration (data security policies) and assigned it, the
appropriate permission sets as well as the User Maintenance UIs. The company now wants to
define a registration process for this role so users can make a self service request.
As part of the implementation team, you need to perform the following tasks:
• Grant the appropriate permissions for the role so that assignees can perform specific
actions on the users they manage
• Create a registration process for the role so users can make a self service request
Tasks
Creating a Registration Process for Your Course Administrator Role
1. Login: YourInitialsUser
Note: the Registration Process Code, Display Name, and Description fields should be
populated automatically based on the selected role.
5. When you choose to create a registration process for existing users, you can specify a
specific group of users for whom the registration process is available. For the purposes of
this course, select “All Users” from Eligible Users radio list instead of choosing a specific
group of users. Then click (B) Submit.
You should see a confirmation message populated indicating the registration process has
been successfully created.
Business Scenario:
Vision Inc. is a computer systems company. The company offers its customers a full range of
computer systems and office equipment. Additionally, the company offers an array of services to
support its customers' products. Vision has decided to implement Oracle User Management to
have a flexible and scalable system for managing access privileges and user accounts.
The company wants to distribute some of its security and administrative tasks to local
administrators instead of having the system administrator retain them exclusively. To accomplish
this, the company will create roles for a partner administrator, a security administrator, and a
customer administrator. Individuals who are assigned these roles will manage a discrete subset
of the company’s users, roles, and external contacts.
As part of the implementation team, you need to perform the following tasks:
• Grant the appropriate permissions for the role so that assignees can perform specific
actions on the users they manage
• Create a registration process for the role so that users can self service request it
Tasks
Testing the Registration Process for Your Course Administrator Role
Please use the following email addresses to locate the user accounts assigned to your
workstation. Without this exclusivity, students will collide during the exercise.
1. (N) Users
2. Perform a search for “<your assigned email>” in the Email field and click (B) Go.
7. Click the Preferences link at the top of the page, click Access Requests link (see example
below):
9. Select the System Administration category, select “YourInitials Course Administrator” role,
click (B) Add to List (which is in the “Selected Roles” list in the right-hand panel) and then
click (B) Next.
10. Enter a justification for requesting this role, click (B) Next.
12. “YourInitials Course Administrator” role and the User Management responsibility should
both appear in the resulting window, because “YourInitials Course Administrator” role
inherits the User Management responsibility.
Tasks
Set your Personal Profile Options
1. Query the “Concurrent:Request Priority” profile value. Note its value, and try to update it.
2. Query the “Viewer: Default Font Size”. Set the value to 10 and Save it.
3. Query the “Printer”. Use the LOV to change or add a value and Save it.
4. Query the “Concurrent:Hold Requests”. Change the user value to “Yes” and Save it.
• Click the “Options…” button, and verify that the printer you selected for the Printer
profile option has defaulted in the Printer field.
6. Use the Find System Profile Values window to find “Currency:Negative Format” at the Site
level.
8. Use the Find System Profile Values window to find the “Flexfields:Shorthand Entry” profile
option at the Site and User level.
10. At which levels can the System Administrator change the values? _______________
4. Query up the profile option “Viewer: Default Font Size”. If there is no value specified, set it
to 10 and click Save.
5. Query up the profile option “Printer”. Use the List of Values to change or add a value. Click
Save.
6. Query up the option “Concurrent:Hold Requests”. Change the User Value to “Yes”. Click
Save.
• Click the “Options…” button and verify that the printer you selected for the “Printer”
profile option has defaulted in the Printer field.
• Take your request off hold by clicking the “Remove Hold” button.
11. What is the current setting of “Currency:Negative Format” for the Site? _______________
12. Use the Find System Profile Values window to find the “Flexfields:Shorthand Entry” profile
option at the Site and User level.
14. At which levels can the System Administrator change the values? _______________
• Run the Signon Audit reports to determine what concurrent programs were run
• Run the Signon Audit reports to determine what responsibilities and users have been
accessed
• Run the Signon Audit reports to see what forms have been accessed
Tasks
Run the Signon Audit Reports
1. Run the complete set of Signon Audit Reports using the time frame of the last week.
• Which responsibilities and users were accessed in the last week? _______________
Monitor Users
4. If you don’t see any users in your Monitor Users form, change the profile option “Sign-On
Audit Level” to “Form” at the user level. Then, sign on again to your user and recheck the
Monitor Users form.
3. Click the List of Values icon to get a list of all reports available for you to run.
• From Request Start Time: one week ago (use the format DD-MMM-YY)
• From Request Start Time: one week ago (use the format DD-MMM-YY)
• From Request Start Time: one week ago (use the format DD-MMM-YY)
• Which responsibilities and users were accessed in the last week? _______________
Monitor Users
21. Find the “Sign-On Audit Level” profile option at the user level for your specific signon.
Change it to “FORM” or “NONE”
(Note: Change the setting. This will enable you to note the differences.)
This demonstration illustrates the use of the Support Cart in Oracle Applications Manager, using
the Hosts page as an example. Other pages can be used also.
1. (N) Oracle Applications Manager > Site Map > Administration > Hosts (under System
Configuration).
2. Add the page to the Support Cart using the Add to Support Cart button at the bottom of the
page. Provide a description for the saved page. Click OK twice on the page that is returned.
3. Navigate to the Support Cart using the Support Cart global button or link.
4. For the Description tab, add information for the Service Request (SR) # (XXXXXXX.XXX)
and a description. Click Update.
5. Navigate to the Applications Signature tab. Select “Product Information” in the Generic
region and select the Delete button. Click Collect.
6. (Optional) Navigate to the Other Information Collected tab. You should see the page
"oam/node/nodeList" listed. Click the icon in the View column to review the Hosts page.
7. Save the page using the Save Cart button on the bottom of the page. Click Save, and then
give your zip file a suitable name as you save it to a local drive.
8. Navigate to the Other Information Collected tab. Select the "oam/node/nodeList" page and
click Delete to delete the page. The Hosts page will be deleted from the table.
10. From the Restore Cart Contents page, use the Browse… button to find and select your
previously-saved zip file. Click Restore.
11. The Hosts page is now back in the Support Cart. Note that “Product Information” is not
included because you deleted it in an earlier step.
Tasks
Submit a Request to Run Once
1. Submit the “Active Responsibilities and Users” report to run once, immediately.
2. Submit the “Active Users” report to run at two-minute intervals from the completion of the
prior run.
3. Submit the “Reports and Sets by Responsibility” report to run one week from today.
Submit a Request to Run Every Day at 2pm for just One Week
4. Submit the “Work Shifts Report” to run every day at 2pm for the next one week.
5. After you have submitted all of your concurrent requests, examine the status of your
requests.
1. Log in to Oracle Applications using the username you created earlier in the class and select
the System Administrator responsibility.
4. Select “Active Responsibilities and Users” report from the list of values for the Name field.
Your form should look similar to the following.
7. Select “Active Users” report from the list of values for the Name field.
• Select the Periodically radio button from the “Run the Job…” option group.
• In the “Re-run every” fields, enter 2 and select Minute(s) from the list of values.
• Select the “From the Completion of the prior run” radio button from the “Apply the
Interval…” option group. Your Schedule screen should appear similar to the following.
10. Select “Reports and Sets by Responsibility” report from the list of values for the Name field.
• Select the Once radio button from the “Run the Job…” option group.
• In the Run At field change the date to one week from today by using the popup calendar
or by typing in the date.
14. Select “Work Shifts Report” from the list of values for the Name field.
• Select the Periodically radio button from the “Run the Job…” option group.
• 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.
• 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.
18. Click (B) Find to view all your requests. Your form should look similar to the following.
19. Use the appropriate buttons on this form to perform each of the tasks.
• Find the “Active Responsibilities” request. The Phase should be Completed and the
Status should be Normal.
• Select a report with Phase Completed and Status Normal (for example, the Active
Responsibilities report). Click (B) Diagnostics. The Request Diagnostics window will
appear. Review the entries and click (B) OK to close the window.
• Select a report with Phase Completed and Status Normal (for example, the Active Users
report). Click (B) View Log…. The log file will appear in a separate browser window.
Review the entries for the log and close the browser window.
• Select a report with Phase Completed and Status Normal (for example, the Active Users
report). Click (B) View Output. The report will appear in a separate browser window.
Review the report and close the browser window.
Additional Tasks
• A Decision window will warn you: “Cancelling a request cannot be undone. Continue?”
• The Phase will be updated to Completed and the Status will be set to Cancelled.
• Click (B) Hold Request. The Phase of the request will be updated to Inactive and the
Status will be set to On Hold.
• Select one of the “Active Users” requests that completed with a normal status.
• You will get a confirmation page indicating that your request for reprinting existing
output has been scheduled along with the Request ID information. Click (B) OK and
Close window.
• Limit the Request Groups access to concurrent reports, programs, and sets
• Assign the new Request Group to your YourInitials Assistant System Administrator
(e.g., JSCS Assistant System Administrator) responsibility
Tasks
Create your Request Group
1. Create a new Request Group. Remember to put your initials at the front of your data entries
to keep your data unique.
• Requests:
1. Log in to Oracle Applications using your username you created earlier in the class and select
the System Administrator responsibility.
• Requests:
4. Save your work. Your work should look similar to the following.
7. Query to find your YourInitials Assistant System Administrator responsibility. Choose your
request group from the list of values for the Request Group Name field.
9. Exit and sign on again as your YourInitials Assistant System Administrator (e.g.,
JSCS_ASST_SYSADMIN)
12. Note the reports that now exist in the list of available reports for you to run.
Tasks
Create your Coded Request Group
1. Create a new Coded Request Group. Remember to put your initials at the front of your data
entries to keep your data unique.
• Requests:
2. Create a new Form Function. Remember to put your initials at the front of your data entries
to keep your data unique. Accept default values unless otherwise specified.
Description tab:
− Function: YourInitials_FNDRSRUN_JOURNAL_ENTRIES
− User Function Name: YourInitials Journal Entries
− Description: Journal Entries
Form tab:
− Form: Run Reports
− Application: Application Object Library
− Parameters:
− Enter the following three parameters in the Parameter field and each of them
should be separated by a space
TITLE = “YourInitials Journal Entries”
REQUEST_GROUP_CODE = “YourInitialsJE”
REQUEST_GROUP_APPL_SHORT_NAME = “<your application short
name>”
1. Log in to Oracle Applications with the username that you created earlier in the class and
select the System Administrator responsibility.
• Requests:
4. Save your work. Your work should look similar to the following.
• Description tab:
− Function: YourInitials_FNDRSRUN_JOURNAL_ENTRIES
− User Function Name: YourInitials Journal Entries
− Description: Journal Entries
• Properties tab:
− Type: Form
• Form tab:
− Form: Run Reports
− Parameters: Enter the following three parameters in the Parameter field and
each of them should be separated by a space:
TITLE = “YourInitials Journal Entries”
REQUEST_GROUP_CODE = “YourInitialsJE”
REQUEST_GROUP_APPL_SHORT_NAME = “<your application short
name>”
8. Save your work. Your work should look similar to the following.
15. Exit Oracle Applications and the Personal Homepage. Sign on again as the System Auditor
(i.e., YourInitials_SYSTEM_AUDITOR) to see your new function on the menu. Your
request group Journal Entries Report will appear on the Navigator for this responsibility.
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 because it is the
only request on the list.
Tasks
Create your Request Set Using Wizard
1. Create a new Request Set using the Wizard. Remember to put your initials at the front of
your data entries to keep your data unique.
3. Include the following programs in your request set: Users of a Responsibility, Reports and
Sets by Responsibility, and Report Group Responsibilities.
Note: The Shared Parameter label simply enables you to set an initial default value for all
occurrences of the same parameter so you can avoid typing the same value for every
occurrence.
3. Click (B) Request Set Wizard (DO NOT enter any other information – the Wizard will
prompt you for necessary information).
• Abort your set when the status of the stage ends in Error.
• Users of a Responsibility
12. Verify the Owner field has the user name of the user you are currently logged in as.
Review each request within the request set to identify which programs could share parameters.
Notice that Application Name and Responsibility name are parameters used in multiple requests.
• Click (B) Parameters, create the shared parameter values by typing them into the
Shared Parameter field.
Note: this time select the Parameter from the List of Values
26. Click the list of values icon for the Request Set field and select YourInitials Assistant
System Administrator.
27. Supply the required parameters by clicking in the Parameters field for each request. Verify
the Shared Parameters are being shared properly.
Tasks
Define your Work Shifts
1. Create a new Work Shift. Remember to put your initials at the front of your data entries to
keep your data unique.
• From: 08:00
• To: 17:00
• From: Monday
• To: Friday
2. Create a new Concurrent Manager. Remember to put your initials at the front of your data
entries to keep your data unique.
• Enabled: (Checked)
• Cache Size: 1
3. Use the following information to assign your work shift to your concurrent manager.
4. Use the information below to define your specialization rules for your Concurrent Manager.
5. 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.
6. In the Administer Concurrent Managers window, scroll through the list of managers until
you find the manager you defined.
10. Go to the View Requests window to verify that your request to activate your manager
completes successfully.
12. Go to the Administer Concurrent Managers window. Your concurrent manager will show
one request pending.
13. Click on the “Requests” button to view your request in the Concurrent Requests screen.
14. Return to the Administer Concurrent Managers window and click on the “Processes” button
to view the Processes window.
3. From the menu, select File > New, or click the New icon on the toolbar.
• From: 08:00
• To: 17:00
• From: Monday
• To: Friday
5. Save your work. The window should appear similar to the example shown.
• Enabled: (Checked)
• Cache Size: 1
8. Save your work. The window should appear similar to the example shown.
10. Save your work. The window should appear similar to the example shown.
13. Save your work. The window should appear similar to the example shown.
14. Close the Specialization Rules window to return to the Concurrent Managers window.
15. From the Concurrent Managers window, query up the Standard Manager.
19. Navigate to the Administer Concurrent Managers window: (N) Concurrent > Manager >
Administer.
20. In the Administer Concurrent Managers window scroll through the list of managers until
you find the manager you defined. Select your manager and click (B) Activate.
21. The status will update to Activating. The window will appear similar to the example shown.
22. Go to the View Requests window (N) Requests > View to verify that your request to
activate your manager completes successfully.
25. In the Submit Request window choose the “Active Users” or “Active Responsibilities and
Users” report.
• Choose Periodically.
• Leave the “Start At” time as the current time and enter five minutes from now for the
“End At” time.
• In the “Re-run every” field select 1 and Minute(s) to run the report once a minute for the
next five minutes.
28. Go to the Administer Concurrent Managers window (N) Concurrent > Manager >
Administer. Your concurrent manager may show one request pending.
Note: You may have to close and reopen the Administer Concurrent Managers window until
you “catch” your process running.
29. Click (B) Requests to view your request in the Concurrent Requests screen. Your form will
look similar to the following.
30. Close this window to return to the Administer Concurrent Managers window.
2. From the File menu, select Open to open the sample solution file named wfvacXX_062.wft
from the file system.
4. Save the workflow definition to the class database using File > Save As. Then close the data
store.
6. Click the Developer Studio link. In the Search region of the Developer Studio page, enter
the name of the XX Vacation Proposal workflow item type and click Go. Then, in the
Results region, click the Run icon for the XX Vacation Proposal item type.
7. Enter a process owner, item key, user key, requestor, approver, from date, and to date. The
requestor and approver should have Workflow administrator and user responsibilities
assigned to them.
9. Select the Status Monitor tab to review the process status in the Status Monitor Web pages.
• In the Search region, enter the XX Vacation Proposal item type and the item key you
chose, and click Go.
• In the Results region, select your process and click the Activity History button to review
the process activities.
• Click the Status Diagram button to review the graphical diagram of the status of the
process.
10. Log off and log in again as the approver. You can use either a Workflow administrator
responsibility or Workflow user responsibility.
12. In the Worklist, select the subject line for the Vacation Proposal notification sent by your
process to open the notification message.
15. Open the Workflow Builder again and make a change to the process diagram, such as
adding a function activity by dragging and dropping the Noop function from the Standard
item type into the process. Then save the definition to the class database again.
16. Repeat steps 5 through 9 to show the new version of the workflow definition in use.
Team: 01
− Descriptive Flexfield Title: Accounting Calendar: Periods
− Navigation Path: Setup > Financials > Calendars > Accounting (Periods region)
Team: 02
− Descriptive Flexfield Title: AutoPost Criteria
− Navigation Path: Setup > Journal > AutoPost
Team: 03
− Descriptive Flexfield Title: Budgetary Control Group: Rules
− Navigation Path: Budgets > Define > Controls (Budgetary Control Rules region)
Team: 04
− Descriptive Flexfield Title: Conversion Rate Types
− Navigation Path: Setup > Currencies > Rates > Types
Team: 05
− Descriptive Flexfield Title: Define Budget Organization: Organization
− Navigation Path: Budgets > Define > Organization
Team: 06
− Descriptive Flexfield Title: Define Recurring Journal: Batch
− Navigation Path: Journals > Define > Recurring
Team: 07
− Descriptive Flexfield Title: Journal Categories
− Navigation Path: Setup > Journal > Categories
Team: 08
− Descriptive Flexfield Title: Journal Sources
− Navigation Path: Setup > Journal > Sources
Team: 09
− Descriptive Flexfield Title: Open and Close Periods
− Navigation Path: Setup > Open/Close
Team: 11
− Descriptive Flexfield Title: Period Types
− Navigation Path: Setup > Financials > Calendars > Types
Team: 12
− Descriptive Flexfield Title: Summary Accounts
− Navigation Path: Setup > Accounts > Summary
Team: 13
− Descriptive Flexfield Title: Suspense Accounts
− Navigation Path: Setup > Accounts > Suspense
Team: 14
− Descriptive Flexfield Title: AutoReversal Criteria Set
− Navigation: Setup > Journal > AutoReverse [select a Journal category]
Team: 15
− Descriptive Flexfield Title: Budget Control Group: Group
− Navigation: Budgets > Define > Controls (main region)
Team: 16
− Descriptive Flexfield Title: Define Recurring Journal: Formula
− Navigation: Journals > Define > Recurring > Lines (B) (Formula region)
Team: 17
− Descriptive Flexfield Title: Define Recurring Journal: Journal Entry
− Navigation: Journals > Define > Recurring (Journal Entry region)
Team: 18
− Descriptive Flexfield Title: Define Recurring Journal: Line
− Navigation: Journals > Define > Recurring > Lines (B) (Line Description region)
Team: 19
− Descriptive Flexfield Title: Journal Authorization Limits
− Navigation: Setup > Employees > Limits
Team: 20
− Descriptive Flexfield Title: Mass Maintenance Requests
− Navigation: Setup > Other > Mass Maintenance
Descriptive flexfields use two types of segments: global and context-sensitive. In this practice,
you will create a descriptive flexfield using only global segments. You will also create value sets
that provide lists of values for your user. The descriptive flexfield is designed to track the
following additional information about orders that have been held:
Tasks
Define your Value Sets
• Define an independent value set named YourInitials_WHO_HELD. Give the value set a
description, a format type of Char, and a maximum size of 2. Enable Non-Hierarchical
Security for the value set.
• Define an independent value set named YourInitials_WHY_HELD. Give the value set a
description, a format type of Char, and a maximum size of 3. Enable Non-Hierarchical
Security for the value set.
2. After defining your value sets, use the Descriptive Flexfield Segments window to define the
structure for the descriptive flexfield assigned to you. Do not allow overrides for the context.
Define three segments for the Global Data Elements context.
• Define a segment named Who Held, with a prompt of Who. Assign the segment the
number 10, the column ATTRIBUTE1, and the value set YourInitials_WHO_HELD.
• Define a segment named Why Held, with a prompt of Why. Assign the segment the
number 20, the column ATTRIBUTE2, and the value set YourInitials_WHY_HELD.
• Define a segment named How Long, with a prompt of Length. Assign the segment the
number 30, the column ATTRIBUTE3, and the value set
YourInitials_HOW_LONG_HELD.
3. After defining the value sets and segments for your flexfield, use the Segment Values
window to define the values associated with each of the independent value sets.
4. Define and enable the following values for the YourInitials_WHO_HELD value set.
Value Description
01 Helen Myers
02 Mien Chan
03 Michael Keller
04 Luis Galvez
5. Define and enable the following values for the YourInitials_WHY_HELD value set.
Value Description
FIR Further information required
MAR Manager authorization required
AJR Additional justification required
6. Define and enable the following values for the YourInitials_HOW_LONG_HELD value set.
Value Description
100 Less than one week
200 One week to one month
300 One month to one year
400 More than one year
7. After defining your value sets, segments, and values, navigate to your descriptive flexfield
and test the results of your work. When you are finished, exit without saving.
2. Enter the information for the first value set in the following fields:
• Maximum Size: 2
4. Enter the information for the second value set in the following fields:
• Maximum Size: 3
6. Enter the information for the third value set in the following fields:
• Maximum Size: 3
10. In the Context Field region, ensure the Displayed check box is cleared.
11. In the Context Field Values region, select the Global Data Elements context and click (B)
Segments to navigate to the Segments Summary window.
12. Enter the following information for the three new segments:
Note: Be sure to save after each segment, you may need to click (B) OK to acknowledge the
Caution message before proceeding.
Window
Number Name Column Value Set Displayed Enabled
Prompt
10 Who Held Who ATTRIBUTE1 YourInitials_WHO_HELD Checked Checked
20 Why Held Why ATTRIBUTE2 YourInitials_WHY_HELD Checked Checked
30 How Long Length ATTRIBUTE3 YourInitials_HOW_LONG_HELD Checked Checked
14. Close the Segments Summary window to navigate back to the Descriptive Flexfield
Segments window.
16. Click (B) Compile to compile the flexfield definition. Click (B) OK to each note about
submitting your request to generate the flexfield view.
18. In the Find window, select YourInitials_WHO_HELD value set and click (B) Find.
19. In the Values, Effective region of the Segment Values window, define the following values:
21. In the Segment Values window, verify Value Set radio button is selected and your cursor is
in the header region, then query the YourInitials_WHY_HELD value set in the Name field.
24. In the Segment Values window, verify Value Set radio button is selected and your cursor is
in the header region, then query the YourInitials_HOW_LONG_HELD value set.
26. Save your work and close the Segment Values window.
27. After defining your value sets, segments, and values, navigate to your descriptive flexfield
using the General Ledger Super User responsibility and test the results of your work. When
you are finished, exit without saving.
This practice reinforces the concept of global segments for a descriptive flexfield and
demonstrates the use of the None validation type. In this scenario, you will define a descriptive
flexfield to track the following information about employees:
• Height
• Weight
Tasks
Define your Value Sets
1. Use the Value Sets window to define three value sets as follows:
• Define an independent value set named YourInitials_WHO_REFER. Give the value set a
description, a format type of Char, and a maximum size of 3. Enable Non-Hierarchical
Security for the value set.
• Define a value set of validation type None named YourInitials_EMP_HEIGHT. Give the
value set a description, a format type of Number, a maximum size of 4, and a precision
of 2.
2. After defining your value sets, use the Descriptive Flexfield Segments window to define the
structure for your descriptive flexfield. For the purposes of this practice, use the same
descriptive flexfield you worked on previously to enter your new structure. Unfreeze the
flexfield definition first in order to make changes to the structure.
3. Delete the segments that you defined previously, and define three new segments for the
Global Data Elements context.
• Define a segment named Height, with a prompt of Height. Assign the segment the
number 20, the column ATTRIBUTE2, and the value set YourInitials_EMP_HEIGHT.
• Define a segment named Weight, with a prompt of Weight. Assign the segment the
number 30, the column ATTRIBUTE3, and the value set YourInitials_EMP_WEIGHT.
• Ensure all three segments are displayed and enabled. When you finish defining the
structure, freeze and compile your flexfield definition.
4. After defining the value sets and segments for your flexfield, use the Segment Values
window to define the values associated with the independent value set.
5. Define and enable the following values for the YourInitials_WHO_REFER value set.
Value Description
100 President
200 Executive Vice President
300 Senior Vice President
6. After defining your value sets, segments, and values, navigate to your descriptive flexfield
and test the results of your work. When you are finished, exit without saving.
2. Enter the information for the first value set in the following fields:
• Maximum Size: 3
4. Enter the information for the second value set in the following fields:
• Maximum Size: 4
• Precision: 2
Note: You cannot enable security for a value set of validation type None.
6. Enter the information for the third value set in the following fields:
• Maximum Size: 3
• Precision: 0
• Min Value: 90
10. Clear the Freeze Flexfield Definition check box and click (B) OK to acknowledge caution.
11. In the Context Field Values region, select the Global Data Elements context and click (B)
Segments to navigate to the Segments Summary window.
14. Enter the following information for the three new segments.
Note: Be sure to save after each segment, you may need to click (B) OK to acknowledge the
Caution message before proceeding.
Window
Number Name Column Value Set Displayed Enabled
Prompt
10 Who Referred Who ATTRIBUTE1 YourInitials_WHO_REFER Checked Checked
20 Height Height ATTRIBUTE2 YourInitials_EMP_HEIGHT Checked Checked
30 Weight Weight ATTRIBUTE3 YourInitials_EMP_WEIGHT Checked Checked
16. Close the Segments Summary window to navigate back to the Descriptive Flexfield
Segments window.
17. Select the Freeze Flexfield Definition check box. Click (B) OK to acknowledge Caution.
20. In the Find window, select YourInitials_WHO_REFER value set and click (B) Find.
21. In the Values, Effective region of the Segment Values window, define the following values:
22. Save your work and close the Segment Values window. Click (B) OK to acknowledge
message.
23. After defining your value sets, segments, and values, navigate to your descriptive flexfield
using the General Ledger Super User responsibility and test the results of your work. When
you are finished, exit without saving.
In this practice, you will set up a context-sensitive segment and create a table-validated value set.
By using context sensitivity, you increase the number of questions you can ask without
increasing the number of columns necessary in the table. In this scenario, you will track
additional information for a transaction based on whether or not the transaction is a project. If it
is not a project, then you do not need to capture additional information. If it is a project, then the
flexfield should track the salesperson, the salesperson’s region, and the project name. To avoid
some repetitive data entry, you will use a table that already exists within Oracle Applications to
validate the project name.
Tasks
Define your Value Sets
• Define an independent value set named YourInitials_SALES_REP. Give the value set a
description, a format type of Char, and a maximum size of 3. Specify that the values
must be uppercase only, and enable non-hierarchical security for the value set.
• Define an independent value set named YourInitials_LOCATION. Give the value set a
description, a format type of Char, and a maximum size of 3. Specify that the values
must be uppercase only, and enable non-hierarchical security for the value set.
• Define a table-validated value set named YourInitials_PROJECT. Give the value set a
description, a format type of Char, and a maximum size of 30. Enable security for the
value set. Specify ARBV_CUSTOMERS in the Oracle Receivables application as the
validation table. Assign the Value column the column name CUSTOMER_NUMBER, a
type of VarChar2, and a size of 30. Assign the Meaning column the column name
CUSTOMER_NAME, a type of VarChar2, and a size of 50.
2. After defining your value sets, use the Descriptive Flexfield Segments window to define the
structure for your descriptive flexfield. For the purposes of this practice, use the same
3. For the context field, enter the prompt “Is this a project?” Specify that a value is required
and context override is allowed.
4. Delete the segments you defined previously for the Global Data Elements context.
5. Define and enable a new context named Yes with the code Yes. Define three new segments
for the Yes context.
• Define a segment named Sales Rep, with a prompt of Sales Rep. Assign the segment the
number 10, the column ATTRIBUTE1, and the value set YourInitials_SALES_REP.
• Define a segment named Location, with a prompt of Location. Assign the segment the
number 20, the column ATTRIBUTE2, and the value set YourInitials_LOCATION.
• Define a segment named Project, with a prompt of Project. Assign the segment the
number 30, the column ATTRIBUTE3, and the value set YourInitials_PROJECT.
6. Define and enable another new context named No with the code No.
7. When you finish defining the structure, freeze and compile your flexfield definition.
8. After defining the value sets and segments for your flexfield, use the Segment Values
window to define the values associated with each of the independent value sets.
9. Define and enable the following values for the YourInitials_SALES_REP value set.
Value Description
CLJ Charles L. Jefferson
AMR Ana M. Rodriguez
PAL Philippe A. Lebeau
10. Define and enable the following values for the YourInitials_LOCATION value set.
Value Description
NYC New York
MAD Madrid
PAR Paris
11. After defining your value sets, segments, and values, navigate to your descriptive flexfield
using the General Ledger Super User responsibility and test the results of your work. When
you are finished, exit without saving.
2. Enter the information for the first value set in the following fields:
• Maximum Size: 3
4. Enter the information for the second value set in the following fields:
• Maximum Size: 3
6. Enter the information for the third value set in the following fields:
• Maximum Size: 30
7. Click (B) Edit Information to navigate to the Validation Table Information window.
8. Enter Receivables as the table application and ARBV_CUSTOMERS as the table name.
Note: ARBV_CUSTOMERS will not appear in the list of values because it has not been
registered as a table, but you can still use it for validation purposes.
10. Save your work and close the Value Set window.
12. Query your descriptive flexfield in the Descriptive Flexfield Segments window.
13. Clear the Freeze Flexfield Definition check box, click (B) OK to acknowledge Caution
message.
14. In the Context Field region, enter information in the following fields:
• Required: Selected
• Displayed: Selected
15. In the Context Field Values region, select the Global Data Elements context and click (B)
Segments to navigate to the Segments Summary window.
18. Close the Segment Summary window to navigate back to the Descriptive Flexfield
Segments window.
19. In the Context Field Values region, enter the following information for the first context:
Note: Be sure to save after each segment, you may need to click (B) OK to acknowledge the
Caution message before proceeding.
Window
Number Name Column Value Set Displayed Enabled
Prompt
10 Sales Rep Sales Rep ATTRIBUTE1 YourInitials_SALES_REP Checked Checked
20 Location Location ATTRIBUTE2 YourInitials_LOCATION Checked Checked
30 Project Project ATTRIBUTE3 YourInitials_PROJECT Checked Checked
23. Close the Segments Summary window to navigate back to the Descriptive Flexfield
Segments window.
24. In the Context Field Values region, enter the following information for the second context:
26. Select the Freeze Flexfield Definition check box. Click (B) OK to acknowledge Caution
message.
27. Click (B) Compile to compile the flexfield definition. Click (B) OK to each note about
submitting your request to generate the flexfield view.
29. In the Find window, select YourInitials_SALES_REP value set and click (B) Find.
32. In the Segment Values window, verify Value Set radio button is selected and your cursor is
in the header region, then query the YourInitials_LOCATION value set in the Name field
34. Save your work and close the Segment Values window.
35. After defining your value sets, segments, and values, navigate to your descriptive flexfield
using the General Ledger Super User responsibility and test the results of your work. When
you are finished, exit without saving.
In this practice, you will create a dependent value set to validate a descriptive flexfield segment.
The descriptive flexfield will track the country and region for a salesperson. The list of values for
the region segment will change depending on the country selected.
Remember, when defining a dependent value set, you must perform the steps in the following
order:
Tasks
Define your Value Sets
• Define an independent value set named YourInitials_COUNTRY. Give the value set a
description, a format type of Char, and a maximum size of 3. Specify that the values
must be uppercase only, and enable Non-Hierarchical Security and Longlist for the value
set.
• Define a dependent value set named YourInitials_REGION. Give the value set a
description, a format type of Char, and a maximum size of 3. Specify that the values
must be uppercase only, and enable Non-Hierarchical Security for the value set.
Associate the dependent value set with the independent value set
YourInitials_COUNTRY. Assign the dependent value set a dependent default value of
YourInitials, and give the default value a description.
2. After defining your value sets, use the Descriptive Flexfield Segments window to define the
structure for your descriptive flexfield. For the purposes of this practice, use the same
descriptive flexfield you worked on previously to enter your new structure. Unfreeze the
flexfield definition first in order to make changes to the structure.
3. Define two new segments for the Global Data Elements context.
• Define a segment named Country Code, with a prompt of Country. Assign the segment
the number 10, the column ATTRIBUTE4, and the value set YourInitials_COUNTRY.
• Define a segment named Region Code, with a prompt of Region. Assign the segment the
number 20, the column ATTRIBUTE5, and the value set YourInitials_REGION.
• Ensure both segments are displayed and enabled. When you finish defining the structure,
freeze and compile your flexfield definition.
4. After defining the value sets and segments for your flexfield, use the Segment Values
window to define the values associated with the independent and dependent value sets.
5. Define and enable the following values for the YourInitials_COUNTRY value set.
Value Description
USA United States
CAN Canada
UK United Kingdom
6. Define and enable the following values in the YourInitials_REGION value set for the
independent value USA.
Value Description
OK Oklahoma
TX Texas
WI Wisconsin
7. Define and enable the following values in the YourInitials_REGION value set for the
independent value CAN.
Value Description
SAS Saskatchewan
BC British Columbia
8. Define and enable the following values in the YourInitials_REGION value set for the
independent value UK.
Value Description
WA Wales
SL Scotland
EN England
9. After defining your value sets, segments, and values, navigate to your descriptive flexfield
and test the results of your work. When you are finished, exit without saving.
2. Enter the information for the first value set in the following fields:
• Maximum Size: 3
4. Enter the information for the second value set in the following fields:
• Maximum Size: 3
5. Click (B) Edit Information to navigate to the Dependent Value Set Information window.
6. In the Independent Value Set region, enter YourInitials_COUNTRY in the Name field.
Copyright © Oracle Corporation, 2008. All rights reserved.
10. Query your descriptive flexfield in the Descriptive Flexfield Segments window.
11. Clear the Freeze Flexfield Definition check box, click (B) OK to acknowledge Caution
message.
12. In the Context Field Values region, select the Global Data Elements context and click (B)
Segments to navigate to the Segments Summary window.
13. Enter the following information for the two new segments:
Note: Be sure to save after each segment, you may need to click (B) OK to acknowledge the
Caution message before proceeding.
Window
Number Name Column Value Set Displayed Enabled
Prompt
10 Country Code Country ATTRIBUTE4 YourInitials_COUNTRY Checked Checked
20 Region Code Region ATTRIBUTE5 YourInitials_REGION Checked Checked
15. Close the Segment Summary window to navigate back to the Descriptive Flexfield
Segments window.
16. Select the Freeze Flexfield Definition check box. Click (B) OK to acknowledge Caution
message.
17. Click (B) Compile to compile the flexfield definition. Click (B) OK to each note about
submitting your request to generate the flexfield view.
19. In the Find window, select YourInitials_COUNTRY value set and click (B) Find.
20. In the Values, Effective region of the Segment Values window, define the following values:
22. In the Segment Values window, verify Value Set radio button is selected and your cursor is
in the header region, query with YourInitials_REGION in the Dependent Value Set field
field.
23. Define and enable the following values for the Independent Value USA.
25. In the Segment Values window, verify Value Set radio button is selected and your cursor is
in the header region, use your down arrow to navigate to the Independent Value CAN.
26. Define and enable the following values for the Independent Value CAN.
28. In the Segment Values window, verify Value Set radio button is selected and your cursor is
in the header region, use your down arrow to navigate to the Independent Value UK.
29. Define and enable the following values for the Independent Value UK.
30. Save your work and close the Segment Values window.
31. After defining your value sets, segments, and values, navigate to your descriptive flexfield
using the General Ledger Super User responsibility and test the results of your work. When
you are finished, exit without saving.
Flexfield definitions can be created under many different responsibilities. However, the System
Administrator responsibility has access to all functions needed to create the definitions in these
practices. In this practice you will create a key flexfield structure and values for your chart of
accounts. The design of the structure has already been determined. The flexfield will have four
segments: a company segment, a cost center segment, an account segment, and a segment
labeled Future for possible future expansion, in that order. Before you define the structure, you
must first create the value sets, then create the structure, identifying the segments by their
respective flexfield qualifiers. Finally, you will create the valid values for each segment. After
creating the values, test your structure by performing the first steps in the process for creating a
new set of books.
Note: After saving your accounting flexfield structure, you may receive a message that the key
flexfield is not compiled. There is no need to take action. The flexfield will be compiled
automatically.
Tasks
Define your Value Sets
• Define an independent value set named YourInitials_CO. Give the value set a
description, a format type of Char, and a maximum size of 2. Enable Non-Hierarchical
Security for the value set. Specify that the values should be right-justified and zero-
filled.
• Define an independent value set named YourInitials_COST. Give the value set a
description, a format type of Char, and a maximum size of 3. Enable Non-Hierarchical
Security for the value set. Specify that the values should be right-justified and zero-
filled.
• Define an independent value set named YourInitials_ACCOUNT. Give the value set a
description, a format type of Char, and a maximum size of 4. Enable Non-Hierarchical
Security and Longlist for the value set. Specify that the values should be right-justified
and zero-filled.
2. After defining your value sets, use the Key Flexfield Segments window to define a new
flexfield structure for the Accounting Flexfield in the Oracle General Ledger application.
Give your structure the code YourInitials_COA, the title YourInitials Chart of Accounts, a
description, and the view name YourInitials_AFF_VIEW. Enable the structure. Use a period
(.) as the segment separator, specify segments should be cross-validated, and allow dynamic
inserts. Define four segments for your structure.
• Define a segment named CO, with a prompt of Company. Assign the segment the
number 1, the column SEGMENT1, and the value set YourInitials_CO. Ensure the
segment is displayed and enabled. Enable security for the segment. Give the segment a
display size of 2 and a description size of 30. Enable the Balancing Segment flexfield
qualifier for the segment.
• Define a segment named CC, with a prompt of Cost Center. Assign the segment the
number 2, the column SEGMENT2, and the value set YourInitials_COST. Ensure the
segment is displayed and enabled. Enable security for the segment. Give the segment a
display size of 3 and a description size of 30. Enable the Cost Center Segment flexfield
qualifier for the segment.
• Define a segment named ACCT, with a prompt of Account. Assign the segment the
number 3, the column SEGMENT3, and the value set YourInitials_ACCOUNT. Ensure
the segment is displayed and enabled. Enable security for the segment. Give the segment
a display size of 4 and a description size of 30. Enable the Natural Account Segment
flexfield qualifier for the segment.
• Define a segment named RFU, with a prompt of Future Use. Assign the segment the
number 4, the column SEGMENT4, and the value set YourInitials_FUTURE. Ensure the
segment is displayed and enabled. Specify a default type of Constant and a default value
of 0000. Enable security for the segment. Give the segment a display size of 4 and a
description size of 30.
• When you finish defining the structure, freeze and compile your flexfield definition.
3. After defining the value sets and segments for your flexfield, use the Segment Values
window to define the values associated with each of the independent value sets.
Value Description
01 Red Co.
02 Orange Co.
03 Yellow Co.
04 Green Co.
05 Blue Co.
5. Define and enable the following values for the YourInitials_COST value set.
Value Description
000 Not Specified
100 Sales
200 Services
300 Development
6. Define and enable the following values for the YourInitials_ACCOUNT value set. Specify
the account type segment qualifier for each value as shown.
7. Define and enable the following value for the YourInitials_FUTURE value set.
Value Description
0000 Not Specified
After defining your value sets, segments, and values, navigate to the Accounting Flexfield to test
the results of your work. To view the Accounting Flexfield, you will perform the beginning steps
in the process for creating your accounting structure and then view the accounting flexfield you
created earlier in this practice.
8. (N) Setup > Financials > Accounting Setup Manager > Accounting Setups.
10. Click Next to access the Create Accounting Setups: Define Accounting Representations
window.
14. In the Primary Ledger region, click the Update icon for Ledger Options.
15. Click Next to access the Update Ledger: Ledger Options window.
16. In the Year End Processing region, click the Search icon for the Retained Earnings Account
field to display the list of values. The Accounting Flexfield appears.
2. Enter the information for the first value set in the following fields:
• Maximum Size: 2
4. Enter the information for the second value set in the following fields:
• Maximum Size: 3
6. Enter the information for the third value set in the following fields:
• Maximum Size: 4
8. Enter the information for the fourth value set in the following fields:
• Maximum Size: 4
11. Query the application General Ledger and the flexfield title Accounting Flexfield.
12. In the Structures region, insert a new record and enter the information for the flexfield
structure in the following fields:
• Code: YourInitials_COA
14. Enter the information for the first segment in the following fields:
• Number: 1
• Name: CO
• Column: SEGMENT1
• Displayed: Selected
• Enabled: Selected
16. Enter the information for the first segment in the following fields:
• Display Size: 2
• Description Size: 30
18. Click (B) Flexfield Qualifiers to navigate to the Flexfield Qualifiers window.
19. Select the Enabled check box for the Balancing Segment flexfield qualifier.
22. Enter the information for the second segment in the following fields:
• Number: 2
• Column: SEGMENT2
• Displayed: Selected
• Enabled: Selected
24. Enter the information for the second segment in the following fields:
• Display Size: 3
• Description Size: 30
26. Click (B) Flexfield Qualifiers to navigate to the Flexfield Qualifiers window.
27. Select the Enabled check box for the Cost Center Segment flexfield qualifier.
30. Enter the information for the third segment in the following fields:
• Number: 3
• Name: ACCT
• Column: SEGMENT3
• Displayed: Selected
• Enabled: Selected
• Display Size: 4
• Description Size: 30
34. Click (B) Flexfield Qualifiers to navigate to the Flexfield Qualifiers window.
35. Select the Enabled check box for the Natural Account Segment flexfield qualifier.
38. Enter the information for the fourth segment in the following fields:
• Number: 4
• Name: RFU
• Column: SEGMENT4
• Displayed: Selected
• Enabled: Selected
40. Enter the information for the fourth segment in the following fields:
• Display Size: 4
• Description Size: 30
43. Select the Freeze Flexfield Definition check box. Click (B) OK to acknowledge Caution
message.
44. Click (B) Compile to compile the flexfield definition. You will find two notes indicating
that the flexfield was compiled successfully. Click (B) OK to each note about submitting
your request to generate the flexfield view.
46. In the Find window, select Value Set and find the YourInitials_CO value set. Click (B)
Find.
47. In the Values, Effective region of the Segment Values window, define the following values:
49. In the Segment Values window, verify Value Set radio button is selected and your cursor is
in the header region, then query the YourInitials_COST value set in the Name field.
52. In the Segment Values window, verify Value Set radio button is selected and your cursor is
in the header region, then query the YourInitials_ACCOUNT value set in the Name field.
Note: Click in the Qualifiers field in the Values, Hierarchy, Qualifiers region to display the
Segment Qualifiers window and enter a value in the Account Type field. Accept the default
values for the other fields in the Segment Qualifiers window.
55. In the Segment Values window, select Value Set and find the YourInitials_FUTURE value
set. Click (B) Find.
Value Description
0000 Not Specified
57. Save your work and close the Value window. Click (B) OK to the note about submitting
your request to compile 4 value set hierarchies.
After defining your value sets, segments, and values, navigate to the Accounting Flexfield to test
the results of your work. To view the Accounting Flexfield, you will perform the beginning steps
in the process for creating your accounting structure and then view the accounting flexfield you
created earlier in this practice.
58. (N) Setup > Financials > Accounting Setup Manager > Accounting Setups.
59. In the Accounting Setups window, click (B) Create Accounting Setup.
60. Click (B) Next to access the Create Accounting Setups: Define Accounting Representations
window.
62. Click (B) Next and (B) Finish to save your accounting structure.
64. In the Primary Ledger region, click the Update icon for Ledger Options.
65. Click (B) Next to access the Update Ledger: Ledger Options window.
66. In the Year End Processing region, click the Search icon for the Retained Earnings Account
field to display the list of values. The Accounting Flexfield appears.
Note: Before you can use security for a flexfield segment, you must enable security both at
the value set level and at the segment level.
Tasks
Define your Security Rule
1. Use the Define Security Rules window to define a security rule for the ACCT segment of
the Accounting Flexfield structure, YourInitials Chart of Accounts, that you defined in the
Define a Key Flexfield lesson. Name the rule YourInitials_SR01, and give the rule a
description. Enter an error message to explain the rule to users.
• Define the first security rule element to include all the possible account values, from
0000 to zzzz.
• Define the second security rule element to exclude the account 4110.
2. Use the Assign Security Rules window to assign your security rule to the General Ledger
Super User responsibility in the Oracle General Ledger application.
After defining your value sets, segments, and values, navigate to the Accounting Flexfield to test
the results of your work. To view the Accounting Flexfield, you will perform the beginning steps
in the process for creating your accounting structure and then view the accounting flexfield you
created earlier in this practice.
3. (N) Setup > Financials > Accounting Setup Manager > Accounting Setups.
6. In the Primary Ledger region, click the Update icon for Ledger Options.
8. In the Year End Processing region, click the Search icon for the Retained Earnings Account
field to display the list of values. The Accounting Flexfield appears.
2. In the Find window, select Key Flexfield and find the ACCT segment of the YourInitials
Chart of Accounts structure for the Accounting Flexfield in the General Ledger application.
3. In the Security Rules region of the Define Security Rules window, enter information in the
following fields:
• Name: YourInitials_SR01
4. In the Security Rule Elements region, enter following information Security Rule Elements:
Type From To
Include 0000 zzzz
Exclude 4110 4110
7. In the Security Rules region of the Assign Security Rules window, enter information in the
following fields:
• Name: YourInitials_SR01
After defining your value sets, segments, and values, navigate to the Accounting Flexfield to test
the results of your work. To view the Accounting Flexfield, you will perform the beginning steps
9. (N) Setup > Financials > Accounting Setup Manager > Accounting Setups.
10. In the Accounting Setups window, search by Ledger YourInitials_COA, click (B) Go.
12. In the Primary Ledger region, click the Update icon for Ledger Options.
13. Click (B) Next to access the Update Ledger: Ledger Options window.
14. In the Year End Processing region, click the Search icon for the Retained Earnings Account
field to display the list of values. The Accounting Flexfield appears.
Whenever you add or change cross-validation rules, you must recompile the flexfield structure to
ensure your changes are reflected in the applications.
Tasks
Define your Cross-Validation Rule
1. Use the Cross-Validation Rules window to define a cross-validation rule for the Accounting
Flexfield structure you defined in the Define a Key Flexfield lesson, YourInitials Chart of
Accounts. Name the rule YourInitials_CVR:01, give the rule a description, and ensure the
rule is enabled. Enter an error message to explain the rule to users, and specify the CO
segment as the error segment.
• Define the first cross-validation rule element to include all the possible code
combinations, from lowest to highest.
• Define the second cross-validation rule element to exclude any code combinations
containing both the Orange Company and the Development cost center.
• After defining the cross-validation rule, recompile the flexfield structure definition.
After defining your value sets, segments, and values, navigate to the Accounting Flexfield to test
the results of your work. To view the Accounting Flexfield, you will perform the beginning steps
in the process for creating your accounting structure and then view the accounting flexfield you
created earlier in this practice.
3. (N) Setup > Financials > Accounting Setup Manager > Accounting Setups.
8. In the Year End Processing region, click the Search icon for the Retained Earnings Account
field to display the list of values. The Accounting Flexfield appears.
2. Query the YourInitials Chart of Accounts structure for the Accounting Flexfield in the
General Ledger application.
3. In the Cross-Validation Rules region, enter the information for the rule in the following
fields:
• Name: YourInitials_CVR:01
• Enabled: Selected
• Error Segment: CO
Type From To
Include 00.000.0000.0000 zz.zzzz.zzzz.zzzz
Exclude 02.300.0000.0000 02.300.zzzz.zzzz
7. Query the YourInitials Chart of Accounts structure for the Accounting Flexfield in the
General Ledger application.
8. Click (B) Compile to compile the flexfield definition. You will find two notes indicating
that the flexfield was compiled successfully. Click (B) OK to each note about submitting
your request to generate the flexfield view.
After defining your value sets, segments, and values, navigate to the Accounting Flexfield to test
the results of your work. To view the Accounting Flexfield, you will perform the beginning steps
in the process for creating your accounting structure and then view the accounting flexfield you
created earlier in this practice.
9. (N) Setup > Financials > Accounting Setup Manager > Accounting Setups.
10. In the Accounting Setups window, search by Ledger YourInitials_COA, click (B) Go.
12. In the Primary Ledger region, click the Update icon for Ledger Options.
13. Click (B) Next to access the Update Ledger: Ledger Options window.
14. In the Year End Processing region, click the Search icon for the Retained Earnings Account
field to display the list of values. The Accounting Flexfield appears.
Tasks
Define your Shorthand Alias
1. Use the Shorthand Aliases window to define shorthand aliases for the Accounting Flexfield
structure, YourInitials Chart of Accounts that you defined in the Define a Key Flexfield
lesson. Enable aliases for this structure, a maximum size of 15, and a prompt of Shorthand.
2. Define an alias named YourInitials_SA_1, give the alias a description, and specify the
complete combination 03.100.1110.0000.
3. Define an alias named YourInitials_SA_2, give the alias a description, and specify the
partial combination 04...0000.
2. Query the YourInitials Chart of Accounts structure for the Accounting Flexfield in the
General Ledger application.
• Enabled: Selected
• Prompt: Shorthand
7. Query the YourInitials Chart of Accounts structure for the Accounting Flexfield in the
General Ledger application.
8. Click (B) Compile to compile the flexfield definition. Click (B) OK to each note about
submitting your request to generate the flexfield view.
Tasks
Define your Value Set
1. Use the Value Sets window to define a table-validated value set named
YourInitials_EMP_NUM. Give the value set a description, a format type of Char, and a
maximum size of 30. Enable Non-Hierarchical Security and Longlist for the value set.
Specify the table PER_ALL_PEOPLE_F in the Oracle Human Resources application as the
validation table. Assign the Value column the column name EMPLOYEE_NUMBER, a
type of Varchar2, and a size of 30. Assign the Meaning column the column name
FULL_NAME, a type of Varchar2, and a size of 240. Restrict the value set to include only
active employees by specifying the following Where/Order By clause:
2. After defining your value set, use the Descriptive Flexfield Segments window to define the
structure for your descriptive flexfield. For the purposes of this practice, use the same
descriptive flexfield you worked on previously to enter your new structure. Unfreeze the
flexfield definition first in order to make changes to the structure.
3. You can keep the two segments that you defined previously for the Global Data Elements
context. Now define a new segment for the Global Data Elements context. Name the
segment Employee Number, with a prompt of Employee Number. Assign the segment the
number 30, the column ATTRIBUTE6, and the value set YourInitials_EMP_NUM.
4. Ensure the new segment is displayed and enabled. When you finish defining the structure,
freeze and compile your flexfield definition.
5. After defining your value set and segment, navigate to your descriptive flexfield and test the
results of your work. When you are finished, exit without saving.
2. Enter the information for the value set in the following fields:
• Maximum Size: 30
3. Click (B) Edit Information to navigate to the Validation Table Information window.
4. Use the lists of values in the Table Application to select Human Resources as the table
application type PER_ALL_PEOPLE_F as the table name.
5. In the Table Columns region, use the lists of values in the following fields:
10. Query your descriptive flexfield in the Descriptive Flexfield Segments window.
12. In the Context Field Values region, select the Global Data Elements context and click (B)
Segments to navigate to the Segments Summary window.
14. Enter the information for the third segment in the following fields:
Window
Number Name Column Value Set Displayed Enabled
Prompt
Employee Employee
30 ATTRIBUTE6 YourInitials_EMP_NUM Checked Checked
Number Number
18. Click (B) Compile to compile the flexfield definition. Click (B) OK to each note about
submitting your request to generate the flexfield view.
19. After defining your value set and segment, navigate to your descriptive flexfield using the
General Ledger Super User responsibility and test the results of your work. When you are
finished, exit without saving.
To set up the cascading dependencies, you will create table-validated value sets using the
following tables:
CAR_MAKERS
CAR_MODELS
CAR_COLORS
Tasks
Define your Value Sets
• Define a table-validated value set named YourInitials_MFG. Give the value set a
description, a format type of Char, and a maximum size of 10. Enable non-hierarchical
security for the value set. Specify the table CAR_MAKERS as the validation table.
Assign the Value column the column name MANUFACTURER_NAME, a type of
Varchar2, and a size of 10. Assign the Meaning column the column name
MANUFACTURER_DESCRIPTION, a type of Varchar2, and a size of 30. Assign the
ID column the column name MANUFACTURER_ID, a type of Number, and a size of 2.
• Define a table-validated value set named YourInitials_MODEL. Give the value set a
description, a format type of Char, and a maximum size of 10. Enable non-hierarchical
security for the value set. Specify the table CAR_MODELS as the validation table.
• Define a table-validated value set named YourInitials_COLOR. Give the value set a
description, a format type of Char, and a maximum size of 10. Enable non-hierarchical
security for the value set. Specify the table CAR_COLORS as the validation table.
Assign the Value column the column name COLOR_NAME, a type of Varchar2, and a
size of 10. Assign the Meaning column the column name COLOR_DESCRIPTION, a
type of Varchar2, and a size of 30. Assign the ID column the column name COLOR_ID,
a type of Number, and a size of 4. Specify the following Where/Order By clause:
2. After defining your value sets, use the Descriptive Flexfield Segments window to define the
structure for your descriptive flexfield. For the purposes of this practice, use the same
descriptive flexfield that you worked on previously to enter your new structure. Unfreeze the
flexfield definition first so that you can change the structure.
3. Delete the segments that you defined previously for the Global Data Elements context. Then
define three new segments for the Global Data Elements context.
• Define a segment named Model, with a prompt of Model. Assign the segment the
number 20, the column ATTRIBUTE2, and the value set YourInitials_MODEL.
• Define a segment named Color, with a prompt of Color. Assign the segment the number
30, the column ATTRIBUTE3, and the value set YourInitials_COLOR.
• Ensure that all three segments are displayed and enabled. When you finish defining the
structure, freeze and compile your flexfield definition.
4. After defining your value sets and segments, navigate to your descriptive flexfield and test
the results of your work. When you are finished, exit without saving.
2. Enter the information for the first value set in the following fields:
• Maximum Size: 10
5. In the Table Columns region, enter the following information for the Value column:
7. Enter the information for the second value set in the following fields:
• Maximum Size: 10
10. In the Table Columns region, enter the following information for the Value column:
13. Enter the information for the third value set in the following fields:
• Maximum Size: 10
14. Click Edit Information to navigate to the Validation Table Information window.
16. In the Table Columns region, enter the following information for the Value column:
20. Query your descriptive flexfield in the Descriptive Flexfield Segments window.
22. Select the Global Data Elements context and click (B) Segments to navigate to the
Segments Summary window.
Window
Number Name Column Value Set Displayed Enabled
Prompt
10 Manufacturer Manufacturer ATTRIBUTE1 YourInitials_MFG Checked Checked
20 Model Model ATTRIBUTE2 YourInitials_MODEL Checked Checked
30 Color Color ATTRIBUTE3 YourInitials_COLOR Checked Checked
29. Click (B) Compile to compile the flexfield definition. Click (B) OK to each note about
submitting your request to generate the flexfield view.
30. After defining your value sets and segments, navigate to your descriptive flexfield using the
General Ledger Super User responsibility and test the results of your work. When you are
finished, exit without saving.
• Set the profile option to control modifications of the folder by the user
Tasks
1. Log on to Oracle Applications using the username you defined earlier, such as
YourInitialsUSER.
2. Select General Ledger Super User responsibility and navigate to (N) Journals > Enter.
3. The first window you see is the Find Journals window. Note that once you create your folder
and assign it to your user this window will not appear.
5. Click Find.
Note: you can view the query here, but you cannot change it. Click OK to close the
window.
11. In the Enter Journals window, the upper left corner next to the Folder icon is the name you
entered for your folder.
12. 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.
14. 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.
16. Choose “Category” from the Show Field window if the Category column has not been added
to the display in the Enter Journals window or select another value when needed and click
OK.
17. 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.
20. In the Find Folders screen, select “Default folder assignments by user” and choose your user
name from list of values.
• User: YourInitialsUser
27. Set the Profile Option to disallow modification by your user. In the System Profile Values
screen enter “No” as the User value for the profile option.
31. Notice that you see a Decision window that says “Find all records in this folder?” This
window displays because you chose “Ask each time” when you defined the folder.
33. Notice that the Journal Entries window opens with your folder displayed.
34. Click on the Folder Tools icon on the toolbar. Note that all the modification icons are
disabled (because you set the Folders: Allow Customization profile option to No).
35. Click on the Folder menu and notice that the only enabled option is Open.
Tasks
Create your Concurrent Program Definition
1. Given the executable program already created, you need to create a concurrent program to
contain it. Query up the Completed Concurrent Requests Report program in the Concurrent
Programs window and use the Copy to button to create your custom program.
2. Add your concurrent program to your existing YourInitials Assistant SysAdmin request
group. Once you have added it to this group, it will have already been assigned to the Your
Initials Assistant System Administrator responsibility and to the YourInitials_Assist_SA
user.
3. Sign-on as the YourInitials_Assist_SA user, and submit a concurrent request for your new
report.
If necessary, log in to Oracle Applications and select the System Administrator responsibility.
6. Save your work. Your completed form should appear similar to the example shown.
11. Insert a new record and the Program YourInitials Completed Concurrent Requests.
12. Save your work. Your completed form should appear similar to the example shown.