GL Changes _R12 vs 11i

09/05/2013 Document Display

https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=rdfe8f2os_510 1/19

R12 Upgrade: Changes to Expect in R12 as Against Release 11i [ID 1443965.1]

Modified: 04-Oct-2012 Type: WHITE PAPER Status: PUBLISHED Priority: 1

In this Document

Abstract

History

Details

A) THE NEW FUNCTIONALITIES INTRODUCED

1. Ledgers:

2. Data Access Set:

3. Accounting Setup Manager : Centralised Setup

4. Definition Access Sets

5. Multi-Ledger Processing

6. Alternate Accounts

7. Sequencing

8. Line Level Reconciliation

9. Third Party Control Accounts

B) RELEASE 12 Vs RELEASE 11i : A GL UPGRADE PERSPECTIVE

1. Basic SetUp : Transformation Into R12

2. Journal Entry

3. Posting

4. AutoPost

5. Journal Reversal

6. Autoreversal

7. Journal Import

8. Recurring Journals

9. Suspense Accounts

10. Translation Process

11. Financial Statement Generator Reports

12. Budgetary Control in R12

C) SOME COMMON QUERIES ADDRESSED

APPENDIX: CHANGE IN STRUCTURE OF TABLES RELATING TO GL MODULE

Still Have Questions?

References

Applies to:

Oracle General Ledger - Version 12.0.1 to 12.2 [Release 12.0 to 12.2]Information in this document applies to any platform.

Abstract

R12 Upgrade: Changes to Expect in R12 as Against functionalities in Release 11i

History

Author: Anshu Anand Create Date 29-03-2012

Details

A) THE NEW FUNCTIONALITIES INTRODUCED

Release 12 brought in plethora of new functionalities along with it. We had the SLA concept being introduced and the experts said “Set of Books” was gone. In thefollowing lines, we have tried to highlight these functionalities

https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=rdfe8f2os_510#WP_ABSTRACT

https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=rdfe8f2os_510#WP_DOCHIST

https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=rdfe8f2os_510#WP_BODY

https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=rdfe8f2os_510#aref_section31



























https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=rdfe8f2os_510#REF



1. Ledgers:

Ledger is the new name for traditional “Set Of Books” that existed in 11i. If you recollect, the Set of Books comprised of three essential components : 3Cs. These were – Chart of Accounts, Calendar and Currency. Ledgers, however, are made up of four such C components normally termed as Four Cs -– Chart of Accounts, Calendar and Currency and Subledger Accounting Method (SLAM). SLAM is a rule based accounting engine, that helps a user havethe representation of the accounting entries in a manner required by his company and/or the local law. The user may choose to record only the Cashentries or the Accruals as well by choosing an available value from the list of Standard SLAMs provided. Users can also create their own Subledgeraccounting methods.

In Release 11i, one responsibility could be assigned to one Set of Book Only. Release 12 brought in an addition here. Now, one can assign multipleledgers to a single responsibility in R12 using the Ledger Sets and Data Access Sets. Ofcourse, one mandation is that only those ledgers can be groupedthat share same Chart of Accounts and Calendar.

2. Data Access Set:

As we discussed earlier, Release 12 allows one to assign multiple ledgers to a responsibility. Alongside, one would also be able to choose the level ofprivileges that one could provide for each of these ledgers. For example, I may want my user to have complete Read Write privileges for Ledger A, buthe should be able to only “View” the data that exists in Ledger B. Data Access Set also makes this kind of a combination possible.

The General Ledger Accounting Setup Program automatically creates a data access set for each ledger and reporting currency (journal level orsubledger level) assigned to a completed accounting setup. The system-generated data access sets created for each ledger and reporting currencyprovide full read and write access to the ledger and all of its balancing segment values and management segment values.

3. Accounting Setup Manager : Centralised Setup

Accounting Setup Manager is a new feature that streamlines the setup and implementation of Oracle Financial Applications.With the Accounting SetupManager, one can perform and maintain the following common setup components from a central location:

Legal EntitiesLedgers, primary and secondaryOperating Units, which are assigned to primary ledgersReporting CurrenciesSubledger Accounting Options. This is where you define the accounting methods for each submodule and associate them to the ledger where theaccounting is stored.Intercompany Accounts and Balancing RulesAccounting and Reporting Sequencing

As part of pre-upgrade process, one should run the Accounting Setup Manager Pre-Update Diagnosis Report. This report identifies potentialincompatibilities that would prevent you from using some new features in R12.

The report also details what changes, if any, the upgrade will have on certain objects.

You could refer the following note for the details on the diagnosis Report.

<Document 961742.1>: Information Request: Accounting Setup Manager Pre-Update Diagnosis Report

4. Definition Access Sets

Definition Access Sets are an optional security feature that allows one to control access to your General Ledger definitions. For example, one can preventcertain users from viewing, making changes, or using your recurring journal, FSG or any other setup for that matter.

