View Criteria non required field

Hello,
I have a view object with a viewCriteria with the following condition: No between no1_prm and no2_prm, the condition for required is optional and I checked ignore null values.
The bind variables of the view object are not required.
I made a page with a search form (af:query) but I want that even I complete only one field (no1_prm or no2_prm) to receive the result for that parameter. Now I receive error that the filed is required.
How can I make :
- when I complete one value for the parameter to receive exact value for that parameter
- when I complete the two values for the parameters to receive all the numbers between the two parameters.
Thank you in advance.

I set only that condition : No between no1_prm and no2_prm with validation optional and ignore null values checked.
The all view object where clause is :
( ( NR BETWEEN :nr_prm1 AND :nr_prm2 ) OR ( :nr_prm1 IS NULL AND :nr_prm2 IS NULL ) )
I mention that in my page I must to have only : No label : input text for no1_prm - input text for no2_prm. If I complete only input text for no1_prm I receive the error for required field.
Thank you.

Similar Messages

View Criteria and Transient fields

Hello, I was wondering, is it possible to have View Criteria set on a Transient field? I have created a Transient field named "Field1". I then go to the Query tab in my ViewObject and select the option "Create new view criteria". Here I select the option "Add Item" and from Attribute list I select my field "Field1". However what I notice is that the "View Object Where Clause" does not get updated when the attribute I select is a transient field - when it is a normal field (i.e. from an Entity) it does get updated. This means that I am unable to create view criteria for transient fields. Is there a way how I can manage to do this?

Transient attributes are not based on database columns. This means that WHERE-clause on transient attributes is a non-sense. It makes sense to add conditions on transient attributes only if the view criteria will be executed as a filter in memory (see the "Query Execution Mode" property in the "Create View Criteria" dialog).

Power view in SharePoint - Required fields not working!!!

Hi,
We have SharePoint 2013 and SQL Server 2014 and SSRS in SharePoint integrated mode.
We have a "Microsoft BI Semantic Model for Power View"-data connection in a document library and by clicking it users can create their own Power View reports.
We have in the document library defined a couple of columns as required.
When a user saves their Power View report(File->Save as) to the document library, the required fields are left blank. They are not checked!!!
WHY?
Does Power View use REST when saving to the document library?
This question should be in SQL Server/Power View/SharePoint -forumns, but MSDN forces you to select only one.
How can we enforce the checking of required columns???

It might be the result of nested script tags.
<script type="text/javascript">
<!--
<!--
Remote one of those opening tags and remove the closing tag in between the scripts.
Also, I'm not sure if you are aware, but your site looks completely broken in Firefox. Edges are ragged and the text runs off the page in places. This is the result of using a graphics program to create your html. Image ready slices are fine for prototyping, but not suitable for production work because they create code that is fragile and too rigid.
I also would not use the Flash header you have used just to display imges. I suggest using a more accessible method.

View criteria with date field in ADF

Hi ADF Experts,
I have a requirement like.I have a VO with query let say "Select * from Employee"
I have created viewCriteria in that VO like "HireDate between 'abc' and 'XYZ'.
In AMImpl class I have written, one fuction to apply viewcriteria on VO and execute query.
Expose that function as service method, and execution form backing bean.
It is working properly for all other column except the date field.(May be beause of date format, as we cannot apply To_Char, or ToDate in view criterai for date format)
Tried all possible combination but no luck
Please help

Hi,
The below link might be helpful for you
http://www.oracle.com/technetwork/developer-tools/adf/learnmore/59-table-filter-by-data-range-176653.pdf
Thanks
Prabhat

Box for view only/non-updateable fields

How can I create a box for a column in JHeadstart that is marked as non-updateable (Update Allowed = false)? I have tried some code in the Additional Properties but have not been able to find the mix. Using disable will put a box, but it dims both the lable and the value and is unacceptablely light.
Edited by: user589963 on Apr 22, 2013 12:49 PM

I tried a different approach by setting the attribute in JHeadstart to Updateable = False and then put this code in the Additional Properties space in Expert Mode:
contentStyle="border:1px solid;padding:0 5px 0;"
That created the box and it was not dimmed like it was when the field was disabled in JHeadstart before. But for all attributes that do not have a value present the box is elevated up into the field above it. The box is not elevated if there is a value in it. Appears to be a bug with JHeadstart. Was just curious if there is other code that would work in the Additional Properties space that would effect how the CSS displays the box.

