Hierarchies - Drill Up/Down doesn't work

[Former Member]

Hello!

May be I am doing this incorrectly. I've followed Moya Watson's work around ([https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4155b345-0a01-0010-ac9f-b3b2c34e993c|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4155b345-0a01-0010-ac9f-b3b2c34e993c]) to enable drill down/up for hierarchies in VC.

When I run the iView, I see my tree's root expanded with 10 child nodes (all with a '+' infront, meaning they can be expanded). When I click on "Drill Up" when the root is selected, all nodes collapse as expected; "Drill Down" also works by expanding the root node and showing the 10 child nodes. However, this functionality doesn't work for any of the 10 child nodes. When any of the 10 nodes is selected and either "Drill Down" or "Drill Up" is clicked, the table refreshes but there is no change in the table (all nodes remain as they were before).

So, the buttons only work for the top most node. Does anyone know what I could have done incorrectly? When this is run via WAD template, it works as expected.

Thank you for your time,

Kiran

Edited by: Kiran on Feb 7, 2008 2:33 PM

[Former Member]

An update.

After some testing, I found that the problem drill up/down are working for only node level 1 <-> 2, was because the part in the web api formula that's related to "Filtering the hierarchy" isn't working.

Here's the code:

'FILTER_NODE_IOBJNM=0COSTCENTER;FILTER_VALUE='&&#ID[ACCCG]@Cost_Center_key&';FILTER_COLLAPSE= ;FILTER_IOBJNM=0COSTCENTER;CMD_1=CMD%3DDRILL_TO_LEVEL%26LEVEL%3D2%26IOBJNM%3D0COSTCENTER%26DATA_PROVIDER%3DDP;'

I started off from scratch and tried to just implement filtering on hierarchies and it doesn't work. I made sure that "Activate Hierarchy" is set on the characteristic for the query.

Any pointers,

Kiran

[Former Member]

Kiran,

I've encountered the same problem. I can only drill down till the 1st level. Have you found a solution for this?

Regards,

Sameer

[Former Member]

Sameer,

I think found the error. The error was that in the mapping, I had the WEBAPI command filled and also had the default mapping left out. I removed the default mapping (like Org Unit = @Organizational_Unit). I am not certain if that was the problem, but most likely it is.

Regards,

Kiran