Table RA_CUSTOMERS

Oracle Applications Data Structure

by Jenny Chan, Red Rock Consulting

Column
CUSTOMER_NUM BER CUSTOMER_CLASS_CODE SALES_CHANNEL_CODE 1000 High Technology 1001 Telecom 1003 Other 1005 Telecom 1006 Other 1007 High Technology 1021 1002 High Technology 1008 High Technology 1086 Other 1087 1088 Other 1004 High Technology 1109 1110 Commercial Commercial Commercial Commercial Internal Commercial Commercial Commercial Commercial

CUSTOMER_ID CUSTOMER_NAM E 1000 Business World

1001 A merican Telephone and Telegraph 1003 United Parcel Service 1005 A T&T Universal Card 1006 Computer Service and Rentals 1007 General Technologies 1021 V ision 1002 Imaging Innovations, Inc. 1008 Total Internet 1146 Department of Def ense 1148 Federal Parts 1150 Modern Truck 1004 Hilman and A ssoc iates 1256 Red Rock Consulting 1257 Shell Rock Consulting

Record

Introduction
Oracle Applications has a very flexible architecture containing valuable information but with flexibility comes complexity in the underlying data structure. Understanding the basic Oracle Applications structure is critical in retrieving important and relevant content. This information is an asset and when used appropriately can be used as a competitive advantage. This article provides a high level overview of the Oracle Applications data structure and some business examples. However, before we get understand the data structure there is some technical terminology that needs explanation. The business examples will be illustrated in Oracle SQL*Plus but you can use the same table joins in your preferred reporting writing tool such as Oracle Query builder and Oracle Discoverer. Please refer to the Oracle Technical Reference manuals for more detail on the entity data models, table descriptions and functional decomposition. Also note that the following information is based on Oracle Applications Release 11.03 data structures.

View CAR_COMM_CUSTOMER_V

CUSTOMER_ID CUSTOMER_NAME 1000 Business World 1001 American Telephone and Telegraph 1005 AT&T Universal Card 1006 Computer Service and Rentals 1007 General Technologies 1002 Imaging Innovations, Inc. 1008 Total Internet 1004 Hilman and A ssociates

CUSTOMER_NUMBER CUSTOMER_CLASS_CODE 1000 High Technology 1001 Telecom 1005 Telecom 1006 Other 1007 High Technology 1002 High Technology 1008 High Technology 1004 High Technology

Synonym Another name assigned to a table for easy identification and used for data classification between Oracle Application modules. Primary Key The column or columns that uniquely identify each row of a table. Foreign Key One of more columns in one table whose values refer to the primary key values in another table. Query Series of command to instruct the database to retrieve the data you have specified. Relationship

Definitions
Table The basic entity of storage in a relational database management system. Consist of one or more units of information (records) each of which contains a number of data elements or fields (or columns). Record/Row One set of related information contained in a table. Column/Field A subdivision of a table, with a column name and a specific data type. View A data source made up of columns from one or more database tables combined into one logical table or object.

A connection between two or more tables. Entity Relationship Diagram (ERD) Diagram that display the relationships between tables.

ERD

RA_CUSTOMERS (RC) CUSTOMER_ID CUSTOMER_NAME CUSTOMER_NUMBER STATUS CUSTOMER_TYPE CUSTOMER_PROSPECT_GROUP CUSTOMER_CLASS_CODE CUSTOMER_CATEGORY_CODE

NUM VC2 VC2 VC2 VC2 VC2 VC2 VC2

Primary Key

Relationship
RA_ADDRESSES_ALL (RA) ADDRESS_ID NUM CUSTOMER_ID NUM STATUS VC2 COUNTRY VC2 ADDRESS1 VC2 ADDRESS2 VC2 ADDRESS3 VC2 ADDRESS4 VC2 CITY VC2 POSTAL_CODE VC2 STATE VC2 ORG_ID NUM

Foreign Key

Tips
There is a screen in Oracle Applications where you would like to report the information.

Click on Help > About This Record from the Menu.

Copyright 2000, Red Rock Consulting Pty Ltd All Rights Reserved

APPS
AR FND
There is a table name (e.g. ITEM) you would like to use but unsure of the exact name.

GL FA INV

AP CM PO

OE

Login to SQL*Plus and type SELECT table_name FROM all_tables WHERE table_name LIKE %ITEM% There is a column (e.g. CUSTOMER_NAME) that you would like to use but unsure which table the column belongs to.

Oracle Applications Data Structure

