Low cost of ownership - high ROI
With a fast install time, easy learning curve and many advanced cost-saving features, Rev-Trac provides an easily demonstrable return on investment.
Because Rev-Trac lives in SAP, there are no hidden extras and no additional network, security, disaster recovery plan, DBA or desktop rollout requirements.
Rev-Trac's place in the change management picture
Rev-Trac is installed in all systems within your SAP landscape and manages all changes as that landscape evolves. It does not replace the change management or help desk system you now use to manage changes across your whole organization.
System requirements
Rev-Trac 5 is compatible with all SAP solution-based systems from SAP 4.0 onwards.
Installation
Most sites install Rev-Trac, load system histories and begin full system monitoring in one day. Implementing the actual Rev-Trac change management process can take one to two weeks, as the organization finalizes decisions regarding workflow, approvers, etc. Training time is typically one to two hours in the classroom, or 30 minutes of training one-to-one.
|
|
Technical specifics
• SAP certified as an ABAP add-on for SAP 4.6C, 4.7 and NetWeaver 7
• Can manage mixed SAP versions from 4.0 onwards within a single installation
• Fully integrates with CTS, CTS+, and TMS, deploying ABAP, non-ABAP, and mixed transports
• Employs standard SAP security model, with SAP passwords, authorizations and profiles
• Allows business issues to be defined before changes are made, or on-the-fly at the time of change
• Provides complete flexibility in the definition of approval processes, organizational models and migration strategies
• Allows the creation of rules specifying what information (e.g., budgets, specifications) must be associated with business issues at different points in their lifecycle
• Provides fully flexible migration scheduling, and automatically promotes business issues through their lifecycle after successful automation
• Automatically notifies users via email when work is ready for approval, has reached a certain stage, or when a migration failure requires investigation
• Extends the SAP locking concept beyond the time of release to reduce risk of inadvertent parallel development within a single system, or across multiple development systems
• Automatically detects potential transport sequencing errors (overtaking and overwriting) for both configuration and workbench objects before migration
• Reports discrepancies between planned and actual location of changes within a landscape, and analyzes differences between specific systems and clients using either current or historical data
• Supports the management of changes to non-SAP systems (eg, Oracle, Unix or legacy systems)
|
