Authorizations
The procedure of the authorization concept used by Reserve for Bad Debt (FS-RBD) is the same as that of the SAP authorization concept.
The authorization checks in FS-RBD differentiate between the following dimensions:
· Activities:
You use the activity to control what a user is permitted to do. For example:
¡ Create a RBD account
¡ Post value adjustment proposals
¡ Display evaluations
· Organization
The organization at RBD area level determines which data the user is permitted to display or process.
Standard Profile
In FS-RBD you do not use RBD-specific profiles, but the standard profiles delivered with every SAP system.
The standard profiles are as follows:
Roles |
Description |
S_A.SYSTEM |
Authorizations for the basis system only |
S_A.ADMIN |
Authorizations for the administration of the operational SAP system, but without authorization for: · ABAP/4 Development Workbench · maintaining superusers · maintaining the standard profiles beginning with “S_A” |
S_A.DEVELOP |
Authorizations for developers working with ABAP/4 Development Workbench |
S_A.CUSTOMIZ |
Authorizations for basis settings in the Customizing system. |
S_A.USER |
Authorizations for end users (without authorization for SAP work areas) |
Authorization Objects
Reserve for Bad Debt (FS-RBD) has the following authorization objects:
Critical combination: Creating and posting value adjustment proposals (planned records) within a role.
Authorization Object |
Description |
Authorization Field |
Values permitted for the authorization field |
RBD_CUST |
RBD: Customizing |
Activity |
16 (Execute) |
RBD_EDIT |
RBD Dialog & Batch |
Activity
RBD area |
01 (Create) 02 (Change) 03 (Display) 10 (Post) 85 (Reverse) 91 (Reactivate) According to RBD Customizing |
RBD_REPO |
RBD: Reporting |
RBD area |
According to RBD Customizing |
Description of these authorization objects:
· The assignment of authorization object RBD_CUST with activity 16 gives the user authorization to use an RBD Customizing tool.
· The assignment of authorization object RBD_EDIT with activity 02 and RBD area 0005, enables the user to change data for an RBD account in the RBD area 0005.
· The assignment of authorization object RBD_EDIT with activities 02 and 10 and the RBD area 0004 enables the user to post planned records for an RBD account in the RBD area 0004.
· The assignment of the authorization object RBD_EDIT with the activities 02, 85, 91 and the RBD area 0003 enables a user to reverse actual records for an RBD account in RBD area 0003, and to reactivate a deactivated account in the RBD area 0003.
· The assignment of the authorization object RBD_REPO in RBD area 0006 enables a user to display the RBD standard evaluations for the data in the RBD area 0006.
Note that the activities Create Value Adjustment Proposals (Planned
Records) and Post Value Adjustment
Proposals (Planned Records) are possible within one role.
·
Use of RBD Authorization Objects
RBD_CUST
Program |
Description |
Permitted Activities |
/IBS/MRB_CUST_KTOFI |
RBD Tool Customizing: Duplicate Account Determination |
16 (Execute) |
RBD_EDIT
Program |
Description |
Permitted Activities |
/IBS/MRB_SAPMKTO |
RBD: Dialog account master data |
01 (Create) 02 (Change) 03 (Display) 10 (Post) 85 (Reverse) |
/IBS/MRB_EWB_UPDATE |
CML Position monitoring update run |
02 (Change) 10 (Post) |
/IBS/MRB_KONTO_REACTIVATE |
Reactivate RBD account |
91 (Reactivate) |
/IBS/MRB_LOG_POST |
RBD Posting log |
03 (Display) |
/IBS/MRB_PEWB_REFRESH |
RBD:CML Monitoring of arrears: Planned record generation (FIVA) and posting |
10 (Post) |
/IBS/MRB_PEWB_RESET |
RBD: CML monitoring of arrears: Clearing actual records (reversal FIVA) |
85 (Reverse) |
RBD_REPO
Program |
Description |
Permitted Activities |
/IBS/DRB_ENTWICKLUNG |
RBD development list, development reserve for bad debt position |
According to RBD Customizing |
/IBS/DRB_HINT_LIST |
Position monitoring: List of notes |
According to RBD Customizing |
/IBS/DRB_REFERENZ |
RBD Drilldown reporting with references |
According to RBD Customizing |
Definition of Customer-Specific Roles
The following information is required for the definition of customer-specific roles for functions in FS-RBD:
· SAP logon names of all employees that are to work in FS-RBD
· RBD areas affected
· Decisions as to which employee is permitted to execute which functions in the RBD Tool
To avoid having to assign a separate role for each employee, we recommend that you form groups of employees that are permitted to execute the same functions. You can then assign a defined role to all of the employees in the group.
Example of generation of user-specific roles:
Activities:
RBD area |
Activity |
Employee |
Role in SAP |
All |
All |
Adams |
RBD_ALLES |
All |
Customizing: Duplicate Account Determination |
Armstrong |
RBD_CUST |
1 |
Create, change, and display RBD account |
Miller |
RBD_SACH_01 |
1 |
Create, change, and display RBD account |
Martin |
RBD_SACH_01 |
1 |
Create, change, and display RBD account |
Smith |
RBD_SACH_01 |
1 |
Change RBD account, post planned records |
Glenn |
RBD_BUCH_01 |
1 |
Change RBD account, post planned records |
O’Hara |
RBD_BUCH_01 |
1 |
Change RBD account, reverse actual records |
Glenn |
RBD_STOR_01 |
1 |
Change RBD account, reverse actual records |
Bertolini |
RBD_STOR_01 |
1 |
Display evaluations |
Santos |
RBD_AUSWERT_01 |
1 |
Display evaluations |
Hunter |
RBD_AUSWERT_01 |
1 |
Display evaluations |
Miller |
RBD_AUSWERT_01 |
1 |
Display evaluations |
Martin |
RBD_AUSWERT_01 |
1 |
Display evaluations |
Smith |
RBD_AUSWERT_01 |
2 |
Create, change, and display RBD account |
Nielsen |
RBD_SACH_02 |
2 |
Create, change, and display RBD account |
Moore |
RBD_SACH_02 |
2 |
Create, change, and display RBD account |
Smith |
RBD_SACH_02 |
2 |
Change RBD account, post planned records |
Glenn |
RBD_BUCH_02 |
2 |
Change RBD account, post planned records |
O’Hara |
RBD_BUCH_02 |
2 |
Change RBD account, reverse actual records |
Glenn |
RBD_STOR_02 |
2 |
Change RBD account, reverse actual records |
Nielsen |
RBD_STOR_02 |
2 |
Display evaluations |
Santos |
RBD_AUSWERT_02 |
2 |
Display evaluations |
Hunter |
RBD_AUSWERT_02 |
2 |
Display evaluations |
Nielsen |
RBD_AUSWERT_02 |
2 |
Display evaluations |
Moore |
RBD_AUSWERT_02 |
2 |
Display evaluations |
Smith |
RBD_AUSWERT_02 |
Roles:
Role in SAP |
RBD Authorization Object Required |
Authorization Field |
Field Value |
RBD_ALLES |
RBD_CUST |
ACTVT |
* |
RBD_ALLES |
RBD_EDIT |
ACTVT |
* |
RBD_ALLES |
RBD_EDIT |
RBDID |
* |
RBD_ALLES |
RBD_REPO |
ACTVT |
* |
RBD_CUST |
RBD_CUST |
ACTVT |
16 |
RBD_SACH_01 |
RBD_EDIT |
ACTVT |
1,2,3 |
RBD_SACH_01 |
RBD_EDIT |
RBDID |
1 |
RBD_BUCH_01 |
RBD_EDIT |
ACTVT |
2,10 |
RBD_BUCH_01 |
RBD_EDIT |
RBDID |
1 |
RBD_STOR_01 |
RBD_EDIT |
ACTVT |
2,85 |
RBD_STOR_01 |
RBD_EDIT |
RBDID |
1 |
RBD_AUSWERT_01 |
RBD_REPO |
RBDID |
1 |
RBD_SACH_02 |
RBD_EDIT |
ACTVT |
1,2,3 |
RBD_SACH_02 |
RBD_EDIT |
RBDID |
2 |
RBD_BUCH_02 |
RBD_EDIT |
ACTVT |
2,10 |
RBD_BUCH_02 |
RBD_EDIT |
RBDID |
2 |
RBD_STOR_02 |
RBD_EDIT |
ACTVT |
2,85 |
RBD_STOR_02 |
RBD_EDIT |
RBDID |
2 |
RBD_AUSWERT_02 |
RBD_REPO |
RBDID |
2 |
As a result, roles are assigned to the user master records as follows:
Employee |
Role in SAP |
Armstrong |
RBD_CUST |
Bertolini |
RBD_STOR_01 |
Adams |
RBD_ALLES |
Glenn |
RBD_BUCH_01 |
Glenn |
RBD_STOR_01 |
Glenn |
RBD_BUCH_02 |
Glenn |
RBD_STOR_02 |
O’Hara |
RBD_BUCH_01 |
O’Hara |
RBD_BUCH_02 |
Hunter |
RBD_AUSWERT_01 |
Hunter |
RBD_AUSWERT_02 |
Martin |
RBD_SACH_01 |
Martin |
RBD_AUSWERT_01 |
Moore |
RBD_SACH_02 |
Moore |
RBD_AUSWERT_02 |
Miller |
RBD_SACH_01 |
Miller |
RBD_AUSWERT_01 |
Nielsen |
RBD_SACH_02 |
Nielsen |
RBD_STOR_02 |
Nielsen |
RBD_AUSWERT_02 |
Smith |
RBD_SACH_01 |
Smith |
RBD_AUSWERT_01 |
Smith |
RBD_SACH_02 |
Smith |
RBD_AUSWERT_02 |
Santos |
RBD_AUSWERT_01 |
Santos |
RBD_AUSWERT_02 |