Dependent LOV in OAF
Dependent LOV in OAF
Dependent LOV in OAF
In this article we are going to create Dependent LOV [List of Values] without writing a single line of code.
Below are the two list of values – LOV we are going to create. Supplieris an independent Lov
and SupplierSite would be the dependent to Supplier one.
.
1. Supplier LOV
2. Supplier Site LOV
User has to select value in SupplierLov first then only user can select value in SupplierSiteLov.
If user will try to select value in SupplierSiteLov without selecting any value in SupplierLov
then error message will come like:
SELECT A.SUPPLIER_ID, A.NAME, A.ON_HOLD_FLAG
FROM FWK_TBX_SUPPLIERS A
SELECT B.SUPPLIER_ID, B.SUPPLIER_SITE_ID,B.SITE_NAME
FROM FWK_TBX_SUPPLIER_SITES B
Ist Step: In this step we will create SupplierLOV
ID : SupplierName.
Search Allowed : True
Selective Search Criteria : True
Prompt : Supplier Name
When a you create a messageLovInput item, JDeveloper automatically creates an inline LOV region
(listOfValues style) & Lov mapping for this item.
* Here I am assuming that you have created one page, ViewObjects, ApplicationModule.
2. Select the listOfValues region, right-click and select New > Region Using Wizard to
quickly create your results table and bind it to the view object you created above.
Here SupName#, OnHoldFlag would be item of typemessageStyledText and ISupplierId would be type
offormValue [Hidden Item].
Set the Search Allowed property of SupName# to True for the result table item corresponding to the
LOV field on the base page.
4. Ist Lov Mapping:
1. Select the messageComponentLayout , right-click and select New > select Item of type
messageLovInput & set these property:
ID : SupplierSiteName.
Search Allowed : True
Selective Search Criteria : True
Prompt : Supplier Site Name
When a you create a messageLovInput item, JDeveloper automatically creates an inline LOV region
(listOfValues style) & Lov mapping for this item.
2. Select the listOfValues region, right-click and select New > Region Using Wizard to
quickly create your results table and bind it to the view object you created above.
Set the Search Allowed property of SupSiteName to True for the result table item corresponding to
the LOV field on the base page.
3. IIIrd Lov Mapping:
��Set the Required property to True for Criteria Items whose values must be populated before the LOV
can be invoked (if not, the OA Framework displays an error message in the LOV window).
��Set the Programmatic Query property to True for any Criteria Items whose values you want to apply
to the WHERE clause programmatically. Tip: you might use this approach; for example, if you have
supplemental Criteria Items whose values should be used for partial matches instead of the default OA
Framework behavior of an exact match (remember that the LOV field value itself is always used for a
partial match).
Final look of Supplier & Supplier Site Lov on page & in Jdeveloper: