Personalization page supports to extend and remove the controller (CO) but no interface to extend the VO.
VO extension requires Jdeveloper to create substitute, which will generate .jpx and server.xml files.
Later JPXImporter will apply extended VO to system.
To backout the extended VO, we can use database scripts to delete personalizations .
refer OAF migration
Steps to back out VO extension -
1) Get the original VO name ( with complete path). This will be document path.
Example /oracle/apps/po/lov/server/DocumentNumbersVO
===========================================================
Use listcustomization to find the personalization details
BEGINJDR_UTILS.LISTCUSTOMIZATIONS('/oracle/apps/po/lov/server/DocumentNumbersVO');
END;
===========================================================
Use delete script to delete the personalization
END;
===========================================================
VO extension requires Jdeveloper to create substitute, which will generate .jpx and server.xml files.
Later JPXImporter will apply extended VO to system.
To backout the extended VO, we can use database scripts to delete personalizations .
refer OAF migration
Steps to back out VO extension -
1) Get the original VO name ( with complete path). This will be document path.
Example /oracle/apps/po/lov/server/DocumentNumbersVO
===========================================================
Use listcustomization to find the personalization details
BEGINJDR_UTILS.LISTCUSTOMIZATIONS('/oracle/apps/po/lov/server/DocumentNumbersVO');
END;
===========================================================
Use delete script to delete the personalization
Begin
jdr_utils.deletedocument(p_document=>'/oracle/apps/po/lov/server/customizations/site/0/DocumentNumbersVO');END;
===========================================================
vacorOis-gu Kristen Barnes Crack
ReplyDeletelansignmaste