Table-all

Table Or View Table Owner Created By

AP_INVOICES_ALL Table Account Payables Anonymous

AP_HOLDS_ALL Table Account Payables Anonymous

AP_INVOICES_INTERFACE Table Account Payables Anonymous

AP_INVOICE_LINES_INTERFACE Table Account Payables Anonymous

AP_INTERFACE_REJECTIONS Table Account Payables Anonymous

AP_CHECKS_ALL Table Account Payables Anonymous

AP_SUPPLIERS Table Account Payables Anonymous

AP_INVOICES_ALL

Account Payables

Table Or View:

Table

Important columns:

INVOICE_ID - NUMBER : Unique internal Identifier for this record. Generated using a database

sequence.

VENDOR_ID - NUMBER : The unique internal identifier of the supplier to which the invoice

belongs. Foreign key to the AP_SUPPLIERS table.

INVOICE_NUM : Invoice number for an invoice. This number entered will be unique per supplier

and operating unit.

SET_OF_BOOKS_ID : Ledger unique identifier

INVOICE_CURRENCY_CODE : Currency code of the invoice. Foreign key to the

FND_CURRENCIES table.

PAYMENT_CURRENCY_CODE : Currency code of payment. If the Invoice Currency is not a

fixed-rate currency, then the Payment Currency will be the same as the

INVOICE_CURRENCY_CODE. For fixed-rate currency such as euro or another EMU currency it

can be different to INVOICE_CURRENCY_CODE

PAYMENT_CROSS_RATE NUMBER : Yes Exchange rate between invoice and payment. The

value is always 1 unless they are associated fixed-rate currencies such as euro or another EMU

currency.

DOC_SEQUENCE_ID NUMBER : Unique Sequence identifier assigned to an invoice, based on

the document category of the invoice. Foreign key to the DOC_SEQUENCE_ID of the

AP_DOC_SEQUENCE_AUDIT table.

DOC_SEQUENCE_VALUE NUMBER : Sequence name assigned to an invoice, based on the

document category of the invoice. Foreign key to the DOC_SEQUENCE_VALUE of the

AP_DOC_SEQUENCE_AUDIT table

Description:

This table corresponds to the Invoices header block of Invoice workbench. AP_INVOICES_ALL

holds information of all AP invoices whether it is a manually entered, imported, created from other

products like Oracle Loans, Oracle Projects, iSupplier Portal, Refunds from Oracle Receivables etc.

This table holds all type of invoices, which includes Standard, Prepayments, Credit Memo, Debit

Memo, Mixed invoice, Withholding invoice, Interest Invoice, Retainage invoices, Payment Requests

etc., An invoice can also have one or more scheduled payments. There will be one row for each

invoice you enter.

An invoice can have one or more invoice lines and each line can have one or more invoice

distributions.

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.

Oracle Payables application uses the INTEREST type invoice for interest that it calculates on

invoices that are overdue. Oracle Payables application links the interest invoice to the original

invoice by inserting the INVOICE_ID in the AP_INVOICE_RELATIONSHIPS table.

The accounting code combinations stored in this table is meta data for creating accounting entries in

Subledger Accounting. Payables provides the code combinations stored in this table to Subledger

Accounting as a source for accounting attributes for deriving the accounting code combinations.

Subledger Accounting generates the final accounting entries that are posted to General Ledger. The

accounting code combination used in the final accounting entries can be same as that stored in

AP_INVOICES_ALL table or can be different depending on the rules setup in Subledger

Accounting. The XLA_AE_HEADERS and XLA_AE_LINES tables in Subledger Accounting stores

the accounting entries posted to General Ledger.

AP_HOLDS_ALL

Account Payables

Table Or View:

Table

Important columns:

1. INVOICE_ID : Invoice identifier 2. LINE_LOCATION_ID : Purchase order line location identifier 3. HOLD_LOOKUP_CODE : Name of hold code 4. HELD_BY : User that placed hold on invoice 5. HOLD_DATE : Date user placed hold on invoice 6. HOLD_REASON : Reason for hold being placed on invoice 7. RELEASE_LOOKUP_CODE : Name of release code 8. RELEASE_REASON : Reason for release being placed on invoice 9. LINE_NUMBER : Invoice line number of the applied hold 10. HOLD_ID : Hold identifier

WF_STATUS : Holds resolution workflow status

Description:

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_INVOICES_INTERFACE

Account Payables

Table Or View:

Table

Important columns:

INVOICE_ID : Unique identifier for this invoice within this batch. Same value should be populated

in invoice's lines in the AP_INVOICE_LINES_INTERFACE table to identify the data as belonging

to the same invoice.

INVOICE_NUM : Enter the invoice number that needs to be assigned to the invoice created in

Payables from this record. The number must be unique for the supplier. If no value is populated in

this column, then during import, Payables uses the system date at the time of import as a default.

PO_NUMBER : Purchase order number from PO_HEADERS.SEGMENT1. This column needs to

be populated if invoice to be matched with an purchase order.

VENDOR_ID NUMBER : Unique identifier for a supplier. Validated against

(PO_VENDORS.VENDOR_ID). Supplier of the invoice to be derived by value in one of the

following columns in this table: VENDOR_ID, VENDOR_NUM, VENDOR_NAME,

VENDOR_SITE_ID or PO_NUMBER.

Description:

This is the open interface table for importing AP Invoices from external sources and stores header

information about invoices. Invoice data comes from sources including: EDI invoices from suppliers

that are loaded through Oracle e-Commerce Gateway, supplier invoices that are transferred through

the Oracle XML Gateway, invoices that are loaded using Oracle SQL*Loader, lease invoices from

Oracle Property Manager, Disbursements from Oracle loans, lease payments from Oracle Assets,

credit card transaction data that are loaded using the Credit Card Invoice Interface Summary,

Expense Report invoices from Oracle Internet Expenses, Payment Requests from Receivables, and

invoices that are entered through the Invoice Gateway. There is one row for each invoice you import.

Oracle Payables application uses this information to create invoice header information when

Payables Open Interface program is submitted.

Data in the AP_INVOICES_INTERFACE table used in conjunction with

AP_INVOICE_LINES_INTERFACE table to create Payables Invoice, Invoice lines, Distributions

and Schedule payments.

Data in this table can be viewed and edited using 'Open Interface Invoices' window.

The Payables Open Interface program validates each record in this interface table selected for import,

and if the record contains valid data then the program creates a Payables Invoice.

AP_INVOICE_LINES_INTERFACE

Account Payables

Table Or View:

Table

Important columns:

INVOICE_ID : Invoice identifier.Validated against AP_INVOICES_INTERFACE.INVOICE_ID

INVOICE_LINE_ID : Invoice line identifier

LINE_NUMBER : Invoice line number

LINE_TYPE_LOOKUP_CODE : Type of invoice line (Item, Freight, Tax, Miscellaneous)

LINE_GROUP_NUMBER NUMBER : Value to identify each item line to which you want to

prorate

Description:

This is the lines interface table for the AP Invoice Open Interface. Use it in conjunction with

AP_INVOICE_INTERFACE table.

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_INTERFACE_REJECTIONS

Table Owner:

Account Payables

Table Or View:

Table

Important columns:

PARENT_TABLE : Reference to table in which the rejection occurred

(AP_INVOICES_INTERFACE or AP_INVOICE_LINES_INTERFACE)

