Previous  Next          Contents  Index  Navigation  Glossary  Library

Parent and Child Values and Rollup Groups

Attention: Only Oracle General Ledger and Oracle Public Sector General Ledger use these features, and only with the Accounting Flexfield.

Note that parent and child value sets have a relationship different from the relationship between independent and dependent values.

See: Designing Your Accounting Flexfield Planning Your Summary Accounts.

Since you can enter any value in a value set with a validation type of None, you cannot create parent-child relationships for segments that use these non-validated value sets. In addition, you cannot create parent-child relationships for dependent value sets.

Parent Value

A parent value is a value that has one or more child values associated with it. A parent value can be assigned to a rollup group. You create parent-child relationships by defining a range of child values that belong to a parent value. You can use parent-child relationships for reporting and other application purposes.

Child Value

A child value is a value that lies in a range of values belonging to a parent value. A child value can belong to more than one parent value. A child value is not a dependent value; that is, the actual value of the child does not depend on the value of another segment. You create parent-child relationships by defining a range of child values that belong to a parent value.

Rollup Group

A rollup group is a collection of parent values. A value cannot belong to a rollup group unless it is a parent value that has child values. Parent values and child values belong to the same value set, which is then attached to a key flexfield segment.

A rollup group allows you to group related parent values for creating summary templates. Given a summary template, General Ledger creates summary and detail reports using all parent values assigned to that rollup group.

You define rollup groups using the Rollup Groups window before you define your key segment values. See: Then, you assign your parent values to the rollup groups when you define the parent values.

See: Rollup Groups Window Segment Values Window

Rollup groups are separate from parent-child relationships. You can assign any parent value to a given rollup group, regardless of that parent value's place in a value hierarchy you might create.

Creating Parent-Child relationships and Rollup Groups

Oracle Applications provides you with windows to define relationships between parent and child values. You create these relationships by defining a parent value and giving it a range of values that become the parent value's children.

You can also use the Account Hierarchy Editor to define new rollup groups then graphically create parent-child relationships and assign parent values to rollup groups.

See: Using Account Hierarchy Editor

You can see the relationship between independent and dependent value sets and parent values and child values in the following diagram:

Oracle Applications stores parent-child relationship information in the FND_FLEX_VALUES and FND_FLEX_VALUE_HIERARCHIES tables.

Parent-Child relationships Using Validation Tables

You can create parent-child relationships for any independent value set used by a key flexfield segment. If your value set is a Table validation type value set, you can also use the Define Segment Values form to create parent values for the values in your table. You cannot create new child values using this form, however (you must create your own application form to maintain your validation table). Oracle Applications stores your parent values for you in the Oracle Application Object Library table and does not add your new parent values to your validation table. In the previous diagram, the parent values would reside in the Object Library table, and the child values would reside in your validation table, though all the values are part of the same value set.

Warning: You should make sure that you never enter parent values in this form that are already contained as values in your validation table, however. If you do, you can cause data corruption, since both values appear in the list of values on that segment, but you can never choose between one of the two values from the list. If that value is already contained in your flexfield combinations data, you can also cause problems since you have two potential descriptions for the same value.

See Also

Overview of Values and Value Sets

Rollup Groups Window

Value Set Windows

Validation Table Information Window

Segment Values Window

Defining Segment Values


         Previous  Next          Contents  Index  Navigation  Glossary  Library