Creating Search View

Hello,
My requirement is I need to create search view with fields Employee Responsible Id , Start Date and Category with default as E_Mail in my custom component.
Please specify me the procedure to get a Search View Page with above mentioned details.
I have created work centre with EMAIL.While clicking on EMAIL Search page should be displayed with above details should be displayed.
Thanks Alot For Upcoming Help.
Regards,
Tejaswy.

Please refer to the link.
http://techskills.wordpress.com/2009/05/09/sap-crm-web-ic-create-a-new-search-view-and-result-view/

Similar Messages

Exception while creating the Search view by using ZBOL

Hi,
I created a ZBOL by using
http://blogs.moovar.com/sap/sap-crm-create-a-custom-bol-for-web-ic/
It is working fine.
I created ZBOL_K.
Now based on this I want create a Search and Search Result.
http://blogs.moovar.com/sap/sap-crm-web-ic-create-a-new-search-view-and-result-view/
In this when I create a Search View I getting the Exception like this.
I went step by step. But in the third page I write like this.
<%@page language="abap" %>
<%@extension name="htmlb" prefix="htmlb" %>
<%@extension name="xhtmlb" prefix="xhtmlb" %>
<%@extension name="crm_bsp_ic" prefix="crmic" %>
<%@extension name="thtmlb" prefix="thtmlb" %>
<%@extension name="chtmlb" prefix="chtmlb" %>
<%@extension name="bsp" prefix="bsp" %>
<%
DATA: LV_XML TYPE STRING.
lv_xml = controller->CONFIGURATION_DESCR->GET_CONFIG_DATA( ).
%>
<chtmlb:config xml = "<%= lv_xml %>"
               mode = "RUNTIME" />
<thtmlb:advancedSearch id                = "advsO"
                       fieldMetadata     = "<%= controller->get_dquery_definitions( ) %>"
                       header            = "<%= TESTSEARCH->get_param_struct_name( ) %>"
                       fieldNames        = "<%= controller->get_possible_fields( ) %>"
                       maxHits           = "//TESTSEARCH/max_hits"
                       values            = "//TESTSEARCH/PARAMETERS"
                       onEnter           = "SEARCH"
                       ajaxDeltaHandling = "false" />
Save and Activate the view.
But when I go to the config tab. It is showing the Error.
An exception occurred in inbound plug IP_DEFAULT of target view BSP_DLC_CONF/AdvSearchConfig
An exception has occurred Exception Class CX_SY_CREATE_OBJECT_ERROR - The object could not be created: The class does not exist.
Method: CL_BSP_MODEL=>CREATE_STANDALONE_MODEL
Source Text Row: 10
And aslo in available Search Criteria I did not get fields.
So, then how I can solve this problem.
Please tell me any solution.
Regards,
B.Krishna.

Hi,
I created a ZBOL by using
http://blogs.moovar.com/sap/sap-crm-create-a-custom-bol-for-web-ic/
It is working fine.
I created ZBOL_K.
Now based on this I want create a Search and Search Result.
http://blogs.moovar.com/sap/sap-crm-web-ic-create-a-new-search-view-and-result-view/
In this when I create a Search View I getting the Exception like this.
I went step by step. But in the third page I write like this.
<%@page language="abap" %>
<%@extension name="htmlb" prefix="htmlb" %>
<%@extension name="xhtmlb" prefix="xhtmlb" %>
<%@extension name="crm_bsp_ic" prefix="crmic" %>
<%@extension name="thtmlb" prefix="thtmlb" %>
<%@extension name="chtmlb" prefix="chtmlb" %>
<%@extension name="bsp" prefix="bsp" %>
<%
DATA: LV_XML TYPE STRING.
lv_xml = controller->CONFIGURATION_DESCR->GET_CONFIG_DATA( ).
%>
<chtmlb:config xml = "<%= lv_xml %>"
               mode = "RUNTIME" />
