Block the G/L for every activity

[Former Member]

Dear All Expert,

In our some G/L there has some transaction with some adjustments which are showing in line item, TB, etc.

But we want to block the G/L centrally, it means it will not show in FBL3n, TB or any where.

Is it possible to do this?

Thanks in advance

With best regards

Bishnu

[former_member192833]

Hi Bishnu,

There is no standard way to achieve your requirement.  Only way to use BAdi/exit.

Also i want to know whether you want to block specific line items from GL or Entire GL.

Regards

Atul

[Former Member]

But the ideal way is to restrict the user from authorisation as it will ensure that the other users are not impacted with this restriction.

Regards,

Francis

[former_member183424]

As of my knowledge, there are no standard way to block the G/L account in report.

Report is used to just show up the all data entry.

You can restrict the data entry, but you can't restrict the Report for any data entry.

You may can use any user exit or badi for t-code FBL3N, where you can restrict the G/L account in this report as per your criteria.

If you don't want to show one G/L account, then you can hard code the G/L account in user exit or badi.

Or if you want to many G/L account, then you can create a Z table with these G/L accounts, the badi or user exit will leave the G/L account in the transaction FBL3N.

[Former Member]

Hi Dev,

Can u tell me the user exit or BADI?

Is this built in or I have to develop?

Regards

BKD

[former_member183424]

You can use

FI_ITEMS_MENUE01

FI_ITEMS_MENUE02.

Also try to find an appropriate badi by using the document

[iklovski]

Hi,

Only via authorization, playing with built-in variants or development. There is no standard functionality, for obvious reasons, which would prevent showing data in the reports on specific account.

Regards,

Eli

[Former Member]

Hi Eli,

Thanks a lot for quick reply.

any hints for authorization group?

Regards

BKD

[iklovski]

You can create authorization role on G/L object and take it out... Though, I strongly, don't recommend this approach as the whole idea of 'hiding' data from the reports.