Case Study
Jade Helps Leader in the Semiconductor Industry to Upgrade Their OVT Oracle Application to R12.2.11
Download Case StudyAvoid Compliance and Potential Support Risks, Take Advantage of the Many New Functional Enhancements by Upgrading the Application from R12.1.3 to R12.2.11 and Database to 19C.
OmniVision Technologies (OVT) is a leader in the semiconductor industry and this case study will illustrate how OVT’s Oracle application was upgraded to the latest version, R12.2.11.
Client: OmniVision Technologies
Industry: Semiconductor industry
About the Client
OVT is a global fabless semiconductor organization that develops advanced digital imaging, analog, and touch & display solutions for a variety of applications, industries, and consumer markets.
OmniVision recognizes that every end market has application-specific requirements that a one-size-fits-all solution cannot address. With dedicated product development teams working closely with supply chain partners and customers, OVT can deliver various Complementary Metal-Oxide Semiconductor (CMOS) image sensor technologies uniquely suited for each target marketplace.
Jade’s Engagement with OVT
Jade Global has been engaged with OVT for more than a decade, which typically includes multiple BU rollouts that cover complex data conversions, restructuring inventory organizations, and iProcurement implementation, etc. The prominent modules were Inventory, OM, and Purchasing, including iProcurement, WIP, BOM, and OSFM and Jade’s SMEs played key roles in implementing and supporting their business requirements.
The Business Benefits
With Jade’s help, OVT has been able to maximize the benefits of Oracle application R12.2.11.
Jade leveraged Oracle R12.2.11 to help OVT upgrade their application to the latest version and upgrade the Oracle database from 12c to 19c.
Business Challenges
Jade Global has been engaged with OVT for more than a decade, which typically includes multiple BU rollouts that cover complex data conversions, restructuring inventory organizations, and iProcurement implementation, etc. The prominent modules were Inventory, OM, and Purchasing, including iProcurement, WIP, BOM, and OSFM and Jade’s SMEs played key roles in implementing and supporting their business requirements.
Business Requirements
OVT has been using Oracle application R12.1.3 for more than a decade and if they had continued with the same version, there would have been impact on compliance and potential support risk. To avoid business risk and to take advantage of the many new functional enhancements of R12.2.11, OVT decided to upgrade their application from R12.1.3 to R12.2.11. In the process, there was an Oracle database upgrade from 12c to 19C.
Why Upgrade to R12.2.11?
- Oracle withdrew support to Oracle E-Business Suite (EBS) R12 and 11.5.10.
- R12.2.X supports online patching. Oracle EBS will remain available to users during patching operations.
- R12.2 has a dual File system.
- Run File system and Patch File system are identical.
- The dual file system feature is introduced to support online patching (ADOP), a new feature introduced in Oracle EBS R12.2
Why 19C?
- Oracle Database 19c offers customers the best performance, scalability, reliability, and security for all their operational and analytical workloads.
- Automatic Indexing.
- SQL Diagnostics and Repair Enhancements
- Bitmap-Based Count Distinct SQL Function.
- Big Data and Performance Enhancements for In-Memory External Tables
- Automatic SQL Plan Management.
- Real-Time Statistics.
- High-Frequency Automatic Optimizer Statistics Collection.
- Hybrid Partitioned Tables.
- R12.2.X supports it. X
The Upgrade Journey
- Upgraded the DB to 19C
- Upgraded the application from R12.1.3 to R12.2.11
- Aligned iProcurement customizations with R12.2.11. There were a lot of customization/personalization in R12.1.3 that had to be re-applied on R12.2.11.
- Ensured all custom reports/custom processes worked as anticipated.
Jade’s Contribution
- Studied client infrastructure and provided the proper action plan for DB and application upgrade.
- We used our proprietary tool, Propero, to identify any impacted objects.
- Identified OAF customization/personalization and re-applied them in R12.2.11.
- Retrofitted the custom objects.
- Confirmed all seeded processes/reports/month-end process functioned as expected.
- Ensured the approval process functioned as expected.
- Enabled functionality of Web ADI templates.
- Identified menus added in R12.2.11 and modified responsibility menus/menu exclusion.
- Identified the responsibilities no longer required (as they were end dated in R12.1.3) and end dated them.
- ECC implementation.