In order to start planning for the next quarter, administrator needs to prepare the box/data, so users can start planning or in closing period administrator/business user need to prepare the data submitted to present to management. Administrator/Business user need to massage the data, and in order to do that, they need to lock the data to refrain from user access the data.
If user’s accessing data means they reserve data ( impacting to conflicting locking ), data is not valid. But bear in mind, data locking only happens to users not to administrator/business user. Usually before administrator do data locking, administrators will inform to user by e-mail about planning/forecasting unavailability beforehand. But let say, there are still users planning/forecasting/reserving data though they’ve already been informed in advance, system will keep user not able to submit their changed data.
To make it, I use characteristic relationship. Both Characteristic Relationship and Data Slice are able to make planning layout not input-ready. The different is if user is in the midst editing data, and we activate data slice. Users are still able to save/submit the data, the planning layout will not be input-ready, if users refresh the planning layout. But for Characteristic Relationship will refrain system from user submit the data, though users will see the planning layout as well after they refresh the planning layout, but at least they can’t save/submit their data. You can see the data validation done by characteristic relationship in the picture above ( pict: data validation).
Administrator Locking Maintenance
There is a layout for administrator/business user to maintain the data locking. At here, I set that administrator is able to lock for all data or based on particular selection data. The configuration in term of what Company Code or LoB or AOO to be locked are stored in ODS, I use planning function in order for user enable to store it (see left picture). The beauty is when administrator activate the locking, it doesn’t only activate the characteristic relationship but it also release the reserved data in t-code rsplse. In the other words, we’re no longer see the user data reserve/lock in t-code rsplse (IP Locking maintenance).
Unreserve user’s data locking
When users do a planning, you’ll see in the t-code rsplse that they’re reserving the data. If you’re opening the same data like what they’re opening at that moment than you’re unable to plan / even you’ll . System will refrain you from planning and sytem will throw out the message ” the data is locked by XXX” . Vividly it’ll be explained in t-code rsplse in tab ‘conflicting locking’ that you’re opening the same data that user’s opening now. With regards to this mater, definitely when administrator is running their fucntions, all data are being reserved by user must be released. We can release it by t-c0de sm12, but it’s not safe, if we grant administrator that t-code. Therefore, this solution use ABAP to replicate what sm12 does to release that lock.
You can use function module: ENQUE_READ and ENQUE_DELETE. The steps are you read first what user is currently locking, than using the derived data, delete the data from lock queue. If in this solution, I can release according to what user select (Line of Bussiness, Company Code, and Area of Operation), than you definitely must check the detail from that locking. What data are currently locked. You can get the detail by using method read_locks of class cl_rspls_enq, by using this method, you’ll know what user’s locking e.g. target version.
Refrain user from planning
If we’ve already activated admin locking than all the planning data are opened by users will not get input-ready. For this one I handle it using characteristic relationship at method check. In the method check, if you go to attribute class, you’ll see e_is_valid, you just assign blank value .
At this solution, the system have luxuries:
- Though admin locking status is in active, but it won’t lock administrator. It’s very important, otherwise administrator won’t be able to run functionalities because of encountering locking.
- When admin locking status is active, user won’t see their planning layout be input-enabled, nevertheless they’re still reserving the data. It looks awkward, but it’s true. Therefore, for user, if they’re encountering not input-enabled caused by admin locking, system will also unreserve data according only to his/her userid.
- System is aware, currently, administrator lock all data or lock according to company code or LoB or Version or Terminal node or etc.
Those 3 points logic are coped in the characteristic relationship.
Messages
Messages are also important at here, otherwise user will yell out when they know that they’re unable to forecast, they think that they’re encountering system error. Therefore, everytime admin lock is in active mode, there will be message saying that admin lock is active, and they’re kindly asked to logoff from system.
Danielnurindra's Blog 