SAP Note

615670 - Authorization check in operational reporting Version 3 Validity: 19.03.2004 - active Language English

Header Data
Released On Release Status Component Priority Category 19.03.2004 10:45:13 Released for Customer CRM-BTX-ANA-RFW Reporting Framework Recommendations / Additional Info Consulting

Other Components CRM-BTX-BF-AU Authorization Check

Symptom
Authorization check not correctly performed in the Reporting Framework

Other Terms
1Order Business Transaction User Profile Role Performance Incorrect SQL trace Reporting Framework Operational Reporting BW extraction Datasource Infosource 0 data records selected 0 documents were found for this selection criteria

Reason and Prerequisites

Buffers for authorization values are not up to date

Solution
This note describes how to influence the behavior of the authorization check during operational reporting, that means - how to switch off buffers for authorizations values - how to switch off authorization check in the Reporting Framework - how to optimize the generated SQL statement with the authorized values. These modifications of the authorization check can be done centrally for all users by modifying the middleware parameter table SMOFPARSFA and can be done individually for each user by modifiying the user parameter 'CRM_RF_PERFORMANCE'. 1) For All users For this, the system administrator should set up in middleware table SMOFPARSFA the parameter 'CRMRF' (Field PARSFAKEY) and 'SETTINGS_REPORTING_FRAMEWORK'(Field PARNAME) with value (Field PARVAL1) - 'A' To switch off the authorization checks - 'B' To switch off Buffers (authorization check is still active but buffers are not anymore used). It makes sense only if you are doing modification in the userids and if you don't want to use buffers temporarely. - 'U' to split database request into separate queries, this might be useful to improve performance if the generated SQL statement for the authorization is too complex for the database optimizer. - Do not use value 'O' or 'S' - Other value : authorization check and buffers are activated 2) Only for 1 user First of all, in order to be able to change the behaviour for an individual user, the parameter 'CRMRF' 'SETTINGS_REPORTING_FRAMEWORK' in the middleware table SMOFPARSFA should be set up with a value different from space ('A', 'B', 'U' or other value). With this setting, each user can influence the behaviour of the authorization check for its own userid with the user parameter 'CRM_RF_PERFORMANCE' and with values 'A', 'B' or 'U' (these values means the same thing as for middleware table) Remark: by default middleware table is not set up with parameter 'CRMRF' 'SETTINGS_REPORTING_FRAMEWORK', in this case authorization check and

buffers are activated for all users (same think as other value). But the difference is that without this parameter in middleware table there is no chance to change the behavior for 1 particular user, indeed in that case user parameter 'CRM_RF_PERFORMANCE' is not considered.

Validity
Software Component From Rel. To Rel. And Subsequent BBPCRM 400 400

References
This document refers to:
SAP Notes 692195 FAQ: Sales Analytics and CRM-BW data Extraction

This document is referenced by:

SAP Notes (1) 692195 FAQ: Sales Analytics and CRM-BW data Extraction