Charge Account Defaulting in PO

 

Charge account defaulting rules depend on 
a) Type of Item 
b) Destination Type
c) Destination Sub-inventory.

There are 3 kinds of Items used in Purchasing.

Expense Items - Referred to as Item A
Inventory Expense Items - Referred to as Item B
Inventory Asset Items - Referred to Item C


1) Expense Items - Referred to as Item A.
These items normally have the following attributes...

INVENTORY_ASSET_FLAG = N
PURCHASING_ITEM_FLAG = Y
INVENTORY_ITEM_FLAG = N

2) Inventory Expense Items - Referred to as Item B
These items normally have the following attributes...

INVENTORY_ASSET_FLAG = N
PURCHASING_ITEM_FLAG = Y
INVENTORY_ITEM_FLAG = Y


c) Inventory Asset Items - Referred to Item C
These items have the following attributes...

INVENTORY_ASSET_FLAG = Y
PURCHASING_ITEM_FLAG = Y
INVENTORY_ITEM_FLAG = Y
COSTING_ENABLED_FLAG = Y


2. DESTINATION TYPE :
The Destination type determines the final destination of the
items.
This can be of two types 
a) EXPENSE
b) INVENTORY - 



3. DESTINATION Subinventory:
When an Item is being received into Inventory , a sub-inventory 
needs to be specified. A subinventory can be 
a) ASSET subinventory
b) EXPENSE sub-inventory


The sql below will help in identifying what type of a 
subinventory , the item is being delivered INTO.


select 
substr(EXPENSE_ACCOUNT,1,6) Exp_act , 
substr(ENCUMBRANCE_ACCOUNT,1,7) Enc_act ,
ASSET_INVENTORY,
substr(SECONDARY_INVENTORY_NAME,1,15) S_name,
substr(DESCRIPTION,1,15) descrip,
substr(SOURCE_ORGANIZATION_ID,1,8) s_o_id
from 
MTL_SECONDARY_INVENTORIES
where 
SECONDARY_INVENTORY_NAME = '&destination_subinventory';

pass the value of DESTINATION_SUBINVENTORY 
from PO_DISTRIBUTIONS_ALL.DESTINATION_SUBINVENTORY

if the value of ASSET_INVENTORY = 1 then this is an ASSET subinventory.
if the value of ASSET_INVENTORY = 2 then this is NOT an ASSET subinventory.




3.Keeping in view of the types of Items and the destination mentioned above
These are the destination types that can be possible against each type of item

Item A can have ONLY one destination- EXPENSE

Item B can have the destination of 
a) EXPENSE
b) INVENTORY -- ASSET subinventory
c) INVENTORY -- EXPENSE subinventory

Item C can have the destination of 
a) EXPENSE
b) INVENTORY -- ASSET subinventory
c) INVENTORY -- EXPENSE subinventory



Defaulting Rules for 
1) Item A --- Defaults from the Expense a/c defined against the ITEM in the Receiving Organization.( Organization Items) 

=======================================================================================
2) Item B--- EXPENSE -Defaults from the Expense a/c defined against the ITEM in the
in the Receiving Organization.( Organization Items) 

2) Item B ---INVENTORY--- ASSET Subinventory .... charge account comes from 
a) EXPENSE a/c of the ASSET SUBINVENTORY in the RECEIVING Organization.
(This is ONLY if the PO Distribution , contains the Subinventory Information) 

b) If the PO distribution DOES NOT have a SUBINVENTORY information
Expense a/c defined in the Organizational Parameters of the Receiving Organization.

3) Item B ---INVENTORY--- EXPENSE subinventory -- comes from 
a) EXPENSE a/c of the EXPENSE SUBINVENTORY in the RECEIVING Organization.
(This is ONLY if the PO Distribution , contains the Subinventory Information) 

b) If the PO distribution DOES NOT have a SUBINVENTORY information
Expense a/c defined in the Organizational Parameters of the Receiving Organization.

=========================================================================================
4) Item C --- EXPENSE -Defaults from the Expense a/c defined against the ITEM in the
in the Receiving Organization.( Organization Items) 

5) Item C ---INVENTORY---ASSEST Subinventory .... charge account comes from 

a) Material a/c defined against the ASSET SUBINVENTORY /of the RECEIVING Organization.
(This is ONLY if the PO Distribution , contains the Subinventory Information)

b) Material a/c defined in the Organizational Parameters of the Receiving Organization.

6) Item C ---INVENTORY --EXPENSE Subinventory -- comes from 
a) Expense a/c defined against the EXPENSE Subinventory in Receiving Organization.
(This is ONLY if the PO Distribution , contains the Subinventory Information)

b) If the PO distirbution DOES NOT have a SUBINVENTORY information
Material a/c defined in the Organizational Parameters of the Receiving Organization.

References:
http://snroracle.blogspot.com/2013_10_01_archive.html

A New Custom Form in Oracle Apps

In this training article (for the readers of http://getappstraining.blogspot.com ), we will learn the steps needed to develop a custom Oracle Apps form from the very scratch.

In the previous chapter we learnt "how to customize an existing oracle delivered form"

Question: Why bother teaching this when Oracle fusion is destined to replace oracle forms by OA Framework?
Answer: Well firstly I am yet to hear an official word from Oracle in this regard, but  I agree it is highly likely that fusion will se demise of Oracle Forms. However more importantly Oracle will support current tech stack indefinitely, I.e Release 12 will be supported for foreseen time as per Apps Unlimited statement. Hence, many of the clients will keep using this technology for decades. Yes, I won't bother my kid learning Oracle form though. 


Question : Ok, what are the steps for building a screen from scratch?
Answer: Below steps in brief
A) Open up TEMPLATE.fmb, and save this as XXHELLOAPPS.fmb
B) Create a new window, by right clicking on Window/new
Name this window as XXHELLOAPPS,and assign it SubClass Type “WINDOW” from picklist.
C) Create a new canvas and name it XXHELLOAPPS , ensuring its Sublcass Type is “Content”
D) Make the windows property reference canvas XXHELLOAPPS and vice versa make the canvas reference windows XXHELLOAPPS.
E) Now create a block named XXHELLOAPPS . Lets keep this a control block for simplicity.
F) go to form level property, and set first navigation block to XXHELLOAPPS. 
G) Add a label and a field named “Hello_World” to this block.
    Go to pre-form to specify the new window and also the new blcok name in When-New-Form-Instance triggers.
   Open the program unit app_stand_window package body and the change the name of the window in Close_Window procedure.

H) Generate the form on PC using Control-T keystrokes. This will ensure that nothing critical has been missed out.
I)  FTP the form file to $XXPO_TOP/forms/US
Surely, this XX will be replaced by the naming convention at your client/company.
J)  cd to  $XXPO_TOP/forms/US
And f60gen on XXHELLOAPPS.fmb
This will create a file executable as XXHELLOAPPS.fmx
K) Go to Application Developer responsibility
Menu /applicaton/form
Register the form
L) Register the Forms Function
Have you read he article form functions[http://getappstraining.blogspot.com/2006/10/oracle-forms-functions-menus-and-their.html] yet?
This forms function must be registered against application "XX Purchasing".
M) Now add a menu item so that this forms function becomes available to specific responsibility.

Thats it, you will be able to open up this form from the responsibility.

Now some important notes:-
1. If you have a table based block, and if that block has some description type fields, then try not to fetch them from post query trigger. Instead, develop a view in apps schema and assign that view as base tale to this block. This has a benefit that users will be able to query on the description field if need be. Indeed you will need to do dml on the actual table yourself by overriding on-insert, on-update, on-delete and on-lock triggers.
2. For each block in the screen, create a form level package spec and package body. Your triggers in the block/block fields will make calls to that package.
3. Try not to do to much pl/sql within the form. Always do such database intensive operations in a database level package.
4. Try not using global variables, unless really needed. Give preference to the creation of form package variables.
5. In a multi record block, always add a field for Current Record Indicator.

