New features and benefits of upgrading to Oracle EBS 12.2.
By: Lavanya M., ennVee
Upgrading Oracle E-Business Suite (EBS) from 11i to 12.2 introduces numerous changes steered towards modern user experience, functionality advancements, streamlined installation, operational efficiency, and increased performance. In this post, we discuss the new features and benefits of upgrading to Oracle EBS 12.2, R12 offerings, Time, Cost, and Resources savings on the transition, and to upgrade EBS 11i instances to a single global instance of R12.
The transition from 11i to R12 is a high-stakes major initiative for any E-Business Suite (EBS) customer. Oracle E-Business Suite (EBS) R12 is a significant new version with valuable new features and capabilities. Currently, most believe that some clients are forced to reimplement to take advantage of R12, but others may be lucky enough to reap the new release benefits via Oracle’s upgrade process. EBS customers with brand new implementations are not impacted by the transition complexities.
Most EBS customers upgrade if given a choice because it is the path of least resistance. Compared to reimplementation, it is simpler, requires less resources, will likely cost less, and the time-to-value is shorter. ISV’s tend to make upgrades easier than starting from scratch, if they know how and can do so at an acceptable cost. If not, individual customers must shoulder the reimplementation burden. Continue reading “Upgrading to Oracle EBS R12.2: New Features, Benefits, & ROI”
An optimal way to apply CPU/PSU patches to Oracle E-Business Suite R12.2.x.
By: Praveen Sreedhar
Lead DBA, ennVee
Each quarter, Oracle releases new Critical Patch Updates (CPU) / Patch Set Updates (PSU). In this article, we discuss applying these patches to Oracle E-Business Suite (EBS) along with the Oracle MOS id references.
In Oracle E-Business Suite (EBS) we have various tech stack components. It’s important to apply the critical patch update (CPU) to all of these components. Continue reading “Applying CPU/PSU Patches to Oracle EBS R12.2.x”
A student transportation provider reduces approval time and TCO by automating the Oracle EBS requisition approval process.
By: Veera Saravanan
Oracle EBS Lead – ennVee
The client is one of the largest school bus operators and student transportation, transit, and coach bus service providers in the world, operating across the United States in 32 states, Canada, and the United Kingdom. Its US operations include an extensive fleet of 15,500 school buses, as well as transit and coach buses. The client uses Oracle E-Business Suite (12.1.3) to support their Financials, Asset Management, and Procurement. Oracle iProcurement is used heavily to manage purchasing and the approval process.
Continue reading “Case Study: Oracle EBS Requisition Approval Process Automation through Work Flow”
A leading manufacturer of commercial printing solutions integrates Oracle EBS and ServiceMax to increase cost savings and time optimization.
The customer provides graphic and precision solutions and is headquartered in Japan with its North America office located in Chicago, IL. They are one of the largest manufacturers and suppliers of system components for the prepress and printing industries worldwide.
After implementing ServiceMax to manage their after-sales operations, the customer needed to integrate ServiceMax with its back-office Oracle E-Business Suite (R12) system. The customer needed ennVee’s help to create a holistic solution, enabling the seamless and automated exchange of data between Oracle E-Business Suite and ServiceMax.
Build interfaces between Oracle E-Business Suite and ServiceMax to automatically:
- Send and receive all order information to process the order in Oracle Order Management.
- Synchronize the work order information in both systems.
- Handle all errors, exceptions, or reconciliation requirements.
ennVee developed interfaces to connect Oracle E-Business Suite and ServiceMax, and designed a custom solution to automate the following processes:
- Raising and Tracking Service Requests in ServiceMax, and integrating the requests with Oracle E-Business Suite.
- Maintaining parts prices in sync across both systems.
- Sending Work Order information to ServiceMax.
- Creating labor orders in Oracle Order Management before processing them for invoicing.
- Validating the order, returning used parts to inventory, and taking the line to closure in Oracle E-Business Suite.
Eight key business process functionalities were addressed:
- A work order is entered into ServiceMax and a sales order is entered in Oracle E-Business Suite whenever there is request from a customer for parts installation.
- A sales order entered into Oracle E-Business Suite will contain the quantity of the order placed and picked by the Engineer.
- An interface sends the information to ServiceMax, and the work order number in ServiceMax is updated along with the parts that are selected for installation.
- After the installation is done at customer site, labor and expense charges are entered in ServiceMax for the respective work order.
- Information is brought into Oracle E-Business Suite to create a sales order for the invoices and labor charges.
- The Engineer inputs the parts used during installation into the work order and completes the work order.
- This information is also brought into Oracle E-Business to perform a back order for any unused parts and to close the order line.
- There is an interface that runs daily to synchronize the prices of the parts in Oracle E-Business and ServiceMax, and sends over any parts that have undergone a price change or were recently added (new parts).
We designed and built four interfaces that would provide the various functionalities required by the customer.
- Interface 1 – Outbound from Oracle EBS (to extract the parts and pricing information to be sent to ServiceMax). Data will be extracted from Oracle EBS into a .CSV file, which will be sent to an inbound ServiceMax server via FTP.
- Interface 2 – Outbound from Oracle EBS. Whenever a service request is raised for installation of parts, a sales order is created in Oracle EBS. This order will have customer information, work order number, parts (items number), quantity, price, engineer bin location, shipped quantity, picked quantity, etc. All of this information is extracted and sent to ServiceMax via .CSV file.
- Interface 3 – Inbound to Oracle EBS. An Order for Labor charge will be entered in ServiceMax and sent to Oracle EBS for a sales order creation. After, a sales order for the labor/service charges will be created in Oracle EBS and invoice-ready.
- Interface 4. The engineer will enter the parts used and all detailed information when the work order number is closed in ServiceMax. This information will be pushed to Oracle EBS, similar to the work order number, parts consumed, closing comments, work order closed date, etc.
As a result of the new integration between ServiceMax and Oracle E-Business Suite, the customer benefitted immensely from a cost savings and time optimization standpoint. With an automated process for raising, tracking, and accessing Service Requests in Oracle E-Business Suite, the customer was able to reduce operational costs, nearly eliminating any manual intervention in the Service Request process. Automating the flow of data between systems enabled drastic business growth and yielded a faster exchange of data across the system.
Visit our website for additional case studies.
ennVee partnered with an independent research firm to survey 300+ IT and project leaders who have or anticipate upgrading to Oracle E-Business Suite R12.2. Respondents cover all major industries. The top reported challenges include Downtime, Migrating Customizations, and Patching and Testing.
Oracle E-Business Suite 12.2 was first released in September 2013. It introduced Online Patching to help customers ensure continuous operation of their key business process. The underlying technology stack was also overhauled and supplemented with Oracle Fusion Middleware. As a result, all standard and custom objects (customizations) need to undergo numerous code changes to ensure compliance with 12.2 and above. While Oracle provides a standard utility for remediating and migration standard objects, the utility does not apply to any non standard (custom) objects. As a result, customers must make manually remediate and migrate all custom objects to their target R12.2 instance. Continue reading “Customer Voice: “Patching, Testing, Migration, and Downtime…” are among the most reported Oracle EBS R12.2 upgrade challenges”