Skip to Content

FV50 : Restrict the POST capability through the Security objects under this transaction.

Our team is trying to restrict the " POST " capability that is active as on icon under the transaction FV50 through the security objects under the transaction.

Any advice will be helpful.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Apr 24 at 01:56 PM

    Please see Vanessa's response here about using Business Transaction Events - - this is what we do at our company to restrict posting. Good luck

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 24 at 02:14 PM


    If the requirement is that a person who has parked the document should not be able to post it, a simple validation in OB28 should work. This can be done based on Field BKPF-PPNAM. The validation works if a person can have a business requirement where the same person may have also need to park and at the same time, authorize posting for a document parked by some one else.

    If a person will have only parking authorization, than look at removing Activity 01 for authorization object F_BKPF_BUK

    Thanks & Regards

    Sanil Bhandari

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 24 at 11:29 PM

    Please refer to this wiki:

    From Rel 4.6C, it is possible to give selected users park only authority using the authorization activity code 77 (Pre-enter) and linking it to the desired authorization object(s) via T-code SU21. The related authorization object(s) must then be linked to the desired profile/user via T-codes SU02/SU01. The following authorization objects are checked:

    F_BKPF_BES Accounting Document: Account Authorization for G/L Accounts
    F_BKPF_BUK Accounting Document: Authorization for Company Codes
    F_BKPF_BUP Accounting Document: Authorization for Posting Periods
    F_BKPF_GSB Accounting Document: Authorization for Business Areas
    F_BKPF_KOA Accounting Document: Authorization for Account Types

    Also see description of note:

    361420 - FB60: User exit for desactivating functions

    Best Regards,

    Thiago Prado

    Add comment
    10|10000 characters needed characters exceeded