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.
You can also set the client_info to specific operating unit to see the data specific to that operating unit only.
Check out the article -> MOAC – Oracle Apps ORG_ID, Multi Org Concept
_TL Table ending with _TL is a Translation Table or multi language tables. Such tables have a column called language. These tables
provide multiple language support.
The primary key is the id column plus the language column.

multi language tables always has corresponding another table with the same name minus the _TL a table without postfix or postfix
as _B or postfix as _F

Translatable table. Holds the translated names/descriptions for base objects will have one row per installed language linked to the
base table by the _id column.

_B Tables ending _B are the base tables

They are very important and the data is stored in the table with all validations. It is supposed that these tables will always contain
the perfect format data. If anything happens to the BASE table data, then it is a data corruption issue.
_B – base table holds the main details of the object in question and it implies that there is also a _TL table for it.
You’d never find a _B table without a _TL table. the primary key is the id column.
_F These are date tracked tables, which occur in HR and Payroll. For these there are two date columns EFFECTIVE_START_DATE
and EFFECTIVE_END_DATE which together with the PK identifies a row uniquely. The date intervals cannot overlap.

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

Some _F tables come with a matching _TL tables, too.

_V Tables ending with _V are views

tables are the views created on 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’).

but the view that represents the join of the base table and the TL table using the user’s session language. You can assume that
almost all _TL tables come paired with a _VL view.

_X Again a view on top of the base table but displays only those date tracked records that are effective as of sysdate, e.g.
per_people_x
_S Tables ending with _S are Sequences used for finding new values for the primary key of a table.

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

_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
_KFV is the view which contains all the information about Key Flex Fields(KFFs).
_DFV is the view which contains the information about Descriptive Flex Fields(DFFs).

_M multiple changes per date table.

Like a _F table, but it allows rows to start and end on the same day.
There is only one such table per_all_assignments_m, and it has additionally the effective_sequence in the primary key.
_DN Denormalised table:
Usually just a simplification of another table that holds hierarchies or trees of some kind.
The denormalised tables are populated by ESS processes and hold the flattened hierarchy that has direct links between all nodes
and their distance.
Those are used e.g. for security profiles based on the manager hierarchy.