<thtmlb:advancedSearch id                = "advsO"
                       fieldMetadata     = "<%= controller->get_dquery_definitions( ) %>"
                       header            = "<%= TESTSEARCH->get_param_struct_name( ) %>"
                       fieldNames        = "<%= controller->get_possible_fields( ) %>"
                       maxHits           = "//TESTSEARCH/max_hits"
                       values            = "//TESTSEARCH/PARAMETERS"
                       onEnter           = "SEARCH"
                       ajaxDeltaHandling = "false" />
Save and Activate the view.
But when I go to the config tab. It is showing the Error.
An exception occurred in inbound plug IP_DEFAULT of target view BSP_DLC_CONF/AdvSearchConfig
An exception has occurred Exception Class CX_SY_CREATE_OBJECT_ERROR - The object could not be created: The class does not exist.
Method: CL_BSP_MODEL=>CREATE_STANDALONE_MODEL
Source Text Row: 10
And aslo in available Search Criteria I did not get fields.
So, then how I can solve this problem.
Please tell me any solution.
Regards,
B.Krishna.

How to get the search option when we are creating new view

Hi,
How to get the search functionality when we are creating new view.
Ex:- if we see the standard component BT112S_SC. Under this
AdvancedSP is the view,
same kind of view if i want to create new view with same bol entity in my new component. I am unable to get that search functionality.
for search functionality,,i think view should inherit the super class CL_BTSRV_ADVS_CNTRL, but in my new view controller class, i am unable to find this class.
Can anybody give me some inputs on this.
Thanks,
neelam

In case you are still not able to proceed please refer the following blog.
http://blogs.moovar.com/sap/sap-crm-web-ic-create-a-new-search-view-and-result-view
Regards,
Harshit

How to create a view?

HI friends,
Can any one help me out in creation of view i am suceeded in creation but while display it is showing no records
i think i am going wrong in selection conditions....can anyone give me clear steps to create a view.?

Hi,
The followings are different types of views:
- Database View (SE11)
Database views are implement an inner join, that is, only records of the primary table (selected via the join operation) for which the corresponding records of the secondary tables also exist are fetched. Inconsistencies between primary and secondary table could, therefore, lead to a reduced selection set.
In database views, the join conditions can be formulated using equality relationships between any base fields. In the other types of view, they must be taken from existing foreign keys. That is, tables can only be collected in a maintenance or help view if they are linked to one another via foreign keys.
- Help View ( SE54)
Help views are used to output additional information when the online help system is called.
When the F4 button is pressed for a screen field, a check is first made on whether a matchcode is defined for this field. If this is not the case, the help view is displayed in which the check table of the field is the primary table. Thus, for each table no more than one help view can be created, that is, a table can only be primary table in at most one help view.
Go thru this link plzz
http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21ecf9446011d189700000e8322d00/frameset.htm
Difference between "Help View" and "Search Help"
- Projection View
Projection views are used to suppress or mask certain fields in a table (projection), thus minimizing the number of interfaces. This means that only the data that is actually required is exchanged when the database is accessed.
A projection view can draw upon only one table. Selection conditions cannot be specified for projection views.
- Maintenance View ( SE54 )
Maintenance views enable a business-oriented approach to looking at data, while at the same time, making it possible to maintain the data involved. Data from several tables can be summarized in a maintenance view and maintained collectively via this view. That is, the data is entered via the view and then distributed to the underlying tables by the system.
Please have a look at below link. It will help you.
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed06446011d189700000e8322d00/frameset.htm
for more detailed info look on:
http://www.sap-img.com/abap/what-is-the-different-types-and-usage-of-views.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/abap+dictionary&
1.Go to se11
2. select view radiobutton and give a name
3. Create
4. select type of view you want to create. Such as database view.
5. give short description
6. give a table name such as mara
7. press the pushbutton relationship. here you will find all the tables which are allowed to create view with mara.
8. select one or mane tables.
8 copy
9.save , check and activate.
cheers,
vasavi
kindly reward if helpful