This Security can be set at three levels:

UseViewModify

If you do not enable security, all users will be able to use, view, and modify your definition.

Following Steps will assist you set the definition:



Navigate to the function to be secured ( eg. Calendar, Budget Organization etc)Check the “enable security” checkbox.Hit the “Assign Security” button to assign the Definition Access Set.Grant Privileges as desired.

Note: Please be careful while setting up these definitions. Though the security is assigned at the responsibility level, the user logging in gets theprivileges that are a consolidations of all the responsibilities assigned to him.

Lets take an example. Say User has the following three responsibilities assigned:

ResponsibilityA View Budget Organization

ResponsibilityB Use Budget Organization

ResponsibilityC Modify Budget Organization

The user would now get all the three privileges whichever responsibility he logs in from

5. Multi-Ledger Processing

Introduction of Ledger sets in R12 facilitates the following accounting operations across ledgers:

Open / close periods for multiple ledgers simultaneouslySubmit concurrent programs for all ledgers in a ledger setCross ledger allocations, recurring journals and year-end closing journalscurrency translation for multiple ledgers simultaneouslyFinancial reporting (FSGs) across ledgersAccount inquiry across ledgersCreate Balance Sheet Closing JournalsCreate Income Statement Closing Journals

6. Alternate Accounts

It is a regular practice amongst users to disable code combinations where they donot require any futher activity to take place. Hence in 11i if there was acase where users were importing the existing data with one such code combination, the import program would error flagging invalid codecombination. This would hold up the entire group of transactions from getting imported.

Release 12 provides a solution to such an issue. When an account is disabled, users can prevent transactions that include the account from erroringduring journal import by defining a replacement account for the disabled account. Journal import replaces the disabled account with the replacementaccount and continues the import process if the replacement account is valid.

This improves processing efficiency by preventing the journal import process from erroring and enabling the successful creation of the journal when anaccount has been disabled.

7. Sequencing

In Release 12, in order to cater to the need for Legal compliance for countries like Europe and Latin America, two more sequencing options have beenintroduced as a part of standard application apart from existing Document Sequences. These Sequences can be assigned not only to journals in GeneralLedger module but also to those created in SLA:

• Accounting Sequence:

Accounting Sequences are assigned to GL journals when they are posted and to Subledger Journals once they complete accounting.

• Reporting Sequence :

Reporting Sequences are assigned to journals in GL and Subledger journals upon GL period closure. Once a period is closed, the close period programfires a ‘Create Reporting Sequences’ program as a shoot off. This program assigns reporting sequences to journals.

This is one of the replacement for Accounting Engine (AX) Legal Sequencing.

You could refer the following note for the details on this functionality:

- Document 1336723.1: Reporting and Accounting Sequences in R12 : A Whitepaper

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?id=1336723.1



8. Line Level Reconciliation

General Ledger Reconciliation allows users to reconcile transactions in General Ledger and ensure that the sum of these set of transactions is zero. Anexample where this functionality would be required is the VAT control account.

One can enable reconciliation either for Natural Account Values for specific code combinations. Using this new functionality, one can selective crossreference transactions by entering a "Reconciliation Reference" at the Journals Line level. One can perform account reconciliation eitherautomatically with the General Ledger Automatic Reconciliation report, or manually in the Reconciliation Lines window.

• Use automatic reconciliation to reconcile journal lines that have matching balancing segments, account segments, and reconciliation references, oroptionally where the reconciliation reference is blank.

• Use manual reconciliation to reconcile journal lines with different code combinations (including different balancing segments or account segments) ordifferent reconciliation references.

For both automatic and manual reconciliation, the balance for the journal lines that you Want to reconcile must be zero. Reconciliations can beperformed between transactions entered in the same or different currencies.

9. Third Party Control Accounts

The Third Party Control Account feature in the Oracle E-Business Suite enables organizations to maintain detailed balances by third party for an accountcode combination. Subledger Accounting checks that valid third party information is associated with the journal line if the account code combination is aThird Party Control Account. If it is not, then Subledger Accounting rejects the journal line.

For example, when the unidentified receipts account code in the Oracle Receivables is defined as a Third Party Control Account, accounting for theunidentified receipts will fail because no third party information is available for such receipts. Similar issues are observed with the rounding account andintercompany accounts.

General Ledger prevents manual journal entries from posting to the Third Party Control Accounts. This ensures that journal lines that post to the controlaccount codes such as Supplier Liability Account, Customer Receivables Account are associated with the valid third party information in the respectivesubledger modules.

Note: this feature was implemented starting 12.1.3 only as a result of an Enhancement Request evaluated by development and approved forimplementation. This will not be backported to previous versions and the only way to get this feature is to implement or upgrade to 12.1.3 version.



