R12: How To Correct Misclassified Accounts in General Ledger [ID 872162.1] Modified 14-DEC-2011 In this Document Goal Symptoms Detecting Misclassified Accounts Important Note Impact of not Resolving Misclassified Account Solution Explanation Solution APPENDIX A APPENDIX B Community Discussions Feedback References Type HOWTO Status PUBLISHED

Applies to:Oracle General Ledger - Version: 12.0 and later [Release: 12.0 and later ] Information in this document applies to any platform.

GoalThe goal of this note is explain the correction of Misclassified Accounts. If using 11i and earlier versions of applications, then please go to Note 1050920.6 How To Correct Misclassified Accounts in General Ledger in 11i. An account is misclassified if the account type of the segment value is different from the account type on a code combination that uses that value. It occurs when the account was initially created with the wrong account type and had code combinations generated from it. Then the account type is subsequently changed on the account value screen to a different account type. This change does not change the account type of the code combination it keeps its original type. The process of changing the account type of a code combination is complicated because you can not do it through the form. This is deliberate as it prevents the account type of a code combination being changed after it is used without users making decisions on how to correct the accounting of journals posted in earlier years. At year end balance sheet balances will be rolled forward and P&L balances will be rolled up into retained earnings. Manual intervention is required to correct the year end balances. There are 5 basic Account Types available and they form two groups: Profit and Loss accounts or Income Statement accounts - the balances are automatically transferred into the Retained Earnings account in the first period of the new year, and therefore the new year's beginning net balance of these accounts is zero: o Expense o Revenue

Balance Sheet accounts - the balances are rolled forward to the same account in the first period of a new year, and therefore the new year's beginning balance is the same as the ending balance of previous year: o Asset o Liability o Owners equity

There are two types of misclassification: a) Simple: between account types in the same group. At year end the behavior of the roll-forward is unchanged. The fix is quite easy as you just need to fix the code combination using sql (this may still impact budgets see Note 308219.1 Effects Of Misclassified Accounts On Budgets And Encumbrance). Example 1. Account 1000 is setup as Expense 2. Code combination 01.1000.1000 is created (the code combination inherits the Expense type) 3. Account 1000 is changed to account type Revenue (both in the same group). This does not change the account type of 01.1000.1000. 4. A new code combination, for example 01.1000.2000 for this account will be Revenue (inherits the current account type). 5. Any of the combinations follow the same behavior at the year end.

b) Complex: the incorrect account type of the account is in a different group of the desired type. At year end the behavior of the roll-forward is different between these two account types so some of the code combinations do not behave as expected for its position in the statement of accounts. Example 1. Account 5000 is setup as Expense (the default) 2. Code combination 01.5000.1000 is created (the code combination inherits the Expense type) 3. Account value 5000 is changed to account type Asset (are in different groups). This does not change the account type of 01.5000.1000. 4. A new code combination, for example 01.5000.2000 for this account will be Asset (inherits the current account type). 5. The 2 combinations will not follow the same behavior at the year end. One, with Expense type, will transfer the balance to the Retained Earnings account, while the other, with Asset type, will keep the balance in the new year.

SymptomsThe effects of misclassification can be observed in different places: In Budgets You are unlikely to see the Simple form causing symptoms in many circumstances but you will find that budget uploads become Debit or Credit depending on whether they are account type Expense, Asset or Owners equity for Debits or Revenue and Liability for Credits. See Note 357956.1: 'Misclassified Accounts Caused Budget Amounts to be Loaded Incorrectly' to help

