After a long gap, I am once again continuing my earlier OPM upgrade blog series. Carrying on from where I left, OPM upgrade is definitely different unlike the other module upgrades in Release 12+. This is due to fact that Oracle has introduced much awaited inventory convergence in this version. Before we jump on to the inventory convergence, associated impact and some of the challenges which customer might face, I would like to share some details on the upgrade steps for an OPM customer. For OPM customers, there are some additional steps to be performed during the upgrades. Please refer oracle support website for details on OPM migration. Usually upgrades are performed through various iterations and each upgrade would have a few sub-phases, ‘pre-migration’, ‘inline migration’ and post migration’. To complete iteration these sub-phases are followed by additional functional configurations, unit and integration testing. While these iterations are in process, another team in parallel would work on re-certifying CEMLI’s to work in the new environment so that when the final system integration testing is being performed, all the pieces of an upgrade puzzle can be tied together.
Going little deeper into upgrade migration steps, there are a set of pre-determined activities which are performed, but the key lies in pre-migration steps which involve convergence migration setup and post migration steps where the transformation to new model happens. Convergence migration setup form facilitates customers to review their current setup related to companies, organizations, warehouses, items, batches and quality data. Especially in the first upgrade iteration, this phase is the most critical phase where a high degree of collaboration happens from the customer and vendor team. Hence, we usually recommend a higher time allocation from the customer team during this phase of the project. The setups thus finalized, will determine the new model. Some of the validations which happen are inventory validations, process execution batch validations, quality validations, MAC to SLA model validations etc. Brief details on each of these validations are available in OPM migration guide.
Our experience in some of OPM upgrade cases indicates details provided in migration guide are not sufficient, for example, how the status control of OPM is handled in discrete with new on-hand material status control or how is ISO handled with upgrade, there are some challenges in handling non-inventory items with new model, dual UOM control and deviation issues affects transactions in new model, negative inventory issues in new model, why all the attributes are not migrated during upgrade. While these are some of the issues, there are many more that affect the overall upgrade activity and indirectly impact solution acceptance and user experience with new solution. In addition to this, especially in the case of OPM upgrades, the volume of data in specific functional areas affects the overall upgrade blackout time and needs detailed evaluation before any plan is finalized. This is where our deep-domain expertise in the process manufacturing vertical can help our customers.