B) RELEASE 12 Vs RELEASE 11i : A GL UPGRADE PERSPECTIVE

In the pages above we saw what new functionalities does Release 12 have in store for me. Let us now see how do we map our existing 11i Setup to R12upgraded instance. We have tried to pick up most of the functionalities available and explained them in the following trail. The list may not be completelyexhaustive. You could leave us your feedback and we shall try to incorporate the changes.

1. Basic SetUp : Transformation Into R12

The upgrade creates a separate Accounting Setup for each primary ledger that is upgraded from a set of books.

The Sets of Books in Release 11i will become Primary Ledgers in Release 12.

Reporting Currencies: Multiple Reporting Currency (MRC) reporting sets of books become reporting currencies in Release 12.

Subledger Accounting Method: All upgraded ledgers in Release 12 will have a subledger accounting method assigned during the upgrade. Anyreporting currencies assigned to the ledger inherit the subledger accounting method from the source ledger. The subledger accounting method enablesOracle General Ledger to integrate with Oracle subledgers using Subledger Accounting. All upgraded, non-public sector ledgers will have a subledgeraccounting method assigned called Standard Accrual or Standard Cash. All upgraded public sector ledgers will have a subledger accounting methodassigned called Encumbrance Accrual or Encumbrance Cash. For US Federal customers, all upgraded ledgers will have the US Federal Accountingsubledger accounting method assigned to them

Legal Entities: HR Organizations classified as GRE/LEs in Release 11i will be upgraded as legal entities in Release 12. Legal entities can be assigned toa ledger and balancing segment values can optionally be mapped to legal entities to help identify transactions by legal entity.

Operating Units: All HR Organizations classified as operating units will be preserved in Release 12. If operating units are assigned to a set of books,then they will be associated to a primary ledger in an accounting setup.

2. Journal Entry

The Journal Entry process and the form have not undergone much change excepting the form layout. The Status Tab details like Posting, Funds,Approval in 11i have moved to 'Other' tab in R12. Other fields like 'Source', ‘Reference Date’, ‘Reconciliation Detail’s also exist this 'Other' tab.

Also, since users have access to multiple ledgers, a new field has been added to choose the ledger for which the journal needs to be creared. Allavailable ledgers are available as List of Value.



3. Posting

a) In 11, Balancing Intercompany Journal entry lines were generated at posting time by the GL posting routine In R12, the Balancing Routine(balancing API is called by GL and SLA): Generates balancing accounting entries for subledger journal entries at time accounting is created. The Programgenerates balancing journal entries upon Posting for all other journals. In Short, In R12,the intra/intercompany will be generated in SLA itself.

So, if there has been a case where the users have upgraded with some unposted journals as well, chances are that posting these journals may end inerror if they are not balanced as per intercompany and are from a subledger module. Posting Program creates intercompany lines only for non-subledger journals. Please apply Patch 12568564:R12.FUN.B to resolve such journals



b) To be able to Post a Journal, one should have

Write Access to All the Balancing Segment Values in the Batch.Subledger Level Reporting currency creates one single batch with different journals for Primary and Secondary ledger. So here we have onesingle Batch with two journals belonging to different ledgers altogether. Users would be able to Post these journals only if theresponsibility they are attached to has Write Access to both the ledgers.

c) In 11i, posting a Journal Reversal in the MRC Primary Books Generated a Reversal automatically in the Reporting Books as well. However, thisfunctionality was not included in R12 initially. This ER (Enhancement Request) is implemented now and included in version 12.1.3

Following patches have been released for earlier versions

For Release 12.0: Patch 9776694:R12.GL.A

For 12.1.1 and 12.1.2: Patch 9776694:R12.GL.B

In addition to applying the patch, there is a new checkbox for 'Synchronize Reversals between Primary and Secondary Ledger(s)' in AccountingSetup Manager under the Journal Processing Tab. This must be checked.

4. AutoPost

The Autopost functionality is retained pretty much the same. However, considering the advantages of a ledger set that R12 offers, one can now shareAutoPost Criteria sets across multiple ledgers that share the same chart of accounts and calendar and use the AutoPost Criteria sets to post journalsacross multiple ledgers simultaneously.

To utilize the AutoPost feature, you must define an AutoPost Criteria Set and assign multiple ledgers or ledger sets to the AutoPost Criteria. When yourun or schedule the AutoPost program, the program posts journals for multiple ledgers.

Navigation: Setup : Journal > AutoPost

5. Journal Reversal

a) Prevents Reversal of Journals with Frozen Sources

It was possible to reverse a frozen subledger journals in 11.5 but the same is not possible in R12 as an enhancement request has been implemented.This change in functionality is intended and expected in Release 12, one will not be able to reverse these journals unless the subledger journal source isUnfrozen.

Following Navigation will help you to do so :