Oracle General Ledger Gl_code_combinations : Setup > Accounts > Combinations This table stores the valid account combinations. The value in your chart of account segments are stored in the columns segment1 to segment30 depending on your application configuration. For example, say your chart of accounts is Company Cost Centre Account then segment1 = company, segment 2 = cost centre and segment3 = account. However, this sequencing of segments is not guaranteed therefore, its best to check your configuration. Another important column is the account_type which signifies your account is an Asset, Liability, Revenue, Expense or Owners Equity account. Gl_je_batches

Login to SQL*Plus and type SELECT table_name, column_name FROM all_tab_columns WHERE column_name = CUSTOMER_NAME The columns org_id and organization_id are different. Organization_id refers to the inventory organizations in Oracle Inventory and org_id refers to the operating unit. Table names that ends with _all has the column org_id included. The org_id signifies the operating unit. Therefore, if you have multiorganization functionality, you will need to use the _all tables. Note that not all tables will have _all suffix. The majority of the entities describes in the following are tables but you may find that there is a view that combines all your requirements. These views will be based on non _all tables. You need to type the following in SQL*Plus to see the data in these views. exec dbms_application_info.set_client_info(org_ id) Org_id is the operating unit in hr_organization_units. The following illustrates a simplified view of the Oracle Applications data schema. Each data schema is mapped to an application module. The apps schema has a number of synonyms and views of all the Oracle Application modules. The fnd has all the schema all the Oracle Application foundation information such as user profiles, responsibility and value sets. You need to login to the appropriate schema when using query tools on a table. Therefore, consult your Database Administrator regarding security to the schema/schemas you need access.

Journals > Enter

This table stores the journal entry batches. Journal entries are batched in General Ledger. Some columns of interest include: Name Set_of_books_id (when you have more than one set of book, youll also need to link to gl_sets_of_books) Status Default_period_name Posted_date Posting_run_id

Gl_je_headers : Journals > Enter This table stores the journal entry headers. There is always two journal lines for each journal header. Some columns of interest includes :

Copyright 2000, Red Rock Consulting Pty Ltd All Rights Reserved

Je_category Period_name Set_of_books_id (when you have more than one set of book, youll also need to link to gl_sets_of_books) Posted_flag Je_source Name Status Ap_invoice_distributions_all : Invoices > Entry > Invoices : This table stores the accounting information for the invoice you have entered. There is one row for each invoice disribution, that is this table corresponds to the Distributions window. Some columns of interest includes : Line_type_lookup_code Dist_code_combination_id (credit entry) Accts_pay_code_combination_id (debit_entry) Base_amount (in functional currency)

