Creation of view in a component

Hi ,
may I have the step by step procedure for the creation of view in a component.
I have created the Enhancement set .
then in BSP_WD_CMPWB I enter the component and say enhance it took me to the area where all views are in display mode and after I selected the views and started the wizard of view creation .
I require info on the data to be given in the wizard and the procedures after that.
plz provide some inputs ,
Thanks and regards,
Sree.

Hi Sree,
In your view.htm are you using the code to get the configuration?
Example:
<%@page language="abap"%><%@ extension name="htmlb" prefix="htmlb"%><%@ extension name="xhtmlb" prefix="xhtmlb"%><%@ extension name="crm_bsp_ic" prefix="crmic"%><%@ extension name="bsp" prefix="bsp"%>
<%@extension name="chtmlb" prefix="chtmlb" %>
<%
data: lv_xml    type string.
lv_xml    = controller->CONFIGURATION_DESCR->GET_CONFIG_DATA( ).
%>
<chtmlb:config xml = "<%= lv_xml %>"
               mode = "RUNTIME" />
Best regards,
Caíque Escaler

Similar Messages

Adding a view in a component of BSP application

Hi All,
I want to create new component for a BSP and add a view to it.
my scenario is : I have a problem in creating a pop-up view whenever a button in a WEB UI is clicked.
I have added a button in the items tab of sales order creation(in WEB UI),so when that button is clicked a pop-up view has to be generated.
the view i am creating is a ineractive view where the user can enter some data and press a button in the pop-up window so that the data is copied in the items tab.
the pop-up contains a table grid where the user can enter the data and press the button in pop-up window.
so could you please let me know how to create this type of pop-up window.
Regarding this some one has send me a solution of creating a new component with a new view.but unfortunately i am not able to create a view because it is asking for nodes and BOL entity.
so could you all provide me some input inorder to create the component and view.
Thanks
Tanveer

Hi Tanveer,
I have done the Similar Case.
By now I hope you have Created a New Component.
Ensure the Following Points before you Proceed.
1. Create a Window/View Set and View.
2. As you are saying yours is Table View while Creating View Specify it as Value Node and assign Corresponding Attributes to the Value Node.
3. Specify Type of View is Table Type.
4. Now in Runtime Repository Add the Created Window.
5. Now add the Created ViewSet and View to the Window and Save.
6. Create a New Interface View which is ( Window Name ) in Runtime Repository.
7. Add Component Usage in Runtime Repository.( In Source Component where Button is Present )
    a. Give ID and Interface View for the Component Usage and give Used Component
        Name. If View is created in same component then give same name other wise
         Give another component name.
8. After create View/Window/Component Interface/Component Usage Now to get the
   Table View in Popup Screen
   Modify the Standard Code similar to the Table View in HTML Page.
   For Reference:
<chtmlb:tableExtension tableId = "Table"
                       layout = "FIXED" >
<chtmlb:configTable id              = "Table"
                      navigationMode = "BYPAGE"
                      onRowSelection = "select"
                      selectedRowIndex      = "<%= CONTEXTNODE->SELECTED_INDEX %>"
                      selectedRowIndexTable = "<%= CONTEXTNODE->->SELECTION_TAB %>"
                      selectionMode         = "<%= CONTEXTNODE->->SELECTION_MODE %>"
                      table           = "//CONTEXTNODE->/Table"
                      usage           = "SEARCHRESULT"
                      visibleRowCount = "10"
                      width           = "100%"
                      showNoMatchText = "FALSE"
