Basic Concepts in Oracle Financials - Important Tables

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
Journals > Enter
This table stores the journal entry batches. Journal entries are batched in General Ledger.
Some columns of interest includes :
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 :
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
Gl_je_lines
Journals > Enter
This table stores the journal entry lines.
The entered_dr and entered_cr stores the amount in the entered currency whereas the accounted_dr and accounted_cr
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 Subledgers)
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_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)
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
Oracle Purchasing
Po_vendors
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)
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_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
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)
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_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
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
Rcv_shipment_lines
Receiving > Receipts
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
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 organisation.
Some columns of interest includes :
Secondary_inventory_name
Description
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
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 configurati on. 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
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
Cst_item_costs
Costs > Item Costs
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
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_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_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
Ra_customer_trx_all
Transactions > Transactions
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)
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_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/UNEARN)
Acctd_amount (functional currency)
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)
Type (CASH, MISC)
Receipt_number
Amount
Currency_code
Pay_from_customer
Receipt_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)
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


About Oracle Apps
partner-pub-3478852466551521:xd3en3s33ig ISO-8859-1
Search

www.aboutoracleapps.com/2007/07/gl-concepts-2.html





Advance Computer Tips
About Online Tips

Popular Articles
Setting up MULTI-ORG

Basic Concepts : AOL

Oracle Apps AR Overview.

Must know concepts of GL/AP/AR

Oracle Finance Functional

FAQ-Oracle Apps AR Functional

Free Oracle Apps vis instance.

Oracle Financials Tutorials
Basic Concepts in Oracle AP - Part1

Basic Concepts in Oracle AP - Part2

Basic Concepts in Oracle AR - Part1

Basic Concepts in Oracle AR - Part2

Basic Concepts in Oracle GL - Part1

Basic Concepts in Oracle GL - Part2

Basic Concepts in Oracle Cash Management- Part1

Basic Concepts in Oracle Cash Management- Part2

Pay On Receipt in Oracle Applications -Tutorial

Recurring Invoice - A complete Tutorial



31 July 2007
Basic Concepts in Oracle GL - Part2
2.8 Consolidation
Consolidated Set of Books
Consolidation is the period-end process of combining the financial results of separate subsidiaries with
the parent organization to form a single, combined statement of financial results. The Global
Consolidation System (GCS) provides the flexibility to help you manage your consolidation needs
regardless of your organization structure.


Consolidated data is required at the end of year usually when companies prepare their balance sheets.
Decide the Global Set of Books Get the Parent SOB and the Subsidiary SOB; keep the Method as
Transaction / Balance. Prepare the Mappings, Mapping Sets as we have to map the subsidiary A/C to
Parent A/C.



Remember that we have to map the Subsidiary A/C to Parent A/C.
Use Accounting Rules



After defining the Accounting Rules for the Subsidiary Accounts Transfer the Consolidation Data Set.
Enter the period , One can define the elimination set to eliminate the transactions .create eliminate set if u
want to eliminate Automatic Interfund Eliminations or certain formulae based eli minations can be done.

3.0 Financial Statement Generator: Reporting tool

Generate financial reports, such as statements of revenues, expenditures, and changes in fund balance
and balance sheets, based upon data in your general ledger.
Suppose we want to prepare a report as given below

INCOME
Accounts of Income
Other Services xxx
xxx


TOTAL OF INCOME xxx

EXPENDITURE
Accounts of Expenditure
. xxx
. xxx


TOTAL EXPENDITURE xxx
NET PROFIT OR NET LOSS XXX

How we will prepare the above report by using FSG

Define Rows
Line 1 Heading, No account assignment is required for line 1.
Line 2 Income Accounts Go to Account Assignment for line 2

Sign Low High
+ zz.Parent zz.Parent
- If it is a parent it will auto take the Childs
(or We can Include various Income Lines if dont want to specify Parent)

Line 3 Total of Income
Before - = and After - =


Go to Calculation Part
Seq Operand Low High
1 + 2 2
This does the total of Income.

Same way we can define the Expenditure A/Cs as well
Suppose we are utilizing line 4 ,5, 6 for Expenditures
Next step is to find out the Net Profit or Loss
Line 7 Line Item - Net Profits or Loss
Before- = After - =

Calculations

1 + 3 (total Exp) 6 (Total Income)

Define Column Set
Position - 45 (say)
Sequence - 1
Column Name Amount

Attach the Column Set and the Row Set with the Report
Run the Financial report to get the above output .



GL -> Reports -> Define -> Row Set

Define - > Rows

Same way Define the column set for amount.
Run the Report.
4.0 Major Interfaces:



