Table Suffixes in Oracle Apps

Table Suffixes:

You have lot of tables ending with different suffixes in Oracle Apps database. Did you ever wonder what these denote? Listed below are the different table suffixes and what they mean.

_ALL: Table ending with _ALL means it stores data related to multiple organizations. Such tables definitely will have a column called org_id which specifies to which org the record belongs to.

_TL: Table ending with _TL is a Translation Table. Such tables have a column called language

_B: Tables ending _B are the base tables

_VL: Tables ending with _VL are Views built upon multi language or translation tables. In other words such views combine base table data with translation table data. If you wish to see the data related to a one particular language, you should set the language using USERENV(‘LANG’).

_V: Tables ending with _V are views

_S: Tables ending with _S are Sequences

_A, _Avn, _ACn: Tables ending with _A, _Avn, _ACn are audit tables.

_F: Tables in which data is tracked with two date columns (Effective_start_Date, Effective_end_date). These tables are primarily used in HRMS and payroll modules.

_DFV /_KFV: DFF/KFF view created on the base table. This is the best way to get the concatenated value of DFF/KFF.
Also using this table the values can be queried based on the DFF/KFF name and not attributes column.

Basics of ERP and AIM Methodology

ERP: Enterprise Resource Planning

Here Resource means 5 m’s
1. Money
2. Man power
3. Machinery
4. Material and
5. Management

ERP Purpose: Planning for proper utilization of resources for a business organization .

ERP as a Product : all objects(i.e. forms, reports )and all other programs are
developed and throwly tested and those will be provided with these ERP.

Methodology : the process used to implement ERP Product for a business Organization.

AIM (APPLICATION IMPLEMENTATION METHODOLOGY):

Methodology for Oracle Apps is AIM(Applications Implementation Methodology)
Phases in Aim Methodology:

1. Definition Phase
2. Operational Analysis Phase
3. Solution Design Phase
4. Build Phase
5. Transition Phase
6. Production Phase

1. Definition Phase: Here the functional consultants prepare the sample structure
(Blue Print) for the real business by gathering the information.

2. Operational Analysis phase: In this the functional consultant prepare BR100
(Business Requirement).

3. Solution Design Phase: here the functional consultant will prepare MD50 by using
BR100. MD50 is the functional document.

4. Build Phase: here the technical consultant converts MD50 to MD70. MD70 is the
technical document. Then the technical consultant prepare the final object and go
with testing, i.e. Unit Testing.

5. Transition Phase: here SIT(System Integration Testing) and UAT(User
Acceptance Testing) is done. Functional consultant does SIT. After this the
functional consultant will train the user in oracle apps product and user does UAT.
If it is satisfied by the user, it is sign off and product will be given to the user.

6. Production phase: loading the project in the client place. Where the server of
oracle apps in the client place.


Types of Docs in Oracle Apps:

MD 050 -- Module design by the functional consultant.
MD 070 -- Technical Document designed by the technical consultant.
MD 020 -- Technical document designed by the functional document.
MD 0120 -- Migration and user training document by the technical consultant.
CV 040 -- Conversion of the functional document by the functional consultant.
CV 060 -- Conversion of the technical document by the technical consultant.