Navigate to: Setup>Journal>SourcesQuery for the source of your journalSelect the intended option from the 'Freeze journals' list of values:

Yes: Journals from this source cannot be changed in the Enter Journals form nor the Journal Correction form. In addition, you cannotreverse journals with Subledger Accounting journal sources that are frozen.No: Journals from this source can be changed in both the Enter Journals form and the Journal Correction form. In addition, you canreverse journals with unfrozen Subledger Accounting journal sources.Journal Entry Page Only: Journals from this source cannot be changed in the Enter Journals form but can be changed in the JournalCorrection form. In addition, you cannot reverse journals with Subledger Accounting journal sources that have this option.

Retest the issue.

Note: A subledger journal should not be reversed as it will cause inconsistency between the subledger accounting (XLA) data and the General Ledgerdata. The reversal should be performed at the subledger level and not directly in GL.Also. It is strongly advised that you freeze the subledger source back after you reverse the journal; unfreezing subledger journal sources will allow usersto reverse subledger sourced journals at will, causing reconciliation problems between general ledger and the subledgers.

b) Prevents Reversal Unposted Journals :

In R12, the default behavior has changed, and its not possible to edit or reverse an Unposted journal. A reversed journal should be an exact duplicate ofthe journal it is reversing.

However, there are circumstances where you may want to edit a reversed journal. This is provided for via patch 6691641 and a profile "GL:Edit ReverseJournals".

Please refer to Document 567641.1 - R12 Cannot Update Journal Name And Description Of Reversed Journal has more details

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?id=567641.1



6. Autoreversal

To utilize the AutoReversal feature, you may define the AutoReversal Criteria Set similar to what you had in 11i. Owing to the multi ledger access inR12, an additional setup would be required here. You will have to assign this Autoreversal Critera Set to the required ledgers using Accounting SetupManager.

So, if you have just upgraded to R12 and your reversals are not happening, check if the Reversal Criteria set is attached to your ledger.

7. Journal Import

a) Reduced Manual Intervention:

R12 did bring in some changes in Journal Import Program. If we recollect the create Accounting Programs in Release 11i populated the data in theinterface table called GL_INTERFACE.

It was then required to run the Journal Import Program from the General Ledger Responsibility to bring in this data into GL base tables. However, thisarrangement also made it possible for users to make any changes in this date lying in the interface table. Now, when the modified data was imported,this could cause reconciliation differences between the submodule and General Ledger.

Release 12 provides an almost solution to this occurrence. The table structure and process flow exists the same even now, but this is hidden from theend users. The Transfer program populates the data in the table gl_interface and fires Journal Import automatically. In case of any errors, the data isrolled back to SLA, leaving nothing in GL_INTERFACE. This process ensures minimal manual intervention and issues that could be caused because ofthat. Having said this, I may want to re-emphasize that the table GL_INTERFACE very much exists to be bring in data from traditional sources. Alongside,the Journal Import form also remains the same to allow import of such a data.

Data Access Sets do apply to Journal Import too. To be able to import data, one should have either Full or Read/Write Access to the ledger and all theBalancing Segment Values for which data is populated in GL_INTERFACE. In case one does not have access to the Ledger at all, the LOV for Ledger willnot appear in Journal -> Import -> Run screen and hence he will not be able to submit Journal Import.

If there are multiple balancing segments in the data in GL_INTERFACE, and the responsibility has access to a few and not to others, then you will be ableto run Journal Import but it will complete in Warning and data will not be imported. Error shown in the Journal Import Execution report would be: EM29 : You do not have access to this ledger and account combination.

b) Import Delete:

R11i had a form to delete data from GL_Interface. The gl_interface data in R12 must now be deleted via a program(GLLDEL Program -Delete JournalImport) submission and not via a form as in previous General Ledger versions. Also, one may need to have read and write access to the ledger or readand write access to all of the import data's balancing segment values or management segment values to delete the journal import data.

This program works the same as the R11i Journal/Import/Delete program in that it will not pick delete batches with all records in "NEW" status. Somerecords in the batch must be of another status (errored).

c) Summarization Control setup with GL which can be overridden while import run.



Release 12 now provides a setup in General Ledger that controls if the Import for a particular module would be in Detail or in Summary. However,these are the default values and can be overridden while running the Transfer Program from the Submodule.

11i on the other hand, did not have any such controlled setup. The Summarization control had to be defined each time the user ran the TransferProgram to General Ledger.

Following is the navigation that determines this setup :

Using General Ledger responsibility, navigate toFinancials -> Accounting Setup Manager -> Accounting SetupsQuery for the Ledger being usedUpdate Accounting OptionsSelect update for 'Subledger Accounting Options' 'Update Accounting Options' for the Application There exists an option 'General Ledger Journal Entry Summarization', which can be set to following values:

i. Summarize by GL Date (Journal Import will create summary journals based on Accounting Date)