PARENT_ID NUMBER : Reference to invoice or invoice line identifier which was rejected

(INVOICE_ID or INVOICE_LINE_ID)

REJECT_LOOKUP_CODE : Invoice rejection reason

Description:

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_CHECKS_ALL

Account Payables

Table Or View:

Table

Important columns:

AMOUNT : Payment amount

BANK_ACCOUNT_ID : longer used

BANK_ACCOUNT_NAME : Bank account name

CHECK_ID NUMBER : Payment identifier

CHECK_NUMBER : Payment number

VENDOR_NAME : Supplier name

VENDOR_SITE_CODE : Supplier site code

PAYMENT_TYPE_FLAG : Type of payment

A - Payment Process Request

M - Manual

Q - Quick payment

R - Reunfund

Description:

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.

Payments are linked with invoices through AP_INVOICE_PAYMENTS_ALL

AP_SUPPLIERS

Account Payables

Table Or View:

Table

Important columns: VENDOR_ID : Yes Supplier unique identifier

SEGMENT1 : Supplier number

Description: AP_SUPPLIERS 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.

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

Table Name Table Or View Table Owner Created By

RA_CUSTOMER_TRX_ALL Table Account Receivables Anonymous

RA_CUSTOMER_TRX_LINES_ALL View Account Receivables Anonymous

RA_CUST_TRX_TYPES_ALL Table Account Receivables Anonymous

RA_INTERFACE_LINES_ALL View Account Receivables Anonymous

AR_CASH_RECEIPTS_ALL(V) View Account Receivables Anonymous

RA_CUSTOMER_TRX_ALL

Account Receivables

Table Or View:

Table

Important columns: CUSTOMER_TRX_ID , BATCH_SOURCE_ID , TRX_NUMBER

Description: Header-level information about invoices, debit memos, chargebacks, commitments and

credit memos.

RA_CUSTOMER_TRX_LINES_ALL

Account Receivables

Table Or View:

View

Important columns:

CUSTOMER_TRX_ID

CUSTOMER_TRX_LINE_ID

LINE_TYPE : Line, TAX or Freight

LINE_NUMBER

INVENTORY_ITEM_ID

QUANTITY_ORDERED

QUANTITY_CREDITED

QUANTITY_INVOICED

UNIT_STANDARD_PRICE

UNIT_SELLING_PRICE

SALES_ORDER

SALES_ORDER_REVISION

SALES_ORDER_LINE

TAX_EXEMPT_FLAG

SALES_TAX_ID

WAREHOUSE_ID

ORG_ID : Organization identifier

Description: RA_CUSTOMER_TRX_LINES_ALL contians the line level information of invoices

(header informations are stored in RA_CUSTOMER_TRX_ALL).

This view contains information for all the type of lines : Line, TAX and Freight.

RA_CUST_TRX_TYPES_ALL

Account Receivables

Table Or View:

Table

Important columns:

CUST_TRX_TYPE_ID NUMBER : Transaction type identifier

NAME : Transaction type Name

TYPE

POST_TO_GL : Indicates if transactions should be posted to the General Ledger. Y for yes, N

otherwise.

ACCOUNTING_AFFECT_FLAG : Indicates if transactions affect open receivable balances. Y for

yes, N otherwise.

CREDIT_MEMO_TYPE_ID : Transaction type identifier of subsequent credit memos

ORG_ID NUMBER : Organization identifier

Description:

The RA_CUST_TRX_TYPES_ALL table stores information about each transaction type that is used

for invoices, commitments, bills receivable, and credit memos. Each row includes AutoAccounting

information as well as standard defaults for the invoices that result.

The POST_TO_GL column stores Y or N to indicate if this transaction can post to your General

Ledger.

The ACCOUNTING_AFFECT_FLAG column stores Y or N to indicate if this transaction can

update your open receivables balances. If the ACCOUNTING_AFFECT_FLAG column is Y, you

can see this transaction in your agings.

The TYPE column contains:

INV - Invoice

CM - Credit Memo

DM - Debit Memo

DEP - Deposit

GUAR - Guarantee

If AutoAccounting is based on transaction type, the GL_ID_REV, GL_ID_FREIGHT, and

GL_ID_REC columns store the default revenue, freight, and receivables accounts. The STATUS and

CREDIT_MEMO_TYPE_ID columns are required even though they are null allowed.

The primary key for this table is CUST_TRX_TYPE_ID.

RA_INTERFACE_LINES_ALL

Account Receivables

Table Or View:

View

Important columns:

INTERFACE_LINE_ID : Primary key

INTERFACE_LINE_ATTRIBUTE1, 2, 3 can be use as per business requirement.

INTERFACE_LINE_ATTRIBUTE1 is mostly used for storing the sales order number.

Description:

AR.RA_INTERFACE_LINES_ALL contains information for each invoice line imported using

AutoInvoice

Account Receivables

Table Or View:

View

Important columns: CASH_RECEIPT_ID : Unique cash receipt id, ORG_ID : Organization identifier

AMOUNT : Amount

Description:

This is the AR_CASH_RECEIPTS_ALL view, which may be used by all products.


FND_VIEWS Table Basics Anonymous

ALL_TABLES Table Basics Anonymous

BEN_ALL_TAB_COLUMNS View Basics Anonymous

XLE_ENTITY_PROFILES Table Basics Anonymous

FND_VIEWS

Basics

Table Or View:

Table

Important columns: View_Name , View_ID ,Application_ID

Description: FND_VIEWS contains the list of all the views present in the database.

Select * From apps. FND_VIEWS, ll show all the tables in database

ALL_TABLES

Basics

Table Or View:

Table

Important columns: Table_name

Description: All_tables contains the list of all the tables present in the database.

Select * From all_tables , ll show all the tables in database

BEN_ALL_TAB_COLUMNS

Basics

Table Or View: View

Important columns: Table_name ,Column_name , Data_type

Description: This view contians information about all the tables and columns

XLE_ENTITY_PROFILES

Basics

Table Or View: Table

Important columns: LEGAL_ENTITY_ID PARTY_ID , LEGAL_ENTITY_IDENTIFIER ,NAME GEOGRAPHY_ID

Description: It contains information about all the legal entities in an instance.

Legal entity is a new concept in R12. Its no longer structured like an organization (IO or OU). Its a part of

TCA architecture.

What is the geography_id in the xle_entity_profiles table?

What other tables does it link to?

HR_OPERATING_UNITS

HRMS

Table Or View: View

Important columns: BUSINESS_GROUP_ID , ORGANIZATION_ID NAME , SET_OF_BOOKS_ID ,

DEFAULT_LEGAL_CONTEXT_ID , SHORT_CODE

Description: HR_OPERATING_UNITS is a view which contains the information about all the operating units in

a particular instance.

HR_ALL_ORGANIZATION_UNITS

HRMS


Important columns: ORGANIZATION_ID

Description: HR_ALL_ORGANIZATION_UNITS holds the definitions that identify business groups and the

organization units within a single business group. Additional information about classifications and

information types for each organization is held in HR_ORGANIZATION_INFORMATION.

HR_LOCATIONS_ALL

HRMS


Important columns: LOCATION_CODE ,LOCATION_ID ,BUSINESS_GROUP_ID

Description: HR_LOCATIONS_ALL holds information about specific work locations defined for an enterprise,

including address details.

