on 12-19-2008 6:59 AM
Hi All,
How to validate or block user to change the WBS code after WBS has been release, in order to minimize error in the system.
Cheers,
Nies
Edited by: Nies on Dec 19, 2008 8:04 AM
Hi,
This can be achieved by using User Status.
You have to forbid Business Process '' Change WBS Number''
Regards,
Amit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
In transaction OK02 creat a user status profile ZTEST
In the same profile create user status WREL - WBS released
select object type as WBS / Project Definition
Double click on created user status WREL
Here u can see various system status
select change wbs as forebidden
select Release as set
means as u release WBS the status will be active and will disallow change number.
Rgds
1st . But the project definition still can be change
Not much idea how to achieve the same with user status.
2nd. How can we block WBS / project definition be changed when the status still created.
For the WBS is if you have ticked initial status in OKG2 for your first user status and if you have forbid the 'Change WBS number' business txn for that user status, than it will surely not allow to change WBS no. when WBS stats is CRTD. the field will become grey.
For the P.D. not much idea. Let wait for others.
Regards
Nitin
1st . But the project definition still can be change
Not much idea how to achieve the same with user status.
You can also do it using user status, the same way you did to block WBS element from being changed after released
But this time in OK02 you specify the object type as Project Definition (i.e. you'll have 2 status profiles; for WBS Element and Project Definition)
These status profiles need to be attached to Project Definition and WBS element accordingly (in trx OPSA)
User | Count |
---|---|
95 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.