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.

Conversion and consolidation tables:

GL_CONSOLIDATION: Stores information about your consolidation mappings. Each row

includes a mapping’s 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 year’s worth of budget amounts for an account.

GL_ACCOUNT_HIERARCHIES stores lists of the detail accounts associated with each summary account. When you create a summary account, the list of its detail accounts is stored in this table, one detail account per row. This table stores one such list for each summary account. GL_ALLOC_BATCHES stores information about MassAllocation and MassBudget batches. Each row includes a batch’s unique ID, name, status, and description. This table corresponds to the Define MassAllocations and Define MassBudget windows of the Define MassAllocations and Define MassBudgets forms. GL_ALLOC_FORMULAS stores information about MassAllocation and MassBudget formulas. GL_ALLOC_FORMULA_LINES stores information about MassAllocation and MassBudget formula lines. This table corresponds to the Formula window of the Define MassAllocations and Define MassBudgets forms. There are four or five lines associated with each MassBudget formula, and there are five lines associated with each MassAllocation formula. GL_ALLOC_HISTORY stores one row for each batch produced by generating MassAllocation and MassBudget journals. Use information in this table to determine when you generated your MassAllocation and MassBudget journals, and for which accounting periods. GL_BALANCES stores actual, budget, and encumbrance balances for detail and summary accounts. This table stores functional currency, foreign currency, and statistical balances for each accounting period that has ever been opened. GL_BUDGETS stores information about your budgets. Each row includes a budget’s name, first and last periods, date created, and status. This table corresponds to the Define Budget form. Oracle General Ledger supports only one budget type (’STANDARD’), so you can uniquely identify a row with only the budget name. The CURRENT_VERSION_ID column is not currently used. GL_BUDGET_ASSIGNMENTS stores the accounts that are assigned to each budget organization. GL_BUDGET_ASSIGNMENT_RANGES stores the account ranges that you want to assign to a budget organization.

GL_DAILY_RATES_INTERFACE is the interface you use to create, update, and delete daily conversion rates. Customers should use this table to load rates into the GL_DAILY_RATES table. Foreign KeysPrimary Key Table Primary Key Column Foreign Key Column FND_CURRENCIES CURRENCY_CODE FROM_CURRENCY FND_CURRENCIES CURRENCY_CODE TO_CURRENCY FND_USER USER_ID USER_ID GL_DAILY_CONVERSION_TYPES USER_CONVERSION_TYPE USER_CONVERSION_TYPE Not null columns FROM_CURRENCY TO_CURRENCY FROM_CONVERSION_DATE TO_CONVERSION_DATE USER_CONVERSION_TYPE CONVERSION_RATE MODE_FLAG GL_IEA_INTERFACE is used to import data into the Global Intercompany System from external systems. The data entered into this table is processed by the GIS Import program. Foreign Keys Primary Key Table Primary Key Column Foreign Key Column FND_CONCURRENT _REQUESTS REQUEST_ID REQUEST_ID FND_CURRENCIES CURRENCY_CODE CURRENCY_CODE GL_CODE_COMBINATIONS CODE_COMBINATION_ID SENDER_CODE_COMBINATION_ID GL_CODE_COMBINATIONS CODE_COMBINATION_ID SENDER_CODE_COMBINATION_ID GL_IEA_SUBSIDIARIES SUBSIDIARY_ID SENDER_SUBSIDIARY_ID GL_IEA_SUBSIDIARIES SUBSIDIARY_ID RECEIVER_SUBSIDIARY_ID GL_IEA_TRANSACTION_TYPES TRANSACTION_TYPE_ID TRANSACTION_TYPE_ID NOT NULL Columns GROUP_ID TRANSACTION_TYPE_ID TRANSACTION_STATUS_CODE CURRENCY_CODE GL_DATE SENDER_SUBSIDIARY_ID RECEIVER_SUBSIDIARY_ID LINE_TYPE GL_INTERFACE is the table you use to import journal entry batches through Journal Import. You insert rows in this table and then use the Import Journals form to create journal batches. You must supply values for all NOT NULL columns.

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.

Conversion and consolidation tables: GL_CONSOLIDATION: Stores information about your consolidation mappings. Each row includes a mapping’s 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 year’s worth of budget amounts for an account.

PAYABLES TABLES

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.

HZ(TCA) tables in Oracle Receivables

This article describes few important HZ tables in AR and their relationships with each other.

HZ_PARTIES:

The HZ_PARTIES table stores basic information about parties that can be shared with any relationship that the party might

establish with another party. The primary key for this table is PARTY_ID.

Few Important Columns are

PARTY_ID: Party identifier

PARTY_NUMBER: Unique identification number for this party

PARTY_NAME: Name of the party

PARTY_TYPE: The party type can only be Person, Organization, Group or Relationship.

HZ_PARTY_SITES:

The HZ_PARTY_SITES table links a party (HZ_PARTIES) and a location (HZ_LOCATIONS) and stores location-specific

party information. One party can optionally have one or more party sites. One location can optionally be used by one or

more parties. The primary key for this table is PARTY_SITE_ID.

Few Important Columns are

PARTY_SITE_ID: Party site identifier.

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.

ADDRESSEE: Addressee information.

HZ_LOCATIONS:

The HZ_LOCATIONS table stores information about a delivery or postal address such as building number, street address,

postal code, and directions to a location. This table provides physical location information about parties (organizations and

people) and customer accounts. The primary key for this table is LOCATION_ID.

Few Important Columns are

LOCATION_ID: Unique identifier for this location

COUNTRY: Country code from the TERRITORY_CODE column in the FND_TERRITORY table

ADDRESS1: First line for address

ADDRESS2: Second line for address

ADDRESS3: Third line for address

ADDRESS4: Fourth line for address

CITY: City

POSTAL_CODE: Postal Code

STATE: State

ADDRESS_KEY: Derived key that facilitates fuzzy searches

HZ_CUST_ACCOUNTS:

The HZ_CUST_ACCOUNTS table stores information about customer accounts , or business relationships that the deploying

company establishes with a party of type Organization or Person. This table focuses on business relationships and how

transactions are conducted in the relationship. Since a party can have multiple customer accounts, this table might contain

several records for a single party. For example, an individual person can establish a personal account, family account, and a

professional account for a consulting practice. The primary key for this table is CUST_ACCOUNT_ID.

Few Important Columns are

CUST_ACCOUNT_ID: Customer account identifier

PARTY_ID: A foreign key to the HZ_PARTY table.

ACCOUNT_NUMBER: Account Number

CUSTOMER_TYPE: Receivables lookup code for the CUSTOMER_TYPE attribute. I for internal customers, R

for revenue generating external customers.

CUSTOMER_CLASS_CODE: Customer class identifier

HZ_CUST_ACCT_SITES_ALL:

The HZ_CUST_ACCT_SITES_ALL table stores all customer account sites across all operating units. Customer account

sites are addresses, for customer accounts, where the deploying company does business with its customers. One customer

account can have multiple customer account sites, and customer account sites for one customer account can belong to

multiple operating units. The primary key for this table is CUST_ACCT_SITE_ID.

Few Important Columns are

CUST_ACCT_SITE_ID: Customer site identifier

CUST_ACCOUNT_ID: Identifier for a customer account. Foreign key to the HZ_CUST_ACCOUNTS table

PARTY_SITE_ID: Identifier for a party site. Foreign key to the HZ_PARTY_SITES table

BILL_TO_FLAG: Indicates if this is a Bill-To site.

SHIP_TO_FLAG: Indicates if this is a Ship-To site.

MARKET_FLAG: Indicates if this is a Marketing site.

HZ_CUST_SITE_USES_ALL:

The HZ_CUST_SITE_USES_ALL table stores business purposes assigned to customer account sites, for example Bill-To,

Ship-To, and Statements. Each customer account site can have one or more purposes. This table is a child of the

HZ_CUST_ACCT_SITES_ALL table, with the foreign

key CUST_ACCT_SITE_ID. The HZ_CUST_SITE_USES_ALL table also stores operating unit identifier, though the

HZ_CUST_ACCT_SITES_ALL table itself stores the operating unit for customer account sites. The primary key for this table

is SITE_USE_ID.

Few Important Columns are

SITE_USE_ID: Site use identifier

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 Bill-To, 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

CUST_ACCOUNT_PROFILE_ID: Unique identifier of this customer profile

CUST_ACCOUNT_ID: Identifier for the Customer Account. Foreign key to the HZ_CUST_ACCOUNTS table.

STATUS: Indicates whether the profile is active or inactive

HZ_CUST_PROFILE_CLASSES:

The HZ_CUST_PROFILE_CLASSES table stores information about the credit characteristics that are common across a

group of customer accounts. The characteristics specified in this table can be used as default characteristics for similar

customer accounts. The primary key for this table is PROFILE_CLASS_ID.

KEY FND TABLES IN ORACLE APPLICATION

Here there are few key FND tables that we use in our AOL queries.

FND_APPLICATION:

Stores applications registered with Oracle Application Object Library.

FND_APPLICATION_TL:

Stores translated information about all the applications registered with Oracle Application Object Library.

FND_APP_SERVERS:

This table will track the servers used by the E-Business Suite system.

FND_ATTACHED_DOCUMENTS:

Stores information relating a document to an application entity.

FND_CONCURRENT_PROCESSES:

Stores information about concurrent managers.

FND_CONCURRENT_PROCESSORS:

Stores information about immediate (subroutine) concurrent program libraries.

FND_CONCURRENT_PROGRAMS:

Stores information about concurrent programs. Each row includes a name and description of the concurrent program.

FND_CONCURRENT_PROGRAMS_TL:

Stores translated information about concurrent programs in each of the installed languages.

FND_CONCURRENT_QUEUES:

Stores information about concurrent managers.

FND_CONCURRENT_QUEUE_SIZE:

Stores information about the number of requests a concurrent manager can process at once, according to its work shift.

FND_CONCURRENT_REQUESTS:

Stores information about individual concurrent requests.

FND_CONCURRENT_REQUEST_CLASS:

Stores information about concurrent request types.

FND_CONC_REQ_OUTPUTS:

This table stores output files created by Concurrent Request.

FND_CURRENCIES:

Stores information about currencies.

FND_DATABASES:

It tracks the databases employed by the eBusiness suite. This table stores information about the database that is not

instance specific.

FND_DATABASE_INSTANCES:

Stores instance specific information. Every database has one or more instance.

FND_DESCRIPTIVE_FLEXS:

Stores setup information about descriptive flexfields.

FND_DESCRIPTIVE_FLEXS_TL:

Stores translated setup information about descriptive flexfields.

FND_DOCUMENTS:

Stores language-independent information about a document.

FND_EXECUTABLES:

Stores information about concurrent program executables.

FND_FLEX_VALUES:

Stores valid values for key and descriptive flexfield segments.

FND_FLEX_VALUE_SETS:

Stores information about the value sets used by both key and descriptive flexfields.

FND_LANGUAGES:

Stores information regarding languages and dialects.

FND_MENUS:

It lists the menus that appear in the Navigate Window, as determined by the System Administrator when defining

responsibilities for function security.

FND_MENUS_TL:

Stores translated information about the menus in FND_MENUS.

FND_MENU_ENTRIES:

Stores information about individual entries in the menus in FND_MENUS.

FND_PROFILE_OPTIONS:

Stores information about user profile options.

FND_REQUEST_GROUPS:

Stores information about report security groups.

FND_REQUEST_SETS:

Stores information about report sets.

FND_RESPONSIBILITY:

Stores information about responsibilities. Each row includes the name and description of the responsibility, the application it

belongs to, and values that identify the main menu, and the first form that it uses.

FND_RESPONSIBILITY_TL:

Stores translated information about responsibilities.

FND_RESP_FUNCTIONS:

Stores security exclusion rules for function security menus. Security exclusion rules are lists of functions and menus

inaccessible to a particular responsibility.

FND_SECURITY_GROUPS:

Stores information about security groups used to partition data in a Service Bureau architecture.

FND_SEQUENCES:

Stores information about the registered sequences in your applications.

FND_TABLES:

Stores information about the registered tables in your applications.

FND_TERRITORIES:

Stores information for countries, alternatively known as territories.

FND_USER:

Stores information about application users.

FND_VIEWS:

Stores information about the registered views in your applications.

fnd tables Useful Fnd tables

fnd_concurrent_queues

fnd_concurrent_programs

fnd_concurrent_requests

fnd_concurrent_processes

fnd_concurrent_queue_size

fnd_appl_tops

fnd_logins

fnd_user

fnd_user_resp_groups

fnd_executables

fnd_lookups

fnd_dm_nodes

fnd_tns_aliases

fnd_nodes

fnd_responsibility

fnd_databases

fnd_unsuccessful_logins

fnd_languages

fnd_application

fnd_profile_option_values

Few Important AP Tables

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.

HZ(TCA) tables in Oracle Receivables

This article describes few important HZ tables in AR and their relationships with each other.

HZ_PARTIES:

The HZ_PARTIES table stores basic information about parties that can be shared with any

relationship that the party might establish with another party. The primary key for this table

is PARTY_ID.

Few Important Columns are

PARTY_ID: Party identifier

PARTY_NUMBER: Unique identification number for this party

PARTY_NAME: Name of the party

PARTY_TYPE: The party type can only be Person, Organization, Group or

Relationship.

HZ_PARTY_SITES:

The HZ_PARTY_SITES table links a party (HZ_PARTIES) and a location

(HZ_LOCATIONS) and stores location-specific party information. One party can optionally

have one or more party sites. One location can optionally be used by one or more parties.

The primary key for this table is PARTY_SITE_ID.

Few Important Columns are

PARTY_SITE_ID: Party site identifier.

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.

ADDRESSEE: Addressee information.

HZ_LOCATIONS:

The HZ_LOCATIONS table stores information about a delivery or postal address such as

building number, street address, postal code, and directions to a location. This table

provides physical location information about parties (organizations and people) and

customer accounts. The primary key for this table is LOCATION_ID.

Few Important Columns are

LOCATION_ID: Unique identifier for this location

COUNTRY: Country code from the TERRITORY_CODE column in the

FND_TERRITORY table

ADDRESS1: First line for address

ADDRESS2: Second line for address

ADDRESS3: Third line for address

ADDRESS4: Fourth line for address

CITY: City

POSTAL_CODE: Postal Code

STATE: State

ADDRESS_KEY: Derived key that facilitates fuzzy searches

HZ_CUST_ACCOUNTS:

The HZ_CUST_ACCOUNTS table stores information about customer accounts , or

business relationships that the deploying company establishes with a party of type

Organization or Person. This table focuses on business relationships and how transactions

are conducted in the relationship. Since a party can have multiple customer accounts, this

table might contain several records for a single party. For example, an individual person can

establish a personal account, family account, and a professional account for a consulting

practice. The primary key for this table is CUST_ACCOUNT_ID.

Few Important Columns are

CUST_ACCOUNT_ID: Customer account identifier

PARTY_ID: A foreign key to the HZ_PARTY table.

ACCOUNT_NUMBER: Account Number

CUSTOMER_TYPE: Receivables lookup code for the CUSTOMER_TYPE attribute.

I for internal customers, R for revenue generating external customers.

CUSTOMER_CLASS_CODE: Customer class identifier

HZ_CUST_ACCT_SITES_ALL:

The HZ_CUST_ACCT_SITES_ALL table stores all customer account sites across all

operating units. Customer account sites are addresses, for customer accounts, where the

deploying company does business with its customers. One customer account can have

multiple customer account sites, and customer account sites for one customer account can

belong to multiple operating units. The primary key for this table is CUST_ACCT_SITE_ID.

Few Important Columns are

CUST_ACCT_SITE_ID: Customer site identifier

CUST_ACCOUNT_ID: Identifier for a customer account. Foreign key to the

HZ_CUST_ACCOUNTS table

PARTY_SITE_ID: Identifier for a party site. Foreign key to the HZ_PARTY_SITES

table

BILL_TO_FLAG: Indicates if this is a Bill-To site.

SHIP_TO_FLAG: Indicates if this is a Ship-To site.

MARKET_FLAG: Indicates if this is a Marketing site.

HZ_CUST_SITE_USES_ALL:

The HZ_CUST_SITE_USES_ALL table stores business purposes assigned to customer

account sites, for example Bill-To, Ship-To, and Statements. Each customer account site

can have one or more purposes. This table is a child of the HZ_CUST_ACCT_SITES_ALL

table, with the foreign

key CUST_ACCT_SITE_ID. The HZ_CUST_SITE_USES_ALL table also stores operating

unit identifier, though the HZ_CUST_ACCT_SITES_ALL table itself stores the operating unit

for customer account sites. The primary key for this table is SITE_USE_ID.

Few Important Columns are

SITE_USE_ID: Site use identifier

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

Bill-To, 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

CUST_ACCOUNT_PROFILE_ID: Unique identifier of this customer profile

CUST_ACCOUNT_ID: Identifier for the Customer Account. Foreign key to the

HZ_CUST_ACCOUNTS table.

STATUS: Indicates whether the profile is active or inactive

HZ_CUST_PROFILE_CLASSES:

The HZ_CUST_PROFILE_CLASSES table stores information about the credit

characteristics that are common across a group of customer accounts. The characteristics

specified in this table can be used as default characteristics for similar customer accounts.

The primary key for this table is PROFILE_CLASS_ID.

HZ_PARTY_RELATIONSHIPS:

The HZ_PARTY_RELATIONSHIPS table stores information about relationships between

parties.

Relationship between the tables

Important tables in AP modules

Invoice Table-

1. AP_Invoices_Batch.

2. Ap_Invoices_All

3. Ap_invoces_lines_all.

4. Ap_invoices_Distributions_All.

Supplier Table

1. PO_Vendors.

2. PO_Vendor_Sites_All.

3. PO_vendor_Contacts.

Interface Table: - Ap_Suppliers_int. AP_supplier_sites_int, AP_supplier_site_contact_int

Payment Table

1. AP_invoices_payment.

2. Ap_Inv_Selection_criteria_all.

3. AP_checks_All

Accounting Table