HR_ORGANIZATION_INFORMATION

HRMS


Important columns: ORGANIZATION_ID, BUSINESS_GROUP_ID,

Description: HR_ORGANIZATION_INFORMATION is used to hold two distinct sets

of organization information. When ORG_INFORMATION_CONTEXT

is set to CLASS this table acts as an intersection table between organizations and organization classifications.

ORGANIZATION_ID identifies the organization and ORG_INFORMATION1 holds the organization classification

name. This information is maintained by the organization classifications block of the Organization form.

When ORG_INFORMATION_CONTEXT is set to an information type held in HR_ORG_INFORMATION_TYPES

the ORG_INFORMATION120 columns hold details for the specific information type. This information is

maintained by a predefined protected descriptive flexfield. (Org Developer DF.)

MTL_SYSTEM_ITEMS_B

Inventory


Important columns:

INVENTORY_ITEM_ID : Inventory item identifier

ORGANIZATION_ID : Organization identifier

ACCOUNTING_RULE_ID : Accounting rule identifier

INVOICING_RULE_ID : Invoicing rule identifier

PURCHASING_ITEM_FLAG: Flag indicating purchasing item

SHIPPABLE_ITEM_FLAG : Flag indicating shippable item

CUSTOMER_ORDER_FLAG : Flag indicating customer orderable item

INTERNAL_ORDER_FLAG : Flag indicating internally orderable item

SERVICE_ITEM_FLAG : Flag indicating service item

INVENTORY_ITEM_FLAG : Flag indicating inventory item

ENG_ITEM_FLAG : Flag indicating engineering item

INVENTORY_ASSET_FLAG : Flag indicating item is an inventory asset

PURCHASING_ENABLED_FLAG : Flag indicating item is purchasable

CUSTOMER_ORDER_ENABLED_FLAG : Flag indicating item is customer orderable

INTERNAL_ORDER_ENABLED_FLAG : Flag indicating item is internally orderable

SO_TRANSACTIONS_FLAG VARCHAR2 : Sales order transactions flag

MTL_TRANSACTIONS_ENABLED_FLAG : Flag indicating item is transactable

STOCK_ENABLED_FLAG : Flag indicating item is stockable

BOM_ENABLED_FLAG : Flag indicating item may appear on a BOM

BUILD_IN_WIP_FLAG : Flag indicating item may be built in WIP

Description: MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for

inventory items, engineering items, and purchasing items. You can specify item-related information in fields

such as: Bill of Material, Costing, Purchasing, Receiving, Inventory, Physical attributes, General Planning,

MPS/MRP Planning, Lead times, Work in Process, Order Management, and Invoicing.

You can set up the item with multiple segments, since it is implemented as a flexfield. Use the

standard 'System Items' flexfield that is shipped with the product to configure your item flexfield.

The primary key for an item is the INVENTORY_ITEM_ID and ORGANIZATION_ID. Therefore,

the same item can be defined in more than one organization.

Each item is initially defined in an item master organization. The user then assigns the item to other

organizations that need to recognize this item. A row is inserted for each new organization the item is

assigned to. Many columns such as MTL_TRANSACTIONS_ENABLED_FLAG and

BOM_ENABLED_FLAG correspond to item attributes defined in the

MTL_ITEM_ATTRIBUTES table. The attributes that are available to the user depend on which

Oracle applications are installed. The table MTL_ATTR_APPL_DEPENDENCIES maintains the

relationships between item attributes and Oracle applications.

Two unit of measure columns are stored in MTL_SYSTEM_ITEMS_B table.

PRIMARY_UOM_CODE is the 3-character unit that is used throughout Oracle Manufacturing.

PRIMARY_UNIT_OF_MEASURE is the 25-character Unit of Measure that is used throughout

Oracle Purchasing. Unlike the PRIMARY_UOM_CODE, the Unit of Measure is language-

dependent attribute, however, PRIMARY_UNIT_OF_MEASURE column stores value in the

installation base language only.

Items now support multilingual description. MLS is implemented with a pair of tables:

MTL_SYSTEM_ITEMS_B and MTL_SYSTEM_ITEMS_TL. Translations table

(MTL_SYSTEM_ITEMS_TL) holds item Description and Long Description in multiple languages.

DESCRIPTION column in the base table (MTL_SYSTEM_ITEMS_B) is for backward

compatibility and is maintained in the installation base language only.

MTL_TXN_REQUEST_HEADERS

Inventory


Important columns:

HEADER_ID : Header identifier

REQUEST_NUMBER : Request number of the move order

TRANSACTION_TYPE_ID : Transaction type identifier

MOVE_ORDER_TYPE : Type of move order


Description: This table stores all of the move order headers. The headers contain all information

which pertains to entire move orders, including the transaction type of the move order, the move

order type, the move order status, and the request number of the move order.

MTL_TXN_REQUEST_LINES

Inventory


Important columns:

LINE_ID : Line identifier


LINE_NUMBER : Line number



FROM_SUBINVENTORY_CODE : From subinventory code

TO_SUBINVENTORY_CODE : To subinventory code

QUANTITY : Quantity requested

QUANTITY_DELIVERED : Quantity which has been delivered

Description: The table MTL_TXN_REQUEST_LINES stores all of the move order lines. The lines are requests to

move some quantity of an item from a source location to a destination location or account. Each move order

line must be tied to a specific move order header.

When a line is detailed or pick released, the quantity detailed is updated appropriately and

transaction lines are created in MTL_MATERIAL_TRANSACTIONS_TEMP. When the transaction

lines are transacted, the quantity delivered is updated.

MTL_TRANSACTION_TYPES

Inventory


Important columns:


TRANSACTION_TYPE_NAME : Name of the transaction type

TRANSACTION_ACTION_ID : Transaction action identifer that is associated with this type

TRANSACTION_SOURCE_TYPE_ID : Transaction source type identifier that is associated with

this transaction type

SHORTAGE_MSG_BACKGROUND_FLAG : Flag indicating background notification should be

provided for this transaction

USER_DEFINED_FLAG : Set to 'Y' if this type is user-defined

Description:

MTL_TRANSACTION_TYPES contains seeded transaction types and the user defined ones.

USER_DEFINED_FLAG will distinguish the two. The table also stores the

TRANSACTION_ACTION_ID and TRANSACTION_SOURCE_TYPE_ID

that is associated with each transaction type.

OE_TABLES (Imp OM tables)

Order Management


Description: Following are important OM tables

OE_ORDER_HEADERS_ALL

OE_ORDER_LINES_ALL

SALES CREDITS OE_SALES_CREDITS

PRICE ADJUSTMENTS OE_PRICE_ADJUSTMENTS

This entity stores Order and Line price adjustments information. It stores the benefits offered at

header, line or group of lines. Benefits can be discounts on other items, item upgrade, terms

substitution, coupons, discounts, surcharges etc.

This table has a lot more columns than SO_PRICE_ADJUSTMENTS to support the capabilities

offered by Advanced Pricing. The entity also stores information for tax, freight and special charges.

PRICING ATTRIBUTES OE_ORDER_PRICE_ATTRIBS

With Order Management, Order and Line pricing attributes are stored in a different entity. The Order

and Line Pricing Attributes Descriptive Flex Definitions are based off this table. You now have 100

pricing attribute columns.

With Advanced Pricing you can use multiple descriptive flex contexts for a given Order Line. With

