Restrict Posting of Parked Documents - FV75

[Former Member]

Hi All,

We have a requirement to allow a User (John Smith) to:

A) Park with FV75

B) NOT Post with FV75

C) Post with F-28, FB70, and other Posting Transactions

Dilemma: If John Smith's role assignments contain the Activity Value which allows F-28 to Post, it also allows FV75 to Post.

Technicality: We have set object F_BKPF_KOA (Authorization for Account Types) to "Do Not Check" for FV75. The Posting Functionality of all FV75, F-28, FB70 ... is now dependent on object F_BKPF_BUK (Authorization for Company Code).

All transactions share this object. For F-28 to Post, the Activity must include 1 (Create) for the relevant Company Code. But, this then allows FV75 to Post to the same Company Code.

We cannot set F_BKPF_BUK to "Do Not Check" for FV75 because of business requirements - however, FYI, doing so for FV75 defaults the program to allow Posting for all Company Codes (which is undesired).

Have you seen this situation before? We would appreciate notes on any form of resolution.

Thanks,

Maggie

[l_borsboom]

You could create a transaction variant for FV75 with transaction SHD0. In this variant you could delete / grey out the posting button (don't forget the menu options as well!). If you search on this forum on SHD0 you will find the appropriate documentation to help you out

If FV75 in general should only be used for parking, not posting, you could assign the new variant as the default variant fot FV75.

If the limited variant should only be assigned to some users, you can create a variant-transacation (e.g. ZFV75) with the new variant and authorize this transaction for John Smith in stead of FV75.

Good luck!

Lodewijk

[Former Member]

Thanks so much. It has also been suggested that the FI Team could create Validation Rules to control the Posting access (with help from a User Exit) - your method is much easier and serves us just fine.