View KM document in Web Dynpro application

Hello - Does anyone have any tips for accessing KM documents in a web dynpro application? I have tried some of the examples found here but several of the methods were deprecated. Any help would be appreciated. Thank you.

Hi
Refer this sample code. unfortunately that page is not opening directly.
public void getAllStores( )
    //@@begin getAllStores()
     String prefix = "/documents/Public Documents/Store Data/";
     wdContext.nodeStoreTable().invalidate();
     IPrivateDocManageView.IStoreTableElement contentElement;
     try {
          IWDClientUser wdClientUser = WDClientUser.getCurrentUser();
          com.sap.security.api.IUser sapUser = wdClientUser.getSAPUser();
          com.sapportals.portal.security.usermanagement.IUser ep5user =
                         WPUMFactory.getUserFactory().getEP5User(sapUser);
          IResourceContext resourceontext = new ResourceContext(ep5user);
          IResourceFactory resourcefactory =
                         com.sapportals.wcm.repository.ResourceFactory.getInstance();
          RID pathRID = RID.getRID(prefix);
          com.sapportals.wcm.repository.IResource resource =
                         resourcefactory.getResource(pathRID, resourceontext);
          ICollection collection = (ICollection) resource;
          IResourceList resoucelist = collection.getChildren();
          IResourceListIterator resourelistiterator =
                         resoucelist.listIterator();
          while (resourelistiterator.hasNext()) {
               String store = null;
               com.sapportals.wcm.repository.IResource tempresouce =
                              resourelistiterator.next();
               if (tempresouce.getName().equals(
                         wdContext.currentFilterDataElement().getFromStore())) {
                    contentElement = wdContext.createStoreTableElement();
                    contentElement.setObjectName(
                                   prefix + tempresouce.getName());
                    wdContext.nodeStoreTable().addElement(contentElement);
                    tempresouce = resourelistiterator.next();
                    while (!tempresouce.getName().equals(
                              wdContext.currentFilterDataElement().getToStore())) {
                         contentElement = wdContext.createStoreTableElement();
                         contentElement.setObjectName(
                                        prefix + tempresouce.getName());
                         wdContext.nodeStoreTable().addElement(contentElement);
                         tempresouce = resourelistiterator.next();
                    tempresouce = resourelistiterator.next();
                    break;
          } // while iterate
     } catch (Exception e) {
                    e.printStackTrace();
Mandeep Virk

Similar Messages

Creating 'Z' views for Standard ABAP Web dynpro Application

Hi Experts,
I am totaly new to ABAP web dynpro objects.
In our project there were some client requirements which required us to change the properties of the Views related to the Webdynpro. The Client now has said that he needs to apply some enhancement pathces on his system. Due to this, the changes made to the Views i.e all the changes done in standard code are lost.
The client now wants a long term solution where all the changes need to be done in 'Z' implimentataion so that changes are not lost every time the pathces are applied.
Is it possible to create an entire new 'Z' Views for the standard Webdynpro instead of standrad ones?
If Yes how does one link them to the Webdynpro application ?

Hi
Have a look at following article about enhancing webdynpro applications.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/700317da-bd79-2c10-368e-8f18bf5d8b81?quicklink=index&overridelayout=true
Regards
Manas Dua

How to execute a BI query/view from a web dynpro application?

Hi all,
I am trying to connect to a BI system from a Web Dynpro application. I have to execute a view/query and process the output in my application. Please guide me about how to establish the connection to the BI system from my web dynpro application and then execute the query/view.
I have tried executing/modelling the BI query/view using Visual Composer but I get an error saying 'QueryView Instantiation failed' when I try to drag the view/query on to the design board.
Please guide me and help me achieve this.
Thanks & Regards,
Kishan

Hi Kishan,
Define system for BI in portal and define JCo destination, then from WDJ application use can query BI.
Create the Technical System and connect with JCO Destinations
or
Connecting through the BI Connecters (ex: XMLA Connecter)
Refer below link:-
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60f35908-ecd4-2910-6c89-e75e1054d9d1?quicklink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/60f35908-ecd4-2910-6c89-e75e1054d9d1
In this document you will get details related to connector and other admin activity.
Hope this may help you.
Deepak!!!

Exiting a Web Dynpro Application by pressing a button on a Web Dynpro View

Hi all,
I want to exit a Web Dynpro application when the user presses an Exit button on the screen. Is there an API for closing the current browser window and exiting the application?Thanks.
Sukru

hi,
For closing Main Window, use Exit Plug in Windows:
Do the following steps :
-> Make an Outbound Plug to the Window.
->Make the type of Outbound plug to Exit Type.
->Add CLOSE_WINDOW of type wdy_boolean as a parameter to the outbound plug of Window.
->Do remember to add Component Name in the Properties Tab of View ( othervs Calling Outbound plug of window from view wont be possible ).
->Fire the outbound plug with close_window as X in the onAction of Exit Button .
Refer SAP online help on using Exit plug to close a window:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/ca3351508f04e7e10000000a42189c/content.htm
method ONACTIONGO_EXIT .
data: L_REF_MAIN_WINDOW type ref to IG_MAIN_WINDOW .
L_REF_MAIN_WINDOW =   WD_THIS->GET_MAIN_WINDOW_CTR( ).
L_REF_MAIN_WINDOW->FIRE_MY_EXIT_PLUG_PLG(     CLOSE_WINDOW =   'X' ).
endmethod.
here Main_window is the window which needs to be closed.
I hope it is clear.

Clear/refresh(F5) fields in web dynpro application view

How to clear or refresh(F5) fields in web dynpro application abap while redirecting to another view? I have tried using "context_node->invalidate()" but it's not working for all the fields, some are getting initialised and some not. Is there any other method to refresh all the fields in the view all at once. Please guide.

Hi,
For the Context node( to which the drop down is bound) create a supply function as shown below:
Now populate the drop down in supply function method instead of WDDOINIT method.
Go to methods tab and write the below code in supply function method:
DATA lo_nd_drop TYPE REF TO if_wd_context_node.
    DATA lt_drop TYPE wd_this->elements_drop.
    DATA ls_drop TYPE wd_this->element_drop.
*Fill Drop down
    ls_drop-val = 'ABC'.
    APPEND ls_drop to lt_drop.
    ls_drop-val = 'DEF'.
    APPEND ls_drop to lt_drop.
* bind all the elements
   node->bind_table(
     new_items            = lt_drop
     set_initial_elements = abap_true ).
Now once you call invalidate( ) the drop down will automatically be initialized( since the supply function will be called again) And you don't have to write the code again to populate the drop down.
hope it's clear now.
Regards,
Kiran

Using EJBs in Web Dynpro Applications

I have recently started to develop Web applications using the Web Dynpro framework. Coming from a pure J2EE world, I must admit that Web Dynpro has a few innovative features that I find interesting for user interface development. The use of component & view contexts, for example, is not unlike the ActionForms that one may find in a Struts application, but pushed a bit further. No complaints here.
What I do have some problems with is the whole CommandBean paradigm that is put forth by SAP (refer to the document <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webdynpro/using%20ejbs%20in%20web%20dynpro%20applications.pdf">Using EJBs in Web Dynpro Applications</a>).
I do understand the usefulness of defining a model that will be used to generate and eventually bind to Context data structures. That's fine. What I do object to is the use of a so-called CommandBean to play that role. Again, coming from a J2EE world, I am familiar with the BusinessDelegate pattern - which would typically be used by a client application to invoke business logic on the server side. I would propose that a better, cleaner way of integrating EJBs with the Web Dynpro framework would be to use a BusinessDelegate for invoking business logic, and importing a separate and distinct ModelBean (instead of a CommandBean) to be used for defining and binding to Context data.
I have built one Web Dynpro application thus far. Instead of using a CommandBean, I created a ModelBean that extends my business object DTO (Data Transfer Object) (which is quite appropriate for that role, given that it implements all the get & set methods that are required for the business data that I need to model). My Web Dynpro application also makes use of an independant BusinessDelegate that is packaged with my EJB DC - this is a standard best practice on J2EE projects. I have been asked by the people working with me to modify this architecture to bring it more in line with the SAP way of doing things. I am open-minded and willing to learn and accept new ways of thinking and doing things. However, I fail to understand the usefulness of merging structure and behaviour by resorting to CommandBeans:
- It violates the MVC paradigm by having one object (the CommandBean) serve as both model AND controller as far as the Web Dynpro application is concerned. The CommandBean is obviously a model - since it is literally imported as such into the Web Dynpro application. It is ALSO a controller from the Web Dynpro's application perspective, since all calls to the back-end go thru the CommandBean via one or more of its execute_xxx methods. In contrast, the use of a business delegate by the Web Dynpro application clearly separates the model (the CommandBean... or rather, a more suitably named ModelBean) from the controller (BusinessDelegate).
- Doesn't carry its own weight. In other words, I haven't yet been provided with any valid justification for going thru the extra effort of coding the CommandBean's execute methods. It's been proposed to me that it somehow serves as an abstraction layer between the Web Dynpro application and the business logic. I would argue that it is the BusinessDelegate's role to abstract away the back-end logic from clients. If one does have a BusinessDelegate available, I would argue there's no need to code execute methods in a separate CommandBean. To prove my point, I would simply point out that all of the CommandBean examples that I have seen so far, either in How-To documents, or in production code, all follow the same pattern....
CommandBean.execute_doSomething() calls BusinessDelegate.doSomething()
Not a heck of an "abstraction" layer... I would in fact argue that it is worse than useless. If some major change occurs in the business logic that requires changing the doSomething() operation, we expect of course to modify the BusinessDelegate. The Web Dynpro client will also presumably need to be modified - that's to be expected, and unavoidable. But then, we'll also need to go about and change the CommandBean's execute_doSomething() method - again, extra work for no apparent benefit. Adding and removing business methods has the same implication. All this for an layer that simply adds the prefix execute_ in front of all business method calls... Is this "abstraction layer" worth the cost of creating and maintaining it ??
- Unnecessarily complicates error handling. I have been told that for technical reasons, it is recommended that all exceptions thrown by the CommandBean be of type WDException or WDRuntimException. But what if the client application needs to react differently to different failure scenarios ? When I create a business object, I might wish to provide the user with an error messages if connection is lost to the backend, and with a different error message if an object already exists in the database with the same attributes. In order to do that, I will have to catch the WDException, extract the cause, and continue processing from there... possible, yes, but clearly less standard and more labor intensive than the classical try/catch mechanism.
To say nothing about the fact that SAP's own API documentation clearly states that applications using Web Dynpro can reference and catch WDExceptions, but THEY MUST NOT THROW OR EXTEND IT !
- Produces unnecessary DCs. Page 6 of the aforementioned document presents an architectural view of a Web Dynpro project that uses a CommandBean. Why an extra DC for the CommandBean ?? I created my ModelBean class right inside the Web Dynpro project (in the Package view). That, to me, is where this class should reside, because it is created for no other reason that to be used by this particular Web Dynpro application. What is the benefit of placing it in its own independant DC ?
- Not a typical application of the Command pattern. The well-documented command pattern (Design Patterns - Gang of Four) has been devised mainly to enable encapsulation of request as objects, thereby making it possible to:
- specify, queue and execute requests at different times
- decouple execution of a command from its invoker
- support undo operations
- support logging changes so that they can be reapplied in case of system crash making it possible to assemble commands into composite commands (macros), thereby structuring a system around high-level operations built on primitive operations.
None of this applies to the way the SAP CommandBeans are being used. Not that much of an issue to people new to J2EE and/or OO development... but quite confusing for those already familiar with the classic Command pattern.
At this point, I fail to understand the advantage of merging structure (model) and behaviour (execute methods) through the use of a unique CommandBean object. Am I missing something ?

Hi Romeo,
You would be disappointed, this reply ain't anywhere nearby to what you are talking about...
I wanted to mail you, but you have not mentioned your email in your profile.
I am really impressed by your flair for writing. It would be far better had you written a blog on this topic. Believe me, it would really be better. There is a much wider audience waiting out there to read your views rather than on the forums. This is what I believe. To top it, you would be rewarded for writing something like this from SDN. On the blogs too, people can comment and all, difference being there you would be rewarded by SDN, here people who reply to you would be rewarded by you. Doesn't make much a difference.
Anyways the ball is still in your court
As far as I am concerned, it has still not been much time since I have started working on Web Dynpro. So can't really comment on the issue...
Bye
Ankur

Web Dynpro application connecting to oracle

Hi all,
i want to create a web Dynpro application which will fetch data from oracle database.
Can anyboby guide me with some documents.
Thanks in advance.

Thanks for your quick reply!
I am trying in another way.I've created a WD application and in custom controller I've put the code for connection, copying the retrived data into context and trying to display the data in one view.
CODE:
DriverManager.registerDriver(
              new oracle.jdbc.driver.OracleDriver());
Connection conn = DriverManager.getConnection(               "jdbc:oracle:thin:@oracle server ip:port:sid",
     "user name",
     "password");
Statement stmt = conn.createStatement();
ResultSet rs = stmt.executeQuery("select * from table");
if (rs != null)
while ( rs.next() )
     //code for copying data into context
stmt.close();
conn.close();
Error(No class defination found) is at first line i.e. new oracle.jdbc.driver.OracleDriver().
I've put classes.zip in lib and build path as well.
Regards,
Sarika.

Reg Simple Web Dynpro Application

Hello Gurus,
I am developing a simple Web Dynpro Application that displays just Purchase Header Details.
It says the runtime Error, "The exception CX_WD_CONTEXT" was raised but was not caught at any stage in Call Hierarchy.
Any Suggestions would be rewarded.....
Regards
Jay

Hi,
I have pasted the short dump....
===========================================================
Runtime Errors UNCAUGHT_EXCEPTION
Except. CX_WD_CONTEXT
Date and Time 27.02.2007 11:48:17
 ShrtText
 An exception that could not be caught occurred.
 What happened?
 The exception 'CX_WD_CONTEXT' was raised but was not caught at any stage in the
 call hierarchy.
 Since exceptions represent error situations, and since the system could
 not react adequately to this error, the current program,
 'CL_WDR_CONTEXT_NODE_VAL=======CP', had to
 be terminated.
 What can you do?
 Print out the error message (using the "Print" function)
 and make a note of the actions and input that caused the
 error.
 To resolve the problem, contact your SAP system administrator.
 You can use transaction ST22 (ABAP Dump Analysis) to view and administer
 termination messages, especially those beyond their normal deletion
 date.
 is especially useful if you want to keep a particular message.
 Error analysis
 An exception occurred. This exception is dealt with in more detail below
 . The exception, which is assinged to the class 'CX_WD_CONTEXT', was not
 caught,
 which led to a runtime error.
 The reason for this exception is:
 Die Anzahl der Elemente der Kollektion des Knotens INDEX.1.EKKO_ITAB verletzt
 die Kardinalität.
 How to correct the error
 You may able to find an interim solution to the problem
 in the SAP note system. If you have access to the note system yourself,
 use the following search criteria:
 "UNCAUGHT_EXCEPTION" CX_WD_CONTEXTC
 "CL_WDR_CONTEXT_NODE_VAL=======CP" or "CL_WDR_CONTEXT_NODE_VAL=======CM001"
 "CHECK_COLLECTION"
 If you cannot solve the problem yourself and you wish to send
 an error message to SAP, include the following documents:
 1. A printout of the problem description (short dump)
 To obtain this, select in the current display "System->List->
 Save->Local File (unconverted)".
 2. A suitable printout of the system log
 To obtain this, call the system log through transaction SM21.
 Limit the time interval to 10 minutes before and 5 minutes
 after the short dump. In the display, then select the function
 "System->List->Save->Local File (unconverted)".
 3. If the programs are your own programs or modified SAP programs,
 supply the source code.
 To do this, select the Editor function "Further Utilities->
 Upload/Download->Download".
 4. Details regarding the conditions under which the error occurred
 or which actions and input led to the error.
 System environment
 SAP Release.............. "640"
 Application server....... "diamond"
 Network address.......... "64.72.230.131"
 Operating system......... "Windows NT"
 Release.................. "5.2"
 Hardware type............ "4x Intel 801586"
 Character length......... 8 Bits
 Pointer length........... 32 Bits
 Work process number...... 0
 Short dump setting....... "full"
 Database server.......... "DIAMOND"
 Database type............ "MSSQL"
 Database name............ "ECC"
 Database owner........... "ecc"
 Character set............ "English_United State"
 SAP kernel............... "640"
 Created on............... "Nov 21 2005 00:50:16"
 Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
 Database version......... "SQL_Server_8.00 "
 Patch level.............. "101"
 Patch text............... " "
 Supported environment....
 Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
 SAP database version..... "640"
 Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
 Memory usage.............
 Roll..................... 8112
 EM....................... 12543552
 Heap..................... 0
 Page..................... 0
 MM Used.................. 11868848
 MM Free.................. 672136
 SAP Release.............. "640"
 User and Transaction
 Information on where terminated
 The termination occurred in the ABAP program "CL_WDR_CONTEXT_NODE_VAL=======CP"
 in "CHECK_COLLECTION".
 The main program was "SAPMHTTP ".
 The termination occurred in line 12 of the source code of the (Include)
 program "CL_WDR_CONTEXT_NODE_VAL=======CM001"
 of the source code of program "CL_WDR_CONTEXT_NODE_VAL=======CM001" (when
 calling the editor 120).
 Source Code Extract
 Line SourceCde
 1 method CHECK_COLLECTION .
 2
 3 data:
 4 path_name type string,
 5 lines type i.
 6
 7 lines = lines( me->collection ).
 8
 9 if ( lines = 0 and abap_true = me->node_info->is_mandatory ) or
 10 ( lines > 1 and abap_false = me->node_info->is_multiple ).
 11 path_name = me->if_wd_context_node~get_path( ).
 >>>>> raise exception type CX_WD_CONTEXT exporting textid = CX_WD_CONTEXT=>COLLECTION_ILLEGAL_
 13 endif.
 14
 15 lines = lines( me->selection ).
 16
 17 if ( lines = 0 and abap_true = me->node_info->is_mandatory_selection ) or
 18 ( lines > 1 and abap_false = me->node_info->is_multiple_selection ).
 19 path_name = me->if_wd_context_node~get_path( ).
 20 raise exception type CX_WD_CONTEXT exporting textid = CX_WD_CONTEXT=>SELECTION_ILLEGAL_C
 21 endif.
 22
 23
 24 endmethod.
 Contents of system fields
 Name Val.
 SY-SUBRC 0
 SY-INDEX 1
 SY-TABIX 1
 SY-DBCNT 12919
 SY-FDPOS 34
 SY-LSIND 0
 SY-PAGNO 0
 SY-LINNO 1
 SY-COLNO 1
 SY-PFKEY
 SY-UCOMM
 SY-TITLE HTTP Control
 SY-MSGTY
 SY-MSGID
 SY-MSGNO 000
 SY-MSGV1
 SY-MSGV2
 SY-MSGV3
 SY-MSGV4
 Active Calls/Events
 No. Ty. Program Include Line
 Name
 22 METHOD CL_WDR_CONTEXT_NODE_VAL=======CP CL_WDR_CONTEXT_NODE_VAL=======CM001 12
 CL_WDR_CONTEXT_NODE_VAL=>CHECK_COLLECTION
 21 METHOD CL_WDR_CONTEXT_NODE_VAL=======CP CL_WDR_CONTEXT_NODE_VAL=======CM01B 34
 CL_WDR_CONTEXT_NODE_VAL=>IF_WD_CONTEXT_NODE~BIND_TABLE
 20 METHOD /1BCWDY/MXAJIDSD2PZXCNSR7DDN==CP /1BCWDY/B_UXWMB4OI2PW6SWO6N6KC 1058
 CL_INDEX_CTR=>WDDOINIT
 Web Dynpro Component ZJAY_WEBDYN1
 Web Dynpro Controller INDEX
 19 METHOD /1BCWDY/MXAJIDSD2PZXCNSR7DDN==CP /1BCWDY/B_UXWMB4OI2PW6SWO6N6KC 167
 CLF_INDEX_CTR=>IF_WDR_VIEW_DELEGATE~WD_DO_INIT
 Web Dynpro Component ZJAY_WEBDYN1
 Web Dynpro Controller INDEX
 18 METHOD CL_WDR_DELEGATING_VIEW========CP CL_WDR_DELEGATING_VIEW========CM003 3
 CL_WDR_DELEGATING_VIEW=>DO_INIT
 17 METHOD CL_WDR_CONTROLLER=============CP CL_WDR_CONTROLLER=============CM00Q 3
 CL_WDR_CONTROLLER=>INIT_CONTROLLER
 16 METHOD CL_WDR_VIEW===================CP CL_WDR_VIEW===================CM00K 5
 CL_WDR_VIEW=>INIT_CONTROLLER
 15 METHOD CL_WDR_CONTROLLER=============CP CL_WDR_CONTROLLER=============CM002 12
 CL_WDR_CONTROLLER=>INIT
 14 METHOD CL_WDR_VIEW_MANAGER===========CP CL_WDR_VIEW_MANAGER===========CM008 58
 CL_WDR_VIEW_MANAGER=>GET_VIEW
 13 METHOD CL_WDR_VIEW_MANAGER===========CP CL_WDR_VIEW_MANAGER===========CM005 23
 CL_WDR_VIEW_MANAGER=>BIND_ROOT
 12 METHOD CL_WDR_VIEW_MANAGER===========CP CL_WDR_VIEW_MANAGER===========CM00B 21
 CL_WDR_VIEW_MANAGER=>INIT
 11 METHOD CL_WDR_INTERFACE_VIEW=========CP CL_WDR_INTERFACE_VIEW=========CM004 5
 CL_WDR_INTERFACE_VIEW=>INIT_CONTROLLER
 10 METHOD CL_WDR_CONTROLLER=============CP CL_WDR_CONTROLLER=============CM002 12
 CL_WDR_CONTROLLER=>INIT
 9 METHOD CL_WDR_CLIENT_COMPONENT=======CP CL_WDR_CLIENT_COMPONENT=======CM003 46
 CL_WDR_CLIENT_COMPONENT=>DISPLAY_TOPLEVEL_COMPONENT
 8 METHOD CL_WDR_CLIENT_APPLICATION=====CP CL_WDR_CLIENT_APPLICATION=====CM00I 30
 CL_WDR_CLIENT_APPLICATION=>INIT
 7 METHOD CL_WDR_WEBDYNPRO_MAIN_TASK====CP CL_WDR_WEBDYNPRO_MAIN_TASK====CM008 29
 CL_WDR_WEBDYNPRO_MAIN_TASK=>IF_WDR_CLIENT_TASK~EXECUTE
 6 METHOD CL_WDR_CLIENT_MANAGER=========CP CL_WDR_CLIENT_MANAGER=========CM004 18
 CL_WDR_CLIENT_MANAGER=>PROCESS_TASK_LISTS
 5 METHOD CL_WDR_CLIENT_MANAGER=========CP CL_WDR_CLIENT_MANAGER=========CM002 99
 CL_WDR_CLIENT_MANAGER=>DO_PROCESSING
 4 METHOD CL_HTTP_EXT_WEBDYNPRO=========CP CL_HTTP_EXT_WEBDYNPRO=========CM001 77
 CL_HTTP_EXT_WEBDYNPRO=>IF_HTTP_EXTENSION~HANDLE_REQUEST
 3 METHOD CL_HTTP_SERVER================CP CL_HTTP_SERVER================CM00D 645
 CL_HTTP_SERVER=>EXECUTE_REQUEST
 2 FUNCTION SAPLHTTP_RUNTIME LHTTP_RUNTIMEU02 879
 HTTP_DISPATCH_REQUEST
 1 MODULE (PBO) SAPMHTTP SAPMHTTP 13
 %_HTTP_START
 Chosen variables
 Name
 Val.
 No. 22 Ty. METHOD
 Name CL_WDR_CONTEXT_NODE_VAL=>CHECK_COLLECTION
 ABAP_TRUE
 X
 5
 8
 ME->NODE_INFO->IS_MANDATORY
 X
 5
 8
 LINES
 12919
 7300
 7200
 %_DUMMY$$
 2222
 0000
 SYST-REPID
 CL_WDR_CONTEXT_NODE_VAL=======CP
 4455455444545554444554433333334522222222
 3CF742F3FE4584FEF45F61CDDDDDDD3000000000
 ABAP_FALSE
 2
 0
 ME->NODE_INFO->IS_MULTIPLE
 2
 0
 SY-REPID
 CL_WDR_CONTEXT_NODE_VAL=======CP
 4455455444545554444554433333334522222222
 3CF742F3FE4584FEF45F61CDDDDDDD3000000000
 ME
 O:167*=CL_WDR_CONTEXT_NODE_VAL
 5000A000
 80007000
 RSJOBINFO
 00000000000000 ####
 222222222222222222222222222222223333333333333322222222222222222222222222222222220000
 000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 PATH_NAME
 INDEX.1.EKKO_ITAB
 44445232444454544
 9E458E1E5BBFF9412
 SY
 ########################################w2##"#################################################
 0000000000000000000000000000000000000000730020000000000000000000000000000000000000000000000000
 1000000010001000000000000000000000000000720020001000000010000000000000000000800000000000000000
 %_EXCP
 O:13087*=CX_WD_CONTEXT
 E0001300
 0000F300
 SPACE
 2
 0
 CX_WD_CONTEXT=>COLLECTION_ILLEGAL_CARDINALITY
 B5CA499B9D5CBA47B8D4664C56B3A97C
 43443334343444334343333433434334
 25314992945321472844664356231973
 ME->SELECTION
 Table[initial]
 ME->NODE_INFO->IS_MANDATORY_SELECTION
 2
 0
 ME->NODE_INFO->IS_MULTIPLE_SELECTION
 2
 0
 No. 21 Ty. METHOD
 Name CL_WDR_CONTEXT_NODE_VAL=>IF_WD_CONTEXT_NODE~BIND_TABLE
 NEW_ITEMS
 Table IT_325[12919x492]
 POOL=/1BCWDY/MXAJIDSD2PZXCNSR7DDN=CL_INDEX_CTR=WDDOINIT=ITAB_EKKO
 Table reference: 153
 TABH+ 0(20) = C8E8E33CD0C4E73C000000009900000045010000
 TABH+ 20(20) = 77320000EC010000FFFFFFFF04C30000801B0000
 TABH+ 40( 8) = 10000000C1308000
 store = 0xC8E8E33C
 ext1 = 0xD0C4E73C
 shmId = 0 (0x00000000)
 id = 153 (0x99000000)
 label = 325 (0x45010000)
 fill = 12919 (0x77320000)
 leng = 492 (0xEC010000)
 loop = -1 (0xFFFFFFFF)
 xtyp = TYPE#000116
 occu = 16 (0x10000000)
 access = 1 (ItAccessStandard)
 idxKind = 0 (ItIndexNone)
 uniKind = 2 (ItUniqueNon)
 keyKind = 1 (default)
 cmpMode = 8 (cmpManyEq)
 occu0 = 1
 collHash = 0
 groupCntl = 0
 rfc = 0
 unShareable = 0
 mightBeShared = 0
 sharedWithShmTab = 0
 isShmLockId = 0
 gcKind = 0
 isUsed = 1
 >>>>> Shareable Table Header Data <<<<< tabi = 0xF8C9E33C
pghook = 0x08E9E33C
idxPtr = 0x00000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16368 (0xF03F0000)
lineAlloc = 12944 (0x90320000)
store_id = 202 (0xCA000000)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<< regHook = 0x80EFFE3C
hsdir = 0x00000000
ext2 = 0x00000000
>>>>> 2nd level extension part <<<<< tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
SET_INITIAL_ELEMENTS
X
5
8
ELEMENT
O:13086*=CL_WDR_CONTEXT_ELEMENT
E0001300
1000E300
ELEMENT->NODE
O:167*=CL_WDR_CONTEXT_NODE_VAL
5000A000
80007000
ME
O:167*=CL_WDR_CONTEXT_NODE_VAL
5000A000
80007000
ME->COLLECTION
Table IT_330[12919x8]
O:167*=CL_WDR_CONTEXT_NODE_VAL=COLLECTION
Table reference: 157
TABH+ 0(20) = 78F2FE3C00000000000000009D0000004A010000
TABH+ 20(20) = 7732000008000000FFFFFFFF04D10000E0030000
TABH+ 40( 8) = 10000000C1288000
store = 0x78F2FE3C
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 157 (0x9D000000)
label = 330 (0x4A010000)
fill = 12919 (0x77320000)
leng = 8 (0x08000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000008
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 4 (cmpSingleEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<< tabi = 0xE8F1FE3C
pghook = 0x18B8D83C
idxPtr = 0x00000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 15408 (0x303C0000)
lineAlloc = 13360 (0x30340000)
store_id = 207 (0xCF000000)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<< regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<< tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
SY-TABIX
1
0000
1000
%_SPACE
2
0
ME->LEAD_SELECTION_INDEX
1
0000
1000
ME->LEAD_SELECTION
O:168*=CL_WDR_CONTEXT_ELEMENT
5000A000
70008000
ME->NODE_INFO->IS_MANDATORY_SELECTION
2
0
ME->SELECTION
Table[initial]
ME->NODE_INFO->IS_INITIALIZE_LEAD_SELECTION
X
5
8
ME->IF_WD_CONTEXT_NODE~NO_SELECTION
-1
FFFF
FFFF
ME->ELEMENTS_SUPPLIED
2
0
No. 20 Ty. METHOD
Name CL_INDEX_CTR=>WDDOINIT
IF_WDR_APPLICATIONAPPLICATION_INFO->STARTUP_PLUG->IF_WD_RR_PARAM_FEATUREPARAMETERS
 Table[initial]
 State Dump for Thread Id 1488
 eax=00000001 ebx=00000103 ecx=fffffffe edx=003c0000 esi=00000000 edi=00000000
 eip=7c82ed54 esp=0589feb0 ebp=0589fef4 iopl=0 nv up ei pl zr na po nc
 cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
 function : KiFastSystemCallRet
 7c82ed54 c3 ret
 7c82ed55 8da42400000000 lea esp,[esp] ss:0589feb0=7c821514
 7c82ed5c 8d642400 lea esp,[esp] ss:098bd47f=00000000
 FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
 0589fef4 00ff70c7 000006c4 00000000 00000000 044bed68 ntdll!KiFastSystemCallRet
 0589ff84 7c349565 00000000 00000000 00000000 044becd0 disp+work!SigIMsgFunc
 0589ffb8 77e6608b 044becd0 00000000 00000000 044becd0 MSVCR71!endthreadex
 0589ffec 00000000 7c3494f6 044becd0 00000000 00000000 kernel32!GetModuleFileNameA
 List of ABAP programs affected
 Index Ty. Program Group Date Time Size Lang.
 0 Prg SAPMHTTP 0 06.11.2003 20:57:21 6144 E
 1 Prg SAPLHTTP_RUNTIME 1 12.11.2004 04:12:18 152576 E
 2 Typ ICFHANDLST 0 21.11.2003 11:40:58 13312
 3 Prg %_CIHTTP 1 12.11.2004 03:26:38 36864 E
 4 Typ ICFSERVICE 0 21.11.2003 11:41:18 13312
 5 Typ ICFATTRIB 0 06.11.2003 20:36:18 4096
 6 Typ ICFLOGIN 0 12.11.2004 03:26:38 9216
 7 Prg CL_HTTP_SERVER================CP 7 12.11.2004 04:13:34 154624 E
 8 Typ ICFRECORDER 0 06.11.2003 20:36:19 12288
 9 Typ IOPROP 0 29.03.2001 16:07:43 2048
 10 Typ ICFSTAT 0 09.11.2000 14:08:22 2048
 11 Prg CL_HTTP_UTILITY===============CP 11 12.11.2004 03:48:49 15360 E
 12 Prg CL_ABAP_TRACE=================CP 12 06.11.2003 21:53:44 6144 E
 13 Prg CL_ICF_RECORDER===============CP 13 12.11.2004 03:26:45 8192 E
 14 Prg CL_HTTP_SERVER_NET============CP 14 12.11.2004 04:13:34 101376 E
 15 Typ ICFRECODER_LOGON 0 06.11.2003 20:28:45 3072
 16 Prg CL_ABAP_RUNTIME===============CP 16 06.11.2003 20:59:29 8192 E
 17 Prg CL_HTTP_REQUEST===============CP 17 12.11.2004 03:48:50 20480 E
 18 Prg CL_HTTP_ENTITY================CP 18 12.11.2004 03:48:50 41984 E
 19 Prg CL_HTTP_RESPONSE==============CP 19 12.11.2004 04:13:34 24576 E
 20 Typ ICFALIAS 0 21.11.2003 11:41:17 13312
 21 Typ ICFVIRHOST 0 19.01.2001 18:13:06 2048
 22 Typ ICFBUFFER 0 21.11.2003 11:41:18 16384
 23 Prg SAPLSHTTP 23 12.11.2004 03:49:05 166912 E
 24 Typ ICFAPPLCUST 0 21.11.2003 11:41:17 2048
 25 Prg CL_HTTP_USER_CONTEXT==========CP 25 12.11.2004 03:48:50 9216 E
 26 Typ BAPIALIAS 0 09.12.1999 13:47:51 1024
 27 Prg SAPLLANG 27 06.11.2003 20:53:03 8192 E
 28 Typ T002 0 14.02.1998 10:24:58 2048
 29 Typ ABAPTEXT 0 16.03.1993 18:19:31 1024
 30 Prg SAPLSCP2 30 23.11.2004 18:49:18 126976 E
 31 Prg SSO2GETPARAM 1 06.11.2003 20:57:30 15360 E
 32 Prg SAPLSSFG 32 09.12.2003 11:41:04 116736 E
 33 Typ SSFARGS 0 19.11.2001 15:50:14 5120
 34 Typ PARMVALUES 0 03.01.1996 15:26:26 2048
 35 Prg SAPLSPFC 35 12.11.2004 03:38:48 239616 E
 36 Typ MOD_FIELDS 0 16.07.1997 14:42:34 2048
 37 Typ SSF_PSE_H 0 15.11.2000 17:54:53 4096
 38 Typ ICFRECSTRU 0 06.11.2003 20:28:45 2048
 39 Prg SAPLSAUTHTRACE 39 16.03.2004 20:07:17 43008 E
 40 Typ IHTTPNVP 0 29.03.2001 16:07:42 2048
 41 Prg CL_HTTP_EXT_WEBDYNPRO=========CP 41 12.11.2004 03:49:03 49152 E
 42 Prg IF_HTTP_EXTENSION=============IP 7 29.03.2001 17:03:40 5120 E
 43 Prg CL_HTTP_EXT_1X1_GIF===========CP 43 12.11.2004 03:48:51 11264 E
 44 Prg IF_HTTP_HEADER_FIELDS_SAP=====IP 43 06.06.2001 13:26:02 5120 E
 45 Prg CL_WDR_CLIENT_MANAGER=========CP 45 12.11.2004 03:48:52 47104 E
 46 Prg CL_WDR_TASK===================CP 46 12.11.2004 03:49:04 46080 E
 47 Prg CL_WDR_EVENT_QUEUE============CP 47 06.11.2003 21:11:25 10240 E
 48 Prg CX_WDR_RT_EXCEPTION===========CP 48 06.11.2003 21:15:08 15360 E
 49 Typ SCX_SRCPOS 0 09.11.2000 14:12:15 2048
 50 Prg CX_WD_EXCEPTION===============CP 50 06.11.2003 21:15:11 10240 E
 51 Prg CX_NO_CHECK===================CP 51 06.11.2003 21:33:04 8192 E
 52 Prg CX_ROOT=======================CP 52 06.11.2003 21:56:05 9216 E
 53 Prg CL_WDR_CLIENT_SSR=============CP 53 12.11.2004 04:21:19 121856 E
 54 Prg CL_WDR_CLIENT_ABSTRACT_HTTP===CP 54 12.11.2004 03:48:52 58368 E
 55 Prg CL_DYNP_GLOBAL_CONTROL========CP 55 06.11.2003 21:02:15 7168 E
 56 Prg CL_WDR_CLIENT_INSPECTOR=======CP 56 12.11.2004 03:48:49 39936 E
 57 Typ WDR_CLIENTS 0 06.11.2003 20:38:42 2048
 58 Typ WDR_CLIENT_DATA 0 06.11.2003 20:33:21 2048
 59 Prg CL_WDR_CLIENT_CONSTANTS=======CP 59 06.11.2003 21:11:17 12288 E
 60 Prg CL_WDR_CLIENT_CSF=============CP 60 12.11.2004 03:48:50 103424 E
 61 Prg IF_WDR_CLIENT_DESCRIPTION=====IP 56 06.11.2003 21:34:13 3072 E
 62 Prg CL_WDR_CLIENT_CSF_COND========CP 62 12.11.2004 03:26:52 32768 E
 63 Prg CL_WDR_CLIENT_ABSTRACT_COND===CP 63 12.11.2004 03:26:52 32768 E
 64 Prg IF_WDR_CLIENT_CONDITION=======IP 56 06.11.2003 21:34:13 29696 E
 65 Prg IF_WDR_CLIENT_INFO_OBJECT_HDL=IP 56 06.11.2003 21:34:13 29696 E
 66 Prg CL_WDR_CLIENT_XML=============CP 66 12.11.2004 03:48:49 80896 E
 67 Prg CL_WDR_CLIENT_XML_COND========CP 67 12.11.2004 03:48:49 32768 E
 68 Prg CL_WDR_VIEW_ELEM_ADAPTER_MNG==CP 68 06.11.2003 22:00:29 49152 E
 69 Prg CL_WDR_UIEL_ADAPTER_MANAGER===CP 69 16.03.2004 19:57:19 13312 E
 70 Prg CL_WDR_ABSTRCT_ADAPTER_MANAGERCP 70 06.11.2003 21:11:15 9216 E
 71 Typ WDY_MD_CHANGE_INFORMATION 0 06.11.2003 20:33:22 2048
 72 Typ WDY_UI_LIBRARY 0 06.11.2003 20:38:47 3072
 73 Prg CL_EXITHANDLER================CP 73 12.11.2004 03:49:03 27648 E
 74 Prg CL_ABAP_TYPEDESCR=============CP 74 07.11.2003 13:01:59 26624 E
 75 Prg CL_ABAP_ELEMDESCR=============CP 75 06.11.2003 22:11:36 33792 E
 76 Prg CL_ABAP_DATADESCR=============CP 76 06.11.2003 22:10:04 16384 E
 77 Prg CL_ABAP_REFDESCR==============CP 77 07.11.2003 13:01:58 20480 E
 78 Prg CL_ABAP_STRUCTDESCR===========CP 78 21.11.2003 11:42:45 34816 E
 79 Prg CL_ABAP_COMPLEXDESCR==========CP 79 06.11.2003 22:10:04 14336 E
 80 Prg CL_ABAP_TABLEDESCR============CP 80 06.11.2003 22:11:36 21504 E
 81 Prg CL_ABAP_CLASSDESCR============CP 81 06.11.2003 22:11:36 25600 E
 82 Prg CL_ABAP_OBJECTDESCR===========CP 82 06.11.2003 22:11:36 29696 E
 83 Prg CL_ABAP_INTFDESCR=============CP 83 06.11.2003 22:11:36 20480 E
 84 Prg CL_ABAP_SOFT_REFERENCE========CP 84 06.11.2003 20:41:10 8192 E
 85 Prg CL_ABAP_REFERENCE=============CP 85 06.11.2003 20:52:43 6144 E
 86 Prg IF_EX_WDR_UIE_LIBRARY=========IP 77 09.12.2003 11:45:52 4096 E
 87 Prg %_CABAP 83 06.11.2003 22:07:49 25600 E
 88 Typ SXS_INTER 0 30.11.1998 15:55:16 2048
 89 Prg SAPLSEXV 89 16.03.2004 20:14:01 108544 E
 90 Prg CL_BADI_FLT_DATA_TRANS_AND_DB=CP 90 12.11.2004 03:49:03 35840 E
 91 Typ SXS_ATTR 0 20.08.2001 12:23:27 4096
 92 Typ V_EXT_ACT 0 09.11.2000 14:27:05 2048
 93 Typ SXC_EXIT 0 09.11.2000 14:23:43 2048
 94 Prg SAPLSEXE 94 12.11.2004 03:49:05 78848 E
 95 Typ TADIR 0 09.11.2000 14:14:40 4096
 96 Prg SAPLPA_PACKAGE_SERVICES 96 12.11.2004 04:12:26 121856 E
 97 Typ SXS_MLCO 0 04.12.2000 14:59:55 2048
 98 Prg CL_EX_WDR_UIE_LIBRARY=========CP 98 09.12.2003 11:43:56 24576 E
 99 Prg CL_WDR_EVENT_ADAPTER_MANAGER==CP 99 06.11.2003 22:00:29 35840 E
 100 Prg CL_WDR_CLIENT_SSR_COND========CP 100 12.11.2004 03:48:49 33792 E
 101 Prg CL_WDR_SERVER_SESSION=========CP 101 09.12.2003 11:39:43 39936 E
 102 Prg CL_WDR_CLIENT_INFO_OBJECT=====CP 102 06.11.2003 21:11:17 12288 E
 103 Prg CL_WDR_CLIENT_USER============CP 103 06.11.2003 21:11:19 34816 E
 104 Prg SAPLISOC 104 06.11.2003 20:53:02 26624 E
 105 Prg CL_WDR_LOCALE=================CP 105 06.11.2003 21:11:28 7168 E
 106 Prg CL_WDR_CLIENT_SESSION=========CP 106 06.11.2003 21:11:18 36864 E
 107 Typ WDR_NAME_VALUE 0 06.11.2003 20:33:21 2048
 108 Prg CL_WDR_CLIENT_WINDOW==========CP 108 06.11.2003 21:11:19 40960 E
 109 Prg IF_WDR_CLIENT=================IP 56 06.11.2003 21:34:13 30720 E
 110 Prg CX_SY_MOVE_CAST_ERROR=========CP 110 06.11.2003 20:41:23 9216 E
 111 Prg CX_DYNAMIC_CHECK==============CP 111 06.11.2003 21:33:04 8192 E
 112 Prg CL_WDR_REC_PLUGIN_MANAGER=====CP 112 06.11.2003 22:00:29 50176 E
 113 Typ WDR_REC_PLUGIN 0 06.11.2003 20:38:42 2048
 114 Prg SAPLSPLUGIN 114 06.11.2003 21:28:25 6144 E
 115 Prg CL_WDR_WEBDYNPRO_MAIN_TASK====CP 115 12.11.2004 03:49:04 60416 E
 116 Prg IF_WDR_CLIENT_TASK============IP 45 06.11.2003 21:34:13 4096 E
 117 Typ WDR_EVENT_ADAPTER 0 09.12.2003 11:37:55 2048
 118 Prg CL_WDAL_URD2_DYNPRO_CONVERSIONCP 118 12.11.2004 04:21:19 263168 E
 119 Prg CL_WDR_SYSTEM_EVT_HANDLER_REG=CP 119 06.11.2003 21:11:35 33792 E
 120 Prg CL_WDR_ABSTRACT_SRV_EVTHDL_REGCP 120 06.11.2003 21:11:15 34816 E
 121 Prg CL_WDR_CLIENT_APPLICATION=====CP 121 12.11.2004 03:48:49 67584 E
 122 Prg CL_WDR_CLIENT_COMPONENT=======CP 122 09.12.2003 11:39:43 64512 E
 123 Prg CL_WDR_RR_RUNTIME_REPOSITORY==CP 123 16.03.2004 19:57:19 27648 E
 124 Prg CL_WDR_RR_APPLICATION=========CP 124 06.11.2003 22:00:29 29696 E
 125 Typ WDY_APPLICATION 0 06.11.2003 20:38:43 3072
 126 Prg CX_WDR_RR_EXCEPTION===========CP 126 09.12.2003 11:39:45 15360 E
 127 Typ WDY_RT_OBJECT_MAP 0 06.11.2003 20:33:24 2048
 128 Prg CL_WDR_RR_COMPONENT===========CP 128 12.11.2004 03:49:04 73728 E
 129 Typ WDY_RR_COMPONENT 0 27.01.2004 13:51:32 2048
 130 Typ WDY_RR_VIEW 0 06.11.2003 20:33:24 2048
 131 Typ WDY_RR_VIEW 0 06.11.2003 20:33:24 2048
 132 Typ WDY_RR_WINDOW 0 06.11.2003 20:33:24 2048
 133 Typ WDY_RR_WINDOW 0 06.11.2003 20:33:24 2048
 134 Typ WDY_RR_COMPO_USAGE 0 06.11.2003 20:33:23 2048
 135 Typ WDY_RR_COMPO_USAGE 0 06.11.2003 20:33:23 2048
 136 Typ WDY_RR_CONTROLLER 0 06.11.2003 20:33:23 2048
 137 Typ WDY_RR_CONTROLLER 0 06.11.2003 20:33:23 2048
 138 Typ WDY_RR_VUSAGE 0 06.11.2003 20:33:24 3072
 139 Typ WDY_RR_VUSAGE 0 06.11.2003 20:33:24 3072
 140 Typ WDY_RR_VCA_INFO 0 06.11.2003 20:33:23 2048
 141 Typ WDY_RR_VCA_INFO 0 06.11.2003 20:33:23 2048
 142 Typ WDY_RR_NAV_LINK 0 06.11.2003 20:33:23 2048
 143 Typ WDY_RR_NAV_LINK 0 06.11.2003 20:33:23 2048
 144 Typ WDY_RR_NAV_TARGREF 0 06.11.2003 20:33:23 2048
 145 Typ WDY_RR_NAV_TARGREF 0 06.11.2003 20:33:23 2048
 146 Typ WDY_SUBSCRIBED_EVENT 0 06.11.2003 20:33:24 2048
 147 Typ WDY_SUBSCRIBED_INBOUND_PLUG 0 06.11.2003 20:33:24 2048
 148 Typ WDY_RR_CTLR_COMPO 0 06.11.2003 20:33:23 3072
 149 Typ WDY_RR_CTLR_COMPO 0 06.11.2003 20:33:23 3072
 150 Typ WDY_RR_UI_EVT_BIND 0 06.11.2003 20:33:23 2048
 151 Typ WDY_RR_UI_EVT_BIND 0 06.11.2003 20:33:23 2048
 152 Typ WDY_RR_UI_VIEW_CONT 0 06.11.2003 20:33:23 2048
 153 Typ WDY_RR_UI_VIEW_CONT 0 06.11.2003 20:33:23 2048
 154 Typ WDY_RR_IOBOUND_PLUG 0 06.11.2003 20:33:23 2048
 155 Typ WDY_RR_IOBOUND_PLUG 0 06.11.2003 20:33:23 2048
 156 Typ WDY_RR_PARAMETER 0 06.11.2003 20:33:23 2048
 157 Typ WDY_RR_PLUG_PARAMS 0 06.11.2003 20:33:23 3072
 158 Typ WDY_RR_PLUG_PARAMS 0 06.11.2003 20:33:23 3072
 159 Typ WDY_RR_UI_ELEM_DEFS 0 06.11.2003 20:33:23 3072
 160 Typ WDY_RR_UI_ELEM_DEFS 0 06.11.2003 20:33:23 3072
 161 Typ WDY_RR_UI_ELEM 0 06.11.2003 20:33:23 3072
 162 Typ WDY_RR_UI_ELEM 0 06.11.2003 20:33:23 3072
 163 Typ WDY_RR_CLUSTER 0 27.01.2004 13:51:32 21504
 164 Prg CL_WDY_MD_PARAM_FEATURE=======CP 164 16.03.2004 20:12:30 25600 E
 165 Typ WDY_MD_OBJECT_DESCRIPTION 0 09.12.2003 11:37:56 2048
 166 Prg CL_WDY_MD_OBJECT==============CP 166 06.11.2003 22:00:30 12288 E
 167 Prg CL_WDR_RR_DB==================CP 167 16.03.2004 20:12:30 82944 E
 168 Typ WDY_COMPONENT 0 06.11.2003 20:38:43 3072
 169 Typ WDY_RR_TEXT 0 06.11.2003 20:33:23 2048
 170 Typ SOTR_KEY 0 09.12.1999 13:48:20 2048
 171 Typ SOTR_TERM 0 15.11.2000 17:54:28 3072
 172 Prg SAPLSOTR_DB_READ 172 12.11.2004 04:15:08 39936 E
 173 Typ SOTR_CNTXT 0 09.12.1999 13:48:20 2048
 174 Typ SOTR_ADMIN 0 09.12.1999 13:48:20 2048
 175 Typ SOTR_TEXT 0 06.11.2003 20:31:14 5120
 176 Typ SOTR_HEAD 0 15.11.2000 17:54:28 4096
 177 Prg CL_WDR_RR_EMPTY_VIEW==========CP 177 06.11.2003 21:11:32 28672 E
 178 Prg CL_WDR_RR_ABSTRACT_VIEW=======CP 178 06.11.2003 22:00:29 35840 E
 179 Prg CL_WDR_RR_INBOUND_PLUG========CP 179 06.11.2003 21:11:32 32768 E
 180 Prg CL_WDR_RR_INCOMING_EVENT======CP 180 06.11.2003 21:11:32 26624 E
 181 Prg CL_WDR_RR_PARAM_FEATURE=======CP 181 06.11.2003 21:11:33 28672 E
 182 Prg CL_WDR_RR_COMPONENT_INTF_IMPL=CP 182 06.11.2003 21:11:31 29696 E
 183 Prg CL_WDR_RR_COMPONENT_INTERFACE=CP 183 06.11.2003 21:11:30 31744 E
 184 Prg CL_WDR_RR_CONTROLLER==========CP 184 06.11.2003 22:00:29 36864 E
 185 Prg CL_WDR_RR_WINDOW==============CP 185 06.11.2003 22:00:29 43008 E
 186 Prg CL_WDR_RR_VIEW_USAGE==========CP 186 06.11.2003 22:00:29 54272 E
 187 Prg CL_WDY_MD_ABSTRACT_VIEW=======CP 187 19.07.2004 03:41:57 96256 E
 188 Typ WDY_VIEW 0 06.11.2003 20:38:47 4096
 189 Prg CL_WDR_RR_VIEW================CP 189 06.11.2003 22:00:29 39936 E
 190 Prg CL_WDR_RR_INTERFACE_VIEW======CP 190 06.11.2003 21:11:32 30720 E
 191 Prg CL_WD_TODO====================CP 191 06.11.2003 21:12:50 24576 E
 192 Prg CL_WDR_CONFIGURATION_CONSTANTSCP 192 06.11.2003 21:11:20 6144 E
 193 Prg CL_WDR_SERVER_CONSTANTS=======CP 193 06.11.2003 21:11:34 6144 E
 194 Prg CL_WDR_UI_ELEMENT_FACTORY=====CP 194 06.11.2003 21:11:36 31744 E
 195 Prg /1BCWDY/MXAJIDSD2PZXCNSR7DDN==CP 195 24.02.2007 13:45:21 89088 E
 196 Prg IF_WDR_CLASSLOADER============IP 122 06.11.2003 21:34:13 27648 E
 197 Prg CL_WDR_DELEGATING_COMPONENT===CP 197 06.11.2003 21:11:24 46080 E
 198 Prg CL_WDR_COMPONENT==============CP 198 06.11.2003 22:09:16 60416 E
 199 Prg CL_WDR_CONTROLLER=============CP 199 06.11.2003 22:00:29 45056 E
 200 Prg IF_WDR_CONTEXT================IP 197 06.11.2003 21:34:13 27648 E
 201 Typ WDR_CONTEXT_ATTR_VALUE 0 06.11.2003 20:33:21 2048
 202 Typ WDR_CONTEXT_ATTR_VALUE 0 06.11.2003 20:33:21 2048
 203 Typ WDR_CONTEXT_ATTRIBUTE_INFO 0 06.11.2003 20:33:21 3072
 204 Typ WDR_CONTEXT_MAPPING_INFO 0 06.11.2003 20:33:21 2048
 205 Prg CL_WDR_CONTEXT_NODE_INFO======CP 205 09.12.2003 11:39:43 29696 E
 206 Prg CX_WD_CONTEXT=================CP 206 06.11.2003 21:15:10 12288 E
 207 Prg CL_WDR_CONTEXT_NODE===========CP 207 09.12.2003 11:39:43 45056 E
 208 Typ WDR_CONTEXT_CHILD 0 06.11.2003 20:33:21 2048
 209 Prg CL_WDR_CONTEXT_NODE_VAL=======CP 209 09.12.2003 11:39:43 66560 E
 210 Prg IF_WDR_COMPONENT_DELEGATE=====IP 195 16.03.2004 20:12:31 27648 E
 211 Prg IF_WD_CONTROLLER==============IP 197 09.12.2003 11:46:03 27648 E
 212 Prg CL_WDR_MESSAGE_MANAGER========CP 212 09.12.2003 11:39:43 74752 E
 213 Prg CL_WDR_DATA_CONTAINER=========CP 213 09.12.2003 11:39:43 69632 E
 214 Typ WDY_RT_DATA_CONT_ATTR_MAP 0 06.11.2003 20:33:24 3072
 215 Typ WDY_RT_DATA_CONT_CNTL 0 06.11.2003 20:33:24 2048
 216 Prg CL_WDR_APPLICATION_WINDOW=====CP 216 06.11.2003 21:11:15 44032 E
 217 Prg CL_WDR_WINDOW=================CP 217 06.11.2003 22:00:29 50176 E
 218 Prg IF_WDR_APPLICATION============IP 101 06.11.2003 22:07:12 29696 E
 219 Typ WDR_EVENT_PARAMETER 0 06.11.2003 20:33:21 2048
 220 Typ WDR_VIEWMAN_LINE 0 06.11.2003 20:33:21 2048
 221 Prg CL_WDR_VIEW_MANAGER===========CP 221 12.11.2004 03:49:04 70656 E
 222 Prg IF_WDR_VIEW_MANAGER===========IP 221 06.11.2003 22:07:12 27648 E
 223 Typ WDR_CONTROLLER_LINE 0 06.11.2003 20:33:21 2048
 224 Prg CX_WDR_BAD_STATE==============CP 224 06.11.2003 21:15:06 9216 E
 225 Prg CX_WDR_RUNTIME================CP 225 06.11.2003 21:15:08 10240 E
 226 Typ WDR_CLIENTCOMP_LINE 0 06.11.2003 20:33:21 2048
 227 Prg CL_WDR_WINDOW_MANAGER=========CP 227 06.11.2003 21:11:39 37888 E
 228 Prg CL_WDR_DELEGATING_IF_VIEW=====CP 228 06.11.2003 21:11:24 45056 E
 229 Prg CL_WDR_INTERFACE_VIEW=========CP 229 06.11.2003 21:11:28 43008 E
 230 Prg CL_WDR_VIEW===================CP 230 06.11.2003 22:00:29 62464 E
 231 Prg IF_WDR_VIEW_DELEGATE==========IP 195 16.03.2004 20:12:31 27648 E
 232 Prg IF_WD_CONTEXT_NODE============IP 228 09.12.2003 11:46:03 31744 E
 233 Prg IF_WD_CONTEXT_NODE_INFO=======IP 228

Error - Creating a Web Dynpro Application Accessing ABAP Functions

Dear All,
we are trying to implement a web dynpro application with accessing ABAP functions.
Previous tasks:
- insert the ABAP system into the SLD from the NWDI System (Transaction RZ70; the ABAP system is correctly insert into the SLD => technical systems)
- equipped the JCO connections with the web dynpro content manager (ping and test = OK)
Its the standard tutorial out of the SDN called Creating a Web Dynpro Application Accessing ABAP Functions.
Some hints:
- There are no errors after the implementation and the rebuild of the project in the NWDS
- The auto deployment works fine to the development runtime system. The application is shown in the Web Dynpro content manager
- The In the build log I found these entries:
System.err] [Invoked from com.sap.s2x.tools.GUID.getnodeaddress(GUID.java:585)]
[System.err] java.net.UnknownHostException: FRASAPP562: FRASAPP562
[System.err] at java.net.InetAddress.getLocalHost(InetAddress.java:1191)
[System.err] at com.sap.s2x.tools.GUID.getnodeaddress(GUID.java:575)
[System.err] at com.sap.s2x.tools.GUID.<clinit>(GUID.java:179)
[System.err] at com.sap.s2x.tools.S2XGUID.getGUID(S2XGUID.java:19)
[System.err] at com.sap.ide.metamodel.core.i18n.LanguageState.createS2XID(LanguageState.java:191)
[System.err] at com.sap.ide.metamodel.core.i18n.S2XLanguageUnmarshaller.unmarshal(S2XLanguageUnmarshaller.java:52)
[System.err] at com.sap.ide.metamodel.core.i18n.TextPoolProxy.loadLanguageState(TextPoolProxy.java:703)
[System.err] at com.sap.ide.metamodel.core.i18n.TextPoolProxy.prepareLanguageForRead(TextPoolProxy.java:646)
[System.err] at com.sap.ide.metamodel.core.i18n.TextPoolProxy.isEmpty(TextPoolProxy.java:222)
[System.err] at com.sap.ide.webdynpro.checklayer.MDOChecker.check(MDOChecker.java:23)
[System.err] at com.sap.ide.webdynpro.checklayer.view.ViewChecker.check(ViewChecker.java:52)
[System.err] at com.sap.ide.webdynpro.checklayer.controller.ViewControllerChecker.check(ViewControllerChecker.java:96)
[System.err] at com.sap.ide.webdynpro.checklayer.controller.ControllerChecker.check(ControllerChecker.java:119)
[System.err] at com.sap.ide.webdynpro.checklayer.controller.ControllerChecker.check(ControllerChecker.java:56)
[System.err] at com.sap.ide.webdynpro.checklayer.component.ComponentChecker.check(ComponentChecker.java:181)
[System.err] at com.sap.ide.webdynpro.checklayer.component.ComponentChecker.check(ComponentChecker.java:56)
[System.err] at com.sap.ide.webdynpro.generation.Generation.check(Generation.java:2039)
[System.err] at com.sap.ide.webdynpro.generation.Generation.generatePersistentComponent(Generation.java:1296)
[System.err] at com.sap.ide.webdynpro.generation.console.GenerationConsole.generate(GenerationConsole.java:175)
[System.err] at com.sap.webdynpro.generation.ant.GenerationAnt.main(GenerationAnt.java:50)
[System.err] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[System.err] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[System.err] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[System.err] at java.lang.reflect.Method.invoke(Method.java:324)
[System.err] at com.sap.webdynpro.generation.ant.WDGenAntTask.execute(WDGenAntTask.java:219)
[System.err] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[System.err] at org.apache.tools.ant.Task.perform(Task.java:364)
[System.err] at org.apache.tools.ant.Target.execute(Target.java:341)
[System.err] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[System.err] at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
[System.err] at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:112)
[System.err] at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:61)
[System.err] at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:213)
[System.err] at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:190)
[System.err] at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)
[System.err] at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)
[System.err] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[System.err] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[System.err] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[System.err] at java.lang.reflect.Method.invoke(Method.java:324)
[System.err] at com.sap.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:350)
[System.err] at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:102)
[System.err] at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:76)
[System.err] at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:58)
[System.err] at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1723)
[System.err] at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1495)
[System.err] at com.sap.tc.buildcontroller.CBSBuildController.build(CBSBuildController.java:727)
[System.err] at com.sap.tc.buildcontroller.CBSBuildController.execCommand(CBSBuildController.java:503)
[System.err] at com.sap.tc.buildcontroller.CBSBuildController.evalCmdLine(CBSBuildController.java:442)
[System.err] at com.sap.tc.buildcontroller.CBSBuildController.run(CBSBuildController.java:314)
[System.err] at com.sap.tc.buildcontroller.CBSBuildController.exec(CBSBuildController.java:252)
[System.err] at com.sap.tc.buildcontroller.CBSBuildController.mainLoop(CBSBuildController.java:207)
- Im able to start the application out of the Web Dynpro content manager with run => only the user interface is displayed without any functionality
- The normal start over the NWDS fails => error text
com.sap.tc.webdynpro.services.sal.core.DispatcherException: The requested deployable object 'local/J08_Flugdat_Daventdcflight~xxx.com' and application 'FlightListApp' are not deployed on the server. Please check the used URL for typos.
There two different URLs in use.
Start via NWDS:
http://frasapp562:50000/webdynpro/dispatcher/J08_Flugdat_Daventdcflight~xxx.com/FlightListApp
Start via web dynpro content manager:
http://frasapp562:50000/webdynpro/dispatcher/xxx.com/aventdc~flight/FlightListApp
For test purposes, we started the BAPI (BAPI_Flight_Getlist) on the ABAP system directly. It works.
Any ideas about the system behaviours (different URLs and missing functionality)?
Thanks a lot in advanced!
Best regards
Christoph