Basic pricing, when entering an Order you can select only one Context (excluding the Item and

Volume Contexts which have special meaning).

LOT AND SERIAL NUMBERS OE_LOT_SERIAL_NUMBERS

This is a new entity in Order Management. It stores lot and serial number information for return

lines. Order Management lets you create returns using the original serial number as a reference. If

you create a return using the original

Order or Invoice as a reference and the item being returned was under serial number control, the

application automatically pulls up serial number information from Oracle Inventory.

HISTORY OE_ORDER_LINES_HISTORY

You are required to provide a cancellation reason only when you are canceling and the canceled

quantity on the

line is incremented by the appropriate amount. A picture of the old record is

captured whenever a reason code is provided with a quantity change. This is

stored in .

OE_PROCESSING_MSGS

Order Management


Important columns:

1. TRANSACTION_ID : System Generated Id 2. HEADER_ID NUMBER : This holds the header id against which the message is logged 3. LINE_ID NUMBER : This holds the Line id against which the message is logged 4. ORIGINAL_SYS_DOCUMENT_REF : This holds the order header source. Will be used for

Order Import

5. ORIGINAL_SYS_DOCUMENT_LINE_REF : This holds the order Line source. Will be used for Order Import

6. SOURCE_DOCUMENT_ID : This holds the source header id. Can be used to join OE_HEADERS_IFACE_ALL with column org_sys_document_ref

7. SOURCE_DOCUMENT_LINE_ID : This holds the source Line id 8. ORDER_SOURCE_ID : This holds the order source. Will be used for Order Import

Description: This table stores the context information of the processing messages that will be

generated during Order Entry concurrent program execution or UI process.

OE_PROCESSING_MSGS _VL

Order Management


Important columns:

TRANSACTION_ID

MESSAGE_TEXT

HEADER_ID

LINE_ID

ORDER_SOURCE_ID

ORIGINAL_SYS_DOCUMENT_REF

ORIGINAL_SYS_DOCUMENT_LINE_REF

SOURCE_DOCUMENT_TYPE_ID

SOURCE_DOCUMENT_ID

SOURCE_DOCUMENT_LINE_ID

ORDER_NUMBER

ORDER_TYPE_ID

ORDER_TYPE

LINE_NUMBER

SHIPMENT_NUMBER

OPTION_NUMBER

ITEM

ORGANIZATION_ID

ORG_ID

MESSAGE_STATUS_CODE

Description: This view is a view built on oe_processing_msgs and oe_processing_msgs_tl for de-

normalization to resolve multilingual issue and names for certain ids.

The view contains columns from below tables

OE_PROCESSING_MSGS OE_ORDER_HEADERS OE_ORDER_LINES OE_TRANSACTION_TYPES_TL FND_CONCURRENT_PROGRAMS_TL FND_CONCURRENT_REQUESTS FND_USER U WF_PROCESS_ACTIVITIES WPA WF_ACTIVITIES_TL WA OE_SOLD_TO_ORGS_V SO OE_PROCESSING_MSGS_TL MT

OE_LINES_IFACE_ALL

Order Management


Important columns:

ORDER_SOURCE_ID : Order source id

ORIG_SYS_DOCUMENT_REF : Original system document reference

ORIG_SYS_LINE_REF : Original system line reference

ORIG_SYS_SHIPMENT_REF : Original system shipment reference

Description: This is a multi-org table for sales order lines open interface. This table stores order lines

information that is imported from a feeder system into Oracle Order Management using Order

Import.

PO_HEADERS_ALL

Purchasing


Important columns: PO_HEADER_ID , SEGMENT1,VENDOR_ID ,VENDOR_SITE_ID

Description: PO_HEADERS_ALL contains header information for all purchasing documents.

You need one row for each document you create. There are six types of documents that use

PO_HEADERS_ALL:

RFQs Quotations Standard purchase orders Planned purchase orders Blanket purchase orders Contracts

Each row contains all the header level informations like : buyer information, supplier information,

brief notes, foreign currency information, terms and conditions information, and the status of the

document. Oracle Purchasing uses this information to record information that is related to a complete

document.

PO_HEADER_ID is the unique system-generated primary key and is invisible to the user.

SEGMENT1 is the system-assigned number you use to identify the document in forms and reports.

Oracle Purchasing generates SEGMENT1 using the PO_UNIQUE_IDENTIFIER_CONT_ALL table

if you choose to let Oracle Purchasing generate document numbers for you. SEGMENT1 is not

unique for the entire table. Different document types can share the same numbers. You can uniquely

identify a row in PO_HEADERS_ALL using ORG_ID, SEGMENT1, and TYPE_LOOKUP_CODE,

or using PO_HEADER_ID.

If APPROVED_FLAG is 'Y', the purchase order is approved. If your document type is a blanket

purchase order, contract purchase order, RFQ, or quotation, Oracle Purchasing uses START_DATE

and END_DATE to store the valid date range for the document. Oracle Purchasing only uses

BLANKET_TOTAL_AMOUNT for blanket purchase orders or contract purchase orders.

If you autocreate a quotation from an RFQ using the Copy Document window, Oracle Purchasing

stores the foreign key to your original RFQ in FROM_HEADER_ID. Oracle Purchasing also uses

FROM_TYPE_LOOKUP_CODE to indicate that you copied the quotation from an RFQ.

Oracle Purchasing does not use SUMMARY_FLAG and ENABLED_FLAG. Because future

versions of Oracle Purchasing will use them, SUMMARY_FLAG and ENABLED_FLAG should

always be 'N' and 'Y' respectively.

PO_LINES_ALL

Purchasing


Important columns:

PO_LINE_ID : Document line unique identifier

PO_HEADER_ID : Document header unique identifier. (References

PO_HEADERS_ALL.po_header_id.)

LINE_TYPE_ID : Line type unique identifier (References PO_LINE_TYPES_B.line_type_id.)

LINE_NUM : Line number

ITEM_ID : Item unique identifier. (References MTL_SYSTEM_ITEMS_B.inventory_item_id.)

CLOSED_FLAG : Indicates whether the line is closed or not

ORG_ID : Operating unit unique identifier

Description: PO_LINES_ALL stores current information about each purchase order line. You need

one row for each line you attach to a document. There are five document types that use lines:

RFQs

Quotations

Standard purchase orders

Blanket purchase orders

Planned purchase orders

Each row includes the line number, the item number and category, unit, price, tax information,

matching information, and quantity ordered for the line. Oracle Purchasing uses this information to

record and update item and price information for purchase orders, quotations, and RFQs.

PO_LINE_ID is the unique system-generated line number invisible to the user. LINE_NUM is the

number of the line on the purchase order.

Oracle Purchasing uses CONTRACT_ID to reference a contract purchase order from a standard

purchase order line. Oracle Purchasing uses ALLOW_PRICE_OVERRIDE_FLAG,

COMMITTED_AMOUNT, QUANTITY_COMMITTED, MIN_RELEASE_AMOUNT only for

blanket and planned purchase order lines.

The QUANTITY field stores the total quantity of all purchase order shipment lines (found in

PO_LINE_LOCATIONS_ALL)

PO_LINE_LOCATIONS_ALL

Purchasing


Important columns:

LINE_LOCATION_ID : Document shipment schedule unique identifier

LAST_UPDATE_DATE : Standard Who column: date when this record was last updated

