Issue in Creating an "EXISTS" View Criteria

Hi,
Jdev -11.1.1.5.0
Following is the usecase to apply 'Exists' View criteria.
We have one NodesEO and two VOs (NodesVO & TopicsVO) which are from same NodesEO.
NodesVO=> Used to form tree structure . Filtering topics with topic_type is null
SELECT * FROM MD_TOPICS NodesEO WHERE NodesEO.TOPIC_TYPE is null and doc_name is not null ORDER BY NodesEO.DOC_NAME
TopicsVO=> Used to prepare ADF table based on selected tree nodes. Filtering nodes with topic_type is not null
SELECT * FROM MD_TOPICS NodesEO WHERE NodesEO.TOPIC_TYPE is not null
Issue: As of now, iam preparing list of selected nodes from tree and then sending the comma separated string to IN clause.
As there is limitation for maximum number of expressions in a list is 1000.
Iam trying to Create an 'EXISTS' View Criteria. So i got reference to implement the same.
http://one-size-doesnt-fit-all.blogspot.in/2011/02/adf-bc-creating-exists-view-criteria.html
Look like, we need to have ViewLink to create EXISTS VC. I tried to create VL from TopicsVOToNodesVO. At the end, I dragged the TopicsVO instance as a table on jsff.
Here iam unable to filter the rows from NodesVO based on checkbox status.
Iam using transient attribute (checkboxConfirmedStatus- String, checkboxCOnfirmed- boolean). Here i've applied VC on transient attribute by selecting 'In memory' option.
At run time, iam getting exception.
<QueryCollection> <buildResultSet> [1729] java.sql.SQLException: Attempt to set a parameter name that does not occur in the SQL: bind_checkboxConfirmed
Please suggest any option to filter the rows from NodesVO based on checkbox (transient attribute) status before applying 'Exists' clause.
Let me know, if I am in wrong process.
Thanks in advance,
Samba.

Can some one suggest on our issue?
Thanks,
Samba.

Similar Messages

Issue When Creating a Database View

Hi
       I am trying two join two tables using a database view through SE11 and this tables are related to SAP HR.
      As per the requirement we need to create a table join using SQVI in which we are facing a issue where the transaction is freezed as as we create a
      Table join using SQVI.
      So..
      Is their any alternative method to join two tables in HR ABAP apart from SQVI.
      When I try to create a DATBASE VIEW in SE11 it says no relation exists even there is one primary key in both the tables.
      Can we do this using SE11 or is there any other way two join these tables or infotypes..for ex how we join p0008 and p0002
      I am new to this pls help me.(Sry for posting ths in ABAP DEV)..

Hi,
there is a difference between database tables and structures. Structures do no exist in the database, they are just a grouping of fields in ABAP dictionary. P0002 ans P0008 are structures that do not contain any data by definition.
You can create SQVI quick view or database view using database tables PA0002 and PA0008.
Check if all join conditions can be used in your case, you may change or delete join conditions using right-mouse-click.
Regards
Clemens

How to apply common View criteria for all LOV View programatically?