GL interface GL_INTERFACE
GL Daily Rates Interface GL_DAILY_RATES
GL Budget GL_BUDGETS
Interface Details

4.1 J ournal Interface (Overview)




General Steps
- Take sample entries
- Check how the entries are entered manually in APPS's FrontEnd
- Check in front end what mandatory columns have to be entered
Also check what are the columns that APPS's populated .
- Check what data from the sample entries i.e.not entered in the
Front End where for eg. We might have to create or use
Different values.
- During the transaction also check if the user does any manual
Validation or links

GENERAL LEDGER INTERFACE (GL INTERFACE)
Brief Description:
This interface will populate the GL_INTERFACE table. After Populating the GL_INTERFACE Table Journal Import Program
should be Executed, Journal Import Program will populate the Base Tables e.g. GL_JE_LINES,
GL_JE_HEADERS, GL_JE_BATCHES with the appropriate data. You can use the
GL_JOURNAL_IMPORT_PKG and GL_INTERFACE_CONTROL table for Multi Table Import.

Journal Import Program EXE Name is: GLLEZL

- Journal import The Journal Import program requires approximately 1.4 megabytes of memory to run.
- If you want Journal Import to assign sequential numbers to your
Journal entries enable sequential numbering, specifying Automatic as both your numbering and document generation
method.
- Disable dynamic insertion. Journal Import runs much faster when it does not have to create new account combinations
dynamically.
- To give accounts u can use either segments or code combination id.ONLY used either the segment1, segment2... OR use
code combination id for insert data. DO NOT USE BOTH.IN CASE BOTH ARE USED THE segment values are used to
identify the account. Journal Import does not allow null values in enabled segments. The segment data has to be of exact
length has defined in the segments. If an invalid code combination id is entered

CASE 1 Suspense posting is disabled
The invalid code combination ID is printed in Journal Import Execution Report.
CASE 2 Suspense posting is enabled

Prints only the segment value separators in Journal Import
Execution Report.
RECOMMENDED

Disabled suspense posting if entering code combination id.Journal Import data will be removed from the GL_INTERFACE
table after it is successfully imported.

GENERAL LEDGER
SETUP > SYSTEM > CONTROL - to setup the history

List of Mandatory as well as non mandatory columns
1. STATUS - Enter the value NEW for bringing new data in GL
2. SET_OF_BOOKS_ID - You can find a list of valid values in the
SET_OF_BOOKS_ID column of the Sets of Books table
(GL_SETS_OF_BOOKS.SET_OF_BOOKS_ID).
e.g. - SELECT SET_OF_BOOKS_ID, NAME FROM GL_SETS_OF_BOOKS;
3. USER_JE_SOURCE_NAME - journal entry source name list of valid values in >
(GL_JE_SOURCES.USER_JE_SOURCE_NAME).
4. USER_JE_CATEGORY_NAME - journal category name list of valid values in > (GL_JE_CATEGORIES.USER_JE_
CATEGORY_NAME).
5. ACCOUNTING_DATE - GL automatically assigns your journal batch to the accounting period that includes your
accounting date.
6. If average balance processing is enabled, Effective Date Rules to validate the accounting date against your transaction
calendar to determine the transactions effective date.
7. CURRENCY_CODE: list of valid values in
(FND_CURRENCIES. CURRENCY_CODE)
8. DATE_CREATED : for info. Only, not reflected in GL application
9. CREATED_BY: Enter an ID that you can use to identify the data coming from your feeder system.
10. ACTUAL_FLAG: Enter the value A for actual amounts, B for Budget
Amounts or E for encumbrance amounts. The value entered here affects the entry in
1. Encumbrance_type_id
2. Budget_version_id
11. ENCUMBRANCE_TYPE_ID: IF 'E' is entered in actual flag.
List of values in > (GL_ ENCUMBRANCE_TYPES. ENCUMBRANCE_TYPE_ID).
SQL to get it > SELECT ENCUMBRANCE_TYPE_ID, ENCUMBRANCE_TYPE
FROM GL_ENCUMBRANCE_TYPES WHERE ENABLED_FLAG = Y;
12. BUDGET_VERSION_ID: if 'B' is entered in actual flag.
13. PERIOD_NAME: Many a times User Parameter.
14ENTERED_DR:, ENTERED_CR:
15. USER_CURRENCY_CONVERSION_TYPE: put as 'USER'
16. CURRENCY_CONVERSION_RATE: Enter or take it from
17. ACCOUNTED_DR: converted dr amt.

