Misbehavior when LOV is mapped from Shared AM's view object.

Question

Hi,
I found a misbehavior when i try to map a LOV from a Shared AM, whereas it is working fine when i map the LOV from a normal AM.
Let me tell you the details about the sample i created to simulate it.
JDeveloper version - 11.1.1.4.0
Sample Application - Based on HR Schema
Functionality requirement:
Screen has a Select one choice, which should list out all the employees from EMP_DETAILS_VIEW, a view of HR schema, without only one employee.
Sample App Details:
1. Created a Shared Application Module, say "SharedSupplierAM" (i.e. Said the scope of the AM as Application Level)
2. Created a view object “EMP_DETAILS_VIEW” with a bind variable "bind_Emp_Id" and a view criteria "NotSaidEmployeeVC". View criteria's where clause is framed as   ( (EMPLOYEE_ID  Does not equal  :bind_Emp_Id ) ) 3. Shuttled an instance of "EMP_DETAILS_VIEW" into SharedSupplierAM.
4. Created another application module, say "ConsumerAM" (It is not a shared AM).
5. Created a BaseViewObject, say "BaseVO", with an attribute "Employee", to which EMP_DETAILS_VIEW from SharedSupplierAM is mapped as LOV.
6. In the View accessor, shuttled the view criteria NotSaidEmployeeVC and hard coded the value "100" for the bind variable bind_Emp_Id.
7. Shuttled an instance of BaseVo into Consumer AM.
Expected functionality:
LOV should not display the Employee whose id is 100.
Issue:
When i run the AM tester, create a row, it displays all the employees irrespective of the view criteria's where clause i framed, whereas when i map the LOV from normal AM (i.e. not a Shared AM), it displays the employees based on the view criteria's where clause !!.
NOTE:
1. Instead of hard coding the value 100 in the view accessor, If you keep another attribute in the BaseVO, say emp_id, and refer it for the bind variable bind_Emp_id, for the first creation of row alone, it is misbehaving. Once a selection from LOV is made, for further creation of rows, it is displaying the proper list.
2. When i repeat all the above said process but map the LOV from normal AM (i.e. not a Shared AM), everything works fine.
Question:
1. Why this inconsistency?
2. Is it a bug or do i've to change my approach of mapping a LOV when it comes from Shared AM?
Thanks in Advance.
Raguraman
Edited by: Raguraman on May 2, 2011 12:54 AM

Answer 1

Thanks to Jobinesh.
I got answer from Jobinesh, which i specified below so that it will be useful for others.
In case of shared AM as the same VO is being shared by multiple users and the query cannot be dirtied at runtime, so applying VC at run time doesn't have any effect/supported. All the VCs need to be applied on the AM where the ViewObject usage is defined, and pass the bind parameter value while defining ViewAccessor as you did in the sample.
Also note that if one attribute(e.g: LoggedInEmpId) drives value for LOV defined on another one, then the first needs to be added in to Dependencies list for the second one using your VO editor and keep autosubmit=true for the driving one, set partialTrigger to refresh LOV
Raguraman