Please let me know if anything is unclear. Feel free to ask your questions.

References:
http://oracle.anilpassi.com/a-new-custom-form-in-oracle-apps.html

FAQ Serial Numbers

 

1. What are the forms/programs?

Inventory > On-hand, Availability > Serial Numbers = INVITSNU.fmb
Inventory > On-hand, Availability > Generate serial numbers = Serial number generation (INV_SERIAL_NUMBER_PUB.GENERATE_SERIALS)

2. What tables?

1) MTL_SERIAL_NUMBERS: Serial numbers, this stores the serial numbers with a serial status noting if the serial is in stores, the current organization and subinventory, as well as mark ids that note if the serial number is locked..

2) MTL_SERIAL_NUMBERS_INTERFACE: Interface serial number table, this is the serial interface table used to note serial numbers that relate to transactions in the interface table (MTL_TRANSACTIONS_INTERFACE). See the Manufacturing Open Interface for more details.

3) MTL_SERIAL_NUMBERS_TEMP: Pending serial number table, this is the serial pending, temporary table used behind the scenes when transacting serial numbers. This goes hand-in-hand with the transaction temporary table (MTL_MATERIAL_TRANSACTIONS_TEMP).

4) MTL_UNIT_TRANSACTIONS: Unit transactions, this is the table used to track the history of serial numbers. Each unit transaction relates to a history record (MTL_MATERIAL_TRANSACTIONS) that outlines the transaction. The tables are joined by transaction_id. 

3. What is the difference between the various levels of serial uniqueness?

Here is an explanation of the uniqueness from the Inventory User's Guide page 5-162:

You use the Organization Parameters window to choose a type of serial number uniqueness for your organization. You can choose to enforce uniqueness Within inventory items, Within an organization, or Across organizations. The three levels for serial uniqueness are cumulative the definitions are as follows: 

• Within Inventory Items: 
Once you assign a serial number to a particular item you cannot assign the same serial number to the same item regardless of the organization. For example if you assign serial number SN100 to item A, you cannot assign serial number SN100 to any other instance of item A in any organization. This also includes CTO items derrived from base model A. However you could receive item B with serial number SN100 in any organization. 

• Within Organizations: 
In addition to the restrictions Within Inventory Items control, the same serial number cannot exist twice within the same organization. For example if you assign SN100 to item A, you will not be able to receive item B with the serial number SN100 in the same organization. However, you could receive item B with the serial number SN100 in any other organization. 

• Across Organizations: 
In addition to the restrictions Within Organizations, you cannot assign the same serial number to any other item regardless of the organization. For example if you assign SN100 to item A you will not be able to receive item B with the serial number SN100 in any organization. If you assign Across Organization uniqueness to any organization it restricts the serial generation in all other organizations. If one organization dictates Across Organizations, all other organizations must do so.

 

4.. What do the serial status numbers mean?

When one reviews the serial number table (MTL_SERIAL_NUMBERS) the column 'CURRENT_STATUS' indicates the status of a serial number. The column is populated with a number. For example, 3 means resides in stores. This means that the serial number has an associated onhand quantity and should be available to transact.

Here is a list of common serial number statuses and ids: 

Status Codes (ID and Description) 
--------------------- 
1 Defined but not used 
3 Resides in stores 
4 Issued out of stores 
5 Resides in intransit 
6 Pending status 
7 Resides in receiving 
8 Resides in WIP 

You can get a full list of the codes with the following SQL:

 

SELECT
lookup_type, 
lookup_code, 
meaning 
FROM mfg_lookups 
WHERE lookup_type = 'SERIAL_NUM_STATUS' 
ORDER BY lookup_type, lookup_code;

 

5.What is a mark id?

The serial number table (MTL_SERIAL_NUMBERS) holds a list of existing serial numbers in the Oracle Applications. When a serial number is being used by a transaction, mark ids are often populated until the transactions are complete. The mark ids act as a lock on the serial number and are meant to only be temporary until the transaction processes. The mark id columns are GROUP_MARK_ID, LINE_MARK_ID, LOT_LINE_MARK_ID. When the mark ids are populated, other transactions cannot use the serials. The Transact Move Order form is an example form that locks serials when they are allocated using the mark ids.
In the example of a move order allocation and assuming no lot control, the serial (MTL_SERIAL_NUMBERS) mark ids (GROUP_MARK_ID, LINE_MARK_ID, LOT_LINE_MARK_ID) match the pending transaction (MTL_MATERIAL_TRANSACTIONS_TEMP) transaction temp id (TRANSACTION_TEMP_ID).


6.What is the difference between serial generation 'At Receipt' vs. 'At Sales Order Issue'?

At inventory receipt 
Create and assign serial numbers when you 
receive the item. Thereafter, for any material 
transaction, you must provide a serial number 
for each unit. 

At sales order issue 
Create and assign serial numbers when you 
issue (ship) the item against a sales order. If 
you select this option, serial numbers are required 
at ship confirm. If you receive an item 
on an RMA (return material authorization), 
you must specify the same serial numbers you 
created at sales order issue. All other material 
transactions for this item bypass serial number 
information. 

No control 
Serial number control not established for this 
item. All material transactions involving this 
item bypass serial number information. 

Predefined 
Assign predefined serial numbers when you 
receive the item. Thereafter, for any material 
transaction, you must provide a serial number 
for each unit.

The serial generation of an item is also called the serial control code. One can also look up the serial control codes for an item via SQL. The list of items in the system is maintained in the table MTL_SYSTEM_ITEMS_B. The column SERIAL_NUMBER_CONTROL_CODE will list the current value of the serial generation. 
Here is a list of common serial control code ids and there descriptions: 

Control Codes (ID and Description) 
--------------------- 
1 No serial number control 
2 Predefined serial numbers 
5 Dynamic entry at inventory receipt 
6 Dynamic entry at sales order issue 

You can get a full list of the codes with the following SQL:
SELECT
lookup_type, 
lookup_code, 
meaning 
FROM mfg_lookups 
WHERE lookup_type = 'MTL_SERIAL_NUMBER' 
ORDER BY lookup_type, lookup_code;

7.How to track a serial number across organizations?
After transferring a serial number between organizations, it only appears in the current organization. The Onhand > Serial number query screen displays the current state of the serial number. It queries the serial number table (MTL_SERIAL_NUMBERS). The serial number table will only have one record for the serial number and item combination. The organization of the serial number is maintained in a column called, CURRENT_ORGANIZATION_ID. This maintains only the last organization to have the serial number. If the serial number changes organizations, the serial number will show only in the new organization. If a serial number is shipped to a customer, the serial is visible with status 'issued out of stores' in the last organization that owned the serial. 

To see the history of the serial number, one would look at the transaction history using the Transactions > Material Transactions form. You can query by item or serial number and see all related transactions. The form queries any transaction that touched the serial number. Unlike the serial number form that queried the serial's current state from MTL_SERIAL_NUMBERS, the material transaction screen queries against all transactions (MTL_MATERIAL_TRANSACTIONS) and looks at the serial number history table (MTL_UNIT_TRANSACTIONS).

Example -- The following query could be useful looking for all transactions of a given serial number -- Note that two queries are joined because the transaction history relates through the lot table if the item is lot controlled:
prompt
accept YourSerial DEFAULT 'JBP10000' prompt 'Please enter your serial (Default JBP10000): '
prompt

break on serial_number

select c.serial_number, a.transaction_id, a.transaction_type_id, a.transaction_quantity, 'No Lot'
from MTL_MATERIAL_TRANSACTIONS a, MTL_UNIT_TRANSACTIONS c
where a.TRANSACTION_ID = c.TRANSACTION_ID
and c.serial_number like '&YourSerial'
UNION
select c.serial_number, a.transaction_id, a.transaction_type_id, a.transaction_quantity, b.lot_number
from MTL_MATERIAL_TRANSACTIONS a, MTL_TRANSACTION_LOT_NUMBERS b, MTL_UNIT_TRANSACTIONS c
where a.TRANSACTION_ID = b.TRANSACTION_ID
and b.SERIAL_TRANSACTION_ID = c.TRANSACTION_ID
and c.serial_number like '&YourSerial'
/

