Understanding Parent/Child Relationships and Account Group Codes
When you set up GL accounts in the JD Edwards EnterpriseOne system, you can assign a level of detail for the accounts. You use the levels to specify a parent/child relationship between accounts. The system enables you to skip numerical levels between a parent account and child account. For example, you might set up an account at a level 4 that is the child of an account at a level 2.
The files that you submit for SPED accounting must show the parent/child relationships between accounts. However, the relationships can contain no gaps in the levels between a parent and child account. For example, an account at a level 4 cannot be a child of a level 2 parent account. Instead, an account at a level 4 must have a parent account at a level 3.
For SPED accounting, the relationships between the parent and child accounts are referred to as the agglutination level. To report on your accounts, you generate data that includes the accounts, the agglutination level, and an agglutination code. When you run the Block J - Opening Balance Sheet and Income Statement program (R76B985), the system assigns to the accounts an agglutination level that is based on the level of detail that you set up for your accounts. The system logic assigns the agglutination levels with no gaps, as required by the SPED reporting requirements.
When you set up accounts for reporting, you associate an account group type code to the accounts that you report. You must assign an account group type code to every account to include in the reports. The system uses the highest level account that is assigned a group code as the parent for all other accounts in the group, and uses the OBJ.SUB of the parent account as the agglutination code.
The first level of each account group must be unique. For example, only one account that is assigned an account group code of 01 (assets) can be a first level, or parent, account.
If you have more than one account at the top level in your chart of accounts and assign them the same account group code, the system does not accurately report your data. For example, if you have two accounts that are at a detail level of 1 in your chart of accounts, and you assign both of those accounts the same account group code, your data is not accurately reported.
The system uses the posting edit code to determine which child accounts to include in the totals for each account group type. The system uses the posting edit code of N to determine which accounts to include (summarize). Accounts that have a posting edit code other than N are considered to be analytical accounts and are not included in the SPED reporting.
If you use a posting edit code of N to prevent transactions from posting to an account, you must change the code before you process accounts for SPED reporting or the account will be included for reporting.
This chart shows an example of how the system determines the accounts to include for SPED accounting. The accounts in the non-colored fields appear in block I. The accounts in the colored fields appear in block J.