1. Ap_Accounting Events

2. Ap_ae_headers_All.

3. Ap_ae_Lins_All.

Payment terms table

1. Ap_terms.

2. Ap_trms_line

Hold_Tables

1. Ap_hold.

2. Ap_hold_lines.

3. Ap_realease

Tolerance table

1. Ap_tolrance.

Reporting Table

2. AP_reporting_ntities

3. Ap_reporting_entities_lines

Distribution Set Table

1. Ap_Distribution_Sets

2. AP_Distribution_Set_lines_all.

Bank table

1. Ap_Bannks_Branches_All.

2. Ap_Bank_Accounts_All

3. Ap_Bank_Account_Uses_All

AP_ACCOUNTING_EVENTS_ALL

An event is an entity whose role is to map transaction data to the accounting created for it.

Every accounting entry needs to be identified with the event that created it. Conceptually,

an event provides information about the timing and the reason for which the document

created the accounting entries. Every event will result in one, and only one, accounting

entry header in each set of books. Also, transaction data is stamped with the event that accounted for

it.

AP_AE_HEADERS_ALL

An accounting entry header is an entity grouping all accounting entry lines created for

a given accounting event and a particular set of books. An accounting entry header can

either be transferred over to GL or not at all. That is, either all its accounting entry lines are

transferred or none at all. The transferred to GL status is marked in the GL_TRANSFER_FLAG.

Possible values for GL_TRANSFER_FLAG are Y, N, or E. Y indicates that the accounting entry

header has been transferred to GL. N indicates that the accounting entry header has not been

transferred to GL due to 2 possible reasons: either the transfer process has not run or it has

run but the accounting entry had an accounting error on it. E indicates that an error was

encountered during the transfer to GL process.

AP_AE_LINES_ALL

An accounting entry line is an entity containing a proper accounting entry with debits or credits

both in transaction currency as well as functional currency along with an account and other

reference information pointing to the transaction data that originated the accounting entry line.

An accounting entry line is grouped with other accounting entry lines for a specific accounting entry

header.

Any such group of accounting entry lines should result in balanced entries in the functional currency.

AP_AGING_PERIODS

AP_AGING_PERIODS contains aging periods that you define for use in the Invoice Aging Report.

You need one row for each period you use in this report. In this table, PERIOD_NAME contains the

name you give to the aging period; it is not a reference to AP_OTHER_PERIODS or GL_PERIODS.

AP_AGING_PERIOD_LINES

AP_AGING_PERIOD_LINES contains information on individual aging periods. The Invoice Aging Report

returns data for these specific aging period lines defined in this table. Each row in this table

corresponds with a date range to which the Invoice Aging Report assigns invoices.

AP_AUD_AUDITORS

AP_AUD_AUDITORS is a Audit-specific table that stores information about auditors. The data in this

table controls which users are valid auditors. The table is shipped preseeded with a fallback auditor.

The fallback auditor is used when no other auditor is available and has auditor_id -1. The primary key

for this table is AUDITOR_ID.

AP_AWT_BUCKETS_ALL

AP_AWT_BUCKETS_ALL contains the denormalized amount of tax withheld to date for a particular

supplier site and a specific withholding tax code within each period. The period type assigned to

the withholding tax code determines the periods. There will not be a row in this table if there is

no withholding tax for this supplier site.

AP_AWT_GROUPS

AP_AWT_GROUPS contains withholding tax groups. Each withholding tax group contains one

or more withholding tax codes. This table corresponds to the Withholding Tax Groups window.

AP_AWT_GROUP_TAXES_ALL

AP_AWT_GROUP_TAXES_ALL is the intersection table that belongs to a specific withholding tax group

and refers to a specific withholding tax code. Its primary key is GROUP_ID and TAX_NAME. The same

withholding tax code cannot belong to the same withholding tax group more than once.

AP_AWT_TAX_RATES_ALL

AP_AWT_TAX_RATES_ALL contains tax rates for Withholding tax type tax codes. Oracle Payables

predefines the Standard and Penalty tax rate types for withholding taxes. In addition, Certificate rate

types are assigned to a specific supplier site and Exception rate types are assigned to a specific

invoice. START_AMOUNT and END_AMOUNT columns are only used if the parent withholding tax uses

amount ranges.

AP_AWT_TEMP_DISTRIBUTIONS_ALL

AP_AWT_TEMP_DISTRIBUTIONS_ALL contains temporary withholding tax type invoice distributions for

projected withholding tax or unconfirmed payment batches.

AP_BANK_ACCOUNTS_ALL

AP_BANK_ACCOUNTS_ALL contains information about your bank accounts. You need one row for each

bank account you define. Each bank account must be affiliated with one bank branch. When you

initiate an automatic payment batch, enter a manual check, or create a Quick payment, you can select

a bank account that you define in this table.

AP_BANK_ACCOUNT_USES_ALL

AP_BANK_ACCOUNT_USES_ALL stores information for the internal and external bank accounts you

define in Oracle Payables and Oracle Receivables applications.

AP_BANK_BRANCHES

AP_BANK_BRANCHES contains information about the bank branches you define when you set up your

banks. You need one row for each bank branch you use. One bank branch may have multiple bank

accounts.

AP_BANK_CHARGES

AP_BANK_CHARGES stores header information you enter in the Bank Charges window in Oracle

Payables or Oracle Receivables. You need one row for each bank combination you define in the Bank

Charges window. TRANSFER_PRIORITY is NULL for a record entered in Oracle Receivables, and NOT

NULL for a record entered in Oracle Payables.

AP_BANK_CHARGE_LINES

AP_BANK_CHARGE_LINES stores ranges for bank charges and tolerance limits. The range consists of

TRANS_AMOUNT_FROM and TRANS_AMOUNT_TO. The record will be uniquely identified by

BANK_CHARGE_ID,TRANS_AMOUNT_FROM, and START_DATE.

AP_BANK_TRANSMISSIONS

AP_BANK_TRANSMISSIONS stores files you send and receive when you use the Automatic Bank

Transmission feature. This table also stores information about each transmitted file. This table has one

row for each file sent or received.

AP_BATCHES_ALL

AP_BATCHES_ALL 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_CHECKRUN_CONC_PROCESSES_ALL

AP_CHECKRUN_CONC_PROCESSES_ALL is a temporary table that contains records for payment

batches with concurrent requests in process. Your Oracle Payables application creates a row in the

table for a payment batch when it submits the concurrent request for the batch. When you select a

payment batch to modify, format, confirm, cancel, or restart, the system checks if there is a record in

the table for the batch. If a record exists, the system checks the status of the concurrent request. If

the status of the request is Pending, Running, or Inactive (indicating that the request may start

running at some later time), the system does not allow you to perform any action on the payment

batch. If the concurrent request is completed, the system allows you to proceed and deletes the

existing record for the payment batch.

AP_CHECKRUN_CONFIRMATIONS_ALL

AP_CHECKRUN_CONFIRMATIONS_ALL is a temporary table that a payment batch uses during the

confirmation stage of a payment batch. There is one row for each payment status (e.g. PRINTED, SET

UP, SPOILED) you use in a payment batch. Your Oracle Payables application deletes the information

from this table when you complete a payment batch.

AP_CHECKS_ALL

AP_CHECKS_ALL stores information about payments issued to suppliers or refunds received from

suppliers. You need one row for each payment you issue to a supplier or refund received from a

supplier. Your Oracle Payables application uses this information to record payments you make to

suppliers or refunds you receive from suppliers. Your 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. Your Oracle Payables application stores address information for all payments. If you

allow changes to the supplier payment address on manual payments or Quick payments, your Oracle

Payables application maintains the new address information in this table. Your Oracle Payables

application uses BANK_ACCOUNT_NUM, BANK_NUM, and BANK_ACCOUNT_TYPE for the supplier's

bank information when you use the Electronic payment method. Your Oracle Payables application

stores a dummy value for CHECK_STOCK_ID for refunds, thus, CHECK_STOCK_ID should not be

treated as a

foreign key to AP_CHECK_STOCKS_ALL in the case of refunds.

AP_CHECK_FORMATS

AP_CHECK_FORMATS contains records for payment formats you can use to create payment

documents. You need one row for each format you use to create payments (for example, checks) to

suppliers. The table AP_PAYMENT_PROGRAMS stores payment program names that you can use to

define payment formats. Each row in this table references AP_PAYMENT_PROGRAMS either two or

three times, once in CREATE_PAYMENTS_PROGRAM_ID, once in CONFIRM_PAYMENTS_PROGRAM_ID,

and once in REMITTANCE_ADVICE_PROGRAM_ID for formats with a separate remittance advice

program.

AP_CHECK_INTEGERS

AP_CHECK_INTEGERS is a temporary table that the Missing Document Report uses to store document

numbers while it searches AP_CHECKS_ALL for gaps in the sequence of document numbers.

AP_CHECK_STOCKS_ALL

AP_CHECK_STOCKS_ALL stores information about payment documents you defined for bank accounts.

You need one row for each payment document you use to create payments for a supplier. Each record

in this table must be associated with a bank account. Each bank account corresponds with zero or

more rows in this table. When you initiate a payment batch, record a manual payment, or create a

Quick payment, you can select a payment document that you defined in this table. For a payment

document you use to create automatic payments, DISBURSEMENT_TYPE_LOOKUP_CODE must be

'COMPUTER GENERATED' or 'COMBINED.' For manual payments, it must be 'RECORDED' or

'COMBINED.' Your Oracle Payables application updates the LAST_DOCUMENT_NUM when you create

payments in an automatic payment batch, enter a manual payment, or create a Quick

payment.AP_DISTRIBUTION_SETS_ALL

AP_DISTRIBUTION_SETS_ALL contains information about Distribution Sets you define to distribute

invoices automatically. You need one row for each Distribution Set you use in your Oracle Payables

application. When you enter an invoice, you can select a Distribution Set that you define in this table.

When you select a Distribution Set for an invoice, your Oracle Payables application automatically

creates invoice distribution lines according to the lines you define for the Distribution Set you select. A

Distribution Set must have one or more Distribution Set lines.

AP_DISTRIBUTION_SET_LINES_ALL

AP_DISTRIBUTION_SET_LINES_ALL contains detailed information about individual distribution lines

you define for a Distribution Set. You need one row for each distribution line for a Distribution Set.

When you select a Distribution Set for an invoice, your Oracle Payables application uses this

information to create invoice distribution lines.A Distribution Set line must be affiliated with a single

Distribution Set. This table corresponds to the Distribution Sets window. This table has no primary

key, since your Oracle Payables application accesses its records exclusively in sets according to

DISTRIBUTION_SET_ID.

AP_DOC_SEQUENCE_AUDIT

AP_DOC_SEQUENCES_AUDIT contains audit information for document sequence numbers assigned to

invoices and payments. Document sequence numbers are used to create unique, sequential, voucher

numbers for referencing invoices and payments.Each document sequence is defined with a range of

numbers. A document sequence is assigned to a document category which, in turn, is assigned to a

document (invoice or payment) during creation.When a number for a document sequence is assigned

to an invoice or payment, your Oracle Payables application creates a row in this table for the number.

Your Oracle Payables application uses the records in this table to verify the availability of a number for

a particular document sequence before allowing the number to be assigned to a document.

AP_DUPLICATE_VENDORS_ALL

AP_DUPLICATE_VENDORS_ALL stores information about suppliers that Supplier Merge updates. The

Supplier Merge window inserts information into this table and then the Supplier Merge concurrent

process uses this information to merge suppliers

AP_ENCUMBRANCE_LINES_ALL

AP_ENCUMBRANCE_LINES_ALL stores all encumbrance entries created by Oracle Payables. It contains

one line per encumbrance entry. An encumbrance line could be created to encumber a charge, QV,

IPV, or ERV, to unencumber an entry created by PO or to reverse an encumbrance entry once the

charge, QV, IPV, or ERV becomes an actual. This table is used to transfer encumbrance over to GL, to

view encumbrance entries or to report on them. It is not updatable through the application.

AP_EXPENSE_REPORTS_ALL

AP_EXPENSE_REPORTS contains information about expense report templates you define for entering

expense reports. When you enter an expense report, you can use a list of values to select the expense

report template that you defined in this table.

AP_EXPENSE_REPORT_HEADERS_ALL

AP_EXPENSE_REPORT_HEADERS_ALL stores header information about the expense reports entered in

Oracle Payables and Oracle Self-Service Expenses. There is one row for each expense report you

enter. Your Oracle Payables application uses this information to create invoice header information

when you transfer expense reports to invoice tables. Transfer expense reports to invoice tables using

the Expense Report Import program. Your Oracle Payables application places the invoice ID in the

VOUCHNO column when you transfer an expense report. To import invoices from an external source,

Oracle recommends that you use the new Payables Open Interface tables.

AP_EXPENSE_REPORT_LINES_ALL

AP_EXPENSE_REPORT_LINES_ALL stores detailed information about expense items for individual

expense reports you enter. Your Oracle Payables application uses this information to create invoice

distributions when you import expense reports using the Expense Report Import program.

AP_EXPENSE_REPORT_PARAMS_ALL

AP_EXPENSE_REPORT_PARAMS_ALL stores accounting distribution information about expense report

types you define. You need one row for each line you want in the template for an expense report

template that you use to enter employee expense reports.

AP_HISTORY_CHECKS_ALL

AP_HISTORY_CHECKS_ALL contains summary information on invoice payments your Oracle Payables

application purges based on purge criteria you enter when you submit a purge. Your Oracle Payables

application inserts summary payment information when you confirm a purge process. Your Oracle

Payables application stores the invoice information in AP_HISTORY_INVOICES_ALL and stores the

relationships in AP_HISTORY_INVOICE_PAYMENTS_ALL.

AP_HISTORY_INVOICES_ALL

AP_HISTORY_INVOICES_ALL stores summary information of the invoices your Oracle Payables

application purges based on purge criteria you enter when you submit a purge. Your Oracle Payables

application inserts summary invoice information in this table when you confirm a purge process. Your

Oracle Payables application stores related payment information in AP_HISTORY_CHECKS and stores

the relationships in AP_HISTORY_INV_PAYMENTS.

AP_HISTORY_INV_PAYMENTS_ALL

AP_HISTORY_INVOICE_PAYMENTS_ALL stores the relationship between invoices and payments that

your Oracle Payables application purges based on purge criteria you enter when you submit a purge.

Your Oracle Payables application inserts summary payment and invoice information in this table when

you confirm a purge process. There is one row for each payment you make for an invoice. Summary

information for each payment and each invoice is stored in AP_HISTORY_CHECKS and

AP_HISTORY_INVOICES

AP_HOLDS_ALL

AP_HOLDS_ALL 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. This table holds information referenced by

the Invoice Holds window. In the strictest sense, AP_HOLDS_ALL has no primary key. It is possible for

your Oracle Payables application to place a certain type of hold on an invoice, then release it, then

place another hold of the same type (if data changes before each submission of Payables Invoice

Validation), which would result in a duplicate primary key. But for practical purposes, the primary key

is a concatenation of INVOICE_ID, LINE_LOCATION_ID, and HOLD_LOOKUP_CODE.

AP_HOLD_CODES

AP_HOLD_CODES contains information about hold codes and release codes that you or your Oracle

Payables application can place on an invoice. There is one row for each hold or release code. When

you enter or validate an invoice, you can select a hold code that you defined in this table. Your Oracle

Payables application also uses these hold codes when it places matching and tax variance holds during

Invoice Validation.Your Oracle Payables application stores translations of HOLD_LOOKUP_CODES in

the AP_LOOKUP_CODES table.

AP_INCOME_TAX_REGIONS

AP_INCOME_TAX_REGIONS contains information about the tax regions you use to record payment

information for 1099 suppliers when your organization participates in the Combined Filing Program.

Each tax region participating in the Combined Filing Program is assigned a region code, reporting limit,

and a reporting limit method which is used to determine if the payments to a 1099 supplier exceed

the region's reporting limit.When you enter a site for a 1099 supplier, you enter a tax region from this

table in the site address. Your Oracle Payables application assigns either this tax region or a default

tax region you define at the system level to each invoice distribution line for the supplier site.Your

Oracle Payables application predefines the tax regions for all U.S. States, the District of Columbia, and

some U.S. Territories. Payables has also predefined the region codes for those tax regions that are

participating in the Internal Revenue Service's Combined Filing Program. You can define additional tax

regions or you can enter region codes for existing regions.

AP_INCOME_TAX_TYPES

AP_INCOME_TAX_TYPES stores the 1099-MISC types that you can assign to a supplier for 1099

reporting. There is one row for each type you use to identify a supplier as a 1099

supplier. When you enter a supplier, you can select a 1099-MISC type if you define the supplier as

Federal Reportable.

AP_INTEREST_PERIODS

AP_INTEREST_PERIODS contains information about interest rates and periods that Payables uses to

create invoices to pay interest owed on overdue invoices. This interest is calculated in accordance with

the U.S. Prompt Payment Act.There is one row for each period for which interest accrues on an

invoice.

AP_INTERFACE_CONTROLS

AP_INTERFACE_CONTROLS is a temporary table that holds control information about segregated data

in the AP_INVOICES_INTERFACE table during the Payables Open

Interface Import. The table ensures that each import must be unique with respect to the combination

of SOURCE and GROUP_ID. This allows the submission of multiple imports at the same time. Your

Oracle Payables application deletes the information from this table when you complete an import.

AP_INTERFACE_REJECTIONS

AP_INTERFACE_REJECTIONS stores information about invoice data from the

AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE tables which could not be processed

by Payables Open Interface Import. If you use Oracle e-Commerce Gateway, you can pass information

from this table to your suppliers by submitting the Payables Open Interface Outbound Advice for

rejected data. You can purge data in this table by using the Payables Open Interface Purge.

AP_INVOICES_ALL

AP_INVOICES_ALL 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. An invoice can also have one or

more scheduled payments. An invoice of type EXPENSE REPORT must relate to a row in

AP_EXPENSE_REPORT_HEADERS_ALL unless the record has been purged from

