BRM
Bussiness Role Management
Define methodology processes and steps
Define Methodology Processes and Steps
Use
In this Customizing activity, you define the methodology processes and steps for role maintenance. The
application provides a set of actions that can be used for role maintenance, such as definition, generation, and
so on. You can select which actions to use, the order, and the frequency. This is called your methodology. For
example, you can define that six steps are required to maintain a role and that approval is required after each
step.
Requirements
You have performed the Customizing activity
Assign Condition Groups to BRFplus Functions
Activities
Defining a methodology process consists of the following procedures:
1. Defining a step
SAP provides a set of actions that you can perform for role maintenance. When you define a step, you
select which actions to use and assign a name that in line with your company guidelines. For example,
you can select delivered action Action and Permissions, and name its phase as Maintain
Authorizations per your company guidelines
2. Defining a methodology process
You create the methodology processes as a framework to attach the methodology steps. You can
create as many methodology processes as you needed. For example, you may want to have one
methodology for finance role requests, and another for office administration role requests.
3. Adding steps to the methodology process
You assign the steps to the methodology processes and select the order of the steps. For example, for
finance role requests, you may want to require several approval steps and risk analysis.
To define a step, do the following:
1. Double-click Define Step.
2. Choose New Entries.
3. In the Step field, enter a unique number to identify the step.
4. In the Actions field, select san action from the dropdown list. The actions are delivered with the
application.
Note: The Provisioning action is only applicable for business roles. It allows business roles to be
reprovisioned when the associated technical roles are changed.
5. To set it as active, select the Active checkbox.
6. In the Phase field, enter a name. This application displays the phase name in the front end.
7. Save the entry.
To define a methodology process, do the following:
1. Double-click Methodology process.
2. Choose New Entries.
3. In the Methodology Process field, enter a number.
4. To set the process as active, select the Active checkbox.
5. To set the process as the default methodology process, select the Default checkbox. The
application uses this methodology process if the user does not specify a process. You can choose only
one as the default.
6. Enter a description.
7. Save the entry.
To add steps to a methodology process , do the following:
1. Select a methodology process and double-click Methodology Process Step.
2. Choose New Entries.
3. In the Step Sequence field, enter a number. This is the order for the step.
4. Select a step from the Step dropdown list. The step is mapped to a phase and action.
5. Press Enter. The application updates the Step number and enters the phase in the Action column.
6. Save the entry.
’
Creating a role in grc
If select abussiness role then
Existence one sample
Mass import
In nwbc
In notepad we get the data like this way and,copy here and save at ms excel sheet,and fill the data there and again
copy at note pad and upload again to system
Role Name [ Alphanumeric(100) ] [ Mandatory ]
Overwrite [ Alphanumeric(1) ] [Y/N]
Role Type [SIN / DRD / COM / BUS / PRF / PDP / GRP / TPL] [Mandatory]
Description [ Alphanumeric(100) ] Business Process Name [ Alphanumeric(10) ] [ Mandatory ]
Subprocess Name [ Alphanumeric(10) ] [ Mandatory ]
Project/Release Name [ Alphanumeric(10) ] [ Mandatory ]
Role Status [ Alphanumeric(3) ]
Critical Level [ Alphanumeric(3) ] Sensitivity [ Alphanumeric(3) ]
Cerification Period in Days [ Numeric(5) ] Reaffirm Period in Days [ Numeric(5) ]
Functional Area [ Alphanumeric(10) ]
Custom Field Name [ Alphanumeric(12) ]
Custom Field Value [ Alphanumeric(100) ]
Approver [ Alphanumeric(12) ]
Alternate Approver [ Alphanumeric(12) ]
Assignment Approver [ Alphanumeric(1) ] [Y/N]
Role Content Approver [ Alphanumeric(1) ] [Y/N]
Master Role [ Alphanumeric(100) ][ Only for Derived Roles ] [ Mandatory ]
Leading Organizational Level [ Alphanumeric(50) ][ Only for Derived Roles ] [ Mandatory ]
Organizational Level From Value [ Alphanumeric(50) ][ Only for Derived Roles ] [ Mandatory ]
Organizational Level To Value [ Alphanumeric(50) ][ Only for Derived Roles ]
Associated Roles [ Alphanumeric(100) ] [Only for Composite / Business Roles]
Associated Role Landscape [ Alphanumeric(10) ][ Only for Business Roles ]
Associated Systems [ Alphanumeric(32) ][ Only for CUA Composite Roles ]
Custom Profile URL [ Alphanumeric(100)] [Only for Template Role]
Custom Profile BAPI [ Alphanumeric(100)] [Only for Template Role]
Methodology Status [I - Initial / C - Complete]
Company [ Alphanumeric(10) ] System [ Alphanumeric(32) ]
Provisioning Allowed [ Alphanumeric(1)] [Y/N]
Allow Auto Provisioning [ Alphanumeric(1)] [Y/N]
System Validity [ Alphanumeric(50) ] [yyyy/mm/dd or Y,M,D]
Source System [ Alphanumeric(32) ]
Target System [ Alphanumeric(32) ]
Role Name [ Alphanumeric(100) ] [ Mandatory ]
