Problem in transaction variant when going back to initial screen

[Former Member]

Hello,

I've created a transaction variant zb21 for the mb21 transaction. When I create a role for the new created t.code 'zb21' and test it everything is okay until the user select back button, there's an authorization error the that the user does not have authorization on the mb21 t.code.

[Former Member]

Coud be caused by the "LEAVE TO TRANSACTION sy-tcode" in the original coding, (FORM beleg_anzeigen INCLUDE MM07RFB0)

So either you  change standard behavior, or give standard transaction authorization.

For reference, read Note 601472 - Authorization check with variant transactions, to find how to change the code.

- using LEAVE TO CURRENT TRANSACTION ABAP (Use Implicit Ehn)

- creating a wrapper report which uses FM RS_HDSYS_CALL_TC_VARIANT and adapt your transaction to call this report

Regards,

Raymond

[Former Member]

Hi

back button in a copied standard transaction (instead an exit) could still call the authorisation check of the standard one.

Can you give the authorisation missing?

Let me know

a

[Former Member]

Hi Andrea,

I haven't copy the standard transaction, I've created a transaction variant and defaulted it to the standard transaction.

[satyabrata_sahoo3]

Create similar auth. objects as of MB21 for your ZB21 in SU24 and assign in the roles.

Similar thread:

http://scn.sap.com/thread/2133579

-Satya

[Former Member]

Hi,

After having the authorisation error, go to tcode /NSU53, and assign the role for the user which you see in /NSU53. Hope this will solve your problem.

Thanks-

Makarand

[RaymondGiuseppi]

Coud be caused by the "LEAVE TO TRANSACTION sy-tcode" in the original coding, (FORM beleg_anzeigen INCLUDE MM07RFB0)

So either you  change standard behavior, or give standard transaction authorization.

For reference, read Note 601472 - Authorization check with variant transactions, to find how to change the code.

- using LEAVE TO CURRENT TRANSACTION ABAP (Use Implicit Ehn)

- creating a wrapper report which uses FM RS_HDSYS_CALL_TC_VARIANT and adapt your transaction to call this report

Regards,

Raymond

[Former Member]

Hi Raymond,

We used the workaround of creating a wrapper report and using FM RS_HDSYS_CALL_TC_VARIANT function module.

The note was already implemented on our system.