Monday, September 8, 2008

Oracle Applications Introduction

To connect the Oracle applications address is:
http://computername.dnssuffix name:portnumber/dev60cgi/ifcgi60
http://computername:oa_html/us/texindex.html

User name is: OPERATIONS
Password is: WELCOME

Responsibility is: System Administration Responsibility

When you click internet explorer and gives the above address then the system will be doing the following activities before getting the log on form:
1) Checks whether the Apache is running or not
2) Checks whether the application server is running or not
3) Checks whether forms server is running or not
4) Checks whether the data base is up and running
5) Establishes a session with applsyspub user
6) Downloads the logon form the client
7) Checks whether the jinitiator is installed or not
8) Enter the user name and password
9) Checks whether the user name and password are correct with the object with applsys schema FND_USER and the table name FND_USER.
10) Checks whether the user has been entrusted with any responsibility with FND_USER_RESP_GROUPS owned by applsys schema and establishes the session.

All the logon users information is tracked through FND_USER public synonym and the table name is FND_USER.

A user can be assigned multiple responsibilities. Any responsibility being accessed in Oracle Applications, the under lined data base user with which the data base operations are performed is Apps Database Account or user.

SCHEMA STRUCTURE OF APPS DATABASE

GL, AR, AP, INV, HR, APPLSYS (System Administration, Application Object Library, Alerts)

APPLICATION SCHEMAS

GL, AR, AP, INV, HR, APPLSYS, APPS, APPLSYSPUB

GENERIC ORACLE DATABASE SCHEMAS

SYS AND SYSTEM


CONCEPT OF DATA GROUP AND CREATION PROCESS:
- While defining a data group the modules and corresponding oracle user accounts can be specified
- The purpose of specifying the oracle user account is to identify the oracle account to connect to when a module responsibility is being accessed. If module specific user accounts have been mapped to the number of user database sessions will be more compare to mapping Apps oracle account to the modules.
- Mapping all Apps to all the modules gives universal access to the entire applications database across all oracle application schemas.
- Data Group is collection of modules, which can integrate with each other through transfer reference and reporting of data.
To define data group

Navigation: Security/ Oracle/ Data Group


Master Information:

Data Group: Give the data Group Name
Description: We can give any description for the above name
Details Information:

Application: We need to select the application name which is going to be part of this data group.

Oracle Id: We need to provide Oracle Id for this data group. Normally APPS

Description: We can give description for each and every line for future reference.

We can press Copy Applications From button to copy Applications from previous defined data groups.

Header Information Stored In: FND_DATA_GROUP
Details Information Stored In: FND_DATA_GROUPS_UNITS.

RESPONSIBILITY

- Responsibility is collection of forms and programs accessible by a specific user.
- Seeded responsibilities are provided when Applications are installed
- Any responsibility with manager or super user suffix provides full access to all the forms and programs of a Module.
- Custom responsibilities can be defined through which the access can be restricted to only specific forms and programs.
- A user can be assigned multiple responsibilities.

TO DEFINE RESPONSIBILITY

Navigation: Security/ Responsibility/ Define

Responsibility Name: Give appropriate responsibility name
Application Name: We need to select Application Name from list of values
Responsibility key: To identify responsibility we can use Responsibility key it is unique.
Description: We need to enter the description.

Effective Dates:

From: We need to give this date from when this responsibility is accessible. This field is mandatory.

To: This is expiry date. This field is optional.

Once an inactive date ha been mentioned for a responsibility all the users accessing that responsibility can not view or access it further.
Data Group:

Name: Select the data group from the list of values.
Application: List will be displayed for applications which are the part of the above data group. We need to select the application.

Available from:
- Oracle Applications or
- Oracle Self Service Web Applications

We need to choose one from where we are accessing the forms.

Request Group:

Name: We need to select from the request group list.
Application: List will be displayed for applications, which are the part of the above data group. We need to select the application.
Menu Name: We need to select menu name from the list of menus.
Web host Name: We need to provide web host name
Web Agent Name: We need to give web agent name.
MENU EXCULSION TAB:
Type: We have to choose this type either menu or function. We can select from list.
Name: Name of the functions to be excluded from this responsibility.
Description: We need to provide description.
EXCLUDED ITEM TAB:
Name:
Application:
SECURING OBJECTS:
Name:
Application:
Table Name: FND_RESPONSIBILITES

REQUEST GROUP

Request group is a group having multiple programs.
MASTER INFORMATION:

Group Name: Give Name of the group
Application: We need to select Application Name from list of values
Code: code which is useful to select at responsibility creation time
Description: We need to enter the description.


REQUESTS DETAILS INFROMATION:

Type: we need to specify the type. List will have the following contents:
- Program
- Application
- Set
- Stage Function

Name: We need to select name of the Program, Application, Set or Stage Function depending up on the value selected in the type column.

Application: This will be automatically appeared when we select the name of the program.

Description: It will be showing automatically once you select name column.
USERS

To define users
Navigation: Security/ User/ Define

User Name: Enter unique user name
Description: Give some description if necessary
Password: We have enter password two times for confirmation

Person: Give person name if he is an employee of the company. We can select from the list of employee values.
Customer: Give the customer name if he is customer of the company. We can select from the list of Customer values.
Supplier: Give the supplier name if he is a supplier of the company. We can select from the list of Supplier values.
Email: Give email id of the above persons
Fax: Give fax number of the above persons.

PASSWORD EXPIRATION:
Days – If you select this you need to provide that in how many days the password expires.
Access – If you select this you need to give that the number of access for that user.
None – If you select this password will not expire till the user is dropped.

Effective Dates:

From: This is mandatory. We need to give from when the user can use the applications.
To: If you gives this date user can not access the oracle after this date.

Responsibilities Tab:

Responsibility: We need to select the responsibility from the list of responsibilities.
Application: This will be populated once the above responsibility is selected.
Security Group: This will be populated once the above responsibility is selected.
Effective Date From: From the date when this user will access this responsibility
Effective Date To: To what date the user can use this responsibility.

Securing Attributes Tab:

Attribute:
Application:
Value:
USER MONITOR:

To see the users activities information

Navigation: Security/ User/ Monitor

1 comment:

Unknown said...
This comment has been removed by the author.