How to create sub views in Oracle SQL

I am trying to write a select statement through TOAD that needs to build a view and then query from that view further in the same statement. I don't mean create a VIEW in the common sense of running a CREATE VIEW command, I mean creating one dynamically within an SQL statement. Here's what I mean - in DB2 sql I can write the following:
WITH COUNT_NUM
COUNT_ADS
AS
(SELECT
COUNT(AD_ID)
FROM AD
WHERE CONTRACT_ID = '000234123'
SELECT * FROM COUNT_NUM;
Obviously this is a real simple example but you get the idea. Using this syntax you can create numerous sub-views to build data into your final select. My question is how to do this for Oracle. I have searched tons of help pages and sites but the only reference is to creating permanent views. I do not want to create temporary views either as I do not have adequate system permissions - I only want to create dynamic ones within my SQL.
Thanks in advance for any help!

In Oracle, the equivalent concept is known as an in-line view. The Oracle version of your statement is:
SELECT *
FROM (SELECT COUNT(AD_ID) count_ads
      FROM AD
      WHERE CONTRACT_ID = '000234123')Essentially, you can use an in-line view anywhere you would use a "real" view or a table, so the follwoing is also possible:
SELECT a.contract_id, a.count_ads, b.count_pages
FROM (SELECT contract_id,ad_id,COUNT(*) count_ads
      FROM ad
      GROUP BY contract_id,ad_id) ads,
     (SELECT ad_id,count(*) count_pages
      FROM ad_pages
      GROUP BY ad_id) ad_pages
WHERE ads.ad_id = ad_pages.ad_idHTH
John

Create a View with Aggregation Function (COUNT)

I've been looking up and down for a way to create a view with a few basic fields and some other fields containing aggregation function.
For instance:
To display a view that contain all the Contract Agreement and the corresponding count of the PO releases.
Agreement Nbr, Total PO releases
I need this view so that I can create a search help with this view.
I found something about the "CREATE VIEW" statement, but I don't have any idea how to use it.
Any helps toward this matter is very much appreciated, thanks.

Hello Aldern
I guess you have read about the SQL statement "CREATE VIEW". When we create a view in the dictionary this SQL statement is finally called to create the view on the DB. Thus, since we do not have any aggregation options in views you cannot achieve what you want using views.
The solution for your problem is to create a <b>search help</b> having a <b>search help exit</b>. Within the exit you can do your aggregation functions and add these values to the displayed search help data.
Regards
Uwe

Radio Button In Advanced Search View

How to bring radio button in Advanced Search view in crm 7.0 web UI?
Edited by: senthil06mx46 on Feb 18, 2010 9:50 PM

Hi,
Your question is not clear. Is the advanced search view relevant? Do you want to make radio buttons available as an option for selecting field values? In that case, the purpose is already served by the "IS" operator. If you simply want to create radio buttons somewhere else in the page, there's a standard BSP application which demonstrats BSP tags. The name, I do not exactly remember. BSP_test or bsp_demo...
Regards,
Arun Prakash

Add record through pop to search view criteria table?

Hi,
I am trying to add data from pop to search view criteria table but i am strukked at inserting data through popup...
i got nullpointer exception like this
<RegionRenderer> <encodeAll> The region component with id: pt1:r1 has detected a page fragment with multiple root components. Fragments with more than one root component may not display correctly in a region and may have a negative impact on performance. It is recommended that you restructure the page fragment to have a single root component.
<RowGatherCallback> <processComponent> Illegal child component ("javax.faces.component.html.HtmlOutputText@17cc21b" id="j_id256") detected inside parent component ("panelGridLayout" with clientId="pt1:r1:1:pgc1:pt_pgl3"). The child component must instead be of type "gridRow" instead.
<Utils> <buildFacesMessage> ADF: Adding the following JSF error message: java.lang.NullPointerException
java.lang.NullPointerException
    at oracle.jbo.server.QueryCollection.getRowSetRefs(QueryCollection.java:2675)
    at oracle.jbo.server.ViewObjectImpl.notifyRowUpdated(ViewObjectImpl.java:12174)
    at oracle.jbo.server.ViewObjectImpl.afterRowUpdate(ViewObjectImpl.java:13921)
    at oracle.jbo.server.ViewObjectImpl.sourceChanged(ViewObjectImpl.java:14224)
    at oracle.jbo.server.EntityCache.sendEvent(EntityCache.java:1566)
    at oracle.jbo.server.EntityCache.deliverEntityEvent(EntityCache.java:1582)
    at oracle.jbo.server.EntityCache.notifyColumnAndBlgChange(EntityCache.java:1640)
    at oracle.jbo.server.EntityImpl.notifyAttributesChanged(EntityImpl.java:7426)
    at oracle.jbo.server.EntityImpl.notifyAttributesChanged(EntityImpl.java:7407)
    at oracle.jbo.server.ViewRowImpl.setAttributeValues(ViewRowImpl.java:1827)
    at oracle.adf.model.binding.DCDataControl.setAttributesInRow(DCDataControl.java:2447)
    at oracle.jbo.uicli.binding.JUCtrlValueBinding.setAttributeValuesInRow(JUCtrlValueBinding.java:997)
    at oracle.jbo.uicli.binding.JUCtrlListBinding.setTargetAttrsFromLovRow(JUCtrlListBinding.java:2813)
    at oracle.jbo.uicli.binding.JUCtrlListBinding.updateTargetFromSelectedValue(JUCtrlListBinding.java:2941)
    at oracle.jbo.uicli.binding.JUCtrlListBinding.setAttributeFromValueList(JUCtrlListBinding.java:2886)
    at oracle.jbo.uicli.binding.JUCtrlListBinding.setSelectedIndex(JUCtrlListBinding.java:1752)
    at oracle.jbo.uicli.binding.JUCtrlListBinding.setInputValueInRow(JUCtrlListBinding.java:3541)
    at oracle.jbo.uicli.binding.JUCtrlValueBinding.setInputValue(JUCtrlValueBinding.java:2926)
    at oracle.jbo.uicli.binding.JUCtrlValueBinding.setInputValue(JUCtrlValueBinding.java:2889)
    at oracle.adfinternal.view.faces.model.binding.FacesCtrlListBinding.setInputValue(FacesCtrlListBinding.java:458)
    at oracle.jbo.uicli.binding.JUCtrlValueBinding.put(JUCtrlValueBinding.java:2546)
    at oracle.jbo.uicli.binding.JUCtrlListBinding.put(JUCtrlListBinding.java:3437)
    at javax.el.MapELResolver.setValue(MapELResolver.java:229)
    at com.sun.faces.el.DemuxCompositeELResolver._setValue(DemuxCompositeELResolver.java:255)
    at com.sun.faces.el.DemuxCompositeELResolver.setValue(DemuxCompositeELResolver.java:281)
    at com.sun.el.parser.AstValue.setValue(Unknown Source)
    at com.sun.el.ValueExpressionImpl.setValue(Unknown Source)
    at org.apache.myfaces.trinidad.component.UIXEditableValue.updateModel(UIXEditableValue.java:361)
    at org.apache.myfaces.trinidad.component.UIXEditableValue.processUpdates(UIXEditableValue.java:311)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.updateChildrenImpl(UIXComponentBase.java:1269)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.updateChildren(UIXComponentBase.java:1259)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.processUpdates(UIXComponentBase.java:1012)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.updateChildrenImpl(UIXComponentBase.java:1269)
    at oracle.adf.view.rich.component.fragment.UIXRegion.updateChildrenImpl(UIXRegion.java:669)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.updateChildren(UIXComponentBase.java:1259)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.processUpdates(UIXComponentBase.java:1012)
    at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl$UpdateModelValuesCallback.invokeContextCallback(LifecycleImpl.java:1561)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnNamingContainerComponent(UIXComponentBase.java:1670)
    at oracle.adf.view.rich.component.fragment.UIXRegion.invokeOnComponent(UIXRegion.java:625)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1750)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1750)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1750)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1750)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnNamingContainerComponent(UIXComponentBase.java:1693)
    at oracle.adf.view.rich.component.fragment.UIXRegion.invokeOnComponent(UIXRegion.java:625)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1750)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
    at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.invokeOnComponent(ContextSwitchingComponent.java:222)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1750)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1750)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1750)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1750)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1750)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
    at oracle.adf.view.rich.component.fragment.UIXInclude.invokeOnComponent(UIXInclude.java:161)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1750)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1627)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1750)
    at org.apache.myfaces.trinidad.component.UIXDocument.invokeOnComponent(UIXDocument.java:106)
    at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:1321)
    at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:678)
    at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:382)
    at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:202)
    at javax.faces.webapp.FacesServlet.service(FacesServlet.java:508)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:173)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:125)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:468)
    at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:468)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:293)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:199)
    at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:180)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
    at java.security.AccessController.doPrivileged(Native Method)
    at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
    at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
    at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
    at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
    at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