ii. No Summarization (Journal Import will create journals in Detail mode)

iii. Summarize by GL Period (Journal Import will create summary journals based on Period to which the Accounting Date falls)

Thus the option 'General Ledger Journal Entry Summarization' will determine if the Import for the application is being done in Detail or Summary mode.

d) Language Independent Import:

Prior to Release 12, it was needed that the Journal Import should be run in the same language as the language, which was used to transfer data toGL_INTERFACE. Though this is not much relevant now (the transfer and journal import are triggered together); still Journal Import can be madeindependent of the language. This can be achieved by running journal import using the Source and Category Key.

Generally the columns user_je_source_name and user_je_category_name in gl_interface, correspond to the columnsGL_JE_SOURCES.user_je_source_name and GL_JE_CATEGORIES.user_je_category_name respectively. These values change for the different languageand thus making journal import language-dependent. However while defining the sources (General Ledger Responsibility : Setup -> Journal -> Source),if the option “Import Using Key” is selected, then import refers to GL_JE_SOURCES.je_source_key and GL_JE_CATEGORIES.je_category_key. These beingthe Key values are common across languages and hence journal import becomes language independent.

8. Recurring Journals

Recurring Journals retain the basic setup and program flow as in 11i. But even this one comes with an enhancement. Release 12 allows creation ofRecurring journals with foreign currencies. Following ER was implemented in R12.

Bug 784902: FOREIGN CURRENCY RECURRING JOURNALS SHOULD BE ALLOWED

One may have to enter the currency and the Conversion rate type during setup.

In 11i, Only functional or STAT currency could have been selected when defining a recurring journal



9. Suspense Accounts

In Release 11i one could setup suspense accounting by making two small setups

Enabling Suspense checkbox andEntering a code combination field for the Suspense Account.

However in R12 there is no checkbox anymore.The Suspense Account is activated if a code combination is populated in the "Suspense Account Field". Beaware when you upgrade from 11i to R12 that the suspense accounting can be activated without your knowledge.

10. Translation Process

a. Period End Rates and Period Average Rates donot Exist anymore in R12

Have you ever faced a situation in R12 where the translation amounts did not tally up with what you are expecting? Well chances are that you may beusing the traditional approach of calculation in 11i.

Release 11i used the Period End rates for the calculation of translated balances for Balance Sheet accounts and Period Average Rates for revenue andexpense accounts.



Release 12 is done away with the concept of Period End and Period Average rates. Now one can define their own rate types and assign them to bepicked up as “Period Average” and “Period End” rates. Now, whenever the translation program is looking for a Period End rate, it would pick up the ratetype defined against the field “Default Period End Rate Type”.

b. Balances Maintained as Separate Reporting Ledger

Balances when translated in 11i , saved the translated amounts in the table GL_BALANCES against the same ledger. The Translated Flag was marked as“Y” to identify these rows.

Release 12 now introduces a new functionality. Translated balances are saved against a different ledger altogether. A Reporting ledger gets attached toyour Primary, as soon the Translation Program is run. So now, balances are indeed saved in the same table GL_BALANCES but against a differentReporting ledger.So, if you have just upgraded to R12 and see a new Reporting Ledger attached to your Primary, donot worry. This is the expectedfunctionality. If the users have been running translations in Release 11i, reporting ledger get automatically created for these currencies at the 'Balance'level. One could validate this by cross checking history of translation in 11i from table:GL_TRANSLATION_TRACKING

Below is a screenshot that shows how a GBP translation ledger looks like. The Primary Currency of the Primary ledger is set up as USD in the belowexample.

11. Financial Statement Generator Reports

The FSG strucrture remains very similar to what existed in Release 11i.

FSG report output takes into account data access set security and only shows the data accessible for one's responsibility. One must have at least readaccess to the data to be able to view it on a report.

Ledger Sets allow you to aggregate data across multiple ledgers in the ledger set. Here is an example of the output from an FSG report. The totalcolumn represents the aggregated or summarized balances across multiple ledgers. This report is generated with the rows representing the accountsand the columns representing the ledgers; the total column represents the total across the ledgers using a ledger set. You can instantly summarize dataacross multiple ledgers in a single FSG report. This provides greater control and visibility into your global operations because you can easily check theperformance of your entities by running one report. Another added benefit with ledger sets is that they essentially allow you to perform real-timeconsolidation. If you have fairly simple consolidation needs, then you could use ledger sets. For example, if you are only using Oracle Financials on asingle database instance and you do not acquire or dispose of companies on a regular basis or have partial ownerships, then you can use ledger sets toperform real-time consolidation. All you need to do is use a different balancing segment value or ledger to house your consolidation entries and thengroup that ledger into a ledger set



FSG Transfers across Instance Versions:

It is not possible to transfer FSGs from an 11i instance to an R12 instance. The following is an Enhancement request already logged for thisrequirement

