Getting error while selecting LOV value

Question

Hi all,
I am getting the below error in R12 apps while selecting the lov value from list (But it is working properly in 11i apps and loacal jdeveloper.)
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 ProjectInformationAM.EmployeeLOVVO1 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.
The lov query is select employee_number,full_name from per_all_people_f
I have tried both internal and external lov but both cases it is showing the error in R12
I have used below code in PR of create page, still no use
if(!am.getEmployeelovVO1().isPreparedForExecution())
am.getEmployeelovVO1().executeQuery();
Row row1 = am.getEmployeelovVO1().createRow();
am.getEmployeelovVO1().insertRow(row1);
row1.setNewRowState(Row.STATUS_INITIALIZED);
Except this lov all lov's working properly,
Any one help on this it is very very urgent....
Thanks

Answer 1

Hi,
I had a similar issue just now, and we fixed it in this way. But the case is probably different compared to your situation.
Situation:
- custom inquiry page
- case: manual search, so not results based or Auto Customization Criteria
- multiple search criteria fields
- separate AM for all the LOV fields
- each LOV has its own VO
- Results table on same page, but with its own VO
- each search criteria field has Lov mapping to the corresponding external Lov region
Issue: when selecting a value via the Lov and coming back into the search page, I received the stale data error.
searched lots of places and finally figured out what was wrong in my case.
Each search field had its BC4J properties set to the VO of the results table. And since we wanted to make a manual search thing, this is not good.
Removing the View Instance value and the View Attribute value in the properties of the search fields resolved the error.
Hoperfully this can help other beginners, like me, in finding a solution for the same mistakes... :)
regards
Ronny