The purpose of this page is to clarify the understanding of the system logic and requirements in relation to the subprocess tab within the organization screen.
In the subprocess tab, internal control managers can assign a subprocess to an organization unit. This process is described in detail in this wiki page.
The first time a user accesses the subprocess tab, there is no content in it. To add a subprocess to the organization, internal control managers or organization owners can assign it through "Assign Subprocess" button.
Assign Subprocess Steps
Once the assign subprocess button is pressed, the following screen appears:
If you receive the below message, it means that the subprocesses were not maintained at the central level.
To know how to maintain the objects at central level, access the following wiki page:
Step 1 - Select Subprocess
In this step, a subprocess must be selected from the central subprocess hierarchy. In my system, there is only one subprocess created. On this screen, the users have 4 basic information regarding the subprocess:
- Name of the subprocess
- Name of the Process
- Description of the subprocess
- Symbol showing whether the subprocess is enabled for shared services
Upon pressing the Next button, user is guided to Shared services step.
Step 2 - Shared Services
If the option 'Shared Services Provider' is not enabled at Organization General Tab, step 2 will be skipped.
The first prerequisite to use Shared Services is to enable Shared Services Provider radio button.
Now, step 2 is available when assigning a subprocess to the organization unit.
During the assignment, there is an option (checkbox) to make the functionality available for a specific subprocess.
Step 3 - Allow Local Changes
In this step, the user has two options for the column "Allow Local Changes":
- Yes > The object allow changes at local level, after the objects have been assigned to organizations
- No > The objects are managed centrally through the Business Processes link
You also have the option to customize and select specific field to allow local changes while managing the objects centrally.
For more information, check allow local changes configuration page.
Step 4 - Select Controls
In this step, users have the option to remove controls from the subprocess.
Step 5 - Select Risks
Here, users can select which risks will be moved within the control or subprocesses. If there are no risks assigned to the objects, this step is skipped.
At this screen, users will review and finally submit the assignment.
When submit button is pressed, a confirmation screen will appear.
Users must press finish button in order to complete the operation.
However, the process is not saved yet. The organization Save button needs to be pressed to create the data in GRC tables.
At this point, users can see a local subprocess and their local controls.
The following relationship is establish in the database, more specifically, in HRP1001.
Click here to open the local subprocess and know more about it.