"Form Personalization" in Oracle e-Business Suite Release 12 still doesn't offer a workaround for suboptimal LOV-Queries

In Oracle E-Business Suite release some list of values (LOV) are not implemented considering the full functionality of the e-Business Suite. The " Project LOV’s" in Payables Invoices (f.e.) always shows all project tasks and expenditure types. Tasks and/or expenditure types, excluded for charges, are shown also. "Charge Allowed flags" and "Transaction Controls" in the Projects module aren’t taken into account in these LOV-queries.

Customers do not like this "feature" ! Being able to select tasks/expenditure types and "hearing afterwards (validation)" that tasks/expenditure types are not allowed for costing. Can we solve this LOV-problem using "Form Personalization (see note 279034.1 on Metalink)" … as long as the standard functionality isn’t implemented as it should be …?

The Form Personalization feature in Oracle e-Business Suite 11.5.10 allows you to ....

declaratively alter the behavior of Forms-based screens, including changing properties, executing builtins, displaying messages, and adding menu entries. Simple LOV properties can also be modified using Form Personalization, including GROUP_NAME, HEIGHT, TITLE, WIDTH, X_POS and Y_POS. At this point in time, the property RECORD_GROUP_QUERY, which would allow you to dynamically change the underlying query of an LOV, cannot be changed. Oracle is considering this functionality for a future release (reference:FormPers_ML_RUP4 Oracle EBS 11.5.10 document on metalink). So, it’s obvious. Forms Personalization is no option in release 11.5.10.

…but maybe there is a solution in e-Business Suite release 12 ….

Oracle e-Business Suite release 12 is an important new release but setting the LOV-property "RECORD_GROUP_QUERY" using Form Personalization isn’t supported. The LOV issue (Payables Invoice project tasks and expenditure types), as mentioned above, isn’t solved in the standard functionality either

… Optimizing LOV-queries wasn’t a point of attention during the definition of the SWAN user interface … ?

LOV-queries may be optimized in future releases. Hopefully by releasing LOV-queries that do consider Projects functionality as "Allow Charges" and "Transaction Controls". If not, new versions of "Form Personalization" may offer workarounds. Let’s wait for release 12.x …. or Fusion Smiley


  1. Amit Bhatnagar June 12, 2009
  2. RM July 25, 2008
  3. Bert Admiraal October 26, 2007
  4. Nitin Jain October 25, 2007
  5. Baskar May 30, 2007
  6. GD May 22, 2007
  7. Bert Admiraal April 20, 2007
  8. Rodney Stephens April 6, 2007
  9. Bert Admiraal March 30, 2007
  10. Nitin Jain March 29, 2007