LAST_UPDATED_BY : Standard Who column: the user who last updated this record. (References

FND_USERS.user_id.)

PO_HEADER_ID : Document header unique identifier. (References

PO_HEADERS_ALL.po_header_id.). For Release shipments, this references the Unique identifier

of Blanket PO

PO_LINE_ID : Document line unique identifier (References PO_LINES_ALL.po_line_id). For

Release Shipments, this references the unique line identifier of Blanket PO

QUANTITY : Quantity ordered or break quantity for blanket purchase orders, RFQs and quotations

QUANTITY_RECEIVED : Quantity received until today

QUANTITY_ACCEPTED : Quantity accepted after inspection, up until today

QUANTITY_REJECTED : Quantity rejected after inspection, up until today

QUANTITY_BILLED : Quantity invoiced by Oracle Payables, up until today

QUANTITY_CANCELLED : Quantity cancelled

TAXABLE_FLAG : Indicates whether the shipment is taxable

TAX_NAME : Tax code for the shipment (References AP_TAX_CODES_ALL.name)

SHIP_TO_ORGANIZATION_ID : Ship-to organization unique identifier(References

HR_ORGANIZATION_UNITS.organization_id)

SHIPMENT_NUM : Shipment line number

SOURCE_SHIPMENT_ID : Unique identifier of the planned purchase order shipment(also stored in

PO_LINE_LOCATIONS_ALL) that was referenced when creating this scheduled release shipment

ORG_ID : Operating unit unique identifier(References HR_OPERATING_UNITS.organization_id)

Description: PO_LINE_LOCATIONS_ALL contains information about purchase order shipment schedules and

blanket agreement price breaks. You need one row for each schedule or price break you attach to a

document line. There are seven types of documents that use shipment schedules:

1. RFQs 2. Quotations 3. Standard purchase orders 4. Planned purchase orders 5. Planned purchase order releases 6. Blanket purchase orders 7. Blanket purchase order releases

Each row includes the location, quantity, and dates for each shipment schedule. Oracle Purchasing

uses this information to record delivery schedule information for purchase orders, and price break

information for blanket purchase orders, quotations and RFQs.

PO_RELEASE_ID applies only to blanket purchase order release shipments. PO_RELEASE_ID

identifies the release on which you placed this shipment.

SOURCE_SHIPMENT_ID applies only to planned purchase order release shipments. It identifies the

planned purchase order shipment you chose to release from.

PRICE_OVERRIDE always equals the purchase order line price for standard purchase order

shipments. For blanket and planned purchase orders, PRICE_OVERRIDE depends on the values of

the ALLOW_PRICE_OVERRIDE_FLAG and NOT_TO_EXCEED_PRICE in the corresponding

row in PO_LINES_ALL:

If ALLOW_PRICE_OVERRIDE_FLAG is 'N', then PRICE_OVERRIDE equals UNIT_PRICE in

PO_LINES_ALL.

If ALLOW_PRICE_OVERRIDE_FLAG is 'Y', the PRICE_OVERRIDE can take any value that is

smaller than NOT_TO_EXCEED_PRICE in

PO_LINES_ALL.

The QUANTITY field corresponds to the total quantity ordered on all purchase order distribution

lines (found in

PO_DISTRIBUTIONS_ALL).

Oracle Purchasing automatically updates QUANTITY_RECEIVED, QUANTITY_ACCEPTED, and

QUANTITY_REJECTED when you receive, return, or inspect goods or services. Oracle Payables

automatically updates QUANTITY_BILLED when you match an invoice with a purchase order

shipment. Oracle Purchasing automatically updates QUANTITY_CANCELLED when you cancel a

purchase order shipment.

Oracle Purchasing sets APPROVED_FLAG to 'Y' when you approve the corresponding purchase

order if there are no problems associated with the shipment and its related distributions. Oracle

Purchasing sets ENCUMBERED_FLAG to 'Y' and enters the ENCUMBERED_DATE when you

approve a purchase order if you use encumbrance.

PO_DISTRIBUTIONS_ALL

Purchasing


Important columns:

PO_DISTRIBUTION_ID : Document distribution unique identifier. Primary key for this table.

PO_HEADER_ID : Document header unique identifier. References

PO_HEADERS_ALL.PO_HEADER_ID.

PO_LINE_ID : Document line unique identifier. References PO_LINES_ALL.PO_LINE_ID.

LINE_LOCATION_ID : Document shipment schedule unique identifier. References

PO_LINES_LOCATIONS_ALL.LINE_LOCATION_ID.

SET_OF_BOOKS_ID : Set of Books unique identifier. References

GL_SETS_OF_BOOKS.SET_OF_BOOKS_ID.

CODE_COMBINATION_ID : Unique identifier for the General Ledger charge account. References

GL_CODE_COMBINATIONS.CODE_COMBINATION_ID.

REQ_DISTRIBUTION_ID : Requisition distribution unique identifier. References

PO_REQ_DISTRIBUTIONS_ALL.DISTRIBUTION_ID.

DELIVER_TO_LOCATION_ID : Unique identifier for the delivery location. References

HR_LOCATIONS_ALL.LOCATION_ID.

DESTINATION_TYPE_CODE : Final destination of the purchased items

DESTINATION_ORGANIZATION_ID : Final destination organization unique identifier.

References HR_ALL_ORGANIZATION_UNITS.ORGANIZATION_ID. Combined with

DESTINATION_SUBINVENTORY, forms a foreign key to

MTL_SECONDARY_INVENTORIES. Combined with WIP_ENTITY_ID, forms a foreign key to

WIP_ENTITIES. Combined with WIP_LINE_ID, forms a foreign key to WIP_LINES. Combined

with WIP_ENTITY_ID, WIP_OPERATION_SEQ_NUM, and

WIP_REPETITIVE_SCHEDULE_ID, forms a foreign key to WIP_OPERATIONS. Combined with

WIP_ENTITY_ID, WIP_OPERATION_SEQ_NUM, WIP_RESOURCE_SEQ_NUM, and

WIP_REPETITIVE_SCHEDULE_ID, forms a foreign key to WIP_OPERATION_RESOURCES

Description: PO_DISTRIBUTIONS_ALL contains accounting distribution information for a purchase order

shipment line. You need one row for each distribution line you attach to a purchase order shipment. There

are four types of documents using distributions in Oracle Purchasing:

1. Standard Purchase Orders 2. Planned Purchase Orders 3. Planned Purchase Order Releases 4. Blanket Purchase Order Releases

Each row includes the destination type, requestor ID, quantity ordered and deliver-to location for the

distribution.

Oracle Purchasing uses this information to record accounting and requisition information for

purchase orders and releases.

PO_DISTRIBUTIONS_ALL is one of five tables storing purchase order and release information.

Some columns in PO_DISTRIBUTIONS_ALL contain information only if certain conditions exist:

If you autocreate this accounting distribution from a requisition, REQ_DISTRIBUTION_ID corresponds to the ID of the requisition distribution you copy on the purchase order.

If you use a foreign currency on your purchase order, Oracle Purchasing stores currency conversion information in RATE and RATE_DATE.

If you use encumbrance, GL_ENCUMBERED_DATE and GL_ENCUMBERED_PERIOD_NAME contain encumbrance information Oracle Purchasing uses to create journal entries in Oracle General Ledger.