identify budgets loaded the wrong way round because of misclassifications. You also see this in the complex form if for example the account type started as expense and was changed to liability. The budget would be a Dr instead of a Cr. In Standard Reports In standard reports like the Trial balance or Account Analysis in the first period of the new year you find that the Opening balance is zero instead of matching the previous years closing balance. Running the period end diagnostic Note 463519.1 shows that there are no apparent errors. On further investigation you notice that either the retained earnings is inflated by the amount or that the account has rolled into the new year when you did not expect it. You will not get this in the simple form only the complex form. In FSG Reports The Balance Sheet account YTD amount start at zeros in the new year because the balance as at the last period of the year is rolled over to Retained earnings at year end. This only happens for the complex case. In Create Account Combination Form In Setup > Account > Combinations you can see the wrong account type defaults in when you enter a code combination in the form GLXACCMB - Create Account Combinations. You can see this in either case.

Detecting Misclassified AccountsDetection of misclassified accounts depends on a change being made to the account segment value after code combinations have been generated causing the account type of one to vary from the account type of the other. If you have not yet changed th account type on the account value the fact that the code combination is of the wrong account type will not show up with any of these methods. Then it is a case of spotting that the code combination is not behaving properly (see symptoms). To detect misclassified accounts in 12.0 and higher use Note 463517.1 Diagnostic test Oracle General Ledger (GL): Misclassified Accounts Activity. The following may also help Note 259210.1 How to Identify Account Code Combinations Having An Account_type Different From Account to help identify misclassified accounts.

Important NoteThis article is a technical description of how to correct misclassified accounts. It is envisaged that the misclassification will be discovered shortly after year end and that accounts have not yet been published. For the complex type problem if accounts have been published or the problem goes back over several years then consideration must be given to whether the amounts are material. You may need advice from your accountants and auditors in that case as for material amounts it would be normal to report this as a prior year adjustment in the income statement.

Impact of not Resolving Misclassified AccountThe first year where there is a misclassified code combination there is no impact. In the First period of the second year the balance will roll forward incorrectly. It will either remain as the bought forward balance for Owners equity, Asset or Liability account or it will be rolled forward as part of the retained earnings balance for the new year for Expense and Revenue accounts. As yet the reports at year end will still be correct because the accounts are reported according to where they appear in the chart of accounts not by

the account type. In the first period of the second year the Year To Date (YTD) figures reported for the account will be incorrect in monthly management reports. For Income statement accounts this means that the expenditure or income against budget will be overstated or in the balance sheet the asset or liability will be understated the difference being in retained earning. In the last period of the second year the published accounts will have incorrectly stated the retained earnings. This will be higher or lower depending on the type of account and whether its a debit or credit. This time although the code combination will still appear in the right part of the accounts the value will be under or over stated. Income statement accounts classified as balance sheet will be showing last years balance included in this year while balance sheet accounts will be understated by last years year end balance. In the third years opening balance you will have two years of miscalculation. If you have gone past the second years reporting and published the accounts without fixing the code combination the accounts will contain errors. If you think these errors are material in size the accounting treatment of this error must be discussed with your accountants or auditors to satisfy the rules governing the publication of company financial statements. If the misclassification is to an income statement account type the difference will be between the retained earnings and the balance sheet ie an asset or liability is understated the difference going to retained earning which is in Owners Equity. For a balance sheet account type the difference is that the revenue or expense will be overstated. Technically not fixing all the years that the code combination existed would only be a problem if you had to later do a fix to the same account combination and that fix corrected all the balances for previous years. This might lead you to think the problem had been incorrectly resolved. Finally translation looks back at all transactions since the code combination was raised so it will be affected by changes.

Solution ExplanationFor the simple situations where the account type is within the same group then go to the sql solutions in the appendix at the end of this note. You do not need to make any journal adjustments for the following cases: You are changing the types belonging to the same group: o Expense to Revenue or vice-versa o Asset to Liability or vice-versa o Asset to Owners Equity or vice-versa o Liability to Owners Equity or vice-versa There are no balances in previous years and the new year is not yet open. There are no journals posted in the misclassified combinations.

For complex situations you will need to clear the balance from the previous year then re-enter it once the correction ot the account type is done. If more than one year is involved you need to consider whether the amounts are material and need to be reported in the year end report otherwise this process will suffice. This is a 4 step process: 1. Identify all the code combinations that are misclassified

