STS: Why data can't be locked when status is sent to approval.
I'd like to ask about STS, I have a problem on it. I'm working in IP.
Why data can't be locked though the status is already in "send to approval" ?
I've setup data slice under the corresponding cube based on exit class: CL_UPS_LOCK_DATASLICE.
Is it because I've yet to assign R_STS_PT authorization to the planner ? So when I'm opening the data using planner user id, data is still not locked yet.
Could you kindly help me to resolve this problem please ?
Thanks a lot all,
Have a good day,
I found that the exit class does work.
You define the exit class in the data slice area of the planning modeller. You use those characteristics in the data slice definition that you will be restricting on in the STS customising header characteristics.
Then I had 5 users set up (basis) one was super user having the authorisation R_STS_SUP and R_STS_PT.
The rest 4 users were created having the authorisation object R_STS_PT.
I included the users in a basic cost centre dummy hierarchy and found that when the lower levels submit for approval, the data is locked for them, of course they can retrieve data but an email is automatically sent to their superiors when this is done.
Good luck to you.