Base page button submit causing Lov Controller procesRequest being called

Hello,
I have created programmatic LOV's to my base page to which I set to declarative LOV region.
I run my page, provide value to one of the LOV and trigger LOV page open, select value and the value gets populated to my base page LOV item.
Now I click submit button which should actually go to my base page CO, however it is going to the LOV Controller.
and as expected my code in LOV CO which should not be called, at this point is called causing errors.
This happens as the LOV items are set validation to true by default in OAF. If Is set the lovItemBean.setUnvalidated(false) to my Lov Item in my bas page CO and then run, my base page submit goes to its correct CO.
Its clear the OAF is trying to validate the values of LOV in base page by calling LOV Controller.
Is it a bug?
Please help.
Edited by: Prashanth Pillai on Aug 13, 2009 4:31 AM

Hi,
Whenever a form submit occurs on the page it checks for Client Side Validations.
These should be enabled as it submits the form only when the validation succeds.
So you should use
lovItemBean.setUnvalidated(false);
in the code
Thanks,
Gaurav

Similar Messages

Controller Is Being Called Twice - Why???

I think this is going to be a complicated question to answer but I'll try to explain what's going on as best I can. The basic problem I'm having is that the controller class gets called twice for some reason (instead of once) and I have no idea why. I type in a URL in my browser that goes to a JSP page called �myJsp.jsp�. Basically all that page contains is this...
<tiles:insert definition =�my.tile� flush=�true�/>In my tiles-defs.xml file I have the following listing...<definition
name="my.tile"
path="SomeOtherJsp.jsp"
controllerClass="x.y.z.MyController">
</definition>
x.y.z.MyController.java makes some calls to a DAO to retrieve data. MyController.java then puts that data into the requestScope for the JSP below to access...
SomeOtherJsp.jsp has nothing special in it although it DOES contain a link to myJsp.jsp (and, somehow, it's like this link is being clicked even though I'm not clicking it).
<a href="myJsp.jsp?someParam=<c:out value="${requestScope.someValue}"/>">Click Here To Do Something</a>If anyone can help I'd greatly appreciate it. By the way, I spoke to someone else who mentioned that I should turn this kind of thing into a struts action instead of doing a deletion within a controller class. I am going to refactor my code to do this. However, I'm still curious to know the answer to my question. Maybe it will help me get a better understanding of exactly what's going on in the world of servlets. :)

Hi Shiv, 
Yes I have placed System.out.println...and a debug point ... 
super.processRequest(pageContext, webBean); 
OAApplicationModule am = pageContext.getApplicationModule(webBean); 
// String personId="13477"; 
// Serializable[] parameters = { personId }; 
if (!pageContext.isFormSubmission()) { 
am.invokeMethod("createEmployeeRow", null); 
} 
//am.invokeMethod("initDetails",parameters); 
System.out.println("!!!!!!!!!!!!!!!!!!!!!!!!!IN Process Request"); 
debug point is at String personID="13477".... 
Thanks Soujanya

LOV selection fails when there are validation errors on the base page

Hi
I have lovs and some other required fields on a page . If there are any validation error on one of those text fields and if I open the LOV (not related to the text fields) and tries to select
an item from the LOV search results, it doesn't do it until unless I go back to the base page and correct all the validation errors on the text fields eventhough those text fields have nothing to do with the LOV.
Any suggestion is appreciated.
Thanks
Anwar

I am on Anwar's team, and I've been dealing with the same problem, although on a different page.
The JSPX for a contrived example is below. I can provide backing bean code, if needed.
The form contains two LOVs. Both fields are required. If you leave both fields blank and click Continue, you get a red box around both fields and error messages are displayed. If you then click the magnifying glass to select from the first LOV, the LOV pop-up is rendered. However, you cannot make a selection, either by double-clicking a line item or by clicking OK (the OK button has no effect). All you can do is cancel.
Interestingly, the act of clicking the magnifying glass on the first LOV gets rid of the red box around that field. So, once you cancel out, the second LOV actually does work. If there were more than two fields on the page, that wouldn't happen. The problem seems to be that the LOV doesn't work unless there are no validation errors on the page other than for the LOV which is being invoked.
As you can see, immediate="true" is set on both LOVs. The behavior is the same whether this is true or not.
I'm left thinking there must be something obvious that we're missing... but none of us can see it.
Thanks,
KEN
<?xml version='1.0' encoding='windows-1252'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
 xmlns:f="http://java.sun.com/jsf/core"
 xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