8.How to enter serial number descriptions (or Descriptive Flexfields / DFF)?

You can enter descriptions for serial numbers using descriptive flexfields. 
There are two that would be helpful: Serial Attributes or Serial numbers 
Serial attributes apper in the onhand > serial number screen in the Serial Info tab with the column name of Attributes. This is similar to the serial entry screens that label the field attributes as well. The Serial numbers descriptive flexfield is visible upon placing the cursor in the descriptive flexfield field usually labled with two brackets like [] also called mug-handles.
To maintain descriptive flexfields for serial numbers:
Navigate to Inventory > Setup > Flexfield > Descriptive > Segments 
Query Serial Attributes or Serial numbers 
You could then setup descriptions for the serials
Read more about descriptive flexfields (DFF) also called attributes in the user's guide.

 

References:

http://snroracle.blogspot.com/2014/02/faq-serial-numbers.html

 

Oracle Purchasing Approval

 

In PO there are two methods to route documents for approval.
1.Approval Hierarchies (uses position hierarchies, A tree of hierarchy more than one person above to approve)

2.Employee/Supervisor Relationships (use employee/supervisor relationship, Just one person above to approve)
Approval Hierarchies

Purchasing utilizes positions as a roadmap to determine how and where documents will be routed once the approval process has been initiated. It is first necessary to have created all positions that are going to be used in the system. Once all positions have been created, it is necessary to build the position hierarchy.
Each position has approval limits, so when a purchase order exceeds the limits of the position, the purchase order is forwarded onto the next position in the Hierarchy
Employee/Supervisor Relationships
This type of hierarchy does not use the Approval Hierarchy form,but is defined by the employee/supervisor relationship. The supervisor of an employee is defined on the Assignment region of the Employee form
If the purchase order entered by the employee exceeds the approval limits, the purchase order is forwarded onto the employees’ supervisor, as defined on the Employee form
To implement this form of approval routing, you need only to define JOBS. The JOB will then serve as the tie to the Approval group, and based on the approval limits from the Approval Group, the Document will either be Approved or Forwarded to the Employees’ Supervisor

References:
http://2lyoracleapps.blogspot.com/

ERP-Enterprise Resource Planning

ERP is often a confusing terminology but to put it in simple terms: ERP is an acronym meaning Enterprise Resource Planning. It is a software package/solution most often used within the manufacturing environment. ERP is a business tool that the management uses to operate the business for the day-in and day-out. It is usually comprised of several modules such as a financial module, a distribution module and a production module. Each of these modules share information that is housed within the database structures on which the ERP system was coded.

ERP helps to break down barriers between departments within a company. For example, many times the sales department may be selling 25% more product than the production department produces. By utilizing an ERP system, the sales department, production department, operations management, shipping, financial department, purchasing department all have access to the up-to-date information that is needed to operate smoothly within any manufacturing environment.

Maximum Personalization on Purchase Requisition Form

We keep on creating personalization on Purchase Requisition screen as per business requirements, one fine day we found the limit. Oracle allows only maximum of 100 personalizations in a standard form its what we thought but digging deeper we found that numbers could be tweaked with fractions (eg: 10.1, 10.2,10.3,11,12)

Its very rare you will need more than 100-Personalizations in a form.

References:

http://2lyoracleapps.blogspot.com/

 

Oracle APPS Important Tables

Oracle APPS Important Tables

ONT- Order Management

Table Name Description 
OE_ORDER_HEADERS_ALL OE_ORDER_HEADERS_ALL stores header information for orders in Order Management. 
OE_ORDER_LINES_ALL OE_ORDER_LINES_ALL stores information for all order lines in Oracle Order Management. 
OE_ORDER_SOURCES Feeder System Names that create orders in Order Management tables. 
OE_ORDER_HOLDS_ALL This table stores information of all the orders and lines that are on hold and the link to hold sources and hold releases. 
OE_SALES_CREDITS This table stores information about sales credits. 
OE_TRANSACTION_TYPES_ALL This table stores information about the order and line transaction types 
WSH_DELIVERY_ASSIGNMENTS Delivery Assignments 
WSH_DELIVERY_DETAILS Delivery Details 
WSH_NEW_DELIVERIES Deliveries 
WSH_TRIPS Trips 
WSH_TRIP_STOPS Trip Stops 


PO - Purchasing

Table Name Description 
PO_ACTION_HISTORY Document approval and control action history table 
PO_AGENTS Buyers table 
PO_DISTRIBUTIONS_ALL Purchase order distributions 
PO_HEADERS_ALL Document headers (for purchase orders, purchase agreements, quotations, RFQs) 
PO_LINES_ALL Purchase document lines (for purchase orders, purchase agreements, quotations, RFQs) 
PO_LINE_LOCATIONS_ALL Document shipment schedules (for purchase orders, purchase agreements, quotations, RFQs) 
PO_RELEASES_ALL Purchase order releases 
PO_LINES_ARCHIVE_ALL Archived purchase order lines 
PO_LINE_LOCATIONS_ARCHIVE_ALL Archived purchase order shipments 
PO_HEADERS_ARCHIVE_ALL Archived purchase orders 
PO_LINE_TYPES_B Line types 
PO_RELEASES_ARCHIVE_ALL Archived releases 
PO_REQUISITION_HEADERS_ALL Requisition headers 
PO_REQUISITION_LINES_ALL Requisition lines 
PO_REQ_DISTRIBUTIONS_ALL Requisition distributions 
RCV_TRANSACTIONS Receiving transactions 
RCV_SHIPMENT_HEADERS Shipment and receipt header information 
RCV_SHIPMENT_LINES Receiving shipment line information 

Oracle APPS Important Tables

ONT- Order Management

Table Name Description 
OE_ORDER_HEADERS_ALL OE_ORDER_HEADERS_ALL stores header information for orders in Order Management. 
OE_ORDER_LINES_ALL OE_ORDER_LINES_ALL stores information for all order lines in Oracle Order Management. 
OE_ORDER_SOURCES Feeder System Names that create orders in Order Management tables. 
OE_ORDER_HOLDS_ALL This table stores information of all the orders and lines that are on hold and the link to hold sources and hold releases. 
OE_SALES_CREDITS This table stores information about sales credits. 
OE_TRANSACTION_TYPES_ALL This table stores information about the order and line transaction types 
WSH_DELIVERY_ASSIGNMENTS Delivery Assignments 
WSH_DELIVERY_DETAILS Delivery Details 
WSH_NEW_DELIVERIES Deliveries 
WSH_TRIPS Trips 
WSH_TRIP_STOPS Trip Stops 


PO - Purchasing

Table Name Description 
PO_ACTION_HISTORY Document approval and control action history table 
PO_AGENTS Buyers table 
PO_DISTRIBUTIONS_ALL Purchase order distributions 
PO_HEADERS_ALL Document headers (for purchase orders, purchase agreements, quotations, RFQs) 
PO_LINES_ALL Purchase document lines (for purchase orders, purchase agreements, quotations, RFQs) 
PO_LINE_LOCATIONS_ALL Document shipment schedules (for purchase orders, purchase agreements, quotations, RFQs) 
PO_RELEASES_ALL Purchase order releases 
PO_LINES_ARCHIVE_ALL Archived purchase order lines 
PO_LINE_LOCATIONS_ARCHIVE_ALL Archived purchase order shipments 
PO_HEADERS_ARCHIVE_ALL Archived purchase orders 
PO_LINE_TYPES_B Line types 
PO_RELEASES_ARCHIVE_ALL Archived releases 
PO_REQUISITION_HEADERS_ALL Requisition headers 
PO_REQUISITION_LINES_ALL Requisition lines 
PO_REQ_DISTRIBUTIONS_ALL Requisition distributions 
RCV_TRANSACTIONS Receiving transactions 
RCV_SHIPMENT_HEADERS Shipment and receipt header information 
RCV_SHIPMENT_LINES Receiving shipment line information 

