Purpose |
Questions and Answers |
General Questions |
Question 1: Why does an account have a 'M' in the Model Consolidation field but the corresponding Business Unit is not a Model? |
Question 2: Can I merge two or more accounts/account ids into one account and account id? |
Question 3: What is the significance of Chart of Accounts Refresh and how is the F0909 table linked to the F0901 table? |
Question 4: I have added a new account but did not run Chart of Accounts Refresh (R0909R). Will this have any impact on Trial Balance rollup or Annual Close? |
Question 5: What is the significance of Build Account Master Word Search Table program (R0901WS)? |
Question 6: How can I set system to enter third G/L Account Number instead of BU.OBJ.SUB while specifying an account? |
Question 7: What is the significance of a header account? |
Question 8: What is the impact of Fixed Asset Postig Edit Code (F0911.FPEC) field on the F1202 table? |
Question 9: Can a "." be use as part of the Business Unit, Object, or Subsidiary? |
Question 10: Is there a limitation to the number of accounts that can be added to the chart of accounts? |
Question 11: Why are Object account descriptions for LOD 7 to 9 displaying as 21 to 23 characters instead of its maximum 30 characters? |
Question 12: Why are some of the new accounts created in F0901 via the import feature not able to print on Trail Balance Report (R09410)? |
Defining Chart of Accounts |
Question 1: Can I add accounts to the F0901 table by importing data from excel? |
Question 2: Can I add accounts to the F0901 table directly using SQL? |
Question 3: What are the different options available for Account Separator Character? |
Question 4: Are there any repercussions of skipping Level of Detail (LOD) while setting up chart of accounts? |
Chart of Account Revisions |
Question 1: Are there any guidelines for modifying the Posting Edit Code of an existing account from 'L' to 'S'? |
Question 2: Is there a quicker way to modify multiple accounts rather than using Revise Single Account form? |
Question 3: Is there a batch process available to delete inactive accounts? |
Question 4: What are the different Global Updates available for Chart of Accounts? |
Question 5: Is there any way to prevent changes being made to Object and Subsidiary field? |
Question 6: Why do I get "Object Number Invalid as entered" error while trying to update an existing account? |
Question 7: Why does the Taxable Account field show as blank for some accounts in Account Master (F0901) table? |
Question 8: How to make it mandatory to enter an address book number for e.g. expense accounts.? |
Question 9: Why do I get "Account Number Invalid " errorm, when trying to change PEC for a Job Cost type account from "I" Inactive to " " Blank? |
Account Category Codes |
Question 1: How can you access account category codes 24 - 43 in P0901 application? |
Question 2: Why does the R09205P report not print the Account Category Codes 24 - 43? |
Question 3: Why do I get error: "Not found in User Defined Code 09/xx" while trying to add/modify an account? |
Flex Accounting |
Question 1: Can the object length be changed in the account flex format setup (P0907)? |
Question 2: Is it valid to setup an account structure like BU.OBJ.SUB.BU? |
Question 3: In an account structure like BU.OBJ.SUB.BU, is it possible to create accounts with blank values of Object Account or Subsidiary? |
Question 4: Is there any limit to the size of account structure? |
Question 5: Why is the Business Unit in the Account Number (ANI) field left justified instead of right justified? |
Account Translations |
Question 1: Why do I see the account description in English in Work with Accounts (P0901) application even the user profile is setup with language other than English? |
Question 2: Why does the system not show the modified language translation description, during copying of an account? |
Question 3: Is there any program to upload the Account Translations into F0901D table? |
This document is part of an Information Center - to see other documents related to Setup in General Accounting, please use the links provided below:
Information Center: JD Edwards EnterpriseOne General Accounting Product > Information Center: Using the JD Edwards EnterpriseOne General Accounting Product > Core Processes > Setup > Doc ID 664720.1
This document contains answer to frequently asked questions related to the Chart of Accounts.
Answer 1: If a business unit is a model, all of the accounts in the business unit contain a 'M' in the Model/Consolidated field in the F0901 table. Otherwise, the Model/Consolidated field is blank.
If you change a model business unit to a business unit that is not a model, you must run the Update Model/Consolidated Field program (R0006QD) to update the F0901 table. The system changes the Model/Consolidated field to blank for all of the accounts within the business unit.
Likewise, if you change a business unit that is not a model to a model business unit, you must run the Update Model/Consolidated Field program to update the F0901 table. The system changes the Model/Consolidated field to M for all of the accounts within the business unit.
For more information on, refer to Document 1393249.1 Global Update: Update the Model/ Consolidated Field (R0006QD).
Answer 2: Two account ids cannot be merged into one. You may consider possible workarounds:
Answer 3: After you revise or delete an existing general ledger account or add a new account which updates Account Master (F0901) table, you must run the Refresh Chart of Accounts program (R0909R) to update the Chart of Accounts - Reference File table (F0909). The F0909 table is further used for Chart of Accounts reporting.
The relationship between F0901 and F0909 is that if you add an account with the same object and subsidiary as an existing account, but with a different description or level of detail, the Refresh Chart of Accounts program retains the first occurrence of the object and subsidiary only for the chart of accounts. For example, assume account 3.5005.WEST has a description of Sales - West Virginia. You add account 1.5005.WEST with a description of Sales - Western Region. When you run the Refresh Chart of Accounts program, the system updates F0909 table with object account 5005 and the description Sales - Western Region.
For more information on how to run R0909R report, refer to Document 1435544.1 Refresh Chart of Accounts section.
Answer 4: Please note that if you add a new account and do not run R0909P report subsequently, this has absolutely no repercussions on either Trial Balance rollup or Annual Close. The Refresh Chart of Accounts program (R0909R) is only required to update the F0909 table which is further used for Chart of Accounts reporting. Basically the Chart of Accounts reporting implies a periodic review of your object accounts across all companies and business units, so that you can:
You can achieve this by Online Chart of Accounts (P0909) application or by running Chart of Accounts report (R0909P). The system displays object accounts in ascending order, regardless of business unit or company.
Answer 5: The Build Account Master Word Search Table program (R0901WS) assists in an account search by building the keywords information in the Account Master Word Search table (F0901WS). If you add, change, or delete account information, you should run this program in update mode to refresh the table and ensure that you are searching the most current information. Once F0901WS table is build, you can use the Account Master Word Search program (P0901WS) to locate an account by specifying different keywords. To locate an account, enter a word or string of characters in the Search Word field. The Account Master Word Search program displays a list of all of the accounts containing that word or string of characters. For example, if you enter "accounts payable," the program displays all of the accounts that contain the word "accounts" and all of the accounts that contain the word "payable." For more information on R0901WS and P0901WS application, refer to Account Master Word Search section in Document 1435544.1 Overview of the Chart of Accounts.
Answer 6: To enter account numbers in a format other than the standard EnterpriseOne format for seldom use, you must specify the format that you are using by preceding the account number with a prefix character symbol that identifies the third G/L Account Number format as defined in General Accounting Constants (P0000). If you will like to frequently enter the third G/L Account Number, leave the Symbol to Identify 3rd G/L Account# as Blank. For more information on Account Symbols, refer to Document 1434211.1 Overview of General Accounting Constants (P0000).
Answer 7: A header account is an account with Post Edit Code N or B. Typically header accounts do not contain data into F0911 or F0902 for AA ledger.
Answer 8: The Fixed Asset Postig Edit Code (FPEC) field available in Account Master (F0901) table is not used in EnterpriseOne. There is an existing Enhancement Bug 10858437 requesting to add the functionality to use this field. However this field is currently being used in the World Software. When an account is setup with FPEC = either '1' or '2', the Asset Number must be inputted for the journal. For more information on the functionality added to World Software, you may refer to Bug 10655746.
Answer 9: Since the "." is use in the system to separate the Business Unit, the Object, and the Subsidiary, the "." can not be use as character in Business Unit, Object, or Subsidiary. The use of the "." as character in the Business Unit, Object or Subsidiary, will end up in unpredictable results.
Answer 10: The number of accounts is limited to 99,999,999. This is due to the Account ID (AID) field in F0901 being limited to 8 characters. Please refer to Document 1506485.1 for additional information.
Answer 11: The Account description field (DL01) in P0901 is of 30 characters. Due to the indentation required for level of detail (LOD), description for LOD 9 object account is indented by 9 characters and only 21 characters will be displayed. This is a known issue and is functioning as per designed.
Answer 12: This is due to GMFMOD field updated as NULL instead of a <blank> space in F0901 for those missing account numbers.
Answer 1: The grid interface of Accounts by Business Unit (P0901) application form allows you to import the account information from an excel sheet.
You can access the Account by Business Unit form (P0901) in following ways:
Answer 2: Oracle Software Support never recommends using programs like SQL to make direct updates to data within a table. Proceed with caution and use this option at your own risk. Always have a backup prior to making any type of table change. For information on setting up Chart of Accounts, refer to Document 1435544.1 Overview of Chart of Accounts (P0901).
Answer 3: You setup Account Separator Character to divide the business unit, object and subsidiary elements in the General Accounting Constants (P0000) application. Consider the following guidelines while setting up Account Separator Character:
Answer 4: It is strongly recommended not to skip levels of detail when you assign a level of detail to an account. You assign a level of detail (LOD) to each account to control how amounts are rolled up, or summarized into a balance for reporting purposes. Nonsequential levels of detail may cause summarization errors in financial reports.
Answer 1: Whenever possible, avoid changing the Subledger Posting Edit Code on an account as this change requires direct updates to the data within the F0911 and/or F0902 tables using SQL. These type of direct updates to general ledger data are not recommended or supported by Oracle Software Support. When it is required to modify the posting edit code on an account from 'L' to 'S' to reduce the size of F0902 table, consider the following:
For more information on similar examples, refer to the Modifying Subledger Posting Edit Code (PEC) section in Document 1440893.1 Overview of the Use of Subledgers within General Accounting.
Answer 2: You can revise an account or multiple accounts using following forms:
Answer 3: You cannot delete an account that has a balance in the F0911 or F0902 tables, irrespective of the value of Account Posting Edit Code (PEC). Alternatively, you can delete accounts that do not contain transactions by running the Delete Account Master Records program (R09814). For more details, on what master tables does this report search before deletion, refer to Document 1404783.1 Overview of Delete Account Master Records Program (R09814).
Answer 4: Following are the various Global Updates program available for Chart of Accounts:
Program Name | Description | KM Document |
---|---|---|
Changing a Business Unit on Multiple Accounts (P09812) | You can change the business unit portion of the account number on many accounts at once by globally changing the business units. For example, you can change business unit 91009 to business unit 910092 for all object and object.subsidiary accounts. | Document 1390947.1 |
Changing Accounts By Object Account (P09803) | You can globally change multiple object account numbers. For example, you can change object account 1101 to 1121 across all business units in company 91009. | Document 1390947.1 |
Changing Accounts By Subsidiary (P09805) | You can globally change a subsidiary for multiple accounts. For example, you might change the subsidiary portion of account 1110.BEAR i.e. BEAR to 2220 for data entry efficiency. | Document 1390947.1 |
Update BU.Obj.Sub to Journal Entry program (R09806) | After you change business units, object account numbers, or subsidiaries, you must update the F0911 and F0902 tables with the revised information by running the Update BU.Obj.Sub to Journal Entry program (R09806). | Document 1390947.1 |
Change Account Information (R09813) | Change Account information such as account description or posting edit code for several accounts at one time. | Document 664713.1 |
Answer 5: You can set the Security processing options for the Review and Revise Accounts program (P0901) to prevent the object and subsidiary fields from being changed if an account has a balance in the F0911 or F0902 table. If no transactions or balances exist for the account, you can change the object and subsidiary, regardless of the setting of the Security processing options.
Security Tab
Enter a value of '1' in the corresponding field to protect the value of field(s) which contain the Legal Account information.
Answer 6: This error can occur if the object number entered is too long or using an invalid format for the mode of entry. Please check the the Account Flex Format Setup application (P0907) and review the length of Object Account Field being setup. For more information on setting up Flex Accounting, refer to Document 1435544.1.
Answer 7: The Taxable Account (TXGL) field was added in Account Master (F0901) table as an enhancement Bug 12486363 starting with 8.9 EnterpriseOne release. The GL Account Taxable flag indicates whether a particular account is taxable or not. When the option is turned on at the Account Master level, the account is taxable. Per the current functionality, there could be two valid values for Taxable Account (TXGL) field:
The situation with accounts having Taxable Account (TXGL) field blank may happen for the migrated data as no such option existed prior to the 8.9 release. So when copying an account from a migrated account with Taxable Flag already as Blank, the F0901 Taxable Flag will obviously be updated as Blank. On the other hand, the creation of new accounts will always update the value of Taxable Account to '0', if the check box is not selected.
Answer 8: There is not a functionality available to make the address book a required field for an specific account in the system. The programs like the Journal Entry (P0911) do not validate if there is or isn't an address book records enter for certain account, like it does with the post edit code for subledger type
Answer 9: If the object and subsidiary fields are blank than the account must have a non-posting edit code associated with it. It is recommended to enter a valid object or valid subsidiary number (allowing this account to have any edit code). If the object and subsidiary fields need to be blank, enter a valid NON-posting edit code such as an "N" for Non-posting or "I" for and Inactive account.
Answer 1: The behaviour of Account Category Codes varies from one release to another as follows:
Xe - 8.9
8.10
8.11 and later releases
Answer 2: The Account Master Report (R09205P) will always capture category codes ranging only from 1 through 23. Its recommended to use the following reports to determine if the appropriate accounts are associated with the appropriate category reporting codes:
For more information on how to run these reports, refer to Document 1435544.1 Reviewing the Chart of Accounts section.
Answer 3: While setting up a new account or modifying an existing account, if you are planning to setup Account Category Codes 01 - 43 as blank, it will be required to add a blank value in the respective Category Code UDC with value of '.' in the Description field. For instance, for Account Category Code 25, setup a blank value of '.' in the Description field in the UDC 09/25. Since UDC values are stored in cache, it will be required to clear the cache to experience the effect.
Answer 1: The Account Flex Format (P0907) program will allow changes to the existing account structure but currently there is no method of updating the existing chart of accounts in F0901 table and the corresponding transactions in order to align with the new account structure. Changing the structure after transactions have been entered will create discrepancies to the existing records and cause multiple errors throughout the software. The only workaround is to create a custom program and change the account structure after identifying all the affected tables.
Answer 2: The Account Flex Format (P0907) program allows user to define multiple segments for the Business Unit, Object and Subsidiary fields. For instance, you may setup two segments for the Business Unit, where one one of the segments appear before Object Account and the other after Subsidiary.
This kind of format is supported in flex accounting as long as the total length including account separating characters is less than or equal to 28.
Answer 3: No. It is not possible to have blank values of Object Account or Subsidiary with an account structure defined as BU.OBJ.SUB.BU. Lets take an example to understand this:
The system throws an error since the long account numbers 000050..001.P0001 and 00050.1105..P0001 are incorrect as the intermediate segments are blank. While using the long account number only the last segment is allowed as blank. Hence for an account structure like BU.OBJ.SUB.BU, when using the long account number, object and subsidiary should not be left as blank.
Answer 4: The total length including account separating characters should be less than or equal to 28.
Answer 5: Per current design, the Data Dictionary display rule set for Business Unit Data Dictionary Item (MCU) is *RAB (Right Adjust Blank Fill). It implies that the Business unit field will display right aligned. In case, Account Flex setup is changed from the default value i..e. MCU = 12, OBJ = 4, and SUB = 8, it will be considered as Flex Accounting used and the Validate Account Number Business Function (XX0901) will concatenate MCU, OBJ and SUB and make Account Number (ANI) field as left aligned and will ignore the Data Dictionary display rule. For more information on Flex Accounting validation, refer to Document 1372342.1 XX0901 - Business Function Detail Information.
Answer 1: Please note that the Work with Accounts (P0901/W0901H) application is based on F0901 table whereas the language translations having alternate descriptions are stored in the F0901D table. The non-english description is visible in P0911, P09200 and other applications and reports which use alternate description from F0901D but not P0901 which reads account description from F0901. Hence this is functioning as designed.
An Enhancement Bug 17385639 has been entered to enhance the P0901 application design by adding an additional description field in order to show the translated account description as setup in the Account Translation (F0901D) table.
Answer 2: If the Account Description (F0901) for the copied account has been changed, in that case the corresponding Translational Information (F0901D) needs to be changed manually.
Answer 3: Currently, there is no such feature to upload directly to the Account translation (F0901D) table. Hence, it need to be updated via P0901 application only. As a workaround, you may consider setting up a model business unit with a set of chart of accounts. The translation will need to be updated together. When a new BU needs to be created, you may use the Copy feature in Work with Business Units (P0006) application to copy the range of accounts from the model BU to the new BU. In this case, all the accounts with the translation in F0901D will be created together.