<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Question Re: user review in Additional Q&amp;A</title>
    <link>https://community.sap.com/t5/additional-q-a/user-review/qaa-p/9597943#M107433</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are these reasons for rejection can be aggregator in existing workflow?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so when someone turning away a request would appear to be chosen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 20 Aug 2013 18:52:00 GMT</pubDate>
    <dc:creator>former_member203442</dc:creator>
    <dc:date>2013-08-20T18:52:00Z</dc:date>
    <item>
      <title>user review</title>
      <link>https://community.sap.com/t5/additional-q-a/user-review/qaq-p/9597941</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; I work in GRC v5.3 SP19&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would like to know more about the option of review users in CUP, especially reasons for rejections,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is its function?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Aug 2013 16:24:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/additional-q-a/user-review/qaq-p/9597941</guid>
      <dc:creator>former_member203442</dc:creator>
      <dc:date>2013-08-12T16:24:10Z</dc:date>
    </item>
    <item>
      <title>Re: user review</title>
      <link>https://community.sap.com/t5/additional-q-a/user-review/qaa-p/9597942#M107432</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;User Review&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;User review allows designated approvers to review the access assigned to a user and the&lt;/P&gt;&lt;P&gt;segregation of duties risks violated by a user. These two procedures are referred to as User&lt;/P&gt;&lt;P&gt;Access Review and User SoD Review.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Features&lt;/STRONG&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Options: &lt;SPAN style="font-size: 10pt;"&gt;You configure review parameters such as reviewer, require admin review, review &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;instructions URL, and so on.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;Coordinator: &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;Choose a coordinator for each reviewer. Access Control uses the coordinator information &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;to generate reports you can use while managing the review process.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;Request Review: &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;Administrators can review requests, and choose to cancel them or change the &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;coordinator and reviewer roles.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;Manage Rejections: &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;Authorized users can search for rejected users, and generate or cancel review requests.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;&lt;SPAN style="font-size: 10pt;"&gt;Reason for Rejection: &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;You configure the rejection reasons, descriptions, and reason codes.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;UAR Load Data Tasks: &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;Create tasks to enable selective user access reviews based on role attributes such as, &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;criticality and names, or user attributes such as, user ID and user groups.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Performing User Access Reviews&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;The User Access Review (UAR) feature provides a workflow-based review and approval&lt;/P&gt;&lt;P&gt;process for user access requests. The periodic reviews of user access are performed by&lt;/P&gt;&lt;P&gt;business managers or role owners, and the system automatically generates the requests&lt;/P&gt;&lt;P&gt;based on the company’s internal control policy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Features&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An automated process for the periodic access review.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Decentralized review of user access.&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;Workflow of requests for review and approval.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;Automatic role removal, if desired.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;Status and history reports to assist in monitoring the review process.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;Audit trail and reports for supporting internal and external audits.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;Support for back-end systems integrated with Access Control as well as legacy systems.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Use of the user UAR feature requires configuration in multiple capabilities. The information in&lt;/P&gt;&lt;P&gt;this section provides details about the user access review feature, its process options,&lt;/P&gt;&lt;P&gt;configuration, and use.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ERM -&amp;gt;&lt;/STRONG&gt; You configure system connectors. This is required for transaction usage and&lt;/P&gt;&lt;P&gt;for user-role assignment information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;RAR -&amp;gt;&lt;/STRONG&gt; You configure connectors. This is required for alert generation to provide&lt;/P&gt;&lt;P&gt;transaction usage information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;CUP -&amp;gt;&lt;/STRONG&gt; You define connectors, configure UAR, configure workflows, and define&lt;/P&gt;&lt;P&gt;coordinators.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Roles in the UAR Process&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Administrator: &lt;/STRONG&gt;This person has the AE_Admin UME role assigned for Access Control. They can&lt;/P&gt;&lt;P&gt;perform general CUP administrator tasks in addition to UAR-specific administrator tasks, such as&lt;/P&gt;&lt;P&gt;cancelling UAR requests and regenerating requests for rejected users.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;User’s Manager:&lt;/STRONG&gt; The direct manager of a user as defined in the User Details Data Source.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Role Owner:&lt;/STRONG&gt; The role owner specified in CUP master data.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Reviewer:&lt;/STRONG&gt; This term refers to the approver at the Reviewer stage. The Reviewer may be&lt;/P&gt;&lt;P&gt;the user’s manager or the role owner.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Coordinator:&lt;/STRONG&gt; The Coordinator specified in CUP master data. The Coordinator is assigned to&lt;/P&gt;&lt;P&gt;Reviewer. They monitor the UAR process and coordinate activities to ensure the process is completed in &lt;SPAN style="font-size: 10pt;"&gt;a timely manner.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Process Options&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;You choose from multiple process options to determine the approvers of the UAR requests.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Admin Review: &lt;SPAN style="font-size: 10pt;"&gt;You decide whether to enable Admin Review. This configuration option provides an opportunity for the &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;administrator to validate the request data after the requests are generated (by the UAR Load Data job) &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;but prior to generating workflow tasks (by the UAR Update Workflow job). If the Reviewer information is &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;incorrect or missing, the administrator can modify the data prior to generating workflow tasks and &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;notifications. The administrator can also delete requests.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;Reviewer Stage: &lt;SPAN style="font-size: 10pt;"&gt;You decide whether the Reviewer stage will be addressed by the User’s Manager or the Role Owner.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;Security Stage: You decide whether to have a security stage. A security stage is mandatory if you do not have automatic &lt;SPAN style="font-size: 10pt;"&gt;provisioning enabled. The security stage may be desired even when automatic provisioning is enabled &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;so that security personnel can ensure accurate data prior to provisioning.&lt;/SPAN&gt;If a security stage will be included in your approval workflow, you must decide whether security personnel &lt;SPAN style="font-size: 10pt;"&gt;will be able to modify the direction previously noted by an Approver. For instance, a security team &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;member may decide to retain basic roles that have been inappropriately marked for removal by an &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;approver.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;Additional Approver Stage: You decide whether you will have an additional stage with the approver derived by a Custom Approver &lt;SPAN style="font-size: 10pt;"&gt;Determinator (CAD). The fields available in the UAR CAD differ from those available in the standard CUP &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;CADs. The fields available are in the UAR CAD are:&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;OL&gt;&lt;LI&gt;Application&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;Request type&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;Role(s) being reviewed&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;UL&gt;&lt;LI&gt;Instruction for Reviewers: &lt;SPAN style="font-size: 10pt;"&gt;You can provide detailed instructions for reviewers to supplement the content of the notification emails. &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;The level of instruction for approval of periodic access reviews might be more extensive since it is an &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;infrequent process and may involve reviewers who do not perform routine approval of requests to create &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;or change accounts.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Configure Rejection Reasons&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Rejection reasons are mandatory when rejecting a review request. You must upload the reason codesand descriptions using a template.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Procedure&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Go to Configuration -&amp;gt; User Review -&amp;gt; Reason for Rejection. The Reason for Rejection screen&lt;/P&gt;&lt;P&gt;appears.&lt;/P&gt;&lt;P&gt;2. Under Import Rejection Reasons, click Download Template. The template opens in Excel.&lt;/P&gt;&lt;P&gt;3. Complete the required information and save the template.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if this concerns your query. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you, &lt;/P&gt;&lt;P&gt;Fernando&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Aug 2013 20:01:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/additional-q-a/user-review/qaa-p/9597942#M107432</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-08-13T20:01:35Z</dc:date>
    </item>
    <item>
      <title>Re: user review</title>
      <link>https://community.sap.com/t5/additional-q-a/user-review/qaa-p/9597943#M107433</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are these reasons for rejection can be aggregator in existing workflow?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so when someone turning away a request would appear to be chosen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Aug 2013 18:52:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/additional-q-a/user-review/qaa-p/9597943#M107433</guid>
      <dc:creator>former_member203442</dc:creator>
      <dc:date>2013-08-20T18:52:00Z</dc:date>
    </item>
  </channel>
</rss>

