This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
A logical grouping of activities which defines a unit of work and creates an assignable responsibility.Once developed, a ‘Role’, or combination of ‘Roles’, are grouped to define positions and their process responsibilities.
Role Characteristics:
Roles are Business Group (BG) and Business Unit (BU) independent and represent the lowest level of an assignable responsibility for a given sub-process.
A logical grouping of activities which defines a unit of work and creates an assignable responsibility. Once developed, a ‘Role’, or combination of ‘Roles’, are grouped to define positions and their process responsibilities within an organization.
Describes a set of logically grouped technology enabled (SAP & Non SAP) and non-technology enabled Activities.
Activities within a Role must be identified as SAP, or other Legacy systems (i.e. ImageNow; Foodstar etc) or non-technology enabled (listed as Manual)
Transactions can be assigned to more than one ActivityRoles are used to define access to SAP Activities and scripts, test for “Segregation of
Duty” requirements and to develop training documentationA Role should be developed at the lowest common denominator, so that it cannot be
broken apart when it is being mapped to different departments, groups or positions (Most likely to be a challenge at the various locationss)
A Role is one component of a Position. Any role which is eventually assigned to a position will give that position (and eventually an individual/s) access to all Activities and scripts assigned to the role (security and training implications)
Defines responsibilities related to the new Business Process :
Provides the Project teams with guidance on ‘Position’ development
Provides Training with a framework for curriculum development
It is the basis for Security
Provides for consistent process responsibility across locations and businesses.
Basis for End User Readiness – Role Mapping Confirmation Session informing Supervisors of Roles that will be mapped to their direct reports and advising them of who will be trained.
To-Be processes are designed by process specialists based on best practice and business input.
Roles are identified as a grouping of activities (taken from the process flow) describing the specific function that needs to be performed at each step in the process. Roles are “verb” driven.
Positions are made up of a grouping or collection of “composite roles” – comparable with current business positions.