Hi,
In my application I use nearly 100 VOs, which will be mapped as LOV to some base VOs. These VOs are not only for LOV but also will be used directly in screen as read-only table. All these VOs contains EFF_BGN_DTand EFF_END_DT. Requirement is to display only the active records in VO.
We don't want to crete view criteria at design time for each and every VO. Instead we want to have a base ViewObjectImpl class, create at runtime and add this common criteria with the existing view criterias (If any given, which are actually required for the developer for screen specific functionality).
NOTE: As all of our VOs are custom java data source implemented and none of them have queries, we cannot use whereclause API but only ViewCriteria.
We want to create a view criteria, that somewhat looks like the below condition.
           (     (TO_CHAR( EffBgnDt, 'yyyy-mm-dd') <= '2010-02-01' )
             AND (TO_CHAR( EffEndDt, 'yyyy-mm-dd') >= '2010-02-01' )
             OR
           (     (TO_CHAR( EffBgnDt, 'yyyy-mm-dd') <= '2010-02-01' )
             AND (EffEndDt IS NULL )
           )Question:
1. Which is the best place in ViewObject class, where I will be able to create common view criteria, include it with existing criterias.
Thanks in Advance.
Raghu

No it is not working. I've tested. When i test your implementation in my sample using AM tester, it is not at all going inside getCriteriaItemClause(ViewCriteriaItem pViewCriteriaItem). For example when i say, AM.findViewObject(String ViewObjectName), followed by getEstimatedRowCount(), it should apply common filter criteria and give me the result.
Given below required scenario:
Department table:
ID     DEPT_NAME     START_DATE     END_DATE
1     Hr          1-Jan-2010
2     Purchasing     1-Jan-2010     31-Dec-2010
3     Shipping             1-Jan-2010     31-Dec-2055
4     Sales          1-Jan-2010
Common criteria to be applied (Programatically) : :bind_current_date between StartDate and EndDate or :bind_current_date >= StartDate and EndDate is null
VO specific view criteria (may vary VO to VO): DeptName not equal to 'Sales'
Expected Result:
Case 1:
         a. DeptView = AM.findViewObject("DepartmentVO")
         b. DeptView.getEstimatedRowCount()
          It should give me 3 records (Hr, Shipping, Sales)
Case 2:
         a. DeptView = AM.findViewObject("DepartmentVO")
         b. Create View Criteria 'NotSalesDeptVC', which should not list out Sales department.
         c. Apply NotSalesDeptVC using RowSet rowSet = (RowSet) this.findByViewCriteria(NotSalesDeptVC, -1, ViewObject.QUERY_MODE_SCAN_VIEW_ROWS)
         d. rowSet.getEstimatedRowCount()
          It is in-memory filtering, will not disturb the default rowset, should give me 2 records (Hr, Shipping)
Case 3:
         a. DeptView = AM.findViewObject("DepartmentVO")
         b. Apply 'NotSalesDeptVC' to the default row set, followed by executeQuery
         c. DeptView.getEstimatedRowCount()
          It should give me 2 records. (Hr, Shipping)
Case 4:
         a. DeptView = AM.findViewObject("DepartmentVO")
         b. Unapply the applied 'NotSalesDeptVC', followed by executeQuery
         c. DeptView.getEstimatedRowcount()
          It should give me 3 records (Hr, Shipping, Sales)Essence is at any point of time, User should always work with active records. He no need to write extra logic to retrieve only the active records but the base Viewobject impl should have. Note, All of my view objects are custom java data source implemented and not query based. Similarly it does not meant that all of my VOs will be having some business specific View criteria. Some VOs may have. Some VOs may not have. However basic active records criteria is applicable for all VOs

Apply View criteria at runtime to child View object

Hi,
I am facing issues while trying to assign View Criteria to child VO that is part of View hierarchy at runtime.
AM Model:
Parent VO ->
Child VO1
-> Child VO2
View Link between :
Parent VO -> Child VO1
Child VO1 -> Child VO2
I have to apply View criteria at runtime at Child VO1 & Child VO2, i tried setApplyViewCriteriaName from AMImpl for these VO but that doesnt work.
It works for Parent VO, So I concluded Apply VC doesnt work directly for Tree structure.
I then override executeQueryforCollection in the VO however i am never able to get the handle for the VO that is getting executed :
Here's what is happening when i fetch my VO tree from AM :
- Parent VO , Child VO are getting instantiated
- Parent VO executeQueryforCollection called
- ** After this a new instance of Child VO is getting instantiated and i dont have any control of setting the VC based on some custom property
as all get defaulted at this point.
Please suggest what can be done in this case.
PS : i can not hardcode the VC condition at View Link.
- Sam

I was able to set the VC condotinally based on property set at Parent level using following code in executeQueryForCollection :
ApplicationModule am= this.getApplicationModule();
ViewObject vo = am2.findViewObject("ParentView1");
prop = (String)vo.getProperty("Parent_prop");
if(propVo_prop.equals("Y"))
this.setApplyViewCriteriaName("VC");
super.executeQueryForCollection(object, object2, i);
is this the right way ? Any performance bottleneck ? This service can be called for 1000 Id's .
Please suggest if there is some better way.
Thanks
-Sam

ADF 11.1.13 View Criteria

suppose the following senario in ADF 11.1.1.3
i want to add a view criteria on an Date attribute such it value between to values
using befor and after condition not between (to enable one of value is null)
but the ADF give out of index error when i try to edit the criteria next time and i can't run it

Not sure, but you may have hit bug 9245990 (or a variant of it). This happens if you use the same attribute twice in one view criteria. It should be fixed in 11.1.2, so you either update to this version, ask for a back port to your version or use this workaround:
1) create one view criteria for the before part
2) create one view criteria for the after part
3) create the final view criteria combining 1) and 2)
Timo

Named View Criteria with no wizard - I write the SQL