The Error has been solved The implementation of a method was missing....
Thx
Christoph

I am getting a error while executing the Web Dynpro Application Page.

Hi All,
I am getting a Error while executing a web dynpro application :::
: Navigation in Phase WDDOMODIFYVIEW Cannot Be Triggered. Component: Z_WEP_PERSONAL_DATA, View: OVERVIEW, Window: Z_XXP_PERSONAL_DATA
I have checked this error description in ST22 :
What happened?
    The exception 'CX_WDR_RT_EXCEPTION' was raised, but it was not caught anywhere
     along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
     'CL_WDR_CLIENT_APPLICATION=====CP' has to be
    terminated.
Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_WDR_RT_EXCEPTION', was not caught
     and
    therefore caused a runtime error.
    The reason for the exception is:
    Navigation in Phase WDDOMODIFYVIEW Cannot Be Triggered. Component:
    Z_XXP_PERSONAL_DATA, View: OVERVIEW, Window: Z_XXP_PERSONAL_DATA
Can u plz help me regarding this error.
Thanks,
Deepika

>Navigation in Phase WDDOMODIFYVIEW Cannot Be Triggered
Looks to me like you are trying to fire a navigation plug within WDDOMODIFYVIEW. According to the rules of the WD Phase Model this is not allowed.

Application specific theme in CE7.1 web dynpro application

