Developer Mode Error during journal entry

Hi I am getting this error while entering a new journal.
Develope mode error
an oracle apps coding standards v iolation was encountered please report this probem to oracle support
fddfu.lc register_form-flex() fucntion detected a flexfield attached to a form field whose length is less than the maximum concat value lenght 700
please change the length of the field
Block : HEADER
Field : ORIGINATING_BAL_SEG_VALUE
Length : 25

Is this a base form or a custom form ? If it is a base form, pl disable any personalizations you may have on this form, and turn off all CUSTOM.pll code - then see if the error still occurs. If it does, pl open an SR with Oracle Support.
HTH
Srini Chavali

Similar Messages

JDeveloper IDE: Developer Mode Error

Hi All,
I am facing an issue after launcing JDEV through /jdevbin/NT/1223_db2dbg_17007206 (JDeveloper IDE for Release 12.2.3 Dev Build 2).
I am getting developer mode error after launcing my application. For the error to perish, we need to disable the same by :
Go Project Properties -> Oracle Applications -> Run Options and remove OADeveloperMode from the selected list.
However the OADeveloperMode option is not visible at project properties. Any idea on how to disable the option through any other means or any workarounds.
The profile “FND:Developer Mode” is already set to No in site level in environment. I am still seeing the Developer Mode error in jdev.
Thanks in advance.
Regards,
Arpita

Hi Shobit,
Error message :
(This developer mode error is thrown instead of being registered due to the lack of the page context object.) The OA passivation framework coding standard has been violated. Web bean properties cannot be modified in the controller processFormData or processFormRequest method. Web bean properties should be modified in the processRequest method only. An attempt to modify a web bean has been made in the following call stack: java.lang.Throwable at oracle.apps.fnd.framework.OACommonUtils.getCallStack(OACommonUtils.java:822) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.setAttributeValue(OAWebBeanHelper.java:1857) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.setAttributeValue(OAWebBeanHelper.java:1891) at oracle.apps.fnd.framework.webui.OAWebBeanFormElementHelper.setAttributeValue(OAWebBeanFormElementHelper.java:2108) at oracle.apps.fnd.framework.webui.beans.message.OAMessageLovInputBean.setAttributeValue(OAMessageLovInputBean.java:616) at oracle.cabo.ui.beans.form.TextInputBean.setRequired(TextInputBean.java:441) at oracle.apps.po.common.webui.ClientUtil.setViewOnlyRecursiveInternal(ClientUtil.java:743) at oracle.apps.po.common.webui.ClientUtil.setViewOnlyRecursiveInternal(ClientUtil.java:864) at oracle.apps.po.common.webui.ClientUtil.setViewOnlyRecursiveInternal(ClientUtil.java:864) at oracle.apps.po.common.webui.ClientUtil.setViewOnlyRecursiveInternal(ClientUtil.java:864) at oracle.apps.po.common.webui.ClientUtil.setViewOnlyRecursiveInternal(ClientUtil.java:864) at oracle.apps.po.common.webui.ClientUtil.setViewOnlyRecursive(ClientUtil.java:704) at oracle.apps.ozf.oa.claim.webui.ClaimUpdateCO.setPageReadOnly(ClaimUpdateCO.java:425) at oracle.apps.ozf.oa.claim.webui.ClaimUpdateCO.processFormRequest(ClaimUpdateCO.java:239) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequest(OAWebBeanHelper.java:854) at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processFormRequest(OAWebBeanContainerHelper.java:385) at oracle.apps.fnd.framework.webui.OAPageLayoutHelper.processFormRequest(OAPageLayoutHelper.java:1241) at oracle.apps.fnd.framework.webui.beans.layout.OAPageLayoutBean.processFormRequest(OAPageLayoutBean.java:1579) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequestChildren(OAWebBeanHelper.java:1066) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequestChildren(OAWebBeanHelper.java:1032) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequest(OAWebBeanHelper.java:887) at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processFormRequest(OAWebBeanContainerHelper.java:385) at oracle.apps.fnd.framework.webui.beans.form.OAFormBean.processFormRequest(OAFormBean.java:395) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequestChildren(OAWebBeanHelper.java:1066) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequestChildren(OAWebBeanHelper.java:1032) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequest(OAWebBeanHelper.java:887) at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processFormRequest(OAWebBeanContainerHelper.java:385) at oracle.apps.fnd.framework.webui.beans.OABodyBean.processFormRequest(OABodyBean.java:363) at oracle.apps.fnd.framework.webui.OAPageBean.processFormRequest(OAPageBean.java:3113) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1897) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:558) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:446) at _OA._jspService(_OA.java:72) at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:473) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:734) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:391) at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:908) at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:458) at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:226) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:127) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:116) at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260) at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303) at java.lang.Thread.run(Thread.java:662)
This error part of the file (oracle.apps.ozf.oa.claim.webui.ClaimUpdateCO) present in the error message is an already existing code.
Now the problem with solving this issues may end up solving many other issues. I am also not sure that my solving one part will fix it or not.
If you can please help me with suppressing the option how we used to do that earlier via jdev, then I can move ahead with my changes and test them.
Thanks,
Arpita

