Restricting project profile in CJ20N/CJ01 t-code

Question

Hi Experts,
Based on the client requirement we have created a new Project Profile named as theShutdown Project. The type of Project is ShutDown. The client wants to restrict the same only for the Plant users usage. 
I know that the type of the project can be restricted thru standard authorization object -
C_PRPS_ART. The coding mask is not restricted or defined as of now.
Since we could not find any standard authorization object which restricts specifically on Project Profile, we tried creating a Z
auth.object as follows:
u2022 SU20 -CREATE AUTHORIZATION FIELD
u2022 SU21 -CREATE AUTHORIZATION OBJECT
u2022 SU21 -LINK AUTHORIZATION FIELD AND AUTHORIZATION OBJECT
u2022 SU24 -ADD THE AUTHORIZATION OBJECT IN THE TCODE CJ20N AND CJ01
u2022 PFCG-CREATE ROLE WITH AUTHORIZATIONS TO TCODES- CJ20N AND CJ01. ALSO
ADD THE AUTHORIZATION OBJECT MANUALLY. GENERATE THE ROLE AND SAVE THE
SAME. LINK USER ID TO THE ROLE
u2022 SE38- LCJWBF7S. CREATE ENHANCEMENT IN FORM PROJ_SET AND ADD
AUTHORISATION CHECK OF THE ABOVE CREATED OBJECT 
The issue is that the above procedure is restricting the access for all the other users too despite it being attached to a particular role only. Every project profile other than shutdown  project is getting an error -"You are not authorisedfor this activity"  
Please advice if our approach is correct or are there any alternative available.
Regards
Khushali

Answer 1

HI,
You need not have a separate Auth Object for "Project Profile".
Make use of your standard auth object "Project Type" only.
Introduce a simple validation to say that The only project type "Shutdown Projects" should be allowed for your Project Profile "Shutdown Project"
By this, while Project creation, system throws error (Error you defined in the validation) in case both the Profile & Type are incompatible. When the user selects the appropriate "Project Type", then the subsequent standard error would be related to authorization on Project Type for the desired users.
regards