Implementation using ConfigSnapshot

ConfigSnapshot can be used as an integral part of any implementation or re-implementation project and where an existing implementation is being extended by configuring additional features or to adapt to changing business requirements. Providing benefit from the early planning stages through to go live and beyond, example benefits include:

Planning Configuration
ConfigSnapshot includes a flexible planning capability that enables you to define and review setup data before it is entered into the E-Business Suite. Data can either be manually entered in to the plan or existing data can be extracted selectively from an environment and subsequently modified in the plan.

Reporting of ConfigSnapshot plans is as flexible as reporting against environment data, meaning the planned configuration can be thoroughly checked for consistency and correctness prior to deploying it to the E-Business Suite environment.

Once the planned configuration has been verified it can be organised to define the order in which the setup should be applied to the target environment and any detailed instructions that should be followed during set up can be included.

Documenting Configuration
ConfigSnapshot provides automatic documentation for over 130 E-Business Suite modules and ensures your environment documentation is as accurate as possible. Rather than manual documentation which is not only time consuming to create, prone to inaccuracy and limited to showing the setup in a single static format that often makes it difficult to review, ConfigSnapshot documentation is extremely flexible; most setup data can be reported in minutes, the output is accurate and the data can be targeted and formatted depending on the requirement both to help project teams review and verify existing setups and to analyse further setup requirements.

Deploying/Migrating Configuration
For several areas is it possible to load new configuration from a plan into the E-Business Suite environment or migrate selected setup data from one environment to another rather than manually re-keying data.

For areas where migration is not currently supported it is still a simple exercise to automatically generate documentation showing exactly what configuration must be entered into the target environment and can be configured to show this in any particular order that should be followed.

Once configuration has been entered in the target environment, whether by automatically loading it or by manually entering it, it can be directly compared against the plan or source environment to ensure all setup was completed correctly.

Managing Change throughout the Project
Many projects will progress through well-defined phases and setups must be controlled during each stage. As well as being able to review the overall setup at any point in time projects benefit from being able to isolate the changes made during specific phases; this both enforces strict change control but also allows teams to focus phase testing on those areas that have changed rather than performing broader testing that may spend unnecessary time on areas of the application unaffected during the phase.

ConfigSnapshot’s baseline capability enables teams to selectively capture setups at any point in time, for example at the start of the phase, and then be able to compare current setups against the baseline, allowing them to confirm all changes made as part of a phase.

Managing Setup across Multiple Environments
As projects progress setups will be managed though multiple environments, as a minimum a development, test and production environment. Depending on the complexity of the project the setup is likely to be completed on each environment over a period of time rather than at a single time for any one environment. This adds a further complexity to managing the setup; as well as ensure all the setup had been documented it is necessary to understand what setup has and has not been deployed to any environment. There is a high risk in any project that some setups are incorrectly configured or missed entirely. The vigilance in try to prevent this consumes a large amount of project resource that could be better focussed on ensuring the project delivers the best solution to the business within a reasonable budget.

ConfigSnapshot enables organisations to enforce tight configuration control without requiring an unwieldy or time consuming process to achieve it. At any stage a comparison or transformation report can be run to highlight any differences that exist between two or more environments or to generate details of what configuration changes would need to be made to a target environment to get it in synch with a source environment. Project teams can use these to create a detailed plan for the next deployment phase of the project.

Planning Security
Security is a complex area within the E-Business Suite with many setups affecting what functions, programs and data users are able to access, including:
  • Users, Responsibilities and Roles
  • Menus
  • Report and Request Groups
  • Profile Options

A challenge during projects is that it is not feasible to test every single security setup to ensure that any one user can access the functionality or data they should be able to and be prevented from accessing any they shouldn’t. This is even more complex when requirements such as segregation of duties are considered.

ConfigSnapshot provides flexible reporting to review all of these setup areas to enable the project team to test key access controls and then ensure that these have been deployed correctly across the entire user base.