SAP Note

361420 - FB60: User exit for deactivating functions

Component: FI-AP-AP-A (Posting/Clearing/Special General Ledger), Version: 18, Released On: 22.07.2004

Symptom
In the FI EnjoySAP Transactions, you want to deactivate some functions (for example, 'Park'
or 'Post') that are active by default.

Other Terms
FB50, FB65, FB70, FB75

Reason and Prerequisites

This function is not available.

Solution
The following changes implement a BTE event where you can deactivate function codes. You can
see from the documentation how to use the user exit.

If you use Release 4.6B Support Package 30 - 34 or Release 4.6C Support Package 18 - 26,
only point 10 of the following correction instructions is relevant.

Caution: After you have implemented this note manually, it is imperative that you delete the
new function module OPEN_FI_PERFORM_00001140_E prior to importing a Support Package.
Otherwise, it inconsistencies may occur in the function group.
1. Call Transaction SE11 and create data type EV00001140 as a data element with the
following field values:
Development class: FIBF
Short description: 'Open FI: Event 00001140'
Domain: XFELD
Field label
Length Field label
Short 10 EV00001140
Medium 10 EV00001140
Long 10 EV00001140
Heading 1 X
Documentation

1. This event runs in the FI Enjoy transactions before the PF status is set. You can fill
the internal table T_EXCTAB with function codes that are active as standard but are not to
be active in your system.

2. The Exit has the following parameters:

a) Import

I_PARKED: Document was already parked

b) Tables
T_BKPF: Table of document headers (input only)

T_EXCTAB: Excluded OK codes.

3. This a publish and subscribe interface.

2. Activate the new data type.
3. Create data type EXCLTAB_LINE as a structure with the following field values:
Development class: FBAS
Short description: 'Lines of EXCLTAB with OK Code to be Deactivated'
Components

Comp RType Comp type DTyp Length Dec.places Short descr.

OKCOD OKCODE CHAR 20 0 Function Code
4. Call Transaction SE37 and create function module OPEN_FI_PERFORM_00001140_E with the
following attributes:
Function group: BFFM2
Short text: 'Execute Open FI activities for Event 00001140'
Import parameters

Parameter name Type spec Ref type Deflt Pass Opt Short text

I_PARKED TYPE XFELD X X Doc already parked

Tables

Parameter name Type spec Ref type Opt Short text

T_BKPF LIKE BKPF Doc header for financial accounting
T_EXCTAB LIKE EXCLTAB_LINE Line of EXCLTAB with OK code to be
deactivated
Documentation

Fill table T_EXCTAB with the OK codes that are not to be active. Use table T_BKPF with
the document headers and the SYST fields to determine the actions that are not to be
executed by the user. Import parameter I_PARKED has value 'X' if the document was
already parked. For example, you could prohibit the posting in the parking transactions
(OK code 'BU') if the user name in the document header is the same as the current user.
This allows you to implement the dual control easily.
5. Call Transaction SE37 and choose menu path 'Goto -> Function groups -> Create group'.
6. Create function group BFFMSMPL4 with the following attributes:
Short text: 'Sample modules 4'
Package: FIML
Application: S
7. Call Transaction SE37 and create function module SAMPLE_INTERFACE_00001140 with the
following attributes:
Function group: 'BFFMSMPL4'
Short text: 'Interface description for Event 00001140'
Parameter name Type spec. Ref type Deflt Pass Opt Short text
I_PARKED TYPE XFELD X X Doc already parked
Tables

Parameter Name Type spec Ref type Opt Short text

T_BKPF LIKE BKPF Doc header for financial accounting
 T_EXCTAB LIKE EXCLTAB_LINE Line of EXCLTAB with OK code to be
deactivated
8. Call Transaction SM30, enter table TBE01 and choose 'Maintain'.
9. Insert the following entry:

Event Text
00001140 POST DOCUMENT: Exclude OK Codes (Enjoy)

Sample function module

SAMPLE_INTERFACE_00001140
10. Call Transaction SM30, enter table TBE02 and choose 'Maintain'.
11. Insert the following entry:

Attr.Type Selection attributes Event

A FI-GL-GL 00001140
12. Add import parameter I_DOCUMENT_EXISTS to the interface of function module
ACC_SIMULATED_DOC_DISPLAY:

Parameter name Type spec Ref type Deflt Pass Opt Short text
I_DOCUMENT_EXISTS TYPE CHAR1 X X Doc already exists
existing
13. Implement the attached program corrections.

Manual Activities

Attributes
Key Value

Other Components FI-GL-GL-A (Posting/Clearing)

Transaction codes SE11

Transaction codes SE37

Transaction codes SM30

Transaction codes COMP

Transaction codes BUCH

Transaction codes FIBF

Software Components
Software Component And subsequent

SAP_APPL

SAP_APPL

SAP_ABA

SAP_ABA

Correction Instructions
Software Component Number of Correction Instructions

SAP_APPL 2
 Support Package
Software Component Version Support Package

SAP_APPL 46B SAPKH46B30

SAP_APPL 46B SAPKH46B35

SAP_ABA 46B SAPKA46B23

SAP_APPL 46C SAPKH46C27

SAP_APPL 46C SAPKH46C18

SAP_ABA 46C SAPKA46C13

SAP_ABA 46D SAPKA46D04

This document refers to

SAP Note/KBA Title

863267 FAQ: Validations in Enjoy transactions

This document is referenced by

SAP Note/KBA Title

863267 FAQ: Validations in Enjoy transactions