can any body help me out this?..
ThankYou

HI,
I think you have created form using two view objects ...recheck one of the value is null before commit ..
Thanks
Nitesh

Basic Requirement to create Tree View

Hi gurus.
While creating Custom Tree View, I am getting following error when i click the Search button in search page..
**An error occurred during event processing in view ASSEG.htm of UI Component ZHIER_VIEW**
**An exception has occurred Exception Class CX_SY_REF_IS_INITIAL - Dereferencing of the NULL reference**
**Method: ZL_ZHIER_VI_ASSEG_IMPL=>EH_ONSEARCH**
**Source Text Row: 109**
please help me if any one done tree view..
helpful if provide correct procedure to create tree view..
Regards.
Ashok.

Hi Lakshmi and Raj
The answer was correct, i was able to resolve that exception...
But the thing is when i click on the search button it is not displaying the result.. i mean it is not triggering the event...
what will be the answer for this please help me .. urgent requirement..
let me explain the scenario here i am taking one advance search page and if u click on search button result should display in tree format...
I done all correctly but i am now unable to point the error... my requirement similar to the standard component SEGAS_SEG.
Thanks
Ashok..

Create a view in the database based off a jdbc connection

I have some data in a DB2 database that I would like to union with a table in an Oracle Database in the Oracle Database.
Can I create a jdbc connection in the Oracle database that points to the DB2 database and then create a view based off of the jdbc connection?
I've never done anything like this , but if this a no brainer please just post a link or something that points me in the right direction thanks...
I've searched...

