Subscribe Node Types One-to-Many — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Subscribe Node Types One-to-Many

edited Apr 11, 2025 3:45PM in Enterprise Data Management 5 comments

The background: I have a flat dimension where I import accounts from a (non-Oracle) GL. When accounts are added, I need to map them to a consolidated chart of accounts in a map hierarchy. The map hierarchy is consists of the chart of accounts with one extra layer of depth, GL accounts from the flat import dimension. This works well when the chart of accounts hierarchy consists of a single node type.

Our planning and consolidation tools, however, have different levels of depth. Our planning tool needs to break certain balance sheet summary amounts into more detail (i.e. it needs an intermediate parent that the consolidations tool does not). Additionally, our planning tool needs to map our income statement to a lower level of total detail (i.e. its deepest level is often—not always—1 level deeper than the consolidations hierarchy). We are required to maintain all consolidated accounts in a single master hierarchy. We've managed to build our master, planning, and consolidations hierarchy sets and subscriptions to be able

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!