Track using ConfigSnapshot
As well as understanding the current setups of your E-Business Suite environments there are requirements to be able to track changes to them over time. During projects there are many reasons that it is important to be able to understand the changes made during key stages of the work, including:
- Being able to identify all records created, updated or deleted so that changes can be accurately repeated
- Understanding the impact of change on an environment introduced by major updates such as patching or upgrades
- Determining whether changes during a test cycle may have been made that have unknowingly introduced an issue
During on-going system management security settings should be tracked to ensure changes do not result in unauthorised access. This requirement covers many areas, including:
- User, responsibility and role management
- Menu changes
- Profile option settings
- Request group and request set management
ConfigSnapshot provides comprehensive baseline capability that captures setup at a particular time; any baseline can cover a single setup step, a module’s entire setup or even multiple modules. Reporting can subsequently be carried out against the historic data and comparisons can be carried out between different baselines or between baselines and the live environment data.
Even where a baseline has not been created ConfigSnapshot can use standard Oracle history fields to report data created or last updated since a particular date or by one or more specific users.
In circumstances where you require capturing every change to critical setups as they happen ConfigSnapshot can enable full audit tracking. Whenever a change is made ConfigSnapshot will capture details of what the change was, when it was made and who made it. Changes are captured whether they are made through the E-Business Suite application or via database tools such as SQL*Plus; in the latter case details of the terminal and IP address where the change was made are also captured.
Unlike many audit track solutions changes are not shown simply as their values in database tables; such reports can often be difficult to interpret as they may not display data in a way that reflects its meaning within the business applications. Table values may be codes rather than something meaningful to a user or may be an identifier to another record in a different table. The data may be part of a complex structure of data and simply seeing a change in a table in isolation without any context of how it relates to the application can be confusing.
ConfigSnapshot audit track reports always display changes in the context of how they relate to the E-Business Suite applications to ensure users can interpret them more easily.