Using Dependent Value set in COA

Dependent segments... These are probably an indication of over complication. They can be laborious to maintain if cross-segment validation is used. It also complicates mass allocations & consolidations. Meaningful account balances are not visible through online inquiry.

You can use dependent account segments when you want a "context-sensitive" segment, but avoid it if possible. Use the Cross Validation Segment Rules instead, as some functions may not work properly with dependent segments (for example the AHE in ADI).

Dependent segments can help split dimensions that are closely related into segments which you can separately identify, giving you benefits for reporting, use of ranges, and other functions. For example, separating account/subaccount into two segments facilitates setting up descriptive flexfields based on accounts, rather than having to itemize each distinct account/subaccount combination.

If you use a dependent segment, use it to its full extent across as many combinations as possible. For example, if you have a subaccount segment, establish major natural accounts and more detail subaccounts throughout your chart of accounts. Common areas of the chart of accounts for potential subaccount details are in cash accounts and tax liability accounts by taxing authority. If your requirement is merely to capture transactions for each of five cash accounts within natural account 1100 and there is no need for more detail in other areas of the chart, it would bepreferable to establish a separate natural account for each cash account rather than a separate segment for only cash account detail.

In GL there are two other issues to consider. You cannot setup parents over dependent segments, since the dependent segment values have no meaning themselves. If you have a true need fordependent segments, the inability to setup parents is generally not a constraint. You can run reports and allocations based on one dependent segment value or all in total (using the provided pseudo parent T), just not a subset of the total. The other issue in GL relates to consolidations.Since consolidations are based on rules for single segments rather than combinations for segments, you cannot easily map different groups of dependent segment values into different consolidated values. For example, you cannot easily map the following account/subaccount combinations:Subsidiary Consolidated1100-001 + 1100-002 1100-0011100-004 + 1100-009 1100-002

You can drop subsidiary subaccount detail by dropping subaccount completely if the consolidated book does not have a subaccount segment, or by defaulting the subaccount during consolidation to a single value such as always 001. You can also develop accounting flexfield rules mapping detail subsidiary ranges to one consolidated accounting flexfield, however this is maintenance-intensive and should be avoided if possible.

The FA mass additions process selects AP invoice lines to add to FA based on several criteria, including the account segment. If you have account/subaccount, ensure all subaccounts for an

account are FA or not FA. If an account number has some subaccounts that are FA and some that are not FA, FA mass additions will add all of them to FA.

Independent Segments : For Accounting Key Flexfields, use independent segments. Do not use the Dependent validation type. It complicates parent/child hierarchies and limits the ability to use parent values with reporting and mass allocation journal entries.Dependent Segments : Dependent segments separate items that are closely related into individually identifiable segments .Account/subaccount is the most common use for independent/dependent segments (account is the major classification and subaccount provides more detail within the account).With dependent segments, you must set up each combination of independent/dependent values. You do not need to set up cross-validation rules for independent/ dependent combinations since you set up each combination individually. Sometimes setting up dependent segments is preferable to maintaining extensive validation rules for combinations of two segments which have many values with no ranges or logic for the valid combinations.Dependent segments limit the values that appear on lists to the dependent values of the independent segment chosen.