AP_EXPENSE_REPORT_HEADERS_ALL. Your Oracle Payables application uses the INTEREST type

invoice for interest that it calculates on invoices that are overdue. Your Oracle Payables application

links the interest invoice to the original invoice by inserting the INVOICE_ID in the

AP_INVOICE_RELATIONSHIPS table.This table corresponds to the Invoices window.

AP_INVOICES_INTERFACE

AP_INVOICES_INTERFACE stores header information about invoices that you create or load for import.

Invoice data comes from sources including: EDI invoices from your suppliers that you load through

Oracle e-Commerce Gateway, supplier invoices that you transfer through the Oracle XML Gateway,

invoices that you load using Oracle SQL*Loader, lease invoices from Oracle Property Manager, lease

payments from Oracle Assets, credit card transaction data that you load using the Credit Card Invoice

Interface Summary, and invoices that you enter through the Invoice Gateway. There is one row for

each invoice you import. Your Oracle Payables application uses this information to create invoice

header information when you submit the Payables Open Interface program. AP_INVOICES_INTERFACE

contains a unique invoice ID which is used to interface with AP_INVOICES_ALL.Please refer to the

appendix of the Oracle Payables User Guide or online help for more detailed information on Open

Interface table columns, including import validation and destination columns.

AP_INVOICE_DISTRIBUTIONS_ALL

AP_INVOICE_DISTRIBUTIONS_ALL holds the distribution line information that you enter for invoices.

There is a row for each invoice distribution. A distribution line must be associated with an invoice. An

invoice can have multiple distribution lines.

Your Oracle Payables application automatically creates rows in this table when: 1) you choose a

distribution set at the invoice level 2) you import expense reports 3) you match an invoice to a

purchase order or receipt; it uses information from the matched purchase order or receipt 4) you

import invoices via the Open Interface Import process 5) you select to automatically calculate tax 6)

you select to automatically do withholding.

Each invoice distribution line has its own accounting date. When you account for an invoice, your

Oracle Payables application creates accounting events, accounting entry headers and accounting entry

lines for those distribution lines that have accounting dates included in the selected accounting date

range for the Payables Accounting Process. The accounting entries can then be transferred over to

General Ledger by running the Transfer to General Ledger process which creates journal entries.

Values for POSTED_FLAG may be Y for accounted distributions or N for distributions that have not

been accounted. Values for ACCRUAL_POSTED_FLAG may be Y if distribution has been accounted and

system is setup for accrual basis accounting or N if either distribution has not been accounted or

accrual basis accounting is not used. Values for CASH_POSTED_FLAG may be Y if distribution has been

accounted and system is set up for cash basis accounting, N if either distribution has not been

accounted or system is not setup for cash basis accounting or P if distribution has been partially

accounted in the cash set of books. The MATCH_STATUS_FLAG indicates the validationl status for the

distribution. Values for the MATCH_STATUS_FLAG can be null or N for invoice distributions that

Invoice Validation has not tested or T for distributions that have been tested or A for distributions that

have been tested and validated.Invoice distributions may be interfaced over/from Oracle Assets or

Oracle Projects. Your Oracle Payables application sets the ASSETS_ADDITION_FLAG to U for

distributions not tested by Oracle Assets; Oracle Assets then adjusts this flag after it tests a

distribution for assignment as an asset. To avoid the same invoice distribution being interfaced to both

Oracle Projects and Oracle Assets, you must interface any project-related invoice distribution to Oracle

Projects before you can interface it to Oracle Assets. If the project-related invoice distribution is

charged to a capital project in Oracle Projects, Oracle Projects sets the ASSET_ADDITION_FLAG to P

when the PA_ADDITION_FLAG is set to Y, Z or T. Oracle Assets only picks up invoice distributions with

the ASSET_ADDITION_FLAG set to U and if project-related, with the PA_ADDITION_FLAG set to Y, Z,

or T. PA_ADDITION_FLAG tracks the status of project-related supplier invoice distribution lines and

expense report distribution lines. For supplier invoice distributions entered via Oracle Payables, the

PA_ADDITION_FLAG is set to N if the distribution is project-related, otherwise it is set to E and it is

updated by Oracle Projects when the distribution is processed by the Oracle Projects Interface Supplier

Invoice process. Oracle Projects sets the PA_ADDITION_FLAG to Y or Z after the item is successfully

processed, or may be set to a rejection code if the line is rejected during transfer to Oracle Pro

AP_INVOICE_KEY_IND_ALL

AP_INVOICE_KEY_IND stores compiled invoice information for the Key Indicators Report. There is one

row for each period for which you report on invoice key indicators. The information in this table is

denormalized for reporting purposes.This table has no foreign keys.

AP_INVOICE_LINES_INTERFACE

AP_INVOICE_LINES_INTERFACE stores information used to create one or more invoice distributions.

Note that one row in this table may create, during the import process, more than one invoice

distribution. For example, if you enter a Tax line in this table and prorate it across multiple Item lines,

during Open Interface Import the system may create multiple Tax invoice distributions based on the

single Tax line in this table

AP_INVOICE_PAYMENTS_ALL

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

is one row for each payment you make for each invoice. There is one payment and one invoice for

each payment in this table. Your 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 application inserts an additional payment line that is the negative of

the original payment line. Values for POSTED_FLAG may be 'Y' for accounted payments or 'N' for

unaccounted payments. Values for ACCRUAL_POSTED_FLAG may be 'Y' for accounted payments or 'N'

for unaccounted payments under accrual basis accounting; values for SH_POSTED_FLAG

may be 'Y' for accounted payments or 'N' for unaccounted payments under cash basis accounting.

AP_INVOICE_RELATIONSHIPS

AP_INVOICE_RELATIONSHIPS relates records in AP_INVOICES_ALL with one another to match

Interest invoices with corresponding overdue invoices. If you use automatic interest calculation,

Payables creates Interest invoices to pay interest on overdue invoices. This interest is calculated in

accordance with the U.S. Prompt Payment Act.

AP_INV_APRVL_HIST_ALL

AP_INV_APRVL_HIST_ALL contains the approval and rejection history of each invoice that passes

through the Invoice Approval Workflow process. The process inserts a record for each approver

assigned to review an invoice. This table corresponds to the Invoice Approval History window.

AP_INV_SELECTION_CRITERIA_ALL

AP_INVOICE_SELECTION_CRITERIA_ALL stores the criteria that a payment batch uses to select

invoices for payment. Your Oracle Payables application creates one row each time you initiate a

payment batch. Your Oracle Payables application uses this information to guide AutoSelect in selecting

invoices for payment.AP_LIABILITY_BALANCE

AP_LIABILITY_BALANCE contains denormalized information about liability accounting entry lines

associated with invoices and payments that have been transferred to GL. The Accounts Payable Trial

Balance report uses this information to report on outstanding invoice liability.

AP_MATCHED_RECT_ADJ_ALL

A new record is added to this table each time a receipt that has been matched to by Payables is

adjusted. Each record contains the original receipt transaction identifier and the adjusted receipt

transaction identifier along with the date it was adjusted. The data in this table will be used for the

Matched and Modified Receipts Report. This table records only 'RETURN' and 'ADJUST' type

transactions in Purchasing.

AP_MC_CHECKS

AP_MC_CHECKS is a Multiple Reporting Currencies table that stores reporting currency information for

each payment in Oracle Payables. There is an optional one to many relationship between

AP_CHECKS_ALL and this table. For each payment in the AP_CHECKS_ALL table, there can be several

invoices in the AP_MC_CHECKS table with the same CHECK_ID value, but different values for

SET_OF_BOOKS_ID. The number of invoices stored in the AP_MC_CHECKS table having the same

CHECK_ID will correspond with the number of Reporting Sets of Books that have been defined.

AP_MC_INVOICES

AP_MC_INVOICES is a Multiple Reporting Currencies table that stores reporting currency information

for each invoice in Oracle Payables. There is an optional one to many relationship between

AP_INVOICES_ALL and this table. For each invoice in the AP_INVOICES_ALL table, there can be

several invoices in the AP_MC_INVOICES table with the same INVOICE_ID value, but different values

for SET_OF_BOOKS_ID. The number of invoices stored in the AP_MC_INVOICES table having the

same INVOICE_ID will correspond with the number of Reporting Sets of Books that have been defined.

AP_MC_INVOICE_DISTS

AP_MC_INVOICE_DISTS is a Multiple Reporting Currencies table that stores reporting currency

information for each invoice distribution in Oracle Payables. There is an optional one to many

relationship between AP_INVOICE_DISTRIBUTIONS_ALL and this table. For each invoice distribution in

AP_INVOICE_DISTRIBUTIONS_ALL, there can be several Invoice distributions in the

AP_MC_INVOICE_DISTS table with the same value for INVOICE_ID and

DISTRIBUTION_LINE_NUMBER, but different values for SET_OF_BOOKS_ID. The number of invoice

distributions stored in the AP_MC_INVOICE_DISTS table having the same INVOICE_ID and

DISTRIBUTION_LINE_NUMBER will correspond with the number of Reporting Sets of Books that have

been defined. There is a mandatory one to many relationship between

the AP_MC_INVOICES table and the AP_MC_INVOICE_DISTS table.

AP_MC_INVOICE_PAYMENTS

AP_MC_INVOICE_PAYMENTS is a Multiple Reporting Currencies table that stores reporting currency

information for each payment in Oracle Payables. There is an optional one to many relationship

between AP_INVOICE_PAYMENTS_ALL and this table. For each invoice in the

AP_INVOICE_PAYMENTS_ALL table, there can be several payments in the

AP_MC_INVOICE_PAYMENTS table with the same INVOICE_PAYMENT_ID value, but different values

for SET_OF_BOOKS_ID. The number of payments stored in the AP_MC_INVOICE_PAYMENTS table

having the same INVOICE_PAYMENT_ID will correspond with the number of Reporting Sets of Books

that have been defined

AP_OTHER_PERIODS

AP_OTHER_PERIODS contains information about the time periods you define for use in recurring

invoices, withholding taxes, key indicators and payment terms. Each row includes a start date and an

end date to define the length of the period. There is one row for each period you use to create key

indicators, withholding tax payments, recurring invoices or payment schedules. Your Oracle Payables

application uses this information to determine if periods are available when you define and create

recurring invoices or submit a Key Indicators report.

AP_OTHER_PERIOD_TYPES

AP_OTHER_PERIOD_TYPES stores the period type you define and use to create recurring invoice,

automatic withholding tax, key indicators and payment terms periods. You need one row for each type

of period you use to create recurring invoice, automatic withholding tax, key indicators or payment

terms periods. You must enter a row in this table before you can create rows in AP_OTHER_PERIODS.

Examples of period types are Monthly, Semi-Annual, and Quarterly. Values for MODULE may be 'KEY

INDICATORS', 'RECURRING PAYMENTS', 'AWT' or 'PAYMENT TERMS'.

AP_PAYMENT_HISTORY_ALL

AP_PAYMENT_HISTORY_ALL 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. The values for TRANSACTION_TYPE can

be PAYMENT MATURITY, PAYMENT CLEARING, or PAYMENT UNCLEARING. Each row in this table also

has the accounting status for the maturity, clearing or unclearing event.

AP_PAYMENT_KEY_IND_ALL

AP_PAYMENT_KEY_IND stores compiled payment information for the Key Indicators Report. There is

one row for each period for which you report on payment key indicators. The information in this table

is denormalized for reporting purposes

AP_PAYMENT_PROGRAMS

AP_PAYMENT_PROGRAMS stores information about payment programs that you use to define payment

formats. You need one row for each payment program you use. Your Oracle Payables application uses

this information to use the proper payment programs when you use a payment format to create

payments. Values in PROGRAM_NAME correspond to names of Pro*C, SQL*Plus, or Oracle Reports

programs. Rows in AP_CHECK_FORMATS reference rows in this table. This table corresponds to the

Automatic Payment Programs window. This table has no foreign keys.

AP_PAYMENT_SCHEDULES_ALL

AP_PAYMENT_SCHEDULES_ALL contains information about scheduled payments for an invoice. You

need one row for each time you intend to make a payment on an invoice. Your Oracle Payables

application uses this information to determine when to make payments on an invoice and how much

to pay in an automatic payment batch. Values for HOLD_FLAG may be 'Y' to place a hold on the

scheduled payment, or 'N' not to do so. Values for PAYMENT_STATUS_FLAG may be 'Y' for fully paid

payment schedules, 'N' for unpaid scheduled payments, or 'P' for partially paid scheduled payments.

For converted records, enter a value for AMOUNT_REMAINING.This table corresponds to the

Scheduled Payments window

AP_PBATCH_SETS_ALL

AP_PBATCH_SETS_ALL stores the payment batch set definitions. You need one row for each payment

batch set that you want to define. You must enter a row in this table before you can enter rows in

AP_PBATCH_SET_LINES_ALL. This table corresponds to the single-row region in Payment Batch Sets

window.

AP_PBATCH_SET_LINES_ALL

AP_PBATCH_SET_LINES_ALL stores the payment batch set lines that make up a payment batch set.

You need one row for each payment batch that you would like to be created .when you submit the

payment batch set to which the payment batch set lines belong. Payment batch set lines belonging to

a payment batch set may use the same or different bank accounts. However, they must use different

payment documents. The values from each row in this table are used to insert a row in

AP_INV_SELECTION_CRITERIA_ALL. When the payment batch set is submitted. This table corresponds

to the multi-row region in Payment Batch Sets window.

AP_PURGE_INVOICE_LIST

AP_PURGE_INVOICE_LIST is a temporary table used to store the INVOICE_IDs during the invoice

purges process. There is one row for each invoice your Oracle Payables application selects to purge

based on invoice purge criteria you enter. Your Oracle Payables application clears the records in this

table when you confirm or abort a purge process. Your Oracle Payables application stores summary

information on purged invoices and payments in AP_HISTORY_INVOICES_ALL and

AP_HISTORY_CHECKS_ALL. Your Oracle Payables application stores the status of the purge process

and statistical information on records it purges in the FINANCIALS_PURGES table.

AP_RECURRING_PAYMENTS_ALL

AP_RECURRING_PAYMENTS_ALL contains information about recurring invoices you define. You need

one row for each set of recurring invoices you arrange with a supplier. Your Oracle Payables

application uses this information to help you create recurring invoices without duplicating data entry.

Values for PAID_FLAG1 and PAID_FLAG2 may be 'Y' for Yes or 'N' for No. This table corresponds to the

Recurring Invoices window

AP_REPORTING_ENTITIES_ALL

AP_REPORTING_ENTITIES_ALL contains information about the reporting entities you define for 1099

reporting. You must define at least one reporting entity for your company or agency; however, you

can define as many reporting entities as you require to satisfy your multi-organization reporting

needs. Each tax reporting entity you define must have a unique Tax Identification Number. When you

submit your 1099 reports, you submit the reports once for each tax reporting entity you define.

AP_REPORTING_ENTITY_LINES_ALL

AP_REPORTING_ENTITY_LINES_ALL holds the line information for the tax reporting entities you

define. Each tax reporting entity must have at least one line that contains the balancing segment

value for the organization for which you perform your 1099 reporting. If you define more than one

organization for your company or agency, you can define tax reporting entities to handle your multi-

organization 1099 reporting. You use different balancing segment values to represent the different

organizations in your company or organization.You can define a reporting entity with a single

balancing segment line for each organization or you can define a reporting entity with multiple lines to

combine 1099 reporting for your organizations. For multi-organization reporting entities, you define a

different balancing segment value for each line; however, you cannot assign the same balancing

segment value to more than one reporting entity. This table corresponds to the Balancing Segment

Values region of the Reporting Entity window.

AP_REPORTING_ENTITY_LINES_ALL

AP_REPORTING_ENTITY_LINES_ALL holds the line information for the tax reporting entities you

define. Each tax reporting entity must have at least one line that contains the balancing segment

value for the organization for which you perform your 1099 reporting.If you define more than one

organization for your company or agency, you can define tax-reporting entities to handle your multi-

organization 1099 reporting. You use different balancing segment values to represent the different

organizations in your company or organization. You can define a reporting entity with a single

balancing segment line for each organization or you can define a reporting entity with multiple lines to

combine 1099 reporting for your organizations. For multi-organization reporting entities, you define a

different balancing segment value for each line; however, you cannot assign the same balancing

segment value to more than one reporting entity. This table corresponds to the Balancing Segment

Values region of the Reporting Entity window.

AP_SELECTED_INVOICES_ALL

AP_SELECTED_INVOICES_ALL is a temporary table that stores information about invoices selected for

payment in a payment batch. Your Oracle Payables application inserts into this table after you initiate

a payment batch. There will be one row for each invoice that Payables selects for payment in the

current payment batch. When you build payments in a payment batch, your Oracle Payables

application uses information in this table to create rows in AP_SELECTED_INVOICE_CHECKS.

Information from this table appears in the Modify Payment Batch window.

AP_SELECTED_INVOICE_CHECKS_ALL

AP_SELECTED_INVOICE_CHECKS_ALL is a temporary table that stores payment information during a

payment batch. Your Oracle Payables application inserts into this table when you build payments in a

payment batch. There will be one row for each payment issued during the current payment batch.

When you confirm a payment batch, your Oracle Payables application inserts these payments into

AP_CHECKS_ALL and creates a payment file. Within a payment batch, SELECTED_CHECK_ID in this

table joins with PRINT_SELECTED_CHECK_ID and PAY_SELECTED_CHECK_ID in

AP_SELECTED_INVOICES to associate a selected invoice with its payment.

AP_SUPPLIER_BALANCE_ITF

This is an interface table that stores all the records for the submission of the AP Supplier Open

Balance Letter report, as per the parameters specified by the user during the report submission.

AP_SUPPLIER_BALANCE_ITF is a denormalized table used for storing the Organization Name, Address,

Supplier and Supplier Site level information. Each row in this table stores invoice amount, payment

amount, discount taken, discount available, original prepayment amount, prepayment amount applied

to an invoice, prepayment amount remaining and the prepayment amount applied. Using this

information, the supplier open balance letter calculates the supplier open balance and publishes it in

