Materialized Views become Views after upgraded to 12.2

"On an editioned database, you can no longer create a materialized view directly" as you did in previous releases.
In order to work around this restriction the Oracle E-Business Suite Online Patching solution implements a new
Effectively-Editioned Materialized View compound object. The developer-specified query is stored in an ordinary view,
called the Logical View. The Materialized View is then generated from the Logical View, using a new database feature that translates the
logical query into an equivalent, edition-legal "implementation query".

Therefore, what you see after the upgrade, that your Materialized view becomes a regular view is expected. So now, you will need to generate
the Materialized view using the new db feature already mentioned. Please go to section Section 1.4.2.5: Materialized Views of note
"Developing and Deploying Customizations in Oracle E-Business Suite Release 12.2 ( Doc ID 1577661.1 )" that will describe how to make your
logical view become a Materialized view.


The Online Patching Database Compliance Checker Report
This utility reports all violations to the Online Patching development standards for database objects.
You must fix any object listed in this report that is part of your custom code. If you do not fix the violations,
then you cannot use the online patching infrastructure to patch the objects listed in this report.

Check for violations of online patching database standards by running the Online Patching Database Compliance Checker with the following command

sqlplus <APPS username> @$AD_TOP/sql/ADZDDBCC.sql By running this script it will generate a report "adzddbcc.lst" which custom objects viaolating online patching standards.

This report has precise information why the object can not be re-defined. Please review and redefine the object according to the Edition based database where as objects should not reference editioned objects.