2. "Zeroise" the balances in the code combinations with the problem as at the end of previous year in all currencies and all Ledgers that share the chart of accounts. If you dont do it in the end of previous year it will not effect current year's balances and so will not show in the reports correctly at year end. 3. Ask the DBA to run the script that corrects the problem code combinations. 4. Reverse the Journals that "zeroised" the balances in step 2 to bring them back into the correct accounts for the current year.

EXAMPLE Changing Profit & Loss to Balance Sheet. Let us use the scenario of the Complex example given above and study a chain of events:# Event Description Create account 5000 as Expense Create combination 01.5000.1000 (Expense) Journal Post Period 01.5000.1000 01.5000.2000 Retained Earnings Account (REA) Suspense Account

1

JAN07 JAN07

2

3

FEB07

+20000 DR 20000 DR 0 0 20000 DR 0 0

Actual Balance DEC07 4 Open New Year and the begin balances are New year final balances JAN08 DEC08

0

20000 DR as the combination was Expense the balance was transferred to the REA

0

5

Correct the account 5000 from Expense to Asset in the Segment value form. This does not effect the balances or the combination type. Create combination 01.5000.2000 (Asset)

6

7

New Journal FEBPost in the new 08 year Actual Balance DEC08

+30000 DR

+4000 DR

30000 DR 0

4000 DR 4000 DR

20000 DR 50000 DR

0 0

8

Open new year and the balances are "unexpected" because the misclassified transferred to REA

JAN09

as the combination is Expense the balances are still transferred to REA To fix the balances of the misclassified account 01.5000.1000 and of the effected REA you need to enter journals to make the year end balances = 0 9 Journal Post to DECzero out the 07 final balance 2007 (using the suspense account) Actual balance DEC07 Actual balance JAN08 Actual balance DEC08 Actual balance JAN09 10 Journal Post to DECzero out the 08 final balance 2008 Actual balance DEC07 Actual balance JAN30000 CR 20000 CR 20000 DR

0 0 30000 DR 4000 DR 4000 DR

0 0 0 30000 DR

20000 DR 20000 DR 20000 DR 20000 DR 30000 DR

0 0

0 0

20000 DR 20000 DR

08 Actual balance DEC08 Actual balance JAN09 0 0 4000 DR 4000 DR 0 0 50000 DR 50000 DR the suspense account is now holding the incorrect balances

the begin and this account was the effects of the final balances of not effected misclassification the account are because it was were removed now zero already correct from the REA 11 Use the sql to correct the 01.5000.1000 combination account type from 'E' to 'A'. Now the behavior will change in the end of year. 12 Reverse and DECPost the 07 journal described in #9 Actual balance DEC07 Actual balance JAN08 Actual balance DEC08 Actual balance JAN09 13 Reverse and Post the journal described in #10 DEC08 -20000 CR

-20000 DR

20000 DR 20000 DR 20000 DR 20000 DR -30000 CR 4000 DR 4000 DR

0 0 0 0

0 0 30000 DR 30000 DR -30000 DR

Actual balance DEC08 Actual balance JAN09

50000 DR 50000 DR the balances now show the correct total balance of the asset

4000 DR 4000 DR this account was always correct

0 0 the REA got corrected with no effect of the asset accounts the suspense account (or other) got cleared in the end

0 0

If you only adjust the last years accounts (30000 from 2008) the balance sheet accounts opening balance would be still incorrect by 20000, so you need to adjust both years in order to get the correct accounting.

