Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.activeviam.com/llms.txt

Use this file to discover all available pages before exploring further.

The LEGAL_ENTITY_HIERARCHY table contains the multi-level legal entity organizational structure.
Column NameTypeNot NullCube FieldDescription
AS_OF_DATEDATEYTimestamp (at close of business) for the data.
LEGAL_ENTITYSTRINGYLeaf node of the book hierarchy. This matches the last non-_DATAMEMBER_ node in levels 1 - 15.
HIERARCHY_LEVEL1STRINGLevel 1Node at level 1 of the book hierarchy.
HIERARCHY_LEVEL2STRINGLevel 2Node at level 2 of the book hierarchy.
HIERARCHY_LEVEL3STRINGLevel 3Node at level 3 of the book hierarchy.
HIERARCHY_LEVEL4STRINGLevel 4Node at level 4 of the book hierarchy.
HIERARCHY_LEVEL5STRINGLevel 5Node at level 5 of the book hierarchy.

Unique Key

Columns
AS_OF_DATE
LEGAL_ENTITY

Incoming Joins

Source TableSource ColumnsTarget Columns
TRADE_MAPPINGAS_OF_DATE
LEGAL_ENTITY
AS_OF_DATE
LEGAL_ENTITY

Populating From a ParentChild Table

Instead of creating and populating the LEGAL_ENTITY_HIERARCHY table directly, you can create a LEGAL_ENTITY_PARENT_CHILD table to store the parent-child relationships.
Column NameTypeNot NullCube FieldDescription
NAMESTRINGYChild in the parent-child relationship.
PARENTSTRINGParent in the parent-child relationship. Null means the child is a root node.
DATEDATEYTimestamp (at close of business) for the data.
With this table and the following SQL script, you can create a series of intermediate views to populate the multiple levels of the LEGAL_ENTITY_HIERARCHY table:
With this table and the SQL script included in the online documentation, you can create a series of intermediate views to populate the multiple levels of the LEGAL_ENTITY_HIERARCHY table.
For performance reasons, views may impact query and aggregation performance.Injecting the results of the final constructed view into a table can improve query performance. The tradeoff is that this final table will need to be manually kept up to date if the underlying parent-child tables are updated.