Remove vo substitution oaf
In VO substitution, We substitute the Custom VO with the Standard VO in OAF page, so whenever that OAF pages runs it always refers to the Custom VO because we have extended the Standard VO by substitute the Custom VO with the Standard VO. But sometimes we need to roll back the changes and this substitution so that our standard VO should be run in the OAG page. For this we should Remove vo substitution oaf. We should remove the registration of the extended VO from the Application Java_Top for which Oracle has provided some standard APIs. In this API we pass the Path of the Custom VO and then this API delete its registrations from the Application. Here below I will share the complete steps and scripts for Remove vo substitution oaf.
Steps of Remove vo substitution oaf
To Use the Remove vo substitution API , we should know the exact path of the Custom/Extended VO other vise this API will give the error of not found this Object in the Application. If you don’t know the exact path of the VO extension, you can find this path from Two ways.
Method1 :-
1. You can go to the application and open the OAF page in which you have done the VO extension, you have to go the About this page of this that OAF Page.
2. To see the Properties of this Page and to know which View Object is working behind this Page. for this we need to go to 'About this Page' in the Bottom of the Page.
3. Click on the Expand All option.
4. Step4:-Click '+' icon for Business Components References Details.
Here below I am just taking an example of standard VO but in your case this will be a Custom VO.
Method2: -
Method2: -
You can also find all the customizations related to this page with this below API , you just need to pass the Page path and it will show all the list of the Customizations under this path with exact name and path.
When you will get the Extended VO name with the Exact path then you can use this below API’s to the delete the VO extension from OAF as below.
DECLARE
BEGIN
jdr_utils.deletedocument(p_document => '/oracle/apps/xxap/inv/lov/server/XXinvVO');
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.
Successfully deleted
Never pass Standard VO 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) login to your instance with putti or any other software
2) cd $ADMIN_SCRIPTS_HOME
3) adapcctl.sh stop
4) adoacorectl.sh stop
5) adapcctl.sh start
6) adoacorectl.sh start
6) adoacorectl.sh start
0 comments:
Post a Comment