You are on page 1of 8

ORACLE APPLICATION-R12

FC- Stands for Functional Consultant


TC- Stands for Technical Consultant
APPS DBA.
Major:
Oracle application R12 is a Implementation Software -- new software
3 people basically involve in doing this majorly
1.APPS DBA- Deals with privileges and data base issues and migration of data .
2.Functional Consultant - Discuss with the purchasing client regarding the usage of the R12
and change according to the REK. Whatever changes /needed by the client is called gaps
Client will find some gap this is called GAPS
Gap Analysis -finding out the gaps between business and oracle apps software
Example: 10 screens/reports need to be developed ----report is called development
5 screen changed----report called customization
10 reports have to be developed ----R.DEV

Changes are called Customization

2 reports modified----R.CUSTZ

new reports needed called as


development

Customizations>changes
developments> new development
Support Project : after the changes of the ERP.
Functional consultant and APPS DBA will meet
3.Technical Consultant:
ERP is a software package>> with oracle apps>> customer buys>>for business areas
Business areas are called modules
example: Finance, Sales etc.
ERP>Software>Customer>Modules Integrated Software>

Roles:
DBA, Functional, Technical consultant.

Getting data into oracle new application is called Data migration.


Data Migration:---done by TECH CONSUL/APPS DBA
Legacy systems(customer system) >>Oracle Application>>
functional Consul give REK to Tech according to client requirement.
Types of Projects:
1. Implementation
2. Customization
3. Development
4. Support
Upgradation:
11i -- 3C { Calendar , Char ,Currency}
R12--4C { Calendar, Char, Currency, Convention}
Documentation:
Reports>>Changes>>Added, removed, calculation, font design.
Development>>reports>columns, calculation(formulas),sample design
AIM Methodology Document---Application Implementation Methodology.
BR--Stands for Business Required document
BR 100 -- Prepared by Functional Consultant-- Rek from client
FC- will prepare MD50(FDD)- Functional Design DocumentTC-will prepare MD70(TDD)- Technical Design Document
Development
Testing
Test scripts
Functional Test
Testing Team (TD50)-Testing Document
User Testing
User acceptance

Migration Object (MD120)--DBA-Migration Document


Sign Off

---------------------------------------------------------------------------------------------------RICE Components:
1.
2.
3.
4.

Reports
Interfaces
Conversions
Extensions

Reports--- As said above


Interfaces-- Data migration-periodically (every month etc)
Conversions--Data Migration --done only one time as implementation.
Extensions--Any customizations/new development is called extensions
Workflow: Data flow diagram --it means if it is raining I will not go to movie if not I will go
Decision making
XML Publisher Reports --

Important Responsibility:
1. System Administrator
2. Application Developer
3. Xml publisher administrator
----------------------------------------------------------------------------------

Technical Architecture
The application is stores in a folder cycle step as below
Apps

Appl
PO ------------Ap, Ar, Gl--Under PO
Report
Sql--- Queries
Forms
Bin
In
Import-- Migrations files

Multiorg--- A single installation accessed by different branches of same organisation


called as Multiorg.
After multiorg is installed FC comes , how many branches you have

Example for Multiorg process Structure ---Business Group = TATA---- Brand --Legal entity=>registered trade make, Location, Address, Phone Number, account number
Tax filling details and files.
e-7879 register number
Ledgers => Books =>4c (Reason for 4C in ledger){Calendar, Char, Currency, Convention}
Calendar => Jan, Feb, Mar-Chart of accounts => list of names commonly used in business terms
ex: Furniture , Sal, bonus, Misc
Currency-Convention-- version should be defined --rates--methodology

Branches (Operating Unit)--Operating unit where actual business is done.


Unique number for each operating unit.

Inventory Organization ---Go down---Each branch


Sub inventory ,sub inv
Locators
Row, rack, bin

After which data migration is the next step-------------------------------------------------------------------------------------------------------------------Types of Tables:


Module Integration
Module in Oracle Application
Popular Cycles Used
Multi org table -- multiple organization data stored in a table is called Multi org table.
Q.)how to recognise these tables
Sol.) Ending will ( _all )
Views: View table ends with ( _v - called as org specific table)
Example: Emp Dept
Create View empdept_v
Select empno, ename, sal, dept.deptno, dept.dname
from
Emp, Dept
Where emp.empno=dept.deptno

Select * from empdept_v


Language specific tables---- ( _tl)
Language specific views---- (_vl)
temp table ---( _temp)

interface ----( _interface)


Interface table is the middle table from original table to oracle application table, usually the
data is transfer (tables) from client to interface before migrating to Apps.
All modules have interface table like Po, Gl etc...
Module Integration
PO--Purchasing Order
AP-- Accounts Payables
AR-- Accounts Receivable
OM--Order Management
GL-- General Ledger
INV-- Inventory
WIP-- Work in Progress
BOM-- Bill of Materials

Simple Cycle of Business


AP<=PO=>INV=> OM=>AR=>GL

P2P(Procure to Pay): PO AP GL
O2C(Order to Cash): OM AR GL

Module in Oracle Application


Finance
----AP , AR, CM, GL , FA

Sales and Distributions , Supply chain management


-----PO inv om, PO, inv, om, wip, bom
Hrms
----Payroll
Crm
-----Isupport, Service request, install base
Oracle has developed 270+ Modules
AOL Concepts-- Application object library
System Administrator--- Responsibility
Application Developer--Responsibility
The above responsibility will be available in ( fnd top)
Ex: fnd_user.
Application
Creating a menu

User

Request group

Related table who columns

Responsibility

Responsibility

Last class details

You might also like