If you do not autocreate the purchase order from online requisitions, REQ_LINE_REFERENCE_NUM and REQ_HEADER_REFERENCE_NUM contain the requisition number and requisition line number of the corresponding paper requisition. These two columns are not foreign keys to another table.

If the distribution corresponds to a blanket purchase order release, PO_RELEASE_ID identifies this release.

If SOURCE_DISTRIBUTION_ID has a value, the distribution is part of a planned purchase order release.

If you cancel the distribution, Oracle Purchasing automatically updates QUANTITY_CANCELLED or GL_CANCELLED_DATE. Oracle Purchasing also enters UNENCUMBERED_AMOUNT if you use encumbrance.

You enter distribution information in the Distributions window, accessible through the Purchase

Orders and Releases windows.

PO_REQUISITION_HEADERS_ALL

Purchasing


Important columns:

REQUISITION_HEADER_ID : Requisition header unique identifier

PREPARER_ID : Unique identifier of the employee who prepared the requisition

SEGMENT1 : Requisition number

AUTHORIZATION_STATUS : Authorization status type

NOTE_TO_AUTHORIZER : Note to approver (Unused since release 8.0)

TYPE_LOOKUP_CODE : Requisition type

TRANSFERRED_TO_OE_FLAG : Indicates whether an internal requisition has been transferred to

Order Management.

INTERFACE_SOURCE_CODE : Source of requisition from Requisition Import

CLOSED_CODE : Close status


Description: PO_REQUISITION_HEADERS_ALL stores information about requisition headers. You need one

row for each requisition header you create. Each row contains the requisition number, preparer, status, and

description.

REQUISITION_HEADER_ID is the unique system-generated requisition number.

REQUISITION_HEADER_ID is invisible to the user. SEGMENT1 is the number you use to identify

the requisition in forms and reports. Oracle Purchasing generates SEGMENT1 using the

PO_UNIQUE_IDENTIFIER_CONTROL table if you choose to let Oracle Purchasing generate

requisition numbers for you.

PO_REQUISITION_HEADERS_ALL is one of three tables storing requisition information.

O_REQUISITION_HEADERS_ALL corresponds to the Header region of the Requisitions window.

SEGMENT1 provides unique values for each row in the table in addition to

REQUISITION_HEADER_ID.

PO_REQUISITION_LINES_ALL

Purchasing


Important columns:


LINE_NUM NUMBER : Line number

LINE_TYPE_ID : Line type

CATEGORY_ID : Item category unique identifier

ITEM_DESCRIPTION : Item description

QUANTITY NUMBER : Quantity ordered

DELIVER_TO_LOCATION_ID : Deliver-to location unique identifier

Description: PO_REQUISITION_LINES stores information about requisition lines. You need one row for each

requisition line you create. Each row contains the line number, item number, item category, item

description, need-by date, deliver-to location, item quantities, units, prices, requestor, notes, and suggested

supplier information for the requisition line.

LINE_LOCATION_ID identifies the purchase order shipment line on which you placed the

requisition. LINE_LOCATION_ID is null if you have not placed the requisition line on a purchase

order.

BLANKET_PO_HEADER_ID and BLANKET_PO_LINE_NUM store the suggested blanket

purchase agreement or catalog quotation line information for the requisition line.

PARENT_REQ_LINE_ID contains the REQUISITION_LINE_ID from the original requisition line

if you exploded or multisourced this requisition line.

PO_REQUISITION_LINES is one of three tables storing requisition information. This table

corresponds to the Lines region

of the Requisitions window.

PO_REQ_DISTRIBUTIONS_ALL

Purchasing


Important columns:

DISTRIBUTION_ID : Requisition distribution unique identifier

LAST_UPDATE_DATE : Standard Who column

LAST_UPDATED_BY : Standard Who column

REQUISITION_LINE_ID : Requisition line unique identifier

SET_OF_BOOKS_ID : Set of Books unique identifier

CODE_COMBINATION_ID : Unique identifier for the General Ledger charge account

DISTRIBUTION_NUM : Distribution number

ALLOCATION_TYPE : Method of allocation across distributions. Can be PERCENT

Description: PO_REQ_DISTRIBUTIONS_ALL stores information about the accounting distributions associated

with each requisition line. Each requisition line must have at least one accounting distribution. You need one

row for each requisition distribution you create. Each row includes the Accounting Flexfield ID and

requisition line quantity.

PO_REQ_DISTRIBUTIONS_ALL is one of three tables storing your requisition information. This

table corresponds to the requisition Distributions window, accessible through the Requisitions

window.

PO_HEADERS_INTERFACE

Purchasing


Important columns:

INTERFACE_HEADER_ID : Interface header unique identifier

BATCH_ID : unique identifier

INTERFACE_SOURCE_CODE : Interface source

PROCESS_CODE : Interface record status

ACTION : Interface action - ADD, NEW

GROUP_CODE : Requisition line grouping


DOCUMENT_TYPE_CODE : Document type to be created: PO or RFQ

DOCUMENT_SUBTYPE : Document subtype

DOCUMENT_NUM : Document number

Description: PO_HEADERS_INTERFACE is the interface table that holds header information for

the PDOI program to create standard/blanket purchase orders and catalog quotations.

The PDOI program validates your data, derives or defaults additional information and writes an

error message for every validation that fails into the PO_INTERFACE_ERRORS table

PO_LINES_INTERFACE

Purchasing


Important columns:

INTERFACE_LINE_ID : Interface line unique identifier


ACTION : Action to be completed: New or Add

Description: PO_LINES_INTERFACE is the interface table that holds lines information for the

PDOI program to create standard/blanket purchase orders and catalog quotations.


error message for every validation that fails into the PO_INTERFACE_ERRORS table.

PO_LINE_LOCATIONS_INTERFACE

Purchasing


Important columns:

INTERFACE_LINE_LOCATION_ID : Interface line location unique identifier



PROCESSING_ID : Identifier for the line locations processed in current request

Description: PO_LINE_LOCATIONS_INTERFACE is the interface table that holds line locations information for

the PDOI program to create standard/blanket purchase orders and catalog quotations.



PO_DISTRIBUTIONS_INTERFACE

Submitted by Anonymous on Tue, 07/13/2010 - 20:22

Purchasing


Important columns:



INTERFACE_DISTRIBUTION_ID : Interface distribution unique identifier

Description: PO_DISTRIBUTIONS_INTERFACE is the interface table that holds distribution information for the

PDOI program to create standard purchase order.



PO_INTERFACE_ERRORS

Purchasing


Important columns:

INTERFACE_TYPE : Error message source

INTERFACE_TRANSACTION_ID : Error transaction unique identifier

COLUMN_NAME : Error column name

ERROR_MESSAGE : Error message text

PROCESSING_DATE : Error transaction date

Description: PO_INTERFACE_ERRORS contains error message information generated by the open interface

programs in Oracle Purchasing. For every interface transaction row with errors, this table contains a row for

each column that has an error.

The INTERFACE_TYPE and INTERFACE_TRANSACTION_ID columns identify the Oracle

Purchasing program and interface transaction that generated the error message. The

COLUMN_NAME and ERROR_MESSAGE columns identify the interface column in error with a

descriptive error message. The PROCESSING_DATE column contains the date when the error

message was generated.

PO_REQUISITIONS_INTERFACE_ALL

Purchasing


Important columns:

