In Oracle E-Business Suite release 18.104.22.168 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