the form of a letter.

AP_SYSTEM_PARAMETERS_ALL

AP_SYSTEM_PARAMETERS_ALL contains the parameters and defaults you define for operating your

Oracle Payables application system. This table contains information such as your set of books, your

functional currency and your default bank account and payment terms. Your Oracle Payables

application also uses this information to determine default values that cascade down to supplier and

invoice entry. This table corresponds to the Payables Options window.There is only one row in this

table. There is no primary key for this table.

AP_TAX_CODES_ALL

AP_TAX_CODES_ALL contains information about the tax codes you define. You need one row for each

tax code you want to use when entering invoices. When you enter invoices, you can use a list of

values to select a tax code defined in this table. Your Oracle Payables application also uses TAX_RATE

to calculate use tax when you enter a taxable amount for an invoice.

AP_TAX_RECVRY_RATES_ALL

AP_TAX_RECVRY_RATES_ALL is used to define tax recovery rates for each recovery rule based on the

accounting flex field, effective date range and/or supplier classification. A tax recovery rule may have

one or more tax recovery rates. A rate is defined for an accounting flex field and an effective date

range. Using the tax code, the recovery rule, and the accounting flex field range information on the

distributions of purchasing documents and supplier invoices, the appropriate tax recovery rate is

automatically defaulted

AP_TAX_RECVRY_RULES_ALL

AP_TAX_RECVRY_RULES_ALL is used to define tax recovery rules. A user can set up tax recovery rules

to determine the recoverable percentage of tax. A tax rule can be assigned to a tax code and is used

as the criteria to default a tax recovery rate on Requisitions, Purchase Orders and Releases, and

Supplier Invoices.

AP_TEMP_APPROVAL_ALL

AP_TEMP_APPROVAL_ALL is a temporary table used by your Oracle Payables application to store hold

information about invoices processed during Invoice Validation. When you submit Invoice Validation,

any holds applied or released are inserted into this table.Your Oracle Payables application then selects

from these records to produce the Invoice Validation Report.

AP_TERMS_LINES

AP_TERMS_LINES stores detail information about payment terms you define. You need one row for

each scheduled payment that you want your Oracle Payables application to create for an invoice. Split

terms have more than one row in this table. DAY_OF_MONTH columns pertain to proxima terms.

AP_TERMS_TL

AP_TERMS stores header information about payment terms you define. You need one row for each

type of terms you use to create scheduled payments for invoices. When you enter suppliers or

invoices, you can select payment terms you have defined in this table. Each terms must have one or

more terms lines.

AP_TOLERANCES_ALL

AP_TOLERANCES_ALL contains the tolerance levels you set for matching and invoice variance testing.

Your Oracle Payables application uses this information to determine during Invoice Validation whether

to hold an invoice for exceeding amounts and quantities that you actually ordered or received, or for

being taxed at significantly more or less than the proper tax rate.This table corresponds to the Invoice

Tolerances window.There is only one row in this table.

AP_TRANSMISSIONS_SETUP

AP_TRANSMISSIONS_SETUP stores information required to use the Automatic Bank Transmission

feature. Each bank can have one or more transmission codes, which provide details about transmitting

files between your system and the bank. This table has one row for each transmission code you define

AP_TRIAL_BAL

Temporary table that holds outstanding invoice balances for the Trial Balance Report

AP_TRIAL_BALANCE

AP_TRIAL_BALANCE contains denormalized information about invoices and payments posted to the

accrual set of books. The Accounts Payable Trial Balance report uses this information to report on

outstanding invoice liability. There is one row for each set of invoice distributions or payments with a

single accounting date that you post to the general ledger in a single run of the posting program.

FINANCIALS_PURGES

FINANCIALS_PURGES stores the criteria that your Oracle Payables application uses to select invoices

to purge. Your Oracle Payables application inserts one row each time you submit the purge process.

Your Oracle Payables application also stores statistical information on the number of records it deletes

from each table when you confirm an invoice purge.

Values for STATUS may be 'INITIATE', 'PRINTED', 'DELETING', 'CONFIRM', 'ABORT', 'COMPLETED-

ABORTED', and 'COMPLETED-PURGED'.This table corresponds to the Submit Purge form.

FINANCIALS_SYSTEM_PARAMS_ALL

FINANCIALS_SYSTEM_PARAMETERS_ALL contains options and defaults you share between your Oracle

Payables application, and your Oracle Purchasing and Oracle Assets applications. You can define these

options and defaults according to the way you run your business. This table corresponds to the

Financials Options window. There is only one row in this table. There is no primary key for this table.

ALL TABLES 11i & R12 PART-2

ACCOUNT RECEIVABLES

Un Changed = 498

New Tables = 118

Deleted = 53

11i TABLES R12 TABLES

1 AQ$_AR_REV_REC_QT_G AQ$_AR_REV_REC_QT_G

2 AQ$_AR_REV_REC_QT_H AQ$_AR_REV_REC_QT_H

3 AQ$_AR_REV_REC_QT_I AQ$_AR_REV_REC_QT_I

4 AQ$_AR_REV_REC_QT_S AQ$_AR_REV_REC_QT_S

5 AQ$_AR_REV_REC_QT_T AQ$_AR_REV_REC_QT_T

6 AR_ACTION_NOTIFICATIONS AR_ACTION_NOTIFICATIONS

7 AR_ADJUSTMENTS_ALL AR_ADJUSTMENTS_ALL

8 AR_ADJUSTMENTS_REP_ITF AR_ADJUSTMENTS_REP_ITF

9 AR_AE_ALLOC_REC_GT AR_AE_ALLOC_REC_GT

10 AR_AGING_BUCKET_LINES_B AR_AGING_BUCKET_LINES_B

11 AR_AGING_BUCKET_LINES_TL AR_AGING_BUCKET_LINES_TL

12 AR_AGING_BUCKETS AR_AGING_BUCKETS

13 AR_APP_RULE_DETAILS AR_APP_RULE_DETAILS

14 AR_APP_RULE_SETS AR_APP_RULE_SETS

15 AR_APP_RULES AR_APP_RULES

16 AR_APPROVAL_ACTION_HISTORY AR_APPROVAL_ACTION_HISTORY

17 AR_APPROVAL_USER_LIMITS AR_APPROVAL_USER_LIMITS

18 AR_ARCHIVE_CONTROL AR_ARCHIVE_CONTROL

19 AR_ARCHIVE_CONTROL_DETAIL AR_ARCHIVE_CONTROL_DETAIL

20 AR_ARCHIVE_DETAIL AR_ARCHIVE_DETAIL

21 AR_ARCHIVE_HEADER AR_ARCHIVE_HEADER

22 AR_ARCHIVE_PURGE_INTERIM AR_ARCHIVE_PURGE_INTERIM

23 AR_ARCHIVE_PURGE_LOG AR_ARCHIVE_PURGE_LOG

24 AR_AUDIT_DATA AR_AUDIT_DATA

25 AR_AUTOCASH_HIERARCHIES AR_AUTOCASH_HIERARCHIES

26 AR_AUTOCASH_RULES AR_AUTOCASH_RULES

27 AR_AUTOREC_EXCEPTIONS AR_AUTOREC_EXCEPTIONS

28 AR_BANK_DIRECTORY AR_BANK_DIRECTORY

29 AR_BATCH_SOURCES_ALL AR_BATCH_SOURCES_ALL

30 AR_BATCHES_ALL AR_BATCHES_ALL

31 AR_BPA_AREA_ITEMS AR_BPA_AREA_ITEMS

32 AR_BPA_CONTENT_AREAS_B AR_BPA_CONTENT_AREAS_B

33 AR_BPA_CONTENT_AREAS_TL AR_BPA_CONTENT_AREAS_TL

34 AR_BPA_DATA_SOURCES_B AR_BPA_DATA_SOURCES_B

35 AR_BPA_DATA_SOURCES_TL AR_BPA_DATA_SOURCES_TL

36 AR_BPA_DATA_SRC_PARAMS AR_BPA_DATA_SRC_PARAMS

37 AR_BPA_DATASRC_APPS_B AR_BPA_DATASRC_APPS_B

38 AR_BPA_DATASRC_APPS_TL AR_BPA_DATASRC_APPS_TL

39 AR_BPA_ITEMS_B AR_BPA_ITEMS_B

40 AR_BPA_ITEMS_TL AR_BPA_ITEMS_TL

41 AR_BPA_PAGE_SETUPS_B AR_BPA_PAGE_SETUPS_B

42 AR_BPA_PAGE_SETUPS_TL AR_BPA_PAGE_SETUPS_TL

43 AR_BPA_PRINT_REQUESTS AR_BPA_PRINT_REQUESTS

44 AR_BPA_RULE_ATTRIBUTES_B AR_BPA_RULE_ATTRIBUTES_B

45 AR_BPA_RULE_ATTRIBUTES_TL AR_BPA_RULE_ATTRIBUTES_TL

46 AR_BPA_RULE_TEMPLATES AR_BPA_RULE_TEMPLATES

47 AR_BPA_RULES_B AR_BPA_RULES_B

48 AR_BPA_RULES_TL AR_BPA_RULES_TL

49 AR_BPA_TEMPLATE_FIELDS AR_BPA_TEMPLATE_FIELDS

50 AR_BPA_TEMPLATE_FILES AR_BPA_TEMPLATE_FILES

51 AR_BPA_TEMPLATES_B AR_BPA_TEMPLATES_B

52 AR_BPA_TEMPLATES_TL AR_BPA_TEMPLATES_TL

53 AR_BPA_URL_PARAMS AR_BPA_URL_PARAMS

54 AR_BPA_URLS_B AR_BPA_URLS_B

55 AR_BPA_URLS_TL AR_BPA_URLS_TL

56 AR_BR_FMT_TMP AR_BR_FMT_TMP

57 AR_BR_STAMP_VALUES_ALL AR_BR_STAMP_VALUES_ALL

58 AR_BR_STATUS_REP_ITF AR_BR_STATUS_REP_ITF

59 AR_BR_STATUS_SUM_ITF AR_BR_STATUS_SUM_ITF

60 AR_BR_TRX_BATCH_RPT AR_BR_TRX_BATCH_RPT

61 AR_CALL_ACTIONS AR_CALL_ACTIONS

62 AR_CASH_BASIS_DISTS_ALL AR_CASH_BASIS_DISTS_ALL

63 AR_CASH_RECEIPT_HISTORY_ALL AR_CASH_RECEIPT_HISTORY_ALL

64 AR_CASH_RECEIPTS_ALL AR_CASH_RECEIPTS_ALL

65 AR_CCID_CORRECTIONS_ALL AR_CCID_CORRECTIONS_ALL

66 AR_CHANGE_MATRIX AR_CHANGE_MATRIX

67 AR_CM_SUM_TRX_DAYS_GT AR_CM_SUM_TRX_DAYS_GT

68 AR_CMGT_AUTO_RECOMMENDS AR_CMGT_AUTO_RECOMMENDS

69 AR_CMGT_AUTO_RULE_DTLS AR_CMGT_AUTO_RULE_DTLS

70 AR_CMGT_AUTO_RULES AR_CMGT_AUTO_RULES

71 AR_CMGT_BANK_REF_ACCTS AR_CMGT_BANK_REF_ACCTS

72 AR_CMGT_BANK_REF_DATA AR_CMGT_BANK_REF_DATA

73 AR_CMGT_CASE_FOLDERS AR_CMGT_CASE_FOLDERS

74 AR_CMGT_CF_AGING_DTLS AR_CMGT_CF_AGING_DTLS

75 AR_CMGT_CF_ANL_NOTES AR_CMGT_CF_ANL_NOTES

76 AR_CMGT_CF_DNB_DTLS AR_CMGT_CF_DNB_DTLS

77 AR_CMGT_CF_DTLS AR_CMGT_CF_DTLS

78 AR_CMGT_CF_RECOMMENDS AR_CMGT_CF_RECOMMENDS

79 AR_CMGT_CHECK_LIST_DTLS AR_CMGT_CHECK_LIST_DTLS

80 AR_CMGT_CHECK_LISTS AR_CMGT_CHECK_LISTS

81 AR_CMGT_COLLATERAL_DATA AR_CMGT_COLLATERAL_DATA

82 AR_CMGT_CREDIT_REQUESTS AR_CMGT_CREDIT_REQUESTS

83 AR_CMGT_CURR_USAGE_GT AR_CMGT_CURR_USAGE_GT

84 AR_CMGT_DATA_POINTS_B AR_CMGT_DATA_POINTS_B

85 AR_CMGT_DATA_POINTS_TL AR_CMGT_DATA_POINTS_TL

86 AR_CMGT_DNB_ELEMENTS_B AR_CMGT_DNB_ELEMENTS_B

87 AR_CMGT_DNB_ELEMENTS_TL AR_CMGT_DNB_ELEMENTS_TL

88 AR_CMGT_DNB_MAPPINGS AR_CMGT_DNB_MAPPINGS

89 AR_CMGT_FINANCIAL_DATA AR_CMGT_FINANCIAL_DATA

90 AR_CMGT_GUARANTOR_DATA AR_CMGT_GUARANTOR_DATA

91 AR_CMGT_OTHER_DATA AR_CMGT_OTHER_DATA

92 AR_CMGT_SCORE_DTLS AR_CMGT_SCORE_DTLS

93 AR_CMGT_SCORE_WEIGHTS AR_CMGT_SCORE_WEIGHTS

94 AR_CMGT_SCORES AR_CMGT_SCORES

95 AR_CMGT_SETUP_OPTIONS AR_CMGT_SETUP_OPTIONS

96 AR_CMGT_TRADE_REF_DATA AR_CMGT_TRADE_REF_DATA

97 AR_COLIND AR_COLIND

98 AR_COLLECTION_INDICATORS_ALL AR_COLLECTION_INDICATORS_ALL

99 AR_COLLECTORS AR_COLLECTORS

100 AR_CONC_PROCESS_REQUESTS AR_CONC_PROCESS_REQUESTS

101 AR_CONC_REQUEST_MESSAGES AR_CONC_REQUEST_MESSAGES

102 AR_CONFIRMATION_ACTIONS AR_CONFIRMATION_ACTIONS

103 AR_CONS_INV_ALL AR_CONS_INV_ALL

104 AR_CONS_INV_TRX_ALL AR_CONS_INV_TRX_ALL

105 AR_CONS_INV_TRX_LINES_ALL AR_CONS_INV_TRX_LINES_ALL

106 AR_CORR_PAY_SCHED_ALL AR_CORR_PAY_SCHED_ALL

107 AR_CORRESPONDENCES_ALL AR_CORRESPONDENCES_ALL

108 AR_CREDIT_HISTORIES AR_CREDIT_HISTORIES

109 AR_CREDIT_MEMO_AMOUNTS AR_CREDIT_MEMO_AMOUNTS

110 AR_CUST_PROF_CLASS_AMOUNTS AR_CUST_PROF_CLASS_AMOUNTS

111 AR_CUST_SEARCH_GT

112 AR_CUSTOMER_ALT_NAMES AR_CUSTOMER_ALT_NAMES

113 AR_CUSTOMER_BALANCE_ITF AR_CUSTOMER_BALANCE_ITF

114 AR_CUSTOMER_CALL_TOPICS_ALL AR_CUSTOMER_CALL_TOPICS_ALL

115 AR_CUSTOMER_CALLS_ALL AR_CUSTOMER_CALLS_ALL

116 AR_CUSTOMER_PROFILE_AMOUNTS AR_CUSTOMER_PROFILE_AMOUNTS

117 AR_CUSTOMER_PROFILE_CLASSES AR_CUSTOMER_PROFILE_CLASSES

118 AR_CUSTOMER_PROFILES AR_CUSTOMER_PROFILES

119 AR_DEBUG AR_DEBUG

120 AR_DISPUTE_HISTORY AR_DISPUTE_HISTORY

121 AR_DISTRIBUTION_SET_LINES_ALL AR_DISTRIBUTION_SET_LINES_ALL

122 AR_DISTRIBUTION_SETS_ALL AR_DISTRIBUTION_SETS_ALL

123 AR_DISTRIBUTIONS_ALL AR_DISTRIBUTIONS_ALL

124 AR_DOC_SEQUENCE_AUDIT AR_DOC_SEQUENCE_AUDIT

125 AR_DOCUMENT_TRANSFERS AR_DOCUMENT_TRANSFERS

126 AR_DUNNING_LETTER_SET_LINES AR_DUNNING_LETTER_SET_LINES

127 AR_DUNNING_LETTER_SETS AR_DUNNING_LETTER_SETS

128 AR_DUNNING_LETTERS_B AR_DUNNING_LETTERS_B

129 AR_DUNNING_LETTERS_CUSTOM_TL AR_DUNNING_LETTERS_CUSTOM_TL

130 AR_DUNNING_LETTERS_TL AR_DUNNING_LETTERS_TL

131 AR_INTERIM_CASH_RCPT_LINES_ALL AR_INTERIM_CASH_RCPT_LINES_ALL

132 AR_INTERIM_CASH_RECEIPTS_ALL AR_INTERIM_CASH_RECEIPTS_ALL

133 AR_INTERIM_POSTING AR_INTERIM_POSTING

134 AR_IREC_CUSTOM_CUST_GT

135 AR_IREC_CUSTOM_SRCH_GT

136 AR_IREC_PAYMENT_LIST_GT

137 AR_JOURNAL_INTERIM_ALL AR_JOURNAL_INTERIM_ALL

138 AR_LOCATION_ACCOUNTS_ALL AR_LOCATION_ACCOUNTS_ALL

139 AR_LOCATION_COMBINATIONS

140 AR_LOCATION_RATES

141 AR_LOCATION_VALUES

142 AR_LOCKBOXES_ALL AR_LOCKBOXES_ALL

143 AR_MC_ADJUSTMENTS AR_MC_ADJUSTMENTS

144 AR_MC_BATCHES AR_MC_BATCHES

145 AR_MC_CASH_BASIS_DISTS_ALL AR_MC_CASH_BASIS_DISTS_ALL