18. ACCOUNTED_CR: converted cr amt.
19. REFERENCE1 (Batch Name): Enter the Batch Name.
20. REFERENCE2 (Batch Description):
21. REFERENCE4 (Journal entry name):
22. REFERENCE5 (Journal entry description):
23. REFERENCE6 (Journal entry reference):
24. REFERENCE24
25. GROUP_ID: Any unique string can serve as group id.
26. ATTRIBUTE1 through ATTRIBUTE 10: for descriptive flex fields

Required NULL Columns in the GL_INTERFACE Table

1. REFERENCE3: Do not enter a value in this column.
2. REFERENCE11 through REFERENCE20: Do not enter a value in this Column.
3. TRANSACTION_DATE: Do not enter a value in this column.
4. JE_BATCH_ID: Do not enter a value in this column.
5. JE_HEADER_ID: Do not enter a value in this column.
6. JE_LINE_NUM: Do not enter a value in this column.
7. CHART_OF_ACCOUNTS_ID: Do not enter a value in this column.
8. FUNCTIONAL_CURRENCY_CODE: Do not enter a value in this column.
9. DATE_CREATED_IN_GL: Do not enter a value in this column.
10. WARNING_CODE: Do not enter a value in this column.
11. STATUS_DESCRIPTION: Do not enter a value in this column.
12. DESC_FLEX_ERROR_MESSAGE: Do not enter a value in this column.
13. REQUEST_ID: Do not enter a value in this column.
14. SUBLEDGER_DOC_SEQUENCE_ID: Do not enter a value in this column.
15. SUBLEDGER_DOC_SEQUENCE_VALUE: Used for communication between
General Ledger and the sub ledgers. Do not populate with your own data.
THE SQL USED TO INPUT THE DATA INTO PRE-INTERFACE TABLE

MULTI TABLE IMPORT
Using alternative tables can help you improve performance since
Journal Import more efficiently processes high volumes of data from multiple tables than from the single GL_INTERFACE
table. Professionals creating data load routines can choose which interface table to put the data in, and whether the table
should be dropped when Journal Import completes successfully.

Prerequisites

1. Data must have both a source and group ID.


To use MultiTable Journal Import

General Ledger provides you with the Journal Import Package (GL_JOURNAL_IMPORT_PKG) to create a new interface
table and Populate the GL_INTERFACE_CONTROL table.


Below are the steps to follow to use MultiTable Journal Import:

1. Create a new interface table. New interface tables must have the same columns as the GL_INTERFACE table but you
can add more
If your needs require.
2. Populate the new interface table with data.
3. Populate the GL_INTERFACE_CONTROL table with one record for each source/group ID combination that was put into
the Interface table. Specify a table name that the data is to be retrieved from for Each Combination. Specify what should be
done with the data once it has been processed.
4. Start Journal Import using the Import Journals window. Specify each of the source/group ID combinations that you want to
Import. If there are multiple tables, Journal Import will be launched multiple times.
5. If Journal Import indicates that the data is erroneous, then correct the data using the Correct Journal Import Data window
or delete it using the Delete Journal Import Data window. If You choose to correct it, and then start Journal Import again
using Import Journals window.
4.2 Daily Rates

II Loading Multicurrency Rates










GL_DAILY_RATES INTERFACE:

This interface can be used to load the data in to GL_DAILY_RATES Table.
Eg. When the client is a organization dealing with share market then needs to keep the track of the Daily
Currency rates.

General Ledger provides the GL_DAILY_RATES_INTERFACE Table that you can use to automatically
insert, update, or delete daily rates in the GL_DAILY_RATES table. General Ledger validates the rows in
the interface table before making changes in the GL_DAILY_RATES table.

One can specify a range of conversion dates; the system inserts, updates, or deletes one row in
GL_DAILY_RATES for each date in your range.

EG. If the Currency conversion rate is specified for 01-oct-97 to 03-oct-97 then three rows will get inserted
In GL_DAILY_RATES Table.


Specify
From To
Currency Currency
JPY USD 01OCT97 Spot .0083
JPY USD 02OCT97 Spot .0083
JPY USD 03OCT97 Spot .0083



As well the Reverse Currency Information also gets inserted automatically

From To
Currency Currency

USD JPY 01OCT97 Spot 120.482
USD JPY 02OCT97 Spot 120.482
USD JPY 03OCT97 Spot 120.482

The insert, update, or deletion of rates in GL_DAILY_RATES is done automatically by database triggers
on the GL_DAILY_RATES_INTERFACE table.

You do not need to run any import programs. You only need to develop an automated process that
populates the interface table with your daily rates information.

The columns in GL_DAILY_RATES_INTERFACE are described below.(columns marked with * are
mandatory)