/>
</chtmlb:tableExtension>
CONTEXTNODE is the Context Node in View.
Now to get the Values in the Table View when popup gets displayed.
Go to the Newly Created View and add Code to populate Values in Table View
Method CL_BSP_WD_CONTEXT_NODE_TV - > IF_BSP_MODEL~INIT.
Now,to Call the Created View as a popup from the New Component when Buton is Clicked
Use the Following Code in the Event of Button Click.
DATA: lr_popup TYPE REF TO if_bsp_wd_popup.
IF lr_popup IS NOT BOUND.
    lr_popup = me->comp_controller->window_manager->create_popup( )
    (Specify Parameters Interface View,Component Usage and Title for Window in the above Method._
    lr_popup->set_display_mode( if_bsp_wd_popup=>c_display_mode_surrounded ).
ENDIF.
Set the callback event on the imported controller ( Specify Event Name which needs to get Triggered when Popup is Closed.)
lr_popup->set_on_close_event( iv_event_name = "EVENT_NAME"
                                       iv_view = me ).
*Set the width of the popup
CALL METHOD lr_popup->set_window_width
    EXPORTING
      iv_width = 500.
*Open the popup
lr_popup->open( ).
This will help in Getting a View as a Popup when Button is Clicked.

Enquiry in creation of view

Hi all,
I want to create a new view using wizard in the BP_HEAD component( CRM 2007) . How will I implement this?
Can anyone plz help me in sorting out this problem.
Regards,
Nithu

Hi,
Just follow the below steps:-
a) First of all, you need to do the groundwork. Design the view on paper, whether its a form/table view, how the data will flow into the view(from custom/component controller), what data will be displayed(which means what context nodes will be added).Table view can display data from only one context node while form view can display from multiple context nodes.
b) Once the groundwork is done, enhance the component ICCMP_BT_INR.
c) Add the view via the view creation wizard.Create the corresponding context nodes in the wizard itself or later after creating the view. Also you can bind the context nodes to the custom/component controller in the wizard itself or later.
Inbound plugs are called when we enter the view while outbound plugs are called while leaving the view.Its not mandatory for a view to have inbound/outbound plugs.Only when there is some kind of a navigation, then we create these plugs. e.g while navigating away from a view, we call the navigation link in the outbound plug. To initialize certain global parameters while entering a view, we do it in inbound plugs.
Hope it gives you some pointers to start with!
Regards,
Rohit

Select-options are not destroyed while calling view of used component popup

Hi Friends ,
I'm facing a unique problem. I'm calling a view of a component within another component. the view that I'm calling has some select-options. When I close the popup window ( using close 'X' of popup ) and then try to reopen the popup system give me a dump. I debugged and found that select-options are not destroyed by system and once it tries to create the select-options again it dumps because they are already there.
This is the source code extract of that dump for your reference .
1 method if_wd_select_options~add_selection_field.
2
3   data:
4     lr_table_descr       type ref to cl_abap_tabledescr,
5     lr_struct_descr      type ref to cl_abap_structdescr,
6     lr_value_field_descr type ref to cl_abap_elemdescr,
7     added_field          like line of mt_added_fields,
8     dfies                type dfies,
9     description          type string,
10     complex_restrictions type if_wd_select_options=>t_complex_restrictions.
11
12   field-symbols:
13     <it_result> type index table.
14
15 * check of someone wants to add a field that already exists
16   read table mt_fields
17        with key m_id = i_id
18        transporting no fields.
19   if sy-subrc = 0.
20 *   might be deleted - recreating a field with different setting is of course allowed
21     read table mt_all_removed_fields
22          with key table_line = i_id
23          transporting no fields.
24     if sy-subrc <> 0.
>>>       message x000(00).
26     endif.
27
28 *   remove the existing field in order to avoid duplicates
29     delete table mt_fields with table key m_id = i_id.
30   endif.
I've already tried using REMOVE_ALL_SEL_SCREEN_ITEMS( ) method of interface IF_WD_SELECT_OPTIONS before creating new elements ( select-options ). If any one can help me in this It would really help and I'll appreciate it.
Thanks in advance,
Laeeq

I've sloved the problem

How to call specific view of used component