Note that we have used for the reversal of the adjustment the change signs reversal method to avoid incrementation of the debits and credits. Because we adjusted both years the opening balance of both years is correct. We could have achieved the same roll forward by doing a journal for Dec 2008 as above and in the last step when the account combination had been corrected we could journal 20k from the retained earnings to the account 01.5000.1000. There are certain ramifications in this case for the accuracy of the accounting that you need to be aware of. Before this fix you have a balance sheet account that does not have the correct balance. That balance does not reflect whatever it is supposed to represent whether its cash in the bank or the value of laptops in the office. Each year for the last number of years this account combination was misclassified and the balance has been effectively 'written off' to retained earnings at each year end. If you want a true and fair representation of the balance sheet this needs to be fixed. That means changing the balance that have already been published and/or reporting in the published accounts if its large enough to be necessary.

There may be different methods to work it: 1. Fix the opening balance of this year and all past years as above. This gives you a true reflection of the opening balance but it changes the published accounts of past years. 2. Fix last years closing balance so all the amounts written off to retained earnings in previous years are journalled back into this account in the last period of last year before you fix the code combination using sql. Then run the glbalfix against the fixed code combination. This would still change the reported figures permanently so they dont match published reports but you wont need to reopen last years accounts. You will need an Sr raised to get the glbalfix script. this is time consuming and gives no added benefit. Its only used where localisations mean you cannot open the period again. 3. Only journal last years balance so the opening balance this year matches the closing balance last year. This would be bad accounting as the balance sheet figure would have no basis in reality. 4. You could correct the code combination using sql and create a journal between retained earnings and the misclassified accounts in the current period or the first period of this year (using the first period of this year avoids making this months PTD figures look distorted, when managers look at them the YTD will still have changed). This does mean that the fixing journal would be identifiable as the cause of the change in the retained earnings from last year and may need explaining with a note in the published accounts. This is the most visible method and possible the best for audit purposes since its easily explained why it was done where as the sudden unexplained change in last years accounts may look like an attempt to hide the need to fix the issue. It does not fix the years opening balance though so is not usually used.

Note 1: If mutiple ledgers share a Chart of Accounts you will need to make sure that all affected accounts in all ledgers are zeroised. You can determine the ledgers with the same COA using the following:select name ledgername, chart_of_accounts_id from gl_ledgers where chart_of_accounts_id in (Select chart_of_accounts_id from gl_ledgers where name = '&ledgername');

When there are consolidation, secondary or reporting ledgers and the ledgers share the same value set for the accounts segment then check that the code combinations associated with that account value are correct in those other ledger. If changing the value then the appropriate journals should be raised in both sets of ledgers and the accounts zeroised before changing the account type.

In R12 you can see which other hierarchies are associated with a value set in Setup : Financials : Flexfields : Key: Segments : 1. 2. 3. 4. query your hierarchy, click on segments button, click on the account segment and click on the value set button. On the value set screen you have a 'Usages' button top right. Click on this and you can see which hierarchies use this value set. 5. Click on the Key flexfield tab and it will give you the Application name, Flexfield Title, Structure name and segment name. When you change the account type it will change for all the structures (hierarchies) that share that value set. Note 2: You may have a situation where the code combination have been corrected but not the balances. In that case you may be asked to reset the code combinations to the original incorrect setting before zeroising the accounts. Note 3: If the misclassification has not crossed fiscal years, you only need to complete steps 8 and 9 in the solution. Note 4: This article contains the steps Oracle General Ledger users must complete in order to change the account type of a misclassified account. You need to complete all steps if the misclassification has existed before the current financial year. Note 5: If you are using Average Daily Balances, and have a misclassified account type, and the account type is misclassified to be an income statement instead of a balance sheet, or a balance sheet instead of an income statement, then you need to reverse all journals in all periods that have been posted to that account. Once you have posted these reversals, you can then fix the account type, reverse the reversals, and post them. see Note 150687.1 How to Correct Misclassified Account Types if Using Average Daily Balances. There is a script available (log an SR and request it quoting this note) by using glbalfix.sql that does this but it may have some performance issues due to the volume of work. Note 6: The Account type attribute is not inherited from the Value to the Combinations when you run GLNSVI Program - Inherit Segment Value Attributes. Note 7: If the misclassification only effects summary templates then you can drop and recreate the summary template after step 8 instead of journaling the affected accounts if you wish. Summary template combinations always have a type of Owners Equity. Since the summary template is updated by the detail level only and a summary code combination could have several account types rollup into it. As you cannot post directly to a summary account template it is virtually impossible for this to occur in a summary template only.

