‎2010 Mar 05 8:45 AM
Hello Experts,
When i am using BAPI_PR_CHANGE, to change PR . Since i have many number of PRs to be changed in , i am running the program in background . Issue now is that i am getting already PR is been changed (processed) by User(myself), so changes cannot be made and stooping the process of change. I am using BAPI_TRANSACTION_COMMIT with WAIT also. but i coukd not change the PR in background. How can i over come this problem? How the lock entries shall be removed fast so that next PR is changed.
Please help me out experts.
Thanks in advance
‎2010 Mar 05 9:08 AM
Hi,
What you can do is through yur program ENQUEUE the pr then used bapi (along with commit)and then DEQUEUE the PR.
This way yur locking problem will not come.
Hope it helps.
Regards
Hiren K.Chitalia
‎2010 Mar 05 12:04 PM
Anyway BAPI is going to take care of locking and unlocking as i am using bapi commit. Is there any need of me externally use enqeue and deqeue .
‎2010 Mar 05 9:08 AM
Hi,
that's really weird. You get a lock only for particular PR, so when you process multiple PRs you shouldn't have any problems. What exactly do you do with PRs? BTW you can see current lock in SM12.
Cheers
‎2010 Mar 05 11:56 AM
Its not the problem with particular PR, Only first PR is being changed succesfully, from second PR , thought it get unreleased, its not able to change, saying user(myself) already processing PR.
‎2010 Mar 05 1:25 PM
Kiran, one bad question, but like it happens at times, have you left one of the PRs open in any of your sessions
‎2010 Mar 05 1:49 PM
No i did not do that, i am out of all PR transactions, before executing the back ground program
‎2010 Mar 05 8:11 PM
Hi,
do you run it in test run? If yes, then have you checked Note 1333005?
Cheers
‎2010 Mar 06 4:27 AM
i am not test running it. i used in the program to change PR items
‎2010 Mar 06 3:16 PM
One bad question. Are you refreshing all the internal tables properly inside the loop? Can you send us your code?
Regards,
Ganga