GL

The journal Import interface uses the GL_INTERFACE table as a bridge between
external systmens
and the Oracle General Ledger base tables. For each journal line that needs to be
imported, a \
single record is inserted into GL_INTERFACE table.
For transfers initiated from Oracle subledgers, the system automatically populates
the GL_INTERFACE
table, and then starts the journal import process.
GL Data Model
GL_JE_BATCHES
Journal Batches
GL_JE_HEADERS
Journals
GL_JE_LINES
Journal Lines
GL_BALANCES
Balances for every code combination, currency and period
A journal batch is a group of related journals that are posted together. The period
in
rise to
to

the

which the journals belong is stored at batch level. Each journal in a batch gives
a separate record in the GL_JE_HEADERS
A journal is a group of journal lines that balance. The sum of the debits is equal
the sum of credits. The currency code is stored at the journal level.
The GL_JE_LINES table holds a record for each journal line. The lines record the
accounted amounts, either debit or credit, and the account code combination that
amount will be posted to.
GL_JE_BATCHES>---------------------------FND_PERIODS
|
|
^
|
GL_JE_HEADERS>-------------FND_CURRENCIES
|
|
|
|
^
|
|
GL_JE_LINES>--GL_CODE_COMBINATIONS
|
|
V
|
|
|
|
^
^
^
GL_BALANCES
GL_SETS_OF_BOOKS
GL_PERIODS
GL_CODE_COMBINATIONS
FNS_CURRENCIES
GL_BALANCES

A row for each set of books

A row for each calender period
All the Account Flexfield segment values
A row for each currency
Balances for every account code, currency, and
period combination.

GL Posting Porcess
The posting process takes a journal batch and updates the account balances in
GL_BALANCES according to all the individual debits and credits that are contained
in the GL_JE_LINES tables belonging to that journal batch. Once the journal batch
has been posted , the attribute GL_BATCHES.POSTED is set to Yes, so that it cannot
be posted a second time. The GL_BALANCES is used to improve performance.
Many processes such as standard reporting and all FSG reprting require the use of
account balances that are contained in the GL_BALANCES.
FSG (Financial Statement generator)
Payables
Purpose:
- Paying suppliers on time, but no earlier than necessary.
- Taking discounts when prudent.
- Preventing duplicate billing/invoice

- Avoiding overdrafts of your bank accounts.

AP_BATCHES
AP_CHECKS
|
|
^
^
AP_INVOICES------<AP_PAYMENT_SCHEDULES----AP_INVOICE_PAYMENTS
|
^
AP_INVOICE_DISTRIBUTIONS
AP_INVOICES
debit memo.

amount

Invoice header information. One row per invoice, credit memo or

carries the VENDOR_ID and the invoice AMOUNT.

AP_INVOICE_DISTRIBUTIONS
Invoive lines including tax lines. Each distribution carries an

and an account code-combination ID.

AP_PAYMENT_SCHEDULES
Holds one row per invoice unless the invoice is due to be paid in
installments. Each installment is characterized by a due date and
an amount.
AP_CHECKS
Holds payment documents, including checks, EFT payments, or wire
transfers
AP_INVOICE_PAYMENTS
Holds permanent record of all payment documents that have been
issued
to pay invoices and invoice installments
APPOST
not
the

GL transfer process in the Concurrent manager that searches AP_INVOICES,

AP_INVOICE_DISTRIBUTIONS, AP_SELECTED_INVOICE_CHECKS tables for new rows that have
been posted to GL. For each new transaction, journal entry lines are inserted into

GL_INTERFACE table. APPOST updates each transferred transaction as posted and

automatically
submits the GL Joural import process. If you have any unposted transactions, you
cannot
close the period.
RECEIVABLES
Produces three documents to notify customers.
- An invoice
- A statement is a summary of the transactions over a period of time. It shows all
open transactions. It may also show payments made within the period.
- A dunning notice to inform the customers of past-due obligations.
QuickCash
Lets you enter receipts quickly, with a minimum of information.
Stored in AR_INTERIM_CASH_RECEPTS and AR_INTERIM_CASH_RECEIPT_LINES
Batches of QuickCash receipts must be posted to transfer them from
these
interim tables to the regular receipt tables within Oracle
Receivables.
TIP: Records are continually inserted and deleted into these two
tables.
Rebuild these from time to time.
AR Datamodel
AR_ADJUSTMENTS Storing adjustments to invoices. The amount of each adjustment, the
activity name, and the accounting information is held in this
table.
When an invoice is adjusted, the AMOUNT_DUE_REMAINING in
AR_PAYMENT_SCHEDULES is updated.
AR_BATCHES
Grouping individual receipts; this table is optional. If used this