SolutionSTEP 1.

Reopen the last period of your prior fiscal year, if it is closed, using the open close period form. If the account was not active before the beginning of this year skip to step 8. STEP 2. Sometimes the problem code combination account type is updated before you discover the unbalanced account. Ensure the account type is still misclassified because you need to make a correction journal while the combination and segment value are the same as it was when the original journals were raised. To find the account type in use on the segment: 1. 2. 3. 4. 5. 6. STEP 3. If you did not run the diagnostic to check which code combinations are misclassified follow this step to do it manually. 1. Check all the code combinations with this account value to see if they match the segment value account type. Navigate >Setup> Account> Combinations Query on the account segment value with the rogue account type value. 2. Find out what the account type is for each one. Make a note or screen shot of these so you can see what values are currently against them. 3. Obtain balances as of the last period of the previous fiscal year by running an accounting report (General Ledger, Trial Balance, Account Analysis) or view the balance online by using the Account Inquiry form. Make sure you check all currencies. In order to correct the balances over the year end and so effect your reports this must remain Incorrect until steps 3-6 are complete. Note: If you use Reporting/Secondary ledgers then you must check the reporting/secondary ledger as well. STEP 4. Use the account inquiry screen or the account analysis report to find what the balances were in the last period of the previous year(s). Where there is no balance at the end of last year skip to step 8. If multiple years are involved its a business decision on how you would handle this. For changing an existing code combination with a Revenue or Expense account type it may be necessary to correct many prior years so that amounts originally passed to retained earnings can form the YTD opening balance of the current year otherwise the YTD balance would be inaccurate. The assumption here is that you would have discovered the issue in the first year. STEP 5. Create a journal entry that brings the misclassified account combinations balances to zero for the last period of your prior fiscal year for every currency. Navigation: Setup > Financial > Flexfields > Key > Values. Application: Select 'Oracle General Ledger' from the list of values (LOV). Title: Select 'Accounting Flexfield' from the LOV Structure: Select the applicable chart of accounts for your ledger from the LOV Segment: Select your natural account segment from the LOV Query back the bad account use the qualifier tab and check the account type.

The contra entry should go to a temporary account such as Suspense but not to retained earnings or another combination with the same account segment value as the one being fixed. (you will reverse this batch in a later step to re-post the balances using change signs so there will be no visible effect). Example: 01.100.5555.00 is misclassified because account 5555 is Expense when it should be Asset. This is causing the opening balance of 01.100.5555.00 to be zero (the amount has been passed to the retained earnings account). 99.100.9999.00 is a clearing account with the correct classification (any account type is good as long as its right). At the end of the year there is a balance net amount of 110.00 GBP (base currency) in the misclassified account 01.100.5555.00. To clear this the appropriate journal raised in the last period is: 01.100.5555.00 for 110.00 GBP Credit 99.100.9999.00 for 110.00 GBP Debit