Hi,
where can I find documentation about setting up application specific themes for Java Web Dynpro applications running in Composition Environment 7.1? I've found documents that refer to the Visual Administrator but since it doesn't exist anymore in CE7.1 there must be a different way.
Regards,

Hi Kevin,
Yes, charts are going to be supported in WD html in next versions of VC( Q3 2008).
Regards,
Kobi.

Delete a file from the KM in a Web Dynpro application

Hello,
We need to delete a file from the KM in a Web Dynpro application.
We have a file name (filename.txt) and its path (/documents/Test/), how can we completely delete the file from the KM?
Thanks,
Gil

Hi venkata reddy,
You wrongly mentioned system admin instead of content admin
Go to Content administration not in the system administration
if u delete the file manually in the portal you can go with
go to Content administration -> KM Content -> go to Particular document -> just tick the check box which doc u want delete -> go to selection -> u will find delete .
Regards,
P.Manivannan

I want to editable description field in my web dynpro application

Hi expert,
The requirement is to make the Description field editable. However, the container for the dynpro only appears to allow for a certain type of action and is essentially used to display the Line Item details, giving no option to change the Line Item Description.
so i want to editable in this description field in my web dynpro application /SAPSRM/WDC_DOTC_PC_I_BD .
Kindly give me soulation ASAP.
Thanks and Regard's.
Vikash

