Skip to Content
avatar image
Former Member

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

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

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • Best Answer
    avatar image
    Former Member
    May 20, 2014 at 03:12 AM


    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.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 25, 2014 at 08:30 AM

    Hi Sourabh,

    We can change the locking logic of planning area without bringing it down.

    The samething i have done in SCM 7.0 environment .

    I am not sure about prior version.

    Regards,

    Mukesh Pandey

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 16, 2014 at 01:58 PM

    Hi Sourabh,

    First of all, as per my knowledge, if you are using the same planning area for different time zones, then there must be dedicated CVCs for each region.

    CVCs for APAC region would be different from CVCs for EU region. In this case atleast the planning books or the data views could be different. When a CVC is being accessed by any transaction in livecache, it will lock that CVC and the same CVC will not be available for change for any background process or a user as well.

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

    You better take the backup of the planning area before u deactivate, change and activate the planning area. And create timeseries.

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

    I don't think it is possible. And not suggestible.

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

    Yes, to be on safer side.

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

    Please get in touch with you Basis team to get some pointers. If they have any dependency to restart the livecache or something like that. Not sure though.

    Thanks,

    Rag

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Raj,

      We have done our investigation on this, CVCs for each region are different, no clashes there.

      Yes background jobs are getting failed because of locking, the users belongs to region other then for which background job is running.

      We have detailed lock in place.

      I am not able to understand this behavior, can you please help.

      Do let me know if you need some more details.

      Rgds

      Sourabh