Bug 8975401 - Unable to migrate gl fsg reports from 11i to R12

12. Budgetary Control in R12

a) Program – Create Journals

In release 12, the Program create Journals is no longer used. This is reserved for modules like Public Sector Budgeting Only.The transfer ofencumbrance entries from the subledger to GL is now done by the Subledger Accounting - Transfer to GL process from the relevant subledger.

The cleanup of the gl_bc_packets table that used to be done by the Sweeper program is now done by a new program called BCOPT – “BudgetaryControl Optimizer”.

So, now if you are looking for clean up for the table gl_bc_packets in R12, please run the “Budgetary Control Optimizer” instead of Program CreateJournals.

b) Different Budgets can be attached for Different time frame

Release 12 has incorporated the functioanlilty of being able to assign multiple budgets for exclusive time frames. Eg One may want Budget A to beutilised for a code combination from 2009 to 2011 and Budget B to be utilised for the time frame 2012 to 2015. This is now possible in R12.



In the above example, the specified set of code combinations would use the Budget “CORP BUD 2006-9’ until its active. The control would automaticallymove to the budget “AGED SR” thereafter. Would you recollect the traditional 11i issue of incorrect last periods. Such a situation can normally be doneaway with now by adding a new budget in the Assignments tab as above.

C) SOME COMMON QUERIES ADDRESSED

1. What is a Ledger? What happened to my Sets of Books?

Your 11i Set of Books is now an R12 ledger, any 11i sets of books you had will be a ledger after you run the R12 upgrade

2. Why did you change the name?

A Ledger is a much better description and matches the business terminology more closely.

3. Does the new table gl_ledgers replace gl_sets_of_books table.

Yes. However the table gl_sets_of_books still exists. Some standard modules that donot use SLA accounting accounting yet still populate the set_of_books_idcolumn in various tables.

The table gl_sets_of_books helps in this mapping.

4. So what about my custom reports that query gl_sets_of_books table or gl_sets_of_books_v view ?

No need to change those. For backward compatibility we created a view gl_sets_of_books which references the gl_ledgers table. gl_sets_of_books_v is alsomodified to reference gl_ledgers table.



5. What happens to the sob_id, are these primary keys preserved?

Yes, the sob_id from 11i will become the ledger_id in R12. The sets of books related data was captured in the table gl_sets_of_books while ledger relevantdata is captured in the table gl_ledgers

6. I see Ledger_id in the gl_interface table, do I have to update all my feeder programs that write to that to populate ledger_id instead ofsob_id?

No. GL_INTERFACE is backward compatible, the gl_sets_of_books_id column is still there and ledger_id is optional, if Journal Import does not find any valuein ledger_id it will use the sob_id

7. Is there documentation that lists the table that have changed between release 11i and release 12?

There does not exist one all inclusive document that documents the change in tables or new table added for the migration of release 11i to release 12. Thebest source for this information is to review the Electronic Technical Reference Manuals (eTRM). More information about using the eTRM in ElectronicTechnical Reference Manuals (eTRM) Basics (Doc ID 432769.1)

You could also refer Appendix in the below trail. This is a generic representation of table structure and may not be all inclusive.

APPENDIX: CHANGE IN STRUCTURE OF TABLES RELATING TO GL MODULE

1. New Tables

Table Name Feature Area

FUN_SEQ_ASSIGNMENTS Setup Forms and Programs

FUN_SEQ_CONTEXTS Setup Forms and Programs

FUN_SEQ_ENTITIES Setup Forms and Programs

FUN_SEQ_HEADERS Setup Forms and Programs

FUN_SEQ_REQUESTS Setup Forms and Programs

FUN_SEQ_RULES Setup Forms and Programs

FUN_SEQ_VERSIONS Setup Forms and Programs

GL_ACCESS_SET_ASSIGNMENTS Setup Forms and Programs

GL_ACCESS_SET_NORM_ASSIGN Setup Forms and Programs

GL_ACCESS_SETS Setup Forms and Programs

GL_AUTOREV_CRITERIA_SETS Journal Entry

GL_BC_PACKETS_HISTS Budgets and related objects

GL_BUDORG_BC_OPTIONS Budgets and related objects

GL_COA_MAPPINGS Consolidation and Eliminations

GL_DEFAS_ACCESS_SETS Setup Forms and Programs

GL_DEFAS_ASSIGNMENTS Setup Forms and Programs



GL_DEFAS_RESP_ASSIGN Setup Forms and Programs

GL_JE_INCLUSION_RULES Setup Forms and Programs

GL_JE_LINES_RECON Reconciliation

GL_JE_SEGMENT_VALUES Journal Entry

GL_LE_VALUE_SETS Setup Forms and Programs

GL_LEDGER_CONFIG_DETAILS Setup Forms and Programs

GL_LEDGER_CONFIGURATIONS Setup Forms and Programs

