Professional Documents
Culture Documents
MTL_SYSTEM_ITEMS_B
= cost_of_sales_account
GL AND PO
GL_CODE_COMBINATIONS
code_combination_id
PO_DISTRIBUTIONS_ALL
= code_combination_id
PO AND AP
PO_DISTRIBUTIONS_ALL
Po_distribution_id
AP_INVOICE_DISTRIBUTIONS_ALL
= po_distribution_id
PO_VENDORS
vendor_id
AP_INVOICES_ALL
= vendor_id
PO AND SHIPMENTS
PO_HEADERS_ALL
Po_header_id
RCV_TRANSACTIONS
= po_header_id
PO_DISTRIBUTIONS_ALL
Po_distribution_id
RCV_TRANSACTIONS
= po_distribution_id
AP_INVOICE_DISTRIBUTIONS_ALL
= RCV_TRANSACTION_ID
PO AND INV
PO_REQUISITION_LINES_ALL
item_id
org_id
MTL_SYSTEM_ITEMS_B
= inventory_item_id
= organization_id
PO AND HRMS
PO_HEADERS_ALL
Agent_id
PO AND REQUISITION
PO_DISTRIBUTIONS_ALL
req_distribution_id
PO_REQ_DISTRIBUTIONS_ALL
= distribution_id
HR_EMPLOYEES
employee_id
MTL_SYSTEM_ITEMS_B
= organization_id
HR_EMPLOYEES
= employee_id
OM AND AR
OE_ORDER_HEADERS_ALL
TO_CHAR( Order_number)
OE_ORDER_LINES_ALL
TO_CHAR(Line_id)
RA_CUSTOMER_TRX_LINES_ALL
= interface_line_attribute1
RA_CUSTOMER_TRX_LINES_ALL
= interface_line_attribute6
OE_ORDER_LINES_ALL
reference_customer_trx_line_id
RA_CUSTOMER_TRX_LINES_ALL
= customer_trx_line_id
OM AND SHIPPING
OE_ORDER_HEADERS_ALL
WSH_DELIVARY_DETAILS
HEADER_ID
OE_ORDER_HEADERS_ALL
LINE_ID
= SOURCE_HEADER_ID
WSH_DELIVARY_DETAILS
SOURCE_LINE_ID
AP AND AR (BANKS)
AR_CASH_RECEIPTS_ALL
AP_BANK_ACCOUNTS
REMITTANCE_BANK_ACCOUNT_ID = ABA.BANK_ACCOUNT_ID
AP AND AR
HZ_PARTIES
AP_INVOICES_ALL
PARTY_ID
OM AND CRM
OE_ORDER_LINES_ALL
LINE_ID
= PARTY_ID
CSI_ITEM_INSTANCES(Install Base)
= LAST_OE_ORDER_LINE_ID
AR_RECEIVABLE_APPLICATIONS_ALL
AR_ADJUSTMENTS_ALL
HZ_PARTIES
A party is an entity that can enter into a business relationship.
This table stores basic information about parties, which is true regardless of this relationship to the
deploying company. Entities are modeled only once in HZ_PARTIES, regardless of how many roles they
play. For example, if an organization is a customer, a distributor, and a partner, there is still only one
record for them in HZ_PARTIES.
Parties can be one of four types:
Organization - Oracle Corporation
Person - Jane Doe
Group Doc Household
Relationship - Jane Doe at Oracle Corporation
HZ_PARTY_SITES
This table links a party (HZ_PARTIES) and a location (HZ_LOCATIONS) and stores location-Specific
party information such as a persons mail stops at their work address.
One party can point to one or more party sites.
One location can point to one or more party site.
Party sites serve as the intersection between parties and locations, allowing for a many-to-many
relationship between the two.
HZ_LOCATIONS
A location is a point in geographical space described by an address and/or geographical Indicators such
as latitude or longitude.
This table stores information about an address such as: street address and postal code.
This table provides physical location information about parties (organizations and people) and customer
accounts.
Records in HZ_LOCATIONS can store delivery and postal code information about a location, store
latitude and longitude, and can be used to determine the appropriate calculations and tax rates for sales
tax and VAT calculations.
HZ_RELATIONSHIPS
This table stores information about relationships between two entities, for example, one party and another
party.
The SUBJECT_ID and OBJECT_ID columns specify the relationship that exists between two parties.
For example, if the party relationship type is Parent Of, then a holding company could be the
SUBJECT_ID in the relationship while one of its subsidiaries could be the OBJECT_ID. Creating a party
contact causes a party relationship to be created.
A party can have different relationships with one or more other parties that can change over time.
HZ_ORGANIZATION_PROFILES
This table stores a variety of information about a party of type Organization.
This table gets populated when a party of type ORGANIZATION is created.
Historical data is also stored in this table.
HZ_PERSON_PROFILES
This table stores a variety of information about a party of type Person.
For example, this table could contain the correct spelling and phonetic pronunciation of the persons
name.
Some information in this table may also be entered into the HZ_PARTIES table.
HZ_ORG_CONTACTS
This table stores a variety of information about an organization contact.
The records in this table provide information about a contact position such as job title, rank, and
department.
This table is not used to store information about a specific person or organization. For example, this
table may include a record for the position of Vice President of Manufacturing that indicates that the
contact is a senior executive, but it would not include the name of the person in that position.
HZ_CUST_ACCOUNTS
This table stores information about customer/financial relationships established between a Party and the
deploying company.
Because a party can have multiple customer accounts, this table may contain several records for a
single party. For example, an individual person may establish a personal account, a family account, and a
professional account for a consulting practice.
HZ_CUST_ACCT_SITES_ALL
This table stores information about customer/financial account sites information.
Stores information about customer sites. One customer account can have multiple sites.
HZ_CUST_SITE_USES_ALL
This table stores information about the business purposes assigned to a customer account site.
A customer account site can have multiple purposes, but each record in this table only specifies one
purpose for a customer account site. For example, a customer account site may be assigned as a ship-to
site in one record and as a bill-to site in another record.
HZ_CUST_ACCOUNT_ROLES
This table stores information about a role or function that a party performs as related to a customer
account. For example, Jane Doe might be the Legal Contact for a specific customer account of
Corporation ABC. Note that account ownership such as financial responsibility for an account is
determined by the single party ID that is stored directly on the HZ_CUST_ACCOUNTS table.
HZ_CONTACT_POINTS
This table stores information about how to communicate with parties or party sites using electronic media
or methods such as Electronic Data Interchange (EDI), e-mail, telephone, telex, and the Internet.
Each medium or method should be stored as a separate method in this table. For example, the
attributes of a complete telephone number connection should be stored in a record, while EDI information
should be stored in a different record.
RA_CUSTOMER_TRX_ALL
This table stores invoice, debit memo, commit-ment, chargeback, bills receivable, and credit memo
header information.
Each row includes general invoice information such as customer, transaction type, and printing
instructions.
You need one row for each invoice, debit memo, commitment, and credit memo you create in Oracle
Receivables and these are all distinguished by their transaction types stored in RA_CUST_ TRX_
TYPES_ALL.
RA_CUSTOMER_TRX_LINES_ALL
This table stores information about invoice, debit memo, credit memo, bills receivable, and commitment
lines. It describes to the customer the charges that appear on these documents.
AR_PAYMENT_SCHEDULES_ALL
This table stores all transactions except adjust-ments and miscellaneous cash receipts. A miscellaneous
cash receipt is one that is not connected to a customer.
All customer-related activity is logged in this table.
This table is updated when an activity occurs against an invoice, debit memo, chargeback, credit memo,
on-account credit, bills receivable,
receipt, or commitments.
RA_CUST_TRX_TYPES_ALL
This table stores information about each transaction type for all classes of transactions, for example,
invoices, commitments, and credit memos.
Each row includes Auto Accounting information
as well as standard defaults for the resulting invoices. The primary key for this table is
CUST_TRX_TYPE_ID.
AR_TRANSACTION_HISTORY_ALL
This table is a Bills Receivable-specific table containing the history of a transactions lifecycle.
A new row is created each time there is activity on the transaction or the status of the transaction has
changed.
This table stores the header for the Receivables posting information.
AR_DISTRIBUTIONS_ALL
This table stores the accounting distributions for cash receipts, miscellaneous receipts, adjustments,
credit memo applications, cash receipt applications, and bills receivable transactions.
AR_CASH_RECEIPTS_ALL
This table stores one record for each receipt entry.
All cash receipts are logged in this table.
Oracle Receivables creates records concurrently in the AR_CASH _RECEIPT_ HISTORY_ ALL,
AR_PAYMENT_ SCHEDULES_ ALL, AR_DISTRI-BUTIONS_ALL, and AR_ RECEIVABLE_ APPLICATIONS_ALL tables for invoice-related receipts.
For receipts that are not related to invoices, records are created in the AR_MISC_CASH_
DISTRIBUTIONS_ALL table instead of the AR_RECEIVABLE_APPLICATIONS_ ALL table.
AR_CASH_RECEIPT_HISTORY_ALL
This table stores all of the activity that is contained for the life cycle of a receipt.
Each row represents one step.
The status field for that row tells you which step the receipt has reached.
Possible statuses are Approved, Confirmed, Remitted, Cleared, and Reversed.
AR_RECEIVABLE_APPLICATIONS_ALL
This table stores all accounting entries for cash and credit memo applications.
Each row includes the amount applied, status, and accounting flex field information.
AR_MISC_CASH_DISTRIBUTIONS_ALL
This table stores all accounting entries for miscellaneous cash applications.
Miscellaneous cash cannot be invoiced, such as stock revenue, interest income, and investment
income.
AR_CASH_RECEIPTS_ALL stores one record for each payment, and this table stores one record for
each distribution of the receipt.
AR_RECEIPT_CLASSES
This table stores the different receipt classes that you define.
Receipt classes determine whether the receipt[s] belonging to this class are created manually or
automatically, and whether the receipts go through the different steps in a receipts life-cycle.
AR_RECEIPT_METHODS
This table stores information about Payment Methods, receipt attributes that you define and assign to
Receipt Classes to account for receipts and their applications.
For automatically created receipts, a Payment Method defines the rules for creating these receipts.
For manually created receipts, a Payment Method defines a user-definable type for the receipt.
Each Payment Method is associated with a set of bank accounts, which forms the set of bank accounts
you can assign to your receipt.
AR_ADJUSTMENTS_ALL
This table stores information about the adjustment applied to the Invoices.
OM - Order Management
Table Name Description
OE_ORDER_HEADERS_ALL stores header information for orders
in Order Management.
OE_ORDER_LINES_ALL stores information for all order lines in
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
Pick Confirmed
wsh_delivery_details Released_status=Y Hard Reservations. Picked the stock. Physical movement of
stock
Ship Confirmed
wsh_delivery_details Released_status=C Y To C:Shipped ;Delivery Note get printed Delivery assigned to
trip stopquantity will be decreased from staged
mtl_material_transactions On the ship confirm form, check Ship all box
wsh_new_deliveries If Defer Interface is checked I.e its deferred then OM & inventory not updated. If
Defer Interface is not checked.: Shipped
oe_order_lines_all Shipped_quantity get populated.
wsh_delivery_legs 1 leg is called as 1 trip.1 Pickup & drop up stop for each trip.
oe_order_headers_all If all the lines get shipped then only flag N
Autoinvoice
wsh_delivery_details Released_status=I Need to run workflow background process.
ra_interface_lines_all Data will be populated after wkfw process.
ra_customer_trx_all After running Autoinvoice Master Program for
ra_customer_trx_lines_all specific batch transaction tables get populated
Price Details
qp_list_headers_b To Get Item Price Details.
qp_list_lines
Items On Hand Qty
mtl_onhand_quantities TO check On Hand Qty Items.
Payment Terms
ra_terms Payment terms
AutoMatic Numbering System
ar_system_parametes_all you can chk Automactic Numbering is enabled/disabled.
Customer Information
hz_parties Get Customer information include name,contacts,Address and Phone
hz_party_sites
hz_locations
hz_cust_accounts
hz_cust_account_sites_all
hz_cust_site_uses_all
ra_customers
Document Sequence
fnd_document_sequences Document Sequence Numbers
fnd_doc_sequence_categories
fnd_doc_sequence_assignments
Default rules for Price List
oe_def_attr_def_rules Price List Default Rules
oe_def_attr_condns
ak_object_attributes