146 AR_MC_CASH_RECEIPT_HIST AR_MC_CASH_RECEIPT_HIST

147 AR_MC_CASH_RECEIPTS AR_MC_CASH_RECEIPTS

148 AR_MC_DISTRIBUTIONS_ALL AR_MC_DISTRIBUTIONS_ALL

149 AR_MC_MISC_CASH_DISTS AR_MC_MISC_CASH_DISTS

150 AR_MC_PAYMENT_SCHEDULES AR_MC_PAYMENT_SCHEDULES

151 AR_MC_RATE_ADJUSTMENTS AR_MC_RATE_ADJUSTMENTS

152 AR_MC_RECEIVABLE_APPS AR_MC_RECEIVABLE_APPS

153 AR_MC_TRANSACTION_HISTORY AR_MC_TRANSACTION_HISTORY

154 AR_MEMO_LINES_ALL_B AR_MEMO_LINES_ALL_B

155 AR_MEMO_LINES_ALL_TL AR_MEMO_LINES_ALL_TL

156 AR_MISC_CASH_DISTRIBUTIONS_ALL AR_MISC_CASH_DISTRIBUTIONS_ALL

157 AR_MRC_CASH_HEADER AR_MRC_CASH_HEADER

158 AR_MRC_CASH_LINES AR_MRC_CASH_LINES

159 AR_MRC_INQ_TRANS_BALANCES AR_MRC_INQ_TRANS_BALANCES

160 AR_NOTES AR_NOTES

161 AR_PAYMENT_SCHEDULES_ALL AR_PAYMENT_SCHEDULES_ALL

162 AR_PAYMENTS_INTERFACE_ALL AR_PAYMENTS_INTERFACE_ALL

163 AR_PERIOD_TYPES AR_PERIOD_TYPES

164 AR_PERIODS AR_PERIODS

165 AR_POSTING_CONTROL AR_POSTING_CONTROL

166 AR_POSTING_REPORT_INTERIM AR_POSTING_REPORT_INTERIM

167 AR_PURGE_OE_EXCEPTIONS AR_PURGE_OE_EXCEPTIONS

168 AR_PURGE_REC_AUX AR_PURGE_REC_AUX

169 AR_PURGE_TRX_AUX AR_PURGE_TRX_AUX

170 AR_RAMC_AUDIT_TRAIL AR_RAMC_AUDIT_TRAIL

171 AR_RATE_ADJUSTMENTS_ALL AR_RATE_ADJUSTMENTS_ALL

172 AR_RECEIPT_CLASSES AR_RECEIPT_CLASSES

173 AR_RECEIPT_METHOD_ACCOUNTS_ALL AR_RECEIPT_METHOD_ACCOUNTS_ALL

174 AR_RECEIPT_METHODS AR_RECEIPT_METHODS

175 AR_RECEIPTS_REP_ITF AR_RECEIPTS_REP_ITF

176 AR_RECEIVABLE_APPLICATIONS_ALL AR_RECEIVABLE_APPLICATIONS_ALL

177 AR_RECEIVABLES_TRX_ALL AR_RECEIVABLES_TRX_ALL

178 AR_REV_REC_QT AR_REV_REC_QT

179 AR_REVENUE_ADJUSTMENTS_ALL AR_REVENUE_ADJUSTMENTS_ALL

180 AR_REVENUE_ASSIGNMENTS_GT AR_REVENUE_ASSIGNMENTS_GT

181 AR_SALES_TAX AR_SALES_TAX

182 AR_SALES_TAX_REP_ITF AR_SALES_TAX_REP_ITF

183 AR_SELECTION_CRITERIA AR_SELECTION_CRITERIA

184 AR_STANDARD_TEXT_B AR_STANDARD_TEXT_B

185 AR_STANDARD_TEXT_TL AR_STANDARD_TEXT_TL

186 AR_STATEMENT_CYCLE_DATES_ALL AR_STATEMENT_CYCLE_DATES_ALL

187 AR_STATEMENT_CYCLE_INTERVALS AR_STATEMENT_CYCLE_INTERVALS

188 AR_STATEMENT_CYCLES AR_STATEMENT_CYCLES

189 AR_STATEMENT_FINCHRG_GT AR_STATEMENT_FINCHRG_GT

190 AR_STATEMENT_HEADERS AR_STATEMENT_HEADERS

191 AR_STATEMENT_LINE_CLUSTERS AR_STATEMENT_LINE_CLUSTERS

192 AR_STATEMENTS_HISTORY_ALL AR_STATEMENTS_HISTORY_ALL

193 AR_SUM_REF_EVENT_HIST AR_SUM_REF_EVENT_HIST

194 AR_SYSTEM_PARAMETERS_ALL AR_SYSTEM_PARAMETERS_ALL

195 AR_TA_ASGN_TO_INT_ALL

196 AR_TA_CASHAPP_OB_ALL

197 AR_TA_CR_AGEN_INF_ALL

198 AR_TA_CUST_HIER_CHILD

199 AR_TA_CUST_HIER_PARNT

200 AR_TA_CUST_INT_ALL

201 AR_TA_CUST_TRXSTR_ALL

202 AR_TA_DEDN_ASSGNS_ALL

203 AR_TA_DEDN_INT_ALL

204 AR_TA_DEDN_RELATE_ALL

205 AR_TA_LEGACY_CUST_INT

206 AR_TA_LEGACY_STAT_INT

207 AR_TA_PAYMNT_HIST_ALL

208 AR_TA_PROF_ASSGNT_ALL

209 AR_TA_PROM_CUST_ALL

210 AR_TA_PROM_CUST_MAP

211 AR_TA_PROM_LINES_INT

212 AR_TA_PROM_PAYMNT_ALL

213 AR_TA_PROM_PAYMNT_TYP

214 AR_TA_PROM_PRODS_ALL

215 AR_TA_PROM_STATUS_MAP

216 AR_TA_PROMOTIONS_ALL

217 AR_TA_PROMOTIONS_INT

218 AR_TA_RECON_INFO_ALL

219 AR_TA_RECV_TRXSET_ALL

220 AR_TA_REMIT_HIST_ALL

221 AR_TA_REMIT_PROF_ALL

222 AR_TA_RISK_COMENT_ALL

223 AR_TA_RULE_OUTPUT

224 AR_TA_RULE_SET_LN_ALL

225 AR_TA_RULE_SETS_ALL

226 AR_TA_RULES_ALL

227 AR_TA_TRX_SET_LN_ALL

228 AR_TA_TRX_SETS_ALL

229 AR_TA_TRX_TO_CREATE

230 AR_TA_TRX_TYP_INT_ALL

231 AR_TA_VERSIONS

232 AR_TAX_CODE_COMBINATION_ID_GT AR_TAX_CODE_COMBINATION_ID_GT

233 AR_TAX_CONDITION_ACTIONS_ALL AR_TAX_CONDITION_ACTIONS_ALL

234 AR_TAX_CONDITION_LINES_ALL AR_TAX_CONDITION_LINES_ALL

235 AR_TAX_CONDITIONS_ALL AR_TAX_CONDITIONS_ALL

236 AR_TAX_EXTR_SUB_AP_EXT

237 AR_TAX_EXTR_SUB_AR_EXT

238 AR_TAX_EXTR_SUB_COM_EXT

239 AR_TAX_EXTRACT_DCL_ITF

240 AR_TAX_EXTRACT_MATRIX_ITF

241 AR_TAX_EXTRACT_SUB_ITF

242 AR_TAX_GROUP_CODES_ALL AR_TAX_GROUP_CODES_ALL

243 AR_TAX_INTERFACE AR_TAX_INTERFACE

244 AR_TRANS_FIELD_FORMATS AR_TRANS_FIELD_FORMATS

245 AR_TRANS_RECORD_FORMATS AR_TRANS_RECORD_FORMATS

246 AR_TRANSACTION_HISTORY_ALL AR_TRANSACTION_HISTORY_ALL

247 AR_TRANSACTIONS_REP_ITF AR_TRANSACTIONS_REP_ITF

248 AR_TRANSMISSION_FORMATS AR_TRANSMISSION_FORMATS

249 AR_TRANSMISSIONS_ALL AR_TRANSMISSIONS_ALL

250 AR_TRX_BAL_SUMMARY AR_TRX_BAL_SUMMARY

251 AR_TRX_DIST_GT AR_TRX_DIST_GT

252 AR_TRX_ERRORS_GT AR_TRX_ERRORS_GT

253 AR_TRX_HEADER_GT AR_TRX_HEADER_GT

254 AR_TRX_LINES_GT AR_TRX_LINES_GT

255 AR_TRX_SALESCREDITS_GT AR_TRX_SALESCREDITS_GT

256 AR_TRX_SUMMARY AR_TRX_SUMMARY

257 AR_TRX_SUMMARY_HIST AR_TRX_SUMMARY_HIST

258 AR_VAT_TAX_ALL_B AR_VAT_TAX_ALL_B

259 AR_VAT_TAX_ALL_TL AR_VAT_TAX_ALL_TL

260 DR$HZ_CLASS_CODE_DENORM_T1$I DR$HZ_CLASS_CODE_DENORM_T1$I

261 DR$HZ_CLASS_CODE_DENORM_T1$K DR$HZ_CLASS_CODE_DENORM_T1$K

262 DR$HZ_CLASS_CODE_DENORM_T1$N DR$HZ_CLASS_CODE_DENORM_T1$N

263 DR$HZ_CLASS_CODE_DENORM_T1$R DR$HZ_CLASS_CODE_DENORM_T1$R

264 HZ_ADAPTER_LOGS HZ_ADAPTER_LOGS

265 HZ_ADAPTER_TERRITORIES HZ_ADAPTER_TERRITORIES

266 HZ_ADAPTERS HZ_ADAPTERS

267 HZ_APPLICATION_TRANS_GT HZ_APPLICATION_TRANS_GT

268 HZ_BANK_VAL_GT HZ_BANK_VAL_GT

269 HZ_BILLING_PREFERENCES HZ_BILLING_PREFERENCES

270 HZ_CERTIFICATIONS HZ_CERTIFICATIONS

271 HZ_CITIZENSHIP HZ_CITIZENSHIP

272 HZ_CLASS_CATEGORIES HZ_CLASS_CATEGORIES

273 HZ_CLASS_CATEGORY_USES HZ_CLASS_CATEGORY_USES

274 HZ_CLASS_CODE_DENORM HZ_CLASS_CODE_DENORM

275 HZ_CLASS_CODE_RELATIONS HZ_CLASS_CODE_RELATIONS

276 HZ_CODE_ASSIGNMENTS HZ_CODE_ASSIGNMENTS

277 HZ_CONTACT_POINT_VAL_GT HZ_CONTACT_POINT_VAL_GT

278 HZ_CONTACT_POINTS HZ_CONTACT_POINTS

279 HZ_CONTACT_PREFERENCES HZ_CONTACT_PREFERENCES

280 HZ_CONTACT_RESTRICTIONS HZ_CONTACT_RESTRICTIONS

281 HZ_CREDIT_PROFILE_AMTS HZ_CREDIT_PROFILE_AMTS

282 HZ_CREDIT_PROFILES HZ_CREDIT_PROFILES

283 HZ_CREDIT_RATINGS HZ_CREDIT_RATINGS

284 HZ_CREDIT_USAGE_RULE_SETS_B HZ_CREDIT_USAGE_RULE_SETS_B

285 HZ_CREDIT_USAGE_RULE_SETS_TL HZ_CREDIT_USAGE_RULE_SETS_TL

286 HZ_CREDIT_USAGE_RULES HZ_CREDIT_USAGE_RULES

287 HZ_CREDIT_USAGES HZ_CREDIT_USAGES

288 HZ_CUST_ACCOUNT_ROLES HZ_CUST_ACCOUNT_ROLES

289 HZ_CUST_ACCOUNT_ROLES_M HZ_CUST_ACCOUNT_ROLES_M

290 HZ_CUST_ACCOUNTS HZ_CUST_ACCOUNTS

291 HZ_CUST_ACCOUNTS_M HZ_CUST_ACCOUNTS_M

292 HZ_CUST_ACCT_RELATE_ALL HZ_CUST_ACCT_RELATE_ALL

293 HZ_CUST_ACCT_RELATE_ALL_M HZ_CUST_ACCT_RELATE_ALL_M

294 HZ_CUST_ACCT_SITES_ALL HZ_CUST_ACCT_SITES_ALL

295 HZ_CUST_ACCT_SITES_ALL_M HZ_CUST_ACCT_SITES_ALL_M

296 HZ_CUST_CONTACT_POINTS HZ_CUST_CONTACT_POINTS

297 HZ_CUST_MERGE_LOG_DICT HZ_CUST_MERGE_LOG_DICT

298 HZ_CUST_PROF_CLASS_AMTS HZ_CUST_PROF_CLASS_AMTS

299 HZ_CUST_PROFILE_AMTS HZ_CUST_PROFILE_AMTS

300 HZ_CUST_PROFILE_AMTS_M HZ_CUST_PROFILE_AMTS_M

301 HZ_CUST_PROFILE_CLASSES HZ_CUST_PROFILE_CLASSES

302 HZ_CUST_SITE_USES_ALL HZ_CUST_SITE_USES_ALL

303 HZ_CUST_SITE_USES_ALL_M HZ_CUST_SITE_USES_ALL_M

304 HZ_CUSTOMER_MERGE_LOG HZ_CUSTOMER_MERGE_LOG

305 HZ_CUSTOMER_PROFILES HZ_CUSTOMER_PROFILES

306 HZ_CUSTOMER_PROFILES_M HZ_CUSTOMER_PROFILES_M

307 HZ_DNB_REQUEST_LOG HZ_DNB_REQUEST_LOG

308 HZ_DQM_DETAILS_GT HZ_DQM_DETAILS_GT

309 HZ_DQM_PARTIES_GT HZ_DQM_PARTIES_GT

310 HZ_DQM_STAGE_GT HZ_DQM_STAGE_GT

311 HZ_DQM_STAGE_LOG HZ_DQM_STAGE_LOG

312 HZ_DQM_SYNC_GT HZ_DQM_SYNC_GT

313 HZ_DQM_SYNC_INTERFACE HZ_DQM_SYNC_INTERFACE

314 HZ_DSS_ASSIGNMENTS HZ_DSS_ASSIGNMENTS

315 HZ_DSS_CRITERIA HZ_DSS_CRITERIA

316 HZ_DSS_ENTITIES HZ_DSS_ENTITIES

317 HZ_DSS_GROUPS_B HZ_DSS_GROUPS_B

318 HZ_DSS_GROUPS_TL HZ_DSS_GROUPS_TL

319 HZ_DSS_SCHEME_FUNCTIONS HZ_DSS_SCHEME_FUNCTIONS

320 HZ_DSS_SECURED_ENTITIES HZ_DSS_SECURED_ENTITIES

321 HZ_DUP_BATCH HZ_DUP_BATCH

322 HZ_DUP_EXCLUSIONS HZ_DUP_EXCLUSIONS

323 HZ_DUP_MATCH_DETAILS HZ_DUP_MATCH_DETAILS

324 HZ_DUP_MERGE_PARTIES HZ_DUP_MERGE_PARTIES

325 HZ_DUP_RESULTS HZ_DUP_RESULTS

326 HZ_DUP_SET_PARTIES HZ_DUP_SET_PARTIES

327 HZ_DUP_SETS HZ_DUP_SETS

328 HZ_DUP_WORKER_CHUNK_GT HZ_DUP_WORKER_CHUNK_GT

329 HZ_EDUCATION HZ_EDUCATION

330 HZ_EMAIL_DOMAINS HZ_EMAIL_DOMAINS

331 HZ_EMPLOYMENT_HISTORY HZ_EMPLOYMENT_HISTORY

332 HZ_ENTITY_ATTRIBUTES HZ_ENTITY_ATTRIBUTES

333 HZ_EXT_DATA_RULES_TL HZ_EXT_DATA_RULES_TL

334 HZ_FINANCIAL_NUMBERS HZ_FINANCIAL_NUMBERS

335 HZ_FINANCIAL_PROFILE HZ_FINANCIAL_PROFILE

336 HZ_FINANCIAL_REPORTS HZ_FINANCIAL_REPORTS

337 HZ_GEO_NAME_REFERENCE_LOG HZ_GEO_NAME_REFERENCE_LOG

338 HZ_GEO_NAME_REFERENCES HZ_GEO_NAME_REFERENCES

339 HZ_GEO_STRUCT_MAP HZ_GEO_STRUCT_MAP

340 HZ_GEO_STRUCT_MAP_DTL HZ_GEO_STRUCT_MAP_DTL

341 HZ_GEO_STRUCTURE_LEVELS HZ_GEO_STRUCTURE_LEVELS

342 HZ_GEOGRAPHIES HZ_GEOGRAPHIES

343 HZ_GEOGRAPHY_IDENTIFIERS HZ_GEOGRAPHY_IDENTIFIERS

344 HZ_GEOGRAPHY_RANGES HZ_GEOGRAPHY_RANGES

345 HZ_GEOGRAPHY_TYPES_B HZ_GEOGRAPHY_TYPES_B

346 HZ_GEOGRAPHY_TYPES_TL HZ_GEOGRAPHY_TYPES_TL

347 HZ_GROUP_VAL_GT HZ_GROUP_VAL_GT

348 HZ_HIERARCHY_NODES HZ_HIERARCHY_NODES

349 HZ_IMP_ADAPTERS HZ_IMP_ADAPTERS

350 HZ_IMP_ADDRESSES_INT HZ_IMP_ADDRESSES_INT

351 HZ_IMP_ADDRESSES_SG HZ_IMP_ADDRESSES_SG

352 HZ_IMP_ADDRESSUSES_INT HZ_IMP_ADDRESSUSES_INT

353 HZ_IMP_ADDRESSUSES_SG HZ_IMP_ADDRESSUSES_SG

354 HZ_IMP_BATCH_DETAILS HZ_IMP_BATCH_DETAILS

355 HZ_IMP_BATCH_SUMMARY HZ_IMP_BATCH_SUMMARY

