Ansicht
Dokumentation

Easy Authorization Management for SAP

F_CASH_PRG - BCA Means of Payment Management: Auth. Group Acc. to Product

BAL_S_LOG - Application Log: Log header data   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Definition

The system checks this authorization object during maintenance of means of payment management. You can use it to ensure that users are only allowed to edit means of payment management for a certain product.

Defined fields

Activity

Authorization group

The authorization group field relates to the authorization group in the product. If this authorization group is not maintained, the system makes no authorization check.

Possible activities

01 Add or create

02 Change

03 Display

05 Block

06 Delete

43 Release

Check in transactions

The system checks these authorization objects during editing of checks (cheques):

• Create check ,,,,(checking of activity 01)

• Request check,,,,(checking of activity 01)

• Block check,,,,,,(checking of activity 05)

• Edit check,,,,,,(checking of activity 05)

• Display check,,,,(checking of activity 03)

• Deledte check,,,,(checking of activity 06)

• Newly assign check,,(checking of activity 02)

There is an additional check in check stack management:

• Create check stack,,(checking of activity 01)

• Request check stack,,(checking of activity 01)

• Issue checks,,,,(checking of activity 01)

• Display check stack,,(checking of activity 03)

• Release check stack,,(checking of activity 43)

• Block check stack,,(checking of activity 05)

• Unblock check stack,,(checking of activity 05)

• Delete check stack,,(checking of activity 06)

• Create check stack locations,,(checking of activity 01)

• Maintain check stack locations,,(checking of activity 01)

Notes

The system does not check the authorization objects for authorization groups (F_CASH_BPG; F_CASH_ACG; F_CASH_PRG) during creation, requesting releasing, unblocking, blocking and deletion of check stacks or during creation and maintenance of check stack locations, as in these transactions there is no individual account known to the system from which the authorization group required for the check could be derived.

During the display of check stacks, the system only checks the above- mentioned authorization objects for authorization groups for issued checks, as in this case, the account involved is known to the system.

Easy Authorization Management for SAP

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 2993 Date: 20240604 Time: 052002     sap01-206 ( 38 ms )