INV – Inventory

Table Name Description 
MTL_CATEGORIES_B Code combinations table for Item Category 
MTL_CATEGORY_SETS_B Category Sets 
MTL_CUSTOMER_ITEMS Customer item Information 
MTL_CUSTOMER_ITEM_XREFS Relationships between customer items and inventory items 
MTL_DEMAND Sales order demand and reservations 
MTL_DEMAND_HISTORIES Sales order demand and reservations 
MTL_ITEM_LOCATIONS Definitions for stock locators 
MTL_ITEM_REVISIONS_B Item revisions 
MTL_ITEM_TEMPLATES_B Item template definitions 
MTL_ITEM_TEMPL_ATTRIBUTES Item attributes and attribute values for a template 
MTL_LOT_NUMBERS Lot number definitions 
MTL_MATERIAL_TRANSACTIONS Material transaction table 
MTL_MATERIAL_TRANSACTIONS_TEMP Temporary table for processing material transactions 
MTL_ONHAND_QUANTITIES_DETAIL FIFO quantities by control level and receipt 
MTL_PARAMETERS Inventory control options and defaults 
MTL_RESERVATIONS Reservations 
MTL_SECONDARY_INVENTORIES Subinventory definitions 
MTL_SECONDARY_LOCATORS Item-subinventory-locator assignments 
MTL_SERIAL_NUMBERS Serial number definitions 
MTL_SYSTEM_ITEMS_B Inventory item definitions 
MTL_TRANSACTION_ACCOUNTS Material transaction distributions 
MTL_TRANSACTION_TYPES Inventory Transaction Types Table 
MTL_TXN_REQUEST_HEADERS Move Order headers table 
MTL_TXN_REQUEST_LINES Move order lines table 
MTL_UNIT_TRANSACTIONS Serial number transactions 


GL- General Ledger

Table Name Description 
GL_CODE_COMBINATIONS Stores valid account combinations 
GL_SETS_OF_BOOKS Stores information about the sets of books 
GL_IMPORT_REFERENCES Stores individual transactions from subledgers 
GL_DAILY_RATES Stores the daily conversion rates for foreign currency 

Transactions 
GL_PERIODS Stores information about the accounting periods 
GL_JE_HEADERS Stores journal entries 
GL_JE_LINES Stores the journal entry lines that you enter in the Enter Journals form 
GL_JE_BATCHES Stores journal entry batches 
GL_BALANCES Stores actual, budget, and encumbrance balances for detail and summary accounts 
GL_BUDGETS Stores Budget definitions 
GL_INTERFACE Import journal entry batches 
GL_BUDGET_INTERFACE Upload budget data from external sources 
GL_DAILY_RATES_INTERFACE Import daily conversion rates 

AR- Accounts Receivables

Table Name Description 
RA_CUST_TRX_TYPES_ALL Transaction type for invoices, commitments and credit memos 
RA_CUSTOMER_TRX_ALL Header-level information about invoices, debit memos, chargebacks, commitments and credit memos 
RA_CUSTOMER_TRX_LINES_ALL Invoice, debit memo, chargeback, credit memo and commitment lines 
RA_CUST_TRX_LINE_GL_DIST_ALL Accounting records for revenue, unearned revenue and unbilled receivables 
RA_CUST_TRX_LINE_SALESREPS_ALL Sales credit assignments for transactions 
AR_ADJUSTMENTS_ALL Pending and approved invoice adjustments 
RA_BATCHES_ALL 
AR_CASH_RECEIPTS_ALL Detailed receipt information 
AR_CASH_RECEIPT_HISTORY_ALL History of actions and status changes in the life cycle of a receipt 
AR_PAYMENT_SCHEDULES_ALL All transactions except adjustments and miscellaneous cash receipts 
AR_RECEIVABLE_APPLICATIONS_ALL Accounting information for cash and credit memo applications 
AR_TRANSACTION_HISTORY_ALL Life cycle of a transaction 
HZ_CUST_ACCOUNTS Stores information about customer accounts. 
HZ_CUSTOMER_PROFILES Credit information for customer accounts and customer account sites 
HZ_CUST_ACCT_SITES_ALL Stores all customer account sites across all operating units 
HZ_CUST_ACCT_RELATE_ALL Relationships between customer accounts 
HZ_CUST_CONTACT_POINTS This table is no longer used 
HZ_CUST_PROF_CLASS_AMTS Customer profile class amount limits for each currency 
HZ_CUST_SITE_USES_ALL Stores business purposes assigned to customer account sites. 
HZ_LOCATIONS Physical addresses 
HZ_ORG_CONTACTS People as contacts for parties 
HZ_ORG_CONTACT_ROLES Roles played by organization contacts 
HZ_PARTIES Information about parties such as organizations, people, and groups 
HZ_PARTY_SITES Links party to physical locations 
HZ_PARTY_SITE_USES The way that a party uses a particular site or address 
HZ_RELATIONSHIPS Relationships between entities 
HZ_RELATIONSHIP_TYPES Relationship types 

CE- Cash Management

Table Name Description 
CE_BANK_ACCOUNTS This table contains bank account information. Each bank account must be affiliated with one bank branch. 
CE_BANK_ACCT_BALANCES This table stores the internal bank account balances 
CE_BANK_ACCT_USES_ALL This table stores information about your bank account uses. 
CE_STATEMENT_HEADERS Bank statements 
CE_STATEMENT_LINES Bank statement lines 
CE_STATEMENT_HEADERS_INT Open interface for bank statements 
CE_STATEMENT_LINES_INTERFACE Open interface for bank statement lines 
CE_TRANSACTION_CODES Bank transaction codes 

AP- Accounts Payables

Table Name Description 
AP_ACCOUNTING_EVENTS_ALL Accounting events table 
AP_AE_HEADERS_ALL Accounting entry headers table 
AP_AE_LINES_ALL Accounting entry lines table 
AP_BANK_ACCOUNTS_ALL Bank Account Details 
AP_BANK_ACCOUNT_USES_ALL Bank Account Uses Information 
AP_BANK_BRANCHES Bank Branches 
AP_BATCHES_ALL Summary invoice batch information 
AP_CHECKS_ALL Supplier payment data 
AP_HOLDS_ALL Invoice hold information 
AP_INVOICES_ALL Detailed invoice records 
AP_INVOICE_LINES_ALL AP_INVOICE_LINES_ALL contains records for invoice lines entered manually, generated automatically or imported from the Open Interface. 
AP_INVOICE_DISTRIBUTIONS_ALL Invoice distribution line information 
AP.AP_INVOICE_PAYMENTS_ALL Invoice payment records 
AP_PAYMENT_DISTRIBUTIONS_ALL Payment distribution information 
AP_PAYMENT_HISTORY_ALL Maturity and reconciliation history for payments 
AP_PAYMENT_SCHEDULES_ALL Scheduled payment information on invoices 
AP_INTERFACE_REJECTIONS Information about data that could not be loaded by Payables Open Interface Import 
AP_INVOICES_INTERFACE Information used to create an invoice using Payables Open Interface Import 
AP_INVOICE_LINES_INTERFACE Information used to create one or more invoice distributions 
AP_SUPPLIERS AP_SUPPLIERS stores information about your supplier level attributes. 
AP_SUPPLIER_SITES_ALL AP_SUPPLIER_SITES_ALL stores information about your supplier site level attributes. 
AP_SUPPLIER_CONTACTS Stores Supplier Contacts 


FA – Fixed Assets