Hi All,
I have the following problem:
I have component 1 which have two views: 1A and 1B. They are included in one window. Default view is 1A.
Navigation between view 1A and 1B it made with buttons and plugs ("go to 1A", "go to 1B").
I have main component 2 which uses component 1 (used component). Component 2 has view 2A and 2B. I have button "Z" in view 2A which calls method of component 1 and navigates to view 2B (where used component 1 is embedded).
First time I press button I navigate to view 1A, its correct. Then I navigate to view 1B (within used component 1).
when I go back (in main component 2) and press button "Z" again, the used component 1 is open with view 1B, not 1A (which is default). That is, used component 1 remember which view the navigation stayed on.
I nee to always see view 1A first when I navigate with button "Z" (open used component).
How I can do that?

hi ,
u must be using component usage ..
in ur component2 , place the view 1B of ur used component in separate window
pls refer this thread as well :
How to call a Particular View from a View of Current Component
regards,
amit

View of one component need to be used in another component.

Hi Experts,
I have created a view in component BP_DATA . I want to use this view in component "BP_HEAD". Can anyone please help me with the steps needed to make the view available in BP_DATA. Do i need to do any type of binding for this.

Hello Ansal,
For using BP_DATA/yourview in component BP_HEAD, first you will have to expose BP_DATA view in component interface. Then you can access that view in BP_HEAD by creating component usage. Once you add the view of BP_DATA in component usage of BP_HEAD, it will be available as a normal view in this component.
-Regards

Day View in calendar Component showing the next at times not everytime!

Day View in calendar Component showing the next at times not everytime! My question is when we go to Day view which day does it show? is it Server day where the application reside or the machine time zone day ?

I think you want to know, days & time picked by which machine, locally or from server? It does take from server where the application is running.

Create a new view under a component in IC Webclient UI

Hi ,
Can anyone tell how to create a new view under a component in IC Webclient UI.
Regards,
Sijo

Depends what kind of view you are talking about. In any case first go to runtime repository on the left panel of the component and then click the edit button.
If you are talking about interface view, right click the component interface and choose "Add interface view". The created view is added to the selected window in the runtime repository.
If you want to add view to the window right click the windows component and select "Add view".
Select the view using the f4 help and save the runtime repository.

Reading the data from one component view into another component view

Hi All,
I have requirement to read the data from one component into another component while creating the service order. Here are the details.
Main View for Service order: BT116H_SRVO in that we have two assignment blocks like Organizational data(BTORGSET) and amount allocation(BTAMNTALL).This two blocks are two different component which are associated with main component(BT116H_SRVO).
I need to read the sales org data from component/View(BTORGSET/Orgsetdata) into Component/View(BTAMNTALL(HdrBillPlanDet) method DO_VALIDATE_INPUT.
I searched in SDN but all the posts are related to the data exchange between two views in same component. But My scenario is different as explained above.
Refer the attachments for the component link..
Please let me know how we can achieve this one..
Thanks,
Sapsar.

Finally I was able to fix my code...My Mistakes were need to read the parent node above three levels and need to use the relation entity name while reading the data..
Below is the correction code
IF iv_index IS NOT INITIAL.
     lr_iterator ?= collection_wrapper->get_iterator( ).
     lr_current ?= lr_iterator->get_by_index( iv_index ).
     lr_entity ?= lr_iterator->get_by_index( iv_index ).
   ELSE.
     lr_current = collection_wrapper->get_current( ).
   ENDIF.
*loop back to root entity
         WHILE lr_entity->get_name( ) NE 'BTAdminH'.
           lr_entity = lr_entity->get_parent( ).
         ENDWHILE.
*Get the related entity
         IF lr_entity IS BOUND.
           lr_collection ?= lr_entity->get_related_entities( iv_relation_name = 'BTHeaderOrgmanSet' ) .
           IF lr_collection IS BOUND.
             lr_orgset_m = lr_collection->get_current( ).
*            lr_orgset = lr_orgset_m->get_related_entity( iv_relation_name = 'BTOrgSet' ).
             lr_orgset = lr_orgset_m->get_property_as_string( 'SALES_ORG' ).
           ENDIF.
         ENDIF.
Thanks,
Sapsar.

Creation of view on single table?

Hi Team,
I have a requirement like for creaation of view on single table (QMEL) in SAP ECC side...
Note: in this table i need 2o fields only....not all fields.
First can we create view on single table?
if 'Yes' can any one tell , How we can creat view on single table?
While creation of view we have four options..
1)Data base view
2)Projection View
3)Maintanace view
4)Help view
in these four options which tyep of view we can choose for creation?
please can any one suggest me and do the need full..
i am waiting your responce...