Thanks for the reply.
The name of the view is V_PC_DOTC_ITM on which we have the records. On each line item there is a description field which is of type (LinkToAction). I want to enable user so that it can change the Description text (I will handle the action). Also, if you have any idea about updating the database table from here as it needs to be updated in BBP_PCPOS table.
-vikash

Close External Window in Web Dynpro Application

Hi Folks,
I am working on a development in Web Dynpro and I am pretty new to this topic, so I seek your help.
The scene is:
I have created a Web Dynpro application in which I open an URL using CREATE_EXTERNAL_WINDOW method of the Window Controller. I am able to open the window but not able to close it.
I tried using methods,
CLOSE()
and
SET_CLOSE_IN_ANY_CASE()
but no success.
Please guide me if anything more needs to be done for closing the opened window.
Thank you.
Sud.

Thank you Thomas,
You correctly pointed out, I was trying to close the external window from my source window.
More precisely, I have a WD application which has a button (Search) on one of its views. On click of 'Search' button, I open a new window using 'CREATE_EXTERNAL_WINDOW' passing the URL 'www.google.com'.
Till this point its fine, but now I want to close this newly opened window. As you said now these are 2 different sessions and cannot communicate anymore, so any guidance how to close this new window?.
OR
Is this the only way to call an URL i.e using CREATE_EXTERNAL_WINDOW? Is there any other way to call an URL without closing my current running WD application?
Request your help......
Thanks.
Regards,
Sud....

Web Dynpro applications not working on ECC 6.0 IDES

Hi,
I'm new to Web Dynpro and developed a custom Web Dynpro (including the application) on a ECC 6.0 IDES system. It's simple with a couple of input fields. When I test it (either via SAP GUI 7.1 or 7.2, or Web GUI), it appears on the browser ok but the screen is frozen. I can't enter anything into the fields, etc. I also tested SAP Web Dynpro applications and they act the same way, frozen screen. There aren't any errors displayed or any runtime errors in ST22. Please advise. I searched this forum but didn't see any issue similar to mine. The IDES vendor suggested I post the issue on SDN.
John

I guess it has do to with some sort of browser's font size or view settings.
press ctrl +0 make the zoom 100% and font size medium and try again.
thanks
sarbjeet singh

View KM document in Web Dynpro application

Similar Messages

Maybe you are looking for