Using JDeveloper/ADF 11.1.2.3.
Is there a way to create a named View Criteria with a SQL Select that is more complex than the wizard can write?
I know that I can write code to create a View Criteria at runtime, but then I can't just drag and drop it like a named one.
One use case:
I have a table named FACILITIES, with a detail table named FACILITY_SERVICES. I want a view criteria for FACILITIES that finds all facilities that have all the required services in a bind variable that is a comma delimited list.
WHERE list.to_vc_array(:requiredServices) /* I wrote this function to translate a comma delimited list to my own vc_arraytype. */
   SUBMULTISET OF
      CAST(MULTISET ( SELECT service
                        FROM facility_services
                       WHERE facilities.facility_id = facility_services.facility_id)
           AS vc_arraytype)With the wizard, I can't even write a simple IN query (match at least one of the required services), much less this more complex one (match ALL the required services).

I'm not sure that this is so bad :)
You need to implement one interface and override one method.
For example:
public class YourVOImpl extends ViewObjectImpl implements ViewCriteriaAdapter {
    protected void create() {
        super.create();
        setViewCriteriaAdapter(this);
    @Override
    public String getViewCriteriaClause(ViewObject viewObject, ViewCriteria viewCriteria) {
        if (viewCriteria == null || viewCriteria.size() == 0) return null;
        return "list.to_vc_array(:requiredServices)\n" +
                  "   SUBMULTISET OF \n" +
                  "      CAST(MULTISET ( SELECT service\n" +
                  "                        FROM facility_services\n" +
                  "                       WHERE facilities.facility_id = facility_services.facility_id)\n" +
                  "           AS vc_arraytype)");
}Dario

View Criteria issue on ADF Tree

Hi,
JDev 11.1.1.5.0
I am facing an issue while displaying ADF tree. I've created ParentVO & ChildVO from a single table with view criteria to filter the nodes.And then created two View links ParentToChild & ChildToChild.
Added VOs & corresponding ViewLinks to ApplicationModule. When I tried to run application module, getting the results as per expectation (applying view criteria at each level).
Now i've dragged the parent vo from data control on to jspx page. when I run the jspx page, it's displaying the tree structure.
Issue is only view criteria is applying for top level nodes(parent VO) but not sub levels. If there is some issue with creation of View criteria then it should give same problem while executing AM. But while running AM, getting the expected results.
It would be great if you provide any clue on this issue
Thanks,
Samba

Thanks for your response.
But my usecase is different. I need to filter the sublevels of the tree.
Following is the sample
Level1
     Level1.1
     Level1.2
     Level1.3
Level2
     Level2.1
     Level2.2
     Level2.3
     Level2.4
Level3
     Level3.1
     Level3.2
     Level3.3
If I gave View Criteria as contains '2' then, Need to filter the nodes contains character 2. Able to filter first level nodes according VC. But VC is not applying for sub levels. Is there any way to set the VC in my case?

Bug in View Criteria for EXISTS operator

Hello!
I have two VO:
DEP (ID, TITLE, STATUS)
EMP (ID, ID_DEP, NAME)
and viewlink DEP.ID <- EMP.ID_DEP
in DEP VO i create view criteria and add two items:
* DEP.STATUS <> 1000
* the EMPVO with EXISTS operator (and after that add condition EMP.NAME contain :nName (bind var))
start app, set "john" in search field, press button "search" and in debug console i found sql for searching in DEP:
SELECT *
FROM (SELECT DEP.ID,
DEP.TITLE,
FROM DEP DEP
where (DEP.STATUS is null OR DEP.STATUS <> 1000)) QRSLT
WHERE ((((EXISTS (SELECT 1
FROM EMP EMP
WHERE ((UPPER(EMP.NAME) LIKE
UPPER('%' || :nName || '%')))
AND (ID = EMP.ID_DEP))))))
in last row present error, must be:
AND (QRSLT.ID = EMP.ID_DEP))))))
coz if no "QRSLT", sql parser think what need compare EMP.ID and EMP.ID_DEP.
Present in JDeveloper 11.1.1.2.0, 11.1.1.3.0.

We have implemented our own ViewCriteriaAdater (derived from oracle.jbo.server.OracleSQLBuilderImpl) and some custom properties to handle this. Overwrite the getFormattedRHSCompareFragment to your needs.
Btw. I think this posting should go to the JDev forum.

Blog post : "Bug in Create/Edit View Criteria Wizard (JDeveloper 11g)"

