Regional-focused Compliance - Governance, Risk, and Compliance Topic for Oracle Applications - page 422

Once the perspective is created within a module, you can maintain it as follows:
• View perspectives, deine their association with the module, and edit the list.
• Associate a perspective with objects within the module, and specify if a
perspective is required for each object. This allows the same or different
perspectives to be associated to objects within modules.
• For example:
° You may want to put perspective values on control objects to identify
the region to which each belongs, whereas you may not want this on
your corporate risk
° You may want to associate the risk object, but not the control object,
to a project perspective
° You may want the organization perspective to be used for both the
risk and control objects
You cannot delete a perspective if data is associated with it. The Delete icon and
button are inactive for rows representing these perspectives in the perspective grid.
But the perspective can be disabled through use of the status flag, which can be set to
Inactive . The version history is updated for this change as well.
If the perspective is changed from not required to required, nothing happens to the
data. This indicates only that the perspective value is required when a save action is
initiated on an object.
Loading data
eGRCM provides the ability to upload the initial set of operational data by using
seeded import templates. Two templates are provided for this purpose:
• Financial Governance Import Template : Use this template
( FinancialGovernanceImportTemplate.xml ) to load data into the
Financial Governance module
• New Module Import Template : Use this template ( NewModuleTemplate.xml )
to load data into a custom eGRCM module
The import templates support the following objects and associations:
• Processes (base object).
• Risks.
• Controls.