Mark,
I was going to suggest the same thing as Jan did when she answered this question that you also posted to the Union DB2 and Oracle data in a view and display in a form using jdbc? forum.
Good Luck,
Avi.

Create Materialized view Error ORA-22818

Hi,
I am creating a materialized view based on a complex query with inline queries, below is a simplified version of the query:
CREATE MATERIALIZED VIEW CM_FA_PEND_mvu
TABLESPACE CISTS_TH
BUILD IMMEDIATE
REFRESH COMPLETE
ENABLE QUERY REWRITE
AS
SELECT/*+ index (a,XT094S3) index (b,XT232S1) index (c, XM143P0) index (d, XM185S1)*/
a .fa_id,
a.fa_type_cd,
a.fa_status_flg,
a.disp_grp_cd,
(SELECT dl.descr
FROM ci_disp_grp_l dl
WHERE dl.disp_grp_cd = a.disp_grp_cd AND dl.language_cd = 'ENG')
disp_grp_cd_descr
FROM ci_fa a,
ci_sp_mtr_hist b,
ci_mtr_config c,
ci_reg d,
ci_fapr_faty e
WHERE a.fa_type_cd = e.fa_type_cd
AND a.sp_id = b.sp_id(+)
AND b.mtr_config_id = c.mtr_config_id(+)
AND c.mtr_id = d.mtr_id(+)
AND a.fa_status_flg = 'P'
AND e.fa_type_prof_cd = 'METERED'
AND ( (b.removal_dttm IS NULL))
I am getting error "ORA-22818: subquery expressions not allowed here". the problem is in columns "disp_grp_cd_descr" (when I remove this column from the query, the MView is created successfully)
Is using inline queries as columns a limitation on creating materialized view?
Is there a workaround ?
Thanks
AK

