Scribd
Upload
23 views2 pages

Authorization Objects For Settlement Management

The document outlines key authorization objects for settlement management in SAP HANA and SAP S/4HANA, including F_KTBER_BUK for company code authorization and F_SMANAGE for settlement management access. It also details steps to configure these authorizations, such as determining required activities, assigning objects, defining field values, testing roles, and maintaining security compliance. The focus is on ensuring proper access control and compliance in settlement processes.

Uploaded by

sadanand warushe
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
23 views2 pages

Authorization Objects For Settlement Management

The document outlines key authorization objects for settlement management in SAP HANA and SAP S/4HANA, including F_KTBER_BUK for company code authorization and F_SMANAGE for settlement management access. It also details steps to configure these authorizations, such as determining required activities, assigning objects, defining field values, testing roles, and maintaining security compliance. The focus is on ensuring proper access control and compliance in settlement processes.

Uploaded by

sadanand warushe
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Common Authorization Objects for Settlement Management

Here are some key authorization objects relevant to settlement management in SAP
HANA and SAP S/4HANA:
1. F_KTBER_BUK - Authorization for Account Assignment Group by
Company Code
o Used for checking the company code level authorization for settlement
processes.
o Fields:

 KTBER: Account assignment group


 BUKRS: Company code
2. F_SMANAGE - Settlement Management Authorization
o Controls access to functions related to settlement management.

o Fields:

 ACTVT: Activity (e.g., 01 for create, 02 for change, 03 for display)


 SM_TYP: Settlement type (e.g., customer rebate, supplier rebate,
etc.)
3. F_BKPF_BUK - Authorization for Document Processing by Company
Code
o Used for checking company code-level authorization for accounting
document creation during settlement.
o Fields:

 BUKRS: Company code


 ACTVT: Activity
4. F_TCODE - Transaction Code Authorization
o Controls access to specific transactions related to settlement
management, such as:
 WB2R_SC: Create settlement
 WB2R_SV: Display settlement
 WB2R_SD: Edit settlement
5. K_CCA - Cost Center Accounting Authorization
o May be relevant if settlements involve cost center postings.

o Fields:
 KOSTL: Cost center
 ACTVT: Activity
 CO_AREA: Controlling area
6. M_REBATE - Authorization for Rebate Processing
o Used for authorizations related to rebate processing.

o Fields:

 ACTVT: Activity
 REBATE: Rebate agreement type

Steps to Configure Authorization for Settlement Management


1. Determine Required Activities:
o Identify the transactions or processes (e.g., create, change, display)
users need access to.
2. Assign Authorization Objects:
o Use the SAP GUI transaction PFCG to assign authorization objects to
roles. Add the appropriate objects like F_SMANAGE or F_BKPF_BUK.
3. Define Field Values:
o Configure field-level access in the authorization objects. For example,
restrict access to specific company codes (BUKRS) or settlement types
(SM_TYP).
4. Test and Validate:
o Test the roles using transaction SU53 or ST01 to check for missing
authorizations when executing settlement-related activities.
5. Maintain Security Compliance:
o Ensure roles are assigned based on the principle of least privilege,
granting only the necessary access.

You might also like