1. FROM_CURRENCY * Source Currency
2. TO_CURRENCY * Target Currency
3. FROM_CONVERSION_DATE * Starting Conversion Date
4. TO_CONVERSION_DATE * Ending Conversion Date
(The difference should not exceed 366 days)
5. USER_CONVERSION_TYPE * Spot / Corporate /
6. CONVERSION_RATE * Currency Conversion Rate
7. MODE_FLAG * - D To delete the Matching Rows,
I Insert new Rows.
8. INVERSE_CONVERSION_RATE If not specified gets Inserted automatically.
9. USER_ID The following Query Can be used
Select user_id from fnd_user where user.name=<user name>
10. ERROR_CODE
11. LAUNCH_RATE_CHANGE Y - If you want the rate change program to run automatically
12. CONTEXT - The descriptive flex field context.
13. ATTRIBUTE1 14 - Any descriptive flex field information associated with the daily rate.



Important tables and their relationship



5.0 IMPORTANT TABLES:



1. GL_BALANCES
Stores actual, summary and encumbrance balances for detail and summary accounts. This table stores
the functional currency, foreign currency and statistical balances for each accounting period that has ever
been opened. Posting Performs update of GL_BALANCES and delete of GL_BC_PACKETS.

ACTUAL FLAG - "A" / "B" / "E" for actual, budget, encumbrance balances.
PERIOD_NET_DR, PERIOD_NET_CR Period Activity is stored.
Also stores the BEGIN_BALANCE_DR, BEGIN_BALANCE_CR.
Year-to-date balance = begin_balance_dr + begin_balance_cr + period_net_dr - period_net_cr.
2. GL_CODE_COMBINATIONS: stores valid account combinations for each Accounting Flex field structure
within your Oracle General Ledger application. Associated with each account are certain codes and flags,
including whether the account is enabled, whether detail posting or detail budgeting is allowed, and
others.

3. GL_SETS_OF_BOOKS: stores the set_of_books_id, chart_of_accounts_id, Name,
Suspense_allowed_flag, Currency_code etc.

4. GL_JE_HEADERS: GL_JE_HEADERS stores journal entries. There is a onetomany relationship
between journal entry batches and journal entries. Each row in this table includes the associated batch
ID, the journal entry name and description, and other information about the journal entry. This table
corresponds to the Journals window of the Enter Journals form. STATUS is U for unposted, P for
posted journals.

4. GL_JE_LINES - GL_JE_LINES stores the journal entry lines that you enter in the Enter Journals form.
There is a onetomany relationship between journal entries and journal entry lines. Each row in this
table stores the associated journal entry header ID, the line number, the associated code combination ID,
and the debits or credits associated with the journal line. STATUS is U for unposted or P for posted.

5. GL_JE_BATCHES: GL_JE_BATCHES stores journal entry batches. Each row includes the batch name,
description, status, running total debits and credits, and other information. This table corresponds to the
Batch window of the Enter Journals form. STATUS is U for unposted, P for posted, S for selected, I
for in the process of being posted. Other values of status indicate an error condition. STATUS_VERIFIED
is N when you create or modify an unposted journal entry batch. The posting program changes
STATUS_VERIFIED to I when posting is in process and Y after posting is complete.

6. GL_JE_SOURCES : stores journal entry source names and GL_JE_SOURCES _TL Stores the
descriptions.

7. GL_PERIOD_STATUTES: GL_PERIOD_STATUSES stores the statuses of your accounting periods. Each
row includes the accounting period name and status. Other applications maintain their calendars in this
table, so each row also includes the relevant application identifier. CLOSING_STATUS is either O for
open, F for future enterable, C for closed, P for permanently closed, or N for never opened.



Global Intercompany System

GL_JEA_TRANSACTIONS
GL_JEA_TRANSACTION_LINES etc.

Global Consolidation System

GL_CONSOLIDATION
GL_CONS_SEGMENT_MAP
GL_CONS_BATCHES
GL_CONSOLIDATION_ACCOUNTS
GL_CONSOLIDATION_SETS etc.

Budgets

GL_BUDGETS
GL_BUDGET_ENTITIES
GL_BUDGET_PERIOD_RANGES etc.


6.0 IMPORTANT REPORTS Listing:


General Ledger Reports can be mainly categorized as -
1. Account Analysis Reports
2. Budget Reports and Listings
3. Account Structure Reports
4. Trial Balance Reports
5. Multicomapny Accounting and Consolidation Reports
6. Miscellaneous Reports
7. Account Structure Reports
8. Currency Listing Reports
9. Financial Statement Generator Reports












Report Screen Shots

1. Account Analysis Report (132 Char)







Account Hierarchy Report
























Trial Balance (Summary)



















Row Set Summary Listing





FSG Report Revenue Expenditure Listing