In Oracle Risk Management, when a business owner is assigned a new role, there may be a delay before the worklist reflects this change. This is because the system needs to refresh the data to include the new role assignments in the worklist generation process. If the business owner responsible for the “Order to Cash” perspective does not see any worklists for the generated incidents, despite having the correct functional privileges and data access, it is likely due to the recent assignment of the role. The system has not yet refreshed the worklists to include the business owner’s new role, which is necessary for them to view the worklists related to the generated incidents.

References:

• Oracle Risk Management Cloud documentation on role assignments and worklist generation1.
• Oracle support documents detailing how to regenerate worklists after changes to GRC security components2.

• Data Security Policy: The Control Manager must be assigned the correct data security policy to access the controls. Without this policy, the manager will not have the necessary permissions to view the controls within the application1.
• Association of Perspective Hierarchy: The Perspective Hierarchy must be associated with the Control Object for the controls to be visible. This association ensures that the controls are correctly linked to the organizational structure within the application2.
• Approval of Perspective Hierarchy: The Perspective Hierarchy needs to be in an Approved state. If it is not approved, the controls related to it will not be displayed for review in the application1.

References:

• The Oracle documentation on viewing and editing advanced controls provides insights into the necessity of correct data security policies and the approval status of the Perspective Hierarchy1.
• The overview of Oracle Advanced Controls explains the importance of associating the Perspective Hierarchy with the Control Object2.

• In a model: You can create a new condition logic filter within a model, select the specific operating unit attribute and its value, and then apply an exclusion through the advanced options checkbox. This method allows you to set up a filter that specifically targets the operating unit you wish to exclude.
• Create Access Global Condition page: By navigating to this page, you can create a new condition logic filter, again selecting the operating unit attribute and its value, and perform an exclusion through the advanced options checkbox. This approach is similar to the first but is done through the global condition page, which may offer a broader scope of application.

References:The information provided here is based on Oracle’s documentation on Risk Management and Compliance, which outlines the procedures for excluding an operating unit in scenarios where there is insufficient personnel to maintain segregation of duties12. For a detailed understanding of these processes, refer to the official Oracle documentation.