FS03 -> FS00 dependenciy authorization problem

[Former Member]

Hi all,

I'm assisting in a release's upgrade from 4.6c to ECC 6.0, and I'm experiencing an authorization's problem related to transaction FS03.

In the 4.6c system I've a user role that can execute the FS03 transaction without problem, and I've transported it to ECC 6.0. Doing a role_cmp/SUIM check everything seem right, but in the newly upgraded system, when I try to run the transaction FS03, I receive an authorization failed error related to the transaction FS00.

It seem like that in ECC 6.0 the transaction FS03 has been changed and somehow now it's related to the transaction FS00.

Does anyone know what could be the problem? Many thanks!!!

[Former Member]

> ... when I try to run the transaction FS03, I receive an authorization failed error related to the transaction FS00.

> ...

>... transaction FS03 has been changed and somehow now it's related to the transaction FS00.

Which error do you get exactly? Does it say something about "You are not authorized to use transaction FS00?

Sometimes transactions are functionally related and even technically identical, but behave differently depending on the calling users context and authority.

This error message might only be misleading or not appropriate, or there is a tcode check in there somewhere which needs to be set up for trusting each FB03, or the user is missing some other authority required for FS00 functions to be usable from FB03 as well but to simplify things it is saying that you cannot use transaction FS00 (but you can use the rest of FB03).

In addition to doing a trace on it, try to just hit "Enter".

Cheers,

Julius

[Former Member]

Check in Su24 whether FS03 has S_TCODE in Check/Maintain state ....in most of the cases it is Check State....anyway if it is in check/maintain state see the values it contain ...does it contain FS00 ? it maybe a possiblity that FS00 has been pulled in your role under S_TCODE with the addition of FS03 in the menu tab.

....its a possibility that SAP may have done some enhancement to this t-code and hence and additional check for this t-code. But normally when you upgrade I thought these things are checked.

You check SAP enhancements to t-codes,

you check your customization that you have done to your t-codes...and then you compare and take decisions.

[Former Member]

Hi Daniele,

We have also upgraded our system from 4.6C to ECC6.0 and never faced this problem regarding FS03. Becuase there are no authorization object changes for FS03 in 4.6c and Ecc6.0. And one thing if you check trace logs for FS03 tcode then you will find that in backend it also check S_tcode authorization object with FS00. So FS00 tcode is mandatory while executing FS03 transaction.

Regards,

Sneha

[Former Member]

Hello Daniele,

There has been additional checks added in Ecc 6.0 when compared to release 4.6C and yes S_TCODE needs the value FS00 compulsarily to execute FS03 in ECC 6.0. However this is not the case with 4.6C.

Regards,

Subbu

[Former Member]

Thanks all!!! I'm quite on the way of solving it.

Subbu do you know if there are SAP notes related to the problem which I can refer to? Many thanks!

[Former Member]

Hello Danielle,

I could not find any relevant SAP note related to this issue.

Regards,

Subbu

[Former Member]

Note that FS03 calls transaction FS00. Search through the code for the table where the settings are and then take a look at coding which looks something like:

CASE ok_code.
...
 WHEN 'FS0+'.
  CALL TRANSACTION 'FS00'.

You can also test this by starting transaction FS03. If you look at your transaction context (bottom right hand corner) you will see that you are in FS00 (not FS03).

Cheers,

Julius