R12 General Ledger White Paper PDF
R12 General Ledger White Paper PDF
R12 General Ledger White Paper PDF
Release12.1.1
White Paper
www.greenchain.biz
To comprehend GL, fundamental concepts of accounting must be understood. These concepts include
accounting equation and transaction principle.
The accounting quotation states that total assets must equal total liabilities plus owner’s equity. An increase in
assets must reflect a corresponding increase in liabilities or owner’s equity. In other words, the balance sheet
accounts must balance. An increase in expenses may also reflect a corresponding increase in liabilities. At
year-end, the Income and expense accounts are closed to retained earnings account in owner’s equity section
of balance sheet.
The transaction principle states that all financial transactions must be recorded and balanced. In other words,
total debits for financial transaction must equal total credits for the financial transaction. Therefore, all, financial
journals in Oracle GL must balance. If not, either the difference will be posted to the suspense account or the
journal must be corrected.
Both these accounting concepts apply in Oracle GL and all Oracle application subsystems, which create the
financial transactions that ultimately create journal entries. A full audit trail from Oracle GL is available.
Oracle GL provides a variety of journal entry capabilities to record financial transactions. Journal entry balance
types include actual journals and budget journals. Actual journals post to either a financial currency or a
statistical currency. Journal source is Payables and the journal category is Payments. In addition, a journal
approval process may be defined and journals may automatically post. A periodic concurrent request may be
run to select and post certain journal sources and categories.
Oracle GL journal capabilities also include recurring journals and allocation journals. Recurring journals speed
data entry by automatically creating the journal. Allocations allow cost pools to be distributed across the
organizations. Allocations may be run in parallel mode, which means all are run at once, or in step-down mode,
which means the allocations are run in a cascading fashion. In other words, the first level allocation journal is
generated before the next level allocation journal.
Oracle GL budget capabilities include online budget entry, a number of mathematical formulas, and ability load
budgets from any other system. In addition, Mass Budgeting allows organization to create budgets or forecasts
based on actual data. For example, preliminary next year budget forecast may be this year’s actual increased
by 10 percent.
Oracle GL provides unsurpassed online inquiry and reporting capabilities. The drill-down from account inquiry to
Oracle application sub-system to T-accounts and journal entry transactions is phenomenal. This drill-down
functionality is available for Oracle application subsystems including Payables, Receivables, Assets, projects,
Inventory and Work In Process (WIP).
Oracle GL provides standard GL reports as with any other Oracle application. In addition, Oracle GL provides a
user report writing tool called the Financial Statement Generator (FSG). FSG allows the user to develop custom
financial reports from the posted account balances.
Oracle GL provides a variety of journal entry capabilities. Journal entries record the financial transactions to
Oracle GL. Journals record the movement between accounts such as depreciation expenses or payroll expense.
All financial transactions must be created as a journal and posted before the GL balances are updated and
available for inquiry and reporting.
The chart of accounts determines accounting flexfield. The accounting flexfield combination must be enabled, be
active within the start and end dates, and have successfully passed the cross-validation rules. The calendar
determines accounting periods open for GL Primary Ledger. Journals may be entered for any open or future
enterable period. Journals may only be posted in an open GL accounting period.
The journal transaction currency defaults to Primary Ledger functional currency. Enter any other currency and
perform foreign currency translation, or select currency of STAT to record statistical journal data.
Journals from Oracle applications should be summarized into Oracle GL. Sending detailed journal transactions
into Oracle GL may impact performance and impede reconciliation capabilities. The Account Analysis reports
provide a complete audit trail from the sub-system to the source transaction whether the transaction was posted
in summary or detail.
Oracle GL provides an audit trail to the feeding subsystem via the use of journal sources and journal categories.
Oracle Applications seed predefined journal sources and categories. Oracle Payables uses journal source of
Payables and journal categories of Purchase Invoices for expense distribution, and payments for disbursement
distributions. Oracle Receivables uses a journal source of Receivables and journal categories of Sales Invoices,
Trade Receipts, Credit Memos, Debit Memos, Miscellaneous Receipts, Adjustments and Chargebacks.
Oracle GL journal methodologies include manual journals, recurring journals, allocation journals, budget journals,
and imported journals (see Exhibit 2.1)
Manual journals are journals entered when no other subsystem exists to create the journals, for example, a
correcting entry.
Recurring journals occur periodically and may have fixed or variable amounts.
Allocation journals distribute allocation cost pools to various accounts based on usage ratios.
Budget journals insert or update budget data.
Imported journals are journals created in a subsystem outside Oracle GL, such as conversion journals, but
also include Oracle Payables and Oracle Receivables journals.
All journal entries in a batch must share the same period. We can create a journal batch for any Open or Future
Enterable accounting period, but we can only post batches in Open accounting periods.
If we do not want to enter batch information, we can enter a journal directly. General Ledger will create a batch
for the entry automatically, using the source (Manual) combined with a unique batch ID and the system date.
Press down arrow to enter next journal line. The next line number will increment from first line number entered.
Journal Enter Journal header name following in-house journal naming conventions
Description Enter journal Description. The journal header description will default to the journal line
description field
Ledger If Multiple Ledgers are accessible, then we need to select one Ledger. Otherwise, Ledger
assigned to the responsibility will be displayed and can not be changed
Category Journal category can be defaulted using the Profile Option: Default Journal Category.
Otherwise user can also select the category from the list
Period Oldest open period will default in Period field. Accept default period or select any open or
future period. The system date will display date in Effective Date field
Effective Date System will populate system date.
Balance Type Balance Type will be displayed as Actual as we are entering Actual Journals using this
window
Journal Type Enter Standard. This will be defaulted
Control Total This is optional.
GreenChain Software Solutions Pvt Ltd Page 3 of 89
Currency Currency will be defaulted to Functional Currency assigned to the primary ledger. In case of
foreign currency journals, this can be changed any other currency enabled
Line Enter journal lines starting with journal Line number
Account Account includes many segments like Department, Company, Product/ Service, Sub-account
etc
Debit/ Credit It is not possible to enter both debit and credit in one single journal line
Oracle defaults Journal category based on profile option. Based on nature of responsibility, this can be defaulted.
Once journals are entered, they can be edited like changing the A/c period, currency, description etc. This is
possible before posting. Journals can also be deleted before posting.
Press T-Accounts to view journals or subledger accounting entries in a graphical T-account format, displayed in
the T Accounts window. (See Exhibit 2.5) The system displays information such as the account, activity detail, net
activity for entry, and account balance.
Post journals /Journal batches to update the account balances of your detail and summary accounts. You can
post actual, budget, or encumbrance journal batches.
One can post journals in three ways
You can post a journal batch by choosing the Post button from the journal window when you are entering or
reviewing a journal entry. Press Post to post journal. Posting journal will start a concurrent process. A request id
window will open. The journal status will change to Selected for Posting. When concurrent job successfully
completes, journal status will change to Posted and GL balances will be updated.
You can select and post journal batches from the Post Journals window.
Automatic Posting: Define criteria for oracle to post journals automatically at regular intervals. Use this
procedure for journals coming from subledgers like Payables, Receivables, and Assets etc.
Once We define an AutoPost criteria set, run AutoPost program to select and post any journal batches that meet
criteria defined by criteria set. We can also schedule AutoPost program to run at specific times and submission
intervals. We can submit AutoPost program or schedule AutoPost runs directly from AutoPost Criteria Sets
window. Alternatively, we can use Submit Request window.
When we enter AutoPost priorities for a criteria set, we can enter All for one or more of selection fields. Use this
feature to select all journal sources or categories; all balance types, or all accounting periods. For example, we
enter journals every period that adjusts our budget balances for subsequent periods. We can define a criteria set
that selects all unposted journal batches with a source of Manual and a balance type of Budget for all periods.
We can then schedule AutoPost program to run at beginning of every period, automatically post our budget
adjustments, and update our budget balances.
If we use budgetary control, we can define criteria set that posts encumbrance journal batches that are created
after funds have been successfully reserved.
(i) To define an AutoPost criteria set:
Navigate to the AutoPost Criteria Set window. Enter a Criteria Set name and Description.
Mark the Enabled check box if you want to enable the criteria set now. Otherwise, leave the check box
unmarked.
Set your Posting Submission Options. If you choose the Submit Only Priorities with Batches in Order option,
be sure to also enter the Number of Priorities.
Enter the range of Journal Effective Dates: AutoPost will only select journals whose effective date is within
the range of days before and after the AutoPost submission date.
Enter your AutoPost priorities for this criteria set. Each priority includes a Priority number, journal Source,
journal Category, Balance Type, and Period.
Use Account Inquiry window (see Exhibit 2.6) to perform online inquiries for any summary or detail account in
your Primary Ledger (see Exhibit 2.7). You can review actual, budget, and encumbrance balances in any
currency, and include variance calculations between balance types. You can also drill down to journal details
affecting your account balances, and review subledger detail if you have Oracle Payables or Oracle Receivables
installed.
We can see PTD, QTD, YTD and PJTD balances from this window and navigate to details.
We can reverse a single journal or an entire batch from Enter Journals window. We can even reverse a journal
entry or batch if we have not assigned it a reversal period.
If we reverse a journal batch, GL creates a reversing journal for each journal in our batch. Note that this also
generates a separate reversal batch for each reversed journal. General Ledger automatically names reversal
batch “Reverses”
A) To reverse a journal entry that does not have a defined reversal period (see Exhibit 2.12)
Choose Reverse Journal. Select the Reversal Period. (See Exhibit 2.12)
Choose OK
GL will display concurrent request ID. The reversal batch will be named Reverses [Original Journal Entry Name]
[Date] [Time]. (See Exhibit 2.13)
First you define journal reversal criteria for journal categories (see Exhibit 2.16) Journal reversal criteria lets you
specify the reversal method, period and date. You can also choose to enable automatic generation and posting of
journals.
When you create a journal entry you want to automatically reverse, specify a journal category that has assigned
reversal criteria. Your journal will be reversed based on the method, period and date criteria you defined for that
journal category.
Once you have posted journals using journal categories associated with journal reversal criteria, you can:
Automatically generate reversals when a new period is opened.
Manually launch a reversal program which finds and generates all journals marked for reversal for a specific
period, including any journals that were manually selected for reversal.
Automatically post any reversal journals including reversals that were not automatically generated.
Prerequisites
General Ledger generates and posts reversals for journals that satisfy the following conditions:
Note: General Ledger automatically submits the AutoReverse program when a new period is first opened in the
Open and Close Periods window. You can also launch AutoReverse at any time through the Submit Request
window. If you want reversals to be generated when a period is opened, set the Profile Option, GL: Launch
AutoReverse after Open Period, to Yes. (See Exhibit 2.17)
To automatically reverse journals (You can submit the Automatic Reversal program for a ledger if you have
read and write access to some or all of the balancing or management segment values assigned to the ledger
and if the ledger has a Journal Reversal Criteria Set assigned.)
Define reversal criteria by journal category in the Journal Reversal Criteria window.
Enter and post Actual journals with journal categories that have reversal criteria defined.
Choose one of the following to reverse your journals:
Run the Open Period program to launch the Automatic Reversal program. (See Exhibit 2.18)
All reversal journals with AutoReverse and AutoPost enabled will be generated and posted according to the
reversal criteria you defined.
To enter a foreign Currency Journal, select currency from list of values, which are enabled in Enter or Enable
Currencies window, conversion type. Whenever we select other than functional currency Oracle will show us the
Entered and Converted currencies (see Exhibit 2.11)
If we use General Ledger's Multiple Reporting Currencies feature, our daily rates are used to convert our primary
Ledger’s journals to the appropriate reporting currencies when the journals are copied to reporting Ledger. Daily
rates must be defined before we post journals in primary Ledger.
Exhibit 2.36 Setup: Currencies: Rates: Daily
In addition, we can enter a range of dates for a single exchange rate in Enter Rates By Date Range window. The
date range can span multiple days or periods.
Exhibit 2.37 Enter Rates by Date Ranges
Journal Import creates journal entries from accounting data we import from Oracle and non-Oracle feeder
systems. We can review, change and post imported journal entries same as any other journal entry. Journal
Import supports multiple charts of accounts, as well as foreign currency, intercompany, statistical, budget, and
encumbrance journals.
Note: Prior to running the journal import process, the journal data file must be loaded into Oracle GL GL-
INTERFACE table.
GreenChain Software Solutions Pvt Ltd Page 11 of 89
Exhibit 2.22 Import Journals Window (Navigation: Journals > Import > Run)
Press Import to initiate the journal import concurrent process. The system opens a decision window to double
check before starting the concurrent process. Press Yes. The system responds with” Your concurrent request id
is n.” Review the Journal Import Execution report. View the journal online. Optionally, run the “Journals-General”
reports which have a report run-time parameter of Unposted journal status.
Navigation: Setup -> financials -> Accounting Set Up Manager -> Accounting Set Up
When you define your ledger, you assign a default suspense account. You can define suspense accounts in
addition to the default suspense account for your Ledger. General Ledger posts a balancing amount to the default
account when there is no suspense account defined with a matching source and category.
To additional suspense accounts, Setup -> Accounts -> Suspense. Oracle defaults suspense account based on
Ledger definition.
Note that if you update the suspense account in the ledger window, the default suspense account is updated in
the Suspense Accounts window. Likewise, if you update the default account in the Suspense Accounts window,
the account in the ledger window is updated.
Enter the Account against which the balancing amount should be posted. You can assign multiple unique
combinations of source and category to a single account.
The process has a result type of GL Journal Approval Process Result that gives one of four results:
• Approval Not Required: The journal batch does not need approval.
• Approved: The journal batch was approved by all necessary approvers. In some cases, this may be the
preparer.
• Validation Failed: The journal batch failed the validation process and was never submitted to the approver.
Mark the Require Journal Approval check box for each journal source that should be subject to approval. When a
journal entry or batch is created using one of these journal sources, journal must be approved before it can be
posted.
Exhibit 2.28 Journal Sources
If our organization uses a shared installation of Oracle Human Resources, use the Enter Person window in GL to
enter all of our employees who are involved in preparing and approving journal entries and batches.
If our organization uses a full installation of Oracle Human Resources, We must log in with a Human Resources
responsibility to enter employees in People window. The Enter Person window will not be available from GL.
When we enter an employee, We also enter employee's supervisor or manager name. The supervisor is default
next approver for journal entries and batches. Likewise, the supervisor's manager is the next approver after the
supervisor.
Journals: Allow Preparer Approval: Determines whether preparers can approve their own journals.
Journals: Find Approver Method: Sets the default method for seeking approval
Exhibit 2.30 System Profile Values (Navigation: other: Profile)
Exhibit 2.30(a) supervisor login (Give Username and Password (Example: CBROWN, WELCOME)
Exhibit 2.31(b) Notification Details Window (Select Notification and say open) then click on approve button.
Determine the inter-company balancing accounts for each journal source and journal category (see Exhibit 2.33).
Exhibit 2.32 Ledger – Journal processing Tab (Setup > financials > Accounting Set Up Manager >
Accounting Set Up)
Enter unbalanced journal (see Exhibit 2.34) and post it. The journal post program created journal lines with line
description Intercompany line added by Posting.(see Exhibit 2.35)
Exhibit 2.40 Journal Categories Window (Setup > Journal > Category)
To define MassAllocation formulas, create a MassAllocation batch that contains one or more MassAllocation
formula entries. We can also copy an existing MassAllocation batch then modify it as needed for your new batch.
Use MassAllocation batches to group your MassAllocation formulas. For example, you might combine all
formulas for a single department or division into one batch, or group all formulas for certain types of calculations
into separate entries. We can create MassAllocations in functional or foreign or statistical currency.
Step 1: Define Parent & Children using Segment Values window and establish the relationship for allocating the
costs (see Exhibit 2.41). For example, Andhra Pradesh can have Hyderabad, Vijayawada and Visakhapatnam as
children in Location or Branch Value Set. Another example is taken in the window displayed.
Step 2: Create Statistical Journal using STAT currency to indicate consumption like Electricity Units for Power,
Gallons for Water, number of people for security services. This journal need not be balanced. Post the journal
after verification (see Exhibit 2.42).
General Ledger uses following format to represent equation. Each factor in this equation relates to a separate
formula line.
A*B/C
We can enter any combination of fixed amounts and accounts in formula lines A, B, or C.
If we do not choose Full Cost Allocation: We can enter an amount instead or an account in any of lines A, B or C.
If we choose Full Cost Allocation: We can enter an account or amount in line A but lines B and C must contain
accounts only.
Select Ledger, A/c Period, balancing segment value and Allocation Method and press submit, Oracle will submit
a concurrent request and creates a Mass Allocation Journal (see Exhibit 2.48)
We can define recurring journal formulas for our functional currency, foreign currencies which have a fixed
relationship with our functional currency, and statistical currency.
Skeleton Journal Entries: Skeleton entries affect the same accounts each period, but have different posting
amounts. After we generate skeleton journal entries, we can edit the unposted journal batch using the Enter
Journals form and enter the journal line amounts.
Skeleton journal entries are useful with statistical information whenever we want to record journals for actual
transactions based on statistical amounts, such as headcount, units sold, inflation rates, or other growth factors.
For example, if we want to enter headcount for each cost center every period, we can define a skeleton entry with
our headcount accounts. After we generate the skeleton entries, enter actual headcount amounts before posting
the batch.
Standard Recurring Journal Entries: Standard recurring journal entries use same accounts and amounts
each period.
Recurring Journal Formula Entries: Formula entries use formulas to calculate journal amounts that vary
from period to period.
Note: if u run any batches in your ledger then this window will appear other wise the next window will appear.
You can define an unlimited number of journal entry lines for each recurring journal entry. The journal entry lines
specify the accounts to update with the recurring journals. Each line also contains the amount to post to the
designated account, or a formula to calculate the journal amounts.
1 Enter a Line number (1 to 9998) to set the order of your recurring journal entry lines. You can indicate an
automatic offsetting line for your recurring journal entry by entering the line number 9999.
2 Enter the Account you want General Ledger to update when you generate and post your recurring journals.
3 Enter an optional Line Description for the recurring entry line.
4 Enter a Formula for the line.
5 Enter the remaining lines for the recurring journal entry. Remember that you can use line number 9999 as
the automatic offsetting line for each recurring journal entry.
When opened, both types of flexfield appear as a pop–up window that contains a separate field and prompt for
each segment. Each segment has a name and a set of valid values, value descriptions.
Key Flexfields
Chart of Accounts is the most important KFF in Oracle. KFF contains Structures. Each structure contains One
or More Segments (Fields). Each segment represents a characteristic of entity. KFF are flexible to let any
organization use code scheme without programming. The sequence of creating Chart of Accounts is explained
below:
While designing COA, we need to decide on number of segments, order of appearance and validation of each
segment. This affects the design of value sets and values.
Define value sets first, either before or while defining structures. Define individual values only after flexfield has
been completely defined (and frozen and compiled). Depending on what type of value set you use, you may not
need to predefine individual values at all before you can use your flexfield.
We can share value sets among segments in different flexfields, segments in different structures of the same
flexfield, and even segments within the same flexfield structure. We can share value sets across key and
descriptive flexfields. We can also use value sets for report parameters for reports that use Standard Request
Submission feature.
Exhibit 3.3 Value Sets Window (Navigation: Setup: Financials: Flexfields: Validation: Sets)
Use Poplist for less than 10 values expected; List of Values between 10 and 200 values;
Long List of Values for more than 200 values.
Security Security does not apply to value sets of validation type None, Special, or Pair. Flexfield value
Type security is not available for Translatable Independent and Translatable dependent value
sets.
No Security - All security is disabled for this value set.
Hierarchical Security: Features of value security and value hierarchies are combined. Any
security rule that applies to a parent value applies to its child values.
Non-Hierarchical Security - Parent value does not "cascade down" to its child values.
Format Type Valid format choices include: Char, Date, Date Time, Number, Standard Date, Standard
DateTime, and Time. Translatable Independent and Translatable Dependent value sets must
have the Char format. Enter formatting information appropriate to format type, including
information such as whether values should include numbers only and whether they must fall
within a certain range.
Validation Select Validation Type as independent for COA. Accounting Flexfield supports
Type Independent, Dependent validation. If we are creating a Dependent, choose Edit
Information button to open appropriate window. Enter any further information required for
validation type.
Step 2: Define the structure for COA. The structure will have Code, Title and Description.
In each segment window, enable security check box to use security rules. Otherwise any defined security rules
are disabled. If value set for this segment does not allow security rules, then this field is display only. Enter the
display size and prompt information for the segment.
Descriptive Flexfields
Descriptive flexfields provide customizable “expansion space” on forms. Use descriptive flexfields to track
additional information, important and unique to business that would not otherwise be captured by forms. These
can be context sensitive, and information stored depends on other values users enter in other parts of form.
A DFF appears on a form as a single–character, unnamed field enclosed in brackets (see Exhibit 3.6). Just like
in a key flexfield, a pop–up window appears when you move your cursor into DFF. Pop–up window has as
many fields as your organization needs.
Freeze flexfield after set up and save changes. Then this window automatically compiles flexfield.
We must freeze and compile flexfield definition before use. For any changes, make sure to freeze
and save flexfield definition again after changes.
Prompt The context field automatically displays any existing context window prompt for this flexfield.
Change this prompt by typing a new prompt over current prompt. Flexfield displays this prompt in
a flexfield window in context-sensitive flexfield structure to see when you enter the flexfield (that
is, if you have permitted Override). When you choose a prompt, keep in mind that context field in
flexfield window appears as just a normal field or segment to user.
Value Set If you have context field values contained in an existing table, create value set that includes those
values, and enter name of that value set here. Using a value set for context field allows you to
have valid context field values without specifically defining context-sensitive segments for those
context field values
Default Enter a default context field value for flexfield to use to determine which descriptive flexfield
Value structure to display. Define default context field value as a structure in Context Field Values zone
before compilation. DFF automatically uses this default context field value if you do not define a
reference field.
If you do not have any context-sensitive segments, or you want the context field to remain blank
unless filled in by a reference field, you should leave this field blank
Required Indicate whether a context field value is required. If a context field value is required, your flexfield
does not allow you to leave the flexfield window without entering a valid value. Otherwise, you do
not have to choose a value for your context field. In this case, you leave the flexfield window
without seeing any context-dependent structures.
Reference Enter the name of the reference field from which your flexfield can automatically derive the context
Field field value. You can select from a list of potential reference fields that have been predefined.
Some descriptive flexfields may not have any reference fields predefined
Displayed If you have any context-sensitive segments for your flexfield, you should always check the
Displayed check box if you do not specify either a default value or a reference field. Without the
displayed context field, your flexfield must determine the context field value from the reference
field or your default value.
If you check the Displayed check box, a user can see and change the context field value that your
flexfield derives from a reference field or obtains as a default value.
A/c calendar defines organization’s financial reporting periods (see Exhibit 3.9).
Once definition is completed, then close the window. System will prompt to validate calendar. (See Exhibit 3.10).
If Current is selected, only current calendar will be selected for validation. A concurrent process will run. View
Requests to review the concurrent process.
After completion of concurrent request, verify the output for any errors. (See Exhibit 3.11).
2.4 Currencies
All ISO currencies are defined in Oracle. We just need to enable the currency using the checkbox. By default
USD and STAT are enabled.
Legal entity, Location, Currency, Calendar, Chart of accounts are required. There Are Two Steps for Ledger
Creation and three pages legal entities page, accounting setups pages, accounting options pages.
2. Legal Entities
Legal entity allows adding, updating, and removing legal entities. Assign unique balancing segment values to
legal entities; Remove balancing segment values and end-date balancing segment values
Exhibit 3.13 ledger creation window (Navigation: Setup-> financials -> Accounting Set Up Manager ->
Accounting Set Up
Navigate to Legal Entities page. Click Create Legal Entity. Enter all relevant fields for the Identification
Information, Legal Address, Additional Information and Balancing Segment Value Assignments.
Click Apply or click Save and Add Details to enter additional information for the legal entity that includes the
following: Registrations and Establishments
Note: Adding this additional information is not required for creating an accounting setup and You can quickly
create legal entities when creating an accounting setup
In the Balancing Segment Value Assignments region, click Add Value Set. Select a value set from the list of
values. Only value sets that use the balancing segment value qualifier are displayed.
To assign balancing segment values for the value set, click Add Balancing Segment Value. Select one or
more balancing segment values to assign to this legal entity. You cannot assign parent values.
Note: Be sure to assign unique balancing segment values to each legal entity. You cannot complete the
accounting setup if multiple legal entities assigned to the same accounting setup have overlapping balancing
segment values assigned or only some of the legal entities have balancing segment values assigned.
Note: Once you add a legal entity to an accounting setup and complete the accounting setup, you cannot
remove balancing segment values from legal entities. You can only disable balancing segment values by
entering an end date
After navigating in to this window click on create accounting setup button. (Next window will appear)
Enter territory, legal entity name; organization name, legal entity identifier, pan, transaction entity then say apply.
Say finish.
Click on return to accounting setups button (it will return to 3.13 windows with ledger creation information)
Exhibit 3.13(h) accounting setup window with automatic ledger short name creation
Note: The Track by Secondary Segment option cannot be changed once the Accounting Setup status is
complete. The First Ever Opened Period cannot be changed once the first period is opened for the ledger.
Oracle GL profile values must be set. For example, GL ledger profile value must be set for the new GL
responsibility (see Exhibit 3.14)
GL ledger name Profile option. Select GL Ledger name under GL responsibility. The GL Ledger ID will be
displayed after saving.
Open first period for GL Ledger (see Exhibit 3.16). Typically one period prior to first period of transaction activity
is opened. This allows balance sheet accounts to be loaded and rolled forward to first period in calendar year to
properly initialize balance sheet beginning balances. Choose this period carefully. Once period is open, it can’t be
reset or reopened.
Press Open. The system opens decision window (see Exhibit 3.17) to double check before opening first GL
period. Press Yes to open first period.
The system displays first period with a status of Open and all Future periods as defined in GL Ledger (see Exhibit
3.18). The accounting period must have a status of Open or Future for financial transactions to be entered.
Press Open Next Period to open subsequent periods. The system opens a decision window and double checks
before starting the concurrent process to open the GL period. Press Yes. The system submits a concurrent
process to properly populate the GL Balances with newly opened period’s beginning balance and period data.
Shorthand flexfield entry helps you satisfy the following data entry needs:
Enter key flexfield data quickly by associating shorthand aliases with frequently-used sets of valid key
flexfield segment values.
Define a shorthand flexfield entry pop-up window (the shorthand window) for any key flexfield. You specify a
name and size for each shorthand window.
You define complete or partial set of key flexfield segment values (the template) that each shorthand alias
represents. These values can be valid flexfield combinations or different patterns of valid segment values.
For each key flexfield structure, you can define as many shorthand aliases as you need. If you make changes to
your shorthand aliases, your changes take effect immediately for both you and other users.
If Shorthand Flexfield Entry is enabled and the Flexfields: Shorthand Entry profile option is set to an appropriate
value, the shorthand window allows you to enter an alias before the flexfield window opens. The combination or
partial combination you defined for your alias is entered into your flexfield window.
In Oracle Applications, only Accounting Flexfield uses Rollup Groups. Rollup groups are used to create
summary accounts for reporting purposes.
1. Enter a code for your rollup group. The code is required and used internally.
2. Enter a name and description for your rollup group. Save your changes.
3. Apply rollup group name to particular values using Segment Values window. (See Exhibit 3.22)
Enter summary account templates to create summary accounts. GL uses templates in combination with parent
segment value definitions to create summary accounts. To enter a summary account template:
D: Summary account for every detail segment value. This value creates the most summary accounts of any
template value.
T: summary account to sum balances of all detail segment values. This value creates the fewest summary
accounts of any template value.
If you enter T for a segment, all summary accounts created by template will have value T for segment.
Therefore, value T must be defined and enabled for segment. Also, segment value must be a parent and detail
posting and budgeting are not allowed.
[Rollup Group Name]: Your template creates and maintains a summary account for each parent segment
value assigned to rollup group you specify. The more parent segment values in a given rollup group, the more
summary accounts your template creates.
Exhibit 3.24 Account Inquiry using Summary Template
Use cross-validation rules to prevent creation of combinations that should never exist (combinations with values
that should not coexist in same combination).
How Cross-Validation Works?
When a user finishes entering segment values in a flexfield pop-up window, flexfield checks whether values
make up a valid combination before updating database. If user entered an invalid combination, a diagnostic
error message appears, and cursor returns to first segment assumed to contain an invalid value.
Cross-validation rules control combinations of values within a particular key flexfield structure. Cross-validation
applies to combinations users attempt to create using either combinations form or foreign key forms (using
dynamic inserts).
Cross-validation rules have no effect on combinations that already exist when you define your cross-validation
rules.
Suppose we define a new cross-validation rule, but have existing entries in your combinations table that violate
the rule. Since existing combinations pre-date rule, flexfield continues to treat them as valid. However, if we try
to create a new combination that violates new rule, flexfield returns an error message and rejects combination.
To prevent users from using previously-existing combinations that are no longer valid according to your cross-
validation rules, always manually disable those combinations using combinations form.
Your use of cross-validation is separate from (and in addition to) your use of dynamic inserts.
For greater control, disallow dynamic inserts. Thus restrict creation of new combinations to certain authorized
people who have access to combinations form. Turn dynamic insertion off using Define Key Flexfield Segments
form. Depending on KFF used, create new combinations using one of your product setup forms (combinations
form). For example, enter new combinations using Define Accounting Flexfield Combination form.
In either case, however, there is no inherent protection against a user creating an invalid new combination.
Cross-validation rules ensure that nobody can create invalid new combinations from either foreign key forms or
combinations form, regardless of whether you allow dynamic inserts.
Tip: Determine whether we need cross-validation rules at all. To provide an extra level of security, use cross-
validation rules even if you turn dynamic insertion off. This allows you to double-check new combinations that
even your authorized personnel enter using the combinations form.
Changing an existing key flexfield structure may adversely affect behavior of any cross-validation rules you
have for that structure, so you should be sure to manually disable or redefine any cross-validation rules to
reflect your changed structure. Flexfield structure changes that make your existing rules invalid include:
changing the order of segments, adding a new segment, disabling a segment, changing segment lengths
For example, if you change a six-segment structure to contain only five segments, you would not be able to use
any new five-segment code combinations since any rules existing for the old six-segment structure would be
violated.
Exhibit 3.25 Enable Cross-Validation
Navigation: Set Up-Financials-Flexfields-Key-Segments
Security lets you determine who can use flexfield segment values and report parameter values. Based on
responsibility and access rules that defined, Security limits what values we can enter in flexfield pop-up
windows and report parameters. Flexfield Value Security gives greater control over who can use restricted data
in your application. When you use Flexfield Value Security, users see only values they are allowed to use;
restricted values do not appear in lists of values associated with the flexfield or report parameter.
You can define security rules for each segment or report parameter for which you want to restrict data entry.
Within a rule, you specify ranges of segment values to include and exclude from use. You can create many
rules for same segment or parameter, and assign rules to different responsibilities. Define error message you
see if you try to enter a value for which you do not have access. If you define no security rules for a segment,
you can enter any value you have defined into that segment.
Choose Non-Hierarchical Security if you do not want security on a parent value to "cascade down" to its child
values. Choose Hierarchical Security if you do want the hierarchical security feature enabled.
Exhibit 3.28 Segments window – Security Enabled
Hierarchical Security Hierarchical security is enabled. With hierarchical security, the features of value
security and value hierarchies are combined. With this feature any security rule that
applies to a parent value also applies to its child values.
Non-Hierarchical Security is enabled, but the rules of hierarchical security do not apply. That is, a
Security security rule that applies to a parent value does not "cascade down" to its child
values.
1. In the Segment Values block, identify value set to which your values belong. You can identify your value set
or by the flexfield segment or concurrent program parameter that uses the value set.
2. In the Security Rule region, enter a name and description for your security rule.
3. Enter a message for this security rule. This message appears automatically whenever a user enters a
segment value that violates your security rule.
4. You define a security rule element by specifying a value range that includes both a low and high value for
your segment. A security rule element applies to all segment values included in the value range you specify.
You identify each security rule element as either Include or Exclude, where Include includes all values in the
specified range, and Exclude excludes all values in the specified range. Every rule must have at least one
Include rule element, since a rule automatically excludes all values unless you specifically include them.
Exclude rule elements override Include rule elements.
You should always include any default values you use in your segments or dependent value sets. If the default
value is secured, the flexfield window erases it from the segment as the window opens, and the user must enter
a value manually. If you want to specify a single value to include or exclude, enter the same value in both the
Low and High fields.
In Assign Security Rules block, identify value set to which your values belong. Identify value set or by
flexfield segment or concurrent program parameter that uses the value set.
In Security Rules block, enter application and responsibility name that identifies responsibility to assign
security rules.
In above picture, values from 000 to 109 and 131 to ZZZ are not visible.
Even if you know the value also system will give an error which you entered in the security rules window.
Oracle GL provides a variety of budget data entry methodologies including online entry and batch load. Online
entry capabilities include direct data entry and budget rules or simple budget formulas. In addition, budget
amounts may be calculated via mathematical formulas utilizing statistical data. Budgets may be transferred
online as well. Users may easily move budgets from one accounting flexfield range to another accounting
flexfield range.
Oracle GL budget batch load capabilities include importing budgets via ADI or from another budget subsystem.
Oracle GL provides an open budget interface. The chapter on budgeting in the Oracle GL User Guide details
the open budget interface process.
Budgets and budget variances may be viewed online in Oracle GL or displayed in FSG reports. Budget versus
actual comparisons may be viewed online in the GL account inquiry window. Simply enter the budget name and
navigate through the windows to view the budget data and actual-to-budget variances. In addition, if the budget
balances were created from budget journals, drill-down to the journal detail is available.
Exhibit 4.1 Setup-financials-Accounting Set Up Manager-Accounting Set Up
In Budgetary Control Tab page Enable Budgetary Control
You can create budget hierarchies by assigning lower-level budgets to a master budget. This enables you to
track budgeted amounts against your control budget.
Exhibit 4.2 Define Budget (Navigation: Budget -> Define -> Budget)
To define a new budget organization that includes only specific ranges of accounts, enter a unique name. If you
have one or more budget organizations defined already, you can create a budget organization named "ALL"
that automatically includes all accounts that are assigned to any budget organization. To do this, enter "ALL" as
the budget organization Name.
3. Enter the sort and display options.
The Ordering Segment is the account segment General Ledger uses to sort accounts when you review the
budget organization assignments, and when you use the Enter Budget Amounts and Enter Budget Journals
windows.
Specify the Display Sequence for your account segments. You can use this sequence to change the order of
your account segments on the Enter Budget Amounts and Enter Budget Journals windows. For each segment,
enter a unique sequence number from 1 to n, where n is the number of segments in your account.
5. Assign accounts to the budget organization. To assign ranges of accounts to the budget organization.
1 Enter a Line number and an account Low and High for each range to assign to budget organization. Ranges
cannot overlap other account ranges with same currency for any budget organization in Ledger.
Calculated: You use budget formulas or Mass Budget journals to enter budget amounts. You cannot use this
entry type if you are using budgetary control.
3 Enter Currency for each account range. For accounts with a budget entry type of Calculated, you must enter
either the functional currency for your Primary Ledger, or STAT. To enter only statistical budget amounts for
account range, enter STAT.
4Review, add, or temporarily delete individual accounts assigned to your budget organization by choosing
Range Assignments (see Exhibit 4.5)
Document sequences can provide proof of completeness. For example, document sequences can be used to
account for every transaction, even transactions that fail.
Document sequences can also provide an audit trail. For example, a document sequence can provide an audit
trail from the general ledger into the subsidiary ledger, and to the document that originally affected the account
balance.
Document sequences generate audit data, so even if documents are deleted, their audit records remain.
4.1 Define
Exhibit 5.1 Define Document Sequences (Setup : Financials : Sequences : Define)
2. Application. Once selected, the application associated with your sequence cannot be changed.
3. Effective From/To: Enter dates document sequence takes effect/is no longer enabled.
4. Type: Once defined, you cannot change the type of document numbering sequence. (Select automatic)
4.2 Assign
1. Navigate to Setup: financials: sequential: assign.
2. Enter application (eg: general ledger).
3. Enter category (eg: expenditure, adjustments).
4. Enter your ledger name for which you are giving sequential numbering.
5. Select type as manual and go to assignment tab enter start date, name of the sequence.
Navigate to journal: enter. Give line information and save the information the document number will come
automatically.
Other information
Navigate to inquiry: accounts. Give the entered currency, date, and account information then say show balances.
Choose Revalue. Your revaluation is automatically saved and the Submit Request window appears or Navigate
to view: request: submit new request. Give request name as “Program-revalue balances”. Say ok and submit
Exhibit 6.7 Detail Balance in Revaluation Gain/Loss Account (for credit account)
Run translation after you have completed all journal activity for an accounting period. If you post additional
journal entries or change your translation rates after running translation for a period, you must retranslate.
Additionally, if you change the account type for an account segment value and want to retranslate your actual
account balances, you may need to purge past translations, change the account type assignment, and then run
translation
1) Provide Rate Type and CTA A/c in Primary Ledger
2) Enter Daily and Historical Rates
3) Rune Translation
4) View Trial Balance (Translation Report)
Step 1:
When you translate your actual balances into another currency, General Ledger automatically adjusts the
balance of the Cumulative Translation Adjustment account to the net difference needed to balance your
translated chart of accounts. If you have multiple companies or balancing entities within a ledger, General Ledger
automatically adjusts the balance of the translation adjustment accounts of each company or balancing entity. If
secondary tracking segment is enabled for closing translation, the Cumulative Translation Adjustment will be
calculated by unique pairs of balancing segments and secondary tracking segment values. General Ledger does
not make adjustments to this account when you translate budget balances.
Step 2:
Navigate to setup: Currencies: Rates: Define. Select Period, Account and enter Rate. Save record.
Step 3:
Run translation to convert a/c balances into Target Currency. Select Ledger, Target Currency and Period. Press
Translate button. Oracle will submit concurrent program.
Step 4:
Once program is completed, GL_BALANCES table is updated with a/c balances in Target Currency. Balances
can be viewed online or through report. Standard report is also available. CTA a/c will carry entries depending
upon exchange rates.
To consolidate multiple sets of books that have different functional currencies, accounting calendars, or charts
of accounts, you must first map your subsidiaries' charts of accounts to your parent's chart of accounts.
A consolidation mapping is a set of instructions for mapping accounts or entire account segments from a
subsidiary Primary Ledger to the parent Primary Ledger. When you subsequently transfer amounts from a
subsidiary to your parent, General Ledger creates an unposted consolidation journal batch in your parent
Primary Ledger based on the subsidiary's mapping information.
Additional Information: You define one consolidation mapping for each subsidiary. If you want to change how
a subsidiary consolidates to your parent, change the subsidiary's consolidation mapping before you transfer the
data. You can group multiple consolidation mappings into a consolidation mapping set. You can then transfer
the mapping set to your parent rather than transferring each subsidiary's data separately.
Balances: Consolidate actual, average, translated, budget, or statistical balances. This method does not
include journal entry detail. If you have average balance processing enabled, your parent should be defined as
a consolidation Primary Ledger with average balances enabled. Note that you are consolidating average
balances.
Transactions: Consolidate actual journal entry detail from a subsidiary Primary Ledger. Use this method only if
both books have same functional currency. You cannot use this method for budgets. If you have average
balance processing enabled, your parent should be defined as a non-consolidation Primary Ledger with
average balances enabled. Note that you are averaging balances once you consolidate detail from your
subsidiaries sets of books.
4. Enter a Description for the mapping. (Optional)
5. Enter name of Subsidiary Primary Ledger and Parent Primary Ledger name.
7. Enter Currency to use for consolidation:
If you are consolidating balances, enter the parent set of book's functional currency. Optionally, enter STAT
to consolidate statistical balances.
If you are consolidating transactions, enter the parent set of book's functional currency. This must be the
same as the subsidiary set of book's functional currency.
8. Enter a range of Effective Dates for which the consolidation mapping can be used. If you use the mapping to
transfer consolidation data for periods that fall outside the effective date range, the transfer will fail.
9. If you have average balance processing enabled, select a default Usage type from the poplist.
Standard: Only standard balances are transferred to the parent Primary Ledger.
Average: Only average balances are transferred to the parent Primary Ledger.
Standard & Average: Both standard and average balances are transferred to the parent Primary Ledger.
10. Select your consolidation run options. You can change these when you transfer your subsidiary data.
Run Journal Import: Checking this option launches Journal Import after your subsidiary data has been
transferred. This creates an unposted consolidation batch in your parent Primary Ledger automatically.
If you choose not to run Journal Import, the transfer process populates the GL_INTERFACE table so that you
can run Journal Import later.
Audit Mode: Check this option to keep a record of how accounts from your subsidiary Primary Ledger map to
accounts in your parent Primary Ledger. You can then run the Consolidation Audit Report, the Disabled Parent
Accounts Report, and the Unmapped Subsidiary Accounts Report to see consolidation audit information.
GreenChain Software Solutions Pvt Ltd Page 72 of 89
After your subsidiary data has been transferred and you have requested the audit reports, purge your
consolidation audit data using the Purge Consolidation Audit Data window.
Create Summary Journals: Check this option to summarize all journal lines that affect the same account code
combination into one line in the parent Primary Ledger. Since this is a summary action, General Ledger creates
one journal entry line showing debits and credits for each account code combination.
AutoPost: Check this option to automatically post your consolidation journals in the parent Primary Ledger
Segment rules: map subsidiary account segments to parent account segments. For example, you can map
your subsidiary's Department segment to your parent's Cost Center segment.
Use Rollup Rules From: Map values from your subsidiary segments to your parent segments using the rule
specified in the Rollup Rules region.
5. If you chose the Use Rollup Rules From action in the previous step, enter the mapping rules in the Rollup
Rules region.
Additional Information: Once you save your work, you cannot modify your rollup rules, except to change the
parent and subsidiary segment detail values. To change a rollup rule, delete it then create a new one.
Account rules: map a specific subsidiary account or a range of accounts to a specific account in your parent
Primary Ledger. For example, you can map subsidiary account 02.300.5400.100 to account
01.100.3000.000.000 in your parent Primary Ledger. Or, you might map the entire range of subsidiary accounts
02.300.5400.100 through 02.300.6999.100 to account 01.100.3000.000.000 in your parent Primary Ledger
Create a mapping set to transfer consolidation data for multiple subsidiaries simultaneously.
1. Enter a Mapping Set name, Parent Primary Ledger name, and Description of the mapping set.
2. Choose a consolidation Method and Select Run Options.
4. Enter Mapping name for each subsidiary-to-parent mapping you want to include in set. The mappings must
use same consolidation method you selected above.
6. (Optional) you have finished entering mappings, choose Transfer Set button to open Transfer Consolidation
Data Set window. From this window, enter transfer set parameters then start process of transferring data from
subsidiaries in mapping set to parent Primary Ledger. If you don't want to transfer data now, go to the next step.
Press Transfer and system will create a unposted journal in parent Primary Ledger (see Exhibit)
Row Sets
A Row Set defines the format and content of the rows in an FSG report. In FSG, the commonly assumed attribute
for a row definition is an account assignment, whereas the attribute for a column definition is a time period (amount
type). When you define a row set, you can:
• Assign accounts -- to indicate which general ledger account balances you want to include in the row. You can
assign an individual account or range of accounts to each row.
• Define calculations -- to perform a variety of complex computations in your report. The calculations can refer to
any previous rows in a report, including rows you choose not to display.
• Specify formatting -- to control page breaks, indentation, line spacing, and underline characters.
Navigation > Reports > Define > Row Set
1. Enter a Line number for each row of the row set. The line number controls the order in which rows appear in a
report. You also use the line number when creating a row calculation.
2. Enter a Line Item description for each row. This appears as the row label on any report you run using this row
set.
3. (Optional) Enter the Format Options, Advanced Options, and Display Options for each row.
4. To have the row generate account balances on your report, choose Account Assignments to assign accounts to
the row. To create a calculation row (for report totals and subtotals), choose Calculations.
A row definition can have account assignments or calculations, but not both.
By assigning a content set to a report request, you can generate hundreds of similar reports in a single run. The
content set controls how the numerous reports differ from each other. For example, assume your organization has
50 departments and that Department is one of your account segments. Also assume that you already have an
FSG report for travel expenses, which you run weekly. By using a content set with your existing report definition,
you can print a travel expense report for each department, in one report request. You can then distribute the
reports to the 50 department managers for review purposes.
Content sets are similar to row sets and actually work their magic by overriding the row set definition of an existing
report. The subtle report variations discussed in the previous paragraph are achieved by the content set altering
the row set account assignments and/or display options.
Navigate Reports > Define > Content Set
When you define the content set, assign the Display type PE to the segment for which you want separate reports
for each segment value. Optionally, you can assign multiple account ranges to the content set.
Use row order to control how detail rows appear in report. You can
• Display account descriptions in addition to or instead of segment values.
• Sort detail rows by amounts displayed in a column.
• Sort detail rows by account segment values or segment value descriptions.
• Rearrange the sequence of your account segments to fit specific reporting needs. For example, you may want
to see product segment values displayed before cost center values.
• Suppress header descriptions for particular account segments.
Define row orders to modify the order of detail rows in a report. Rank rows in ascending or descending order
based on the amount in a particular column and/or by sorting segments by description or value.
To sort detail rows by an account segment's values or descriptions, the segment's display type in the related row
definition must be either Expand or Both. Optionally, you can use a content set whose display type is set to
Row/Expand or Row/Both.
A display group defines a range of rows in a row set or columns in a column set. Display groups are assigned to
display sets to control which rows and columns appear on a report.
• Enter the Name and Description of the display group.
• Enter the name of a Row Set or Column Set. To create a generic display group, leave these fields blank.
• Enter from and To Sequence numbers in your row or column display range.
• For example, if you specify a row set and choose 10 through 40 as your sequence range, your display group
will affect rows 10 through 40.
Define display sets to control the display of ranges of rows and/or columns in a report. To use display sets you
must also define display groups to identify the ranges of rows and/or columns whose display you want to control.
Exhibit 10.10 Define Report (Navigate Reports > Define > Report)
Enter Report Name, Title and Description. The report title is what FSG will print at the top of the report.
Select Row Set and Column Set. Select Content Set, Row Order, and/or Display Set, which are optional.
Enter Segment Override values for the account segments you want to override. When you enter a segment
override value, FSG produces a report for the specific value you specify. For example, assume you have a report
definition which produces a combined assets report for four companies. If you modify the report definition to add a
segment override for company 02, then FSG will print an assets report for company 02 only.
Enter a default Currency for the report. FSG uses this currency only for those rows and columns to which you did
not assign a currency when you defined row and column sets.
Select a Rounding Option to use for calculations in the report:
Calculate Then Round: FSG performs calculations before any rounding.
Round Then Calculate: FSG rounds values before they are used in calculations.
Select a Level of Detail for the report. There are three options, which correspond to the levels of detail you can
assign to rows and columns. If you specify a level of detail for your report, FSG will only print those rows and
columns with matching levels of detail.
Note: If you do not enter a level of detail for a report, the system will assume the level of detail is Financial Analyst.