What are the common symptoms of Authorization check F_BKPF_BUK in FBCJ?
The FI cash journal is used. In the system SAP 1805616 has been implemented already; as a result, when the cash journal is used, the authorization object F_BKPF_BUK is checked.
The following things occur when the check takes place:
When the cash journal is called:
- OBJECT F_BKPF_BUK with the activity 03 ("Display")
When the cash journal documents are changed:
- OBJECT F_BKPF_BUK with the activity 02 ("Change")
When the cash journal documents are deleted:
- OBJECT F_BKPF_BUK with the activity 06 ("Delete")
When the cash journal documents are saved:
- OBJECT F_BKPF_BUK with the activity 01 ("Add or Generate")
When the cash journal documents are posted:
- OBJECT F_BKPF_BUK with the activity 10 ("Post")
According to the documentation for the activities, these authorizations are correct. For the posting of documents, the authorization object F_BKPF_BUK is used with activity 01 ("Add or Generate") in the FItransactions.
In order to save in the cash journal, a user requires authorization for the activity 01 but this enables posting in FI also; however, this is undesired.
The activity 01 must be used for F_BKPF_BUK in the cash journal to achieve consistency in FI posting transactions. This is done for the cash journal documents posting (when saving cash journal documents, it should not be checked).
With this SAP Note as follows, the authorization checks for F_BKPF_BUK are revised again:
The "accounting document: authorization for company codes" is signified by the authorization object F_BKPF_BUK, the accounting document is related to the authorization object. In the cash journal for the display, generation, or deletion of the follow-on document, the authorization object BF_BKPF_BUK is now only checked.
When the cash journal is entered, F_BKPF_BUK is no longer checked. This means with SAP 1805616, the checks that have been implemented are revoked.