Identifying Custom Code and Scripting
An upgrade can impact custom code integrated with P6 EPPM. The upgrade brings your custom changes into the new release based on system code associated with objects. The upgrade will consider objects that are incorrectly coded to system codes obsolete and will not bring them into the upgraded version. To avoid this:
- Ensure all custom changes are coded correctly.
- Test all interfaces and customizations to ensure changes to tables, APIs, or Web Services in the upgraded software do not affect them.
- Review and update custom responsibilities and menus.
Note: In some cases, you can remove customizations after an upgrade if new features and functionality satisfy these business requirements.
Related Topics
Treating Your Upgrade Activity as a Formal Company Project
Using an Appropriate Change Management Strategy
Building an Upgrade Team with Broad and Complementary Skills
Utilizing Peer and Oracle Resources
Deciding When to Change or Add Business Processes
Ensuring the Quality of Your Data
Taking Inventory for Your System
Understanding and Mitigating Project Risks
Calculating New Hardware Sizing
Adhering to Current Tested Configurations Requirements
Implementing the Current P6 EPPM Release and Patches
Minimizing Application Data to Upgrade
Testing a Copy of the Production Database
Leveraging Existing Test Scripts and Plans
Training End Users on the New Solution
Last Published Tuesday, December 12, 2023