Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
• Auditing user activity. Monitor what users are doing and when they
do it. Choose who to audit and what type of data to audit.
You can think of Oracle Applications as having two sides: a front end that
users see and work with, and a back end where data manipulation is performed.
The natural division between user applications and the underlying database
structures results in two separate job functions: system administrator, and
database administrator.
TCS Confidential
Defining Application Users
You allow a new user to sign–on to Oracle Applications by defining an
application user. An application user has a username and a password. You define
an initial password, then the first time the application user signs on, they must
enter a new (secret) password.
When you define an application user, you assign to the user one or more
responsibilities. If you assign only one responsibility, the user, after signing on,
immediately enters an application. If you assign two or more responsibilities, the
user, after signing on, sees a window listing available responsibilities.
Responsibility
A responsibility is a level of authority in Oracle Applications that lets users
access only those Oracle Applications functions and data appropriate to their
roles in an organization. Each responsibility allows access to:
• A restricted list of windows that a user can navigate to; for example, a
responsibility may allow certain Oracle Planning users to enter forecast items,
but not enter master demand schedule items.
Each user has at least one or more responsibilities and several users can
share the same responsibility.
2
TCS Confidential
Defining a Responsibility
When you define a responsibility, you assign to it some or all of the
components described below:
3
TCS Confidential
Function
A function is a part of an application’s functionality that is registered under
a unique name for the purpose of assigning it to, or excluding it from, a
responsibility. There are two types of functions: form functions, and non–form
functions. For clarity, we refer to a form function as a form, and a non–form
function as a subfunction, even though both are just instances of functions in the
database.
4
TCS Confidential
Subfunction (Non–Form Function)
Menu
A menu is a hierarchical arrangement of functions and menus of functions.
Each responsibility has a menu assigned to it.
Menu Entry
5
TCS Confidential
6
TCS Confidential
Request Groups and Request Sets
• Request sets define run and print options, and possibly, parameter values,
for a collection of reports or concurrent program. End users and System
Administrators can define request sets. A System Administrator has request
set privileges beyond those of an end user.
• Users cannot use the Submit Requests form to run single requests and
request sets that are not in their responsibility’s request security group.
• Users can, however, run request sets that contain requests that are not in
their request security group, if the request set is in their request security
group.
If you assign a request set, but not the requests in the set, to a request
security group, the user:
The Request Security Groups figure on the next page illustrates the
relationship between a request security group, application user, and a
responsibility.
7
TCS Confidential
Data Group
A data group is a list of Oracle Applications and the Oracle username
assigned to each application. Each application in a data group must have a
unique Oracle username assigned to it. An application may be listed only once in
a data group.
8
TCS Confidential
Purpose of the Data Group
Each responsibility has a data group associated with it. A data group
serves two purposes:
1. It identifies the Oracle username that forms connect to when you select the
responsibility.
2. Concurrent managers use a data group to match the application that owns a
report or concurrent program (submitted by a user of the responsibility) with a
unique Oracle username.
User Profiles
A user profile is a set of changeable options that affect the way your
application looks and behaves. As System Administrator, you control how Oracle
Applications operate by setting user profile options to the values you want. You
can set user profile options at four different levels: site, application, responsibility,
and user.
9
TCS Confidential
Setting User Profile Options
As System Administrator, you use the System Profile Values window to set
profile options for your user community. If you change a user profile option value,
your change takes effect as soon as your users log on again or change
responsibilities.
When you set a user profile, you provide Oracle Applications with standard
information (such as printer) that describes a user, responsibility, application, or
site. You can set values for user profile options at each profile level.
The values you set at each level provide run–time values for each user’s
profile options. An option’s run–time value becomes the highest–level setting for
that option.
10
TCS Confidential
Concurrent Programs and Requests
A concurrent program is an executable file that runs simultaneously with
other concurrent programs and with online operations, fully utilizing your
hardware capacity. Typically, a concurrent program is a long–running, data–
intensive task, such as posting a journal or
generating a report.
• The reports and concurrent programs that may be selected from the Submit
Requests form belong to a request security group, which is a request group
assigned to a responsibility.
11
TCS Confidential
Request Sets as concurrent programs
When you define a request set, you create a concurrent program that runs
the reports in your request set according to the instructions you entered. All
concurrent programs that run request sets are titled Request Set <name of
request set>. In the Concurrent Programs form, if you query a request set
concurrent program on the basis of the program’s name, you must enter in the
Name field the words:
Request set editing and report viewing privileges are different for reports
that belong to a user’s request security group than they are for reports that are
not in the user’s request security group.
• can add any other reports in their request security group to the request set.
12
TCS Confidential
• can delete any report from the request set, regardless of whether that report
is in their request security group.
• can update print options or parameters for an individual report in the request
set, if the report is in their request security group.
• cannot view online reports in a request set if those reports are not included in
their request security group.
• cannot run an individual report by itself, but can only run the entire request
set.
• cannot cancel pending requests for the individual reports in the set if those
reports are not included in their request security group.
2. By leaving the Owner field blank, System Adminstrators can create request
sets whose individual programs and parameters cannot be edited or updated
by end users. Only a System Administrator can edit a request set that has no
owner.
You can share a parameter and its entered value among some or all of the
reports (or concurrent programs) in your request set. You identify a parameter as
shared by giving it a label. Then, for each concurrent program in your request
set, you can assign the same label to a parameter for that program. Among the
programs in your request set, the parameters for each program share or accept a
common value. The first time you enter a value for any of the shared parameters,
13
TCS Confidential
that value becomes the shared parameters value. This is useful, because you
only have to enter a value once, rather than for each program in the request set.
Responsibility level
Form level
14
TCS Confidential
Enforcing Incompatibility Rules
15
TCS Confidential
Using Data Groups for cross–application reporting
16
TCS Confidential
If you wish to define or modify a value set, you must first carefully plan your value
set’s purpose and implementation.
Using the Concurrent Programs form, you can see a concurrent program’s
parameters by choosing Parameters. Each parameter has a value set that
defines what values are permissible for the parameter. To see the name of a
parameter’s value set, look at the Value Set field in the Argument Details block.
17
TCS Confidential