Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Description
MTL_PARAMETERS
MTL_SYSTEM_ITEMS_B
MTL_ITEM_STATUS
MTL_UNITS_OF_MEASURE_TL
MTL_ITEM_LOCATIONS
MTL_ITEM_CATEGORIES
MTL_CATEGORIES_B
MTL_CATEGORY_SETS_B
MTL_DEMAND
MTL_SECONDARY_INVENTORIES
MTL_ONHAND_QUANTITIES
MTL_TRANSACTION_TYPES
MTL_MATERIAL_TRANSACTIONS
MTL_ITEM_ATTRIBUTES
MTL_ITEM_CATALOG_GROUPS_B
MTL_ITEM_REVISIONS_B
MTL_ITEM_TEMPLATES_B
MTL_DESCRIPTIVE_ELEMENTS
Table
PA_PROJECTS_ALL
Description
It stores the highest units of work defined in Oracle
Projects.
PA_PROJECT_ASSETS_ALL
It contains assets information defined for capital
projects.
PA_PROJECT_ASSIGNMENTS
It stores details of all Assignments for a project.
PA_PROJECT_CLASSES
It contains the class codes of class categories that are
used to classify projects.
PA_PROJECT_ROLE_TYPES
Implementation-defined responsibilities or positions
assigned to employees on projects are stored here.
PA_PROJECT_STATUSES
It stores valid project status codes.
PA_PROJECT_TYPES_ALL
It stores implementation-defined project classifications
that supply default information and drive some project
processing.
PA_TASKS
It contains user-defined subdivisions of project work.
PA_TASK_TYPES
It stores implementation-defined classifications of
task.
PA_TRANSACTION_INTERFACE_ALL It is an interface table to import transactions from
external sources into Oracle Projects.
PA_TRANSACTION_SOURCES
It stores implementation-defined sources of imported
transactions originating in an external system.
PA_IMPLEMENTATIONS_ALL
It contains information about the configuration of an
Oracle Projects installation.
PA_ACTION_SETS
It stores action set templates as well as action sets
belonging to an object, such as projects, requirements,
etc.
PA_ACTION_SET_LINES
It stores action set lines that belong to an action set or
an action set template.
PA_ACTION_SET_TYPES
It stores attributes of action set types.
PA_AGREEMENTS_ALL
It has customer contracts that serve as the basis for
work authorization.
PA_AGREEMENT_TYPES
Implementation-defined classifications of customer
agreements.
PA_BILL_RATES_ALL
Information about bill rates and markups of standard
bill rate schedules.
PA_BUDGETS
It stores budgets information.
PA_BUDGET_LINES
It stores detail lines of project and task budgets.
PA_BUDGET_TYPES
It contains implementation-defined classifications of
types of budgets used for different business purposes.
PA_CLASS_CATEGORIES
It stores implementation-defined categories for
classifying projects.
PA_CLASS_CODES
It stores implementation-defined values within class
categories that can be used to classify projects.
PA_EVENTS
GL Tables
GL Tables
General Ledger tables can be grossly classified into following 5 categories. Here are few
important tables in each category.
Ledgers Tables:
GL_LEDGERS: Stores information about the ledgers defined in the Accounting Setup
Manager and the ledger sets defined in the Ledger Set form. Each row includes the ledger or
ledger set name, short name, description, ledger currency, calendar, period type, chart of
accounts, and other information.
GL_CODE_COMBINATIONS: Stores valid account combinations for each Accounting
Flexfield structure within your Oracle General Ledger application.
Period Tables:
GL_PERIODS: Stores information about the accounting periods you define using the
Accounting Calendar form.
GL_PERIOD_SETS: Stores the calendars you define using the Accounting Calendar
form.
GL_PERIOD_TYPES: Stores the period types you define using the Period Types form.
Each row includes the period type name, the number of periods per fiscal year, and other
information.
Journal Tables:
GL_JE_BATCHES: Stores journal entry batches. Each row includes the batch name,
description, status, running total debits and credits, and other information.
GL_JE_HEADERS: Stores journal entries. There is a one-to-many relationship between
journal entry batches and journal entries. Each row in this table includes the associated
batch ID, the journal entry name and description, and other information about the journal
entry.
GL_JE_LINES: Stores the journal entry lines that you enter in the Enter Journals form.
There is a one-to-many relationship between journal entries and journal entry lines. Each
row in this table stores the associated journal entry header ID, the line number, the
associated code combination ID, and the debits or credits associated with the journal line.
GL_JE_SOURCES: Stores journal entry source names and descriptions. Each journal
entry in your Oracle General Ledger application is assigned a source name to indicate how it
was created. This table corresponds to the Journal Sources form.
GL_JE_CATEGORIES: Stores journal entry categories. Each row includes the category
name and description.
Budgeting tables:
GL_BUDGET_TYPES: Stores information about budget types. Oracle General Ledger
supports only one budget type, STANDARD. Therefore, this table always contains only one
row.
GL_BUDGET_ASSIGNMENTS: Stores the accounts that are assigned to each budget
organization. Each row includes the currency assigned to the account and the entry code for
the account. The entry code is either E for entered or C for calculated. This table
corresponds to the Account Assignments window of the Define Budget Organization form.
GL_BUDGET_INTERIM: It is used internally by Oracle General Ledger applications to
post budget balances to the GL_BALANCES table. Rows are added to this table whenever
you run the budget posting program. The budget posting program updates the appropriate
budget balances in GL_BALANCES based on the rows in this table, and then deletes the
rows in this table that it used.
Interface Tables:
GL_INTERFACE: It is used to import journal entry batches through Journal Import. You
insert rows in this table and then use the Import Journals window to create journal batches.
The supplier name, legal identifiers of the supplier will be stored in TCA and a
reference to the party created in TCA will be stored in AP_SUPPLIERS.PARTY_ID, to
link the party record in TCA.
AP_SUPPLIER_SITES_ALL:
There is a row for unique combination of supplier address, operating unit and the
business relationship that you have with the supplier.
The supplier address information is not maintained in this table and is maintained in
TCA. The reference to the internal identifier of address in TCA will be stored in
AP_SUPPLIER_SITES_ALL.LOCATION_ID, to link the address record in TCA.
Each row includes the supplier reference, purchasing, invoice, and general
information.
AP_INVOICES_ALL:
An invoice can have one or more invoice distribution lines and can have one or more
scheduled payments.
AP_INVOICE_LINES_ALL:
An invoice line should contain all the attributes that are present on the physical or
electronic invoice presented by the supplier.
AP_INVOICE_DISTRIBUTIONS_ALL:
There is one row for each invoice distribution and a distribution must be associated
with an invoice.
There is one row for each payment you make for each invoice and there is one
payment and one invoice for each payment in this table.
Oracle Payables application updates this table when you confirm an automatic
payment batch, enter a manual payment, or process a Quick payment.
When you void a payment, your Oracle Payables inserts an additional payment line
that is the negative of the original payment line.
AP_PAYMENT_SCHEDULES_ALL:
The table contains a row for each future dated payment, once the future dated
payment matures, i.e. becomes negotiable.
Any time a payment is cleared or uncleared, a row is inserted into this table for the
payment.
AP_BATCHES_ALL:
It contains summary information about invoices you enter in batches if you enable
the Batch Control Payables option.
If you enable Batch Control, each invoice must correspond to a record in this table.
Your Oracle Payables application uses this information to group together invoices
that one person entered in a batch.
AP_CHECKS_ALL:
There is one row for each payment you issue to a supplier or refund received from a
supplier.
Oracle Payables application uses this information to record payments you make to
suppliers or refunds you receive from suppliers.
Oracle Payables application stores the supplier name and bank account name for
auditing purposes, in case either one is changed after you create the payment. Oracle
Payables application also stores address information for all payments.
AP_HOLDS_ALL:
It contains information about holds that you or your Oracle Payables application
place on an invoice.
For non-matching holds, there is one row for each hold placed on an invoice. For
matching holds, there is one row for each hold placed on an invoice-shipment match.
An invoice may have one or more corresponding rows in this table.
Your Oracle Payables application does not pay invoices that have one or more
unreleased holds recorded in this table.
AP_BANK_ACCOUNTS_ALL:
There is one row for each bank account you define and each bank account must be
affiliated with one bank branch.
AP_BANK_ACCOUNT_USES_ALL:
It stores information for the internal and external bank accounts you define in Oracle
Payables and Oracle Receivables applications.
AP_CARDS_ALL:
It stores information about the corporate credit cards issued to your employees by
your corporate credit card providers.
AP_TRIAL_BALANCE:
PARTY_ID: Identifier for the party. Foreign key to the HZ_PARTIES table.
LOCATION_ID: Identifier for the party site. Foreign key to the HZ_LOCATIONS
table.
PARTY_SITE_NUMBER: Party site number.
PARTY_SITE_NAME: User-defined name for the site.
CITY: City
STATE: State
belong to multiple operating units. The primary key for this table is CUST_ACCT_SITE_ID.
Few Important Columns are
CUST_ACCT_SITE_ID: Identifier for the customer account site. Foreign key to the
HZ_CUST_ACCT_SITES_ALL table
SITE_USE_CODE: Business purpose assigned to customer site account, such as BillTo, Market, and Statements.
PRIMARY_FLAG: Indicates if this site is the primary site for this customer account.
Y for the primary customer account site. N for other customer account sites.
HZ_CUSTOMER_PROFILES:
The HZ_CUSTOMER_PROFILES table stores information about the credit characteristics
of a single customer account or a customer account site or a party. A profile class defined in
the
HZ_CUSTOMER_PROFILE_CLASSES table can be used to provide default values for the
attributes in this table. The primary key for this table is CUST_ACCOUNT_PROFILE_ID.
Few Important Columns are