In C4C you can create custom reports where you can specify selection values that are fixed at design time and are not changeable during the runtime execution of the report. This can be done when defining custom reports, using ‘Set Fixed Value Selections’ in Step 4 of the Report creation.(Characteristic Properties)
For example, if a manager should see only the Opportunities of his Reporting Line, or an Employee who should see only those opportunities that he is responsible for, then
This would be a use-case to have restrictions for the Employee ID on the report. By placing fixed value selections on the Employee characteristic, the system can determine which opportunities would be selected based on the person logged in and his ownership of the Opportunities, or his team’s ownership of the Opportunities, etc
One can argue that using Role Based Authorizations, you can restrict the data that the user is allowed to see. While this is true and highly recommended,r based authorizations would bring up say all opportunities that the user is authorized to see - including those where he is the employee responsible or has access to it by virtue of being in the associated account team or territory team depending upon how the access restrictions were set for his role. If you need it to be even more specific, to show only those reports where he is the Employee Responsible, you can use Fixed value selections as explained above
Similarly, if you want to show the results for a specific year only – eg: Current Year reports, then you can use the relative selects offered on the Date fields to pre-set the date field selection values which cannot be changed by the user
A lot of characteristics offer relative selects that can be used in Fixed Value Selections - Eg Sales Unit, Party ID etc. The cool thing is that although we use Fixed Value Selections, using a Relative Select option for a Fixed Value Selection, you are actually making it dynamic in nature while keeping the data controlled.
Eg: A fixed value selection for the Employee ID of Opportunities, where instead of specifying an actual Employee ID, you specify a Relative Select Option like ‘Employee – My User Name’. This makes the report dynamic in the sense that based on the logged in employee, the system would adapt to show the results where the logged in employee is the Employee Responsible.
User Tara logs in, and can see only those Opportunities where she is the Employee responsible
Similarly, for a logged in manager, if the relative select is ‘My Teams’, then based on the logged in employee, the system would dynamically resolve the team’s data to be retrieved.
User Tara logs in and now can see reports for her team (from the Org chart). In the following example, Anjana is the only employee who reports to Tara and has Opportunities
What’s even better is, that you can define your own custom relative selects, and use them for the Fixed Value Selections. Check out my blog for Custom Relative Selects here:
Defining Fixed Value Selections on Custom Reports would imply that these characteristics would not be available as a selection parameter for report execution since these have already been defined by the Admin during report creation. The report would be launched with the values already specified
Eg: Having specified Employee ID with Fixed Value Selections, this report does not allow the Employee ID characteristic to be pulled in as a selection parameter in the Web View of the Report
Thanks,
Vinita
For example, if a manager should see only the Opportunities of his Reporting Line, or an Employee who should see only those opportunities that he is responsible for, then
- You would need to pre-populate the selection for the Employee characteristic and
- Ensure that this is not changeable at runtime by the end user
This would be a use-case to have restrictions for the Employee ID on the report. By placing fixed value selections on the Employee characteristic, the system can determine which opportunities would be selected based on the person logged in and his ownership of the Opportunities, or his team’s ownership of the Opportunities, etc
One can argue that using Role Based Authorizations, you can restrict the data that the user is allowed to see. While this is true and highly recommended,r based authorizations would bring up say all opportunities that the user is authorized to see - including those where he is the employee responsible or has access to it by virtue of being in the associated account team or territory team depending upon how the access restrictions were set for his role. If you need it to be even more specific, to show only those reports where he is the Employee Responsible, you can use Fixed value selections as explained above
Similarly, if you want to show the results for a specific year only – eg: Current Year reports, then you can use the relative selects offered on the Date fields to pre-set the date field selection values which cannot be changed by the user
A lot of characteristics offer relative selects that can be used in Fixed Value Selections - Eg Sales Unit, Party ID etc. The cool thing is that although we use Fixed Value Selections, using a Relative Select option for a Fixed Value Selection, you are actually making it dynamic in nature while keeping the data controlled.
Eg: A fixed value selection for the Employee ID of Opportunities, where instead of specifying an actual Employee ID, you specify a Relative Select Option like ‘Employee – My User Name’. This makes the report dynamic in the sense that based on the logged in employee, the system would adapt to show the results where the logged in employee is the Employee Responsible.
User Tara logs in, and can see only those Opportunities where she is the Employee responsible
Similarly, for a logged in manager, if the relative select is ‘My Teams’, then based on the logged in employee, the system would dynamically resolve the team’s data to be retrieved.
User Tara logs in and now can see reports for her team (from the Org chart). In the following example, Anjana is the only employee who reports to Tara and has Opportunities
What’s even better is, that you can define your own custom relative selects, and use them for the Fixed Value Selections. Check out my blog for Custom Relative Selects here:
Defining Fixed Value Selections on Custom Reports would imply that these characteristics would not be available as a selection parameter for report execution since these have already been defined by the Admin during report creation. The report would be launched with the values already specified
Eg: Having specified Employee ID with Fixed Value Selections, this report does not allow the Employee ID characteristic to be pulled in as a selection parameter in the Web View of the Report
Thanks,
Vinita
- SAP Managed Tags:
5 Comments
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
