Authorization bypassed in debug mode

[Former Member]

<b>On the t-code F-43 for Invoice posting, a user who didn't have access to the transaction, seem to be able to post a document while running a program that uses the same transaction in debug mode or while processing as a background job.</b>

Please advise how this can be avoided, while the user surely doesn't have access to the transaction, he's still able to bypass the authorization issue while working in debug mode or processing a background job.

[Former Member]

Hello,

you can try TCODE GGB0 (validations) and there you can carry out validation based on an authorization object (Create a new one if required) and do the desired thing in case of authorization chack failure.

Regards

Saket Sharma

[Former Member]

Thanks for the insight.

Does the authorization object check need to be explicitly done in the program?

Any ideas on why the authorization is bypassed only when accessing the t-code using a BDC program in the debug mode or as a back ground job.

While running the t-code directly, the authorization holds good!

[Former Member]

Hey Murali,

Is the user using a standard transaction or a customised program.

Regards,

Ravi