Ansicht
Dokumentation
F_PAIT_ATT - BCA Payment Item: Authorization Types
CL_GUI_FRONTEND_SERVICES - Frontend Services BAL_S_LOG - Application Log: Log header dataThis documentation is copyright by SAP AG.
Definition
The system checks this authorization object during maintenance of payment items.
With this authorization object you can define authorizations for any of the input fields for the maintenance of payment items. Depending on the field value, you specify which payment items a user is allowed to maintain. To do this you define an authorization type in Customizing and store the names of the fields you want checked.
The system also checks this authorization object for the payment item when you create, release, change, display, or delete a prenote.
Note
This authorization is optional. You do not need to issue it if no master records need special protection and no authorization types are defined in Customizing for this reason.
Defined fields
Activity
Authorization type
You use this to define to which authorization type this authorization is to apply.
Authorization value (field 1)
You use this to define the value of the first table field stored for the authorization type.
Authorization value (field 2)
You use this to define the value of the second table field stored for the authorization type.
Possible activities
01 Add or create
02 Change
03 Display
06 Delete
43 Release
85 Reverse
A1 Postpone
L0 All functions
Check in transactions
The system checks the authorization object during posting, changing, displaying, reversing and returning of payment items and also during release (principle of dual control).
The system does not check the authorization objects for payment items (F_PAIT_*) during the posting of payment orders.
Notes
During posting, the system checks activity 'Add or create' (01). Object F_PAIT_GRP is an exception. In this case, during posting the system checks activity 10 (post).
Activity 'Release' (43) relates here to the releasing of items with the status 'Control, principle of dual control'.
For the final posting of items in post processing, however, you only need activity 'Change' (02).
The system only checks activity 'Add or create' during manual posting of payment items. This means that there is no check of this authorization object during the automatic creation of payment items (as part of balancing, for example).
The system checks activity 'Postpone' (A1) when payment items are returned.
The system checks activity 'All functions' (LO) when entry is made with transaction Payment item -> Edit -> Special -> All activities.
During creation, display and deletion of planned items the system checks activities 'Add or create' (01), 'Display' (03) or 'Delete' (06).
Procedure
If you wish to use this authorization, proceed as follows:
- Determine the fields to which you want the authorization to apply.
- In Customizing define the authorization types with the fields determined above (choose Maintian authorization types (IMG activity)).
- In the profile generator define the authorization you wish to issue to selected employees by listing the authorization type fields and the activities (choose Generate and assign authorization types(IMG)).
- Assign this authorization to the users by means of the corresponding activity group.
ABAP Short Reference SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.
Length: 3880 Date: 20240523 Time: 050758 sap01-206 ( 63 ms )
