I'm sure you could refrain from using editioning views however I believe that the (only) supported method is to use them.
Just adding to the above, if you are using 12c database then you can force some objects in the custom schema to be non-editioned.
I'm not sure whether this is supported but to be in the safe side you should make sure that all custom objects are properly setup.
Thanks guys for your reply.
Below are my findings. Although there were few genuine cases for which logical views were not created but in MOST cases, it's applicable for those objects which did not APPS synonym.
So, in order to make sure that logical views get created for all custom tables, make sure they have APPS synonym already in place.
I would generally advise to upgrade all tables to support online patching.
The instructions in "Developing and Deploying Customizations in Oracle E-Business Suite Release 12.2 (Doc ID 1577661.1)" describe how to create an "Effectively Editioned Table" which is needed in order to use online patching techniques to patch the table in the future.
Hope this helps!!!