Gl_je_lines : Journals > Enter This table stores the journal entry lines. The entered_dr and entered_dr stores the amount in the entered currency whereas the accounted_dr and accounted_dr stores the amount in the functional currency. Other columns of interest includes : Set_of_books_id (when you have more than one set of book, youll also need to link to gl_sets_of_books) Period_name Status Description Reference_1..reference10 (these columns links back to your Sub ledgers) For example, for Purchasing transactions Reference_1 = PO Reference_2 = po_headers_all.po_header_id Reference_3 = po_distributions_all.po_distribution_id Reference_4 = po_headers_all.segment? (this is the purchase order number Oracle Payables Ap_invoices_all : Invoices > Entry > Invoices This table stores all the invoices you enter. For an invoice to be approved, the total invoice amount must be stored in Ap_invoice_distributions_all and ap_payment_schedules_all. Some columns of interest includes : Invoice_num Invoice_date Amount_paid Invoice_currency_code Invoice_type_lookup_code Payment_status_flag

Ap_checks_all : Payments > Entry > Payments This table stores payments to suppliers. Some columns of interest includes : Amount (in functional currency) Check_date Bank_account_name Check_number Payment_method_lookup_code Payment_type_flag

Ap_invoice_payments_all : Payments > Entry > Payments This table stores invoice payments to suppliers. This table is updated when you confirm an automatic payment batch, enter a manual payment or process a Quick Payment. Void payments are represented as a negative of the original payment line.Some columns of interest includes : Accounting_date Period_name Amount Payment_num

Ap_payment_distributions_all : Payments > Entry > Payments : This table stores accounting information for payments. There is at least one CASH payment distribution for each invoice payment. Additional rows may include DISCOUNT, GAIN and LOSS distributions where appropriate. Some columns of interest includes : Line_type_lookup_code (CASH/DISCOUNT/GAIN/LOSS) Base_amount

Ap_invoice_distributions_all : Invoices > Entry > Invoices

Oracle Purchasing Po_Vendors

Copyright 2000, Red Rock Consulting Pty Ltd All Rights Reserved

: Supply Base > Suppliers This table stores supplier information. Some columns of interest includes : Segment1 (supplier number) Vendor_name Terms_id Vendor_type Ship_to_location (link to hr_locations for location information) Bill_to_location (link to hr_locations for location information)

Category_id (link to mtl_categories for the category name)

Po_line_locations_all : Purchase Orders > Purchase Orders This table stores purchase order shipment schedules and blanket agreement price breaks. A purchase order is closed when QUANTITY is equal to QUANTITY_RECEIVED. Some columns of interest includes : Quantity Quantity_accepted Quantity_received Quantity_cancelled Need_by_date Ship_to_organization_id (link to org_organization_definitions for the organization code)

Po_vendor_sites_all : Supply Base > Suppliers This table stores supplier sites information. Some columns of interest includes : Pay_site_flag Purchasing_site_flag Address_line1 to address_line3 City State Area_code Zip

Po_distributions_all : Purchase Orders > Purchase Orders This table stores the accounting information on a purchase order shipment. This table is used for Standard and Planned Purchase Orders and Planned and Blanket Purchase Order Release. Some columns of interest includes : Quantity_ordered Quantity_billed Amount_billed Quantity_delivered Quantity_cancelled Destination_organization_id (link to org_organization_definitions for the organization code) Destination_subinventory

Po_headers_all : Purchase Orders > Purchase Orders This table stores the seven types of purchasing documents such as Purchase Order and Blanket Agreement. Segment1 is the document number (i.e. purchase order number) Some columns of interest includes : Agent_id (link to per_people_f for the buyer) Type_lookup_code

Rcv_shipment_headers : Receiving > Receipts This table stores the receiving information. The three receipt sources are Supplier, Inventory and Internal Order. There is one receipt header per receipt source. Some columns of interest includes : Receipt_num Shipment_num Receipt_source_code Shipped_date Ship_to_org_id

Po_lines_all : Purchase Orders > Purchase Orders This table stores purchasing document lines. Some columns of interest includes : Line_num Item_description Unit_price Unit_meas_lookup_code (unit of measure) Quantity Item_id (link to mtl_system_items for the item number)

Rcv_shipment_lines : Receiving > Receipts

Copyright 2000, Red Rock Consulting Pty Ltd All Rights Reserved

This table stores information about items that have been shipped and/or received from a receipt source. Some columns of interest includes : Line_num Quantity_shipped Unit_of_measure Item_id (link to mtl_system_items for item number) To_organization_id (link to org_organization_definitions for organization code) To_subinventory Shipment_line_status_code (EXPECTED, FULLY RECEIVED, PARTIALLY RECEIVED) Quantity_received Quantity_shipped

Transaction_source_name

Mtl_transaction_accounts : Transactions > Material Distributions (Inquiry) This table stores the inventory accounting information. There are two rows in this table for each transaction in mtl_material_transactions. Some columns of interest includes : Transaction_date Gl_batch_id Accounting_line_type Base_transaction_value

Mtl_system_items : Items > Master Items or Items > Organization Items This table stores the item definition. An item must exist in an inventory organisation. Your item number is stored in the columns segment1 to segment20 depending on your application configuration. If you have configured your items to have to segments then you may be using segment1 and segment2 Some columns of interest includes : Segment1 to segment20 Description Invetory_item_flag Purchasing_item_flag Inventory_asset_flag Stock_enabled_flag Invoiceable_item_flag Shippable_item_flag So_transaction_flag Mtl_transactions_enabled_flag Primary_unit_of_measure

Oracle Inventory Org_organization_definitions : Setup > Organizations > Parameters This view contains basic information on all inventory organisations. Some columns of interest includes : Organization_code Organization_name Set_of_books_id (when you have more than one set of book, youll also need to link to gl_sets_of_books) Inventory_enabled_flag

Mtl_secondary_inventories : Setup > Organizations > Subinventories This table stores all subinventory information for an inventory organization. Some columns of interest includes : Secondary_inventory_name Description

Mtl_onhand_quantities : On-hand, Availability > On-hand Quantities This table stores quantity on hand in a location for each item. Some columns of interest includes : Date_received Transaction_quantity Subinventory_code

Mtl_material_transactions : Transactions > Material Transactions (Inquiry) This table stores all inventory transactions including cost updates. Some columns of interest includes : Transaction_quantity Transaction_type_id Transaction_source_type_id

Cst_item_costs : Costs > Item Costs

Copyright 2000, Red Rock Consulting Pty Ltd All Rights Reserved

This table stores the item cost information. Note that there can be multiple costs per item and the actual cost is where the cost type is Frozen. Some columns of interest includes : Cost_type_id (link to cst_cost_types) Item_cost

This table stores invoice, debit memo, chargeback, commitment and credit memo header information. Some columns of interest includes : Cust_trx_type_id (link to ra_cust_trx_types_all) Set_of_books_id (when you have more than one set of book, youll also need to link to gl_sets_of_books) Terms_id (link to ra_terms) Trx_number (invoice number) Trx_date (invoice date)

Oracle Receivables Ra_customers : Customers > Standard This table stores customer information. Some columns of interest includes : Customer_name Customer_number Status Customer_prospect_code Customer_type Orig_system_reference (for imported customers from an external source)

Ra_customer_trx_lines_all : Transactions > Transactions This table stores the invoice, debit memo, chargeback, commitment and credit memo line information. Some columns of interest includes : Line_number Description Quantity_ordered Quantity_credited Quantity_invoiced Unit_standard_price Unit_selling_price Line_type Extended_amount Revenue_amount

Ra_addresses_all : Customers > Standard This table stores customer address information and your remit-to addresses. Some columns of interest includes : Status Orig_system_reference (for imported customer addresses from an external source) Address1 to address4 City State Postal_code

Ra_cust_trx_line_gl_dist_all : Transactions > Transactions This table stores the accounting information for revenue, unearned revenue, unbilled receivables, receivables, charges, freight and tax for each invoice or credit memo line. Some columns of interest includes : Amount_gl_date Gl_posted_date Account_class (CHARGES/FREIGHT/TAX/REC/REV/UNBILL/UNEA RN) Acctd_amount (functional currency)

Ra_site_uses_all : Customers > Standard This table stores the customers site and site purpose. You must have one row for each address. A customer must have one bill to address for Receivables. A customer must have one ship to address and one bill to address for Order Entry. Some columns of interest includes : Site_use_code (BILL_TO, SHIP_TO, STMTS, DUN/LEGAL) Primary_flag Status Location

Ar_cash_receipts : Receipts > Receipts This table stores the payment information. Some columns of interest includes : Set_of_books_id (when you have more than one set of book, youll also need to link to gl_sets_of_books) Status (APP, UNAPP, UNID, NSF, STOP, REV)

Ra_customer_trx_all : Transactions > Transactions

Copyright 2000, Red Rock Consulting Pty Ltd All Rights Reserved

Type (CASH, MISC) Receipt_number Amount Currency_code Pay_from_customer Receipt_date

Order_category (I, P. S, R, RMA) Order_number Purchase_order_num Original_system_source_code (for imported orders from an external source) Original_system_reference (for imported orders from an external source) Order_type_id (link to so_order_types_all for order type) Date_ordered S1 to s30 S1_date to s30_date

Ar_receivable_applications : Receipts > Receipts This table stores accounting entries for cash and credit memo applications. Some columns of interest includes : Amount_applied Line_applied Tax_applied Application_type Display Gl_date Set_of_books_id (when you have more than one set of book, youll also need to link to gl_sets_of_books)

So_lines_all : Orders, Returns > Orders, Returns This table stores the orders and returns line information. The s1 to s30 and s1_date to s30_date relates to the order line cycle status. Some columns of interest includes : Line_type_code (DETAIL, PARENT, REGULAR, RETURN) Ordered_quantity Cancelled_quantity Selling_price Price_list_id (links to so_price_lists for price list) Schedule_date Promise_date

Ar_payment_schedules : Transactions > Transactions and Receipts > Receipts This table stores all transactions except adjustments and miscellaneous cash receipts. This table is updated when a transaction occurs against an invoice, debit memo, chargeback, credit memo, on-account credit, or receipt. Some columns of interest includes : Amount_due_original Status Class (DEP, DM, PMT, GUAR, CM, CB, INV) Due_date Amount_due_remaining Invoice_currency_code Amount_applied Anmount_credited Amount_adjusted

So_line_details : Orders, Returns > Orders, Returns This table stores order scheduling information. Some columns of interest includes : Released_flag Quantity Schedule_date Delivery (link to mtl_demand for reservation details)

So_picking_batches_all : Shipping > Release Sales Orders or Shipping > Release Sales Orders, SRS This table stores the batch of orders that have been pick released. The header_count column indicates the number of picking headers are contained in a picking batch. So_picking_headers_all : Shipping > Release Sales Orders or Shipping > Release Sales Orders, SRS

Oracle Order Entry So_headers_all : Orders, Returns > Orders, Returns This table stores the orders and returns information. The s1 to s30 and s1_date to s30_date relates to the order cycle status. Some columns of interest includes :

Copyright 2000, Red Rock Consulting Pty Ltd All Rights Reserved

This table stores the picking headers within a picking batch. Some columns of interest includes : Status_code (BACKORDERED, BACKORDER RELEASE, CLOSED, OPEN, PENDING, IN PROGRESS) Pick_slip_number Picked_by (link to per_people_f for picked by user) Date_released Date_confirmed Date_shipped

Some columns of interest includes : Name Planned_departure_date Actual_depature_date Waybill Date_closed

So_picking_lines_all : Shipping > Release Sales Orders or Shipping > Release Sales Orders, SRS This table stores the picking lines for a picking header. Some columns of interest includes : Requested_quantity shipped_quantity Date_requested Cancelled_quantity

So_picking_line_details : Shipping > Release Sales Orders or Shipping > Release Sales Orders, SRS This table stores the location for the picking lines that have been reserved. Some columns of interest includes : Requested_quantity Serial_number

Wsh_departure : Shipping > Departure Planning> Departure Planning or Shipping > Departure Planning > New Departures This table stores departure information for departure planning. Some columns of interest includes : Name Planned_departure_date Actual_depature_date

Wsh_delivery : Shipping > Departure Planning> Departure Planning or Shipping > Departure Planning > New Deliveries This table stores delivery information within a departure.

Copyright 2000, Red Rock Consulting Pty Ltd All Rights Reserved

g l _

c o d e _

c o m

L 1

i n a t i o n s

g l _

j e _ j e _

b b

a t c h e s a t c h _
G L 3

L 2

o r g _ i d m i d t l _

o r g a n i z a t i o n _

I N

V 1

o r g a n i z a t i o n _ d e f i n i t m i o t n l s_

i d m

a t e r i a l _

I N

V 3

t r a n s a c t i o n _ t r a n s a c t mi o tn l s _ i d

i d

t r a n s a c t i o n _

I N

V 6

a c c o u n t

i n v e n t o r y _ i t e m _ o r g a n i z a t i o s n u _ b i i dn v e n t o r y _ c o d e o r g a n i z a t i o n _ i d s e c o n d a r y _
I N V 2

g l _

j e _ j e _

h e a d e r s h e a d e r _ l i n e s
G L 4

i n v e n t o r i e sm

t l _

s y s t e m

I N

V 4

i t e m

i n v e n t o r y _ i t e m _ s o r g a n i z a t i o n _ i d i d c s t _ i t e m
I N

i d

s e c o n d a r y _

i n v e n t o r y _ m

n a mi n e v e n t o r y _ i t e m _ o r g a n i z a t i o n _ i d o n h a n d _
I N V 5

c o d

e _

c o m

i n a t i o n _

i dg l _

j e _

G
t r x _ a l l

e n e r a l
a r _ t r x _ c a s h _ c a s h _ i d
A A R 7

L e d n ve er n t o r y I g
s o _ i d h e a d e r s _ h e a d e r _
O E 2 O E 1

t l _

q u a n t i t y

c o s t s

V 7

c u s t o m r a _ c u s t o m
A R 1

b i l l _ t o _ c u s t o m e r _ i d e r s h i di p _ t o _ c u s t o m e r _ i d _ r a _ c u s t o m
A

e r s e r _

e r _

R 4

r e c e i p t s r e c e i p t _ l e _
R 8

h e a d e r _ a l l i d

i d

s o _

p i c k i n g _

E 4

a t c h e s _ i d e r s _

a l l

c u s t o m r a _
A R 2

b i l l _ t o _ s i t e _ u s e _ i d i d c u s t o m e r _ t r x _ i d s h i p _ t o _ s i t e _ u s e _ i d c u s t o m e r _ a l l r a _ c u s t o m e r _
A R 5

o r d e r _ i d e r _

b a t c h _ h e a d e r _ i d s o _ p i c k i n g _
O E 5

a d d r e s s e s _ a d d r e s s _

t r x e r _

l i n e s _ aa rl _ l t r x g l _ _ l i n e _

r e c e i v a b i d p a y m

a p p l i c a t is o o n _ s l i n e s _ s c h e d u l e _ i d l i n e _ l i n e _
O

a l l

l i n e _

h e a d

a l l i d w s h _ d e p a r t u r e i d
O E 8

i d r a _ u s e _ i d

c u s t o m c u s t _ t r x
A1 R 6

e n t _
A R 9

i d
E 3

p i c k i n g _ o r d l i n e _ l i n e _ s o _ d e t a i l _ i d i d p i c k i n g _
O E 6

h e a d e r _ a l l

r a _

s i t e _

u s e s _ a l l s i t e _

R 3

l i n e _

a d i s t _ ra _l l p a y m

e n t _

s c h

e d u l e ss o _

d e t a i l s

l i n e s _

p i c k i n g _ p i c k i n g _
O

R e c e i v a b l e sO
a p _ i n v o i c e s _ i n v o i c e _ a p _ i n v o i c e _ d
A P 2 A P 1

r d e r
p o _

E n t r y
v e n d o r s v e n d o r _ i d
P O 1

s o _

l i n e _

E 7

d e p a r t u r e _ l i n pe l _ a i n d n e d _ d e p a r t u r e _ i d a c t u a l _ d e p a r t u r e _ i d d e t a i l s w s h _ d e l i v e r i e s
O E 9

i n v o i c e _ a l l i d i n v o i c e _

i d a p _ i d

p a y m

e n t _

P 3

v e n d o r _

i d p o _ h e a d p o _ p o _ i d

s c h e d u l e s _

a l l

e r s _

P O

a l l e r _ i d

r c v _

s h i p m s h i p m

e n t _ e n t _
P O 8

P O

e a d e r s i d

h e a d
P O

h e a d e r _ l i n e s

i s t r i b

u t i o n s _

a l al p _

c h e c k s _ c h e c k _

P 4

a l l i d e n t s _ a l l i d l Pa al y a b l e s

p o _

v e n d o r _

P O

s i t e s _ a l l v e n d o r _

s i t e _

l i n e s _ p o _

a l l i d a l l i d

r c v _

s h i p m

e n t _

l i n e _
P O 5

a p _

i n v o i c e _

p a y m

P 5

p o _

l i n e _

l o c a t i o n s _

i n v o i c e _ a p _ i n v o i c e _
A P 6

p a y m

e n t _

l i n e _

l o c a t i o n _
6

d i s t r i b

u t i o n s _

P u r c h a s i n g

p o _

d i s t r i b

P O

p o _ d i s t r i b u t i o n s _ a l l

u t i o n _

i d

C r o s s G G L 1 L 1

p p l i c a t i o n c o d e _ c o d e _ c c c s a p a s a t a o i o o o o n i n h n r n r d d d u d e e e r _ _ _ c o m c o m b b

J o i n s i n a t i o n _ i n a t i o n _ i o n _ i o n _ i o n _ e = i d i d i d i d i d ' O = = = = = = = A R 6 P O 6 P O 6 I N V A P 2 A P 6 O E 3 E N T O E 6 E N T P O 7 P O O O A 8 E 2 E 2 R 5 , , R R , A c o9 d e _ R b v r Pa d l c o m b i n a t i o n _ t _ n t o u e _ b i i d A P 1 _ 6 p o _ h e a d e r _ i d i d = = P O P O A R A R A R 1 2 1 2 2 R R P O P O v v c s a s a o e e u i t n i t n r 3 6 p o _ p o _ h e a d e r _ d i s t r i b i d i d

G L 1 G L 1 G L 1 I N V I N I N I N I N I N V V V V V

3 3 3 3 4 4

c k d i p d a n d g a n v e

c o m b i n a t c o m b i n a t c o m b i n a t c e _ l i n e _ i d s o u r c e _ c o d i n g _ l i n e _ i d s o u r c e _ c o d m e n t _ n u m b s o u r c e _ c o d s a c t i o n _ s o s o u r c e _ c o d n i z a t i o n _ i d n t o r y _ i t e m

A Y Y ' '

R R

u d g e t _ a c c o u n a r i a n c e _ a c c o u e f e r e n c e _ a c c 6c c t s _ p a y _ c o d i s t _ c o d e _ c o m i n e _ d e t a i l _ i d l i n e _ n u m l i n e _ i d

i d , a c c r uA a P l _ i d n t s A P c o m b i n a A t iP o n a t i o n _ i d E O O E O A E R R R

a c c po ou _n td _i s i td r , i b v i d v c s b i a i a i a e e u h n n s i

u t i o n _

u t i o n _

1 1n _ 1 1 1 5 5 5

d o r _ i d d o r _ s i t e _ i t o m e r _ i d p _ t o _ s i t e _ t o _ f a n t f a n t f a n t s i t e _ _ f a _ f a _ f a l i c l i c l i c

= d= = u= s e _ i d

i d

e = ' O R D E e r = e = ' R C V ' u r c e _ i d= e = ' R C V ' = _ i d =

p i c k i n g _ s h i p m s h i p m

i l l _ n t n n t n n t n e r i e r d i e r d i d

u s= e _

e n t _ e n t _

i d i d

A A

o r g a n i z a t i o n _ i d P Oi n 4 v ,e n t o r y _ i t e m _

c e e r c e e r c e e r

n e _ a t = e _ c o n n e _ a t = e _ c o n n e _ a t = e _ c o n

t r t t r t t r t

i b Ou t E e 1 1 e x t = ' O i b Ou t E e 2 6 e x t = ' O i b Ou t E e 6 7 e x t = ' O

D l i n D p i R D

n d o r _ n d o r _ s t o m e e _ u s e d s i t e e _ i s e d s i t e d e r _ n E R E N e _ i d E R E N c k i n g _ E R E N

i d s i t e _ i d r _ i d _ i d _ u s e _ c o d e _ i d _ u s e _ c o d e u m b e r T R Y ' T R Y ' l i n e _ i d T R Y '

= =

' S ' B

I P _ T

T O

O '

'

I L L _

Copyright 2000, Red Rock Consulting Pty Ltd All Rights Reserved

Business Examples
To illustrate how important knowing the Oracle Applications data structure, I have included some business examples. Reconciliation Are you having problem reconciling your General Ledger to your subledger ? This process can take a long time to resolve if you dont know where to look. The following SQL*Plus example displays the sum of the Trade Receipts from your Receivables subledger for a given period name (i.e. Apr-00) by the General Ledger batch name. This example also assumes that you are entering receipts in batches. You can even go further and look at the accounts for which these trade receipts have debited and credited by joining ar_receivable_applications to the gl_code_combinations table via code_combination_id. The gl_import_references table links the General Ledger journal tables to Receivables.
SELECT Gb.name gl_batch_name, B.name ar_batch, NVL(SUM(DECODE(ra.status,'APP', ra.amount_applied,0)),0) NVL(SUM(DECODE(ra.status,'ACC', ra.amount_applied,0)),0) NVL(SUM(DECODE(ra.status,'UNAPP',ra.amount_applied,0)),0) NVL(SUM(DECODE(ra.status,'UNID', ra.amount_applied,0)),0) FROM ar_receivable_applications_all ra, ar_cash_receipts_all cr, ar_batches_all b, ar_cash_receipt_history_all crh, gl_je_batches gb WHERE ra.cash_receipt_id = cr.cash_receipt_id AND cr.cash_receipt_id = crh.cash_receipt_id AND crh.batch_id = b.batch_id AND (crh.batch_id, crh.cash_receipt_id, gb.je_batch_id) IN (SELECT DISTINCT ab.batch_id, ac.cash_receipt_id, b.je_batch_id FROM ar_batches_all ab, ar_cash_receipt_history_all ah, ar_cash_receipts_all ac, gl_import_references i, gl_je_headers h, gl_je_batches b WHERE h.je_header_id = i.je_header_id AND b.je_batch_id = i.je_batch_id AND i.reference_2 = ah.cash_receipt_id AND ah.cash_receipt_id = ac.cash_receipt_id AND ab.batch_id(+) = ah.batch_id AND h.je_source = 'Receivables' AND h.je_category = 'Trade Receipts' AND h.je_batch_id = b.je_batch_id AND h.period_name = 'Apr-00') GROUP BY gb.name, b.name ORDER BY 1, 2 /

+ + + rec_amount

Information Management You schedule your orders but you are running low in stock for some items. The following example displays the reservation information for the item parameter. Based on this information, you can then decide which orders can be rescheduled. The table mtl_demand stores the reservation information and fnd_user contains user information. The majority of the tables have the columns created_by, last_updated_by that represents the user who entered the transaction and the last user to have updated the transaction, respectively.
SELECT DECODE(d.reservation_type, 1, 'On Demand', 2, 'Reserved') Res_type, SUBSTR(u.user_name, 1, 20) User_name, SUBSTR(i.segment1, 1, 10) Item, c.customer_name cust_name, c.customer_number cust_number, h.order_number Ord_no, substr(l.shipment_priority_code, 1, 10) ship_code, Copyright 2000, Red Rock Consulting Pty Ltd All Rights Reserved

h.date_ordered Date_ordered, r.organization_code Org, d.line_item_quantity demand_qty FROM so_headers_all h, mtl_demand d, mtl_sales_orders s, mtl_system_items i, org_organization_definitions r, fnd_user u, ra_customers c, so_lines_all l WHERE h.created_by = u.user_id AND d.inventory_item_id = i.inventory_item_id AND d.organization_id = i.organization_id AND h.order_number = s.segment1 AND r.organization_id = d.organization_id AND c.customer_id = h.customer_id AND d.demand_source_line = l.line_id AND l.header_id = h.header_id AND d.line_item_quantity > 0 AND i.segment1 BETWEEN '&&item_from' AND '&&item_to' AND d.demand_id IN (SELECT MAX(d1.demand_id) FROM mtl_demand d1 WHERE d1.line_item_quantity > 0 AND d1.demand_source_type in (2, 8) AND d1.parent_demand_id IS NOT NULL GROUP BY d1.reservation_type, d1.parent_demand_id) ORDER BY DECODE(d.reservation_type, 1, 'Demand', 2, 'Reserved'), SUBSTR(u.user_name, 1, 20), SUBSTR(i.segment1, 1, 10) /

Your customers have been returning products, but why ? Is it the product quality, is it the delivery ? How can the business improve ? You enter return reasons on Return Material Authorisations (RMAs) and the following example reviews the returns for a given date range (where &&from_date and &&to_date are parameters in SQL*Plus) for when the RMAs have been created.
SELECT l.transaction_reason_code reason_code, c.customer_name cust_name, SUBSTR(s.segment1, 1, 10) item, h.order_number ord_no, t.trx_number inv_no, 0 - NVL(l.ordered_quantity, 0) - NVL(l.cancelled_quantity, 0) rma_quantity, NVL(tl.quantity_credited, 0) qty_credited, NVL(tl.quantity_credited, 0) * NVL(unit_selling_price, 0) total_cr, u.user_name creator_name, h.creation_date creation_date FROM fnd_user u, mtl_system_items s, ra_customers c, ra_customer_trx_all t, ra_customer_trx_lines_all tl, so_headers_all h, so_lines_all l WHERE h.order_category = 'RMA' AND h.cancelled_flag is null AND tl.customer_trx_id = t.customer_trx_id(+) AND tl.interface_line_attribute6(+) = l.line_id AND c.customer_id = h.customer_id AND u.user_id = h.created_by AND l.inventory_item_id = s.inventory_item_id AND l.warehouse_id = s.organization_id AND h.header_id = l.header_id AND h.creation_date between to_date('&&from_date', 'DD-MON-RRRR') AND to_date('&&to_date', 'DD-MON-RRRR') ORDER BY 1, 2 /

Copyright 2000, Red Rock Consulting Pty Ltd All Rights Reserved

Alerts You need to ensure that all orders entered for the day is booked in order to progress to the next step. Therefore, you may setup an Oracle Alert based on the following SQL*Plus and email the output to the Sales Order Administrator. The following can also highlight training issues if one particular user is not booking orders on a regular basis as indicated by the Created_by column.
SELECT o.organization_code Org_name, SUBSTR(msi.segment1, 1, 10) Item, SUBSTR(msi.description, 1, 45) Item_desc, sh.order_number Order_number, sh.date_ordered Date_ordered, SUBSTR(fu.user_name, 1, 12) Created_by, NVL(sl.ordered_quantity, 0) - NVL(sl.cancelled_quantity, 0) Qty_ordered, sl.selling_price*sl.ordered_quantity Ext_amount FROM so_headers_all sh, mtl_system_items msi, so_lines_all sl, fnd_user fu, org_organization_definitions o WHERE sh.header_id = sl.header_id AND o.organization_id = msi.organization_id AND sh.order_category IN ('R', 'RMA') AND sl.inventory_item_id = msi.inventory_item_id AND sl.warehouse_id = msi.organization_id AND sh.created_by = fu.user_id AND (sh.s1 = 5 or sh.s1 = 15) AND sh.cancelled_flag is null AND sh.creation_date BETWEEN TO_DATE('&&from_date, 'DD-MON-RR') AND TO_DATE('&&to_date', 'DD-MON-RR') ORDER BY o.organization_code, SUBSTR(msi.segment1, 1, 10), SUBSTR(msi.description, 1, 45), sh.order_number /

About the Author Jenny Chan is an Applications Consultant with Red Rock Consulting based in Sydney, Australia. She has 9 years experience within the Oracle environment, 5 of which have been working with Oracle Applications. You can reach her by email at chanj@redrock.net.au and there are web pages of articles and tips at http://www.redrock.net.au.

Copyright 2000, Red Rock Consulting Pty Ltd All Rights Reserved