<jsp:directive.page contentType="text/html;charset=windows-1252"/>
<f:view>
 <af:document title="Add Item">
 <af:form>
 <af:panelGroupLayout>
 <af:panelHeader text="Header">
 <af:panelFormLayout>
 <af:inputListOfValues label="Id" searchDesc="Search" popupTitle="Supplier Id"
 simple="true" required="true" id="supplierId"
 model="#{viewScope.AddItemBackingBean.supplierIdListOfValuesModel}"
 value="#{viewScope.AddItemValuesBean.supplier.id}"
 autoSubmit="true" immediate="true"/>
 <af:inputListOfValues label="Description" searchDesc="Search" popupTitle="Supplier Id"
 simple="true" required="true" id="supplierDescription"
 model="#{viewScope.AddItemBackingBean.supplierDescriptionListOfValuesModel}"
 value="#{viewScope.AddItemValuesBean.supplier.description}"
 autoSubmit="true" immediate="true"/>
 <f:facet name="footer">
 <af:panelGroupLayout layout="horizontal" halign="right" >
 <af:commandButton text="Continue"
 actionListener="#{viewScope.AddItemBackingBean.continueAction}"
 id="continueButton" />
 </af:panelGroupLayout>
 </f:facet>
 </af:panelFormLayout>
 </af:panelHeader>
 </af:panelGroupLayout>
 </af:form>
 </af:document>
</f:view>
</jsp:root>

The LOV modal window could not return value to the base page

when practicing the "create1" task in tutorial, met an issue.
when create an employee, manageName is a messageLovInput and managerID is a messageTextInput.
The issue is the LOV modal window could not return value to the mangerName, but can return to managerID .
If I remove the data boud porperties of the managerName (the bc4j porperties of view name-EmpFullVO and view attribute-MgrName), the lov works fine.
What is the reason?

James I would suggest to read the LOV topic in OAF developers' guide. Lov mappings are responsible for bringing pop up values to base page in LOV.
--Mukul

Subject: Trouble in Multi-Select LOV. Does not populate records in Base Pag

Hi Friends,
I am trying to use multi-select LOV for the first time. But the base page table does not get populated after the rows are selected in the LOV. I am initializing the Base Page VO like below. And all fields are mapped between both the VO's, Can you please help as to what else could be the problem.
if("UPDATE".equals(s1))
vo.setMaxFetchSize(-1);
vo.executeQuery();
} else
if("CREATE".equals(s1))
vo.setMaxFetchSize(0);
vo.setPreparedForExecution(true);
}

Is there any other piece of code you have used?
Try my suggestion and follow the Dev guide once step by step to implement the multi select LOV. They have a nice sample and then you can compare where you went wrong. I feel like you are missing something part of setup.
--Shiv

"Printable Page" button causes isBackNavigationFired(true)

I ve got the following problem
I have a train implemented with 3 pages. On every page we don't allow the users to use the BrowserBack button.
    if (pageContext.isBackNavigationFired(true))
      pageContext.redirectToDialogPage(new OADialogPage(NAVIGATION_ERROR));
    }     Page 3 (Review page) contains the "submit" and a "Printable Page" button.
Properties for "Printable Page" button
destination URI : OA.jsp?page=pagePG&retainAM=Y&OARF=printable
target frame : _blank
When we press the submit button, everything is saved correctly. but when we first use the "Printable Page" button (opens a new window) and then submit, the OA framework detects that we used the BroweserBack Button. Submitting the data becomes impossible.
Does anyone knows what I'm doing wrong, or is this normal behaviour.

