Hi Manohar,
Yes, you can control that.
Perhaps one of the Packages was running on multiple Org members. BPC decided that it's too many to lock them individually and locked as an interval. Org member(s) for the other Package probably fell inside that interval.
Let's say 1st Package ran on Orgs ABC, ..., KLM and the 2nd Package ran or Org DEF. 1st Package will create a lock on ABC - KLM and 2nd will try locking DEF. This will create a locking conflict.
So, solution would be to make BPC think that 1st lock doesn't have enough members to lock them as interval. For this you have to find out how many members of Org Dimension can be in one Package and make RECLEVEL_NR and INTERVAL_NR at least that big. Then BPC will lock them individually and if 2nd Package runs on different Orgs they won't lock each other.
Just don't make those parameters too big because it will slow the locking down.
Regards,
Gersh