hi
Using steps 1 to 13 from the blog post "Bug in Create/Edit View Criteria Wizard (JDeveloper 11g)" by Andrejus Baranovskis, I have been able to reproduce the issue he describes.
see http://andrejusb.blogspot.com/2008/12/bug-in-createedit-view-criteria-wizard.html
I the blog post comments he writes "... there was no time for me to fill bug in Metalink ...".
Maybe someone from Oracle can pick it up from this forum post and file it as a bug if it is one (and if possible post the bug number here).
many thanks
Jan Vervecken

The mechanism is to create a reproduceable test case, create a Service Request in metalink.oracle.com, post the test case, and convince the analyst to file it as a bug.
It may be not efficient at some time, but this the way it is handled.
--olaf

Issue with Inline View Criteria

Hi,
I have a VO created on two tables that are joined by a 1:1 association(say Opportunity and Revenue). The query is specified in Expert mode because I need some aggregations performed using analytic functions. Data security predicates are applied on top of this query using a dummy View Criteria. My requirement now is that I need to filter these results using another VC. The issue is that both the tables have attributes with the same name(say Cust ID) and I need to filter based on this using an inline View Criteria. I have done the same declaratively. However, I get an error on hitting the page saying the columns have been ambiguously defined.
On digging through the log, I discovered the test Query fails to prefix the alias before the attribute. So what I get is something similar to this
select (o.id, r.amt, sum(), count(), avg(), o.custId) from opty o, revn r where (o.id in DATA SECURITY PREDICATE) and (custId = :bindCustId)
Is there a way to ensure that the custId can be changed to o.custId???
Note - The View Criteria was created on an attribute from opty table that was exposed i.e in this case, o.custId. Although the query builder shows it correctly while creating the VC declaratively, the issue persists as seen from the logs.
Thanks,
Manoj

Hi experts...
Any pointers to this issue???
Please help!
Regards,
Debolina

11g View Criteria "Exists" Problem!!

Jdeveloper Version 11.1.1.1.0
Example: Model HR
Hi everybody,
I am using the example model HR and i would like to get a view criteria to search the departments by name and employees by the lastname. But i need to get the departments when the "firstNameEmployee" is empty even though they are no employees.
Now i get only the departments with some employee.
That is a example of my concrete problem. In the view must have only the attributes of department.
and here is the query:
( ( ( UPPER(Departments.DEPARTMENT_NAME) LIKE UPPER('%' || :VariableNameDepartament || '%') ) OR ( :VariableNameDepartament IS NULL ) )
AND (EXISTS(SELECT 1 FROM EMPLOYEES Employees WHERE ( ( ( UPPER(Employees.LAST_NAME) = UPPER(:VariableNameEmployee) ) OR ( :VariableNameEmployeeIS NULL ) ) )
AND (Departments.DEPARTMENT_ID = Employees.DEPARTMENT_ID))) )
Thanks!

Hi,
Using view criteria does not change anything. After the query, the view object only contains the filtered rows.
So you can get the result the same way you did before.
Gabriel.
ps: I hope I got your use case correctly. If not please give us some more detail
Edited by: Gabriel Sideras on Sep 27, 2011 3:01 PM

How to create a Tab Link in the existing view

Hello Experts,
My requirement is to make one view as Tab Link.
You must have seen in many existing IC Web screens, there are multiple tabs in the view area and you can toggle between the views by clicking the tab links.
As per my requirement, in the component ICCMP_BT_INR, in one of the views i need to create a tab link for the view Questionnaire which is part of different component ICCMP_SURVEY
Could you please guide me here ?
Regards,
Srikanth

Hi,
I quite certain that you can do this but it is lot of work. You need to create navigations links in run time repository, create plugs, create viewset with views. And then mostly important you need to call appropriate plugs, navigations. I am afraid I can not explain every thing step by step but definitely it requires lot of details and work.
However if you can see some existing examples then you will get an idea. One good example I have worked on is IUICMIO_MAIN and IUICMIO_METER. In this when MIO_ACCOUNT is called in MAIN, it will call two tabs from IUICMIO_METER dynamically.
Hope this helps.
-ASB

Issue with creating materialized view