batch holds information about the batch source used, the bank

account,

and control totals.

AR_CASH_RECEIPT_HISTORY
Storing the current sales status of a receipt, receipt history,
and receipt reversals. Receipts go through a cycle of steps
that include confirmation, remittance, and clearance. Each step
creates rows in this table. The CODE_COMBINATION_ID column stores
the

accounts that are debited and credited as part of these steps.

AR_CASH_RECEIPTS

Storing one row for each receipt. Invoice-related receipts have

payment
related to the invoice)

schedules and applications, while miscellaneous receipts (not

have distributions stored on AR_MISC_CASH_DISTRIBUTIONS.

AR_MISC_CASH_DISTRIBUTIONS
Storing all the accounting entries for miscellaneous cash
applications.
Miscellaneous cash is income not related to a customer, such as
stock
dividents or bank interest.
AR_PAYMENT_SCHEDULES
Storing two types of records: invoice related and receipt-related.
The table
contains one record for each invoice installment, or one row per
receipt.
Different transactions types are identified by the CLASS;
INV - invoice, DB - debit memo, CM - credit memo, GUAR - guarantee,
CB - charge back, PMT - receipt.
AR_RECEIVABLES_APPLICATIONS
Linking the receipts applied to invoices with the credit memos
applied to
invoices. This table holds the amount applied, the status, and the
accouting distribution for the application.
RA_BATCHES
Storing information such as batch source and control totals.
Invoice
batches are optional.
RA_CUST_TRX_LINE_GL_DIST
Storing all accounting records for a transaction. These are
distinguished
by the ACCOUNT_CLASS designation, which can be freight, receivable,
revenue, tax, unearned revenue, unbilled receivable, or charges.
The ARGLTP program uses GL_DATE and AMOUNT to post the correct
amounts
to GL for each transaction.
RA_CUST_TRX_LINE_SALESREPS
Storing sales credit assignments for invoice lines.
RA_CUSTOMER_TRX Storing header information for invoices, debit memos, credit memos,
chargebacks, deposits, and guarantees. Each row includes general
information
such as customer, transaction type, and printing information.
This is a fundemental table in Receivables.
RA_CUSTOMER_TRX_LINES
Each transaction line relates to just one transaction in
RA_CUSTOMER_TRX.
Lines may be either revenue item lines, tax lines, or freight.
Each row records the quantities ordered, invoiced, and credited, as
well as
unit prices.
(Invoices, Chargebacks,

Debit memos, Credit memos, Commitments)

RA_BATCHES
|
^
RA_CUSTOMER_TRX---<AR_ADJUSTMENTS
|
-----<AR_PAYMENT_SCHEDULES
|
^
RA_CUST_TRX_LINES
|
|
|
^
|
RA_CUST_TRX_LINE_GL_DIST
^
RA_CUST_TRX_LINE_SALESREPS

Receipts
AR_BATCHES
|
^
AR_CASH_RECEIPTS
|
^
AR_CASH_RECEIPT_HISTORY
|
^
AR_DISTRIBUTIONS

CASH MANAGEMENT
- Bank reconsiliation
- Cash forecasting
Only available in GUI.
CM DATA MODEL
CE_STATEMENT_HEADERS_ALL
Holds one row for each seperate bank statement.
CE_STATEMENT_LINES
Holds one row for each line on a bank statement.
Oracle Assets
Oracle Purchasing
PO and PER tables
Oracle Inventory
MTL tables
Concurrent Manager
(Navigate Other Concurrent). Press the Enter Query function twice
to automatically retrieve the last query.
Enter a colon in one of the query fields. SQL*Forms then displays a window
where the user can enter a precise query like:
REQUEST_ID > 943124 AND (STATUS_CODE = 'E' OR PHASE_CODE ='R')
FND_CONCURRENT_REQUEST - Row for every job to be run.
Aplications Object Library (AOL)
Tuning Common to add indexes on the user attributes populated by DDF's (Descriptive
Flexfields)
Sometimes indexes are missing after a patch or an upgrade. Consult the techical
manual to check all the indexes are there.
Rebuilding Interface Tables
Rows are continually inserted and deleted from interface tables.
The following tables should be routinely monitored and rebuild:
GL_INTERFACE
Journal import tables
AR_PAYMENTS_INTERFACE
Lockbox table
RA_INTERFACE_LINES_ALL
RA_INTERFACE_DISTRIBUTIONS_ALL