What is iSetup:
- iSetup is a tool that supports initial implementations of the Oracle E-Business Suite.
- iSetup mainly supports the ongoing maintenance of setup data. This includes simplifying the migration of setup data – from one instance to another; aiding in cloning setup data; and keeping track of setup data among the different environments.
- The main focus of iSetup is to help migrate functional setups from one E-Business Suite instance to another. During migration, setups can be extracted selectively using filters on setup attributes. Extracted setup data can be optionally transformed before loading into target instance.
- Another capability of iSetup is setup comparison, whereby a report can be generated on the exact differences of setup information between two instances or from the same instance across different timelines.
The iSetup solution addresses all the CRP business needs. You can create first time setups based on requirements gathered. You can use the same configuration to populate multiple instances or make refinements before loading into subsequent instances.
Uses of iSetup:
- Initially EBS implementation involves a manual setup using either a Manual Entry or Business Accelerators . iSetup can help start such implementation scenarios by loading a CRP instance from an industry best practice configuration.
- iSetup provides an enterprise wide repository to store business specific configuration snapshots. These Gold copies can be used to configure a new instance, thus avoiding re-configurations.
- iSetup expedites implementations by providing out-of-the-box migration templates tailored to suit various implementation phases.
- iSetup can also help promote setups from CRPs to multiple test, development and production environments.
- iSetup enforces business validations inherent in interfaces owned by Oracle product modules.
- iSetup can be used to copy all setups striped by an Operating Unit and move it to another EBS instance using Hierarchical selection set feature which cascades filter criteria to all related setups in the selection set template.
- In a roll-out scenario, iSetup can be used to replicate the setups tied to an existing Operating Unit to a new Operating Unit.
- iSetup can be used to migrate incremental setups selectively across instances using filters on setup attributes. Instead of cloning the entire EBS instance, iSetup can be used to move required setup data from a production instance to a testing instance. New setups can be added to the test instance and those specific setups can be selectively migrated to production instance while the instance is up and running. This minimizes the need to redo setups, and execute expensive clone activities.
- iSetup provides standard and comparison reporting features. Standard reports help in documenting the setups in regular PDF/RTF/Excel that serve as a standard reference for implementation teams.
- iSetup comparison reports can help in troubleshooting functional setups by enabling users to compare setups across instances or timelines.
Configuration Contorls Governor(CCG) (formerly Integra Apps):
CCG helps you reduce financial loss, compliance cost, and audit effort related to your business application setups. It does this by identifying setup changes, storing them in a central repository, and reporting them. CCG can operate both automatically and on demand. It provides role-based security to ensure the privacy of sensitive business data.
Why CCG need to be used:
CCG’s Change Tracker is useful for customers who want their business users to be able to:
- Activate/deactivate Change Tracking for all business application setups without a technician’s assistance Interpret setup change information without a technician’s assistance.
- Receive alerts when setup changes occur .
- Use a single repository of all Change Tracking information for all business application setups.
- Implement controls without employing Table Audit
CCG to Create BR100
Create a BR100-like framework in Oracle GRC Manager.Enter your business requirements into the framework, and import the setup data that’s captured by CCG. Then, add your comments in the framework as desired, and take any needed compensating, remediation, or mitigating steps. If you’re wondering why CCG doesn’t let you annotate the setup data it captures, it’s because that would be at odds with a key GRC best practice: providing a single point of interaction between GRC users and all the data they need to make good decisions. Only solutions like GRCM and GRCI permit that holistic view, and only solutions like GRCM permit the automation of policies and workflows that rely on data from multiple sources, CCG being just one.