Error in Posting doc using FBV0

[Former Member]

Hi,

We are in the process of implementing Roles and authorizations in one

of our client-

While UAT we are facing one issue-

Eg,

User uatuser1 is an execuive and having F-63 and FV60 T-codes for

perking documents

So, this user perked two document doc1 using F-63 and doc2 using FV60.

Now the user uatuser2 is a supervisor and he will do posting of these

perked documents doc1 and doc2 using FBV0 T-code.

This user uatuser2 posted successfully the doc1 perked by F-63.

But the issue is when this user tries to post the doc2 which is perked

by FB60 then he got an authorization error called-

"You are not authorized to use Transaction FV60". But doesn't have FV60

T-code with hm.

If we take SU53 dump as well as ST01 trace we can see only FB60 T-code

is coming in missing authorization.

So, please let us know why the system behaves like this? Whether it is

calling FB60 internally while posting through FBV0.

Regards,

Sudip

[martin_voros]

Hi,

yes, it calls transaction FV60. It works this way only for enjoy transactions and it's mentioned in note 441412.

Cheers

[arpan_paik]

You can give access to the transaction and control park access in supervisor role by activity 77 for corresponding objects to the transaction

Regards,

Arpan Paik

[Former Member]

If there is no harm in them having FB60... then add it as an "authorization default" to the role.

They will be able to start it but will not see it in the menu.

Cheers,

Julius

[arpan_paik]

Dear Julius,

Sorry to ask qtn on other people thread.. Did you mean manual S_TCODE? Authorization default escape me

Regards,

Arpan Paik

[Former Member]

On the Menu tab of PFCG you can also select "Authorization defaults". Here you can add tcodes (amongst other things) to the menu of the role. The authorizations will be standard and will also pull the proposals as a "normal" transaction does, but the tcode will not be visible in the menu to the end user.

It is just a way to make the menu smaller although there are more objects in it (e.g. symbolic transactions, RFC function modules, web services) which the user does not see.

Note that in the case of tcodes added this way they can execute the tcode directly via the ok-code command field and will see it displayed in SU53 if they are authorized to know what they do have in their authorizations.

Cheers,

Julius

[Former Member]

Thanks everybody...my issue is resolved