Tuesday, November 10, 2009

Unlocking the Projects on Local from Backend

ometimes developers find the difficulty that when they GET all the projects from the server, some other user locked some of the projects. So the user cannot Lock these projects locally. Here is a few queries by which Projects can be unlocked locally from the Backend
SELECT LOCKED_BY FROM S_PROJECT WHERE ROW_ID='1-3TN-3WVR'
UPDATE S_PROJECT SET LOCKED_BY='1-21JM' WHERE ROW_ID='1-3BX-G32'

LOCKED_BY can be replaced by the ROW_ID of users own User ID and ROW_ID of the Project can be found from the tools. 


To verify you can use the following statement also:
update siebel.s_project set locked_by=(select row_id from siebel.s_user where login='') where row_id='';


http://www.siebeldigest.com/

1 comments:

Rajkumar Raju said...

It doesnt seems like you are unlocking it.. LOCKED_FLG or some flag should be set to N and LOCKED_BY should be set to NULL for unlocking.. What you are actually doing is , swapping the Lock from one user to another user... So LOCK remains as it is.. What say?