Hi,
We have a select query (containing joins, aggregates and UNION ALL’s) using which we are creating materialized views. We were able to create these mat views in development environment, however when tried to run the same scripts in a higher environment the creation never completes. The higher environment has three times more data than in Dev currently.
The below operations complete well in time , but when we add “CREATE MATERIALIZED VIEW MAT_VIEW_NAME” to the select query it takes forever (we have cancelled the operation after waiting for more 1 hour)
Select count(1) from the complete Mat. View query -     takes 3.2 min to complete - the query resullts in      3,010,068 rows
Create Normal VIEW using complete Mat. View select query -     takes      3.06 sec     to complete
Create table using complete Mat. View select query     takes 5.75 min to complete - the query resullts in           3,010,068
Does anyone have an idea why this could be happening ? if you have ever faced this kind of issue, can you please provide pointers on how you were able to solve the problem. We are using Oracle 11g.
Let me know if I have to provide any other information for you to understand the issue better.
Thanks

SELECT vis.uid, findet.yr, findet.ect, vis.ind,
tm_view.col1_id, tm_view.col1_name,
tm_view.col2_id, tm_view.col2_name,
tm_view.col3_id, tm_view.col3_name,
clnt.cl_id, clnt.cl_nm,
prodparent_view.parent_cd,
prodparent_view.parent_desc,
prod_view.parent_cd,
prod_view.parent_desc,
prod_view.child_cd,
prod_view.child_desc,
SUM (value1), SUM (value2),
SUM (value3), SUM (value4),
SUM (value5), SUM (value6),
SUM (value7), SUM (value8),
SUM (value9), SUM (value10),
SUM (value11), SUM (value12)
FROM vis,
(SELECT *
FROM analytic_e,
(SELECT table_val
FROM TAB_CHECK s
WHERE s.tgt_table_nm = 'ANALYTIC'
AND s.table_val = 'ANALYTIC_E')
WHERE table_val = 'ANALYTIC_E'
UNION ALL
SELECT *
FROM analytic_o,
(SELECT switch_val
FROM tab_check s
WHERE s.tgt_table_nm = 'ANALYTIC'
AND s.switch_val = 'ANALYTIC_O')
WHERE switch_val = 'ANALYTIC_O') findet,
prod_view,
prodparent_view,
tm_view,
clnt,
(select to_number(to_char(ref_dt,'yyyy'))-1 year_agg from DATE_TABLE) tbabt
WHERE tbabt.yr = findet.yr
AND vis.cl_key = findet.cl_key
AND tm_view.hi_key = findet.hi_key
AND prod_view.child_cd = findet.prod_cd
AND clnt.cl_key = findet.cl_key
AND prodparent_view.child_cd = prod_view.parent_cd
GROUP BY vis.uid, findet.yr, findet.ect, vis.ind,
tm_view.col1_id, tm_view.col1_name,
tm_view.col2_id, tm_view.col2_name,
tm_view.col3_id, tm_view.col3_name,
clnt.cl_id, clnt.cl_nm,
prodparent_view.parent_cd
prodparent_view.parent_desc
prod_view.parent_cd
prod_view.parent_desc
prod_view.child_cd
prod_view.child_desc
Higher Environment
| Id | Operation | Name | Rows | Bytes |TempSpc| Cost (%CPU)| Time | Pstart| Pstop |
| 0 | SELECT STATEMENT | | 57M| 65G| | 20M (1)| 66:48:28 | | |
| 1 | HASH GROUP BY | | 57M| 65G| 73G| 20M (1)| 66:48:28 | | |
|* 2 | HASH JOIN | | 57M| 65G| | 109K (2)| 00:21:58 | | |
| 3 | TABLE ACCESS BY INDEX ROWID | HIER | 2100 | 244K| | 172 (0)| 00:00:03 | | |
|* 4 | INDEX RANGE SCAN | UK_HIER | 2100 | | | 16 (0)| 00:00:01 | | |
|* 5 | HASH JOIN | | 57M| 59G| | 109K (1)| 00:21:52 | | |
| 6 | VIEW | VW_GBF_25 | 1908 | 868K| | 2612 (1)| 00:00:32 | | |
| 7 | HASH GROUP BY | | 1908 | 141K| | 2612 (1)| 00:00:32 | | |
| 8 | VIEW | | 45107 | 3347K| | 2609 (1)| 00:00:32 | | |
| 9 | UNION-ALL | | | | | | | | |
| 10 | HASH UNIQUE | | 22518 | 1473K| 1872K| 1010 (1)| 00:00:13 | | |
|* 11 | TABLE ACCESS FULL | HIER | 22518 | 1473K| | 650 (1)| 00:00:08 | | |
| 12 | HASH UNIQUE | | 22518 | 1165K| 1512K| 947 (1)| 00:00:12 | | |
|* 13 | TABLE ACCESS FULL | HIER | 22518 | 1165K| | 650 (1)| 00:00:08 | | |
| 14 | HASH UNIQUE | | 71 | 1917 | | 652 (1)| 00:00:08 | | |
|* 15 | TABLE ACCESS FULL | HIER | 22518 | 593K| | 650 (1)| 00:00:08 | | |
|* 16 | HASH JOIN | | 64M| 38G| 4936K| 106K (1)| 00:21:16 | | |
| 17 | VIEW | | 45107 | 4404K| | 2609 (1)| 00:00:32 | | |
| 18 | UNION-ALL | | | | | | | | |
| 19 | HASH UNIQUE | | 22518 | 1473K| 1872K| 1010 (1)| 00:00:13 | | |
|* 20 | TABLE ACCESS FULL | HIER | 22518 | 1473K| | 650 (1)| 00:00:08 | | |
| 21 | HASH UNIQUE | | 22518 | 1165K| 1512K| 947 (1)| 00:00:12 | | |
|* 22 | TABLE ACCESS FULL | HIER | 22518 | 1165K| | 650 (1)| 00:00:08 | | |
| 23 | HASH UNIQUE | | 71 | 1917 | | 652 (1)| 00:00:08 | | |
|* 24 | TABLE ACCESS FULL | HIER | 22518 | 593K| | 650 (1)| 00:00:08 | | |
|* 25 | HASH JOIN | | 3021K| 1550M| 15M| 24492 (1)| 00:04:54 | | |
| 26 | PARTITION HASH ALL | | 491K| 10M| | 1059 (1)| 00:00:13 | 1 | 16 |
| 27 | MAT_VIEW ACCESS FULL | VIS | 491K| 10M| | 1059 (1)| 00:00:13 | 1 | 16 |
|* 28 | HASH JOIN | | 388K| 190M| 6056K| 12929 (1)| 00:02:36 | | |
| 29 | TABLE ACCESS FULL | CLNT | 64540 | 5294K| | 411 (1)| 00:00:05 | | |
|* 30 | HASH JOIN | | 388K| 159M| | 4072 (1)| 00:00:49 | | |
| 31 | TABLE ACCESS FULL | DATE_TABLE | 2 | 16 | | 3 (0)| 00:00:01 | | |
| 32 | VIEW | | 582K| 235M| | 4065 (1)| 00:00:49 | | |
| 33 | UNION-ALL | | | | | | | | |
| 34 | NESTED LOOPS | | 272K| 52M| | 1860 (1)| 00:00:23 | | |
|* 35 | TABLE ACCESS BY INDEX ROWID| TAB_CHECK | 1 | 46 | | 1 (0)| 00:00:01 | | |
|* 36 | INDEX UNIQUE SCAN | SYS_C0041157 | 1 | | | 0 (0)| 00:00:01 | | |
| 37 | PARTITION RANGE ALL | | 272K| 40M| | 1859 (1)| 00:00:23 | 1 |1048575|
| 38 | TABLE ACCESS FULL | ANALYTIC_E | 272K| 40M| | 1859 (1)| 00:00:23 | 1 |1048575|
| 39 | NESTED LOOPS | | 309K| 58M| | 2205 (1)| 00:00:27 | | |
|* 40 | TABLE ACCESS BY INDEX ROWID| TAB_CHECK | 1 | 46 | | 1 (0)| 00:00:01 | | |
|* 41 | INDEX UNIQUE SCAN | SYS_C0041157 | 1 | | | 0 (0)| 00:00:01 | | |
| 42 | PARTITION RANGE ALL | | 309K| 44M| | 2204 (1)| 00:00:27 | 1 |1048575|
| 43 | TABLE ACCESS FULL | ANALYTIC_O | 309K| 44M| | 2204 (1)| 00:00:27 | 1 |1048575|
Development
| Id | Operation | Name | Rows | Bytes |TempSpc| Cost (%CPU)| Time | Pstart| Pstop |
| 0 | SELECT STATEMENT | | 1696K| 1276M| | 291K (1)| 00:58:20 | | |
| 1 | HASH GROUP BY | | 1696K| 1276M| 1325M| 291K (1)| 00:58:20 | | |
|* 2 | HASH JOIN | | 1696K| 1276M| | 9721 (2)| 00:01:57 | | |
| 3 | VIEW | | 15464 | 1132K| | 1855 (1)| 00:00:23 | | |
| 4 | UNION-ALL | | | | | | | | |
| 5 | HASH UNIQUE | | 7681 | 502K| | 618 (1)| 00:00:08 | | |
|* 6 | TABLE ACCESS FULL | HIER | 7681 | 502K| | 617 (1)| 00:00:08 | | |
| 7 | HASH UNIQUE | | 7681 | 375K| | 618 (1)| 00:00:08 | | |
|* 8 | TABLE ACCESS FULL | HIER | 7681 | 375K| | 617 (1)| 00:00:08 | | |
| 9 | HASH UNIQUE | | 102 | 2448 | | 618 (1)| 00:00:08 | | |
|* 10 | TABLE ACCESS FULL | HIER | 7681 | 180K| | 617 (1)| 00:00:08 | | |
|* 11 | HASH JOIN | | 371K| 252M| | 7847 (2)| 00:01:35 | | |
| 12 | VIEW | | 15464 | 1510K| | 1855 (1)| 00:00:23 | | |
| 13 | UNION-ALL | | | | | | | | |
| 14 | HASH UNIQUE | | 7681 | 502K| | 618 (1)| 00:00:08 | | |
|* 15 | TABLE ACCESS FULL | HIER | 7681 | 502K| | 617 (1)| 00:00:08 | | |
| 16 | HASH UNIQUE | | 7681 | 375K| | 618 (1)| 00:00:08 | | |
|* 17 | TABLE ACCESS FULL | HIER | 7681 | 375K| | 617 (1)| 00:00:08 | | |
| 18 | HASH UNIQUE | | 102 | 2448 | | 618 (1)| 00:00:08 | | |
|* 19 | TABLE ACCESS FULL | HIER | 7681 | 180K| | 617 (1)| 00:00:08 | | |
|* 20 | HASH JOIN | | 122K| 71M| | 5987 (2)| 00:01:12 | | |
|* 21 | TABLE ACCESS FULL | HIER | 7681 | 915K| | 617 (1)| 00:00:08 | | |
|* 22 | HASH JOIN | | 122K| 57M| 4512K| 5368 (2)| 00:01:05 | | |
|* 23 | HASH JOIN | | 9556 | 4395K| 3856K| 2409 (2)| 00:00:29 | | |
| 24 | TABLE ACCESS FULL | CLNT | 74426 | 2979K| | 310 (1)| 00:00:04 | | |
|* 25 | HASH JOIN | | 9556 | 4012K| | 1710 (2)| 00:00:21 | | |
| 26 | TABLE ACCESS FULL | DATE_TABLE | 1 | 7 | | 3 (0)| 00:00:01 | | |
| 27 | VIEW | | 19112 | 7894K| | 1706 (2)| 00:00:21 | | |
| 28 | UNION-ALL | | | | | | | | |
| 29 | MERGE JOIN CARTESIAN | | 19111 | 4068K| | 1701 (2)| 00:00:21 | | |
|* 30 | TABLE ACCESS FULL | TAB_CHECK | 1 | 49 | | 3 (0)| 00:00:01 | | |
| 31 | BUFFER SORT | | 248K| 40M| | 1698 (2)| 00:00:21 | | |
| 32 | PARTITION RANGE ALL| | 248K| 40M| | 1698 (2)| 00:00:21 | 1 |1048575|
| 33 | TABLE ACCESS FULL | ANALYTIC_E | 248K| 40M| | 1698 (2)| 00:00:21 | 1 |1048575|
| 34 | MERGE JOIN CARTESIAN | | 1 | 537 | | 5 (0)| 00:00:01 | | |
| 35 | PARTITION RANGE ALL | | 1 | 488 | | 2 (0)| 00:00:01 | 1 |1048575|
| 36 | TABLE ACCESS FULL | ANALYTIC_O | 1 | 488 | | 2 (0)| 00:00:01 | 1 |1048575|
| 37 | BUFFER SORT | | 1 | 49 | | 3 (0)| 00:00:01 | | |
|* 38 | TABLE ACCESS FULL | TAB_CHECK | 1 | 49 | | 3 (0)| 00:00:01 | | |
| 39 | PARTITION HASH ALL | | 810K| 16M| | 1456 (2)| 00:00:18 | 1 | 16 |
| 40 | MAT_VIEW ACCESS FULL | VIS | 810K| 16M| | 1456 (2)| 00:00:18 | 1 | 16 |
-----------------------------------------------------------------------------------------------------------------------------------------

