ORACLE EBS OVERVIEW

SESSION 1 OF 4

RAJESH ANAND

Agenda

• Organization Structure

• Security

• Business Group, Legal Entity, Operating

Unit, Inventory Org

• Application Object Library

Business Group, Legal Entity, Operating Unit,

Inventory Org

• Business Group: Holds employee information and is the

top level

• Legal Entity: Legal entity is the one for which you want

a Balance Sheet and Income statement

• Ledger: Is the accounting book and has 4C’s 1. Chart of Account (Particulars of Goods)

2. Currency (Amount)

3. Calendar (Date)

4. Subledger Accounting Convention (Cash / Accrual)

• Operating Unit: The purpose of an operating unit is to

segregate or separate sub-ledger transactions

Business Group, Legal Entity, Operating Unit,

Inventory Org

Responsibility relationship with BG, Ledger,

LE and OU

Profiles options are used to establish the relationship

between a Responsibility and Business Group,

Ledger, and Operating Unit

Responsibility relationship Inventory

Organization access is used to grant a responsibility

access to an Inventory Org

Security

• User Definition

• Responsibilities

� Menus

� Function

� Forms

� Exclusions

� Request Set

� Data Access

• Profiles

• Reporting

User Definition

User

Employee/Person Responsibilities

Profile Options

Security – User Definition

User:

• Attached to a person/employee

• Has access to responsibilities

• Profiles can be used for various purposes including

application behavior, security and control, access, etc.

Security – Responsibility Definition

• Responsibility Definition includes application, request

group and a menu

• An application is a module/sub-ledger

• A request group is a set of reports

• A menu can be made up of sub-menus and functions

• Sub-menu can be a collection of functions

• A function is typically a form

Take Away:

� A menu, sub-menu and function can access areas

within different applications/modules

� A responsibility can span across various areas within

Oracle EBS

Security – Responsibility Definition

• Exclusions: Restrictions can be enforced within a

responsibility through various options:

• Menu Exclusions

• Menu Definition

Take Away:

� Considerations: Segregation of Duty typically drives

Responsibility definition

Examples:

• Invoice entry responsibility should not have access to

payment processing

• Supplier setup responsibility should not have access to

purchase order processing

Security – Profiles

(Operating Unit, Business Group, Ledger)

• A responsibility is tied to an Operating Unit, Business

Group and Ledger through profile options

• Access to an inventory organization is controlled by

Organization Access within the inventory module

• Profile option usage is not limited to the above

Security

Responsibility

ApplicationRequest Group

Menu

Menu(s)/Sub-Menu(s) Functions

• Operating Unit

• Business Group

• Ledger

• Inventory Organization(s)

Concentric Circle Rule for Profile Options

Site

Application

Responsibility

User

Inner circles override the values from

outer circles and inner circles inherit

values from outer circles

AOL: Concurrent Requests

• Definition

• Executable

• Request Sets

• Submission

• Monitor

• Diagnostics

• Attaching a concurrent program to request groups

AOL: Lookups, Personalizations and

attachments

• Application Lookup

• AOL Lookups

Personalizations:

• Requirements

• Form personalizations

Attachments:

• Types

• How to?

• Levels

FlexFields

• Key Flexfield: A single or multi-segment data element

that uniquely identifies key data elements/codes in the

application. Example – Accounting Structure, Item

• Descriptive Flexfield: Additional information for master

or transaction data.

* Descriptive Flexfields can be context sensitive whereas

Key Flexfields cannot be context sensitive

FlexFields

• Flexfield Definition: Flexfields are made up of

segments and each segment in turn can be based upon

a pre-defined list of values (static or dynamic).

• Value Sets: Pre-defined list of values are called value

sets

� In case of static values, pre-defined values can be

maintained

� Dynamic value sets can be based upon values in the

database (SQL Statement)

� Value sets can have constant values

Concentric Circle Rule for application level

setups

Application/Sub-

ledger system

settings

Master

Data

Transaction

Data

Inner circles override the values from

outer circles and inner circles inherit

values from outer circles