Time Dependent Hierarchy Not Working as expected

[Former Member]

Hi,

I have loaded a Time Dependent hierarchy (Time Dependent Hierarchy Structure with Use Temporal Join checked). I have transaction data for Jan, Feb and March 2013. The Leaf nodes have different parents in each of these months. There is transaction data in all three months.

When I execute my report for range Jan-Mar (date range 01.01.2013 - 31.03.2013), I expect to see 3 assignments of the leaves, as per the time range. However, I see all of the transactions of the 3 months, grouped under the latest relationship.

I have tried changing the Key Date of the Hierarchy in Query Designer, but this doesn't help either. I have used a replacement path variable here, to get fed from the CALDAY input variable.

Any assistance to get expected result is appreciated.

[yasemin_kilinc · Accepted solution]

Hi,

we had the same issue, but I could not find any way to show that. Variable does not work, since it calculates the value before the report is shown. The only way is assigning the key date of the hierarchy a variable with manuel input so that user can enter the key date and show the results acordingly.

If you find any alternative solution please let me know.

Regards

Yasemin...

[Former Member · Accepted solution]

Thanks for your response Yasemin. If we look at the Time Dependent Hierarchy example that is given on the help.sap link (http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a6702e07211d2acb80000e829fbfe/frameset.htm) the example provided appears to be to provide the solution. However, it is not clear where "maintenance of the key date derivation type (RSTHJTMAINT)" is... as what we need is for the key date to be picked up based on the transaction date, not one of the ranges.

[yasemin_kilinc · Accepted solution]

Hi Sowmya,

It is so nice you are one step ahead of me. I read the document from your link. And tried an example. In RSTHJTMAINT transaction I created a derivation type. When I use the characteristic with hierarchy structure temporal join checked, in the query designer it asks for the "from data, derivation type" there you can select the derivation type you have created. I think for your case, you need to create a derivation type using basis time characteristic as 0CALDAY (because your data changes everyday, I guess). As I read in documents these are all valid for SAP Netveawer 7.0.

Please let me know if it works or not.

Regards

Yasemin...

[Former Member · Accepted solution]

Hey Yasemin,

The Time dependency with Temporal join worked. The issue is that this adds a "Validity Date" column along with the transaction data. This is what allows the Temporal Join of the data. Ruins the readability, but gives the relationship. Correct, the steps you've listed above are right. That is how it works. 🙂