ERP and Oracle E-Business Suite

8/13/2019 ERP and Oracle E-Business Suite

1/51

ERP Definition

ERP stands for Enterprise Resource Planning

ERP is a comprehensive software package

ERP systems typically include the followingcharacteristics:

An integrated system that operates in real time (ornext to real time), without relying on periodicupdates.

A common database, which supports all applications.

A consistent look and feel throughout each module.

Installation of the system without elaborateapplication/data integration by the InformationTechnology (IT) department


2/51

ERP Functional/Technical Components

Finance/Accounting

Human Resources

Manufacturing

Supply Chain Management (SCM)

Project Management

Customer Relationship Management (CRM)

Data Services

Access Control (User and Role Management)


3/51

Generic ERP Tools

User Interface (Forms)

Reports

Database

Web Server/ Applications Server (for Web

Enabled/based ERPs)


4/51

ERP Features

Independent of Operating System

Independent of Database System

Process End-to-End business Information

Modularity

Integration between modules

Interfacing capabilities with external file and businessapplications

Integration with Online Analytical process systems (OLAP)

Web based

Support Multi-Currency transactions Open to Customization and Localization (Native country

implementation


5/51

Commercial Full Fledged ERPs

Oracle E-Business Suite (from Oracle Corp)

Peoplesoft (from Oracle Corp)

JD Edwards (from Oracle Corp)

SAP (from SAP Labs)

Ramco Marshall (from Ramco Systems)


6/51

Industry/Vertical ERPs

Siebel CRM

Reatek

Hyperion Flex-Cube

Tally Accounting Package

Sage Accounting Package


7/51

Benefits of Oracle E-Business Suite

Available in 30 languages Supports multiple currencies

Supports flexible management of businessprocesses

Has single database model for entire businessdata

Supports statutory and customary localrequirements

Is built on open standards Collaborates with trading partners (customer,

suppliers, dealers, wholesalers etc..)


8/51

Oracle E-business Suite Product

Families


9/51

Important Modules in Product Families Financials

General Ledger

Receivables

Cash Management

Fixed Assets

Payables

Sub Ledger Accounting

HRMS

HR

Payroll

Time and Labor

Oracle Learning Management

Advanced Benefits

Manufacturing

Process Manufacturing

OPM Costing

Process Execution

Product Development

E-Records

OPM Quality Discrete Manufacturing

Bills of Material

Costing

Quality

Work in process

Engineering


10/51

Important Modules in Product Families Projects

Project Costing

Project Billing Project Manufacturing

Project Resource Management

Project Management

CRM

iStore

Service Requests

Contracts

Teleservice

Depot repair

Field Service

Administration

System Administration Application Object Library

Alerts

Workflow


11/51

Important Modules in Product Families Sales and Marketing

Order Management Pricing

Shipping

Release management

Procurement

Purchasing

iProcurement

Sourcing

iSupplier


12/51

Oracle E-business Architecture


13/51

Oracle E-Business Architecture Desktop/Client tier: This tier provides the user interface.

This tier could consist of a desktop computer, laptop or

mobile devices like PDAs, and so on. This tier is mainly

involved in capturing and displaying information to the user.

Application tier: This tier is responsible for holding all the

application logic. It supports and manages various

Applications components, and is sometimes known as the

middle tier.

Database tier: This tier is responsible for storing and

retrieving the application data. It supports and manages the

Oracle database.


14/51


15/51

E-business Suite Shared Entities


16/51

AOL Shared Entities


17/51

Shared Entities Ownership

Set of Books - General ledger

Units of Measure - Inventory

Items - Inventory

Suppliers - TCA

Customers - TCA

Organizations - HR

Locations - HR

Sales Force - Sales and Marketing

Employees - HR


18/51

Major Business Processes


19/51

Procure to Pay (P2P)


20/51

Procure to Pay (P2P)

Procure to Pay

This business flow outlines how a company

raises purchase orders for procurement of

goods or service and then processes

associated invoices for payment, transfer to

GL and reconciliation with bank statements.


21/51

Order to Cash (O2C)


22/51

Order to Cash (O2C)

Order to Cash

This business flow encompasses activities

starting from order entry, checking/booking of

the items in the inventory, shipping of goods,

raising invoices, reconciling bank statements

and transferring accounting entries to General

Ledger.


23/51

People to Paycheck


24/51

People to Paycheck

People to Paycheck

This business process encompasses activities related tocalculation and generation of payroll payments toemployees. This flow enables users to set up necessarypayroll elements and methods for particularemployees, perform payroll processing (standardperiodic, supplementary, and one-offs for a singleemployee), pay employees by check or direct deposit,

request various related reports, and perform costingand transfer of completed payroll data to the generalledger.


25/51

Multi-OrgWhat Is Multi-Org?

Multi-Org is a server-side (applications and database) enhancement thatenables multiple business units in an enterprise to use a single installationof Oracle Applications products while keeping transaction data separateand secure. The Multi-Org enhancement uses native database views tobuild a security layer on top of a single installation of Oracle Applications.

In Oracle Applications Release 12, the following products support Multi-Org capabilities:

Cash Management

Order Management, Shipping Execution and Release Management

Payables

Property Manager

Projects Purchasing

Receivables

Sales Compensation

Sales and Marketing

Service


26/51

E-business Suite Multi-org Structure

BusinessGroup

LegalEntity1

OperatingUnit1

OperatingUnit2

LegalEntity2

OperatingUnit3


27/51

E-business Suite Multi-org Structure

LegalEntity1

OperatingUnit1

InventoryOrg1

WIP Org1

OperatingUnit2

InventoryOrg2


28/51

E-Business Suite Modules

Implementation by Modules


29/51

Multi-org Data Security Model


30/51

HR Organization Types

Business Group

Legal Entity

Operating Unit Inventory organization

WIP organization


31/51

Organization Naming Conventions

Organization Naming ConsiderationsMulti-Org naming conventions should be used to identify the Oracle Organizations

Classification (for example, Set of Books, Operating Unit, Inventory Organization) andits unique characteristics like country or currency, location name, and usage.

The following are general guidelines for creating Organization Names:

Sets of Books where:

SOB_; is an operational book that obtains journal entries directly from a subledger

system (for example, accounts payable, inventory).

COB_; is a consolidation set of books.

ROB_; is a reporting set of books when using the Multiple Reporting Currency (MRC)

feature.

Business Group: BG_ Human Resources Organization: HR_

Legal Entity: LE_

Operating Unit: OU_


32/51

Fundamentals of System

Administration


33/51

Define New Application Login User


34/51

Assigning Responsibilities to Users


35/51

Tables for User and Responsibility

Assignment

User

FND_USER

Responsibility Assignments to User

FND_USER_RESP_GROUPS

Where FND stands for foundation. All the database

tables of System Administration, Applicationobject library, Alerts and Workflow modules start

with FND_ prefix


36/51

Importance of Responsibilities


37/51

Components of Responsibility


38/51

Components of Responsibility

(Defined)

Datagroup : Data group: A data group specifies

the Oracle Application

Menu : A menu specifies the forms that a

responsibility can display and the functions it

can access.

Request Group : Collection of reports and

programs that can be submitted thru a

responsibility.


39/51

Define a New Responsibility


40/51

Function and Menu security


41/51

Function and Menu security

Use exclusion rules to configure a responsibility. You can exclude functions at any level. When you exclude a menu item from a responsibility, all menus and functions that are

nested in that menu are also excluded.

When you exclude a function from a responsibility, all occurrences of that function

throughout the responsibilitys menu structure are excluded.

A full access responsibility with a menu that includes all the functions in an application is

predefined for each Oracle Applications product. Some applications may provide additionalpredefined responsibilities that include a smaller set of functions (that is, fewer forms and

subfunctions).

As a System Administrator, you can restrict the functionality a responsibility provides by

defining rules to exclude specific functions or menus of functions. In fact, we recommend that

you use exclusion rules to customize a responsibility in preference to constructing a new menu

hierarchy for that responsibility.

For example, suppose you want to customize a responsibility to restrict the functionality of a

form included in that responsibility.


42/51

Profile Options

Profile options control the behavior/access

levels for the different features and

functionalities available from the Oracle E-

business suite.


43/51

Profile option setting levels

Site

Application

Responsibility

User


44/51

Profile Option Execution Hierarchy

Request processing in Oracle E


45/51

Request processing in Oracle E-

business Suite

Tasks in Oracle E-business suite are broadlycategorized as online/immediate andoffline/background processing tasks.

For all the Report and program requests

submitted thru the Standard RequestSubmission, the execution is handled by thebackground processing engine called ConcurrentManager

Concurrent manager handles/executes multiplereport/program processing requests by default ina first come-first serve basis.


46/51

R12 Oracle Database Model Every Product/Module/Application uses a different schema. (GL for

General ledger, AR for Receivables, AP for Payables)

Tables, Views and Sequences in the product specific schema.

All code objects (triggers, packages, procedures, functions) owned by AppsSchema.

Public synonyms of tables, views and sequences of all the products ownedby Apps schema

All the Front end responsibilities access the R12 database thru Appsschema.

Applsys schema holds the tables of Sysadmin, AOL, Alerts and Workflowmodules.

Applsyspub schema tracks the Application user sessions from the logintime to the logout time.

Every module/product has a two corresponding tablespaces one usertablespace and another index tablespace.

The password of Applsys and Apps schema must always be same, else theimportant services/processes like Concurrent Managers etc will notfunction.

l fi ld


47/51

Flexfields A flexfield is a Flexible Field which can

capture varying length of informationdepending on the Organizations requirement.

Types of Flexfields Key Flexfield

Descriptive Flexfield

Range Flexfield

D i ti Fl fi ld


48/51

Descriptive Flexfield Appears as short, unnamed text item in

majority of forms in Oracle EBSresponsibilities.

By default, all the DFF items/fields would bedisabled.

DFF is used to capture additional businessinformation that is unique to a business.

All DFFs are enabled in the AOL

Module/Application developer responsibility. All DFFs are owned by AOL module.

DFF are accessed as Pop-up windows.

D i ti Fl fi ld


49/51

Descriptive Flexfield

DFF information is captured in ATTRIBUTE

Prefixed columns. Oracle EBS provides from a minimum of 7 to a

max of 45 attribute columns in majority of tables.

DFF Implementation is optional.

DFF data is not reported on the Standard reportsof Oracle EBS reports. Reports must becustomized to publish the output of DFFinformation.

New/Additional DFFs can be registered with AOLmodule.

DFF information cannot be shared across formsor modules.

K Fl fi ld


50/51

Key Flexfields Key Flexfield appear as normal text items with

Labels/boilerplates in Oracle EBS forms.

KFF implementation is mandatory. If a KFF is notimplemented, certain processes, features,functionalities or set of integrations will not functionproperly.

KFFs are also accessed as pop-up windows in theoracle EBS forms.

KFFs information is stored in SEGMENT prefixedcolumns.

All standard reports by default supports the reporting

of KFF data. New/Additional KFFs can be registered with the AOL

module.

KFF information is shared across Forms/Modules.


51/51

Range Flexfield Range Flexfield is automatically implemented

once the corresponding KFF is implemented.

Range based operations can be performed in

the reports and forms using the Range

flexfield, with the validation that higher rangevalues must be equal to or greater than lower

range of values.

ERP and Oracle E-Business Suite

Documents

Transcript of ERP and Oracle E-Business Suite