LOV view criteria missing in af:query field when AM pooling is disabled

Hi all,
Again, another strange behaviour with fields in af:query when AM pooling is disabled.
I have a field with a LOV in the af:query area. This LOV has a view criteria that involves a bind variable. In the VO, the view accessor for this LOV applies the view criteria and sets the bind variable. When AM pooling is disabled, double clicking a row or clicking the OK button in the LOV window removes the where clause defined by the view criteria. When activation occurs, the bind variable still exists but the framework doesn't know where to apply it...
Any help will be very appreciated,
Thanks
JDeveloper 11.1.1.3.0 with ADF BC
We've just realised that this behaviour occurs even when pooling is enabled. So this is becoming now a serious problem.
The scenario is as following: We have two LOVs in the search area (af:query). One of them is dependent on the other. Then, this second LOV has a view criteria and a bind variable representing the value selected for the first LOV. The query for the second LOV is filtered properly, but once a value has been selected and the LOV window dismissed, nothing is returned to the field.
We have observed that SecondLovViewImpl.executeQueryForCollection() method executes twice:
1. When LOV is opened: here, the bind variable is correctly setted.
2. When a row in the LOV table is selected: here, the bind variable is reset to null.
The log says (in Spanish):
<OracleSQLBuilderImpl><bindParamValue> [46062] Binding null of type 12 for "bindProgram"
<FacesCtrlLOVBinding$ListOfValuesModelImpl><_getRowFromSelectedRowKey> ADFv: No se ha encontrado ninguna fila para rowKey: [oracle.jbo.Key[P1 SP11 ]].
I would be very grateful if somebody asked me... even for saying "this is nonsense", "this is a known bug", "cascading LOVs are not supported by af:query", or anything else... If a code snippet is required, I'll put it as well.
Thanks in advance
Edited by: Marge on 02-sep-2010 5:41

Hi,
there are two bugs associated with bind variables in successors that I am aware of. One of them is supposed to be fixed in the next patch set, another one is still open. However, both problems were found with AM pooling enabled as well, so I don't know this is the same problem (though it sounds like). If you can, I suggest to create a reproducible testcase on one of the Oracle database schema, like HR or OE, and file a bug. If you don't have a time for or access to support, send the test case in a zip file (rename ".zip" to ".unzip") to the mail Id you find in my OTN profile. However, be aware that when I file the bug then it wont be visible for you, nor can it be escalated on your behalf. Anyway, at least it would get filed
Frank

Set view criteria on af:query choice LOV field

i have an af:query. one of the fields is a choice. the LOV for the choice come from a VO. i need to set view criteria for the query for the LOV for the choice. that is, the query for the values of the choice requires view criteria.
moreover, that search criteria is only known by the view. because the hooks for the choice are set up entirely in the model, i don't see how it would ever be possible to use values from the view to define the query for the LOV for the choice.
any ideas?

Assuming that you can have a method at the AM level that sets the viewCriteria for your VO, you can drag this method to the page flow to be executed before you go into the query page - this will set the right condition for the list that needs to populate the LOV.
Then the query component can use that VO as an LOV like this:
http://blogs.oracle.com/shay/2009/12/adf_query_with_parameters_and_1.html

Non key field in Maintainance View

Hi,
I have generated a maintainance view for a Z table. I want to sort data from SM30 by means of a selection screen, for that, in the 'View Flds' tab in the maintainance view, i have entered a 'S' for which ever fields i want to filter the data on.
When i execute the table maintainance, i am able to see only the key fields and not the non-key ones in the selection popup, though i have put a 'S' for both, the key and non-key fields.
Can anyone please let me know how to get the non-key fields on the selection popup when i execute the maintainance view?
Cheers,
Raghav.

Not possible via this functionality. A workaround was suggested by Raymond in this thread:
Transaction code for Table Maitainence for table
Thomas

Re-order fields of a view criteria

We have a view and in that view we defined a view criteria.
The view criteria is based on 5 different views. I need to sort the order of attributes. And this cannot be done by sort order since we don't have access to all the attributes in the one "View Object"
Is it possible to bind the af query and then sort the order of attributes?

try in the query :
order by :variable,:variable2
:)

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

How can I use a single query panel with two view criteria?