356 HZ_IMP_CLASSIFICS_INT HZ_IMP_CLASSIFICS_INT

357 HZ_IMP_CLASSIFICS_SG HZ_IMP_CLASSIFICS_SG

358 HZ_IMP_CONTACTPTS_INT HZ_IMP_CONTACTPTS_INT

359 HZ_IMP_CONTACTPTS_SG HZ_IMP_CONTACTPTS_SG

360 HZ_IMP_CONTACTROLES_INT HZ_IMP_CONTACTROLES_INT

361 HZ_IMP_CONTACTROLES_SG HZ_IMP_CONTACTROLES_SG

362 HZ_IMP_CONTACTS_INT HZ_IMP_CONTACTS_INT

363 HZ_IMP_CONTACTS_SG HZ_IMP_CONTACTS_SG

364 HZ_IMP_CREDITRTNGS_INT HZ_IMP_CREDITRTNGS_INT

365 HZ_IMP_CREDITRTNGS_SG HZ_IMP_CREDITRTNGS_SG

366 HZ_IMP_DUP_DETAILS HZ_IMP_DUP_DETAILS

367 HZ_IMP_DUP_PARTIES HZ_IMP_DUP_PARTIES

368 HZ_IMP_ERRORS HZ_IMP_ERRORS

369 HZ_IMP_FINNUMBERS_INT HZ_IMP_FINNUMBERS_INT

370 HZ_IMP_FINNUMBERS_SG HZ_IMP_FINNUMBERS_SG

371 HZ_IMP_FINREPORTS_INT HZ_IMP_FINREPORTS_INT

372 HZ_IMP_FINREPORTS_SG HZ_IMP_FINREPORTS_SG

373 HZ_IMP_INT_DEDUP_RESULTS HZ_IMP_INT_DEDUP_RESULTS

374 HZ_IMP_OSR_CHANGE HZ_IMP_OSR_CHANGE

375 HZ_IMP_PARTIES_INT HZ_IMP_PARTIES_INT

376 HZ_IMP_PARTIES_SG HZ_IMP_PARTIES_SG

377 HZ_IMP_RELSHIPS_INT HZ_IMP_RELSHIPS_INT

378 HZ_IMP_RELSHIPS_SG HZ_IMP_RELSHIPS_SG

379 HZ_IMP_TMP_ERRORS HZ_IMP_TMP_ERRORS

380 HZ_IMP_TMP_REL_END_DATE HZ_IMP_TMP_REL_END_DATE

381 HZ_IMP_WORK_UNITS HZ_IMP_WORK_UNITS

382 HZ_INDUSTRIAL_CLASS_APP HZ_INDUSTRIAL_CLASS_APP

383 HZ_INDUSTRIAL_CLASSES HZ_INDUSTRIAL_CLASSES

384 HZ_INDUSTRIAL_REFERENCE HZ_INDUSTRIAL_REFERENCE

385 HZ_INT_DUP_RESULTS HZ_INT_DUP_RESULTS

386 HZ_INT_DUP_RESULTS_GT HZ_INT_DUP_RESULTS_GT

387 HZ_LOC_ASSIGNMENTS

388 HZ_LOCATION_PROFILES HZ_LOCATION_PROFILES

389 HZ_LOCATION_VAL_GT HZ_LOCATION_VAL_GT

390 HZ_LOCATIONS HZ_LOCATIONS

391 HZ_LOG HZ_LOG

392 HZ_LOG2 HZ_LOG2

393 HZ_MATCH_RULE_PRIMARY HZ_MATCH_RULE_PRIMARY

394 HZ_MATCH_RULE_SECONDARY HZ_MATCH_RULE_SECONDARY

395 HZ_MATCH_RULES_B HZ_MATCH_RULES_B

396 HZ_MATCH_RULES_TL HZ_MATCH_RULES_TL

397 HZ_MATCHED_CONTACTS_GT HZ_MATCHED_CONTACTS_GT

398 HZ_MATCHED_CPTS_GT HZ_MATCHED_CPTS_GT

399 HZ_MATCHED_PARTIES_GT HZ_MATCHED_PARTIES_GT

400 HZ_MATCHED_PARTY_SITES_GT HZ_MATCHED_PARTY_SITES_GT

401 HZ_MERGE_BATCH HZ_MERGE_BATCH

402 HZ_MERGE_DICTIONARY HZ_MERGE_DICTIONARY

403 HZ_MERGE_ENTITY_ATTRIBUTES HZ_MERGE_ENTITY_ATTRIBUTES

404 HZ_MERGE_PARTIES HZ_MERGE_PARTIES

405 HZ_MERGE_PARTIES_SUGG HZ_MERGE_PARTIES_SUGG

406 HZ_MERGE_PARTY_DETAILS HZ_MERGE_PARTY_DETAILS

407 HZ_MERGE_PARTY_HISTORY HZ_MERGE_PARTY_HISTORY

408 HZ_MERGE_PARTY_LOG HZ_MERGE_PARTY_LOG

409 HZ_MERGE_PARTYDTLS_SUGG HZ_MERGE_PARTYDTLS_SUGG

410 HZ_MOBILE_PREFIXES HZ_MOBILE_PREFIXES

411 HZ_ORG_CONTACT_ROLES HZ_ORG_CONTACT_ROLES

412 HZ_ORG_CONTACT_VAL_GT HZ_ORG_CONTACT_VAL_GT

413 HZ_ORG_CONTACTS HZ_ORG_CONTACTS

414 HZ_ORG_PROFILE_VAL_GT HZ_ORG_PROFILE_VAL_GT

415 HZ_ORGANIZATION_INDICATORS HZ_ORGANIZATION_INDICATORS

416 HZ_ORGANIZATION_PROFILES HZ_ORGANIZATION_PROFILES

417 HZ_ORIG_SYS_MAPPING HZ_ORIG_SYS_MAPPING

418 HZ_ORIG_SYS_REFERENCES HZ_ORIG_SYS_REFERENCES

419 HZ_PARAM_TAB HZ_PARAM_TAB

420 HZ_PARTIES HZ_PARTIES

421 HZ_PARTY_INTERFACE HZ_PARTY_INTERFACE

422 HZ_PARTY_INTERFACE_ERRORS HZ_PARTY_INTERFACE_ERRORS

423 HZ_PARTY_PREFERENCES HZ_PARTY_PREFERENCES

424 HZ_PARTY_RELATIONSHIPS HZ_PARTY_RELATIONSHIPS

425 HZ_PARTY_SCORE_DTLS_GT HZ_PARTY_SCORE_DTLS_GT

426 HZ_PARTY_SITE_USES HZ_PARTY_SITE_USES

427 HZ_PARTY_SITE_VAL_GT HZ_PARTY_SITE_VAL_GT

428 HZ_PARTY_SITES HZ_PARTY_SITES

429 HZ_PARTY_VAL_GT HZ_PARTY_VAL_GT

430 HZ_PERSON_INTEREST HZ_PERSON_INTEREST

431 HZ_PERSON_LANGUAGE HZ_PERSON_LANGUAGE

432 HZ_PERSON_PROFILES HZ_PERSON_PROFILES

433 HZ_PHONE_AREA_CODES HZ_PHONE_AREA_CODES

434 HZ_PHONE_COUNTRY_CODES HZ_PHONE_COUNTRY_CODES

435 HZ_PHONE_FORMATS HZ_PHONE_FORMATS

436 HZ_PRIMARY_TRANS HZ_PRIMARY_TRANS

437 HZ_PURGE_BATCHES HZ_PURGE_BATCHES

438 HZ_PURGE_CANDIDATES HZ_PURGE_CANDIDATES

439 HZ_PURGE_GT HZ_PURGE_GT

440 HZ_REFERENCES HZ_REFERENCES

441 HZ_REG_VERIFICATIONS

442 HZ_REGISTRATIONS

443 HZ_RELATIONSHIP_TYPES HZ_RELATIONSHIP_TYPES

444 HZ_RELATIONSHIP_VAL_GT HZ_RELATIONSHIP_VAL_GT

445 HZ_RELATIONSHIPS HZ_RELATIONSHIPS

446 HZ_ROLE_RESPONSIBILITY HZ_ROLE_RESPONSIBILITY

447 HZ_SECONDARY_TRANS HZ_SECONDARY_TRANS

448 HZ_SECURITY_ISSUED HZ_SECURITY_ISSUED

449 HZ_SELECT_DATA_SOURCES HZ_SELECT_DATA_SOURCES

450 HZ_SRCH_CONTACTS HZ_SRCH_CONTACTS

451 HZ_SRCH_CPTS HZ_SRCH_CPTS

452 HZ_SRCH_PARTIES HZ_SRCH_PARTIES

453 HZ_SRCH_PSITES HZ_SRCH_PSITES

454 HZ_STAGED_CONTACT_POINTS HZ_STAGED_CONTACT_POINTS

455 HZ_STAGED_CONTACTS HZ_STAGED_CONTACTS

456 HZ_STAGED_PARTIES HZ_STAGED_PARTIES

457 HZ_STAGED_PARTY_SITES HZ_STAGED_PARTY_SITES

458 HZ_STOCK_MARKETS HZ_STOCK_MARKETS

459 HZ_STYLE_FMT_LAYOUTS_B HZ_STYLE_FMT_LAYOUTS_B

460 HZ_STYLE_FMT_LAYOUTS_TL HZ_STYLE_FMT_LAYOUTS_TL

461 HZ_STYLE_FMT_LOCALES HZ_STYLE_FMT_LOCALES

462 HZ_STYLE_FMT_VARIATIONS HZ_STYLE_FMT_VARIATIONS

463 HZ_STYLE_FORMATS_B HZ_STYLE_FORMATS_B

464 HZ_STYLE_FORMATS_TL HZ_STYLE_FORMATS_TL

465 HZ_STYLES_B HZ_STYLES_B

466 HZ_STYLES_TL HZ_STYLES_TL

467 HZ_SUSPENSION_ACTIVITY HZ_SUSPENSION_ACTIVITY

468 HZ_THIRDPARTY_EXCEPS HZ_THIRDPARTY_EXCEPS

469 HZ_THIRDPARTY_RULE HZ_THIRDPARTY_RULE

470 HZ_TIMEZONE_MAPPING HZ_TIMEZONE_MAPPING

471 HZ_TIMEZONES HZ_TIMEZONES

472 HZ_TIMEZONES_TL HZ_TIMEZONES_TL

473 HZ_TRANS_ATTRIBUTES_B HZ_TRANS_ATTRIBUTES_B

474 HZ_TRANS_ATTRIBUTES_TL HZ_TRANS_ATTRIBUTES_TL

475 HZ_TRANS_FUNCTIONS_B HZ_TRANS_FUNCTIONS_B

476 HZ_TRANS_FUNCTIONS_TL HZ_TRANS_FUNCTIONS_TL

477 HZ_USER_CREATE_RULES HZ_USER_CREATE_RULES

478 HZ_USER_ORG_GT HZ_USER_ORG_GT

479 HZ_USER_OVERWRITE_RULES HZ_USER_OVERWRITE_RULES

480 HZ_WIN_SOURCE_EXCEPS HZ_WIN_SOURCE_EXCEPS

481 HZ_WORD_LISTS HZ_WORD_LISTS

482 HZ_WORD_REPLACEMENTS HZ_WORD_REPLACEMENTS

483 HZ_WORK_CLASS HZ_WORK_CLASS

484 JE_DE_AR_BATCHES JE_DE_AR_BATCHES

485 JE_DE_REMITTANCE_RESULTS JE_DE_REMITTANCE_RESULTS

486 JG_ZZ_AR_BALANCES JG_ZZ_AR_BALANCES

487 JG_ZZ_AR_TMP_ACCOUNT JG_ZZ_AR_TMP_ACCOUNT

488 JG_ZZ_AR_TMP_BAL JG_ZZ_AR_TMP_BAL

489 JG_ZZ_AR_TMP_DETAIL JG_ZZ_AR_TMP_DETAIL

490 JG_ZZ_II_INT_RATES_ALL JG_ZZ_II_INT_RATES_ALL

491 JG_ZZ_INT_INV_LINES_ALL JG_ZZ_INT_INV_LINES_ALL

492 JG_ZZ_INTEREST_BATCHES_ALL JG_ZZ_INTEREST_BATCHES_ALL

493 JG_ZZ_INTEREST_INVOICES_ALL JG_ZZ_INTEREST_INVOICES_ALL

494 JG_ZZ_JGZZCSLP_MESSAGES JG_ZZ_JGZZCSLP_MESSAGES

495 OCM_CREDIT_REVIEW_GT OCM_CREDIT_REVIEW_GT

496 RA_ACCOUNT_COMBINATIONS RA_ACCOUNT_COMBINATIONS

497 RA_ACCOUNT_DEFAULT_SEGMENTS RA_ACCOUNT_DEFAULT_SEGMENTS

498 RA_ACCOUNT_DEFAULTS_ALL RA_ACCOUNT_DEFAULTS_ALL

499 RA_ADDRESSES_ALL RA_ADDRESSES_ALL

500 RA_BATCH_SOURCES_ALL RA_BATCH_SOURCES_ALL

501 RA_BATCHES_ALL RA_BATCHES_ALL

502 RA_CM_REQUEST_LINES_ALL RA_CM_REQUEST_LINES_ALL

503 RA_CM_REQUESTS_ALL RA_CM_REQUESTS_ALL

504 RA_CONTACT_PHONES_INT_ALL RA_CONTACT_PHONES_INT_ALL

505 RA_CONTACT_ROLES RA_CONTACT_ROLES

506 RA_CONTACTS RA_CONTACTS

507 RA_CUST_PAY_METHOD_INT_ALL RA_CUST_PAY_METHOD_INT_ALL

508 RA_CUST_RECEIPT_METHODS RA_CUST_RECEIPT_METHODS

509 RA_CUST_TRX_LINE_GL_DIST_ALL RA_CUST_TRX_LINE_GL_DIST_ALL

510 RA_CUST_TRX_LINE_SALESREPS_ALL RA_CUST_TRX_LINE_SALESREPS_ALL

511 RA_CUST_TRX_TYPES_ALL RA_CUST_TRX_TYPES_ALL

512 RA_CUSTOMER_BANKS_INT_ALL RA_CUSTOMER_BANKS_INT_ALL

513 RA_CUSTOMER_MERGE_HEADERS RA_CUSTOMER_MERGE_HEADERS

514 RA_CUSTOMER_MERGES RA_CUSTOMER_MERGES

515 RA_CUSTOMER_PROFILES_INT_ALL RA_CUSTOMER_PROFILES_INT_ALL

516 RA_CUSTOMER_RELATIONSHIPS_ALL RA_CUSTOMER_RELATIONSHIPS_ALL

517 RA_CUSTOMER_TRX_ALL RA_CUSTOMER_TRX_ALL

518 RA_CUSTOMER_TRX_LINES_ALL RA_CUSTOMER_TRX_LINES_ALL

519 RA_CUSTOMERS RA_CUSTOMERS

520 RA_CUSTOMERS_INTERFACE_ALL RA_CUSTOMERS_INTERFACE_ALL

521 RA_GROUP_BY_COLUMNS RA_GROUP_BY_COLUMNS

522 RA_GROUP_BYS RA_GROUP_BYS

523 RA_GROUPING_RULES RA_GROUPING_RULES

524 RA_GROUPING_TRX_TYPES RA_GROUPING_TRX_TYPES

525 RA_INTERFACE_DISTRIBUTIONS_ALL RA_INTERFACE_DISTRIBUTIONS_ALL

526 RA_INTERFACE_ERRORS_ALL RA_INTERFACE_ERRORS_ALL

527 RA_INTERFACE_LINES_ALL RA_INTERFACE_LINES_ALL

528 RA_INTERFACE_SALESCREDITS_ALL RA_INTERFACE_SALESCREDITS_ALL

529 RA_ITEM_EXCEPTION_RATES RA_ITEM_EXCEPTION_RATES

530 RA_LINE_ORDER_BY_COLUMNS RA_LINE_ORDER_BY_COLUMNS

531 RA_LINE_ORDER_BYS RA_LINE_ORDER_BYS

532 RA_LINE_ORDERING_RULES RA_LINE_ORDERING_RULES

533 RA_MC_BATCHES RA_MC_BATCHES

534 RA_MC_CUSTOMER_TRX RA_MC_CUSTOMER_TRX

535 RA_MC_CUSTOMER_TRX_LINES RA_MC_CUSTOMER_TRX_LINES

536 RA_MC_TRX_LINE_GL_DIST RA_MC_TRX_LINE_GL_DIST

537 RA_PHONES RA_PHONES

538 RA_RECUR_INTERIM RA_RECUR_INTERIM

539 RA_REMIT_TOS_ALL RA_REMIT_TOS_ALL

540 RA_RULE_SCHEDULES RA_RULE_SCHEDULES

541 RA_RULES RA_RULES

542 RA_SALESREP_TERRITORIES RA_SALESREP_TERRITORIES

543 RA_SALESREPS_ALL_OLD RA_SALESREPS_ALL_OLD

544 RA_SITE_USES_ALL RA_SITE_USES_ALL

545 RA_TAX_EXEMPTIONS_ALL RA_TAX_EXEMPTIONS_ALL

546 RA_TERMS_B RA_TERMS_B

547 RA_TERMS_LINES RA_TERMS_LINES

548 RA_TERMS_LINES_DISCOUNTS RA_TERMS_LINES_DISCOUNTS

549 RA_TERMS_TL RA_TERMS_TL

550 RA_TERRITORIES RA_TERRITORIES

551 SYS_IOT_OVER_375198 SYS_IOT_OVER_375198

552 AR_ACTIVITY_DETAILS

553 AR_BASE_GL_ACCT_BALANCES

554 AR_CC_ERROR_HISTORY

555 AR_CC_ERROR_MAPPINGS

556 AR_CCID_BY_GL_ACCOUNTS

557 AR_CHARGE_SCHEDULE_HDRS

558 AR_CHARGE_SCHEDULE_LINES

