Skip to Content
author's profile photo Former Member
Former Member

__EMPTY_SELECTION__ Lock Integrated Planning

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.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Jan 16, 2012 at 04:22 PM

    Hi Karim,

    __EMPTY_SELECTION__ indicates that the selection table used for the enqueue request is empty, i.e. this lock request locks the whole cube. As a result this lock overlaps with all other enqueue requests for this real-time InfoCube.

    What to do:

    1 If 'Plant' is the only lock relevant characteristic, maintain 'Plant' in as lock relevant in transaction RSPLSE, i.e. 'Plant' is contained in the 'right hand' table (the lock relevant characteristics) on the second tab. Observe, that the default is that all InfoCube characteristics are lock relevant, i.e. contained in the right hand table. Maybe you made all characteristics except 'Plant' lock relevant.

    2. In the filter of the input-ready query use the restrictions for 'Plant', e.g. a single value. You may use a variable for this. It is important that the restriction is in the filter, not in the default values. The query filter used to set the locks.

    3. The same is true for planning functions.

    Using this modeling you will get no lock conflicts.

    Regards,

    Gregor

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.