Restricting BNK_MONI T-code

[Quadir]

Hi,

Any idea how can we restrict BNK_MONI T-code on the basis on company code since even after restricting, users are able to run for all company code?

Thanks,

Syed Imam

[Sandra_Rossi]

Did you run an authorization trace to make sure which authorization checks are executed and what are the results of each check?

[Lakshmipathi · Accepted solution]

BNK_MONI is a monitoring transaction, not a posting or execution transaction. It’s primarily used to view payment statuses and batches.

SAP designed it to check F_STAT_MON, which includes fields like:

• Authorization group
• Payment medium status
• Payment run status

It does not include company code as a restriction field, which means you can't directly restrict access by company code using standard authorization objects.

Here are some approaches and Best Practices which you can also try

1. Authorization Groups
Assign different authorization groups to payment batches based on company code. Then restrict F_STAT_MON by authorization group. This requires customizing your payment configuration to tag batches appropriately.

2. Custom Enhancement (BAdI or User Exit)
Implement a custom check via enhancement in BNK_MONI or related function modules. You can intercept the selection logic and restrict based on user’s company code authorization.

3. Role-Based UI Restriction
If you're using SAP Fiori apps, you can apply restriction types at the business catalog level. For example, restrict by company code using the “Company Code” restriction field in the role definition.

[Quadir · Accepted solution]

Hi @Lakshmipathi ,

Your response is highly appreciated. I think your 3rd suggestion is only valid for S/4 HANA public cloud. Am I correct ?

[Lakshmipathi]

Yes you are right.  It is applicable in SAP S/4HANA Cloud, public edition.

[Quadir]

Hi Sandra,

Yes i did trace and surprisingly the code is not checking the authorization object F_REGU_BUK. Instead it is checking F_STAT_MON