Hi,
You will not be able to get around this. When you navigate to your printable page, the framework increments the oapc parameter (it adds 1 to the original value). When you then go back and action something on the previous page, the framework compares the value in the URL with the value it stores in memory. If the values do not match it re-fires processRequest because the bean hierarchy could be invalid (it's probably not in your case).
So you will have to think of a way around this.
Why are you not letting users use the back button? You can write your application so that you code around any use of the back button. For example, if you are passing parameters on the request, put them on the transaction. When the user hits the back button, OA Framework will re-execute processRequest, if the parameters are null you can fetch them from the transaction (assuming it is retained).
Hope this helps.
Cheers,
Dave

LOV doesn't return selected value to the base page

Hi All,
I have created an LOV based on VO. When I select value on the LOV page, it is not returning the selected value to the base page.
I am getting the error when I select any value .
Error
You are trying to access a page that is no longer active.
- The referring page may have come from a previous session. Please select Home to proceed.
Can anyone please guide me which property has to be set.
Thanks,
Edited by: user4482525 on Apr 21, 2009 11:49 PM

1> Go to the About this page* of the page and check whether page Root AM is extended or not?
If the page root AM is extended then delete the extension by jdr_util.deleteDocument or using functional Adminstartor
or
2> See in the LOV CO, if you are using the method "releaseApplicationModule"
If yes , then remove this.
Thanks,
Kumar

LOV does not return value to the base page sometimes

Hi,
I have created messageLOV type items. These LOVs do return value to the base page usually. We have a user in Uruguay who is trying to use the page which has the LOVs. He says the LOV takes a long time to return to the main page after he clicks on quick select and also the value does not get populated in the main page.
We have not been facing any such problem here in India. The LOV has been tested rigorously with no issues as such.
Can you please suggest a reason why such a problem is occuring? Expecting your replies soon
Thanks,
Priya

Thiyaga, did you read the devguide or the tutorial ?
Can you please give me the inputs about the creation of LOV and it requires how many lov mappings as mandatory?
This is there in the devguideHow to identify the mapping fields of an LOV which is already existing in the base page to reproduce in a similar way and need to do a customization on top of it ?
Open the page XML and you can find the LOV mappings.Tapash

Enkitec Modal LOV window too narrow - 'next page' button missing

Hi,
Apex 4.2, any theme, any browser.
Does anyone know how to set the minimum width for the popup window for this otherwise excellent plugin.
The problem occurs when the width of the data in the search results is narrower than the search bar at the top of the window. It truncates the search bar so that the button to navigate to the next page of results is not showing.
Thanks,
Nick.

Hi Dan,
Sorry for the delay in replying - I've been away.
Apex versions 4.2.0.00.27 and 4.2.2.00.11, theme 22
Firefox 20.0.1
IE 8.0.7601.17514
Windows 7
I also posted another issue on the Apex Plugins site - "A column headed 'Total Rows' appears in my results, showing the number of records returned. This column is not in my select statement and I do not want it in my results. Also, the 'Next Page' button does nothing when there are more rows returned than can be displayed on one page". Could this be part of the same problem?
Thanks,
Nick.

Need help in passing parameter from base page to popup page

Dear ALL,
I have a requirement as below.
I have a page having one LOV, I need to select one value from that LOV and select one button from the page then it should open a popup page with the required data in tabular format for the field i selecetd.
so i created a lov in my page and able to invoke the popup page through java script but how i can execute the query in popup page by taking the parameter whta i selected from base page.
Please help me out.

Mukul's Oracle Technology Blog: JavaScript In OA Framework
--Sushant

Unable to capture button event in pageLayout Controller

Hi Guys,
I have the following layout
pageLayout
pageLayoutCO (controller)
----header (Region)
----------messageComponentLayout (Region)
-----------------MessageLovInpurt
-----------------MessageChoice(Item)
-----------------MessageTextInput
-----------------MessageLayout
----------HideShow (Region)
-----------------MessageLovInpurt(Item)
-----------------MessageChoice(Item)
-----------------MessageTextInput(Item)
-----------MessageComponentLayout (Region)
-----------------MessageLayout
------------------------SubmitButton(ID:SearchBtn)
------------------------SubmitButton(ID:ClearBtn, fires partial action named clear)
-----------header(Region)
I am not able to capture the event fired by the button ClearBtn in the controller of the pagelayout.....
The two methods I used as follows aren't worked:
if ("clear".equals(pageContext.getParameter(OAWebBeanConstants.EVENT_PARAM)))
if (pageContext.getParameter("ClearBtn") != null) {
what should i do in order to capture the button event in the pageLayout Controller
Thanks in advance
Mandy
Edited by: user8898100 on 2011-8-2 上午7:49

Mandy,
Its really strange that its not able to caputure the event in CO.
Below is the way in which we handle to Submit action at CO level.
/Check whether ClearBtn is same in case too.
if(pageContext.getParameter("ClearBtn")!=null){
System.out.println("Inside the Clear Btn Action");
Regards,
Gyan

If I open another URL from my homepage, the "go back one page" button is grayed out so I can't get back to my home page.

This problem only started recently.
Opening another web page (URL) from my homepage always opens in the same tab and the "go back one page" button is gray and does not work. If I open a series of web pages in the same tab the green "back" button is green. Clicking on the "recent pages" down arrow will allow me to go back, but only to the page after the home page.
In other words, after browsing, I can get back to the opening page (my home page) only by clicking on the house icon but not by using the "recent pages" function.
Is there an option that changed after the last update?

Do you see any tab history if you right click the Back or Forward button?
Start Firefox in [[Safe Mode]] to check if one of the add-ons is causing the problem (switch to the DEFAULT theme: Tools > Add-ons > Themes).
* Don't make any changes on the Safe mode start window.
See:
* [[Troubleshooting extensions and themes]]

How to get inputted value in a RTE field on custom page and submit by REST call in 'Sharepoint hosted app'.

Hi I am facing the three questions below.
1. How to use default RTE in custom page in Sharepoint hosted app.
I saw the article of Rich text Editor (ribbon based) in a webpart in SharePoint 2013 and tried it. But it did not work well. I guess it needs code-behind setting, however sharepoint hosted app does not support code-behind.
Does anybody know how to do this?
2. In above case, I placed the below code on custom page and tried to get the field's value when submit button was clicked.
<SharePoint:InputFormTextBox ID="rftDefaultValue"
RichText="true"
RichTextMode="FullHtml" runat="server"
TextMode="MultiLine" Rows="5">
</SharePoint:InputFormTextBox>
In debugger, the returned value was 'undefined'.
var note = $('#hogehoge').val();
Is it possible to get the RTE value? If yes, please let me know how to do this.
3. I need to submit the RTE value using REST call.
In this
article in MSDN, the item creation sample treats single line text field. Does anybody know the sample for RTE?

Hi,
According to your description, you might want to use Rich Text Editor control in your SharePoint hosted app.
First of all, I would suggest you post one question in one thread to make it easier to be discussed, which would also help you get a quick solution.
Though we can add this control into a SharePoint hosted app, however, as we can’t add code behind for it, plus with the potential compatibility issues in different
browsers, I would suggest you use other JavaScript Rich Text Editor plugins instead.
Two JavaScript Rich Text Editor plugins for your reference:
http://quilljs.com/
http://nicedit.com/
If you want to submit the value of Rich Text Editor control to a SharePoint list using REST call, since the content in the Multiple Line of Text column is wrapped
with nested HTML tags, the similar requirement would also be applied to the content to be submitted.
Here is a code snippet about how to update a Multiple Line of Text column for your reference:
updateListItem(_spPageContextInfo.webAbsoluteUrl, "List018", 1);
function updateListItem(siteUrl, listName, itemId)
var itemType = GetItemTypeForListName(listName);
var item = {
"__metadata": { "type": itemType },
"MultiTextEnhanced": "<div><a href='http://bing.com/'>Bing</a> </div>",
"Title": "123"
$.ajax({
url: siteUrl + "/_api/web/lists/getbytitle('" + listName + "')/items(" + itemId + ")",
method: "GET",
headers: { "Accept": "application/json; odata=verbose" },
success: function (data) {
console.log(data);
$.ajax({
url: data.d.__metadata.uri,
type: "POST",
contentType: "application/json;odata=verbose",
data: JSON.stringify(item),
headers: {
"Accept": "application/json;odata=verbose",
"X-RequestDigest": $("#__REQUESTDIGEST").val(),
"X-HTTP-Method": "MERGE",
"If-Match": data.d.__metadata.etag
success: function (data) {
console.log(data);
error: function (data) {
console.log(data);
error: function (data) {
console.log(data);
// Getting the item type for the list
function GetItemTypeForListName(name)
return"SP.Data." + name.charAt(0).toUpperCase() + name.slice(1) + "ListItem";
Thanks
Patrick Liang
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support,
contact [email protected]
Patrick Liang
TechNet Community Support

"Go back one page" button - for some reason doesn't work

For some reason, multiple pages are showing up - duplicates of the page that I'm viewing, so when I click on the "go back one page" button nothing happens - I'm required to right click on the button and select the actual last page that I want to view, again.
Stated another way, why are multiple pages listed/included under the "go back one page" button - I'm thinking this is a new 'feature' that is not good, at all.

Start Firefox in [[Safe Mode]] to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).
*Don't make any changes on the Safe mode start window.
*https://support.mozilla.com/kb/Safe+Mode
*https://support.mozilla.com/kb/Troubleshooting+extensions+and+themes

Page buttons not working_code properly working

Hi Guru's plse help me this issue.
This is custom controller clas... The code is I think ri8.. it does not shows any error.
But when click on (in the page) BUTTONS LIKE search claim and new claim, it does not show any details and not move to ClailPG.
I send AMImpl class also, methods are called in this class.. plse reply me asap... plse help me..
Thi is controller clas..
package xx.oracle.apps.xx.med.claims.webui;
import com.sun.java.util.collections.HashMap;
import java.io.Serializable;
import oracle.apps.fnd.common.VersionInfo;
import oracle.apps.fnd.framework.OAApplicationModule;
import oracle.apps.fnd.framework.OAException;
import oracle.apps.fnd.framework.server.OADBTransaction;
import oracle.apps.fnd.framework.webui.OAControllerImpl;
import oracle.apps.fnd.framework.webui.OAPageContext;
import oracle.apps.fnd.framework.webui.beans.OAWebBean;
import oracle.apps.fnd.framework.webui.beans.form.OAFormValueBean;
import oracle.apps.fnd.framework.webui.beans.message.OAMessageDateFieldBean;
import oracle.apps.fnd.framework.webui.beans.table.OATableBean;
import oracle.cabo.ui.data.DataObjectList;
import oracle.cabo.ui.data.DictionaryData;
import xx.oracle.apps.xx.util.conversion.Collection;
import xx.oracle.apps.xx.util.dialogpage.OAConfirmationPage;
import xx.oracle.apps.xx.util.dialogpage.OAWarningPage;
public class xxMedClaimsQueryCO extends OAControllerImpl
public static final String RCS_ID = "$Header$";
public static final boolean RCS_ID_RECORDED = VersionInfo.recordClassVersion("$Header$", "%packagename%");
String personId;
String dateFrom;
String dateTo;
String claimId;
String readOnlyFlag;
public void processRequest(OAPageContext pageContext, OAWebBean webBean)
super.processRequest(pageContext, webBean);
this.personId = pageContext.getParameter("PersonId");
this.dateFrom = pageContext.getParameter("DateFrom");
this.dateTo = pageContext.getParameter("DateTo");
if (this.personId != null) {
initPage(pageContext, webBean);
initTable(pageContext, webBean);
void initPage(OAPageContext pageContext, OAWebBean webBean) {
OAApplicationModule am = pageContext.getApplicationModule(webBean);
Serializable[] parameters = { this.personId, this.dateFrom, this.dateTo };
am.invokeMethod("initMedClaims", parameters);
void initTable(OAPageContext pageContext, OAWebBean webBean) {
formatImageColumn(pageContext, webBean, "UpdateSwitcher");
formatImageColumn(pageContext, webBean, "DeleteSwitcher");
formatImageColumn(pageContext, webBean, "ClaimDetails");
formatImageColumn(pageContext, webBean, "ApproveSwitcher");
void formatImageColumn(OAPageContext pageContext, OAWebBean webBean, String columnName)
OATableBean table = (OATableBean)webBean.findIndexedChildRecursive("ClaimsRN");
table.prepareForRendering(pageContext);
DataObjectList columnFormats = table.getColumnFormats();
int columnIndex = pageContext.findChildIndex(table, columnName);
DictionaryData columnFormat = (DictionaryData)columnFormats.getItem(columnIndex);
columnFormat.put("columnDataFormat", "iconButtonFormat");
public void processFormRequest(OAPageContext pageContext, OAWebBean webBean)
super.processFormRequest(pageContext, webBean);
if ((pageContext.isLovEvent()) && ("EmployeeNumber".equals(pageContext.getLovInputSourceId())))
processLovEmployeeNumber(pageContext, webBean);
if (pageContext.getParameter("Search") != null) {
processSearchClaims(pageContext, webBean);
if (pageContext.getParameter("New") != null) {
processNewClaim(pageContext, webBean);
if (pageContext.getParameter("Clear") != null) {
redirectToCurrentPage(pageContext, webBean);
if ("clickClaimDetails".equals(pageContext.getParameter("event"))) {
processClaimDetails(pageContext, webBean);
if ("clickUpdateClaim".equals(pageContext.getParameter("event"))) {
processUpdateClaim(pageContext, webBean);
if ("clickDeleteClaim".equals(pageContext.getParameter("event"))) {
processDeleteClaim(pageContext, webBean);
if ("clickApproveClaim".equals(pageContext.getParameter("event"))) {
processApproveClaim(pageContext, webBean);
if (pageContext.getParameter("WarningYesButton") != null) {
processWarningYes(pageContext, webBean);
if (pageContext.getParameter("ConfirmationOkButton") != null)
processConfirmationOk(pageContext, webBean);
void processLovEmployeeNumber(OAPageContext pageContext, OAWebBean webBean)
OAWebBean rootBean = pageContext.getRootWebBean();
OAFormValueBean personId = (OAFormValueBean)rootBean.findIndexedChildRecursive("PersonId");
this.personId = ((String)personId.getValue(pageContext));
void processSearchClaims(OAPageContext pageContext, OAWebBean webBean) {
setDateFields(pageContext, webBean);
OAApplicationModule am = pageContext.getApplicationModule(webBean);
Serializable[] parameters = { this.personId, this.dateFrom, this.dateTo };
am.invokeMethod("initMedClaims", parameters);
void setDateFields(OAPageContext pageContext, OAWebBean webBean) {
OAWebBean rootBean = pageContext.getRootWebBean();
OAMessageDateFieldBean dateFrom = (OAMessageDateFieldBean)rootBean.findIndexedChildRecursive("ClaimDateFrom");
if (dateFrom.getValue(pageContext) == null)
this.dateFrom = null;
else {
this.dateFrom = String.valueOf(dateFrom.getValue(pageContext));
OAMessageDateFieldBean dateTo = (OAMessageDateFieldBean)rootBean.findIndexedChildRecursive("ClaimDateTo");
if (dateTo.getValue(pageContext) == null)
this.dateTo = null;
else
this.dateTo = String.valueOf(dateTo.getValue(pageContext));
void processNewClaim(OAPageContext pageContext, OAWebBean webBean)
redirectToClaimPage(pageContext, webBean);
void processClaimDetails(OAPageContext pageContext, OAWebBean webBean) {
this.claimId = pageContext.getParameter("pClaimId");
this.readOnlyFlag = "Y";
redirectToClaimPage(pageContext, webBean);
void processUpdateClaim(OAPageContext pageContext, OAWebBean webBean) {
this.claimId = pageContext.getParameter("pClaimId");
redirectToClaimPage(pageContext, webBean);
void processDeleteClaim(OAPageContext pageContext, OAWebBean webBean) {
this.claimId = pageContext.getParameter("pClaimId");
Serializable[] parameters = { this.claimId };
OAApplicationModule am = pageContext.getApplicationModule(webBean);
am.invokeMethod("deleteClaim", parameters);
am.getOADBTransaction().postChanges();
redirectToWarningPage(pageContext, new OAException("DIV", "DIV_DELETE_WARNING"));
void processWarningYes(OAPageContext pageContext, OAWebBean webBean)
OAApplicationModule am = pageContext.getApplicationModule(webBean);
am.getOADBTransaction().commit();
redirectToConfirmationPage(pageContext, new OAException("DIV", "DIV_DELETE_SUCCESS"));
void processConfirmationOk(OAPageContext pageContext, OAWebBean webBean)
processSearchClaims(pageContext, webBean);
void processApproveClaim(OAPageContext pageContext, OAWebBean webBean) {
this.claimId = pageContext.getParameter("pClaimId");
Serializable[] parameters = { this.claimId };
OAApplicationModule am = pageContext.getApplicationModule(webBean);
am.invokeMethod("approveClaim", parameters);
am.getOADBTransaction().commit();
processSearchClaims(pageContext, webBean);
void redirectToClaimPage(OAPageContext pageContext, OAWebBean webBean) {
HashMap pageParameters = new HashMap(5);
pageParameters.put("PersonId", this.personId);
pageParameters.put("DateFrom", this.dateFrom);
pageParameters.put("DateTo", this.dateTo);
pageParameters.put("ClaimId", this.claimId);
pageParameters.put("ReadOnlyFlag", this.readOnlyFlag);
pageContext.setForwardURL("OA.jsp?page=/div/oracle/apps/div/med/claims/webui/ClaimPG", null, 0, null, pageParameters, Boolean.FALSE.booleanValue(), "N", 99);
void redirectToCurrentPage(OAPageContext pageContext, OAWebBean webBean)
HashMap pageParameters = new HashMap(5);
pageParameters.put("PersonId", null);
pageParameters.put("DateFrom", null);
pageParameters.put("DateTo", null);
pageContext.setForwardURLToCurrentPage(pageParameters, Boolean.FALSE.booleanValue(), "N", 99);
void redirectToWarningPage(OAPageContext pageContext, OAException exception)
HashMap pageParameters = new HashMap(5);
pageParameters.put("PersonId", this.personId);
pageParameters.put("DateFrom", this.dateFrom);
pageParameters.put("DateTo", this.dateTo);
OAWarningPage warningPage = new OAWarningPage(exception);
warningPage.setFormParameters(Collection.getUtilHashtable(pageParameters));
pageContext.redirectToDialogPage(warningPage);
void redirectToConfirmationPage(OAPageContext pageContext, OAException exception)
HashMap pageParameters = new HashMap(5);
pageParameters.put("PersonId", this.personId);
pageParameters.put("DateFrom", this.dateFrom);
pageParameters.put("DateTo", this.dateTo);
OAConfirmationPage confirmationPage = new OAConfirmationPage(exception);
confirmationPage.setFormParameters(Collection.getUtilHashtable(pageParameters));
pageContext.redirectToDialogPage(confirmationPage);
this is server AMIMPL Class file.
package xx.oracle.apps.xx.med.claims.server;
import java.sql.CallableStatement;
import java.sql.SQLException;
import oracle.apps.fnd.common.MessageToken;
import oracle.apps.fnd.framework.OAException;
import oracle.apps.fnd.framework.OAViewObject;
import oracle.apps.fnd.framework.server.OAApplicationModuleImpl;
import oracle.apps.fnd.framework.server.OADBTransaction;
import oracle.apps.fnd.framework.server.OAExceptionUtils;
import oracle.jbo.Row;
import oracle.jbo.RowSetIterator;
import oracle.jbo.domain.Number;
public class xxMedClaimsAMImpl extends OAApplicationModuleImpl {
/**This is the default constructor (do not remove)
public xxMedClaimsAMImpl() {
/**Sample main for debugging Business Components code using the tester.
public static void main(String[] args) { /* package name */
/* Configuration Name */launchTester("xx.oracle.apps.xx.med.claims.server",
"xxMedClaimsAMLocal");
public void initMedClaims(String pPersonId, String pDateFrom,
String pDateTo) {
xxMedClaimsVOImpl vo = getxxMedClaimsVO1();
if (vo == null) {
MessageToken[] errTokens =
{ new MessageToken("OBJECT_NAME", "xxPfMemberContribVO1") };
throw new OAException("AK", "FWK_TBX_OBJECT_NOT_FOUND", errTokens);
vo.initQuery(pPersonId, pDateFrom, pDateTo);
public void initMedClaim(String pClaimId) {
SinpMedClaimsVOImpl vo = getxxMedClaimsVO1();
if (vo == null) {
MessageToken[] errTokens =
{ new MessageToken("OBJECT_NAME", "SinpPfMemberContribVO1") };
throw new OAException("AK", "FWK_TBX_OBJECT_NOT_FOUND", errTokens);
vo.initQuery(pClaimId);
public void createClaim() {
xxMedClaimsVOImpl vo = getxxMedClaimsVO1();
if (!vo.isPreparedForExecution()) {
vo.executeQuery();
Row row = vo.createRow();
vo.insertRow(row);
row.setNewRowState(Row.STATUS_INITIALIZED);
public String getClaimId() {
OADBTransaction transaction = getOADBTransaction();
Number claimId = transaction.getSequenceValue("xx_MED_CLAIMS_SEQ");
return String.valueOf(claimId);
public void deleteClaim(String pClaimId) {
int claimToDelete = Integer.parseInt(pClaimId);
OAViewObject vo = getxxMedClaimsVO1();
xxMedClaimsVORowImpl row = null;
int fetchedRowCount = vo.getFetchedRowCount();
RowSetIterator iterator = vo.createRowSetIterator("iterator");
if (fetchedRowCount > 0) {
iterator.setRangeStart(0);
iterator.setRangeSize(fetchedRowCount);
for (int i = 0; i < fetchedRowCount; i++) {
row = (xxMedClaimsVORowImpl)iterator.getRowAtRangeIndex(i);
Number primaryKey = row.getClaimId();
if (primaryKey.compareTo(claimToDelete) == 0) {
row.setEnabledFlag("N");
break;
iterator.closeRowSetIterator();
public void approveClaim(String pClaimId) {
try {
String pkgName = "xx_med_claims_wf_pkg";
String procName = "init_approval";
String parameters = "(p_claim_id => :1)";
String stmt =
"BEGIN " + pkgName + "." + procName + parameters + "; END;";
OADBTransaction tr = getOADBTransaction();
CallableStatement st = tr.createCallableStatement(stmt, 1);
st.setInt(1, Integer.parseInt(pClaimId));
st.execute();
st.close();
OAExceptionUtils.checkErrors(tr);
} catch (SQLException e) {
throw OAException.wrapperException(e);
/**Container's getter for xxMedClaimsVO1
public xxMedClaimsVOImpl getxxMedClaimsVO1() {
return (xxMedClaimsVOImpl)findViewObject("xxMedClaimsVO1");
public void validateClaim(String pClaimId) {
try {
String pkgName = "xx_med_oaf_val_pkg";
String procName = "validate_claim";
String parameters = "(p_claim_id => :1)";
String stmt =
"BEGIN " + pkgName + "." + procName + parameters + "; END;";
OADBTransaction tr = getOADBTransaction();
CallableStatement st = tr.createCallableStatement(stmt, 1);
st.setInt(1, Integer.parseInt(pClaimId));
st.execute();
st.close();
OAExceptionUtils.checkErrors(tr);
} catch (SQLException e) {
throw OAException.wrapperException(e);
plse reply me some solution my frnds......

Hi,
Yes I can see that... Should we ask oracle for a patch for this? Thanks!
OA Framework 12.0.4
Oracle OA Extension 10.1.3 - build 1028
Business Components 10.1.3.3
UIX (Cabo) 2_3_6_2
BiBeans Runtime 3.1.1.7 nondebug BI Beans 3.1.1.x
MDS 9.0.6.0.0_26
XML Oracle XML Developers Kit 10.1.3.0.0 - Production
AOL/J Applications Object Library, Core Java Roll Up Patch J
Servlet 2.4
Java 1.5.0_11
JDBC Driver 10.2.0.3.0
Database Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
Operating System Linux 2.6.9-89.0.11.ELsmp
Browser Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; InfoPath.2)

Base page button submit causing Lov Controller procesRequest being called

Similar Messages

Maybe you are looking for