Note: If you have multiple currencies in the account balance, create journal entries to zero out entries in your functional currency and to zero out entries for each foreign currency. You would set the profile 'Journals: Allow Multiple Exchange Rates' to Yes and enter the entered amount and accounted amount such that it clears the account. Note: If you use Reporting/secondary ledgers then you must check that the journal generated in these ledgers will "zeroize" the account as well. If not generate a journal in the ledger to cope with the rounding differences.The same applies to any secondary ledgers. STEP 6. Post the journal entry. For those with reporting ledgers or secondary ledgers that share this value set, must post the Reporting/Secondary ledger Journals. Then run a summary Trial Balance for this account to ensure the closing balance is zero in all ledgers. STEP 7. Verify the misclassifed account's balance is zero by running an accounting report (General Ledger, Trial Balance, Account Analysis) or view the balance online by using the Account Inquiry form. STEP 8. Correct the account type of the misclassified account as follows: 1. 2. 3. 4. Responsibility = General Ledger Super User Navigation = Setup/Financials/Flexfields/Key/Segments Navigate to the Key Flexfield Segments form. Oracle General Ledger prevents you from changing the account type unless you first unfreeze all Accounting Flexfield structures that reference your account segment, see Note 1015950.6 Uncheck the Freeze Flexfield Definition check box. 5. Repeat previous steps for each accounting flexfield structure which references your misclassified account type. 6. Navigate to Setup/Financials/Flexfields/Key/Values.

7. 8. 9. 10. 11. 12.