Table Name Description 
FA_ADDITIONS_B Descriptive information about assets 
FA_ADJUSTMENTS Information used by the posting program to generate journal entry lines in the general ledger 
FA_ASSET_HISTORY Historical information about asset reclassifications and unit adjustments 
FA_ASSET_INVOICES Accounts payable and purchasing information for each asset 
FA_BOOKS Financial information of each asset 
FA_BOOK_CONTROLS Control information that affects all assets in a depreciation book 
FA_CALENDAR_PERIODS Detailed calendar information 
FA_CALENDAR_TYPES General calendar information 
FA_CATEGORIES_B Default financial information for asset categories 
FA_CATEGORY_BOOKS Default financial information for an asset category and depreciation book combination 
FA_DEPRN_DETAIL Depreciation amounts charged to the depreciation expense account in each distribution line 
FA_DEPRN_PERIODS Information about each depreciation period 
FA_DEPRN_EVENTS Information about depreciation accounting events. 
FA_DEPRN_SUMMARY Depreciation information at the asset level 
FA_DISTRIBUTION_ACCOUNTS Table to store account ccids for all distributions for a book 
FA_DISTRIBUTION_DEFAULTS Distribution set information 
FA_DISTRIBUTION_HISTORY Employee, location, and Accounting Flexfield values assigned to each asset 
FA_DISTRIBUTION_SETS Header information for distribution sets 
FA_FORMULAS Depreciation rates for formula-based methods 
FA_LOCATIONS Location flexfield segment value combinations 
FA_MASS_ADDITIONS Information about assets that you want to automatically add to Oracle Assets from another system 
FA_METHODS Depreciation method information 
FA_RETIREMENTS Information about asset retirements and reinstatements 


HRMS- Human Resource Management System

Table Name Description 
HR_ALL_ORGANIZATION_UNITS Organization unit definitions. 
HR_ALL_POSITIONS_F Position definition information. 
HR_LOCATIONS_ALL Work location definitions. 
PER_ADDRESSES Address information for people 
PER_ALL_PEOPLE_F DateTracked table holding personal information for employees, applicants and other people. 
PER_ALL_ASSIGNMENTS_F Allocated Tasks 
PER_ANALYSIS_CRITERIA Flexfield combination table for the personal analysis key flexfield. 
PER_ASSIGNMENT_EXTRA_INFO Extra information for an assignment. 
PER_ASSIGNMENT_STATUS_TYPES Predefined and user defined assignment status types. 
PER_CONTRACTS_F The details of a persons contract of employment 
PER_CONTACT_RELATIONSHIPS Contacts and relationship details for dependents, beneficiaries, emergency contacts, parents etc. 
PER_GRADES Grade definitions for a business group. 
PER_JOBS Jobs defined for a Business Group 
PER_PAY_BASES Definitions of specific salary bases 
PER_PAY_PROPOSALS Salary proposals and performance review information for employee assignments 
PER_PEOPLE_EXTRA_INFO Extra information for a person 
PER_PERIODS_OF_PLACEMENT Periods of placement details for a non-payrolled worker 
PER_PERIODS_OF_SERVICE Period of service details for an employee. 
PER_PERSON_ANALYSES Special information types for a person 
PER_PERSON_TYPES Person types visible to specific Business Groups. 
PER_PERSON_TYPE_USAGES_F Identifies the types a person may be. 
PER_PHONES PER_PHONES holds phone numbers for current and ex-employees, current and ex-applicants and employee contacts. 
PER_SECURITY_PROFILES Security profile definitions to restrict user access to specific HRMS records 


PAY- Payroll

Table Name Description 
PAY_ACTION_INFORMATION Archived data stored by legislation 
PAY_ALL_PAYROLLS_F Payroll group definitions. 
PAY_ASSIGNMENT_ACTIONS Action or process results, showing which assignments have been processed by a specific payroll action, or process. 
PAY_ELEMENT_CLASSIFICATIONS Element classifications for legislation and information needs. 
PAY_ELEMENT_ENTRIES_F Element entry list for each assignment. 
PAY_ELEMENT_ENTRY_VALUES_F Actual input values for specific element entries. 
PAY_ELEMENT_LINKS_F Eligibility rules for an element type. 
PAY_ELEMENT_TYPES_F Element definitions. 
PAY_ELEMENT_TYPE_USAGES_F Used to store elements included or excluded from a defined run type. 
PAY_ORG_PAYMENT_METHODS_F Payment methods used by a Business Group. 
PAY_PAYMENT_TYPES Types of payment that can be processed by the system. 
PAY_PAYROLL_ACTIONS Holds information about a payroll process. 
PAY_PEOPLE_GROUPS People group flexfield information. 
PAY_PERSONAL_PAYMENT_METHODS_F Personal payment method details for an employee. 
PAY_RUN_RESULTS Result of processing a single element entry. 
PAY_RUN_RESULT_VALUES Result values from processing a single element entry. 
PAY_SECURITY_PAYROLLS List of payrolls and security profile access rules. 
PAY_INPUT_VALUES_F Input value definitions for specific elements. 


BOM – Bills Of Material 

Table Name Description 
BOM_DEPARTMENTS Departments 
BOM_DEPARTMENT_CLASSES Department classes 
BOM_DEPARTMENT_RESOURCES Resources associated with departments 
BOM_OPERATIONAL_ROUTINGS Routings 
BOM_OPERATION_NETWORKS Routing operation networks 
BOM_OPERATION_RESOURCES Resources on operations 
BOM_OPERATION_SEQUENCES Routing operations 
BOM_OPERATION_SKILLS 
BOM_RESOURCES Resources, overheads, material cost codes, and material overheads 
BOM_STANDARD_OPERATIONS Standard operations 
BOM_ALTERNATE_DESIGNATORS Alternate designators 
BOM_COMPONENTS_B Bill of material components 
BOM_STRUCTURES_B Bills of material 
BOM_STRUCTURE_TYPES_B Structure Type master table 




WIP – Work in Process 

Table Name Description 
WIP_DISCRETE_JOBS Discrete jobs 
WIP_ENTITIES Information common to jobs and schedules 
WIP_LINES Production lines 
WIP_MOVE_TRANSACTIONS Shop floor move transactions 
WIP_MOVE_TXN_ALLOCATIONS Move transaction allocations for repetitive schedules 
WIP_OPERATIONS Operations necessary for jobs and schedules 
WIP_OPERATION_NETWORKS Operation dependency 
WIP_OPERATION_OVERHEADS Overheads for operations in an average costing organization 
WIP_OPERATION_RESOURCES Resources necessary for operations 
WIP_OPERATION_YIELDS This table keeps all costing information for operation yield costing. 
WIP_TRANSACTIONS WIP resource transactions 
WIP_TRANSACTION_ACCOUNTS Debits and credits due to resource transactions 


FND – Appication Object Library

Table Name Description 
FND_APPLICATION Applications registered with Oracle Application Object Library 
FND_CONCURRENT_PROGRAMS Concurrent programs 
FND_CONCURRENT_REQUESTS Concurrent requests information 
FND_CURRENCIES Currencies enabled for use at your site 
FND_DATA_GROUPS Data groups registered with Oracle Application Object Library 
FND_FLEX_VALUES Valid values for flexfield segments 
FND_FLEX_VALUE_HIERARCHIES Child value ranges for key flexfield segment values 
FND_FLEX_VALUE_SETS Value sets used by both key and descriptive flexfields 
FND_FORM Application forms registered with Oracle Application Object Library 
FND_FORM_FUNCTIONS Functionality groupings 
FND_ID_FLEXS Registration information about key flexfields 
FND_ID_FLEX_SEGMENTS Key flexfield segments setup information and correspondences between table columns and key flexfield segments 
FND_ID_FLEX_STRUCTURES Key flexfield structure information 
FND_LOOKUP_TYPES Oracle Application Object Library QuickCodes 
FND_LOOKUP_VALUES QuickCode values 
FND_MENUS New menu tabl for Release 10SC 
FND_PROFILE_OPTIONS User profile options 
FND_PROFILE_OPTION_VALUES Values of user profile options defined at different profile levels 
FND_REQUEST_SETS Reports sets 
FND_REQUEST_SET_PROGRAMS Reports within report sets 
FND_REQUEST_SET_STAGES Stores request set stages 
FND_RESPONSIBILITY Responsibilities 
FND_RESP_FUNCTIONS Function Security 
FND_USER Application users 


