Time Dependent Hierarchy in BPC

Vijay Vyakaranam
What is TDH?
Hierarchy in BPC Parent/Child relationship
which helps aggregation of data
TDH allows users to define hierarchies based
on a time range. The aggregation of data and
rollup behavior will be different based on the
time range
Business Scenarios for TDH
Employee movement frequently occurring
scenario
M&A / Restructuring To break barriers to
entry and/or to make use of certain monetary
benefits companies these days undergo these
events. TDH captures these events effectively
which are especially important for proper
financial consolidations
Business Scenarios for TDH
Customer reclass Based on relationship with
the customer, there may be a need to reclass a
customer from a Small Accounts category to
a Key Accounts category
Product reclass Company reorganization
activity may force a product reclass
Other scenarios as they arise
Business Scenarios for TDH
Especially useful in the planning context, as
business users will have the ability to create
what-if scenarios for rollups and analyze the
results
Prerequisites for TDH
SAP BPC 10, NW 7.30, SP09 and higher
SAP BPC 10, Powered by HANA, NW 7.30,
SP03 and higher
SAP BPC 10, NW 7.31, SP02 and higher
SAP EPM Add-in, SP13 and higher
Configuration of TDH
Simple and straight forward
Only a few steps

Involves both backend (BW) and frontend
(BPC Web Administration)
Once TDH is enabled on the server, all
environments created on this server will be
able to use this functionality

Backend Configuration
Pre-requisite: User should have access to BW
(SPRO, RSA1)
Step 2 Enable TDH in dimension
Step 3 Create new hierarchy version
Key Date in EPM Reports
This is a new feature in reports which shows up in
EPM context
This is NOT a dimension in your model
This enables the user to pick a date which reads
the appropriate hierarchy version
This feature can be used very effectively in the
what-if scenario analyses
Shows up under Options -> Context Options. Can
hide/lock this key date just like a dimension

Security Implications
Data Access Profiles are always defined using
the hierarchy version of current date
At run time, data security is always resolved
with hierarchy version of current date, no
matter what key date is selected in the reports

Security Implications Example
Please share your thoughts!