E-Business Architecture

(R12.1.3)

1
Outline

► E-Business Version History

► E-Business Modules
► E-Business Architecture
► E-Business FileSystem
► E-Business Login Hierarchy

2
E-Business Version History

3
 E-Business Version History

R12.0.3
R12.2.2.1
R12.0.2 R12.0.6 R12.2.2.2
R12.1.1
R12.1.2 R12.1.3 R12.2.2.3 R12.2.4 R12.2.7 R12.2.8
R12.0.1 R12.0.4

2007 2008 2009 2010 2013 2014 2017 2018

 E-Business Version History

https://blogs.oracle.com/ebs/oracle-continuous-innovation-on-oracle-e-business-suite-122
5
http://www.oracle.com/us/support/library/lifetime-support-applications-069216.pdf
E-Business Modules

► To facilitate big businesses, Oracle Corporation have created

collection of software in the category of ERP (Enterprise Resource
Planning) known as modules, that are integrated to talk to each other
and known as Oracle Applications or E-Business Suite.
► Oracle ERP Oracle Ebusiness Suite(Ebiz) Oracle Apps all are same ☺
► Oracle is a complete enterprise suite of
• Financial,
• Human Resources,
• Manufacturing,
• Supply Chain,
• CRM,
• Front Office Applications & many more modules

6
 E-Business Architecture

E-Business Version
Layer 11.5.10.2 12.0.4 12.1.* R12.2.*

Database 9iR2 10gR2 11gR1 11.2.0.4

RDBMS 9.2.0.6 10.2.0.4 11.1.0.7 12c is supported

Developer 6i 10g 10g

10.1.2.3
Forms & Reports 8.0.6.3 10.1.2.2 10.1.2.3

Oracle WebLogic
Server 10.3.6 in
9iAS 10gAS 10gAS Oracle Fusion
Web & Java
1.0.2.2.2 10.1.3.0.0 10.1.3.4 Middleware 11g
Release 1
(11.1.1.6)

Sun JRE Sun JRE Sun JRE

Java (JDK) Jinitiator 1.3.1.24
1.5.0_13 1.6.0_10
7 1.6.0_10
E-Business Architecture
For R12.1.*

8
E-Business Architecture

9
E-Business Architecture
(Application Tier)

10
E-Business Architecture
(Application Tier)
► $APPL_TOP
► Top directory for all Oracle Application software
► Contains $PROD_TOP for each product
► Applications patches make changes in APPL_TOP
► Environment variables setup at login
► Environment files
► Can be shared (shared APPL_TOP)
► NFS mounted filesystem
► Shared by two or more application tier servers
► Apply patches once for all application tiers
► Single point of failure
11
E-Business Architecture
(Application Tier)
► Environment files are the type of configuration files usually used
to set up a working environment to point to the various top-level
directory structures such as COMMON_TOP and other environment
variables such as NLS_LANG relevant to Oracle Applications
configuration. During the installation, several environment files
are created, usually in the root of different ORACLE_HOMEs.
► For applications developers, the most important environment file
is the consolidated environment file APPS<CTX_NAME>.env in the
APPL_TOP directory, where <CTX_NAME> is
► the configuration context name, usually in the format
<DATABASE_SID>_ <HOSTNAME>.

12
E-Business Architecture
(DB Tier)
► Product schemas Contains only data-related objects
such as : product database tables and sequences. An
example is the GL (General Ledger) product. All of the
data-related tables are owned by the GL schema in the
database.
► APPS schema Contains database code–related objects
for all the products : such as PL/SQL code, views,
triggers, and others.

13
E-Business Architecture
(DB Tier)
► To achieve a higher reuse of data sharing, Oracle
Applications utilize an APPS database schema.
► Imagine for a second if all the database code and data
objects were owned and stored in the product-specific
schemas such as GL (General Ledger), AP (Payables), PO
(Purchasing), and others.
► In this scenario, it would be really difficult to manage the
access rights for all the objects that, for example, a
database stored procedure needs to access in other product
schemas.
► The approach used in Oracle Applications is to have database
synonyms in the APPS schema for each database table and
sequence in individual product schemas, and in addition to
that, each product schema grants full privileges to APPS
schema

14
E-Business Architecture
(DB Tier) – Module/Application
Specific

15
E-Business Architecture
(DB Tier – Import SCHEMA’s)
► APPLSYS This schema contains objects from the
Oracle Applications foundation and technology layer.
Examples of the products in this category are AD
(administration utilities) and FND (Applications
foundation).
► APPLSYSPUB This schema is a special one and is used
only for the purposes of the initial user login process to
validate a user’s credentials.

16
 E-Business - Queries
select product_group_name, release_name, applications_system_name,
aru_release_name from FND_PRODUCT_GROUPS

select * from all_users where username='GL'

select * from all_objects where object_name ='GL_LEDGERS'

17
E-Business - LoginScreen

18
E-Business - UI

Responsibility
User

Main Menu

SubMenu
Functions(OAF/Form)
19
 E-Business – Login Hierarchy

► USER
► RESPONSIBILITY

► MAIN MENU

► SUB-MENU

► FUNCTION
(OAF/FORM)

► FUNCTION(OAF/FORM)

► ..

► …

► …

► ..

20
E-Business – Login Hierarchy

► A responsibility is a collection of business functionalities, such as

UI screens and reports, that is granted to Oracle Applications users
for the purpose of access control to the screens and data that are
related to the user’s role within the organization.
► A menu is a reusable grouping of application functionality and
consists of functions and other menus.
► A request group is a grouping of reports and concurrent programs
that is assigned to a responsibility.

21
E-Business Suite – File System

er
Ti
n
atio
l ic
p
Ap

ie r
s eT
t a ba
D a

22
E-Business Suite – File System
Application Tier

$JAVA_TOP

ShellScript/SQLLoader Files

Forms fmb files

Reports RDF OAF Class Files and BC4J XML Files

SQL Scripts 23