R12 Table Naming Convention

-

Here is a good explanation for table name conversiton in Oracle R12.

 _ALL
Table holds all the information about different operating units. Multi-Org environment. You can also set the client_info to specific operating unit to see the data specific to that operating unit only.
 _TL
Tables corresponding to another table with the same name minus the _TL. These tables provide multiple language support. For each item in the table without _TL there can be many rows in the _TL table, but all with different values in the LANGUAGE column.
 _B
These are the CORE BASE tables. They are very important and the data is stored in the table with all validations. It is supposed that these table will always contain the perfect format data. If anything happens to the BASE table data, then it is a data corruption issue.
 _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. Many think they are Secured data. Guess someone from Oracle confirms.
 _V
Tables are the views created on base tables
 _VL
Views for multi language tables which combines the row of the base table with the corresponding row of the _TL table where the LANGUAGE = USERENV('LANG').
 _S
Sequences, used for finding new values for the primary key of a table.
 _A
Audit Shadow Tables
 _AVN
Audit Shadow Views
 _ACN
Audit Shadow Views
 _MRC_V
MRC (Multiple Reporting Currency) is supported by the following Oracle Applications - Oracle Assets,Oracle Cash Management, Oracle Cost Management,  Oracle General Ledger, Oracle Global Accounting Engine, Oracle Payables, Oracle Receivables, Oracle Purchasing, Oracle Projects

Source: rafi-oracle

Comments

Post a Comment

Popular posts from this blog

Oracle Fusion : SQL Query to Retrieve Shopping Category Hierarcy

-
You can use below SQL query to list down all shopping cateogry hierarcy (both browsing and purchasing ones) and description for English and Turkish languages. Please feel free to contact me if you relaize any mistake. SELECT prct.CATEGORY_NAME PARENT_CATEGORY_NAME_TR , prce.CATEGORY_NAME PARENT_CATEGORY_NAME_US , pch.PURCHASING_CAT_FLAG , CASE WHEN pch.PURCHASING_CAT_FLAG = 'Y' THEN ( SELECT ect.CATEGORY_NAME FROM EGP_CATEGORIES_TL ect WHERE pch.child_category_id = ect.category_id AND ect.language = 'TR' ) ELSE ( SELECT prct.CATEGORY_NAME FROM POR_BROWSE
Read more

Automatic Generation of Charge Account in Requisition Import

-
Requisition Import process is used to import requisitions from other Oracle or third-party non-Oracle systems. Before R12.2.2,  while importing requisitions from Oracle or third-party non-Oracle systems, if users do not provide charge account segment or CCID for other accounts in the Requisitions Interface table (PO_REQUISITIONS_INTERFACE), then these requisitions are not imported. The interface expects the accounts (charge, budget, variance, and accrual) as mandatory fields and does not process requisitions unless the charge account is populated. With this new feature, when requisitions are imported using the Requisition Import Process, the Charge, Budget, Variance and Accrual accounts for the requisitions are generated automatically by calling the Requisition Account Generator Workflow. Automatic generation of the charge account CCID happens only if the charge account and corresponding segments are empty. You can check following document to get more information. Auto
Read more