Hi all,
I have a requirement to allow users to change the "display mode" on a search results tree table for an advanced search page. What this will do is change the structure of how the data is laid out. In one case the tree table is 3 levels deep, in the other case it's only 2 with different data being at the root node.
What I've done so far:
1) I exposed the data relationship for these two ways of viewing the data in the application module's data model.
2) I created a view criteria in the two view objects that are at the root of the relationships, where (for simplicity sake) I'm only comparing a single field.
This is in one view object:
<ViewCriteria
    Name="PartsVOCriteria"
    ViewObjectName="gov.nasa.jpl.ocio.qars.model.views.PartsVO"
    Conjunction="AND">
    <Properties>... </Properties>
    <ViewCriteriaRow
      Name="vcrow23"
      UpperColumns="1">
      <ViewCriteriaItem
        Name="PartDiscrepantItemsWithIRVO"
        ViewAttribute="PartDiscrepantItemsWithIRVO"
        Operator="EXISTS"
        Conjunction="AND"
        IsNestedCriteria="true"
        Required="Optional">
        <ViewCriteria
          Name="PartDiscrepantItemsWithIRVONestedCriteria"
          ViewObjectName="gov.nasa.jpl.ocio.qars.model.views.PartDiscrepantItemsWithIRVO"
          Conjunction="AND">
          <ViewCriteriaRow
            Name="vcrow26"
            UpperColumns="1">
            <ViewCriteriaItem
              Name="InspectionRecordNumber"
              ViewAttribute="InspectionRecordNumber"
              Operator="="
              Conjunction="AND"
              Value=""
              Required="Optional"/>
          </ViewCriteriaRow>
        </ViewCriteria>
      </ViewCriteriaItem>
    </ViewCriteriaRow>
</ViewCriteria>
and this is in the other view object:
<ViewCriteria
      Name="IRSearchCriteria"
      ViewObjectName="gov.nasa.jpl.ocio.qars.model.views.InspectionRecordVO"
      Conjunction="AND">
      <Properties>... </Properties>
      <ViewCriteriaRow
         Name="vcrow7"
         UpperColumns="1">
         <ViewCriteriaItem
            Name="InspectionRecordNumber"
            ViewAttribute="InspectionRecordNumber"
            Operator="="
            Conjunction="AND"
            Required="Optional"/>
      </ViewCriteriaRow>
   </ViewCriteria>
3) I had a query panel and tree table auto-generated by dragging the data control for ONE of the view object data relationship that's exposed in the app module. Then I created a second query panel and tree table the same way but using the data control for the other. I'm hiding one of the query panels permanently and toggling the visibility of the tree tables based on the display mode the user chooses. Both tables have separate bindings and iterators.
This is a portion of the page definition:
<executables>
    <variableIterator id="variables"/>
    <searchRegion Criteria="IRSearchCriteria"
                  Customizer="oracle.jbo.uicli.binding.JUSearchBindingCustomizer"
                  Binds="InspectionRecordVOIterator"
                  id="IRSearchCriteriaQuery"/>
    <iterator Binds="InspectionRecordVO" RangeSize="25"
              DataControl="QARS_AppModuleDataControl"
              id="InspectionRecordVOIterator" ChangeEventPolicy="ppr"/>
    <iterator Binds="Root.QARS_AppModule.PartsVO1"
              DataControl="QarsMasterAppModuleDataControl" RangeSize="25"
              id="PartsVO1Iterator"/>
    <searchRegion Criteria="PartsVOCriteria"
                  Customizer="oracle.jbo.uicli.binding.JUSearchBindingCustomizer"
                  Binds="PartsVO1Iterator" id="PartsVOCriteriaQuery"/>
</executables>
4) I've created a custom queryListener to delegate the query event.
This is in my advanced search jsp page:
<af:query id="qryId1" headerText="Search" disclosed="true"
                  value="#{bindings.IRSearchCriteriaQuery.queryDescriptor}"
                  model="#{bindings.IRSearchCriteriaQuery.queryModel}"
                  queryListener="#{pageFlowScope.SearchBean.doSearch}"
                  queryOperationListener="#{bindings.IRSearchCriteriaQuery.processQueryOperation}"
                  resultComponentId="::resId2" maxColumns="1"
                  displayMode="compact" type="stretch"/>