I quickly skimmed the links provided by others; and in my short discussions with DBA friend of mine; and other sources... partition should be based on user needs, sql server resources, and partition maintenance time.
Lets say you have 50 regions and 1) partition the data by region, AND 2) place each partition on a different disk, and 3) i am in Texas and only query data in the Texas region then performance will be increased because I am not scanning through the other
49 regions.
If you have temporal data (dependent on time - like say financial reports that are sent to the SEC) - the partitions are by time: 1) data from last 13 months is stored on SSD, 2) data 13 months - 3 years old is on HDD, and 3) data >3 years old is stored
on compressed HDD. (i say 13 months so you have an entire year and month to date) --- accountants can get the current data VERY quickly, project managers who need to see a 3 year trend will not have to wait long, and when the SEC calls, who cares?,
the reports can be queued and generated at night when no one is working.
I see partitions are giving the users the least amount of data to query which speeds their results.

Three levels hierarachy - hierarchy viewer data visualization component

I am not getting the third level when i am using the hierarchy viewer....any pointers will be a great help
Edited by: Deepak Subramanian on Jan 22, 2010 5:34 AM

oops sorry if i sounded vague....
using jdev version 11g
well I am trying to use the hierarchy viewer data visualization component to create a hierarchy which shows the managers and employees below them.
am using a single query based VO which has two columns manager and employee.
then created a self view link with that vo
the data control looks something like
manager(first level)
----manager or employee(first level)
---------employee(third level)
I am dragging entire data control on the page so that the create hierarchy viewer option appears.
from there I am stuck...
when I am running the page, I am getting just two levels...the last level is not showing up :(.....
Edited by: Deepak Subramanian on Jan 22, 2010 5:35 AM

Add View of one component in another component

HI All,
I need to show view "TextView" of component SRQM_NOTES in component BT116IT_SRVO.
That is: i would like to show text for each Item of a particular order.
How can I do that?
Add View to a certain ViewSet / Change a configuration / add view to the Window... or what not???
Please help here.. I need it.. THANKS, Johannes

Hi there,
Your requirement is simple though lenghty to implement. Following is the solution :
You have not mentioned in which view you would like to get the text.Let it be.
1. Add SRQM_NOTES as a component usage in BT116IT_SRVO. For this, first enhance BT116_SRVO. Then in its runtie repository, right click on component usage-> ADD . Lets name it UCSRQM_NOTES, then give compoent SRQM_NOTES and interface view ( use f4 ) SRQM_NOTES/MainWindow . Save the repository.
2. right click on ViewSet BT116IT_SRVO/ItemTableVS ( i assumed this. you do F2 on web ui to find out exact view and then proceed with this set in the viewset contating that view.
Say Add Vieware. Lets name it ItemNotes. after view area is created, right click & say add view.Use F4 and select UCSRQM_NOTES.SRQM_NOTES/MainWindow . Save the repository.
Repository work is over.
3. Now go to BT116IT_SRVO/ItemTableVS . click on config tab. do the configuration and add the newly created viewarea in the configuration. save the configuration.
This completes adding the view from SRQM_NOTES to BT116IT_SRVO.
4. Now, you will also need to see the text for the item selected. for this we will need to do the context node binding.
For this, go to the component controller class of BT116IT_SRVO & redefine the method WD_USAGE_INITIALIZE.
First give the call to super and later code following
CASE iv_usage->usage_name.
    WHEN 'UCSRQM_NOTES'.
* bind single item component usages
      iv_usage->bind_context_node( iv_controller_type = cl_bsp_wd_controller=>co_type_component
                                   iv_target_node_name = 'BTADMINI'
                                   iv_node_2_bind      = 'BTADMINI' ).
ENDCASE.
Now you are ready to test on UI !!
Hiope this helps.
Thanks & Regards,
Suchita

How to create navigational links...and connect views of another component

Hi...
I am new to SAP CRM...
I have a requirement where i need to navigate from the main window of a component to the view of a different component.
Scenario:
When i click on edit button after selecting a line item in the assignment block in the BT111H_OPPT/Details ,it should navigate to the details page of the line item which is the view of another component that has been created .say ZRP/PEL.
How can i achieve this using the concept of inbound/outbound plugs and navigational links?
I have got a vague idea on plugs from my search...that these are entry/exit points to views.
But what is the procedure to follow to attain the functionality?
How do we decide on which component needs which all plugs?
Anyhelpful pointers would be rewarded.
Also, an idea on what exactly does the inbound/outbound plugs do and how is the flow happening , how are navigational links working etc would be appreciated.
Thanks..

Steps to create navigational link:
1.     Create an outbound plug in the component from where you want to navigate. Sometimes
                standard navigational links are already there.. you just need to identify it.
2.     Create a Component usage in runtime repository for target component.
3.     Add this component usage to the main window view in repository.
4.     Create navigation link between the transaction type and the target component view.
5.     In the outbound plug, use the view manager to navigate to the target component. Ex:
                ME->FIRE_OUTBOUND_PLUG( IV_OUTBOUND_PLUG   = 'TO_OUTPLUG''
                          IV_DATA_COLLECTION = LR_COL ).
6.     Pass the data through the data collection.

Creation of Views

Hai Experts,
I'm new to the ABAP development area. I am learning about tables, buffers etc. And now i want to know about Views and the creation of Views. So can anybody give me the steps involved in the creation of views?
Regards,
P.Shanthi

Creating a Maintenance View
http://help.sap.com/saphelp_40b/helpdata/en/cf/21ed2d446011d189700000e8322d00/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5a/0c88924d5911d2a5fb0000e82deaaa/content.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/abap/abap+dictionary&focusedcommentid=39861
Enter the name of the view in the initial screen of the ABAP Dictionary, select object class Views and choose Create. A dialog box appears, in which you must choose the type of the view. Select the type Maintenance view.
The maintenance screen for maintenance views appears. You will see three input areas for tables, join conditions and view fields. Carry out the following actions in this screen:
Enter a short explanatory text in the field Short text.
In Tables, enter the primary tables of the view.
If required, include more tables in the view. In a help view you can only include tables which are linked to one another with foreign keys.
Position the cursor on the primary table and choose Relationships. All existing foreign key relationships of the primary table are displayed. Check the foreign keys you require and choose Copy. The secondary tables involved in such a foreign key are included in the view. The join conditions derived from the foreign keys ( Foreign Key Relationship and Join Condition) are displayed.
You can also include tables which are linked to one of the previously included secondary tables with a foreign key. To do this, position the cursor on the secondary table and choose Relationships. Then proceed as described above.
You can only select foreign keys in which the secondary table for the primary table or for the secondary table which transitively preceded it is in an n:1 relationship. This is the case if the secondary table is the check table of the base table and the foreign key was not defined generically. If the base table is the check table, the foreign key fields must be key fields of a text table or the foreign key must have cardinality of n:1 or n:C.
The foreign keys violating these conditions are displayed at the end of the list under the header Relationships with unsuitable cardinality.
Select the fields which you want to include in the view.
You can enter the field names directly. If you do not know the field names, you can copy them from the tables. To do this, position the cursor on a table and choose TabFields. The fields of the table are now displayed in a dialog box. You can copy fields from here by marking the first column and choosing on Copy.
Formulate the selection conditions. To do this choose Goto ® Selection condition. The input area for the selection conditions appears in place of the input areas for the fields. Maintain the selection condition as described in Maintaining the Selection Condition for a View. You can then switch back to the fields display with Goto ® View fields.
Activate the view with View ® Activate. A log is written during activation. You can display it with Utilities ® Activation log. If errors or warnings occurred during the activation of the view, you branch directly to the activation log.
Create the documentation for the view with Goto ® Documentation. This documentation is output for example when you print the view with View ® Print.
Branch to transaction SE54 with Environment ® Tab.maint.generator. From the view definition you can generate maintenance modules and maintenance interfaces there which distribute the data entered with the view to the base tables. You can find more information about using this transaction in the documentation Generating the Table Maintenance Dialog.
Optional Settings
You can make the following optional settings:
Change data element of a view field:
Select the Mod column (modify) for the view field and choose Enter. The Data element field is now ready for input. Enter the new data element there. This data element must refer to the same domain as the original data element. With the F4 help key for the Data element field, you can display all the data elements which refer to the domain of the field. If you want to assign the original data element again, you only have to reset the Mod flag and choose Enter.
Change maintenance status:
The Maintenance Status defines how you can access the view data with the standard maintenance transaction (SM30). Choose Extras ® Maintenance status. A dialog box appears in which you can select the maintenance status of the view.
Define the delivery class of the view:
Choose Extras ® Delivery class. A dialog box appears in which you can enter the delivery class of the maintenance view.
Define the maintenance attribute of a view field
The maintenance attribute defines special access modes for the fields of the view. You can make the following entries in field F in the input area for the view fields:
R : Only purely read accesses are permitted for fields with this flag. Maintenance with transaction SM30 is not possible for such fields.
S : Fields with this flag are used to create subsets when maintaining view data. Only a subset of the data is displayed. This subset is defined by entering the corresponding value in this field.
H : Fields with this flag are hidden from the user during online maintenance. They do not appear on the maintenance screen. You have to ensure in a separate procedure that each such field has the correct contents. Otherwise, they are left empty.
: There are no restrictions on field maintenance.
Check functions:
With Extras ® Runtime object ® Check you can determine whether the definition of the view in the ABAP Dictionary maintenance is identical to the specifications in the runtime object of the view. With Extras ® Runtime object ® Display you can display the runtime object of the view.
Display foreign key of a view field:
If a foreign key which was automatically included in the view definition is defined for the field of the base table, you can display it. To do so, position the cursor on the view field and choose Extras ® Foreign keys.
Display foreign key on which a join condition is based:
If a join condition was derived from a foreign key, you can display its definition. To do so, position the cursor on the join condition and choose Extras ® Foreign keys.
See also:
Maintenance Views

Using only 1 view from a component ( usage )

hi experts..
I have a component C1 with 7 views...
I have another componet C2 in ehich i want to use only 1 view of the component C1 rather than the entire component...
How can i do that...
jagruti

Hi again.
can u make it more simpler sascha..
In the component controlelr of C1 create en event
(mark as interface).
Steps below r not clear.....
Then in the actíon handler method of C1 fire this
event.
The action handler method assigned to the back button in the view you want to use in C2. Here you can use the wizzard to fire the event in the component controller. There should be a fire_... method in the component controller now.
In the controller of view in C2 which contains the
ViewUiContainerElement create an event handler method
for the event of C1. In this handler you fire an
outbound of the view which navigates to another view
in C2.
this is described in the above mention thread. In C2 you created a viuew with the ViewUiContainerElement which embedds the view with the back button of C1.
Go to the attrib utes tab of this view and add the usage of C1 here.
Then go to the methods tab of this view and create a method handleBackEvent and choose event handler. In the event columen make a F4 and select the event of the component usage C1. Hit enter.
Create an outbound plug in this view which should be use to navigate to the view in C2 you want. Then go to the event handler method just created and fire the outbound plug.
Do not forget to connect the outbound to the inbound of the view you want to navigate to.
sorry for bugging u..
No prob.
jagruti..
Cheers,
Sascha
Message was edited by:
Sascha Dingeldey

Creation of view in a component

Similar Messages

Maybe you are looking for