Types of transactions in AR

There are only 6 types of transactions available

1) Invoice (Bill customer for products and services)
2) Debit memo (Bill customers for products or services that were not included on the
original invoice)
3) Credit memo (Credit customers (On-account credits do not refer to specific invoices.))
4) Deposits (Bill customers for contractual agreements)
5) Guarantee (A contractual agreement that is referenced by invoices (Bill customers for
the items on the invoice, not the guarantee.))
6) Chargeback (Adjust the remaining balance of an existing debit item to zero, and create
a new debit item to bill customer for unpaid balance of original invoice.)
n R12 we have 2 key flexifields and those 2 are optionals
1) Sales tax location key flexield: this flexfiled is used to calculate tax based on the
location wise
2) Territory key flexfiled: By using this key flexfield we can find out the the sales
information based on the location wise
For AR and CM : Receipt Number is Required andFor AP and CM : Payment Document
Number is required
Transaction Flexfield in auto invoice.
1. Transaction Flexfields are used to capture information that will help you trace
transactions from Oracle Receivables back to the systems from which they originated, in
Auto Invoices.AutoInvoice ensures that each Transaction Flexfield is unique so you can
refer to previously processed transactions.
2. Transaction Flexfield actually identifies the the uniqueness among the Multiple lines of
a single Invoice
There are 11 types of invoices in AP..
1. Standard
2. Prepayment
3. Debit Memo
4. Credit Memo
5. With Holding Tax
6. Expense Report
7. Mixed Invoice
8. Interest
9. PO default
10.Quick Match
11. Recurring Invoice
Auto invoice:- Auto invoice is the interface between Order management and Account
Receivables. Auto invoice picks data from AR interface tables, validate and create

transactions in AR.
Auto Lock box:- Auto lock box is used to process payment advise from bank. Bank send
the lock box file to Oracle apps. This file contain information of payment received in the
bank from the customers. Auto lock box process the file and create AR receipt in AR and
Auto Cash application process can apply receipts to the open invoices of the customer.
Conc Program for Auto invoice.
For Auto Invoice : RAXMTR (Auto invoice Master Program) whichmark records in interface
table to be processesd. then it calls RAXTRX (Auto invoiceImport Program) which
validated the records and updates into base table.For Customer Invoice : RACUST
Encumbrance

In Oracle Applications, encumbrances are used with only AP-PO-GL modules and not AR.
Budgets are created in GL. Typically, encumberances are used to reserve funds for a
purchase you are going to make in future. Thus the available funds are calculated using
the formula Budget amount minus encumberances minus actual expenses.
Encumberance feature can be used in Oracle Applications based on the setups in
Financial Options in AP. Purchasing creates encumbrances when you reserve funds for a
requisition or purchase order. Payables reverses the PO encumberances when you create
accounting entries for invoices.

************************************************88
_ALL : Table holds all the information about different operating units. Multi-Org
environment. You can also set the client_info to specific operating unit to see the data
specific to that operating unit only.
_TL are tables corresponding to another table with the same name minus the _TL. These
tables provide multiple language support. For each item in the table without _TL there can
be many rows in the _TL table, but all with different values in the LANGUAGE column.
_B these are the BASE tables.
They are very important and the data is stored in the table with all validations.
It is supposed that these table will always contain the perfect format data.
If anything happens to the BASE table data, then it is a data corruption issue.
_F these are date tracked tables, which occur in HR and Payroll. For these there are two
date columns EFFECTIVE_START_DATE and EFFECTIVE_END_DATE which together with the
PK identifies a row uniquely. The date intervals cannot overlap. Many think they are
Secured data. Guess someone from Oracle confirms.
_V tables are the views created on base tables
_VL are views for multi language tables which combines the row of the base table with
the corresponding row of the _TL table where the LANGUAGE = USERENV('LANG').
_S are sequences, used for finding new values for the prima

ry key of a table.
_A are Audit Shadow Tables
_AVN and _ACN are Audit Shadow Views (when data was changed, and with what values