, , , ,

Multi Org(Multiple Organizations)

The Oracle Applications organization models define organizations and the relationships among them in arbitrarily complex enterprises. This organization model serves as the cornerstone for all of the Oracle Applications products. It dictates how transactions flow through different organizations and how those organizations interact with each other.
Generally, a complex enterprise has several organization structures, such as Internal, Accounting, and Human Resources. You are able to define different structures to customize Oracle Applications according to your business needs.
Basic Business Needs
Oracle Applications provides you with the features you need to satisfy the following basic business needs:

  1. Use a single installation of any Oracle Applications product to support any number of organizations, even if those organizations use different sets of books.
  2. Define different organization models
  3. Support any number of legal entities within a single installation of Oracle Applications.
  4. Secure access to data so that users can access only the information that is relevant to them.
  5. Sell products from a legal entity that uses one set of books and ship them from another legal entity using a different set of books, and automatically record the appropriate intercompany sales by posting intercompany accounts payable and accounts receivable invoices.
  6. Purchase products through one legal entity and receive them in another legal entity.

Major Features
Multiple Organizations in a Single Installation
You can define multiple organizations and the relationships among them in a single installation of Oracle Applications. These
organizations can be business groups, sets of books, legal entities, operating units, or inventory organizations.
When you run any Oracle Applications product, you first choose an organization—either  implicitly by choosing a responsibility, or explicitly in a Choose Organization window. Each window and report then displays information for your organization only. Organizations that share the same functional currency, Accounting Flexfield structure, and calendar can post to the same set of books.
Secure Access
You can assign users to particular organizations. This ensures accurate transactions in the correct operating unit.
Sell And Ship Products From Different Legal Entities
You can sell from one legal entity and ship from another, posting to each organization’s set of books.
Receive Goods Into Any Inventory Organization
You can enter purchase orders and assign for receipt any inventory organization that uses the same set of books. Your purchase order operating unit and receiving inventory organization must share the same set of books to receive against a purchase order.
Automatic Accounting for Internal Requisitions
You can create an internal requisition (sales order) in one organization, then ship from another organization, with correct intercompany invoicing.
Multiple Organizations Reporting
You can set up your Oracle Applications implementation to allow reporting across operating units by setting up the top reporting level. You can run your reports at the set of books level, legal entity level, or operating unit level

/by
, , , , ,

Self Service Features


Implementors and administrators can verify the successful configuration of end user functions by performing the tasks described in this section.
Self-Service Registration
Oracle User Management enables users to register for access to applications without requiring assistance from administrators. To register for application access, users must provide information in the required fields and click the Submit button.
Oracle User Management ships with the following sample self-service registration processes:

  • Employee Self-Service Registration
  • Customer Self-Service Registration (external individuals)

Organizations can use these registration processes in their existing form, or can use them as references for developing their own registration processes.
Requesting Additional Application Access
Oracle User Management enables you to request additional access to the specific applications for which you are eligible. Application access is based on roles and to access an application you must be granted the appropriate role. Perform the following to view the roles you have been assigned and to request additional ones.
Steps
1. After logging into the system, click the Preferences link in the upper right corner, and click the Access Requests link in the sidebar menu. The Access Requests page displays the roles you have been assigned. Click the Request Access button to request one or more additional roles.
2. Most roles are organized according to role categories: roles that are not categorized appear under the Miscellaneous node. Select the role category that contains the role you want to request. If you do not see the required role, then either you are not eligible for the role or it has not been set up to for additional access requests.
3. Select the role or roles you require for additional access to the system, and click on the Add to List button. You can optionally remove roles from your list by clicking on the Remove Roles button.
4. When you have selected all your required roles, click on the Next button.
5. Enter a justification for your request and click on the Next button. You can remove any pending roles or check their status in the page that appears next.
Guidelines
Some roles may require you to provide additional information. In such cases, the system will prompt you for additional information before you can complete the process for requesting a role.
If the role being assigned would cause a separation of duties violation, the operation will flag this in the workflow attributes, and any approvers for the request will see the details.
Login Assistance
It is not uncommon for system administrators to 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, who cannot do any work in the meantime, and for the administrator.
In addition, a user will occasionally request the password to be reset, when it is actually the user name that has been forgotten, or vice versa. This type of occurrence leads to even more time being lost.
A new feature reduces the time spent in such administrative activities by implementing a login help mechanism that is easily accessed from 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, you can either:

  • Go to the Forgot Password section, enter the correct user name and then click on the “Forgot Password” button. You will then be emailed details of how to reset your password.
  • Go to the Forgot User Name section, enter the email address associated with the account, and click on the Forgot User Name button. The user name will then be emailed to the address specified.

