Skip to Content
0
Former Member
Jan 16, 2012 at 01:22 PM

__EMPTY_SELECTION__ Lock Integrated Planning

148 Views

Hi all.

I'm running an input-ready query through a InfoCube. Actual for Plant and Calmonth.

So far so good. I managed to get the query input ready and it saves back to the cube alright. I haven't used any planning functions or filters within IP - just created a aggregation level on the InfoCube and the wrote the query on top of that.

Next problem is that I'm trying to manage the locking conflicts. I will probably have 10 or more people that possibly could be running this query at the same time (who are all responsible for different Plant). So I figured I could set Plant as the lock characteristic on my planning cube, because we will only have 1 person filling in numbers for each Plant.

After a lot of trial and error I get this __EMPTY_SELECTION__ as a locking reason. I can't get this to work.

I'm using Plant, Material, Calmonth in my query. Along with Amount as key figure.

I have tried alternating the lock characteristics to different ones, but with no luck.

Maybe, I need to use in my query, the variable in plant.

Please help.

Thanks.