Issue with creating a view

Oracle gurus,
pls assist me to modify the following query to create my own view that will allow me to display department name of the employee assignment screen.
People>Enter & Maintain>Assignment
Organization
SELECT plrl.letter_request_id letter_request_id,ads_adi_utils_pkg.decode_nls_lookup('TITLE',papf.title,plrl.business_group_id) title
, SUBSTR(papf.first_name,1,1)||'.' init
, papf.first_name first_name
, papf.last_name last_name
, hou.name organisation
, pad.address_line1 address_line_1
, pad.address_line2 address_line_2
, pad.address_line3 address_line_3
, pad.town_or_city town
, pad.postal_code post_code
, pav.name vacancy
, pj.name job
, pp.name position
FROM per_all_people_f papf
, per_letter_request_lines plrl
, per_all_assignments_f paaf
, per_addresses pad
, per_all_vacancies pav
, hr_all_organization_units hou
--, HR_ALL_ORGANIZATION_UNITS_TL hou1
, per_jobs pj
, per_all_positions pp
WHERE paaf.person_id = papf.person_id
AND plrl.assignment_id = paaf.assignment_id
AND paaf.vacancy_id = pav.vacancy_id(+)
AND papf.person_id = pad.person_id(+)
AND pad.primary_flag(+) = 'Y'
--AND hou1.organization_id = hou.organization_id(+)
AND paaf.organization_id = hou.organization_id(+)
AND pav.job_id = pj.job_id(+)
AND pav.position_id = pp.position_id(+)
AND paaf.effective_end_date = (SELECT MAX(effective_end_date)
FROM per_all_assignments_f WHERE assignment_id = paaf.assignment_id)
AND papf.effective_start_date = (SELECT MAX(effective_start_date)
FROM per_all_people_f WHERE person_id = papf.person_id)
Please help me to modify the above query so that the output must show the employee assignment organization and not the vacancy org.
Please help

