Pages

Recently Viewed

Tuesday, July 8, 2014

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.
 
 

 

 

Monday, June 30, 2014

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 –
 
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.

 
 

Thursday, June 26, 2014

How to create custom DFF

Mostly we use standard DFF by adding more context and segment combination.  This will be very useful when we don’t have standard DFF enable and need to store some additional details.
 
Oracle provides option to create custom DFF –
 
Login to EBS >>Application Developer (R) >> Flexfield >>Descriptive >> Register
Application – Oracle IProcurement
Title – Sandeep
Table Application – Oracle IProcurement
Structure Column – Attribute15 (This should be attribute category. Taken attribute15 as no category was available on selected table)
 
Name – TESTDFF
Description –
Table Name – POR_ITEM_ATTRIBUTE_VALUES
Context Prompt – TestSandeep
DFF View Name – SANDEEP_DFV (Name should be ending with _DFV)
 
 
Sandeep DFF on table POR_ITEM_ATTRIBUTE_VALUES has been created successfully.
 
 
Flexfield >>Descriptive >> Segment >> select segment and create attribute as standard DFF
 
 
Now we can use this DFF at any page. In case any LOV is required define the segment and add the value set with attribute.

 

 

Saturday, June 21, 2014

Submit concurrent Program from standard Oracle Form using Form personalization

To launch a concurrent program directly from core forms ( without going to SRS window), we can use oracle form –
 
>Create a custom PL/SQL package.
>>Call the concurrent program
>>>Add accustom menu using form personalization – Click here
>>>>Create a new form personalization
Event – SPECIAL[n]
Action –Built In 
                Execute a procedure
                                                     
 
>>>>>How to execute procedure using form personalization – Click here
 

 

 

How to show message dynamically in Oracle Forms

Using form personalization we can show custom message on defined actions.
To show the different message content based on the form data, we can use form personalization.
Create a PL/SQL function
>> Return different message based on predefined rules (conditions)
Function –
xxx_pkg.getmessage(param1 VARCHAR2) return VARCHAR2
IS
BEGIN
If param1 = 1 THEN return ‘Sandeep’ end if;
If param1 =2 THEN return ‘OAL’ END IF;
EXCEPTION
Return ‘Exception in custom program’
END ;
>>> Create a form personalization to display message

= select xxx_pkg.getmessage(Paramaer) from dual
 
 
 

Inventory organization Check using Form Personalization

This is for Inventory related core forms. Oracle inventory pops us change organization form to pick an organization before launching any form.
Based on the selection only forms are appearing and are applicable only for selected organization.
 
Change organization set the organization value in
Block – PARAMETER
Field – ORG_CODE
 
Using form personalization, we can check if we are in expected organization or not.
 
While opening the form below message will pop up -
 
Org check condition will not work for WHEN-NEW-FORM-INSTANCE trigger.
We should use this at WHEN-NEW-BLOCK-INSTANCE.

 

 

Create custom Menu in forms

As OAF provides adding new items and flexibility to change the code on any button press, Oracle form is not flexible enough to accommodate such requirement.
But instead of extending the action logic of existing forms, oracle form offers to disable the existing button (removed option to perform standard action) and execute custom logic from menu.
 
For any to- do action from core forms, using form personalization we can add custom menus (Menu >> Tools>>) and instruct any action as per requirement.
 
Steps to add new menu –
Form >> Menu >> Help >> Diagnostics >>Custom Code >> Personalize>> Create a new personalization at form/function level
 
Event – WHEN NEW FORM INSTANCE
Action – Menu >> Select Special options from LOV (SPECIAL1) >> Give user defined name >> Save and Exit
 
 
Go To form >> Menu >> Tools >> This will show you new menu
 
We can add any action for custom menu –
Create a new personalization
 
Event – SPECIAL1
Action – Message
                 “This is custom menu helpful to execute custom actions”           
 
 
 
 
  

 

 

Procedure Call using Form Personalization

How to Launch a procedure using form personalization ?
 
Form >> Menu >> Help >> Diagnostics >>Custom Code >> Personalize
 
Create a personalization
Event–        Any trigger
Action –               Built in >> Execute procedure >>
 
 
Syntex –
 
='begin
xxxxx_pkg.call_program('''||${item.<BLOCK_NAME>.<FILED_NAME>.value}||''', '''||${item.<BLOCK_NAME>.<FILED_NAME>.value}||''',1,’Test’);
end'
 
 
Description –
Procedure declaration
XXXX_PKG.call_program(pramaetr1 VARCHAR2,
   parameter2 VARCHAR2,
  parameter3 NUMBER,
  parameter4 VARCHAR2);
 
Parameter1 & 2 , value will be passed form form field.
Parameter3, constant value 1 is being passed.
Parameter4, constant value ‘Test’ is being passed.
                                 
 

Saturday, February 15, 2014

LOV in WebADI - Component

Interface property can be used to set the value set. This will provide list option in excel sheet and will have limitation on values.
Usages of component will provide standard EBS LOV option. Steps are as below -
 
 
1)      Desktop Integration Manager (R) >> Manage Component >> Create Component
Provide display name, internal name and application.
Component Type:
LOV-Table -  
Ø  SQL details will be provided into interface column properties
Ø  Component name should be provided in interface column properties
 
LOV-JAVA (Please click here)

Complete component details and apply.
Table_column-alias – Interface column name
Table_column – Value set column name (Meaning)
Table-select-column - Interface column name
 
 
Go to interface >> properties window and provide the component created.