Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

ERM Configuration error "UNHANDLED ERROR N/A"

Former Member
0 Kudos

Hi Experts ,

We are doing ERM configuration in our ECC system .

while configuration we are receiving "UNHANDLED ERROR N/A" error.

we contacted SAP and received the reply to run SU25 first as ECC system was recently upgraded but SU25 was not executed.

As of now our ECC system is working fine without SU25 run as during and after upgrade we have resolved the errors using testing results and one of the tool.

Now we have suggestions to run SU25 w/o bringing any new objects/tcodes or any changes to any of the profiles and roles.

Please suggest if it is possible to run Su25 w/o effecting existing security and how. we are planning to test it in one of our sandbox first.

Thank You

Ritu

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Now we have suggestions to run SU25 w/o bringing any new objects/tcodes or any changes to any of the profiles and roles.

Why did you upgrade then? If you do not care about SU24 and have manual authorizations then you should not care about running SU25 either?

The main pest here is that the GRC "permissions" level data is based only on the proposals of SU24. This is actually a very stupid design as it forces you to maintain proposals with values simply so that you can report on them, but then your roles look like a dog's breakfast.

Actually, if you could maintain all transactions contexts for all their capabilities as proposals as well, then at the end you will have achieved the same as if you had re-written the whole of the system code because you will have seen it all. And all roles with standard authorizations will be equivalent to SAP_ALL as well.

If you are using menus and proposals, then perform the upgrade tasks propoerly and raise customer messages to complain about the proposals which GRC type tools have convinced SAP to maintain excessively in SU24 and those which they did not maintain at all because they are not on some SOD radar (but are still a big security problem).

That is enough rant now... --> Do you have a sandbox copy or know the exact release and SP level?

This is just a table entry from which the exception is raised, which is also transported in step 3. You should shame yourself, but you could simply transport it instead of upgrading.

Cheers,

Julius

2 REPLIES 2

Former Member
0 Kudos

Now we have suggestions to run SU25 w/o bringing any new objects/tcodes or any changes to any of the profiles and roles.

Why did you upgrade then? If you do not care about SU24 and have manual authorizations then you should not care about running SU25 either?

The main pest here is that the GRC "permissions" level data is based only on the proposals of SU24. This is actually a very stupid design as it forces you to maintain proposals with values simply so that you can report on them, but then your roles look like a dog's breakfast.

Actually, if you could maintain all transactions contexts for all their capabilities as proposals as well, then at the end you will have achieved the same as if you had re-written the whole of the system code because you will have seen it all. And all roles with standard authorizations will be equivalent to SAP_ALL as well.

If you are using menus and proposals, then perform the upgrade tasks propoerly and raise customer messages to complain about the proposals which GRC type tools have convinced SAP to maintain excessively in SU24 and those which they did not maintain at all because they are not on some SOD radar (but are still a big security problem).

That is enough rant now... --> Do you have a sandbox copy or know the exact release and SP level?

This is just a table entry from which the exception is raised, which is also transported in step 3. You should shame yourself, but you could simply transport it instead of upgrading.

Cheers,

Julius

0 Kudos

yep ... everything you said is true...

Release 701 , RTA is VIRSANH SP17 .

Edited by: RawatRitu on Dec 9, 2011 9:19 PM