Application: Select 'Oracle General Ledger' from the list of values (LOV). Title: Select 'Accounting Flexfield' from the LOV Structure: Select the applicable ledger from the LOV Segment: Select your natural account segment from the LOV Enter your account value and click on the [Find] button. With your cursor on the value, tab over to the 'Qualifier' column. This will bring up the Qualifier window and you will see for example: - Allow Budgeting: Yes - Allow Posting: Yes - Account Type: Expense 13. In the 'Account Type' field, select Asset, Expense, Liability, Ownership or Revenue from LOV. 14. Save your changes before exiting the form. 15. Navigate back to the Key Flexfield Segment form, refreeze your accounting structure(s) and click on the [Compile] button. STEP 9. You must ask your Database or System Administrator to correct the account type of all accounts referencing the misclassified account by correcting the ACCOUNT_TYPE column in the GL_CODE_COMBINATIONS table using SQL*Plus. Example scripts are shown below in Appendix A and Appendix B. If you attempt to correct it on the code combination screen you will receive the message 'FRM-40200 Field Protected Against Update'. STEP 10. Restore the misclassified account balance by reversing the journal entries you posted to the last period of your prior fiscal year (in Step 6). Reverse the journal entry into the same period in which it was originally posted using the change signs method of reversal (change signs will reverse a 100Dr with a -100Dr so the PTD and YTD amounts will be unchanged by this fix. STEP 11. Post the reversing journal entry. Posting rolls the balances forward correctly to the next fiscal year and updates retained earnings where necessary. If you are using Reporting or Secondary ledgers make sure the reversal is posted in those ledgers as well. STEP 12. If in your close process you normally run 'Create Income Statement Journals' or 'Create Balance Sheet Closing Journals' then this may now be incorrect so you may need to take steps to correct them. The decision whether or not to do this is an accounting decision so you may need to discuss with your accountants and/or auditors in case the Journal results have been published. Should you need to make adjustments after the income statement closing journals or Create Balance Sheet Closing Journals are posted, reverse and post the original closing entries, make your adjustments, then rerun the closing process to capture the new adjustments. If the 'Create Balance Sheet Closing Journals' have already been reversed in the following year you may need to reverse the reversed journal. Change the period to the last period of the previous year post it and

reverse it again in that period to get the balances back to their original state. Then proceed with regenerating the 'Create Balance Sheet Closing Journals'. STEP 13. Review the corrected account balance by running an accounting report such as a Trial Balance or view the balance online by using the Account Inquiry form.

APPENDIX AThis script is for situations where only a few values are affected but many combinations. It should be used in its entirety. Copy and paste it into a text file called comb.sql and ftp or copy it to the server you are running the sql from and run it there. This is for versions R12.0 and higher only. This works in toad you can use the scripts but accept does not work on the server with sqlplusREM Changing account types script by Simon Goddard 02-APRIL-2002 PROMPT To run this sql you will need to know the name of your Ledgers PROMPT the name of the 'Natural account segment' PROMPT and the Account Type you are changing from and to. PROMPT WARNING: make sure your finance department have taken the initial steps 1- 7 PROMPT to correct the Misclassified Accounts for all sets of books according to the manual PROMPT or the Note 1050920.6. select name ledgername, chart_of_accounts_id from gl_ledgers where chart_of_accounts_id in (Select chart_of_accounts_id from gl_ledgers where name like '&&&&name');

PROMPT select the chart_id of the set of books you need to change from PROMPT results above. Ensure journals have been posted for all sets of books affected. ACCEPT chart_id number PROMPT 'Chart_id: ' select application_column_name segment_num, segment_name from fnd_id_flex_segments_vl where id_flex_num=&&chart_id and (ID_FLEX_CODE='GL#') and (APPLICATION_ID=101); PROMPT This gives the column names for all segments. PROMPT Enter the Account segment from segment_num above as SEGMENT# ACCEPT segment_num Char PROMPT 'SEGMENT#: ' select code_combination_id ccid, account_type from gl_code_combinations where &&segment_num = '&&acct_value' and chart_of_accounts_id = &&chart_id; PROMPT This gives a list of what the account type is currently set to

PROMPT store these results as backup PROMPT To update the combinations press enter else CTRL C ACCEPT endbit PROMPT 'continue:' Update gl_code_combinations set account_type = '&&New_Account_Type' where &&segment_num = '&&acct_value' and chart_of_accounts_id = &&chart_id and account_type= '&&current_account_type'; commit; select code_combination_id ccid, account_type from gl_code_combinations where &&segment_num = '&&acct_value' and chart_of_accounts_id = &&chart_id; Clear Buffer

APPENDIX BThis script is for where there are many values that need changing each with a number of combinations. These scripts can be run individually. This is for versions R12.0 and higher only. Important: Perform this on your test system first. Verify that you have a backup copy of the gl_code_combinations table before proceeding. Do not do this while users could be accessing the gl_code_combinations table.

1. Get the Chart Of Accounts id (COA id)select name ledgername, chart_of_accounts_id from gl_ledgers where chart_of_accounts_id in (Select chart_of_accounts_id from gl_ledgers where name like '&&&&name');

2. List the code combinations that contain the misclassified account type:select code_combination_id, account_type from gl_code_combinations where segment# = '&&acct_value' and chart_of_accounts_id = &&coa_id

NOTE: segment# represents the segment that holds the natural account segment value (i.e. account segment). 3. Update the combinations:Update gl_code_combinations set account_type = '&&New_Account_Type'

where segment# = '&&acct_value' and chart_of_accounts_id = &&coa_id

Valid values for Account_type are: A = assets E = expense L = liability O = owner's equity R = revenue

NOTE: segment# represents the segment that holds the natural account segment value (i.e. account segment).

Community DiscussionsStill have questions? Use the live My Oracle Support General Ledger Community window below, to search for similar discussions or start a new discussion on this subject.

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

ReferencesNOTE:1050920.6 - How To Correct Misclassified Accounts in General Ledger in 11i Related

Products

Oracle E-Business Suite > Financial Management > Financial Control and Reporting > Oracle General Ledger

Keywords ACCOUNT TYPES; ASSET TYPE; BALANCE SHEET; BALANCES; CLOSING BALANCE; EARNINGS; END BALANCE; END OF YEAR; FIRST PERIOD; GLBALFIX; INCOME STATEMENT; INCORRECT BALANCES; LAST PERIOD; LIABILITY; OPEN BALANCE; OPEN PERIOD; PERIOD END; PRIOR YEAR; RETAINED EARNINGS; REVENUE ACCOUNTING

Errors FRM-40200 Back to topArticle Rating Rate this document Excellent Good Poor Did this document help you? Yes No Just browsing How easy was it to find this document? Very easy Somewhat easy Not easy Cancel Important Note: this feedback may be anonymously visible to other customers until processed by Oracle Support. CommentsProvide f eedback f or this article. Please use 'Contact Us' f or other feedba