Creating Accounts Receivables Responsibility | Oracle Apps R12
By Jag - October 14, 2014
Learn Step by Step ScreenShot Creating Accounts Receivables Responsibility on Oracle Apps R12,Responsibility Name,Application,HTML Based Applications
Responsibilities Window
Use this window to define a responsibility. Each application user is assigned at least one responsibility.
A responsibility determines whether the user accesses Oracle Applications or Oracle Mobile Applications; which applications functions a user can use; which reports and concurrent programs the user can run; and which data those reports and concurrent programs can access.
Responsibilities cannot be deleted. To prevent a responsibility from being used, set the Effective Date's to field to a past date and restart Oracle Applications.
Before defining your responsibility, do the following:
Use the Data Groups window to list the ORACLE username your
responsibility's concurrent programs reference on an application-by-application
basis.
Use the Request Groups window to define the Request Group you
wish to make available with this responsibility.
Use the Menus window to view the predefined Menu you can
assign to this
Responsibilities Block
An application name and a
responsibility name uniquely identify a responsibility.
Responsibility Name
If you have multiple
responsibilities, a pop-up window includes this name after you sign on.
Application
The owning application for the
responsibility.
This application name does not
prevent the user of this responsibility from accessing other applications'
forms and functions if you define the menu to access other applications.
Responsibility Key
This is the internal key for
the responsibility that is used by loader programs, (concurrent programs that
load messages, user profiles, user profile values, and other information into
Oracle Applications tables). The responsibility key is unique per application.
Effective Dates (From/To)
Enter the start/end dates on
which the responsibility becomes active/inactive. The default value for the
start date is the current date. If you do not enter an end date, the
responsibility is valid indefinitely.
You cannot delete a
responsibility, because its information helps to provide an audit trail. You
can deactivate a responsibility at any time by setting the end date to the
current date. If you wish to reactivate the responsibility later, either change
the end date to a date after the current date, or clear the end date.
Available From
This is the navigator from
which the responsibility will be available (Oracle Applications forms
navigator, mobile navigator).
A responsibility may be
associated with only one Applications system.
Data Group
Note: Data groups are used for backward compatibility only.
Oracle Application Framework does not support the data groups feature.
Name/Application
The data group defines the
pairing of application and ORACLE username.
Select the application whose
ORACLE username forms connect to when you choose this responsibility. The
ORACLE username determines the database tables and table privileges accessible
by your responsibility. Transaction managers can only process requests from
responsibilities assigned the same data group as the transaction manager.
Menu
The menu whose name you enter
must already be defined with Oracle Applications.
Request Group -
Name/Application
If you do not assign a request
security group to this responsibility, a user with this responsibility cannot
run requests, request sets, or concurrent programs from the Submit Requests
window, except for request sets owned by the user. The user can access requests
from a Submit Requests window you customize with a request group code through
menu parameters.
Menu Exclusions Block
Note: Menu exclusions should be used for backward
compatibility only.
Define function and menu
exclusion rules to restrict the application functionality accessible to a
responsibility.
Type
Select either Function or Menu
as the type of exclusion rule to apply against this responsibility.
When you exclude a function
from a responsibility, all occurrences of that function throughout the
responsibility's menu structure are excluded.
When you exclude a menu, all of
its menu entries, that is, all the functions and menus of functions that it
selects are excluded.
Name
Select the name of the function
or menu you wish to exclude from this responsibility. The function or menu you
specify must already be defined in Oracle Applications.
HTML-Based Applications
Security
Oracle HTML-based applications use columns, rows and values in
database tables to define what information users can access. Table columns
represent attributes that can be assigned to a responsibility as Securing
Attributes or Excluded Attributes. These attributes are defined
in the Web Application
Dictionary.
Excluded Items
Use the List of Values to
select valid attributes. You can assign any number of Excluded Attributes to a
responsibility.
Securing Attributes
Use the List of Values to
select valid attributes. You can assign any number of securing attributes to
the responsibility.
Creating Accounts Receivables Responsibility
 | ||||
| System Administrator |
3. N: Security >
Responsibility > Define
 | ||||||||||
| Responsibility Define |
 |
| Responsibility |
4.
Enter the required data save and Close
5. Assigning the Ivas_receivables
responsibility to ivas user id
Switch Responsibility: - System Administrator | ||||
| Switch Responsibility-System Administrator |
6. N: - Security-> User->
Define
 |
| User- Define |
 | |||
| Direct Responsbilities |
7. Add Ivas_receivables Responsibility
to your User and Save your Work.
8. Save your work and close
9. Assigning the Profile values for Ivas_receivables
responsibility
Switch Responsibility: - System
Administrator
N: - Profile-> System
 | ||||||||
| Profile-System |
 | ||||||||||||||||||||||||||||||||
| System Profile Value |
10. Enter the Application,
Responsibility and Profile Option Name as ‘gl%ledger%’ then Click on Find
11. Select ivas ledger as GL Ledger Name at
Responsibility level
 |
| Responsibility level |
12. Save and close.
13. N: - Profile-> System
 | |||||||||||
| Navigator System Administrator |
 |
| Find system Profile Values |
14. Enter the Application, Responsibility and Profile Option
Name as ‘%mo%oper%’ then Click on Find
 |
| System Profile Values |
15. Select ivas operating
unit as MO: Operating Unit at Responsibility level
16. Save your work and close.
0 comments