This is in my backing bean:
public void doSearch(QueryEvent queryEvent) {
      String bindingName = flag
         ? "#{bindings.IRSearchCriteriaQuery.processQuery}"
         : "#{bindings.PartsVOCriteriaQuery.processQuery}";
      invokeMethodExpression(bindingName, queryEvent);
   private void invokeMethodExpression(String expr, QueryEvent queryEvent) {
      FacesContext fctx = FacesContext.getCurrentInstance();
      ELContext elContext = fctx.getELContext();
      ExpressionFactory eFactory = fctx.getApplication().getExpressionFactory();
      MethodExpression mexpr =
         eFactory.createMethodExpression(elContext, expr, Object.class, new Class[] { QueryEvent.class });
      mexpr.invoke(elContext, new Object[] { queryEvent });
When no inspection record number (the only search field so far) is supplied in the query panel, then it behaves correctly. Namely, the tree tables shows all search results. However, when an inspection record number is supplied the tree table that was created with the query panel in use (remember there are two query panels, one of them is hidden) shows a single result (this is correct) while the other tree table (the one with the hidden query panel that isn't in use) shows all results (this is NOT correct).
Is what I'm trying to accomplish even doable? If so, what am I missing?
I'm using JDeveloper 11.1.1.7
Thanks,
Bill

I ended up keeping one query panel permanently visible and the other permanently hidden. When performing a search using the table that has the hidden query panel, I seed the query descriptor for the hidden query panel using the visible query panel's query descriptor and then delegate the request:
   public void doSearch(QueryEvent queryEvent) {
      String bindingName = null;
      if(isIrTableRendered()) {
         bindingName = "#{bindings.IRSearchCriteriaQuery.processQuery}";
      } else {
         seedPartsQueryDescriptor();
         bindingName = "#{bindings.PartsVOCriteriaQuery.processQuery}";
         queryEvent = new QueryEvent(partsQuery, partsQuery.getValue());
      invokeMethodExpression(bindingName, queryEvent);
   private void seedPartsQueryDescriptor() {
      ConjunctionCriterion criterion = irQuery.getValue().getConjunctionCriterion();
      for(Criterion criteria : criterion.getCriterionList()) {
         AttributeCriterion attributeCriteria = (AttributeCriterion)criteria;
         List values = attributeCriteria.getValues();
         String qualifiedName = attributeCriteria.getAttribute().getName();
         int indexOfDot = qualifiedName.lastIndexOf(".");
         String name = indexOfDot < 0
            ? qualifiedName
            : qualifiedName.substring(indexOfDot + 1);
         ConjunctionCriterion partsCriterion =
            partsQuery.getValue().getConjunctionCriterion();
         for (Criterion partsCriteria : partsCriterion.getCriterionList()) {
            AttributeCriterion partsAttributeCriteria =
               (AttributeCriterion) partsCriteria;
            String partsQualifiedName =
               partsAttributeCriteria.getAttribute().getName();
            if (partsQualifiedName.endsWith(name)) {
               partsAttributeCriteria.setOperator(attributeCriteria.getOperator());
               List partsValues = partsAttributeCriteria.getValues();
               partsValues.clear();
               for (int i = 0, count = values.size(); i < count; i++) {
                  partsValues.set(i, values.get(i));
   private void invokeMethodExpression(String expr, QueryEvent queryEvent) {
      FacesContext facesContext = FacesContext.getCurrentInstance();
      ELContext elContext = facesContext.getELContext();
      ExpressionFactory expressionFactory =
         facesContext.getApplication().getExpressionFactory();
      MethodExpression methodExpression =
         expressionFactory.createMethodExpression(elContext, expr, Object.class, new Class[] { QueryEvent.class });
      methodExpression.invoke(elContext, new Object[] { queryEvent });
Then when the advanced/basic button is pressed for the visible query panel, I programmatically set the same mode for the hidden query panel:
   public void handleQueryModeChange(QueryOperationEvent queryOperationEvent) {
      if(queryOperationEvent.getOperation() == QueryOperationEvent.Operation.MODE_CHANGE) {
         QueryMode queryMode = (QueryMode) irQuery.getValue().getUIHints().get(QueryDescriptor.UIHINT_MODE);
         QueryDescriptor queryDescriptor = partsQuery.getValue();
         queryDescriptor.changeMode(queryMode);
         AdfFacesContext.getCurrentInstance().addPartialTarget(partsQuery);

How can we hide the non key field values in the sm30 display

hello experts,
I have to protect the non key field values in the sm30 display , can u help me out wat changes i have to do in the layout.

Hello Gopal,
What do you mean by 'protecting' your non-key field value?
1) You want to display it, but make it non-changeable
A - Make the field as output-only in screen, as already answered by a preivous collegue
2) You do not want to display this field at all
A - Goto the DDIC definition of the view (not possible for a table directly), and maintain the required field as a Hidden. After activating, remember to re-generate the maintenance dialogue. Also, please maintain Event 21, in case you want to access/change the value of this field in background.
3) You want to maintain special validations/checks for the field
This can be easily done by introducing your modules within the CHAIN-FIELD commands in the PAI of the generated screens.
Best Regards,
Rekha

View criteria condition needs to check value in column from another VO

Hi All,
My Jdev version - 11.1.1.6
My use case is as follows-
2 view objects say EmpVO and DeptVO which have view link with deptId as the foreign key attribute. I need to show the distinct list of departments along with a column which contains the employee names separated by comma for the particular department in the corresponding row. Hence, for DeptVO I use the query as follows -
-          SELECT deptId,
-                 deptName,
-                 (SELECT listagg (empName, ',') WITHIN GROUP (ORDER BY empName)
-                            emp_names
-                    FROM EMP_TABLE emp
-                   WHERE emp.deptId = dept.deptId)
-                    emp_names
-          FROM DEPT_TABLE
This gives me the result on screen as follows -
DeptId          DeptName          EmpNames
101               HR                    emp1,emp2
102               Finance             emp3,emp4,emp5
Now, my requirement is that there should be a search on department which should also contain an LOV (with search icon) for the employee names i.e. if user selects emp4 from the LOV, department table should list the record for 102.
For this , I added an LOV on the EmpNames attribute of DeptVO (to map the values from EmpVO) and added a view criteria based on which I added a query panel on screen and the relevant partialTrigger attribute so that the department table should reflect the search results. I tried 2 options in the View Criteria of DeptVO i.e.
1. Added an Item 'EmpNames = '. WIth this, EmpNames attribute appear with Searh icon in the query panel(which is required) but it does not display the right department record bcz it tries to match exactly with values like 'emp3,emp4,emp5'
2. If I add Item 'EmpNames CONTAINS ' , EmpNames search will work from query panel i.e. if I enter the value as emp4, department 102 will be shown in the results table but there is no Search icon on the EmpNames field in query panel. The component actually becomes an inputText.
It would be of great help if you can guide on a better way to achieve this use case. Please let me know if there needs to a change in the approach or if any other details are needed.
Regards,
Ansh

Hi Timo,
Thanks for this. I have already implemented this part. Here, in the example there's an LOV on department id and form is on employee entity. However, my use case is a different one. I need to search for department which should contain a search criteria for employee in the form of LOV.
Could you suggest some possible solution?
Regards,
Ansh

COPA Derivation based with target field as non-copa field

Hello experts,
There is a requirement to derive the Characteristic maintained in Classification view(AUSP table) in Material master based on material number.The target field into which the characteristic value needs to be populated is not in COPA(it is a non-copa field).
I tried to use table look up with AUSP table, but it is asking for values of certain key fields like
ATZHL(Characteristic value counter) MAFID(Indicator: Object/Class) and
KLART(Class Type), which are not there in COPA.
With the Enhancement in KEDR transaction, EXIT_SAPlKEDRCOPA_001 and Include ZXKKEU11, I created an enhancement step by giving the material as the key in the source fields.With that material number I can do a select on the AUSP table inside the include ZXKKEU11 and get the characteristic value. The problem i am facing is that the target field which stores the internal characteristic value is not there in COPA?And while creating a derivation rule, I can only select the COPA fields as target fields.
It's urgent....any suggestions please? Points will be rewarded for any useful answer.
Thanks,
Anky

Hi,
As far as I know the derivation functionality in COPA is meant for derivation of characteristic values to store them in a characteristic field.
If you splitt up the derivation in two steps it might be possible to use the USERTEMP fields, to store the information needed and to pass it on to an other lookup step as a key-reference.
Regards,
Roy

Search page with Non-Mandatory Fields

JDev 11.1.2.3.0 ADF BC
I have a Search page that has 12 fields where Nothing is mandatory while inputting at least one(any of the fields) is mandatory. I am looking to reduce the code in this case, I don't want to use a Stored procedure or backing bean method to handle the if and else's. I would be excited to handle this at the Model part itself(Writing a proper SQL query or by means of bind variables/view criteria).
Hope the use case is clear.

You can use ViewCriteria with Validation property set to "Selectively Required"
Dario

View Criteria non required field

Similar Messages

Maybe you are looking for