Scribd
Upload
48 views8 pages

OAF Extension

The document discusses extending Oracle Application Framework (OAF) controllers (CO) and view objects (VO) at different levels. It provides details on the steps to extend a CO, including copying class files, creating an extended CO class, and personalizing the application. Steps are also provided for extending a VO, such as identifying the VO, creating a project, generating a JPX file, and importing/deploying the file.

Uploaded by

Anu Chipurupally
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
48 views8 pages

OAF Extension

The document discusses extending Oracle Application Framework (OAF) controllers (CO) and view objects (VO) at different levels. It provides details on the steps to extend a CO, including copying class files, creating an extended CO class, and personalizing the application. Steps are also provided for extending a VO, such as identifying the VO, creating a project, generating a JPX file, and importing/deploying the file.

Uploaded by

Anu Chipurupally
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

OAF Extension

Outline

 CO (Controller) Extension
 VO (ViewObject) Extension
CO Extension

 Can be done at various levels[Personalization]


 Standard CO is replaced by extended CO using Personalization to
the region
 Information is stored in JDR% Tables
 Can be disabled by setting profile “Disable%Self%Service%Person%
 BC4J Extensions [EO, VO & AM] happen at site level
 But extension of Controller can be done at all the possible levels at
which Personalization can be done. This means, for a given page,
you can have controller xxCO1 for First Responsibility and controller
xxCO2 for second responsibility
Sample on CO Extension

Let's see the steps involved in doing the CO


Extension
1. Go to Payables Vision Operations USA
responsibility and click on Entry.
2. Click on About This Page link at the bottom of the
page.
3. Click on Business Component References Objects.
4. The controller associated with the page will be
displayed.
Sample on CO Extension

5. Copy the class files from middle tier to myclasses


(Jdeveloper)
6. Create a new CO file with the following properties
 Name – ExtSuppSummCO
 Package – xxlearn.oracle.apps.fnd.pos.webui
 Extends - oracle.apps.fnd.pos.webui.SuppSummCO

7. Write the required logic in : ExtSuppSummCO


8. Once done move the class file to the middle tier
9. Perform the personalization on the page to give the
information about the new CO on the region
10. Once done with the above steps….. CO
extension..is ready..
VO Extension

 Only done at site level


 To deploy, import .jpx file into DB
 Substitution info stored in JDR% Tables
 Can be disabled by setting profile “Disable Self Service
Personal%”
 Same Above process is followed for the BC4J Objects
(EO,AM)
 VO extension is used when there is a change required
for the SQL Query
Steps to extend VO

1. Identify the VO to be extended


2. Move the related class files from server to local system (myclasses)
3. In Jdeveloper create a project
4. Create a new VO extending seeded VO
5. Right click on project →project properties → perform substation .
<projectName>.jpx file will be generated
6. Import jpx file to MDS.
1. jpximport C:\jdev\jdevhome\jdev\myprojects\OAFExtProj.jpx -username apps -
password apps -dbconnection
"(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=glo.dev.com)(POR
T=1521))(CONNECT_DATA=(SID=VIS)))“
7. Move the xml,class files of the new VO to server
8. Bounce The Server (It is mandatory)
9. Perform personalization on the page to add new attribute

You might also like