No version and no exception ... the full text is necessary the number alone insufficient ... to help you much other than recommend you read this:
http://download.oracle.com/docs/cd/E11882_01/server.112/e10810/basicmv.htm#DWHSG8195
where it says:
"The SELECT clause in the materialized view creation statement defines the data that the materialized view is to contain. Only a few restrictions limit what can be specified. Any number of tables can be joined together. Besides tables, other elements such as views, inline views (subqueries in the FROM clause of a SELECT statement), subqueries, and materialized views can all be joined or referenced in the SELECT clause. You cannot, however, define a materialized view with a subquery in the SELECT list of the defining query. You can, however, include subqueries elsewhere in the defining query, such as in the WHERE clause."
Something you could have found in a second or two in the docs at http://tahiti.oracle.com by searching for "Materialized Views Restrictions"
But without your version and the actual error message this may not apply.

How to create Search Help For Ztable fields

Hi all,
Please let me know How to create Search Help in SE11(what are the parameter i should pass)
and How to maintain search help for Ztable fields at DIctionary level (in SE11) and programming level.

hello .
there are two types of search helps .
1. elementary search help .
2. collective serch help
Below are the steps to create elementary search helps :
1 In the initial screen of the ABAP Dictionary, select object class Search help, enter the name of the search help and choose Create.
2.then youget a option elementary or collective search as per you r need .
3.select Elementary search help and choose
4.write explanatory text in the field Short text.
5. in the selection method give the name of the table or a view .
6 . Select the fields that should be used for value selection or in a hit list .
7. then define the attributes of the search help .
8 Select the IMP flag if it is an import parameter. Select the EXP flag if it is an export parameter.
9 .define the dialog type of the search help.
The dialog type tells how the hit list will be displayed in the input help.
10 . save and activate .
plz reward if usefull
Thanks ,
Abhishek .

Insufficient Privileges when create materialized view as user system