559 AR_CHARGE_SCHEDULES

560 AR_CLOSED_GL_PERIODS

561 AR_COGS_REV_ITF

562 AR_CONS_BILL_CYCLE_DATES

563 AR_CONS_BILL_CYCLES_B

564 AR_CONS_BILL_CYCLES_TL

565 AR_CONT_ACTIONS_ALL

566 AR_CRH_APP_GT

567 AR_CRH_GT

568 AR_CUST_SEARCH_GT_ALL

569 AR_DEFERRAL_REASONS

570 AR_DEFERRED_LINES_ALL

571 AR_DETECT_GT

572 AR_GL_ACCT_BALANCES

573 AR_GL_RECON_GT

574 AR_INTEREST_BATCHES_ALL

575 AR_INTEREST_HEADERS_ALL

576 AR_INTEREST_LINES_ALL

577 AR_INTERFACE_CONTS_ALL

578 AR_INV_API_DIST_GT

579 AR_INV_API_HEADERS_GT

580 AR_INV_API_LINES_GT

581 AR_IREC_APPLY_CREDIT_GT

582 AR_IREC_CSTM_CUST_GT_ALL

583 AR_IREC_CSTM_SRCH_GT_ALL

584 AR_IREC_PAYMENT_GT_ALL

585 AR_IREC_PRINT_REQUESTS

586 AR_IREC_SELFREG_CUST_QS

587 AR_IREC_SELFREG_SITE_QS

588 AR_LATE_CHARGE_CREDITS_GT

589 AR_LATE_CHARGE_CUST_BALANCE_GT

590 AR_LATE_CHARGE_DOC_GT

591 AR_LATE_CHARGE_TRX_T

592 AR_LC_CUST_SITES_T

593 AR_LINE_APP_DETAIL_GT

594 AR_LINE_CONTS_ALL

595 AR_LINE_DIST_INTERFACE_GT

596 AR_LINE_REV_ADJ_GT

597 AR_LLCA_TRX_ERRORS_GT

598 AR_LLCA_TRX_LINES_GT

599 AR_LOC_COMBINATIONS_OLD

600 AR_LOCATION_RATES_OLD

601 AR_LOCATION_VALUES_OLD

602 AR_RDR_PARAMETERS_GT

603 AR_REC_TRX_LE_DETAILS_ALL

604 AR_RECEIPTS_GT

605 AR_RECEIVABLE_APPS_GT

606 AR_REMIT_GT

607 AR_REVIEWED_LINES_GT

608 AR_SUBMISSION_CTRL_GT

609 AR_TRX_COGS_GT

610 AR_TRX_CONTINGENCIES_GT

611 AR_TRX_DIST_TMP_GT

612 AR_TRX_HEADER_TMP_GT

613 AR_TRX_LINES_TMP_GT

614 AR_TRX_SALESCREDITS_TMP_GT

615 AR_UPG_120_CONTROL

616 AR_XLA_HEADERS_EXTRACT

617 AR_XLA_LINES_EXTRACT

618 ARI_REG_VERIFICATIONS_GT

619 HZ_ADAPTER_USERS

620 HZ_ADDRESS_USAGE_DTLS

621 HZ_ADDRESS_USAGES

622 HZ_BES_GT

623 HZ_BUS_OBJ_DEFINITIONS

624 HZ_BUS_OBJ_TRACKING

625 HZ_CREDIT_RATINGS_EXT_B

626 HZ_CREDIT_RATINGS_EXT_TL

627 HZ_DL_SELECTED_CRITERIA

628 HZ_DQM_SETUP_DIAGNOSTICS

629 HZ_DQM_SH_SYNC_INTERFACE

630 HZ_FIN_NUMBERS_EXT_B

631 HZ_FIN_NUMBERS_EXT_TL

632 HZ_FIN_REPORTS_EXT_B

633 HZ_FIN_REPORTS_EXT_TL

634 HZ_JMS_OUT

635 HZ_LOC_ASSIGNMENTS_OBS

636 HZ_LOCATIONS_EXT_B

637 HZ_LOCATIONS_EXT_TL

638 HZ_MATCH_RULE_CONDITIONS

639 HZ_NON_PURGE_CANDIDATES

640 HZ_ORG_PROFILES_EXT_B

641 HZ_ORG_PROFILES_EXT_SG

642 HZ_ORG_PROFILES_EXT_TL

643 HZ_ORIG_SYSTEMS_B

644 HZ_ORIG_SYSTEMS_TL

645 HZ_PARTY_SITES_EXT_B

646 HZ_PARTY_SITES_EXT_TL

647 HZ_PARTY_USAGE_RULES

648 HZ_PARTY_USAGES_B

649 HZ_PARTY_USAGES_TL

650 HZ_PARTY_USG_ASSIGNMENTS

651 HZ_PER_PROFILES_EXT_B

652 HZ_PER_PROFILES_EXT_SG

653 HZ_PER_PROFILES_EXT_TL

654 HZ_SHADOW_ST_CONTACTS

655 HZ_SHADOW_ST_CPTS

656 HZ_SHADOW_ST_PARTIES

657 HZ_SHADOW_ST_PSITES

658 HZ_TEMP_REL_GT

659 HZ_THIN_ST_CONTACTS

660 HZ_THIN_ST_CPTS

661 HZ_THIN_ST_PARTIES

662 HZ_THIN_ST_PSITES

663 HZ_TRANSFORMATIONS_B

664 HZ_TRANSFORMATIONS_TL

665 HZ_WORD_RPL_COND_ATTRIBS

666 HZ_WORD_RPL_CONDS_B

667 HZ_WORD_RPL_CONDS_TL

668 RA_AR_GT

669 RA_CUSTOMER_TRX_LINES_GT

ORDER MANAGEMENT

Un Changed = 148

New Tables = 2

Deleted = 0

11i TABLES R12 TABLES

1 OE_ACTION_PRE_REQS OE_ACTION_PRE_REQS

2 OE_ACTIONS_IFACE_ALL OE_ACTIONS_IFACE_ALL

3 OE_ADJ_ATTRIB_EBS_LOG OE_ADJ_ATTRIB_EBS_LOG

4 OE_AK_GEN_OBJECTS_CFG OE_AK_GEN_OBJECTS_CFG

5 OE_AK_OBJ_ATTR_EXT OE_AK_OBJ_ATTR_EXT

6 OE_AK_OBJ_WF_ITEMS OE_AK_OBJ_WF_ITEMS

7 OE_AK_OBJECTS_EXT OE_AK_OBJECTS_EXT

8 OE_APPROVER_LIST_MEMBERS OE_APPROVER_LIST_MEMBERS

9 OE_APPROVER_LISTS OE_APPROVER_LISTS 0

10 OE_APPROVER_TRANSACTIONS OE_APPROVER_TRANSACTIONS

11 OE_ATTACHMENT_OBJECT_REFS OE_ATTACHMENT_OBJECT_REFS

12 OE_ATTACHMENT_OBJECT_REFS_TL OE_ATTACHMENT_OBJECT_REFS_TL

13 OE_ATTACHMENT_RULE_ELEMENTS OE_ATTACHMENT_RULE_ELEMENTS

14 OE_ATTACHMENT_RULES OE_ATTACHMENT_RULES

15 OE_AUDIT_ATTR_HISTORY OE_AUDIT_ATTR_HISTORY

16 OE_BLANKET_HEADERS_ALL OE_BLANKET_HEADERS_ALL

17 OE_BLANKET_HEADERS_EXT OE_BLANKET_HEADERS_EXT

18 OE_BLANKET_HEADERS_HIST OE_BLANKET_HEADERS_HIST

19 OE_BLANKET_LINES_ALL OE_BLANKET_LINES_ALL

20 OE_BLANKET_LINES_EXT OE_BLANKET_LINES_EXT

21 OE_BLANKET_LINES_HIST OE_BLANKET_LINES_HIST

22 OE_BLANKET_ORG_ASSIGN OE_BLANKET_ORG_ASSIGN

23 OE_CC_PROCESSOR_TEMP OE_CC_PROCESSOR_TEMP

24 OE_CONC_REQUEST_IFACE OE_CONC_REQUEST_IFACE

25 OE_COPY_LINE_SORT_TMP OE_COPY_LINE_SORT_TMP

26 OE_CREDIT_BALANCES_ALL OE_CREDIT_BALANCES_ALL

27 OE_CREDIT_CHECK_RULES OE_CREDIT_CHECK_RULES

28 OE_CREDIT_EXPOSURE_TEMP OE_CREDIT_EXPOSURE_TEMP

29 OE_CREDIT_HIERARCHY_TEMP OE_CREDIT_HIERARCHY_TEMP

30 OE_CREDIT_SUMMARIES OE_CREDIT_SUMMARIES

31 OE_CREDITS_IFACE_ALL OE_CREDITS_IFACE_ALL

32 OE_CUST_ITEM_SETTINGS OE_CUST_ITEM_SETTINGS

33 OE_CUST_TOTAL_AMTS_ALL OE_CUST_TOTAL_AMTS_ALL

34 OE_CUSTOM_ACTIONS OE_CUSTOM_ACTIONS

35 OE_CUSTOMER_INFO_IFACE_ALL OE_CUSTOMER_INFO_IFACE_ALL

36 OE_DEF_ATTR_CONDNS OE_DEF_ATTR_CONDNS

37 OE_DEF_ATTR_DEF_RULES OE_DEF_ATTR_DEF_RULES

38 OE_DEF_CONDITIONS OE_DEF_CONDITIONS

39 OE_DEF_CONDITIONS_TL OE_DEF_CONDITIONS_TL

40 OE_DEF_CONDN_ELEMS OE_DEF_CONDN_ELEMS

41 OE_DEFAULT_ACTIONS OE_DEFAULT_ACTIONS

42 OE_DOC_SEQUENCE_AUDIT OE_DOC_SEQUENCE_AUDIT

43 OE_DROP_SHIP_SOURCES OE_DROP_SHIP_SOURCES

44 OE_EM_INFORMATION_ALL OE_EM_INFORMATION_ALL

45 OE_EVENT_ATTRIBUTES OE_EVENT_ATTRIBUTES

46 OE_EXP_INTERFACE_ERRORS OE_EXP_INTERFACE_ERRORS

47 OE_EXPOSURE_INTERFACE OE_EXPOSURE_INTERFACE

48 OE_FOLDER_EXTENSIONS OE_FOLDER_EXTENSIONS

49 OE_HEADER_ACKS OE_HEADER_ACKS

50 OE_HEADERS_EBS_LOG OE_HEADERS_EBS_LOG

51 OE_HEADERS_IFACE_ALL OE_HEADERS_IFACE_ALL

52 OE_HOLD_AUTHORIZATIONS OE_HOLD_AUTHORIZATIONS

53 OE_HOLD_DEFINITIONS OE_HOLD_DEFINITIONS

54 OE_HOLD_RELEASES OE_HOLD_RELEASES

55 OE_HOLD_SOURCES_ALL OE_HOLD_SOURCES_ALL

56 OE_INVOICE_NUMBERS OE_INVOICE_NUMBERS

57 OE_ITEM_CUST_VOLS_ALL OE_ITEM_CUST_VOLS_ALL

58 OE_LINE_ACKS OE_LINE_ACKS

59 OE_LINE_SETS OE_LINE_SETS

60 OE_LINES_EBS_LOG OE_LINES_EBS_LOG

61 OE_LINES_IFACE_ALL OE_LINES_IFACE_ALL

62 OE_LOT_SERIAL_NUMBERS OE_LOT_SERIAL_NUMBERS

63 OE_LOTSERIAL_ACKS OE_LOTSERIAL_ACKS

64 OE_LOTSERIALS_IFACE_ALL OE_LOTSERIALS_IFACE_ALL

65 OE_NOTES_OBJECT_REFS OE_NOTES_OBJECT_REFS

66 OE_NOTES_OBJECT_REFS_TL OE_NOTES_OBJECT_REFS_TL

67 OE_NOTES_RULE_ELEMENTS OE_NOTES_RULE_ELEMENTS

68 OE_NOTES_RULES OE_NOTES_RULES

69 OE_ORDER_HEADER_HISTORY OE_ORDER_HEADER_HISTORY

70 OE_ORDER_HEADERS_ALL OE_ORDER_HEADERS_ALL

71 OE_ORDER_HEADERS_ALL_EFC OE_ORDER_HEADERS_ALL_EFC

72 OE_ORDER_HOLDS_ALL OE_ORDER_HOLDS_ALL

73 OE_ORDER_LINES_ALL OE_ORDER_LINES_ALL

74 OE_ORDER_LINES_HISTORY OE_ORDER_LINES_HISTORY

75 OE_ORDER_NUMBER_SOURCES OE_ORDER_NUMBER_SOURCES

76 OE_ORDER_PRICE_ATTRIBS OE_ORDER_PRICE_ATTRIBS

77 OE_ORDER_SOURCES OE_ORDER_SOURCES

78 OE_PAYMENT_TYPES_ALL OE_PAYMENT_TYPES_ALL

79 OE_PAYMENT_TYPES_TL OE_PAYMENT_TYPES_TL

80 OE_PAYMENTS OE_PAYMENTS

81 OE_PAYMENTS_HISTORY OE_PAYMENTS_HISTORY

82 OE_PAYMENTS_IFACE_ALL OE_PAYMENTS_IFACE_ALL

83 OE_PC_ASSIGNMENTS OE_PC_ASSIGNMENTS

84 OE_PC_CONDITIONS OE_PC_CONDITIONS

85 OE_PC_CONDITIONS_TL OE_PC_CONDITIONS_TL

86 OE_PC_CONSTRAINTS OE_PC_CONSTRAINTS

87 OE_PC_EXCLUSIONS OE_PC_EXCLUSIONS

88 OE_PC_RSET_SEL_COLS OE_PC_RSET_SEL_COLS

89 OE_PC_RSETS OE_PC_RSETS

90 OE_PC_RSETS_TL OE_PC_RSETS_TL

91 OE_PC_VALIDATION_PKGS OE_PC_VALIDATION_PKGS

92 OE_PC_VTMPLT_COLS OE_PC_VTMPLT_COLS

93 OE_PC_VTMPLTS OE_PC_VTMPLTS

94 OE_PC_VTMPLTS_TL OE_PC_VTMPLTS_TL

95 OE_PRICE_ADJ_ASSOCS OE_PRICE_ADJ_ASSOCS

96 OE_PRICE_ADJ_ATTRIBS OE_PRICE_ADJ_ATTRIBS

97 OE_PRICE_ADJ_EBS_LOG OE_PRICE_ADJ_EBS_LOG

98 OE_PRICE_ADJS_HISTORY OE_PRICE_ADJS_HISTORY

99 OE_PRICE_ADJS_IFACE_ALL OE_PRICE_ADJS_IFACE_ALL

100 OE_PRICE_ADJUSTMENTS OE_PRICE_ADJUSTMENTS

101 OE_PRICE_ATTRIB_EBS_LOG OE_PRICE_ATTRIB_EBS_LOG

102 OE_PRICE_ATTS_IFACE_ALL OE_PRICE_ATTS_IFACE_ALL

103 OE_PROCESSING_MSGS OE_PROCESSING_MSGS

104 OE_PROCESSING_MSGS_TL OE_PROCESSING_MSGS_TL

105 OE_PURGE_ORDERS OE_PURGE_ORDERS

106 OE_PURGE_SETS OE_PURGE_SETS

107 OE_REASONS OE_REASONS

108 OE_RESERVATION_SETS OE_RESERVATION_SETS

109 OE_RESERVTNS_IFACE_ALL OE_RESERVTNS_IFACE_ALL

110 OE_RETROBILL_REQUESTS OE_RETROBILL_REQUESTS

111 OE_RSV_SET_DETAILS OE_RSV_SET_DETAILS

112 OE_SALES_CREDIT_HISTORY OE_SALES_CREDIT_HISTORY

113 OE_SALES_CREDIT_TYPES OE_SALES_CREDIT_TYPES

114 OE_SALES_CREDITS OE_SALES_CREDITS

115 OE_SELECTED_ITEMS OE_SELECTED_ITEMS

116 OE_SETS 0 OE_SETS

117 OE_SYS_PARAMETER_DEF_B OE_SYS_PARAMETER_DEF_B

118 OE_SYS_PARAMETER_DEF_TL OE_SYS_PARAMETER_DEF_TL

119 OE_SYS_PARAMETERS_ALL OE_SYS_PARAMETERS_ALL

120 OE_SYSTEM_PARAMETERS_ALL OE_SYSTEM_PARAMETERS_ALL

121 OE_SYSTEM_PARAMS_UPG OE_SYSTEM_PARAMS_UPG

122 OE_TRANSACTION_TYPES_ALL OE_TRANSACTION_TYPES_ALL

123 OE_TRANSACTION_TYPES_TL OE_TRANSACTION_TYPES_TL

124 OE_UI_QUERIES_TL OE_UI_QUERIES_TL

125 OE_UI_QUERY_COLUMNS OE_UI_QUERY_COLUMNS

126 OE_UPGRADE_DISTRIBUTION OE_UPGRADE_DISTRIBUTION

127 OE_UPGRADE_ERRORS OE_UPGRADE_ERRORS

128 OE_UPGRADE_LOG OE_UPGRADE_LOG

129 OE_UPGRADE_PC_ATTR_MAP OE_UPGRADE_PC_ATTR_MAP

130 OE_UPGRADE_PC_CONDNS OE_UPGRADE_PC_CONDNS

131 OE_UPGRADE_PC_SCOPE OE_UPGRADE_PC_SCOPE

132 OE_UPGRADE_PC_TEMP OE_UPGRADE_PC_TEMP

133 OE_UPGRADE_WF_ACT_MAP OE_UPGRADE_WF_ACT_MAP

134 OE_UPGRADE_WF_HIST_TEMP OE_UPGRADE_WF_HIST_TEMP

135 OE_UPGRADE_WF_OBS_CODES OE_UPGRADE_WF_OBS_CODES

136 OE_UPGRADE_WF_VLD_CYC OE_UPGRADE_WF_VLD_CYC