TRANSACTION_ID : Transaction unique identifier

PROCESS_FLAG : Transaction processing state

INTERFACE_SOURCE_CODE VARCHAR2 : Interface transaction source

INTERFACE_SOURCE_LINE_ID : Interface transaction reference column

SOURCE_TYPE_CODE : Requisition source


AUTHORIZATION_STATUS : Authorization status type

Description: PO_REQUISITIONS_INTERFACE_ALL contains requisition information from other applications.

Each row includes all the information necessary to create approved or unapproved requisitions in Oracle

Purchasing. The Oracle Purchasing Requisition Import feature uses this information to create new requisition

headers, lines and distributions.

You use the Submit Request window to launch the Requisition Import program for any set of rows.

You identify the set of rows you want to import by setting the INTERFACE_SOURCE_CODE and

BATCH_ID columns appropriately in the interface table.

The Requisition Import program validates your data, derives or defaults additional information and

writes an error message for every validation that fails into the PO_INTERFACE_ERRORS table.

Then the program groups and numbers requisition lines according to the criteria you specify in the

GROUP_CODE and REQ_NUMBER_SEGMENT1 columns, and creates new requisitions.

Most of the columns in the PO_REQUISITIONS_INTERFACE_ALL table are identical to the

corresponding columns in

the PO_REQUISITIONS_HEADERS_ALL, PO_REQUISITION_LINES_ALL and

PO_REQ_DISTRIBUTIONS_ALL tables. You can additionally enter reference information in the

INTERFACE_SOURCE_LINE_ID column.

PO_REQ_DIST_INTERFACE_ALL

Submitted by Anonymous on Tue, 07/13/2010 - 20:41

Purchasing


Important columns:

ACCRUAL_ACCOUNT_ID : Unique identifier for the General Ledger accrual account

ALLOCATION_TYPE : Specifies the method of allocation across distributions. Can be PERCENT.

ALLOCATION_VALUE : Allocation split value

INTERFACE_SOURCE_CODE : Interface transaction source

INTERFACE_SOURCE_LINE_ID : Interface transaction reference column

Description: PO_REQ_DIST_INTERFACE_ALL is the interface table that creates multiple

distributions using Requisition Import.

RCV_HEADERS_INTERFACE

Purchasing


Important columns:

HEADER_INTERFACE_ID : Interface EDI header unique identifier

GROUP_ID : Interface group for set processing

ASN_TYPE : The document type: values are ASN, ASBN, or RECEIVE

TRANSACTION_TYPE : The transaction purpose code: values are NEW, REPLACE, ADD, or

CANCEL

RECEIPT_NUM : Receipt number

RECEIPT_HEADER_ID : Receipt system ID

VENDOR_NAME : Supplier name from ASN; used to derive VENDOR_ID

VENDOR_NUM : Supplier Num from ASN; used to derive VENDOR_ID

VENDOR_ID : Source supplier unique ID

VENDOR_SITE_CODE : Supplier site code from ASN; used to derive VENDOR_SITE_ID

VENDOR_SITE_ID : Source supplier site unique identifier

FROM_ORGANIZATION_CODE : Source organization code; used to derive from

ORGANIZATION_ID

FROM_ORGANIZATION_ID : Source organization unique identifier (internal transfers only)

INVOICE_NUM : EDI transaction 857 invoice number associated with the shipment/billing notice

(ASN with billing information)

INVOICE_DATE : EDI transaction 857 invoice date associated with the shipment/billing notice

TOTAL_INVOICE_AMOUNT : EDI transaction 857 invoice amount associated with the

shipment/billing notice

TAX_NAME : EDI transaction 857 tax name associated with the shipment/billing notice

TAX_AMOUNT : EDI transaction 857 tax amount associated with the shipment/billing notice name

indicated at the header level

FREIGHT_AMOUNT : EDI transaction 857 freight bill amount associated with the shipment/billing

notice

ORG_ID : Operational Unit Unique Identifier

OPERATING_UNIT : Operating Unit Name used to derive ORG_ID

VALIDATION_FLAG : Marked after open interface validation

Description: RCV_HEADERS_INTERFACE is an interface table that stores receiving header information.

RCV_TRNSACTIONS_INTERFACE

Purchasing


Important columns:

INTERFACE_CHARGE_ID : Entity identifier

AMOUNT : Charge amount

CURRENCY_CODE : Currency code of the charge

PARENT_HEADER_INTERFACE_ID : Identifier of the parent item transaction header interface.

Required for header level charges.

PARENT_INTERFACE_ID : Identifier of the parent item transaction interface. Required for line

level charges.

VENDOR_ID : Identifier of the charge providor

VENDOR_SITE_ID : Identifier of the charge providor site

PROCESSING_STATUS_CODE : The status of preprocessing this charge

TRANSACTION_STATUS_CODE : The status code of processing this charge

Description: RCV_CHARGES_INTERFACE stores charge data that will be used to import charges into Receiving

system through ROI. Each charge record needs to have a backing item transaction for Receiving processor to

pick it up. For header level charge, a reference to RCV_HEADERS_INTERFACE is required, while for line level

charge, a reference to RCV_TRNSACTIONS_INTERFACE is required.

RCV_SHIPMENT_HEADERS

Purchasing

Table Or View:

Table

Important columns:

SHIPMENT_HEADER_ID - NUMBER - Receipt header unique identifier

RECEIPT_SOURCE_CODE - VARCHAR2 - Source type of the shipment - VENDOR, INTERNAL

ORDER or

CUSTOMER

VENDOR_ID - NUMBER - Source supplier unique identifier

VENDOR_SITE_ID

ORGANIZATION_ID - NUMBER - Source organization unique identifier

SHIPMENT_NUM - Shipment number assigned by the shipment's source

RECEIPT_NUM - Receipt number

Description: RCV_SHIPMENT_HEADERS stores common information about the source of your

receipts or expected receipts. You group your receipts by the source type and the source of the

receipt. Oracle Purchasing does not allow you to group receipts from different sources under one

receipt header.

There are two receipt source types, Supplier and Internal Order, that you need to use when receiving

against different source document types. You use a receipt source type of 'Supplier' when receiving

items that you ordered from an external supplier using

a purchase order. When you receive items that are part of an inter-organization transfer, or when

receiving items that you request from your inventory using an internal requisition, the receipt type

would be 'Internal Order'. The 'Internal Order' receipt source type populates the

ORGANIZATION_ID column.

Oracle Purchasing creates a receipt header when you are entering your receipts or when you perform

inter-organization transfers using Oracle Inventory. When Oracle Inventory creates a receipt header

for an intransit shipment, the receipt number is not populated until you receive the shipment.


HR_ALL_ORGANIZATION_UNITS Table HRMS Anonymous

HR_OPERATING_UNITS View HRMS Anonymous

HR_LOCATIONS_ALL Table HRMS Anonymous

HR_ORGANIZATION_INFORMATION Table HRMS Anonymous

HR_ALL_ORGANIZATION_UNITS

HRMS


Important columns:

ORGANIZATION_ID

Description: HR_ALL_ORGANIZATION_UNITS holds the definitions that identify business groups and the

organization units within a single business group. Additional information about classifications and

information types for each organization is held in HR_ORGANIZATION_INFORMATION.

HR_OPERATING_UNITS

HRMS

Table Or View: View

Important columns:

BUSINESS_GROUP_ID

ORGANIZATION_ID NAME

SET_OF_BOOKS_ID

DEFAULT_LEGAL_CONTEXT_ID

SHORT_CODE

Description: HR_OPERATING_UNITS is a view which contains the information about all the operating units in

a particular instance.

HR_LOCATIONS_ALL

HRMS


Important columns:

LOCATION_CODE

LOCATION_ID

BUSINESS_GROUP_ID

Description: HR_LOCATIONS_ALL holds information about specific work locations defined for an enterprise,

including address details.

HR_ORGANIZATION_INFORMATION

HRMS


Important columns:

ORGANIZATION_ID

BUSINESS_GROUP_ID

Description: HR_ORGANIZATION_INFORMATION is used to hold two distinct sets

of organization information. When ORG_INFORMATION_CONTEXT

is set to CLASS this table acts as an intersection table between organizations and organization classifications.

ORGANIZATION_ID identifies the organization and ORG_INFORMATION1 holds the organization classification

name. This information is maintained by the organization classifications block of the Organization form.

When ORG_INFORMATION_CONTEXT is set to an information type held in HR_ORG_INFORMATION_TYPES

the ORG_INFORMATION120 columns hold details for the specific information type. This information is

maintained by a predefined protected descriptive flexfield. (Org Developer DF.)

From where do you access this addl. Org. Info. screen. I'm trying to find out the navigation path of

the screen is based on HR_ORGANIZATION_INFORMATION table.

Its available in organization form

Navigation

Inventory -> Setup -> Organizations -> Organizations

Query the organization and then on organization clasification select name 'inventory' and click on

others and select accounting information

INVENTORY


MTL_SYSTEM_ITEMS_B Table Inventory Anonymous

MTL_TXN_REQUEST_HEADERS Table Inventory Anonymous

MTL_TXN_REQUEST_LINES Table Inventory Anonymous

MTL_TRANSACTION_TYPES Table Inventory Anonymous

MTL_SYSTEM_ITEMS_B

Inventory


Important columns:



ACCOUNTING_RULE_ID : Accounting rule identifier

INVOICING_RULE_ID : Invoicing rule identifier

PURCHASING_ITEM_FLAG: Flag indicating purchasing item

SHIPPABLE_ITEM_FLAG : Flag indicating shippable item

CUSTOMER_ORDER_FLAG : Flag indicating customer orderable item

INTERNAL_ORDER_FLAG : Flag indicating internally orderable item

SERVICE_ITEM_FLAG : Flag indicating service item

INVENTORY_ITEM_FLAG : Flag indicating inventory item

ENG_ITEM_FLAG : Flag indicating engineering item

INVENTORY_ASSET_FLAG : Flag indicating item is an inventory asset

PURCHASING_ENABLED_FLAG : Flag indicating item is purchasable

CUSTOMER_ORDER_ENABLED_FLAG : Flag indicating item is customer orderable

INTERNAL_ORDER_ENABLED_FLAG : Flag indicating item is internally orderable

SO_TRANSACTIONS_FLAG VARCHAR2 : Sales order transactions flag

MTL_TRANSACTIONS_ENABLED_FLAG : Flag indicating item is transactable

STOCK_ENABLED_FLAG : Flag indicating item is stockable

BOM_ENABLED_FLAG : Flag indicating item may appear on a BOM

BUILD_IN_WIP_FLAG : Flag indicating item may be built in WIP

Description: MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for

inventory items, engineering items, and purchasing items. You can specify item-related information in fields

such as: Bill of Material, Costing, Purchasing, Receiving, Inventory, Physical attributes, General Planning,

MPS/MRP Planning, Lead times, Work in Process, Order Management, and Invoicing.

You can set up the item with multiple segments, since it is implemented as a flexfield. Use the

standard 'System Items' flexfield that is shipped with the product to configure your item flexfield.

The primary key for an item is the INVENTORY_ITEM_ID and ORGANIZATION_ID. Therefore,

the same item can be defined in more than one organization.

Each item is initially defined in an item master organization. The user then assigns the item to other

organizations that need to recognize this item. A row is inserted for each new organization the item is

assigned to. Many columns such as MTL_TRANSACTIONS_ENABLED_FLAG and

BOM_ENABLED_FLAG correspond to item attributes defined in the

MTL_ITEM_ATTRIBUTES table. The attributes that are available to the user depend on which

Oracle applications are installed. The table MTL_ATTR_APPL_DEPENDENCIES maintains the

relationships between item attributes and Oracle applications.

Two unit of measure columns are stored in MTL_SYSTEM_ITEMS_B table.

PRIMARY_UOM_CODE is the 3-character unit that is used throughout Oracle Manufacturing.

PRIMARY_UNIT_OF_MEASURE is the 25-character Unit of Measure that is used throughout

Oracle Purchasing. Unlike the PRIMARY_UOM_CODE, the Unit of Measure is language-

dependent attribute, however, PRIMARY_UNIT_OF_MEASURE column stores value in the

installation base language only.

Items now support multilingual description. MLS is implemented with a pair of tables:

MTL_SYSTEM_ITEMS_B and MTL_SYSTEM_ITEMS_TL. Translations table

(MTL_SYSTEM_ITEMS_TL) holds item Description and Long Description in multiple languages.

DESCRIPTION column in the base table (MTL_SYSTEM_ITEMS_B) is for backward

compatibility and is maintained in the installation base language only.

MTL_TXN_REQUEST_HEADERS

Inventory


Important columns:


REQUEST_NUMBER : Request number of the move order


MOVE_ORDER_TYPE : Type of move order


Description: This table stores all of the move order headers. The headers contain all information which

pertains to entire move orders, including the transaction type of the move order, the move order type, the

move order status, and the request number of the move order.

MTL_TXN_REQUEST_LINES

Inventory


Important columns:

LINE_ID : Line identifier


LINE_NUMBER : Line number



FROM_SUBINVENTORY_CODE : From subinventory code

TO_SUBINVENTORY_CODE : To subinventory code

QUANTITY : Quantity requested

QUANTITY_DELIVERED : Quantity which has been delivered

Description: The table MTL_TXN_REQUEST_LINES stores all of the move order lines. The lines are requests to

move some quantity of an item from a source location to a destination location or account. Each move order

line must be tied to a specific move order header.

When a line is detailed or pick released, the quantity detailed is updated appropriately and

transaction lines are created in MTL_MATERIAL_TRANSACTIONS_TEMP. When the transaction

lines are transacted, the quantity delivered is updated.

MTL_TRANSACTION_TYPES

Inventory


Important columns:


TRANSACTION_TYPE_NAME : Name of the transaction type

TRANSACTION_ACTION_ID : Transaction action identifer that is associated with this type

TRANSACTION_SOURCE_TYPE_ID : Transaction source type identifier that is associated with

this transaction type

SHORTAGE_MSG_BACKGROUND_FLAG : Flag indicating background notification should be

provided for this transaction

USER_DEFINED_FLAG : Set to 'Y' if this type is user-defined

Description:

MTL_TRANSACTION_TYPES contains seeded transaction types and the user defined ones.

USER_DEFINED_FLAG will distinguish the two. The table also stores the

TRANSACTION_ACTION_ID and TRANSACTION_SOURCE_TYPE_ID

that is associated with each transaction type.

Table-all

Documents

Transcript of Table-all