remove the effective date conditions from your query -
AND paaf.effective_end_date = (SELECT MAX(effective_end_date)
FROM per_all_assignments_f WHERE assignment_id = paaf.assignment_id)
AND papf.effective_start_date = (SELECT MAX(effective_start_date)
FROM per_all_people_f WHERE person_id = papf.person_id)and add the below -
AND sysdate between paaf.effective_start_date and paaf.effective_end_date
AND sysdate between papf.effective_start_date and papf.effective_end_dateCheers,
Vignesh

Issue while applying View Criteria

Hi all,
We have a taskflow which has View Criteria as the input parameter.
When the taskflow is invoked, the View Criteria is set in the pageFlowScope.
Requirement is that we need to apply this view criteria to a View object.
When we applied the view criteria to the View object and executed the query, an SQLException is being thrown
(Missing IN or OUT Parameter at index::1)
In the ManagedBean's method, verified if the view criteria has bindVariables:
VariableValueManager variableValueManage = vc.ensureVariableManager();
System.err.println("Name :"+variableValueManage.getVariableValue("pName"));
Confirmed that the bind variable is carrying the appropriate value.
This View Criteria when applied to the corresponding VO and executed, java.sql.SQLException is thrown:
ViewObjectImpl testVO = gettestVO() ;
ViewCriteriaManager vcm = testVO.getViewCriteriaManager();
vcm.applyViewCriteria(quickSearchViewCriteria);
testVO.executeQuery();
Exception: java.sql.SQLException: Missing IN or OUT parameter at index:: 1
In the query, the bind Variable "pName" is not binded, though the view criteria has the value.
Thanks in advance,
Raghu

Hi all,
We have a taskflow which has View Criteria as the input parameter.
When the taskflow is invoked, the View Criteria is set in the pageFlowScope.
Requirement is that we need to apply this view criteria to a View object.
When we applied the view criteria to the View object and executed the query, an SQLException is being thrown
(Missing IN or OUT Parameter at index::1)
In the ManagedBean's method, verified if the view criteria has bindVariables:
VariableValueManager variableValueManage = vc.ensureVariableManager();
System.err.println("Name :"+variableValueManage.getVariableValue("pName"));
Confirmed that the bind variable is carrying the appropriate value.
This View Criteria when applied to the corresponding VO and executed, java.sql.SQLException is thrown:
ViewObjectImpl testVO = gettestVO() ;
ViewCriteriaManager vcm = testVO.getViewCriteriaManager();
vcm.applyViewCriteria(quickSearchViewCriteria);
testVO.executeQuery();
Exception: java.sql.SQLException: Missing IN or OUT parameter at index:: 1
In the query, the bind Variable "pName" is not binded, though the view criteria has the value.
Thanks in advance,
Raghu

Issue in Creating an "EXISTS" View Criteria

Similar Messages

Maybe you are looking for