08-11-2009 2:51 PM
All Security Gurus!!
How do I remove the AUTHORIZATION FIELD - PROFIT_CTR from SU21 maintaining an authorization object. I was able to add it which caused it to affect a few tcodes so I am trying to remove it and am having issues because it does not let me remove it.
Thanks
Edited by: Julius Bussche on Aug 11, 2009 5:29 PM
Subject title given more usefull meaning...
12-02-2009 6:58 PM
08-11-2009 3:05 PM
Basically you cannot. I believe a way to work around this is to transport the same object from a system where it does not have this extra field.
Have a look at this thread:
08-11-2009 3:12 PM
Thank you very much Jurjeen. That answer was very helpful. I am going to try it.
Thanks
08-11-2009 3:19 PM
Jurgen,
If this was originally transported to all system and clients, can I do it from my sandbox environment? If so how can I.
Thanks
08-11-2009 3:27 PM
Go ahead and create a transport on your sandbox. Give the transport request number to your Basis folks and they can copy the data and cofile to your landscape and manually add it to the import queue.
Michael
08-11-2009 4:55 PM
Michael,
We did that but ran into an issue with the co-file. We could not see the data in the co-files for that transport. Please help.
08-11-2009 8:42 PM
Which object did you add this field to?
Did you also add authorization values to this field and transport those roles?
Did you change any coding (SAP's own coding?) to include this field ID?
There are a number of checks done when you release a transport, and others when you import authorizations (and roles). Did you bypass any of these before when creating this field?
Cheers,
Julius
08-11-2009 9:12 PM
Which object did you add this field to? NO
Did you also add authorization values to this field and transport those roles? THIS IS IN SANDBOX - NO CUSTOM ROLES THERE
Did you change any coding (SAP's own coding?) to include this field ID? NO
There are a number of checks done when you release a transport, and others when you import authorizations (and roles). Did you bypass any of these before when creating this field? NO
Thanks
Daisy
08-12-2009 8:37 AM
>
> Which object did you add this field to? NO
This kinda sounds like answering NO to the question "What is the day today?". The actual object name may help us search for a solution.
08-12-2009 8:55 AM
>
> Michael,
>
> We did that but ran into an issue with the co-file. We could not see the data in the co-files for that transport. Please help.
can we come back to this one, please? what, exactly does 'issue' mean? what was wrong with the cofile?
08-12-2009 11:22 AM
According to the above "NO" series, it is just a field not used by any object and not checked as an objectless field ID in any code either.
At most it is using an existing domain and the value ranges have been messed up - but that would have been an object modification requiring an object key and might even have been done "locally" in each system...
Perhaps an empty transport cofile means that it is a mime in a forest?
Just guessing - as there is not much else to work with here.
Cheers,
Julius
12-02-2009 6:58 PM
12-02-2009 9:11 PM
Do you have a note number, or was it a customer message number?
I (and others who use the search...) might be interested.
Cheers,
Julius