Removing OA Framework VO substitutions

As part of OA Framework extensibility it is possible to substitute a VO definition, which allows to satisfy business requirements such as adding additional conditions to it as well as to retrieve additional columns.

Such extensions, however, are not shown on the personalization catalog available under the System Administration responsibility and thus are not easily disabled in case something is wrong with them.

In order to remove the substitution definition, you have to identify the customization path and then use the jdr API to remove it.

In order to identify the customization, use the following call:

begin

jdr_utils.listcustomizations('/oracle/apps/po/notifications/server/PoNotifLinesSummaryVO');

end

It will output the path of the customization, which is the one to remove.
/oracle/apps/po/notifications/server/customizations/site/0/PoNotifLinesSummaryVO

In order to delete the customization definition, use the following call, using the output from the previous command as a parameter.

begin

jdr_utils.deletedocument('/oracle/apps/po/notifications/server/customizations/site/0/PoNotifLinesSummaryVO');

end;

You will get the following message if everything is ok, otherwise you could get an error if document is not found in case you did not properly copy the path or if you execute the command a second time.
Succesfuly deleted document /oracle/apps/po/notifications/server/customizations/site/0/PoNotifLinesSummaryVO
Now, be careful not to pass the base document path to the delete call, otherwise you will remove the actual seeded VO or page definition and you will panic (I did) when the page no longer opens when called on the application. Do not Worry, you will find the xml either on $JAVA_TOP or under the mds folder of the corresponding application and XMLImporter can be used to restore it.