on 09-07-2012 6:13 AM
Hi,
Greetings !!!
I'm trying to make the project definition, WBS element and Description of both to be grey out after Release of that element.Through user status I'm able to make WBS grey out but not project definition.
I have also tried it through Field selection but not successful.
Can any one help me to solve this?
With Regards,
Soubhagya Rout
Hello Soubhagya Rout
you can try the following
1. Authority checks
Run CJ20N and check the authorizations it uses.
There is an activity on the PS relevant activities of 45,
which controls the change of project number.
When this authorization is removed, the project definition will be
protected automatically as soon as a project is created.
Please also be aware that for changing the WBS ID, you have to
include activity 045 in all the relevant C_PRPS_* objects.
2. User exit CNEX0002.
There are two options to do this. One is to use customer enhancement
CNEX0002: PS Authorization Check. For more information on how to set
this up, please refer to the documentation in transaction SMOD. You
can also access the information on the SAP Help Library or read
the attached FAQ SAP Note 554415.
Basically you can create an authorization profile which sets field
PROJ-PSPID to display only. This authorization is then assigned to
users.
3: You can mimic the same functionality that was in earlier releases
by using a User Status as defined below.
Create or amend a user status using transaction OK02.
Create a new line entry and set the "Init. Status" flag so that this
status is applied as soon as the Project / WBS is created.
Set the business transaction behind this to disallow "Change WBS
number, Save.
Specify this User Status Profile within the Project Profiles of your
projects. When you now create a project the WBS number fields are
open for input until you press enter or save the project.
To change the WBS number you then need to remove the user status and
reply when finished. Being a User Status you can also assign an
Authorization code to this so that only certain individuals can
carry this out.
Hope thsi helps
Ger
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI Soubhagya,
In that case I can think of following two methods to resolve your issue:
1. Screen variant (T-code SHD0)
2.System Status: Maintain (T-code BS22)
Among the above two options I think option 1 would be more suitable for you.
Try to explore both the options on priority basis check which is best for you and you will be fine.
Good day ahead.!!
Regards
Ankur
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Soubhagya,
Screen variants are status independent. I tried it here and found the results independent of system status:
Triggering of non editing of PD description w.r.t. a status change could have been controlled by a user status which was found ineffective in your case. I think Soubhagya you will have to go for some ABAP development if no any std. methodology suffice here.
However, Let's wait for other expert's response on the same.
Regards
Ankur
User | Count |
---|---|
98 | |
12 | |
10 | |
6 | |
6 | |
4 | |
3 | |
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.