_ALL are multi-org tables, on which org-striped views are based. Example po_headers_all and po_headers
_TL are translation 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.
_TL are translation 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.
_VL are 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').
_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. (This is also called Date Effectivity)
_B these are the BASE tables.
They are very important and the data is stored in the these 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.
_V are views.
_S are sequences.
_A are Audit Shadow Tables.
_AVn and _ACn are Audit Shadow Views (when data was changed, and with what values).
_DFV and _KFV: DFF/KFF table 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.
_X Current information table. There is no date tracking.
_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. (This is also called Date Effectivity)
_B these are the BASE tables.
They are very important and the data is stored in the these 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.
_V are views.
_S are sequences.
_A are Audit Shadow Tables.
_AVn and _ACn are Audit Shadow Views (when data was changed, and with what values).
_DFV and _KFV: DFF/KFF table 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.
_X Current information table. There is no date tracking.
No comments:
Post a Comment