If I login as system (connect sys/****@DevDB) and try to create a materialized view for another schema (e.g. XDCONTROLDB), I get the insufficient privileges error. If I login as sys as sysdba then I can create successfully.
I have searched some ariticles in Google and grant create any snapshot, create any table, create any view, global query rewrite, select any table system privileges to system but still get the same error.
Any other privileges I need to grant to system?
Cheers
below is a sample script to create the view which get the error:
CREATE MATERIALIZED VIEW XDControlDB."XDTest1" PCTFREE 10
PCTUSED 0 MAXTRANS 255
STORAGE ( INITIAL 64K NEXT 0K MINEXTENTS 1 MAXEXTENTS
2147483645 PCTINCREASE 0)
TABLESPACE "USERS"
BUILD IMMEDIATE
REFRESH COMPLETE START WITH sysdate NEXT sysdate + 1/24
ENABLE QUERY REWRITE AS
SELECT * From XDControlDB.RiskInstance;
Message was edited by:
user500168
Message was edited by:
user500168

Thanks for your reply. After I grant privileges to system, I login as system and try to create the view as below which I get the insufficient privileges error:
CREATE MATERIALIZED VIEW XDControlDB."XDTest1" PCTFREE 10
PCTUSED 0 MAXTRANS 255
STORAGE ( INITIAL 64K NEXT 0K MINEXTENTS 1 MAXEXTENTS
2147483645 PCTINCREASE 0)
TABLESPACE "USERS"
BUILD IMMEDIATE
REFRESH COMPLETE START WITH sysdate NEXT sysdate + 1/24
ENABLE QUERY REWRITE AS
SELECT 1 From XDControlDB.RiskInstance;
As you can see, I try to create the view under a schema called 'XDCONTROLDB'. If I login as sys as sysdba, then it create successfully.
After I create UserA, and grant the privileges I mentioned in the ealier post, I login as UserA, and run the statement above I get the same privileges error. But if I change the stament to below which will create the view under UserA's schema, then it create successfully:
CREATE MATERIALIZED VIEW UserA."XDTest1" PCTFREE 10
PCTUSED 0 MAXTRANS 255
STORAGE ( INITIAL 64K NEXT 0K MINEXTENTS 1 MAXEXTENTS
2147483645 PCTINCREASE 0)
TABLESPACE "USERS"
BUILD IMMEDIATE
REFRESH COMPLETE START WITH sysdate NEXT sysdate + 1/24
ENABLE QUERY REWRITE AS
SELECT 1 From XDControlDB.RiskInstance;
Looking for your suggestions,
Cheers

How to create table view

Dear Experts,
how to create table view for single table? and once I create table view I have to create Generic data source so plz provide me the step to create it.
Please search the forum before posting a thread
Edited by: Pravender on May 6, 2011 11:18 AM

Hi,
                     There is big advantage of creating a view for single table rather than RSO2.
            My scenario is like this : My table VBAK has 113 fields i want only 9 fields from them.
                     RSO2: By doing generic extraction with RSO2 it will fetch all 113 fields from the table VBAK.So,it'll definitely degrades the performance . For transferring 9 fields why we have to fetch all 113 fields.
                     VIEW: By using view we can specify some fields in view fields.So, only those 9 fields will be fetched from table. In this extract structure contains 9 field transferring 9 fields.Then we can create generic extraction using this view.
Regards
satya.

How to create help view

hai,
how to create help view

Views
Importance/Use of Views
Data for an application object is often distributed on several database tables. Database systems therefore provide you with a way of defining application-specific views on the data contained in several tables. These are called views.
Data from several tables can be combined in a meaningful way using a view (join). You can also hide information that is of no interest to you (projection) or only display those data records that satisfy certain conditions (selection).
A view is a logical view on one or more tables, that is, a view is not actually physically stored, instead being derived from one or more other tables.
The data of a view can be displayed exactly like the data of a table in the extended table maintenance.
Join, Projection and Selection
CROSS PRODUCT
Given two tables TABA and TABB. Table TABA has 2 entries and table TABB has 4 entries
Each record of TABA is first combined with each record of TABB. If a join condition is not defined, the cross product of tables TABA and TABB is displayed with the view.
Join condition
A join condition describes how the records of the two tables are connected.
Inner Join and Outer Join
The data that can be selected with a view depends primarily on whether the view implements an inner join or an outer join.
With an inner join, you only get the records of the cross-product for which there is an entry in all tables used in the view.
With an outer join, records are also selected for which there is no entry in some of the tables used in the view. (ABAP allows left outer join.)
The data that can be selected with a view depends primarily on whether the view implements an inner join or an outer join.
Projection
Sometimes some of the fields of the tables involved in a view are not of interest. The set of fields used in the view can be defined explicitly (projection). In our example, Field 4 is of no interest and can be hidden.
We specify the fields which we need to show in our view by including them under the view flds tab when creating a view in the dictionary.
+Selection Conditions+
Selection conditions that are used as a filter can be defined for a view.
Specifying these conditions under the Selection conditions tab when creating a view in the dictionary would have an effect which is similar to specifying a where clause when writing a select query to restrict data.
View Types
Four different view types are supported. These differ in the way in which the view is implemented and in the methods permitted for accessing the view data .
Database views are implemented with an equivalent view on the database.
Projection views are used to hide fields of a table (only projection).
Help views can be used as selection method in Search help.
Maintenance views permit you to maintain the data distributed on several tables for one application object at one time.
Database Views
Database views should be created if want to select logically connected data from different tables simultaneously.
Database views implement an inner join.
Application programs can access the data of a database view using the database interface. (Just as we write select queries on database tables, we can write them for views as well.)
Includes in Database Views
An entire table can be included in a database view. In this case all the fields of the included table will become fields of the view (whereby you can explicitly exclude certain fields).
To include one of the tables in the view, enter character * in field View field, the name of the table to be included in field Table and character * again in field Field name on the View fields tab page of the maintenance screen of the view.
You can also exclude individual fields of an included table. If you do not want to include a field of the included table in the view, enter - in field View field, the name of the included table in field Table and the name of the field to be excluded in field Field name.
Inserts with Database Views
If a database view contains only one single table, data can be inserted in this table with the view .
You have the following options for the contents of the table fields not contained in the view:
If the field is defined on the database with NOT NULL as initial value, the field is filled with the corresponding initial value.
If the field is defined on the database as NOT NULL without initial value, an insert is not possible. This results in a database error.
If the field is not defined on the database as NOT NULL, there will be a NULL value in this field.
Projection Views
Projection views are used to hide fields of a table. This can minimize interfaces; for example when you access the database, you only read and write the field contents actually needed
For the above diagram, fields F3 and F4 are irrelevant, and therefore hidden from the projection view of the table.
Maintenance Views
A maintenance view permits you to maintain the data of an application object together.
The maintenance status determines which accesses to the data of the underlying tables are possible with the maintenance view.
Maintenance Status
The maintenance status of a view controls whether data records can also be changed or inserted in the tables contained in the view.
The maintenance status can be defined as follows:
Read only: Data can only be read through the view.
Read, change, delete, insert: Data of the tables contained in the view can be
changed, deleted, and inserted through the view.
Read and change: Existing view entries can be changed. However, records
cannot be deleted or inserted.
Read and change (time-dependent views): Only entries whose non-time
dependent part of the key is the same as that of existing entries may be
inserted.
Help Views
Help view is created if a view with outer join is needed as selection method of a search help.
Help views are used exclusively for search helps.
A conventional database view selects data from the database using an inner join.
For a help view however, data is selected using a left outer join.
Eg-> Suppose table SCARR (Airline master table) has AA American airlines
AB Air Berlin
AC- Air Canada as three entries.
Table SPFLI (Flight schedule) has entries corresponding only to airlines AA (American airlines) and AB (Air Berlin).
Now if a database view were to be used as a selection method for a search help for airlines, we would only get AA and AB as possible entries because the database view implements an inner join.If however, we were to use a help view as the selection method here, we would get AA,AB and AC as possible entries because a help view would implement a left outer join.
Restrictions for Maintenance and Help Views
There are some restrictions for selecting the secondary tables of a maintenance view or help view. The secondary tables have to be in an N:1 dependency to the primary table or directly preceding secondary table. This ensures that there is at most one dependent record in each of the secondary tables for a data record in the primary table.
Append Views
Append views are used for enhancements of database views of the SAP standard.
With an append view, fields of the base tables of the view can be included in the view without modifications. This is analogous to enhancing a table with an append structure.
An append view is assigned to exactly one database view. More than one append view can be created for a database view.
The append technique described can only be used for database views. With an append view, only new fields from the base tables contained in the view can be inserted in the view. You cannot insert new tables in the view or modify the join conditions or selection conditions of the view.
Check out the below related threads
Views
views

Creating Search View

Similar Messages

Maybe you are looking for