JA - Asia/Pacific Localizations

Table Name Description 
JAI_CMN_BOE_HDRS Stores BOE header info when a BOE Invoice is created through IL 
JAI_CMN_BOE_DTLS Detail table for BOE Invoices 
JAI_CMN_TAXES_ALL Master table for Localization Taxes 
JAI_CMN_TAX_CTGS_ALL Stores tax categories and their link to excise ITEM classes. 
JAI_CMN_TAX_CTG_LINES Stores the tax lines for defined tax categories 
JAI_CMN_VENDOR_SITES Stores excise account related information about vendors. 
JAI_RGM_DEFINITIONS Stores regime information. 
JAI_RGM_TAXES This table stores tax details for transactions having TCS tax type. 
JAI_CMN_RG_23AC_I_TRXS Stores Information of RG23A/C records and known as Quantity Register. 
JAI_CMN_RG_23AC_II_TRXS Stores Information of RG23A/C Part II Details. Also known as Amount Register 
JAI_CMN_RG_23D_TRXS Quantity register for Trading Organizations 
JAI_CMN_RG_BALANCES Store the current balances of RG23A, RG23C and PLA Registers 
JAI_CMN_RG_PLA_TRXS Stores the Transaction Information of PLA Register. 
JAI_CMN_RG_PLA_HDRS Stores PLA header Infomation when a PLA invoice is created in AP module 
JAI_CMN_RG_PLA_DTLS Stores PLA Detail Information when a PLA Invoice is created in AP Module 


QP – Advanced Pricing 

Table Name Description 
QP_LIST_HEADERS_B QP_LIST_HEADERS_B stores the header information for all lists. List types can be, for example, Price Lists, Discount Lists or Promotions. 
QP_LIST_LINES QP_LIST_LINES stores all list lines for lists in QP_LIST_HEADERS_B. 
QP_PRICE_FORMULAS_B QP_PRICE_FORMULAS_B stores the pricing formula header information. 
QP_PRICE_FORMULA_LINES QP_PRICE_FORMULA_LINES stores each component that makes up the formula. 
QP_PRICING_ATTRIBUTES QP_PRICING_ATTRIBUTES stores product information and pricing attributes. 
QP_QUALIFIERS QP_QUALIFIERS stores qualifier attribute information. 






XLA - Subledger Accounting 

Table Name Description 
XLA_EVENTS The XLA_EVENTS table record all information related to a specific event. This table is created as a type XLA_ARRAY_EVENT_TYPE. 
XLA_TRANSACTION_ENTITIES The table XLA_ENTITIES contains information about sub-ledger document or transactions. 
XLA_AE_HEADERS The XLA_AE_HEADERS table stores subledger journal entries. There is a one-to-many relationship between accounting events and journal entry headers. 
XLA_AE_LINES The XLA_AE_LINES table stores the subledger journal entry lines. There is a one-to-many relationship between subledger journal entry headers and subledger journal entry lines. 
XLA_DISTRIBUTION_LINKS The XLA_DISTRIBUTION_LINKS table stores the link between transactions and subledger journal entry lines. 
XLA_ACCOUNTING_ERRORS The XLA_ACCOUNTING_ERRORS table stores the errors encountered during execution of the Accounting Program. 
XLA_ACCTG_METHODS_B The XLA_ACCTG_METHODS_B table stores Subledger Accounting Methods (SLAM) across products. SLAMs provided by development are not chart of accounts specific. Enabled SLAMs are assigned to ledgers. 
XLA_EVENT_TYPES_B The XLA_EVENT_TYPES_B table stores all event types that belong to an event class. 
XLA_GL_LEDGERS This table contains ledger information used by subledger accounting.

Table Name Description 
MTL_CATEGORIES_B Code combinations table for Item Category 
MTL_CATEGORY_SETS_B Category Sets 
MTL_CUSTOMER_ITEMS Customer item Information 
MTL_CUSTOMER_ITEM_XREFS Relationships between customer items and inventory items 
MTL_DEMAND Sales order demand and reservations 
MTL_DEMAND_HISTORIES Sales order demand and reservations 
MTL_ITEM_LOCATIONS Definitions for stock locators 
MTL_ITEM_REVISIONS_B Item revisions 
MTL_ITEM_TEMPLATES_B Item template definitions 
MTL_ITEM_TEMPL_ATTRIBUTES Item attributes and attribute values for a template 
MTL_LOT_NUMBERS Lot number definitions 
MTL_MATERIAL_TRANSACTIONS Material transaction table 
MTL_MATERIAL_TRANSACTIONS_TEMP Temporary table for processing material transactions 
MTL_ONHAND_QUANTITIES_DETAIL FIFO quantities by control level and receipt 
MTL_PARAMETERS Inventory control options and defaults 
MTL_RESERVATIONS Reservations 
MTL_SECONDARY_INVENTORIES Subinventory definitions 
MTL_SECONDARY_LOCATORS Item-subinventory-locator assignments 
MTL_SERIAL_NUMBERS Serial number definitions 
MTL_SYSTEM_ITEMS_B Inventory item definitions 
MTL_TRANSACTION_ACCOUNTS Material transaction distributions 
MTL_TRANSACTION_TYPES Inventory Transaction Types Table 
MTL_TXN_REQUEST_HEADERS Move Order headers table 
MTL_TXN_REQUEST_LINES Move order lines table 
MTL_UNIT_TRANSACTIONS Serial number transactions 


GL- General Ledger

Table Name Description 
GL_CODE_COMBINATIONS Stores valid account combinations 
GL_SETS_OF_BOOKS Stores information about the sets of books 
GL_IMPORT_REFERENCES Stores individual transactions from subledgers 
GL_DAILY_RATES Stores the daily conversion rates for foreign currency 

Transactions 
GL_PERIODS Stores information about the accounting periods 
GL_JE_HEADERS Stores journal entries 
GL_JE_LINES Stores the journal entry lines that you enter in the Enter Journals form 
GL_JE_BATCHES Stores journal entry batches 
GL_BALANCES Stores actual, budget, and encumbrance balances for detail and summary accounts 
GL_BUDGETS Stores Budget definitions 
GL_INTERFACE Import journal entry batches 
GL_BUDGET_INTERFACE Upload budget data from external sources 
GL_DAILY_RATES_INTERFACE Import daily conversion rates 


AR- Accounts Receivables

