Professional Documents
Culture Documents
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.
1 begin
2 jdr_utils.listCustomizations( '/oracle/apps/ap/oie/server/TrackExpens
3 end ;
4 /
5
6
It will output the path of the customization, which is the one to remove.
1 /oracle/apps/ap/oie/server/customizations/site/0/TrackExpenseReportsVO
2
In order to delete the customization definition, use the following call, using the
output from the previous command as a parameter.
nt( '/oracle/apps/ap/oie/server/customizations/site/0/TrackExpenseReportsVO' )
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/ap/oie/server/customizations/site/0/TrackExpenseReportsVO.
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. Worry not, 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.
1 View comments
oracle.amox.mx/2013/07/removing-oa-framework-vo-substitutions.html 1/2
12/25/23, 10:35 AM Removing OA Framework VO substitutions | amox :: oracle
Enter Comment
Load more
oracle.amox.mx/2013/07/removing-oa-framework-vo-substitutions.html 2/2