VO Extension without JDeveloper

VO Extension is tool (JDeveloper) dependent but can be done manually by using below steps.

Steps to extend VO:

Create new VO  xxxxx_StandardVO.xml by renaming the standard VO StandardVO.xml (from server).

Edit below sections of VO according your customization need.

<ViewObject>

Name = New VO Name

Extends = original VO Name with complete path

ComponentClass = NewVO associate file with complete path

<SQLQuery>

Update the SQL with new changes.

<ViewAttribute> - Not required If change is in where condition or existing SQL logic

If adding a new sql field,we need to add ViewAttributes for new field.

Example -

<ViewObject

   Name=" xxxxx_StandardVO "

   Extends="oracle.apps.application.subapplication.common.server. StandardVO"

   BindingStyle="OracleName"

   CustomQuery="true"

   ComponentClass="xxxxx.oracle.apps.application.subapplication.common.server.xxxxx_StandardVOImpl"

   UseGlueCode="false">

<ViewAttribute

      Name="NEWFIELD"

      IsUpdateable="false"

      IsPersistent="false"

      Precision="30"

      Type="java.lang.String"

      ColumnType="VARCHAR2"

      AliasName=" NEWFIELD "

      Expression=" NEWFIELD "

      SQLType="VARCHAR" >

      <DesignTime>

         <Attr Name="_OverrideAttr" Value="true" />

         <Attr Name="_DisplaySize" Value="30" />

      </DesignTime>

   </ViewAttribute>

Create associated java file xxxxx_StandardVOImpl.java

package xxxxx.oracle.apps.application.subapplication.common.server;

import oracle.apps.application.subapplication.common.server. StandardVOImpl;

public class xxxxx_StandardVOImpl extends StandardVOImpl {

    public xxxxx_StandardVOImpl() {

    }  }