For security, the relevant data is stored securely in workflow tables, and the URLs employed have both an expiration time and a single-use limitation.
The identify verification process required in previous Applications releases is no longer needed. Instead, a link to a secure page is sent to the email address of the user name defined in the system. From this secure page, the user can change password immediately.

/by
, , , , , ,

User and Data Auditing

There are two types of auditing in Oracle Applications: auditing users, and auditing database row changes.
Auditing User Activity
Auditing users is supported by:
• Sign-On:Audit Level profile option setting
• Audit Reports
Based on the audit level you choose, Sign-On audit records usernames, dates, and times of users accessing the system, as well as what responsibilities, forms, and terminals users are using.
Auditing Database Row Changes
Auditing database row changes is supported by:
• From the Help menu, About This Record
• AuditTrail:Activate profile option setting
• Audit forms
/by
, , , , , ,

User Session in R12

Using the following profile options you can specify limits on user sessions.
ICX:Session Timeout
Use this profile option to enforce an inactivity time-out. If a user performs no Oracle Applications operation for a time period longer than the time-out value (specified in minutes), the user’s session is disabled. The user is provided an opportunity to re-authenticate and re-enable a timed-out session. If re-authentication is successful, the session is re-enabled and no work is lost. Otherwise, Oracle Applications exits without saving pending work.
If this profile option to 0 or NULL, then user sessions will never time out due to inactivity.
ICX: Limit time
Use this profile option to specify the absolute maximum length of time (in hours) of any user session, active or inactive.


/by
, , , , , ,

Objects in AOL


Data Security uses the concept of an Object to define the data records that are secured.
Object
Data security permissions are managed on objects. Business entities such as Projects and Users are examples of objects. Only a securable business-level concept should be registered as an object. An object definition includes the business name of the object and identifies the main table and primary key columns used to access the object.
Object Instance
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. An instance is identified by a set of one or more primary key values as defined by the object. In addition, “All Rows” for an object indicates all data rows of the object.
Users and Groups
Users and groups are Oracle Workflow roles. See the Oracle Workflow documentation for more information on roles.
Privileges given to users and groups determine their access to secured objects.
The data security system allows you to assign privileges to groups of users instead of assigning privileges to each user individually.
Users
Users are individuals who have access to software applications at a particular enterprise. A user must have a unique name and should map one-to-one with an individual human or system. “Group” accounts are not correct uses of the user entity.
Groups
Users can belong to Groups. The grouping can come from position or organization relationships modeled in applications such as Oracle Human Resources. Alternatively, ad-hoc groups can be created explicitly for security purposes. A group is sometimes referred to as a role.

Creating Objects

Use these pages to find, create, and edit data objects. You define objects to be secured in the Data Security system. Objects can be tables or views. An object must be queryable in SQL, and the combination of primary key columns specified must be a unique key.
In these pages, objects are described with the following

  • The Name is the name that appears in the Object Instance Set and Grants pages. This name should be user-friendly.
  • The Code is the internal name of the object.
  • The Application Name is the owning application.
  • The Database Object Name is the name of the underlying database object
/by