Journal Entries FB50 and Parking

Question

FI Gurus,
Client wants to have some users to only be able to  park documents in FB50 and Not be able to post. Then have a different person to approve the JE based on dollar amount and post journal entry if it is within their $ amount authority. Does anyone knows of a procedure to accomplish this?
Thank You for your help

Answer 1

Hello Frank,
For the enjoy PP transactions as FB50, please consider Business transaction events.
Please take the following steps.
Start transaction FIBF, this is a well experieced way to prevent posting in ENJOY PP transactions as FB60 for instance. Please start transaction FIBF, menu environment -> info system (P/S), start this report w/o any further selections and choose key 00001140. How to proceed now isdescribed and claryfied by example in the documentation. As far as authority objects are concerned no particular activities are necessary.
You will see the following information referenced in the documentation.
FU SAMPLE_INTERFACE_00001140
=============================
Functionality
     This function module is an interface description only and does not contain any instructions. It is intended for developers of those additional components that provide their own function module at
Event 00001140 (Change document, transaction access).
     Function module SAMPLE_INTERFACE_00001140 must not be changed.
     If you want to create your own function module that is to be accessed at      the callup point mentioned above, proceed as follows:
     1.  Copy the function module to your own name range.
     2.  Do not change any transfer parameters !!
     3.  Write your own coding in the copied function module.
     4.  Save and activate your function module.
     5.  Carry out the necessary settings in Customizing. Business
         Transaction Events
EVENT
     The event is in the PBO part of the FI Enjoy Transactions (FB60, FB50, FV60 and so on). Here you can determine which buttons or menu paths are to be deactivated for specific customers.
INTERFACE
Table T_BKPF with the document headers is transferred to the additional component. Parameter I_PARKED is also transferred; this has the value 'X' if the document has been parked. Use this data to determine which actions the user is not permitted to perform.
Fill table T_EXCTAB with the OK-Codes that are not to be active. These are hidden in the transaction.
Example
For example, in the parking transactions (such as: SY-TCODE = 'FV60'), you can prohibit posting (OK code 'BU') if the user name in the document header is the same as the current user. This enables you to use the dual control principle.
     Example coding:
  if sy-tcode  = 'FV60'.
  if i_parked = 'X'.  " document has already been parked
     read table t_bkpf index 1.
     if t_bkpf-usnam eq sy-uname.  " park user = current user ?
        t_exctab-okcod = 'BU'.        " do not allow to post
              append t_exctab.
      endif.
     endif.
    endif.
Parameter
     I_PARKED
     T_BKPF
     T_BSEG
     T_EXCTAB
Exceptions
Function group
     BFFMSMPL4
Please also review note 361420.
I hope it helps
Best Regards,
Vanessa Barth.