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.

Conversion and consolidation tables:

GL_CONSOLIDATION: Stores information about your consolidation mappings. Each row includes a mappings ID, name,
description, and other information. This table corresponds to the first window of the Consolidation Mappings form. You need one
row for each consolidation mapping you define.
GL_CONSOLIDATION_ACCOUNTS: Stores the account ranges that you enter when you consolidate balances using the
Transfer Consolidation Data form. This table corresponds to the Account Ranges window of the Transfer Consolidation Data form.
GL_DAILY_RATES: Stores the daily conversion rates for foreign currency transactions. It replaces the
GL_DAILY_CONVERSION_RATES table. It stores the rate to use when converting between two currencies for a given conversion
date and conversion type.
GL_DAILY_BALANCES: Stores daily aggregate balances for detail and summary balance sheet accounts in sets of books with
average balances enabled.

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.
GL_INTERFACE_CONTROL: It is used to control Journal Import execution. Whenever you start Journal Import from the
Import Journals form, a row is inserted into this table for each source and group id that you specified. When Journal Import
completes, it deletes these rows from the table.
GL_BUDGET_INTERFACE: It is used to upload budget data into your Oracle General Ledger application from a spreadsheet
program or other external source. Each row includes one fiscal years worth of budget amounts for an account.

AP_SUPPLIERS:

This table replaces the old PO_VENDORS table.

It stores information about your supplier level attributes.

Each row includes the purchasing, receiving, invoice, tax, classification, and general information.

Oracle Purchasing uses this information to determine active suppliers.

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:
This table replaces the old PO_VENDOR_SITES_ALL table.

It stores information about your supplier site level attributes.

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:
It contains records for invoices you enter.

There is one row for each invoice you enter.

An invoice can have one or more invoice distribution lines and can have one or more scheduled payments.

AP_INVOICE_LINES_ALL:
It contains records for invoice lines entered manually, generated automatically or imported from the Open Interface.

An invoice can have one or more invoice lines.

An invoice line represents goods (direct or indirect materials), service(s), and/or associated tax/freight/miscellaneous
charges invoiced from a supplier.

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:
It holds the distribution information that is manually entered or system-generated.

There is one row for each invoice distribution and a distribution must be associated with an invoice.

An invoice can have multiple distributions.

AP_INVOICE_PAYMENTS_ALL:
It contains records of invoice payments that you made to suppliers.

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:
This table stores information about scheduled payment information on invoices.

AP_PAYMENT_HISTORY_ALL:
It stores the clearing/unclearing history for payments.

It also stores the maturity history for future dated payments.

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.

There is one row for each batch of invoices you enter.

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:
It stores information about payments issued to suppliers or refunds received from suppliers.

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:
It contains information about your bank accounts.
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:
It contains denormalized information about invoices and payments posted to the accrual set of books.
Filed under Apps Tables, Payables Tagged with account payables, AP, apps tables, Oracle Apps, Oracle E-Business Suite

Oracle Apps Receivables (AR) Tables

Transactions
RA_CUSTOMER_TRX_ALL

Transaction
Header table

Transaction
RA_CUSTOMER_TRX_LINES_A Lines table
LL
along with Tax
lines.
Distribution
RA_CUST_TRX_LINE_GL_DIST for
_ALL
Transaction
Lines
Salesrep
information
RA_CUST_TRX_LINE_SALESR
for
EPS_ALL
Transaction
Lines

Transaction Interface

Tables
RA_INTERFACE_LINES_ALL

Transaction
Lines interface

Transaction
RA_INTERFACE_SALESCREDI
Sales credit
TS_ALL
information
Transaction
RA_INTERFACE_DISTRIBUTIO
Distribution
NS_ALL
information
RA_INTERFACE_ERRORS_ALL

Transaction
errors table

Interface table
AR_PAYMENTS_INTERFACE_A
to import
LL
receipts
Lockbox
transfers the
receipts that
AR_INTERIM_CASH_RECEIPTS
pass
_ALL
validation to
the interim
tables
Lockbox
transfers the
receipts that
AR_INTERIM_CASH_RCPT_LIN
pass
ES_ALL
validation to
the interim
tables

Receipts tables
AR_CASH_RECEIPTS_ALL

Cash Receipt
Header tables

stores Receipt
AR_RECEIVABLE_APPLICATIO
Application
NS_ALL
details
AR_PAYMENT_SCHEDULES_A This table is
updated when

LL

an activity
occurs against
an invoice,
debit memo,
chargeback,
credit memo,
on-account
credit, bills
receivable

This table
stores all of
the activity
that is
contained for
the life cycle
of a receipt.
Each row
represents
one step.
The status
AR_CASH_RECEIPT_HISTORY
field for that
_ALL
row tells you
which step the
receipt has
reached.
Possible
statuses are
Approved,
Confirmed,
Remitted,
Cleared, and
Reversed.

Customer Tables

HZ_PARTIES

HZ_CUST_ACCOUNTS

A party is an
entity that can
enter into a
business
relationship.
This table
stores

information
about
customer/fina
ncial
relationships
established
between a
Party and the
deploying
company.

HZ_PARTY_SITES

This table
links a party
(HZ_PARTIES)
and a location
(HZ_LOCATION
S) and stores
locationSpecific party
information
such as a
persons mail
stops at their
work address.

HZ_CUST_ACCT_SITES_ALL

This table
stores
information
about
customer/fina
ncial account
sites
information.

HZ_CUST_SITE_USES_ALL

This table
stores
information
about the
business
purposes
assigned to a
customer
account site

HZ_LOCATIONS

A location is a
point in
geographical
space
described by
an address
and/or
geographical
Indicators
such as
latitude or
longitude.

Setup tables

RA_CUST_TRX_TYPES_ALL

This table
stores
information
about each
transaction
type for all
classes of
transactions,
for example,
invoices,
commitments,
and credit
memos.

AR_RECEIPT_CLASSES

This table
stores the
different
receipt classes
that you
define.

AR_RECEIPT_METHODS

This table
stores
information
about
Payment
Methods,
receipt
attributes that

you define
and assign to
Receipt
Classes to
account for
receipts and
their
applications