This self-study course walks you through the implementation planning process for Oracle Configuration Controls Governor (CCG) 5.5.1.

This online self-study couse introduces you to Oracle Configuration Controls Governor (CCG) 5.5.1.  You will learn how to navigate through CCG 5.5.1.  You will also learn how organizations can use Oracle CCG 5.5.1 to facilitate Oracle Application Configuration Management.  Similarly, you will learn how organizations can use Oracle CCG 5.5.1 to track and monitor changes to key application configuration control parameters.

You will learn that organizations can leverage the functionality of Oracle CCG 5.5.1 during an Oracle Financials implementation or upgrade to enforce the implementation of approved "baseline controls", track differences in the configuration of the Oracle Financials between instances, ledger sets, ledgers, and operating units.

This online self-study course illustrates how you can use Oracle CCG 5.5.1 to Create Snapshots of the configuration parameters for Oracle Financials.  You will learn how establish a "baseline" of the Oracle system controls.

You will learn how to:

• Create a Definition
• Test the Definition
• Lock the Definition
• Use the Definition
• Share the Definition

This online self-study course illustrates how you can use Oracle CCG 5.5.1 to Compare Snapshots.  CCG identifies differences between ERP application setups by comparing snapshot occurrences. You can compare occurrences from different points in time and different ERP instances.

To summarize, you will:

• Search for an auto-generated change tracking definition.
• Edit the definition to specify what to track.
• Run the definition to deploy change tracking functionality to the ERP instance.
• View the change tracker.
• Specify change tracker queries and alerts

This self-study course illustrates how to Create Users, Roles and Security Groups in Oracle CCG 5.5.1. 

Typically, each CCG user has his or her own username and password. This lets you control each user’s login access, roles and permissions. Roles determine the menu items the user sees; permissions control the ERP data the user can access. Rather than granting permissions directly to users, you grant them to security groups, then assign users to the security groups. Users who do not belong to any security groups will not be able to access any ERP data. Similarly, users who do not have any roles will not see any CCG menu items.