Frequently Asked Questions about Properties

Why are my property values different for the same node between a list and a hierarchy viewpoint?

List and hierarchy viewpoints differ in their data chains:

  • List viewpoints reference a list node set, which references one or more node types.
  • Hierarchy viewpoints reference a hierarchy node set (which includes the top nodes for the viewpoints), which references a hierarchy set, which then references one or more node types (see Understanding Viewpoints).

For hierarchy viewpoints, the hierarchy set contains the Parent and Child relationships as well as the relationship level properties. Because list viewpoints do not reference a hierarchy set, it does not provide positional information or relationship level property information about a node.

Therefore, a list viewpoint and a hierarchy viewpoint will display different property values for the same node in these instances:

  • The node level property is inherited.
  • The node level property is derived based on positional information, such as Parents, Ancestors, or Siblings.

A list viewpoint and a hierarchy viewpoint will display the same property values for the same node in these instances:

  • The node level property is defined.
  • The node level property is not inherited.
  • The node level property is not derived based on positional information, such as Parents, Ancestors, or Siblings.

Tip:

Using properties with Derived and Stored default values enable you to use an expression to calculate values that include positional logic and then store those values so that they can be referenced from a list viewpoint as defined values. See Derived and Stored Properties.

Consideration for Oracle Financials Cloud General Ledger and Oracle E-Business Suite General Ledger Exports

Because Oracle Financials Cloud General Ledger and E-Business Suite General Ledger applications export segment values from the list viewpoint and segment tree values from hierarchy viewpoints, it is important that you do not use any properties with a Derived default type with positional logic. Use Derived and Stored default type properties instead.

Note:

If you switch a property from Derived to Derived and Stored, you must use requests or loads to populate the values so that they become defined.