Free Trial

Oracle® E-Business Suite & Cloud Applications
Configuration Automation and Control

Reduce Time - Reduce Errors - Reduce Cost - Reduce Risk

The Challenge:

Effective management of application setup is essential during upgrades and there are particular challenges that organisations must overcome to ensure a successful upgrade project. The complexity of the E-Business Suite and Cloud Applications, from both functional and technical perspectives, makes this a time consuming and costly process.

Most E-Business Suite systems include customisations that may be affected by changes during the upgrade. These must be identified and assessed for potential impact. The scope of what should be considered a customisation is broad and all such areas should be considered. As well as custom database objects and programs it is key to include any setups that incorporate some code element in their definition.

There are several possible effects on application setups and each of these should be considered:

  • Existing implementation setup may be modified or lost
  • Seeded data may be modified or added and affect key business processes
  • New setups may be automatically created based on existing implementation setups where functionality areas change significantly; it is key to understand what has been configured, what is appropriate and what changes or extensions may be required

A huge challenge is the potential effect on security by the upgrade; the introduction of new forms, functions and concurrent programs etc. must be understood and this is difficult within both the E-Business Suite and Cloud Applications. The nature of areas such as menu structures and permissions can lead to users automatically gaining access to functionality that should be controlled.

Further setup changes will almost certainly be necessary after the main upgrade process. These must be managed to ensure they are correctly repeated during each iteration of the upgrade.

Upgrade projects consist of several iterations and it is essential to accurately repeat all required steps for each. A missed or incorrect step could have serious consequences for the success of the project.

Close control of testing cycles of the upgrade are also key to its success.

Identify more than 45 types of customisation automatically

Determine changes to seeded data that might allow users to access new forms / concurrent programs

Identify down to the code level which customisations are affected by patching

How ConfigSnapshot Helps:

ConfigSnapshot is able to identify existing customisations and present them in an easy to understand format enabling project teams to assess whether each individual customisation should be retained after the upgrade. This allows a comprehensive test plan for customisation areas to be established early in the project.

Further, ConfigSnapshot is able to determine the likely impact of the upgrade on each retained customisation showing each affected object referenced in the code and highlighting in the code itself each instance of the object. Development teams can scope and plan the work required much earlier than if they were manually checking each code item; saving significant time and reducing the risk that the work required greatly exceeds any initial estimate.

Directly comparing the pre and post upgrade application setups allows any changes or additions to be identified. Teams can quickly determine any actions that might be required to deal with unexpected effects and to plan effectively based on other changes, whether to implementation specific or seeded data. Project teams can identify new functions and programs introduced by the upgrade to determine which should be controlled and which users have inherited access so any necessary restrictions can be applied.

Several features are available to simplify managing any setup changes made, including:

  • Automatic documentation of existing setup allowing teams to base decisions on accurate information
  • Ability to plan new setups directly in ConfigSnapshot prior to entering them in the E-Business Suite rather than using static manual documents. Teams can report flexibly on planned setups and also compare setups in the E-Business Suite directly to planned setups ensuring they are completed correctly.
  • Automatically deploy application setups from the plan to the environment via ConfigSnapshot’s migration capability
  • Record all setup changes made to the upgraded environment removing the duplication of effort associated with manually maintaining setup documentation. This also provides a clear recipe of actions to be followed during each iteration.

ConfigSnapshot enables you to directly compare the setups of each iteration of the upgrade process quickly identifying any differences. The project team can assess whether any difference is expected or whether it indicates a step has not be completed correctly during a particular iteration allowing corrective action to be taken. This provides further quality assurance for the upgrade of the Production environment to minimise the risk of error.

ConfigSnapshot provides change tracking to allow all environments to be controlled; ensuring any modifications can be identified. This enables tracking both of any additional setups required for the upgraded version and during key test cycles to ensure any changes made are accurately captured.

Demonstration & Free Trial

Request a web demo and then download a trial version of ConfigSnapshot absolutely FREE
Register now by providing your details below:

"ConfigSnapshot is no doubt a great tool for generating comparison reports to identify differences in different e-Business environments. However, the real power lies in the migration component. The migration engine is extremely accurate and the execution precision prevents errors during configuration migrations. The details window is very helpful for configuration visualizations. DevOps is about automation, ConfigSnapshot is the bridge between IT and development"

Technical Architect – Industry: Leading Global Technology and Services Innovator