GL_LEDGER_NORM_SEG_VALS Setup Forms and Programs

GL_LEDGER_RELATIONSHIPS Setup Forms and Programs

GL_LEDGER_SEGMENT_VALUES Setup Forms and Programs

GL_LEDGER_SET_ASSIGNMENTS Setup Forms and Programs

GL_LEDGER_SET_NORM_ASSIGN Setup Forms and Programs

GL_LEDGER_SET_REQUESTS Setup Forms and Programs

GL_LEDGERS Setup Forms and Programs

GL_LEGAL_ENTITIES_BSVS Setup Forms and Programs

GL_MGT_SEG_UPGRADE Other Issues

GL_MGT_SEG_UPGRADE_H Other Issues

GL_SEG_VAL_HIERARCHIES Setup Forms and Programs

GL_SEG_VAL_NORM_HIERARCHY Setup Forms and Programs

GL_SUMMARY_BC_OPTIONS Budgets and related objects

2. Obsoleted Tables

None of the obsolete tables have been dropped. Some obsolete tables have been renamed with the suffix _11i. Some obsolete tables are highlighted below.

Table Name Feature Area Replaced By

GL_IEA_AUTOGEN_MAP Global Intercompany System Advanced Global Intercompany

GL_IEA_CLEARING_ACCOUNTS Global Intercompany System Advanced Global Intercompany

GL_IEA_IMPORT_REGISTRY Global Intercompany System Advanced Global Intercompany

GL_IEA_INTERFACE Global Intercompany System Advanced Global Intercompany



GL_IEA_RECUR_BATCHES Global Intercompany System Advanced Global Intercompany

GL_IEA_RECUR_LINES Global Intercompany System Advanced Global Intercompany

GL_IEA_SEGMENT_MAP Global Intercompany System Advanced Global Intercompany

GL_IEA_SEGMENT_RULE_MAP Global Intercompany System Advanced Global Intercompany

GL_IEA_TRANSACTION_LINES Global Intercompany System Advanced Global Intercompany

GL_IEA_TRANSACTION_TYPES Global Intercompany System Advanced Global Intercompany

GL_IEA_TRANSACTIONS Global Intercompany System Advanced Global Intercompany

GL_INTERCOMPANY_ACC_SETS Global Intercompany System Advanced Global Intercompany

GL_INTERCOMPANY_ACCOUNTS Global Intercompany System Advanced Global Intercompany

GL_MC_BOOK_ASSIGNMENTS Setup Forms and Programs Advanced Global Intercompany

GL_MC_CONVERSION_RULES Setup Forms and Programs GL_LEDGER_RELATIONSHIPS

GL_MC_REPORTING_OPTIONS Setup Forms and Programs GL_JE_INCLUSION_RULES

GL_OASIS_FIN_ASSIGNMENTS Financial Intelligence GL_LEDGER_RELATIONSHIPS

GL_SYSTEM_SETUP Setup Forms and Programs Relevant columns were moved to the GL: Numberof formulas to validate for each MassAllocationbatch, GL: Number of formulas to validate foreach Recurring Journal batch and GL: ArchiveJournal Import Data profile options

GL_TRANSLATION_RATES Revaluation, Translation and Conversion Rates GL_DAILY_RATES

RG_DSS_DIM_SEGMENTS Financial Analyzer Enterprise Planning and Budgeting

RG_DSS_DIMENSIONS Financial Analyzer Enterprise Planning and Budgeting

RG_DSS_HIERARCHIES Financial Analyzer Enterprise Planning and Budgeting

RG_DSS_HIERARCHY_DETAILS Financial Analyzer Enterprise Planning and Budgeting

RG_DSS_REQUESTS Financial Analyzer Enterprise Planning and Budgeting

RG_DSS_SEG_RANGE_SETS Financial Analyzer Enterprise Planning and Budgeting

RG_DSS_SEG_RANGES Financial Analyzer Enterprise Planning and Budgeting

RG_DSS_SYSTEM_SEG_ORDER Financial Analyzer Enterprise Planning and Budgeting

RG_DSS_SYSTEM_VARIABLES Financial Analyzer Enterprise Planning and Budgeting

RG_DSS_SYSTEMS Financial Analyzer Enterprise Planning and Budgeting

RG_DSS_VAR_DIMENSIONS Financial Analyzer Enterprise Planning and Budgeting

RG_DSS_VAR_SELECTIONS Financial Analyzer Enterprise Planning and Budgeting



RG_DSS_VAR_TEMPLATES Financial Analyzer Enterprise Planning and Budgeting

RG_DSS_VARIABLES Financial Analyzer Enterprise Planning and Budgeting

3. Modified Tables

The set_of_books_id column has been renamed to ledger_id in all tables with some exceptions as mentioned below. All setups secured by definition accesssets have a new security_flag column in the relevant tables.

