GL Technical Deep DiveOracle General Ledger
*
Purpose:
This document provides an overview of features and enhancements included in Release 12.  It is intended solely to help you assess the business benefits of upgrading to Release 12.
Disclaimer:
This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle.  Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Software License and Service Agreement, which has been executed and with which you agree to comply.  This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without prior written consent of Oracle.  This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.   This document is for informational purposes only and is intended solely to assist you in planning for the implementation and upgrade of the product features described.  It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions.  The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.   Due to the nature of the product architecture, it may not be possible to safely include all features described in this document without risking significant destabilization of the code.
Copyright © 2006, Oracle. All rights reserved.
*
Troubleshooting Recommendations
*
Performance Considerations
Setup data flattening programs to speed up queries and data processing
General Ledger Accounting Setup Program
Setup Flattening Program for Table Validated Value Sets
Costs for creating and dropping interim tables are reduced by using global temporary tables.
Improvements allow you to run programs and reports across ledger sets.
You can post to multiple ledgers at one time.
The new program, Posting: Single Ledger, retains the same compatibility rules with Open Period and Translation as in Release 11i.
Two new setup data flattening programs have been introduced to pre-calculate data that can be used to speed up queries and data processing. The General Ledger Accounting Setup Program is automatically submitted based on certain events. It is discussed a few slides later. The Setup Flattening Program for Table Validated Value Sets needs to be manually submitted when changes are made to a table validated value set.
GL has a number of programs where interim tables were used for processing. Almost all these interim tables have been replaced with global temporary tables. So there is no overhead of creating and dropping the interim tables.
Major improvements have been made to allow you to run programs and reports efficiently and easily across ledger sets.
You can post to multiple ledgers at a time.
To take the best advantage of concurrency rules, a new program, Posting: Single Ledger, has been introduced. General Ledger logic will automatically select this program if the posting request will affect balances for a single ledger. This program is compatible with Open Period, Translation, etc running for a separate ledger. Custom logic that submits the original Posting program will not be affected.
Posting and Posting: Single Ledger are compatible with one another and with themselves. They are the exact same program but with different registrations.
Copyright © 2006, Oracle. All rights reserved.
*
Accounting Setup Manager
Definition Access Sets
There are many data model changes and the important ones are mentioned in the Technical TOI document. The next few slides will cover changes describing the flow of data and highlight some items that are not in the Technical TOI or the eTRM.
Copyright © 2006, Oracle. All rights reserved.
*
GL_LE_VALUE_SETS, GL_LEGAL_ENTITIES_BSVS
GL_LEDGER_RELATIONSHIPS, GL_JE_INCLUSION_RULES
Every accounting setup is saved as a configuration. There is a one to one relationship between a primary ledger and a configuration.
The configuration details help drive the Accounting Setup Manager UI by keeping track of various steps and their status. E.g. here we see a checkmark for the Oracle Primary Ledger indicating that ledger options have been completed.
The ledger options, similar to what was your set of books definition in 11i, are stored in GL_LEDGERS. All ledgers and ledger sets are stored in GL_LEDGERS.
Ledger relationships such as primary ledger to reporting currency or primary ledger to secondary ledger are stored in GL_LEDGER_RELATIONSHIPS along with currency conversion and initialization rules.
The source-category conversion rules are stored in GL_JE_INCLUSION_RULES. This table is now used to store rules that can be used by multiple features.
The balancing segment value assignments to legal entities are stored in GL_LE_VALUE_SETS and GL_LEGAL_ENTITIES_BSVS. The balancing segment value assignments to ledgers are stored in GL_LEDGER_NORM_SEG_VALS. Every BSV or balancing segment value assigned to the legal entity is also assigned to the ledger. If no values are assigned to the legal entity, then all values are valid for the legal entity. If you change this setup and assign a single BSV, say 10, then only value 10 is valid for the legal entity. If you decide to move from no assignments / full access to some assignments / partial access, then you have to make sure to assign a full set of values otherwise you will be unable to view/process transactions for the unassigned values.
Copyright © 2006, Oracle. All rights reserved.
*
Accounting Setup Manager
GL_SET_OF_BOOKS
GL_LEDGERS
UPGRADE
GL_SETS_OF_BOOKS
BACKWARD
COMPATIBLE
VIEW
The data in the GL_SETS_OF_BOOKS table has been upgraded to GL_LEDGERS.
The GL_SETS_OF_BOOKS table has been dropped and a backward compatible view also called GL_SETS_OF_BOOKS is available.
Copyright © 2006, Oracle. All rights reserved.
*
Confirm accounting setup
Create / update ledger set
Create new segment value
GL_ACCESS_SET_ASSIGNMENTS
Setup Flattening Program for Table Validated Value Sets
GL_ACCESS_SET_ASSIGNMENTS and GL_ACCESS_SET_LEDGERS store flattened information to improve security checks on data access sets that contain privileges for ledger sets or parent segment values.
GL_LEDGER_SET_ASSIGNMENTS stores flattened information to speed up queries on ledger sets that contain other ledger sets.
GL_LEDGER_SEGMENT_VALUES stores information on balancing segment value assignments to ledgers. If a parent segment value is assigned, it will be expanded and stored as detail segment values.
GL_SEG_VAL_HIERARCHIES stores parent and child segment value mappings based on the segment value hierarchy. This data is used by programs like MassAllocation and FSG.
Each event could result in multiple tables getting updated. E.g. If you add a new ledger to a ledger set, then in addition to the ledger set tables, the data access set tables that store data to access the ledger set would also get updated.
Copyright © 2006, Oracle. All rights reserved.
*
Create / update / delete definition access set
Create / update / delete responsibility assignment
Create / update / delete definition assignment
FND_GRANTS
GL_DEFAS_ASSIGNMENTS
Event
Compile Definition Access Sets
The Compile Definition Access Sets program is submitted to insert, update or delete security assignments every time you create, update or delete definition access sets, responsibility assignments or definition assignments.
Copyright © 2006, Oracle. All rights reserved.
*
Privileges
Definition Access Sets
The definition access sets feature is based on the ATG Grants Security model.
Each setup definition that can be secured is identified by an object type. In this example we are securing an FSG report and the object type is GL_DAS_FSG_REPORT.
Each privilege is represented by a function. Typically the function name is defined as the object type and suffixed with V, M or U to represent the View, Modify and Use privileges.
When you secure a definition, the Compile Definition Access Sets program stores the responsibility, object type, object ID and privileges in the FND_GRANTS table.
You will receive cumulative security access across all your responsibilities.
Copyright © 2006, Oracle. All rights reserved.
*
Problem – Setup data compilation or flattening programs were terminated before completion
Solution - Touch the affected object and force resubmission of the program
If for some reason the flattening or compilation programs are terminated before they run to completion, the setup data will be stuck in processing status and will not be available for queries and processing. The data will get processed the next time the program is run, or you can force resubmission of the program by touching the affected object.
Copyright © 2006, Oracle. All rights reserved.
Wrap Up / Q&A
Oracle General Ledger
*
Program Changes
*
Journals
Balances
Journal Import
There are many data model changes and the important ones are highlighted in the Technical TOI document. The next few slides will cover changes describing the flow of data and highlight some items that are not in the Technical TOI or the eTRM.
Copyright © 2006, Oracle. All rights reserved.
*
(continued)
GL_JE_BATCHES
set_of_books_id
chart_of_accounts_id
period_set_name
accounted_period_type
GL_JE_HEADERS
ledger_id
display_alc_journal_flag
Journals
One batch can now contain journals for multiple ledgers so long as the ledgers share the same chart of accounts, calendar and period type. Hence, the set_of_books_id column has been dropped from the GL_JE_BATCHES table and three new columns have been added.
In the GL_JE_HEADERS table, the set_of_books_id column has been renamed to ledger_id.
Now journals replicated by Posting to a reporting currency are stored in the same batch as the primary journals. During the process of posting, the reporting currency journals are stored with a display_alc_journal_flag value of N indicating that the journals are still in the process of being generated. Once Posting is complete, this flag will be updated to null and the reporting journals will be visible in the posted batch. If posting fails, the journals with display_alc_journal_flag = N will be deleted and the batch will not be posted. When the batch is posted again, the reporting journals will be recreated from scratch.
Copyright © 2006, Oracle. All rights reserved.
*
period_net_dr_beq
94
50
period_net_dr
period_net_cr
period_net_cr_beq
94
USD
GBP
period_net_dr
period_net_cr
period_net_dr_beq
period_net_cr_beq
50
94
100
194
USD
GBP
Balances (GL_BALANCES)
You can choose to track amounts entered directly in the primary currency.
The columns storing functional currency equivalents for foreign currencies are reused to store the entered primary currency amounts in the primary currency rows.
Copyright © 2006, Oracle. All rights reserved.
*
(continued)
GL_INTERFACE
set_of_books_id
ledger_id
The GL_INTERFACE table contains both the set_of_books_id and ledger_id columns. You can populate either of these two columns.
The GL_JOURNAL_IMPORT_PKG and GLLEZL journal import program both have support for backward compatibility.
Copyright © 2006, Oracle. All rights reserved.
*
glpvmc() - Retrieve currency conversion rates for replication to reporting currencies and secondary ledgers and verify write access to reporting currencies
glpvsl() - Calculate target period and use the chart of accounts mappings to determine accounts for replication to secondary ledgers
glpimc() - Create reporting journals
glpcjl() - Insert rounding imbalance lines in both primary and reporting journals
glpisl() - Insert suspense lines in primary and reporting journals
All programs in GL have been changed to support security and access to multiple ledgers. This presentation will focus on changes to Posting. The slides highlight some of the functions performed by Posting.
Copyright © 2006, Oracle. All rights reserved.
*
glpiil() - Call intracompany and intercompany balancing API for primary and reporting journals
glperp() - Print the batch validation output report
glpipi() - Insert balances records in GL_POSTING_INTERIM
glpire() - Insert retained earnings amounts
glpsum() - Calculate summary accounts
glpsqn() - Assign accounting sequences
glpubr() - Update GL_BALANCES and mark batches as posted
SINGLE DATABASE TRANSACTION
Wrap Up / Q&A
Thank You
Thank You