Table Name Description 
RA_CUST_TRX_TYPES_ALL Transaction type for invoices, commitments and credit memos 
RA_CUSTOMER_TRX_ALL Header-level information about invoices, debit memos, chargebacks, commitments and credit memos 
RA_CUSTOMER_TRX_LINES_ALL Invoice, debit memo, chargeback, credit memo and commitment lines 
RA_CUST_TRX_LINE_GL_DIST_ALL Accounting records for revenue, unearned revenue and unbilled receivables 
RA_CUST_TRX_LINE_SALESREPS_ALL Sales credit assignments for transactions 
AR_ADJUSTMENTS_ALL Pending and approved invoice adjustments 
RA_BATCHES_ALL 
AR_CASH_RECEIPTS_ALL Detailed receipt information 
AR_CASH_RECEIPT_HISTORY_ALL History of actions and status changes in the life cycle of a receipt 
AR_PAYMENT_SCHEDULES_ALL All transactions except adjustments and miscellaneous cash receipts 
AR_RECEIVABLE_APPLICATIONS_ALL Accounting information for cash and credit memo applications 
AR_TRANSACTION_HISTORY_ALL Life cycle of a transaction 
HZ_CUST_ACCOUNTS Stores information about customer accounts. 
HZ_CUSTOMER_PROFILES Credit information for customer accounts and customer account sites 
HZ_CUST_ACCT_SITES_ALL Stores all customer account sites across all operating units 
HZ_CUST_ACCT_RELATE_ALL Relationships between customer accounts 
HZ_CUST_CONTACT_POINTS This table is no longer used 
HZ_CUST_PROF_CLASS_AMTS Customer profile class amount limits for each currency 
HZ_CUST_SITE_USES_ALL Stores business purposes assigned to customer account sites. 
HZ_LOCATIONS Physical addresses 
HZ_ORG_CONTACTS People as contacts for parties 
HZ_ORG_CONTACT_ROLES Roles played by organization contacts 
HZ_PARTIES Information about parties such as organizations, people, and groups 
HZ_PARTY_SITES Links party to physical locations 
HZ_PARTY_SITE_USES The way that a party uses a particular site or address 
HZ_RELATIONSHIPS Relationships between entities 
HZ_RELATIONSHIP_TYPES Relationship types 

CE- Cash Management

Table Name Description 
CE_BANK_ACCOUNTS This table contains bank account information. Each bank account must be affiliated with one bank branch. 
CE_BANK_ACCT_BALANCES This table stores the internal bank account balances 
CE_BANK_ACCT_USES_ALL This table stores information about your bank account uses. 
CE_STATEMENT_HEADERS Bank statements 
CE_STATEMENT_LINES Bank statement lines 
CE_STATEMENT_HEADERS_INT Open interface for bank statements 
CE_STATEMENT_LINES_INTERFACE Open interface for bank statement lines 
CE_TRANSACTION_CODES Bank transaction codes 

AP- Accounts Payables

Table Name Description 
AP_ACCOUNTING_EVENTS_ALL Accounting events table 
AP_AE_HEADERS_ALL Accounting entry headers table 
AP_AE_LINES_ALL Accounting entry lines table 
AP_BANK_ACCOUNTS_ALL Bank Account Details 
AP_BANK_ACCOUNT_USES_ALL Bank Account Uses Information 
AP_BANK_BRANCHES Bank Branches 
AP_BATCHES_ALL Summary invoice batch information 
AP_CHECKS_ALL Supplier payment data 
AP_HOLDS_ALL Invoice hold information 
AP_INVOICES_ALL Detailed invoice records 
AP_INVOICE_LINES_ALL AP_INVOICE_LINES_ALL contains records for invoice lines entered manually, generated automatically or imported from the Open Interface. 
AP_INVOICE_DISTRIBUTIONS_ALL Invoice distribution line information 
AP.AP_INVOICE_PAYMENTS_ALL Invoice payment records 
AP_PAYMENT_DISTRIBUTIONS_ALL Payment distribution information 
AP_PAYMENT_HISTORY_ALL Maturity and reconciliation history for payments 
AP_PAYMENT_SCHEDULES_ALL Scheduled payment information on invoices 
AP_INTERFACE_REJECTIONS Information about data that could not be loaded by Payables Open Interface Import 
AP_INVOICES_INTERFACE Information used to create an invoice using Payables Open Interface Import 
AP_INVOICE_LINES_INTERFACE Information used to create one or more invoice distributions 
AP_SUPPLIERS AP_SUPPLIERS stores information about your supplier level attributes. 
AP_SUPPLIER_SITES_ALL AP_SUPPLIER_SITES_ALL stores information about your supplier site level attributes. 
AP_SUPPLIER_CONTACTS Stores Supplier Contacts 


FA – Fixed Assets

Table Name Description 
FA_ADDITIONS_B Descriptive information about assets 
FA_ADJUSTMENTS Information used by the posting program to generate journal entry lines in the general ledger 
FA_ASSET_HISTORY Historical information about asset reclassifications and unit adjustments 
FA_ASSET_INVOICES Accounts payable and purchasing information for each asset 
FA_BOOKS Financial information of each asset 
FA_BOOK_CONTROLS Control information that affects all assets in a depreciation book 
FA_CALENDAR_PERIODS Detailed calendar information 
FA_CALENDAR_TYPES General calendar information 
FA_CATEGORIES_B Default financial information for asset categories 
FA_CATEGORY_BOOKS Default financial information for an asset category and depreciation book combination 
FA_DEPRN_DETAIL Depreciation amounts charged to the depreciation expense account in each distribution line 
FA_DEPRN_PERIODS Information about each depreciation period 
FA_DEPRN_EVENTS Information about depreciation accounting events. 
FA_DEPRN_SUMMARY Depreciation information at the asset level 
FA_DISTRIBUTION_ACCOUNTS Table to store account ccids for all distributions for a book 
FA_DISTRIBUTION_DEFAULTS Distribution set information 
FA_DISTRIBUTION_HISTORY Employee, location, and Accounting Flexfield values assigned to each asset 
FA_DISTRIBUTION_SETS Header information for distribution sets 
FA_FORMULAS Depreciation rates for formula-based methods 
FA_LOCATIONS Location flexfield segment value combinations 
FA_MASS_ADDITIONS Information about assets that you want to automatically add to Oracle Assets from another system 
FA_METHODS Depreciation method information 
FA_RETIREMENTS Information about asset retirements and reinstatements 



HRMS- Human Resource Management System

Table Name Description 
HR_ALL_ORGANIZATION_UNITS Organization unit definitions. 
HR_ALL_POSITIONS_F Position definition information. 
HR_LOCATIONS_ALL Work location definitions. 
PER_ADDRESSES Address information for people 
PER_ALL_PEOPLE_F DateTracked table holding personal information for employees, applicants and other people. 
PER_ALL_ASSIGNMENTS_F Allocated Tasks 
PER_ANALYSIS_CRITERIA Flexfield combination table for the personal analysis key flexfield. 
PER_ASSIGNMENT_EXTRA_INFO Extra information for an assignment. 
PER_ASSIGNMENT_STATUS_TYPES Predefined and user defined assignment status types. 
PER_CONTRACTS_F The details of a persons contract of employment 
PER_CONTACT_RELATIONSHIPS Contacts and relationship details for dependents, beneficiaries, emergency contacts, parents etc. 
PER_GRADES Grade definitions for a business group. 
PER_JOBS Jobs defined for a Business Group 
PER_PAY_BASES Definitions of specific salary bases 
PER_PAY_PROPOSALS Salary proposals and performance review information for employee assignments 
PER_PEOPLE_EXTRA_INFO Extra information for a person 
PER_PERIODS_OF_PLACEMENT Periods of placement details for a non-payrolled worker 
PER_PERIODS_OF_SERVICE Period of service details for an employee. 
PER_PERSON_ANALYSES Special information types for a person 
PER_PERSON_TYPES Person types visible to specific Business Groups. 
PER_PERSON_TYPE_USAGES_F Identifies the types a person may be. 
PER_PHONES PER_PHONES holds phone numbers for current and ex-employees, current and ex-applicants and employee contacts. 
PER_SECURITY_PROFILES Security profile definitions to restrict user access to specific HRMS records 


PAY- Payroll

