To add values to a Risk Type list of values, you need to add the lookup codes to the GRCM_RISK_TYPE Lookup Type. Here's how you can do it:
* Navigate to the Lookups page in the Setup and Administration work area.
* Click on Create Lookup to open the Create Lookup page.
* In the Lookup Type field, enter GRCM_RISK_TYPE.
* Enter a code in the Lookup Code field. The code should consist of 30 or fewer characters, use upper-case for alphabetic characters, and underscores to fill the space between words.
* In the Meaning field, enter the text that will be presented in the list of values.
* Ensure that the combination of lookup code and meaning is unique.
* In the Status field, select Active to make the new value available for use.
References:
* Manage Lookups documentation from Oracle1.
* Risk Management User Guide2.

Oracle Advanced Access Controls is designed to enforce segregation of duties within your applications. It identifies users with sensitive access and separation-of-duties conflicts by analyzing their assigned roles and privileges. When these authorizations, individually or in combination, create the potential for fraud or significant error, Oracle Advanced Access Controls flags them, helping to prevent such risks.
References:
* Overview of Oracle Advanced Controls1.
* Oracle Advanced Access Controls identifies users with sensitive-access and separation-of-duties conflicts2.

When setting up assessments in Financial Reporting Compliance, the following tasks should be completed:
* Identify the type of assessments included in each assessment cycle: This involves understanding the different assessment activities that will be conducted and ensuring they align with the objectives of the assessment cycle1.
* Determine if control assessments are planned ahead of time or are run impromptu: This task involves deciding whether the assessments will be scheduled as part of a batch (planned) or initiated on an individual basis (impromptu) as the need arises1.
* Determine whether assessments templates, plans, and completed assessments need to go through a review and approve workflow: This includes establishing a process for reviewing and approving the assessment templates, plans, and the assessments themselves to ensure they meet the required standards and objectives1.
References:
* The Oracle documentation on Financial Reporting Compliance provides detailed information on the overview of assessments, including the creation and management of assessment templates and plans, as well as the initiation of assessment batches or impromptu assessments1.
* Additional resources from Oracle outline the processes for setting up and completing assessments, emphasizing the importance of planning, scheduling, and reviewing assessments to ensure compliance and effective risk management234.

To secure controls based on the company organization using the Oracle Risk Management import template, the following worksheets are essential:
* Perspective Items: This worksheet is used to define values for all perspectives. Each value must have a type code that matches the type code for the perspective it belongs to, which is set in the Perspective worksheet1.
* Controls: The Controls worksheet supplies data that defines the controls themselves. This is crucial for establishing the specific controls that will be secured1.
* Perspective-Control: This worksheet defines how perspective values relate to controls. It is necessary to associate specific controls with the relevant organizational perspectives1.
References:The information is based on the Oracle Risk Management documentation, which details the use of the Data Migration template and its worksheets for importing various types of data, including object data, transaction data, and association data1.

* Filter A is used to select payments from the specified business units (BU1, BU2, BU3, and BU4), excluding BU5.
* Filter B groups the payments by each supplier and sums the payment amounts. This filter is then used to identify suppliers who have been paid more than $100,000 USD across the selected business units.
References:The information is based on the Oracle Risk Management Cloud documentation and resources that discuss transaction models and filtering criteria for identifying specific conditions such as payment amounts to suppliers1.