Error during manuel entry/Change of condition.

Dear friends,
while I am trying to create standard customer order(VA01), I have faced an error message as: Item 00001:Error during manuel entry/Change of condition.
Can anyone tell me solution?
Thanks in advance.

Hi,
Goto to V/08 for your pricing procedure, check for the condition type if it is mandatory condition and / or if it is manual condition.
In V/06, select condition type and check the value for Manual entry field
Hope you get some inputs
regards,
Sagar

Development mode error

Developer Mode Error: Stale Data
The requested page contains stale data. This error could have been caused through the use of the browser's navigation buttons (the browser Back button, for example). If the browser's navigation buttons were not used, this error could have been caused by coding mistakes in application code. Please check Supporting the Browser Back Button developer guide - View Object Primary Key Comparison section to review the primary causes of this error and correct the coding mistakes.
Cause:
The view object XxEmployeeAM.XxEmployeeSearchVO1 contained no record. The displayed records may have been deleted, or the current record for the view object may not have been properly initialized.
To proceed, please select the Home link at the top of the application page to return to the main menu. Then, access this page again using the application's navigation controls (menu, links, and so on) instead of using the browser's navigation controls like Back and Forward.
can you please help me with this error,that will be helpful to me
i am using jdeveloper version 12.1.3

package xxcuso.oracle.apps.fnd.emprec.server;
import oracle.apps.fnd.framework.server.OAApplicationModuleImpl;
import oracle.jbo.Row;
import xxcuso.oracle.apps.fnd.emprec.server.XxEmployeeSearchVO1Impl;
import xxcuso.oracle.apps.fnd.emprec.server.XxEmployeeVO1Impl;
import xxcuso.oracle.apps.fnd.emprec.server.XxEmployeeVO1RowImpl;
//import java.lang.Number;
import java.lang.String;
import oracle.jbo.domain.Number;
import xxcus.oracle.apps.fnd.emprec.server.XxEmployeeSearchVOImpl;
import xxcus.oracle.apps.fnd.emprec.server.XxEmployeeVOImpl;
//import oracle.jbo.domain.Number;
// --- File generated by Oracle ADF Business Components Design Time.
// --- Custom code may be added to this class.
// --- Warning: Do not modify method signatures of generated methods.
public class XxEmployeeAM1Impl extends OAApplicationModuleImpl
/**This is the default constructor (do not remove)
public XxEmployeeAM1Impl()
public void searchEmployee(String empNum, String empName) {
try {
XxEmployeeSearchVO1Impl vo = getXxEmployeeSearchVO1_1();
vo.setMaxFetchSize(-1);
vo.setWhereClause(null);
vo.setWhereClauseParams(null);
vo.setWhereClause("EMPNO = nvl(" + empNum + ",EMPNO)" +
"AND UPPER(ENAME) like UPPER('%" + empName + "%')");
System.out.println("search query - " + vo.getQuery());
vo.executeQuery();
} catch(Exception e) {
e.printStackTrace();
public void initCreateEmp() {
try {
XxEmployeeVO1Impl empCreateVO = getXxEmployeeVO1_1();
empCreateVO.setMaxFetchSize(0);
XxEmployeeVO1RowImpl row = (XxEmployeeVO1RowImpl)empCreateVO.createRow();
// here we are setting the employee number using a DB Sequence
Number empNum = (Number)getOADBTransaction().getSequenceValue("EMPLOYEE_NUMBER_S");
row.setEmpno(empNum);
empCreateVO.insertRow(row);
row.setNewRowState(Row.STATUS_INITIALIZED);
} catch (Exception e) {
e.printStackTrace();
public void initUpdateEmp(String empNum) {
try {
XxEmployeeVO1Impl employeeVO = getXxEmployeeVO1_1();
employeeVO.setWhereClause(null);
employeeVO.setWhereClauseParams(null);
employeeVO.setWhereClause("EMPNO = :1");
employeeVO.setWhereClauseParam(0, empNum);
employeeVO.setMaxFetchSize(-1);
employeeVO.executeQuery();
} catch (Exception e) {
e.printStackTrace();
public void commit() {
try {
XxEmployeeVO1Impl employeeVO = getXxEmployeeVO1_1();
XxEmployeeVO1RowImpl row = (XxEmployeeVO1RowImpl)employeeVO.first();
String savedEmp = row.getEmpno().toString();
getOADBTransaction().commit();
//return savedEmp;
} catch (Exception e) {
e.printStackTrace();
/**Sample main for debugging Business Components code using the tester.
public static void main(String[] args)
launchTester("xxcuso.oracle.apps.fnd.emprec.server", /* package name */
"XxEmployeeAM1Local" /* Configuration Name */);
/**Container's getter for XxEmployeeSearchVO1_1
/* public XxEmployeeSearchVO1Impl getXxEmployeeSearchVO1_1()
return (XxEmployeeSearchVO1Impl)findViewObject("XxEmployeeSearchVO1_1");
/**Container's getter for XxEmployeeVO1_1
public XxEmployeeVO1Impl getXxEmployeeVO1_1()
return (XxEmployeeVO1Impl)findViewObject("XxEmployeeVO1_1");
public XxEmployeeSearchVO1Impl getXxEmployeeSearchVO1_1()
return (XxEmployeeSearchVO1Impl)findViewObject("XxEmployeeSearchVO1_1");
/**Container's getter for XxEmployeeVO1_1
public XxEmployeeVO1Impl getXxEmployeeVO1_1()
return (XxEmployeeVO1Impl)findViewObject("XxEmployeeVO1_1");
}

Developer Mode Error

Hi everyone,
I'm trying to find out what I did wrong closing the connection after calling a Stored Proc, the stored works fine and it made the update and others intructions, the problem comes when I whant to reload some VO's before they data was updated.
Here's the error:
Developer Mode Error - The database connection in the AppsContext object associated with the root application module's transaction has changed while the application module was in use. Cause: This could have been caused if application code called releaseJDBCConnection(), logOut(), or freeWebAppsContext() on the AppsContext object. Note that the AppsContext's JDBC connection is referenced and used by the application module's transaction. Action: Check your application code and remove these calls if the AppsContext was handed out from OADBTransactionImpl.getAppsContext(). (This developer mode check cannot detect the release event, if the same connection instance got checked out again through the getJDBCConnection call on AppsContext after the release.).
and here's my code in the AM
public void methodExample(String famEX){
Connection con = getOADBTransaction().getJdbcConnection();
CallableStatement cs = null;
for(blah blah blah){
if( blah blah){
try{
cs = con.prepareCall("begin dbEschema.SP_Example_Update_Proc(?,?); end;");
//some instructions
//declare and enter the "IN" values
int p_Id_Fam = (Integer.parseInt(famEX));
String p_Item_Id = r.getItemId();
cs.setInt(1, p_Id_Fam);
cs.setString(2, p_Item_Id);
//Execute the procedure
cs.executeUpdate();
cs.close();
con.close();
}catch(Exception e){
System.err.println("Exception: "+ e.getMessage());
}finally{
try{
if(cs != null)
cs.close();
if(con != null)
con.close();
}catch(Exception ex){
System.err.println("2nd Exception: "+ ex.getMessage());
cs = null;
con = null;
I wonder what can be the mistake, I hope you can help me
Regards,
Mentor
Edited by: mentor on 9/08/2010 03:29 PM

Thanks Ajay, Reetesh
I found another way to call without any problem the StroredProc from AOF, this can be helpful for another users.
OADBTransactionImpl oadbtransactionimpl = (OADBTransactionImpl)getDBTransaction();
Row[] rows = getacDVO1().getAllRowsInRange();
for(int i = 0; i < rows.length; i++){
acDVORowImpl r = (acDVORowImpl)rows;
StringBuilder procedureCall = new StringBuilder();
if(r.getSelected().equals("ON")){
try{
int p_Id_Cat = (Integer.parseInt(String));
String p_cve = r.getYourElements();
procedureCall.append("begin SCHEMA.YOUR_STORED_PROCEDURE('").append(p_Id_Cat);
procedureCall.append("', '").append(p_cve_ac).append("'");
procedureCall.append("); end;");
OracleCallableStatement oraclecallablestatement = (OracleCallableStatement)oadbtransactionimpl.createCallableStatement(procedureCall.toString(), -1);
oraclecallablestatement.execute();
getOADBTransaction().commit();
}catch(SQLException sqlexception){
System.err.println("SQL Exception: "+ sqlexception.getMessage());
getOADBTransaction().rollback();
throw OAException.wrapperException(sqlexception);
}catch(Exception e){
System.err.println("Exception: "+ e.getMessage());
getOADBTransaction().rollback();
throw OAException.wrapperException(e);
I hope this example can be very useful to this community
Best Regards,
Mentor

Design mode: Error during component layout. Choose Design Refresh to refresh design mode.

Description Resource Path Location Type
Design mode: Error during component layout. Choose Design > Refresh to refresh design mode. etPlayer.mxml /etPlayer/src Unknown Problem
Refreshing wont work..
any ideas?

Some elements can cause the design view to break, it recently happened to me and this was my solution.
I began by commenting out most of the visual elements from code and going back and forth to design view to try and get it working.
Finally I narrowed it down to the "ToggleButtonBar" component. After I commented this line out the design view was up and running.
This might not be the solution but it will get you back up and running.

Developer Mode Error: Stale Data -- Master Detail OAF Page

Dear Members,
I have created a simple master detail OAF Page by following the below steps:-
1/ Created a MasterEO
2/ Created a DetailEO
3/ Created a MasterDetailAO
4/ Created a MasterVO based on MasterEO
5/ Created a DetailVO based on DetailEO
6/ Created a MasterDetailVL (view link) based on MasterDetailAO
7/ Created an AM
7/ Attached the MasterVO and MasterDetailVL to the AM
8/ Created a simple Master Detail Page in which user can enter the master and detail records. After entering the details user can click on the save button.
Code in AM_
public void createHeader()
+{+
OAViewObject vo = getMasterVO1();
if (vo.getFetchedRowCount() == 0)
+{+
vo.setMaxFetchSize(0);
+}+
Row row = vo.createRow();
vo.insertRow(row);
row.setNewRowState(Row.STATUS_INITIALIZED);
+}+
public void createLines()
+{+
OAViewObject vo = (OAViewObject)getDetailVO1();
if(!vo.isPreparedForExecution())
+{+
vo.setWhereClause("1=2");
vo.executeQuery();
+}+
vo.setWhereClause("1=2");
vo.setWhereClauseParams(null);
vo.executeQuery();
Row row = vo.createRow();
vo.insertRow(row);
row.setNewRowState(Row.STATUS_INITIALIZED);
+}+
Code in ProcessRequest method of CO_
super.processRequest(pageContext, webBean);
OAApplicationModule am = pageContext.getApplicationModule(webBean);
am.invokeMethod("createHeader");
am.invokeMethod("createLines");
I am facing the below error when trying to save the master detail records in the respective OAF Page_
Developer Mode Error: Stale Data_
The requested page contains stale data. This error could have been caused through the use of the browser's navigation buttons (the browser Back button, for example). If the browser's navigation buttons were not used, this error could have been caused by coding mistakes in application code. Please check Supporting the Browser Back Button developer guide - View Object Primary Key Comparison section to review the primary causes of this error and correct the coding mistakes.
Cause:
The number of displayed records, 1, exceeds the actual number of records, 0, in view object AstfAM.DetailVO1. Some of the displayed records may have been deleted.
To proceed, please select the Home link at the top of the application page to return to the main menu. Then, access this page again using the application's navigation controls (menu, links, and so on) instead of using the browser's navigation controls like Back and Forward.
I request the members to help me in resolving the above error.
Many thanks in advance.
Regards,
R4S.

Hi user11991972,
I just faced the same issue and I managed to fixed it using this thread:
Developer Mode Error: Stale Data
In my case, I amended the "Change indicator" checkbox on some of EO attributes.
One of the master attributes was updated by the AM from the detail page, but when navigating back, the master page was not refreshed due to a customer requirement.
But I wonder if it could be of any help in your case...
Regards,
Olivier

Prepayment functionalitygives an error during Order Entry

Hi all,
We have oracle applications Suite - 11i (11.5.10.2) .
At time of prepayment during Order Entry form, we are getting following error.
_"Function not available to this responsibility. Change responsibilities or contact your system administrator" ._
Following is the Navigation Path :
Sales Order Entry > Query with existing SO > Others TAB > Select ACTIONS button > Select PAYMENTS option .
Thanks
Sanjay

Sanjay,
This is because the Function that is invoked when you select the Payments Action from Sales Order Screen has not been granted to your responsibility. The best way is to check the ONT_SUPER_USER menu in application Developer (this is the menu that is used by order Management super user), and see what all functions are there (manily the ones without prompts like 'Sales Orders: Print Payment Receipt'). ANd then compare the same with the menu that your responsibility is using (System Adminsitrator >> Security >> Responsibilities). I think you should get your answer. Please let me know.

Abab error during service entry sheet

dear experts
during service entry sheet the below error dump message is came.
pls any one solver porblem.
document # generated but which is not meet our oringla no range also its not save and terminated.
Update was terminated
System ID....   NEP
Client.......   900
User.....   mmusr
Transaction..   ML81N
Update key...   62B9FADE4AA3F18C8457001F29CC32A8
Generated....   06.01.2010, 14:49:32
Completed....   06.01.2010, 14:49:32
Error Info...   ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC

Check ST22 for abap dump. It looks program try to insert duplicate record. If there is an enhancement in standard tcode debug it. If not ask it to SAP via OSS.

Oracle GL error during journal import- ICM DOWN

Hi all,
I hit an error regarding the Concurrent Manager - Oracle GL during the journal import from GL_INTERFACE table. I've already populate the table with a set of dummy values. i've run the journal import to import the value from the table. i've clicked on correct and search for the Journal Import Data, but Oracle Application prompted me an error - FRM-40350: Query caused no record to retrieve, So i view the request, each and every of the request ID's phase is "Pending" with its status as "Stand by". I checked on the diagnostics and the error code was as following
CONC-DG-INACTIVE ICM DOWN
This request may have to wait on one or more of the following requests to complete before it can begin execution:
i have 2 doubts.firstly i was thinking could it be that i couldnt search for the Journal Import data at Journal: import - Correct was due to the Concurrent manager was down, thus prompting error FRM-40350? please advise. Secondly is that does CONC-DG-INACTIVE ICM DOWN suggest me to startup the concurrent management script? please advise
thanks in advance
Larry
user572825

that i couldnt search for the Journal Import data at Journal: import - Correct was >due to the Concurrent manager was down, thus prompting error FRM-40350?no i dont think so
>please advise. Secondly is that does CONC-DG-INACTIVE ICM DOWN suggest >me to startup the concurrent management script?
check fisrt if there is any runing request and wait till finish if there no runing requeste try to restart the CM if that didnot solve you issue run the CMclean.sql script then restart the CM
fadi hasweh
http://oracle-magic.blogspot.com/
Oracle is not Magic, it just takes years of experience

Getting Account-Determination related Error during Service Entry Approval

Dear Sir,
We have created a Service Order (Purchase Order) with Account-Assignment Category as "Q" and Item-Category as "D" . The In the Purchase Order , Account assignment given was a WBS Element and appropriate GL for expense booking was also mentioned .
Subsequently , we did Service Entry (ML81n) .
Now during the approval of Service Entry Sheet , we are getting following error...
"Account determination for entry 9000 KBS 0001 not possible" .
We request to kindly guide us as what steps need to be followed to resolve this error . We will be highly greatful for the given kind help pl .
With Regards
Sania

HI
.1. In OBYC, check the Account Determination check box is not ticked. This means the account determination is not done from OBYC. It is done as per the account assignment entered in PO. 2. Check OMJJ go to OMJJ and enter teh movement type 101and go to Account geouping folder and click on it
all the line which has KBS in TEKey check the Check acc *** check box than you will not get this error.
3.Goto OBYC double click KBS and enter your valuation grouping code and assign to the G/L accounts and save

Account determination error during service entry for service PO

Dear Experts,
This about service PO. I created PO # 4501517101 & wanted to perform service entry via t/code ML81N. But I'm getting error "147 Account determination for entry OP01 FR1 OP01 not possible"
Appreciate if could anyone assist me on this issue. TQ.
rgds,
nantha

Please correct the assignment in OBYC and also in this error itself u can see one icon of proceed.If you will click on Proceed, then it will take u in to OBYC, where u have to do the corrections.

OAF: Error:Developer Mode Error: Cannot Display Page

Hi Everyone,
When i click on button it shows me the below error:
"You cannot complete this task due to a loss of page data.
Cause:
This error has been encountered because the SESSION_TIMEOUT_RECOVERY_ENABLED profile option value was set to "No" when the page was run with OAPassivationTestMode value, "1."
Action:
Use a combination of responsibility and application that has the SESSION_TIMEOUT_RECOVERY_ENABLED profile option value set to "Yes." For the application level value, the application associated with the page definition will be used for this profile, not the application associated with the responsibility. Or set OAPassivationTestMode value to "2" to bypass this error. Setting the passivation test mode to "2" has the effect of setting the SESSION_TIMEOUT_RECOVERY_ENABLED value to Yes and the application module retention level value to MANAGE_STATE."
How to do this?
plz help me to get out of this?
Thanks.

Hi,
You can try changing
/<yourinstance>/erpapp/iAS/Apache/Jserv/etc
zone.properties session.timeout
Check link
http://mukx.blogspot.com/2007_11_01_archive.html
http://www.solutionbeacon.com/best7.htm
Thanks,
Jit

DI: Error importing Journal entries

does anyone know what this error is refering to?
Add Journal: -5011[JDT1.Account][line 1], 'Row in Transaction with Account No.'
//Code
vJournal.ReferenceDate = CDate(refDate)
vJournal.TaxDate = CDate(refDate)
vJournal.Reference = "Import"
vJournal.Lines.AccountCode = "112000000100101"
vJournal.Lines.ShortName = "_SYS00000000002"
vJournal.Lines.ContraAccount = "341000000100101"
vJournal.Lines.Debit = 30.0
vJournal.Lines.DueDate = CDate(refDate)
vJournal.Lines.Reference1 = "Import"
vJournal.Lines.ReferenceDate1 = CDate(refDate)
vJournal.Lines.TaxDate = CDate(refDate)
vJournal.Lines.Add()
vJournal.Lines.AccountCode = "341000000100101" vJournal.Lines.ShortName = "_SYS00000000102"
vJournal.Lines.ContraAccount = "112000000100101"
vJournal.Lines.Credit = 30.0 vJournal.Lines.DueDate = CDate(refDate)
vJournal.Lines.Reference1 = "Import"
vJournal.Lines.ReferenceDate1 = CDate(refDate)
vJournal.Lines.TaxDate = CDate(refDate)

Hi,
After the Line vJournal.Lines.Add()
You then need to reference the new line with a call to vJournal.Lines.SetCurrentLine(1)

Developer mode error in OAF

Hi All,
I am getting the below error while creating a simple OAF page.
Error: Stale Data
The requested page contains stale data. This error could have been caused through the use of the browser's navigation buttons (the browser Back button, for example). Cause:
The view object XxEmployeeAM.XxEmployeeSearchVO1 contained no record. The displayed records may have been deleted, or the current record for the view object may not have been properly initialized.
I have two custom pages,two controllers , and an AM.
Please help me understand why I am facing the issue.

My Am code is as below:
public class XxEmployeeAMImpl extends OAApplicationModuleImpl {
    /**This is the default constructor (do not remove)
    public XxEmployeeAMImpl() {
    public XxEmployeeVOImpl getXxEmployeeVO1() {
        return (XxEmployeeVOImpl)findViewObject("XxEmployeeVO1");
    /**Sample main for debugging Business Components code using the tester.
    public static void main(String[] args) {
        launchTester("xxcus.oracle.apps.fnd.emprec.server", /* package name */
      "XxEmployeeAMLocal" /* Configuration Name */);
    public void searchEmployee(String empNum, String empName) {
        try {
      XxEmployeeSearchVOImpl vo = getXxEmployeeSearchVO1();
      vo.setMaxFetchSize(-1);
      vo.setWhereClause(null);
      vo.setWhereClauseParams(null);
      vo.setWhereClause("EMPLOYEE_ID = nvl(" + empNum + ",EMPLOYEE_ID)" +
                "AND UPPER(FIRST_NAME) like UPPER('%" + empName + "%')");
      System.out.println("search query - " + vo.getQuery());
      vo.executeQuery();
     } catch(Exception e) {
      e.printStackTrace();
    public void initUpdateEmp(String empNum) {
        try {
      XxEmployeeVOImpl employeeVO = getXxEmployeeVO1();
      employeeVO.setWhereClause(null);
      employeeVO.setWhereClauseParams(null);
      employeeVO.setWhereClause("EMPLOYEE_ID = :1");
      employeeVO.setWhereClauseParam(0, empNum);
      employeeVO.setMaxFetchSize(-1);
      System.out.println("employeeVO.executeQuery(); "+employeeVO.getQuery());
      employeeVO.executeQuery();
      } catch (Exception e) {
       e.printStackTrace();
    public void commit() {
    try {
    XxEmployeeVOImpl employeeVO = getXxEmployeeVO1();
    XxEmployeeVORowImpl row = (XxEmployeeVORowImpl)employeeVO.first();
    String savedEmp = row.getEmployeeId().toString();
    getOADBTransaction().commit();
    //return savedEmp;
    } catch (Exception e) {
    e.printStackTrace();
    public void initCreateEmp() {
        try {
      XxEmployeeVOImpl empCreateVO = getXxEmployeeVO1();
      empCreateVO.reset();
      empCreateVO.setMaxFetchSize(-1);
         empCreateVO.setWhereClause(null);
         empCreateVO.setWhereClauseParams(null);
         if (!empCreateVO.isPreparedForExecution())
         empCreateVO.executeQuery();
      XxEmployeeVORowImpl row = (XxEmployeeVORowImpl)empCreateVO.createRow();
    // here we are setting the employee number using a DB Sequence
        row.setEmployeeId( getOADBTransaction().getSequenceValue("XXTRN_EMP_SEQ"));
        empCreateVO.insertRow(row);
        row.setNewRowState(Row.STATUS_INITIALIZED);
     } catch (Exception e) {
      e.printStackTrace();
    /**Container's getter for XxEmployeeSearchVO1
    public XxEmployeeSearchVOImpl getXxEmployeeSearchVO1() {
        return (XxEmployeeSearchVOImpl)findViewObject("XxEmployeeSearchVO1");

Developer Mode Error during journal entry

Similar Messages

Maybe you are looking for