Compile and generate class file (xxxxx_StandardVOImpl.class

Create a OAProject.jpx file

<?xml version='1.0' encoding='windows-1252' ?>

<!DOCTYPE JboProject SYSTEM "jbo_03_01.dtd">

<JboProject

   Name="OAProject"

   SeparateXMLFiles="true"

   PackageName="" >

   <DesignTime>

      <Attr Name="_ejbPackage" Value="false" />

      <Attr Name="_NamedConnection" Value="DBConnection1" />

      <Attr Name="_version" Value="10.1.3.41.57" />

      <Attr Name="_jprName" Value="OAProject.jpr" />

   </DesignTime>

   <Containee

      Name="server"

      FullName="oracle.apps.application.subapplication.common.server"

      ObjectType="JboPackage" >

   </Containee>

   <Containee

      Name="server"

      FullName="xxxxx.oracle.apps.application.subapplication.common.server"

      ObjectType="JboPackage" >

   </Containee>

   <Substitutes>

      <Substitute OldName ="oracle.apps.application.subapplication.common.server.StandardVO" NewName ="xxxxx.oracle.apps.application.subapplication.common.server.xxxxx_StandardVO" />

   </Substitutes>

</JboProject>

Create server.xml file

<?xml version='1.0' encoding='windows-1252' ?>

<!DOCTYPE JboPackage SYSTEM "jbo_03_01.dtd">

<JboPackage

   Name="server"

   SeparateXMLFiles="true"

   PackageName="xxxxx.oracle.apps.application.subapplication.common.server" >

   <DesignTime>

      <Attr Name="_ejbPackage" Value="false" />

      <Attr Name="_version" Value="10.1.3.41.57" />

   </DesignTime>

   <Containee

      Name="xxxxx_StandardVO"

      FullName="xxxxx.oracle.apps.application.subapplication.common.server.xxxxx_StandardVO"

      ObjectType="ViewObject" >

   </Containee>

</JboPackage>

Place all files at respective locations and run JPX Importer  

Print parametr in XML report without having XML tags

Oracle provides option to print input parameter directly in RTF without generating a XML tag for this. This can be done in below 2 steps,

Define the parameter reference: this can be done in two different ways

<?param@begin:P_PARAM?>

<xsl:param name="P_PARAM" xdofo:ctx="begin"/>

Print the report parameter value:

<?$P_PARAM?>

Example

CP Parameter Name

START_TIME

END_TIME

Invoke parameters on rtf

<?param@begin:START_TIME?>

<?param@begin:END_TIME?>

Create 2 form field (Placeholder) in RTF  with below values

<?$START_TIME?>

<?$END_TIME?>

iStore Customization and Migration

Istore codes are mainly JSP changes. Below is the steps need to follow to customize and migrate the iStore changes.

 

Find the file from $OA_HTML

cp $OA_HTML/ ibeCScdDirectEntry.jsp /home/Sandeep

rename the file with “xx”  (xxibeCScdDirectEntry.jsp)

 

Copy the file to $OA_HTML

cp /home/sandeep/xxibeCScdDirectEntry.jsp $OA_HTML/

 

Navigate to FND_TOP and compile the JSP in that environment

cd $FND_TOP/patch/115/bin/

perl ojspCompile.pl --compile -s xxibeCScdDirectEntry.jsp

 

Bounce Apache

$ADMIN_SCRIPTS_HOME/adoacorectl.sh stopall

$ADMIN_SCRIPTS_HOME/adoacorectl.sh startall

               

 

 
 

: XML-20112: (Fatal Error) Error opening external DTD 'jbo_03_01.dtd'

Error while importing custom VO.

 

Above error occurs while trying importing xml files. Developer will face this while extending VO.

 

OA extension, requires following files at respective folder structure under JAVA_TOP

1        CustomVO   (xxABCVO.xml)

2          Custom VOImpl file (xxABCVOImpl.class)

3          server.xml

4        OAProject.jpx

 

To extend VO, only jpx file needs to be uploaded using jpximporter command

 

Trying to import other 2 xml files (server and custom VO), will throw above error as these were not right file for xml importer.

 

Please ignore the error if jpx importer is successful. Your VO will be extended.

---

   

How to define and call java methods in JSP Pages ( iSTORE)

Customizing JSP pages are similar to OAF changes.

 

If customizing the JSP page, writing validations and logic in Java and refering the method in JSP page, is easier option.

 

How to define and call a Java code in JSP page -

 

Create a java file and place at server ( $JAVA_TOP/xxxxx/oracle/apps/<product>/<catagory>)

Ex – created java file names xxxxxItem.class and placed at location $JAVA_TOP/xxxx/oracle/apps/ibe/catalog

 

 

Similar to import a java class in OAF, each jsp have this section at top. This is the referenced java files.

Included the custom file reference.

 

Invoke defined method inside the code –

 

 

We can extend the logic in java file for any new validations and place the new version at referred location.

Bounce the apache and changes will reflect.

 
 

Project workbench TAB on Self Service Page

 

Project workbench TAB available on HOME Page

 

 

Menu Name - Project Workbench Tab Structure

 

Exclusion Request -  

To exclude any Tab, create a custom Menu and exclude. Add custom menu on required responsibilities.

 

Inclusion Request -

To include these tab on any responsibility. Include all below menu and functions.

 

Prompt                                 Menu                                    Function

 
 

Warning !!! Due to high volume of data, got out of memory exception - XML Memory Error

 

Issue – Memory  Exception while generating XML publisher report

 

 

Resolution 1 -  Give the below shown option in CP definition –

 

 

 

 

Resolution 2 - Set the scalable option in data template (XML Publisher >> Data Definition >> Data Template. Xml )

<properties>

   <property name="scalable_mode" value="on" />

</properties>

 

 
 

Java.io.FileNotFoundException - Bursting Error

 

Bursting Error –

 

Set Bursting parameters..

Temp. Directory:/ora/integration_xxx/ebs/xxx

[070814_031305645][][STATEMENT] Oracle XML Parser version ::: Oracle XML Developers Kit 10.1.3.130 - Production

[070814_031305647][][STATEMENT] setOAProperties called..

Bursting propertes.....

{user-variable:cp:territory=AU, user-variable:cp:ReportRequestID=1000101, user-variable:cp:language=en, user-variable:cp:responsibility=2000, user-variable.OA_MEDIA=http://oracle.xxxx.local:2010/OA_MEDIA, burstng-source=EBS, user-variable:cp:DebugFlag=Y, user-variable:cp:parent_request_id=1000101, user-variable:cp:locale=en-AU, user-variable:cp:user=SANDEEP, user-variable:cp:application_short_name=XDO, user-variable:cp:request_id=1000101, user-variable:cp:org_id=30, user-variable:cp:reportdescription=Bursting Error Report, user-variable:cp:Dummy for Data Security=N}

Start bursting process..

Bursting process complete..

Generating Bursting Status Report..

--Exception

/ora/integration_xxx/ebs/xxx/070814_031305694/XXXXREPORTNAME.xls (No such file or directory)

java.io.FileNotFoundException: /ora/integration_xxx/ebs/xxx/070814_031305694/XXXXREPORTNAME.xls (No such file or directory)

                    at java.io.FileInputStream.open(Native Method)

                    at java.io.FileInputStream.<init>(FileInputStream.java:106)

                    at java.io.FileInputStream.<init>(FileInputStream.java:66)

                    at oracle.apps.xdo.oa.cp.JCP4XDOBurstingEngine.zipOutputFiles(JCP4XDOBurstingEngine.java:523)

                    at oracle.apps.xdo.oa.cp.JCP4XDOBurstingEngine.runProgram(JCP4XDOBurstingEngine.java:292)

                    at oracle.apps.fnd.cp.request.Run.main(Run.java:157)

 

Resolution -

Check the uploaded template properties. Either use correct territory or leave this field as blank (this is not mandatory)

Keeping territory blank is advisable.

 

In case its already created and delete icon is disabled. Use below query to delete the template file from backend.

 

 

 
 

How to add LOV field on OAF page without OAF customizations

Adding LOV field on OAF page, requires creation of many OAF objects. Those not having much exposure on OAF can use below to achieve same –

•  
• Check if any DFF is available on the page and can be reused by adding the new segments
• Adding value set to any segment will display LOV on segment on OAF pages
• If no DFF available, create custom DFF using respective table
• Create new flex item on page to include the custom DFF
• Assign the value set to the segment will fulfill the need.

 

This is simple and easily maintainable as LOV data will be fully controlled by your value set used.

How to add custom flexfield on OAF page

This is similar to adding any new fields on OAF page and will be achieved using OAF personalization.

 

Go to OAF page >> Personalize Page >> Create Item >>

 

Item Style = Flex

Id – DFF   (Any unique Value)

Appl Short Name – ICX ( Oracle iProcurement)

Name – TESTDFF  (DFF Name) Click Here to create custom DFF

View Instance –  OneTimeLocationDisplayVO  (Associated VO of the page)

This will show the DFF available on the screen. Re order as per requirement.

 

Associated VO Details ( About This Page)

 

Note – Add Flex item on page layout region.