Kontakt

Ansicht
Dokumentation

Extended Authorization Concept in Release 4.02 ( RELNBANK_402_RISK_AUTH )

Extended Authorization Concept in Release 4.02 ( RELNBANK_402_RISK_AUTH )

General Data in Customer Master   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Extended Authorization Concept in Release 4.02

Description

Release 4.02 introduces an extended authorization concept for Risk Management. The concept covers the following areas:

  • Transaction authorizations
As previously, when a transaction is started in the IMG or the task level menu, the system checks authorization object J_B_TRANB to see if the user has authorization for the transaction code.
  • Customizing authorizations
Central customizing functions (such as the Maintain RM Area function) are checked against authorization object J_B_RMCUS1. Here the user must have authorization for the transaction code and the activity (display, change) i.e. same principle as for 4.01.
  • Authorization groups for application objects
A new function introduced with Release 4.02, allows you to assign an authorization group to various objects used in Risk Management (portfolio hierarchy, evaluation type and so on). When users attempt to process these objects, their authorization to do so is checked against authorization object T_RMOB_AUG. They must have authorization for both the authorization group and the activity.
If users want to use the corresponding objects in evaluations, they must have authorization for the authorization group and the activity "display".
The authorization groups are user-defined and created in the IMG.
  • Authorizations for characteristic values
As from Release 4.02, finance objects requested in evaluations are checked against authorization object T_RMCHAR_V. Users must have authorization for the characteristic name, characteristic value and report category (such as NPV, VaR, gap analysis). These conditions apply to all characteristics used in the report.

Effects on System Administration

If the delivered authorization profiles J_RM_EXPERTE and J_RM_ORDUSER are used, no further action is necessary since these profiles will be adjusted accordingly. Any user-defined authorization profiles must be extended. If you do not want to use the new authorization checks, enter "*" for all fields in authorization objects T_RMOB_AUG and T_RMCHAR_V.






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

Length: 2484 Date: 20240419 Time: 212019     sap01-206 ( 47 ms )