Required step before changing locking logic in planning area to Live Cache lock

[sourabh_jain66]

Hi Experts,

In our company we are using common planning area and book for multiple time jones, and because of this we are encountering frequent locking conflicts. Currently we are using detailed locking in place in our planning area. CVCs in each time jone are different, so the idea of using common planning area and books.

After reading lots of threads and SAP help information, i could reach on a conclusion that changing locking logic to live cache lock can resolve our issue.

I need your help on below points;

1) What all precautionary steps, i need to take before changing locking logic in planning area to live cache lock.

2) Is it possible somehow to change locking logic in planning area without deactivating it?

3) Is it required to take data back up before changing locking logic.

4) Other points which i need to take care of before making this change.

Your help is highly appreciated.

Regards

Sourabh

[Former Member · Accepted solution]

Hi Sourabh,

It is great to give suggestions to the experts.

Some users will have Super User access and they will be doing changes.

Get the process chains logs when you got locking issues and check for which user it got locked. Then check the Authorizations.

when you are doing changes at Planning area level it is better to have a backup. ALso suggest other teams and Basis before doing the changes. So that data transfers can be blocked at that time.

Thanks,

Bala.

[sourabh_jain66 · Accepted solution]

Hi Bala,

Thanks for your answer, you are the expert here and i am on the receiving side, so the term expert is subjective .

So, yes there are some user having authorizations to make changes in any of the region, but the issue comes when somebody doesn't have authorization for making change in one specific region and background job gets failed because of locking from that user.

This is happening very frequently.

We have detailed locking in place, can you think of anything which might be the cause of this issue.

Do let me know if you need some more details.

Rgds

Sourabh

[Former Member · Accepted solution]

Hi Sourabh,

Right now I am not sure of other ideas, may be our experts can suggest you..

Thanks,

Bala.

[Former Member · Accepted solution]

Hi Sourabh,

I think in ur PA, there is check box ticked for Detailed lock and Keyfigure specific lock.

But ideally, as per my knowledge, we need to have checkbox ticked for "Activate Livecache lock" and "key figure specific lock".

Using Activate livecache lock will help in avoiding the issues in ur case. If this is checked, if any CVC is being accessed by a BG job in livecache, the same CVC cannot be accessed by any user.

Try this scenario in ur sandbox if you have.

Thanks,

Raj

[sourabh_jain66 · Accepted solution]

Hi Experts,

Can somebody please help me understand this behavior, after putting lot of effort analyzing the system, i am still clueless on this.

Please help.

Rgds

Sourabh

[jagannadhb · Accepted solution]

Hi Sourabh,

We have a similar situation in our project, where a code is written to lock/unlock Planning area only for a particular selection of Users.

So if one Timezone is starting their jobs, they just need to run this Job for their particular user group (created in SU01).

Probably your ABAPer can help you.

Here BAPI_USER_LOCK was used. For further information on this, you can see this thread

Regards

JB

[Former Member · Accepted solution]

Hi Sourabh,

As JB rightly said, try developing a custom program which will kickout the user before the planning starts in your process chain.

Most of the projects does this. This could be one solution to avoid user lock issues.

As you said, the planning area is same for all other markets as well, you can speak to your developer and design the solution.

Thanks,

Raj

[sourabh_jain66 · Accepted solution]

Hi JB,

This is one possible solution, but there are global planners who sits in Europe region and adjust the plan for whole globe.

In case i lock all the users from other regions using this program this will not alow central planners as well to work.

Is there any other workaround / suggestion you can think of in order to allow central planners to keep working and background job also doesn't fail, i might sound silly but that's what we are trying to achieve.

Your help here is really appreciated.

Rgds

Sourabh

[jagannadhb · Accepted solution]

Hi Sourabh

In Our project, we have a LOCK/UNLOCK program with selections of which user groups to lock/unlock. The user groups can be maintained in SU01. Also we have a table where we can maintain exceptions.

Your ABAPer can help you.

Regards,

JB