Table Name Description 
PAY_ACTION_INFORMATION Archived data stored by legislation 
PAY_ALL_PAYROLLS_F Payroll group definitions. 
PAY_ASSIGNMENT_ACTIONS Action or process results, showing which assignments have been processed by a specific payroll action, or process. 
PAY_ELEMENT_CLASSIFICATIONS Element classifications for legislation and information needs. 
PAY_ELEMENT_ENTRIES_F Element entry list for each assignment. 
PAY_ELEMENT_ENTRY_VALUES_F Actual input values for specific element entries. 
PAY_ELEMENT_LINKS_F Eligibility rules for an element type. 
PAY_ELEMENT_TYPES_F Element definitions. 
PAY_ELEMENT_TYPE_USAGES_F Used to store elements included or excluded from a defined run type. 
PAY_ORG_PAYMENT_METHODS_F Payment methods used by a Business Group. 
PAY_PAYMENT_TYPES Types of payment that can be processed by the system. 
PAY_PAYROLL_ACTIONS Holds information about a payroll process. 
PAY_PEOPLE_GROUPS People group flexfield information. 
PAY_PERSONAL_PAYMENT_METHODS_F Personal payment method details for an employee. 
PAY_RUN_RESULTS Result of processing a single element entry. 
PAY_RUN_RESULT_VALUES Result values from processing a single element entry. 
PAY_SECURITY_PAYROLLS List of payrolls and security profile access rules. 
PAY_INPUT_VALUES_F Input value definitions for specific elements. 


BOM – Bills Of Material 

Table Name Description 
BOM_DEPARTMENTS Departments 
BOM_DEPARTMENT_CLASSES Department classes 
BOM_DEPARTMENT_RESOURCES Resources associated with departments 
BOM_OPERATIONAL_ROUTINGS Routings 
BOM_OPERATION_NETWORKS Routing operation networks 
BOM_OPERATION_RESOURCES Resources on operations 
BOM_OPERATION_SEQUENCES Routing operations 
BOM_OPERATION_SKILLS 
BOM_RESOURCES Resources, overheads, material cost codes, and material overheads 
BOM_STANDARD_OPERATIONS Standard operations 
BOM_ALTERNATE_DESIGNATORS Alternate designators 
BOM_COMPONENTS_B Bill of material components 
BOM_STRUCTURES_B Bills of material 
BOM_STRUCTURE_TYPES_B Structure Type master table 




WIP – Work in Process 

Table Name Description 
WIP_DISCRETE_JOBS Discrete jobs 
WIP_ENTITIES Information common to jobs and schedules 
WIP_LINES Production lines 
WIP_MOVE_TRANSACTIONS Shop floor move transactions 
WIP_MOVE_TXN_ALLOCATIONS Move transaction allocations for repetitive schedules 
WIP_OPERATIONS Operations necessary for jobs and schedules 
WIP_OPERATION_NETWORKS Operation dependency 
WIP_OPERATION_OVERHEADS Overheads for operations in an average costing organization 
WIP_OPERATION_RESOURCES Resources necessary for operations 
WIP_OPERATION_YIELDS This table keeps all costing information for operation yield costing. 
WIP_TRANSACTIONS WIP resource transactions 
WIP_TRANSACTION_ACCOUNTS Debits and credits due to resource transactions 


FND – Appication Object Library

Table Name Description 
FND_APPLICATION Applications registered with Oracle Application Object Library 
FND_CONCURRENT_PROGRAMS Concurrent programs 
FND_CONCURRENT_REQUESTS Concurrent requests information 
FND_CURRENCIES Currencies enabled for use at your site 
FND_DATA_GROUPS Data groups registered with Oracle Application Object Library 
FND_FLEX_VALUES Valid values for flexfield segments 
FND_FLEX_VALUE_HIERARCHIES Child value ranges for key flexfield segment values 
FND_FLEX_VALUE_SETS Value sets used by both key and descriptive flexfields 
FND_FORM Application forms registered with Oracle Application Object Library 
FND_FORM_FUNCTIONS Functionality groupings 
FND_ID_FLEXS Registration information about key flexfields 
FND_ID_FLEX_SEGMENTS Key flexfield segments setup information and correspondences between table columns and key flexfield segments 
FND_ID_FLEX_STRUCTURES Key flexfield structure information 
FND_LOOKUP_TYPES Oracle Application Object Library QuickCodes 
FND_LOOKUP_VALUES QuickCode values 
FND_MENUS New menu tabl for Release 10SC 
FND_PROFILE_OPTIONS User profile options 
FND_PROFILE_OPTION_VALUES Values of user profile options defined at different profile levels 
FND_REQUEST_SETS Reports sets 
FND_REQUEST_SET_PROGRAMS Reports within report sets 
FND_REQUEST_SET_STAGES Stores request set stages 
FND_RESPONSIBILITY Responsibilities 
FND_RESP_FUNCTIONS Function Security 
FND_USER Application users 


JA - Asia/Pacific Localizations

Table Name Description 
JAI_CMN_BOE_HDRS Stores BOE header info when a BOE Invoice is created through IL 
JAI_CMN_BOE_DTLS Detail table for BOE Invoices 
JAI_CMN_TAXES_ALL Master table for Localization Taxes 
JAI_CMN_TAX_CTGS_ALL Stores tax categories and their link to excise ITEM classes. 
JAI_CMN_TAX_CTG_LINES Stores the tax lines for defined tax categories 
JAI_CMN_VENDOR_SITES Stores excise account related information about vendors. 
JAI_RGM_DEFINITIONS Stores regime information. 
JAI_RGM_TAXES This table stores tax details for transactions having TCS tax type. 
JAI_CMN_RG_23AC_I_TRXS Stores Information of RG23A/C records and known as Quantity Register. 
JAI_CMN_RG_23AC_II_TRXS Stores Information of RG23A/C Part II Details. Also known as Amount Register 
JAI_CMN_RG_23D_TRXS Quantity register for Trading Organizations 
JAI_CMN_RG_BALANCES Store the current balances of RG23A, RG23C and PLA Registers 
JAI_CMN_RG_PLA_TRXS Stores the Transaction Information of PLA Register. 
JAI_CMN_RG_PLA_HDRS Stores PLA header Infomation when a PLA invoice is created in AP module 
JAI_CMN_RG_PLA_DTLS Stores PLA Detail Information when a PLA Invoice is created in AP Module 


QP – Advanced Pricing 

Table Name Description 
QP_LIST_HEADERS_B QP_LIST_HEADERS_B stores the header information for all lists. List types can be, for example, Price Lists, Discount Lists or Promotions. 
QP_LIST_LINES QP_LIST_LINES stores all list lines for lists in QP_LIST_HEADERS_B. 
QP_PRICE_FORMULAS_B QP_PRICE_FORMULAS_B stores the pricing formula header information. 
QP_PRICE_FORMULA_LINES QP_PRICE_FORMULA_LINES stores each component that makes up the formula. 
QP_PRICING_ATTRIBUTES QP_PRICING_ATTRIBUTES stores product information and pricing attributes. 
QP_QUALIFIERS QP_QUALIFIERS stores qualifier attribute information. 






XLA - Subledger Accounting 

Table Name Description 
XLA_EVENTS The XLA_EVENTS table record all information related to a specific event. This table is created as a type XLA_ARRAY_EVENT_TYPE. 
XLA_TRANSACTION_ENTITIES The table XLA_ENTITIES contains information about sub-ledger document or transactions. 
XLA_AE_HEADERS The XLA_AE_HEADERS table stores subledger journal entries. There is a one-to-many relationship between accounting events and journal entry headers. 
XLA_AE_LINES The XLA_AE_LINES table stores the subledger journal entry lines. There is a one-to-many relationship between subledger journal entry headers and subledger journal entry lines. 
XLA_DISTRIBUTION_LINKS The XLA_DISTRIBUTION_LINKS table stores the link between transactions and subledger journal entry lines. 
XLA_ACCOUNTING_ERRORS The XLA_ACCOUNTING_ERRORS table stores the errors encountered during execution of the Accounting Program. 
XLA_ACCTG_METHODS_B The XLA_ACCTG_METHODS_B table stores Subledger Accounting Methods (SLAM) across products. SLAMs provided by development are not chart of accounts specific. Enabled SLAMs are assigned to ledgers. 
XLA_EVENT_TYPES_B The XLA_EVENT_TYPES_B table stores all event types that belong to an event class. 
XLA_GL_LEDGERS This table contains ledger information used by subledger accounting.

References:
http://rushikeshranade.blogspot.com/2012/09/oracle-apps-important-tables.html