137 OE_UPGRADE_WSH_IFACE OE_UPGRADE_WSH_IFACE

138 OE_WORKFLOW_ASSIGNMENTS OE_WORKFLOW_ASSIGNMENTS

139 OM_ID_LIST_TMP OM_ID_LIST_TMP

140 OM_SETUP_VALID_ENTITIES OM_SETUP_VALID_ENTITIES

141 OM_SETUP_VALID_ERRM OM_SETUP_VALID_ERRM

142 OM_SETUP_VALID_PROF_OPT OM_SETUP_VALID_PROF_OPT

143 OM_SETUP_VALID_REP OM_SETUP_VALID_REP

144 ONT_DBI_CHANGE_LOG ONT_DBI_CHANGE_LOG

145 ONT_PRICE_ADJ_TEMP_ONT ONT_PRICE_ADJ_TEMP_ONT

146 ONT_PRT_MARGIN_ANA_ERR ONT_PRT_MARGIN_ANA_ERR

147 ONT_PRT_MARGIN_ANALYSIS ONT_PRT_MARGIN_ANALYSIS

148 ONT_WF_SKIP_LOG ONT_WF_SKIP_LOG

149 OE_CC_TEMP

150 OE_SCH_ID_LIST_TMP

FIXED ASSTETS

Un Changed = 179

New Tables = 19

Deleted = 0

11i TABLES R12 TABLES

1 FA_ACE_BOOKS FA_ACE_BOOKS

2 FA_ADD_WARRANTIES FA_ADD_WARRANTIES

3 FA_ADDITION_REP_ITF FA_ADDITION_REP_ITF

4 FA_ADDITIONS_B FA_ADDITIONS_B

5 FA_ADDITIONS_TL FA_ADDITIONS_TL

6 FA_ADJUST_REP_ITF FA_ADJUST_REP_ITF

7 FA_ADJUSTMENTS FA_ADJUSTMENTS

8 FA_AMORT_SCHEDULES FA_AMORT_SCHEDULES

9 FA_ARCHIVE_HISTORY FA_ARCHIVE_HISTORY

10 FA_ASSET_HIERARCHY FA_ASSET_HIERARCHY

11 FA_ASSET_HIERARCHY_PURPOSE FA_ASSET_HIERARCHY_PURPOSE

12 FA_ASSET_HIERARCHY_VALUES FA_ASSET_HIERARCHY_VALUES

13 FA_ASSET_HISTORY FA_ASSET_HISTORY

14 FA_ASSET_INVOICES FA_ASSET_INVOICES

15 FA_ASSET_KEYWORDS FA_ASSET_KEYWORDS

16 FA_ASSET_LISTING_REP_ITF FA_ASSET_LISTING_REP_ITF

17 FA_BALANCES_REP_ITF FA_BALANCES_REP_ITF

18 FA_BALANCES_REPORT FA_BALANCES_REPORT

19 FA_BALANCES_REPORT_GT FA_BALANCES_REPORT_GT

20 FA_BONUS_RATES FA_BONUS_RATES

21 FA_BONUS_RULES FA_BONUS_RULES

22 FA_BOOK_CONTROLS FA_BOOK_CONTROLS

23 FA_BOOK_CONTROLS_HISTORY FA_BOOK_CONTROLS_HISTORY

24 FA_BOOKS FA_BOOKS

25 FA_BOOKS_GROUPS FA_BOOKS_GROUPS

26 FA_BOOKS_SUMMARY FA_BOOKS_SUMMARY

27 FA_BUDGET_DISTRIBUTION FA_BUDGET_DISTRIBUTION

28 FA_BUDGET_INTERFACE FA_BUDGET_INTERFACE

29 FA_CALENDAR_PERIODS FA_CALENDAR_PERIODS

30 FA_CALENDAR_TYPES FA_CALENDAR_TYPES

31 FA_CAP_REP_ITF FA_CAP_REP_ITF

32 FA_CAPITAL_BUDGET FA_CAPITAL_BUDGET

33 FA_CATEGORIES_B FA_CATEGORIES_B

34 FA_CATEGORIES_TL FA_CATEGORIES_TL

35 FA_CATEGORY_BOOK_DEFAULTS FA_CATEGORY_BOOK_DEFAULTS

36 FA_CATEGORY_BOOKS FA_CATEGORY_BOOKS

37 FA_CEILING_TYPES FA_CEILING_TYPES

38 FA_CEILINGS FA_CEILINGS

39 FA_CONVENTION_TYPES FA_CONVENTION_TYPES

40 FA_CONVENTIONS FA_CONVENTIONS

41 FA_COSTCLEAR_REP_ITF FA_COSTCLEAR_REP_ITF

42 FA_DEFERRED_DEPRN FA_DEFERRED_DEPRN

43 FA_DELETED_MASS_ADDITIONS FA_DELETED_MASS_ADDITIONS

44 FA_DEPRN_BASIS_RULES FA_DEPRN_BASIS_RULES

45 FA_DEPRN_DETAIL FA_DEPRN_DETAIL

46 FA_DEPRN_OVERRIDE FA_DEPRN_OVERRIDE

47 FA_DEPRN_PERIODS FA_DEPRN_PERIODS

48 FA_DEPRN_REP_ITF FA_DEPRN_REP_ITF

49 FA_DEPRN_RULE_DETAILS FA_DEPRN_RULE_DETAILS

50 FA_DEPRN_SUMMARY FA_DEPRN_SUMMARY

51 FA_DEPRN_TAX_REP_ITF FA_DEPRN_TAX_REP_ITF

52 FA_DEPRN_TAX_REP_NBVS FA_DEPRN_TAX_REP_NBVS

53 FA_DISTRIBUTION_ACCOUNTS FA_DISTRIBUTION_ACCOUNTS

54 FA_DISTRIBUTION_DEFAULTS FA_DISTRIBUTION_DEFAULTS

55 FA_DISTRIBUTION_HISTORY FA_DISTRIBUTION_HISTORY

56 FA_DISTRIBUTION_SETS FA_DISTRIBUTION_SETS

57 FA_EXCLUDE_HIERARCHY_LEVELS FA_EXCLUDE_HIERARCHY_LEVELS

58 FA_EXT_INV_RETIREMENTS FA_EXT_INV_RETIREMENTS

59 FA_FISCAL_YEAR FA_FISCAL_YEAR

60 FA_FLAT_RATES FA_FLAT_RATES

61 FA_FORMULAS FA_FORMULAS

62 FA_GROUP_ASSET_DEFAULT FA_GROUP_ASSET_DEFAULT

63 FA_GROUP_ASSET_RULES FA_GROUP_ASSET_RULES

64 FA_GROUP_ASSETS FA_GROUP_ASSETS

65 FA_GROUP_DEPRN_DETAIL FA_GROUP_DEPRN_DETAIL

66 FA_GROUP_DEPRN_RATES FA_GROUP_DEPRN_RATES

67 FA_GROUP_DEPRN_SUMMARY FA_GROUP_DEPRN_SUMMARY

68 FA_GROUP_REP_ITF FA_GROUP_REP_ITF

69 FA_HIERARCHY_CONTROLS FA_HIERARCHY_CONTROLS

70 FA_HIERARCHY_DISTRIBUTIONS FA_HIERARCHY_DISTRIBUTIONS

71 FA_HIERARCHY_RULE_DETAILS FA_HIERARCHY_RULE_DETAILS

72 FA_HIERARCHY_RULE_SET FA_HIERARCHY_RULE_SET

73 FA_HR_RETIREMENT_DETAILS FA_HR_RETIREMENT_DETAILS

74 FA_HR_RETIREMENT_HEADERS FA_HR_RETIREMENT_HEADERS

75 FA_INS_LINES FA_INS_LINES

76 FA_INS_MST_POLS FA_INS_MST_POLS

77 FA_INS_POLICIES FA_INS_POLICIES

78 FA_INS_VALUES FA_INS_VALUES

79 FA_INV_COMPARE_REP_ITF FA_INV_COMPARE_REP_ITF

80 FA_INV_INTERFACE FA_INV_INTERFACE

81 FA_INVENTORY FA_INVENTORY

82 FA_INVMISS_REP_ITF FA_INVMISS_REP_ITF

83 FA_INVOICE_TRANSACTIONS FA_INVOICE_TRANSACTIONS

84 FA_ITC_RATES FA_ITC_RATES

85 FA_ITC_RECAPTURE_RATES FA_ITC_RECAPTURE_RATES

86 FA_JOURNAL_ENTRIES FA_JOURNAL_ENTRIES

87 FA_LEASE_PAYMENT_ITEMS FA_LEASE_PAYMENT_ITEMS

88 FA_LEASE_PAYMENTS FA_LEASE_PAYMENTS

89 FA_LEASE_SCHEDULES FA_LEASE_SCHEDULES

90 FA_LEASES FA_LEASES

91 FA_LIFE_DERIVATION_INFO FA_LIFE_DERIVATION_INFO

92 FA_LOCATIONS FA_LOCATIONS

93 FA_LOOKUP_TYPES_B FA_LOOKUP_TYPES_B

94 FA_LOOKUP_TYPES_TL FA_LOOKUP_TYPES_TL

95 FA_LOOKUPS_B FA_LOOKUPS_B

96 FA_LOOKUPS_TL FA_LOOKUPS_TL

97 FA_MAINT_EVENTS FA_MAINT_EVENTS

98 FA_MAINT_REP_ITF FA_MAINT_REP_ITF

99 FA_MAINT_SCHEDULE_DTL FA_MAINT_SCHEDULE_DTL

100 FA_MAINT_SCHEDULE_HDR FA_MAINT_SCHEDULE_HDR

101 FA_MASS_ADDITIONS FA_MASS_ADDITIONS

102 FA_MASS_CHANGES FA_MASS_CHANGES

103 FA_MASS_CHANGES_ITF FA_MASS_CHANGES_ITF

104 FA_MASS_EXT_RET_EXCEPTS FA_MASS_EXT_RET_EXCEPTS

105 FA_MASS_EXT_RETIREMENTS FA_MASS_EXT_RETIREMENTS

106 FA_MASS_EXTERNAL_TRANSFERS FA_MASS_EXTERNAL_TRANSFERS

107 FA_MASS_RECLASS FA_MASS_RECLASS

108 FA_MASS_RECLASS_ITF FA_MASS_RECLASS_ITF

109 FA_MASS_RET_EXCEPTS FA_MASS_RET_EXCEPTS

110 FA_MASS_RETIREMENTS FA_MASS_RETIREMENTS

111 FA_MASS_REVAL_REP_ITF FA_MASS_REVAL_REP_ITF

112 FA_MASS_REVALUATION_RULES FA_MASS_REVALUATION_RULES

113 FA_MASS_REVALUATIONS FA_MASS_REVALUATIONS

114 FA_MASS_TAX_ADJUSTMENTS FA_MASS_TAX_ADJUSTMENTS

115 FA_MASS_TRANSFERS FA_MASS_TRANSFERS

116 FA_MASS_UPDATE_BATCH_DETAILS FA_MASS_UPDATE_BATCH_DETAILS

117 FA_MASS_UPDATE_BATCH_HEADERS FA_MASS_UPDATE_BATCH_HEADERS

118 FA_MASSADD_DISTRIBUTIONS FA_MASSADD_DISTRIBUTIONS

119 FA_MASSADD_REP_ITF FA_MASSADD_REP_ITF

120 FA_MC_ADJUSTMENTS FA_MC_ADJUSTMENTS

121 FA_MC_ASSET_INVOICES FA_MC_ASSET_INVOICES

122 FA_MC_BOOK_CONTROLS FA_MC_BOOK_CONTROLS

123 FA_MC_BOOKS FA_MC_BOOKS

124 FA_MC_BOOKS_GROUPS FA_MC_BOOKS_GROUPS

125 FA_MC_BOOKS_RATES FA_MC_BOOKS_RATES

126 FA_MC_BOOKS_SUMMARY FA_MC_BOOKS_SUMMARY

127 FA_MC_CONVERSION_HISTORY FA_MC_CONVERSION_HISTORY

128 FA_MC_CONVERSION_RATES FA_MC_CONVERSION_RATES

129 FA_MC_DEFERRED_DEPRN FA_MC_DEFERRED_DEPRN

130 FA_MC_DEPRN_DETAIL FA_MC_DEPRN_DETAIL

131 FA_MC_DEPRN_PERIODS FA_MC_DEPRN_PERIODS

132 FA_MC_DEPRN_SUMMARY FA_MC_DEPRN_SUMMARY

133 FA_MC_GROUP_DEPRN_DETAIL FA_MC_GROUP_DEPRN_DETAIL

134 FA_MC_GROUP_DEPRN_SUMMARY FA_MC_GROUP_DEPRN_SUMMARY

135 FA_MC_MASS_RATES FA_MC_MASS_RATES

136 FA_MC_RETIREMENTS FA_MC_RETIREMENTS

137 FA_METHODS FA_METHODS

138 FA_MRC_INQ_FINANCIALS FA_MRC_INQ_FINANCIALS

139 FA_PARALLEL_WORKERS FA_PARALLEL_WORKERS

140 FA_PERIOD_MAPS FA_PERIOD_MAPS

141 FA_PERIODIC_PRODUCTION FA_PERIODIC_PRODUCTION

142 FA_PLSQL_DEBUG FA_PLSQL_DEBUG

143 FA_PRICE_INDEX_VALUES FA_PRICE_INDEX_VALUES

144 FA_PRICE_INDEXES FA_PRICE_INDEXES

145 FA_PRODUCTION_INTERFACE FA_PRODUCTION_INTERFACE

146 FA_PROJECT_REP_ITF FA_PROJECT_REP_ITF

147 FA_PROPTAX_REP_ITF FA_PROPTAX_REP_ITF

148 FA_RATES FA_RATES

149 FA_RECLASS_REP_ITF FA_RECLASS_REP_ITF

150 FA_RESERVE_LEDGER FA_RESERVE_LEDGER

151 FA_RESERVE_LEDGER_GT FA_RESERVE_LEDGER_GT

152 FA_RETIRE_REP_ITF FA_RETIRE_REP_ITF

153 FA_RETIREMENTS FA_RETIREMENTS

154 FA_RX_ATTRSETS_B FA_RX_ATTRSETS_B

155 FA_RX_ATTRSETS_TL FA_RX_ATTRSETS_TL

156 FA_RX_DYNAMIC_COLUMNS FA_RX_DYNAMIC_COLUMNS

157 FA_RX_LOV FA_RX_LOV

158 FA_RX_MULTIFORMAT_REPS FA_RX_MULTIFORMAT_REPS

159 FA_RX_REP_COLUMNS_B FA_RX_REP_COLUMNS_B

160 FA_RX_REP_COLUMNS_TL FA_RX_REP_COLUMNS_TL

161 FA_RX_REP_PARAMETERS FA_RX_REP_PARAMETERS

162 FA_RX_REPORTS FA_RX_REPORTS

163 FA_RX_SECURITY FA_RX_SECURITY

164 FA_RX_SUMMARY_TL FA_RX_SUMMARY_TL

165 FA_SHORT_TAX_RESERVES FA_SHORT_TAX_RESERVES

166 FA_SUPER_GROUP_RULES FA_SUPER_GROUP_RULES

167 FA_SUPER_GROUPS FA_SUPER_GROUPS

168 FA_SYSTEM_CONTROLS FA_SYSTEM_CONTROLS

169 FA_TAX_INTERFACE FA_TAX_INTERFACE

170 FA_TAX_REPORT FA_TAX_REPORT

171 FA_TRACK_MEMBERS FA_TRACK_MEMBERS

172 FA_TRANSACTION_HEADERS FA_TRANSACTION_HEADERS

173 FA_TRANSFER_DETAILS FA_TRANSFER_DETAILS

174 FA_TRANSFER_REP_ITF FA_TRANSFER_REP_ITF

175 FA_TRX_REFERENCES FA_TRX_REFERENCES

176 FA_WARRANTIES FA_WARRANTIES

177 FA_WHATIF_ITF FA_WHATIF_ITF

178 JE_DE_FA_SUMMARY JE_DE_FA_SUMMARY

179 JE_HU_BALANCES_REPORT JE_HU_BALANCES_REPORT

180 FA_ASSET_FAILURES_GT

181 FA_BOOK_CONTROLS_GT

182 FA_DEFERRED_DEPRN_EVENTS

183 FA_DEPRN_DETAIL_H

184 FA_DEPRN_EVENTS

185 FA_DEPRN_SUMMARY_H

186 FA_INQUIRY_TRX_GT

187 FA_MASS_ADDITIONS_GT

188 FA_MASS_TAX_ADJ_REP_T

189 FA_MC_DEPRN_DETAIL_H

190 FA_MC_DEPRN_SUMMARY_H

191 FA_TRANSACTION_INTERFACE

192 FA_WORKER_JOBS

193 FA_XLA_EXT_HEADERS_B_GT

194 FA_XLA_EXT_LINES_B_GT

195 FA_XLA_EXT_LINES_STG_GT

196 FA_XLA_EXT_LINES_TL_GT

197 FA_XLA_UPG_EVENTS_GT

198 FA_XLA_UPG_HEADERS_GT

Base tables for Procure To Pay

Base tables for Procure To Pay Requisition

po_requisition_headers_all

po_requisition_lines_all ( segment1 ========== requisition number)

po_req_distributions_all

Purchase order

po_headers_all

po_lines_all

po_distributions_all

po_line_locations_all

Receipt

rcv_shipment_headers

rcv_shipment_lines

rcv_transactions

quality result stored in qa_results table

Note: shipment_header_id is the link between rcv_shipment_headers and

rcv_shipment_linespo_header_id is the link between rcv_shipment_headers and

rcv_transaction

Invoices

ap_invoices_all

ap_invoice_distributions_all

Payments

ap_checks_all

ap_invoice_payments_all

ap_payment_schedules_all

Payment Reconcillation

ap_banks

ap_bank_branches

GL Transfer

gl_periods

gl_period_status

gl_set_of_books

glfv_charts_of_accounts