Table Name Feature Area Brief Description of Change

GL_ALLOC_FORMULAS MassAllocations,Budgets andEncumbrances

Add currency_conversion_type to support foreign currency allocations

GL_AUTO_ALLOC_SETS MassAllocations,Budgets andEncumbrances

Add chart_of_accounts_id, period_set_name and accounting_period_type to enable sharing ofAutoAllocations across ledgers sharing the same chart of accounts and calendar

GL_AUTOMATIC_POSTING_OPTIONS Posting Add ledger_id to enable AutoPost across ledgers

GL_AUTOMATIC_POSTING_SETS Posting Add chart_of_accounts_id, period_set_name and accounting_period_type to enable sharing ofAutoPost Criteria Sets across ledgers sharing the same chart of accounts and calendar

GL_AUTOREVERSE_OPTIONS Journal Entry Add criteria_set_id to support AutoReverse criteria sets stored in the master tableGL_AUTOREV_CRITERIA_SETS

GL_BALANCES Balances andRelated Objects

Add quarter_to_date_dr_beq, quarter_to_date_cr_beq, project_to_date_dr_beq andproject_to_date_cr_beq to store entered ledger currency balances

GL_CODE_COMBINATIONS Setup Forms andPrograms

Add alternate_code_combination_id to support replacement for disabled accounts functionalityimplemented by Journal Import

CONSOLIDATION Consolidation andEliminations

Included coa_mapping_id to enable consolidations to use chart of accounts mappings

GL_INTERFACE Journal Import Included ledger_id and retain set_of_books_id for backward compatibility

GL_JE_BATCHES Journal Entry Dropped set_of_books_id and add chart_of_accounts_id, period_set_name andaccounting_period_type to support batches containing journals for multiple ledgers sharing thesame chart of accounts and calendar

GL_JE_HEADERS Journal Entry Included columns to store the accounting and reporting sequences

GL_PERIOD_STATUSES Setup Forms andPrograms

Included Add ledger_id and retained set_of_books_id for backward compatibility

GL_RECURRING_HEADERS Recurring Journalsand Budgets

Included currency_conversion_type to support foreign currency recurring journals

GL_SYSTEM_USAGES Setup Forms andPrograms

Included efb_upgrade_flag and reconciliation_upg_flag to track successfully completed optionalpost-update programs

4 New Views

A number of new views have been added to support UIs and processing of new features. Some of the views are mentioned below.



View Name Feature Area

GL_ACCESS_SET_LEDGERS Setup Forms and Programs

GL_ALC_LEDGER_RSHIPS_V Setup Forms and Programs

GL_AUTOREV_CRITERIA_SETS_V Journal Entry

GL_BUDGET_ASSIGNMENTS_UNIQUE_V Budgets and Related Objects

GL_BUDORG_BC_OPTIONS_V Budgets and Related Objects

GL_DEFAS_ASSIGNMENTS_V Setup Forms and Programs

GL_DEFAS_RESP_ASSIGN_V Setup Forms and Programs

GL_ENTERED_CURRENCIES_V Balances and Related Objects

GL_HISTORICAL_RATES_PERIOD_V Revaluation, Translation and Conversion Rates

GL_JE_LINES_RECON_V Journal Entry

GL_LEDGER_LE_V Setup Forms and Programs

GL_LEDGER_NAMES_V Setup Forms and Programs

GL_LEDGER_NORM_BSVS_V Setup Forms and Programs

GL_LEDGER_SET_ASSIGNMENTS_V Setup Forms and Programs

GL_LEDGER_SET_NORM_ASSIGN_V Setup Forms and Programs

GL_LEDGER_SETS_V Setup Forms and Programs

GL_LEDGERS_PUBLIC_ALL_V Setup Forms and Programs

GL_LEDGERS_PUBLIC_V Setup Forms and Programs

GL_LEDGERS_V Setup Forms and Programs

GL_REC_BATCHES_LOV_V Recurring Journals and Budgets

GL_SECONDARY_LEDGER_RSHIPS_V Setup Forms and Programs

GL_SETS_OF_BOOKS Setup Forms and Programs

GL_SUMMARY_BC_OPTIONS_V Summarization

GL_SUMMARY_TEMPLATES_V Summarization

GL_TRANSLATION_RATES Revaluation, Translation and Conversion Rates









CLICK TO DOWNLOAD PDF FORMAT

Still Have Questions?

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle SupportGeneral Ledger Community.

To provide feedback on this note, click on the Rate this document link.

References

https://support.oracle.com/epmos/main/downloadattachmentprocessor?attachid=1443965.1:WHITEPAPER&clickstream=no

https://communities.oracle.com/portal/server.pt/community/general_ledger/240%22

GL Changes _R12 vs 11i

Documents

Transcript of GL Changes _R12 vs 11i