CProjects:Error in webdynpro enhancement

Hi,
We had added some custom fields in the basic data tab of task by creating an enhancement in teh standard web dynpro component dpr_det_task_o. It was working fine.
Then we went to SE19 to the enhancement implementation-.changed the description and again attached it to a new transport and tried activating it.
Now, though we did not make any other changes, the enhancement does not get activated as it shows some conflicts in teh adjustment tab of the enhancement implementation in se19. The yellow error icon which gets displayed against the error says "Tool supported enhancement".
I am unable to understand the meaning of this error. we did not change anything in the enhancement but the error messages say some conflicts have occured in the layout.
If anyone has come across something like this, please let me know.
Regards,
Simmi

Hi,
We have a similar issue with an enhancement in this view. We got this error after implementing a Support Package (PPM 4.5), and today we didn't succeed in fixing it?
Component error: Conflicts in layout have occurred
Detailed errors: Parent element XXX for element XXX_LAYOUT_DATA does not exist
Maybe there was a change in your system as well?
Matthias

Similar Messages

Error message in enhancement spot

Hi...,
I want to give error message in enhancement spot.
I am using FM 'CR_BT_ORDER_POST'.
wHEN USER WILL TRY TO CHANGE SERVICE ORDER.i WANT TO THROUGH ERROR MESSAGE.AND KEEP THE CURSOR ON SAME SERVICE ORDER SCREEN
But now it is coming out of IW32.WHEN I AM GIVING ABORT MESSGAE TYPE.ERROR MESSAGE IS NOT ALLOWED IN UPDATE TASK MODE.
tHANKS,
aNIL

Hi,
I think you have to use the function module 'POPUP_TO_CONFIRM' give the error message what you want to and if the user press any button keep the control on the same screen.
Regards,
Himanshu

Time out error in webdynpro

Hi all,
We are facing a time out error uisng webdynpro.
The webdynpro application is mapped to the enterprise portal for the users.
When ever the users loads the application and first click on the link then again loads the application and click any link(as clicked previously) then the application returs time out error.
I am little confused as not known the error is a portal one or webdynpro error.
Requesting experts for a say on this.
thanks

Hi,
You can try this...
Re: TimeOut
Cheers,
Kris.

Syntax Error after creating enhancements for subroutine

Problem:
Creating enhancement sections gives a syntax error when creating enhancement options and implementations for a subroutine and then ceating enhancement options and implementations for the call to that same subroutine.

Syntax Error:
"Different number of parameters in FORM and PERFORM (routine: SET_LAYOUT, number of formal parameters: 2, number of actual parameters: 1)


Here's the following scenario:


A subroutine is defined in a program.
The subroutine is called within the same program.


I then executed these steps:
 1. Defined an enhancement section around the subroutine definition
 2. Defined an enhancement section around the subroutine call.
 3. Implemented the enhancement section around the subroutine definition and add an additional parameter.


 Currently, this gives a syntax error as expected, since the call to the subroutine needs 1 more parameter.


 4. Implemented the enhancement section for the subroutine call. I change the call in the implementation so it passes the new parameter.


A syntax check to this gives an error. The syntax checker is not only checking the new implementation, but also the original subroutine that should have been overwritten.


The enhancement sections use the same enhancement spot, and the enhancement implementations use the same implementation.


I tried various combinations of using different enhancement spots and/or implementations, but all give the same syntax error. I tried separating the subroutine in a different include and retried my testing, but it still gave the same syntax error.


Here's the sample code I first created to try troubleshooting the problem:


<pre>
ENHANCEMENT-SECTION ZEP_Z_MICHAEL_02 SPOTS ZES_Z_MICHAEL .
 PERFORM set_layout
 CHANGING
 wa_layout.
END-ENHANCEMENT-SECTION.
$$-Start: ZEP_Z_MICHAEL_02----
$$
ENHANCEMENT 2 ZEI_TEST_SECTIONS.
 "inactive version
 PERFORM set_layout
 using 'X'
 CHANGING
 wa_layout.
ENDENHANCEMENT.
$$-End: ZEP_Z_MICHAEL_02----
$$
ENHANCEMENT-SECTION ZEP_Z_MICHAEL_01 SPOTS ZES_Z_MICHAEL STATIC .
FORM set_layout
CHANGING p_wa_layout TYPE slis_layout_alv.
p_wa_layout-zebra = 'X'.
wa_layout-no_colhead = 'X'..
p_wa_layout-colwidth_optimize ='X'.
wa_layout-window_titlebar = 'Woot'.
ENDFORM. "set_layout
END-ENHANCEMENT-SECTION.
$$-Start: ZEP_Z_MICHAEL_01----
$$
ENHANCEMENT 1 ZEI_TEST_SECTIONS.
 "inactive version
FORM set_layout
using p_test type boolean
CHANGING p_wa_layout TYPE slis_layout_alv.
p_wa_layout-zebra = 'X'.
wa_layout-no_colhead = 'X'..
p_wa_layout-colwidth_optimize ='X'.
wa_layout-window_titlebar = 'Woot'.
ENDFORM. "set_layout
ENDENHANCEMENT.
$$-End: ZEP_Z_MICHAEL_01----
$$
</pre>


Please let me know if you think I am doing something wrong.


Thanks, 
Mike

Edited by: Michael Herman on Mar 8, 2010 8:11 PM

Yes, Sandra. That is what did and it worked with no syntax errors!
I'm not sure if this is getting off topic or not, but the SAP documentation(taken from the SAP help after pressing F1 on the keyword static in ERP6) seems misleading:
"The STATIC addition is intended for the enhancement of data declarations, while the statement ENHANCEMENT-POINT without the STATIC addition is designed for the enhancement of executable coding."
I would think the enhancement section ZEP_Z_MICHAEL_02 would fall under the category of executable code, while the enhancement section ZEP_Z_MICHAEL_01 would fall under the category of declarative code.
Unfortunately, all the SAP enhancement sections I come accross are dynamic. The SAP help explains the reasoning for this:
"In contrast to the statement ENHANCEMENT-POINT, the addition STATIC of the statement ENHANCEMENT-SECTION can only be used with maximum caution for changes of data declarations, because a replacement and no completion is carried out. Especially application development within SAP should not use the addition STATIC at all with ENHANCEMENT-SECTION as the change will be active in the entire customer system. "
I do not know what the word "completion" means in the previous quote, so I can't determine why it would matter. Regardless, if a developer wanted to change a standard subroutine declaration, they would also have to mod an enhancement section to change it to static. This seems to defeat the purpose of using enhancements, but maybe this scenario is not what enhancements were intended for.

Sub node does not exist error in webdynpro.

Hello Experts,
I have Faced following Run time Error in Webdynpro.
"Subnode ZALV21.ALV_TABLE does not exist "
I done External Mapping Neatly In controller Usage.Even Though I faced this Runtime Error.
Kindly Reply me ASAP.
Regards,
Ameya Karadkhedkar

Hi,
Is component controller of your component is active? It seems that the node ALV_TABLE is not being activated. Hence the instance of it not found during run time.
Regards,
Rama

Webdynpro Enhancement for DPR_DET_CONTAINER in cProjects

Hi gurus,
We are presently working on cPprojects web dynpros, we have to enhance some of the dynpros.
I have a requirement where the Web dynpro component DPR_DET_CONTAINER has to be enhanced. We need to add a tab named contract detail in DPR_DET_CONTAINER.
Can some please tell me how to modify a standard webdynpro specially DPR_DET_CONTAINER.
Regards,
Abhi.

No need in most cases to mod anything.
I dont know what you enhancement does / should do.
Here is a sample from one of my basic C-Project enhancements. Extra TAB.
Good Luck,
Phil.
*** WDA CPROJECT INCLUDE
method CONTROL_BE_RETRIEVE .
 DATA: lr_context TYPE REF TO if_wd_context.
IF wd_this->mv_upd_flag = abap_true.
 lr_context = wd_context->get_context( ).
 lr_context->reset_context_change_log( ).
 lr_context->reset_changed_by_client( ).
 wd_this->update_data_from_be( ).
* context is up to date!
 CLEAR wd_this->mv_upd_flag.
ENDIF.
endmethod.
method ON_AFTER_SAVE .
wd_this->mv_upd_flag = abap_true.
wd_this->control_be_retrieve( ).
endmethod.
method ON_REPORT_CHANGES .
* 1. get context changes and report to changemanager
* 2. report actions to changemanager
DATA lr_context TYPE REF TO if_wd_context.
DATA lt_changed_attr TYPE wdr_context_change_list.
DATA ls_changed_attr TYPE LINE OF wdr_context_change_list.
DATA ls_action TYPE dpr_ts_ui_do_action.
DATA lv_rejected TYPE boole_d.
* check changelog
lr_context = wd_context->get_context( ).
lt_changed_attr = lr_context->get_context_change_log( ).
IF NOT lt_changed_attr[] IS INITIAL.
 wd_this->fire_changes_occurred_evt( ).
 wd_this->mv_upd_flag = abap_true.
ENDIF.
LOOP AT wd_this->mt_action INTO ls_action.
 wd_this->fire_send_events_evt( ).
 wd_this->mv_upd_flag = abap_true.
ENDLOOP.
CLEAR wd_this->mt_action[].
endmethod.
METHOD on_set_change_mode .
DATA:
node_ui_ctrl TYPE REF TO if_wd_context_node,
elem_ui_ctrl TYPE REF TO if_wd_context_element,
stru_ui_ctrl TYPE if_componentcontroller=>element_ui_ctrl ,
lv_abap_bool TYPE abap_bool.
*>>>>>>>>>>>>>>>> SET THE DISPLAY MODE <<<<<<<<<<<<<<<<<START<
*is_cust_input_values-change_mode = 0. READ_ONLY true
node_ui_ctrl = wd_context->get_child_node( name = if_componentcontroller=>wdctx_ui_ctrl ).
* get the node where we control the UI from
elem_ui_ctrl = node_ui_ctrl->get_element( ).
* set read only based on mode passed in
IF new_mode = 0.
 lv_abap_bool = abap_true.
ELSE.
 lv_abap_bool = abap_false.
ENDIF.
* and set ctx appropriately
elem_ui_ctrl->set_attribute( value = lv_abap_bool
 name = 'READ_ONLY' ).
*>>>>>>>>>>>>>>>> SET THE DISPLAY MODE <<<<<<<<<<<<<<<<<END<
ENDMETHOD.
method ON_UPDATE .
* check if the PO DATA is complete,
* throw an error if not.
check wd_this->mv_upd_flag = abap_true.
wd_this->control_be_retrieve( ).
endmethod.
method README .
** WDC documentaiton
*This WDC is used as a common include
*This component starts via inbound window PLUG
*The plug decides with view category to call and fires the appropriate
*outbound plug to navigate to the next view
*Common routines at component controller are used to react to the
*save event.
*A common model class is called to post the Phase data.
*The context on the Component CTR is used to post data.
*Context tracking is used to send the event "changes occurred"
endmethod.
METHOD start .
* load the project info
* and retrieve the customer include data
* set the node info
* ATTRIBUTES on CNTLR
* gr_dpr_phase_o TYPE REF TO cl_dpr_phase_o,
* gr_common TYPE REF TO if_dpr_common,
* gr_object_manager TYPE REF TO cl_dpr_appl_object_manager,
* gs_phase_int TYPE dpr_ts_phase_int.
DATA:
 l_ev_pro_type TYPE dpr_tv_pro_type,
 lr_common TYPE REF TO if_dpr_common,
 lv_raw_guid TYPE dpr_tv_guid,
 ls_phase_chg TYPE DPR_TS_phase_CHG,
 node_dpr_phase_ext TYPE REF TO if_wd_context_node,
 elem_dpr_phase_ext TYPE REF TO if_wd_context_element,
 stru_dpr_phase_ext TYPE if_componentcontroller=>element_dpr_phase_ext.
* set display or change mode
wd_this->on_set_change_mode( EXPORTING
 new_mode = is_cust_input_values-change_mode ).
*>>>>>>>>>>>>>>>> Get project details and store in Attr and CTX <<<<<<<<<<<<<<<<<START<
* Get instance of DPR object manager, is has running object details
wd_this->gr_object_manager = cl_dpr_appl_object_manager=>get_instance( ).
* set a guid from GUID we where given when custom WDC was called
lv_raw_guid = is_cust_input_values-guid . "the current PHASE GUID
TRY.
* Try to get object from application object mapper
 wd_this->gr_common =
 wd_this->gr_object_manager->mr_mapper->get_application_object_by_guid(
 lv_raw_guid ).
 CATCH cx_dpr_object_mapping_error.
ENDTRY.
ASSERT wd_this->gr_common IS BOUND. " bug.. must be fixed
* cast this object as a project, it msut be a project or we fail
wd_this->gr_dpr_phase_o ?= wd_this->gr_common.
ASSERT wd_this->gr_dpr_phase_o IS BOUND. " bug.. must be fixed
lv_raw_guid = IS_CUST_INPUT_VALUES-root_guid .
* now get the root DPR projecty obecjt
TRY.
* Try to get object from application object mapper
 lr_common =
 wd_this->gr_object_manager->mr_mapper->get_application_object_by_guid(
 lv_raw_guid ).
 CATCH cx_dpr_object_mapping_error.
ENDTRY.
ASSERT lr_common IS BOUND. " bug.. must be fixed
* get the project
* cast this object as a project, it msut be a project or we fail
wd_this->gr_dpr_project_o ?= lr_common.
ASSERT wd_this->gr_dpr_project_o IS BOUND. " bug.. must be fixed
* project category/type specific start up options
l_ev_pro_type = wd_this->get_pro_type( ).
CASE l_ev_pro_type.
 WHEN zcl_cp_proj_cat=>CO_OPWS_CM." OPWS Contract management .
 wd_this->start_cm( ).
 WHEN OTHERS.
ENDCASE.
* stick project on attr and in CTX, we need else where
* especially navigation to view
wd_this->gr_dpr_phase_o->get_data_ext(
 IMPORTING
 es_phase_chg = ls_phase_chg
 "ES_PROJECT_EXT = ES_PROJECT_EXT
 es_phase_int = wd_this->gs_phase_int ).
* locate our CTX node for holding extended PROJ fields
node_dpr_phase_ext = wd_context->get_child_node( name = if_componentcontroller=>wdctx_dpr_phase_ext ).
* get element via lead selection
elem_dpr_phase_ext = node_dpr_phase_ext->get_element( ).
* stru_dpr_phase
MOVE-CORRESPONDING ls_phase_chg-extended_attributes
 TO stru_dpr_phase_ext.
* set the full phase record
elem_dpr_phase_ext->set_static_attributes(
 static_attributes = stru_dpr_phase_ext ).
ENDMETHOD.
m
endmethod.
method UPDATE_DATA_FROM_BE .
DATA:
 ls_phase_chg TYPE DPR_TS_phase_CHG ,
 node_dpr_phase_EXT TYPE REF TO if_wd_context_node,
 elem_dpr_phase_EXT TYPE REF TO if_wd_context_element,
 stru_dpr_phase_ext TYPE if_componentcontroller=>element_dpr_phase_EXT.
* get proj from CTX
node_dpr_phase_ext = wd_context->get_child_node( name = if_componentcontroller=>wdctx_dpr_phase_ext ).
elem_dpr_phase_ext = node_dpr_phase_ext->get_element( ).
* we need to set the customer append structure here
elem_dpr_phase_ext->get_static_attributes( importing
 static_attributes = stru_dpr_phase_ext ).
* first get the full set of PROJECT DATA,
* since we do not want to change the normal defintion
* area, just the Attributes part.
wd_this->gR_DPR_phase_O->get_data_ext(
 IMPORTING
 ES_phase_CHG = lS_phase_CHG
* ES_PROJECT_EXT = ES_PROJECT_EXT
* ES_PROJECT_INT = ES_PROJECT_INT
* move our data over the custome extension
MOVE-CORRESPONDING stru_dpr_phase_ext
 to ls_phase_chg-extended_attributes.
TRY.
wd_this->gR_DPR_phase_O->set_data_ext(
 EXPORTING
 is_phase_chg = ls_phase_chg ).
 CATCH CX_DPR_OBJECT_UPDATE_ERROR .
 assert 1 = 0. "Set failed.
ENDTRY.
endmethod.
method WDDOINIT .
 DATA: lr_context TYPE REF TO if_wd_context.
* turn the change log on for context
lr_context = wd_context->get_context( ).
lr_context->enable_context_change_log( ).
endmethod.

Error Message in Enhancement of webdynpro

Hi,
I have a req in Webdynpro standard view to display error message when field have no value.
For this i have used enhancement and under that i am displaying error msg by
    CALL METHOD cl_dp_wd_msghdl=>report_message
      EXPORTING
        iv_message           = lv_message
       iv_show_as_popup     = ABAP_FALSE
        iv_cancel_navigation = 'X'" ABAP_TRUE
        io_api_controller    = lr_controller
        iv_message_type      = 'E'
io_fpm_msg_manager   =
               wd_comp_controller->mo_fpm->mo_message_manager.
but it is stoping there ?
saved the order with sucess message and error message both.
Please tel me the feasible soln

Hi Subramaniyan,
Proceed as follows on how to implement the Post document method.
1. Execute TCode SE24 and input the Object type as IF_EX_MB_MIGO_BADI and click on Display
2. Place the cursor on the method POST_DOCUMENT
3. Press F9 or follow the menu path GoTo->Documentation->To component
4. System will display the documentation relevant to POST_DOCUMENT and also there is a NOTE on message handling
5. Also regarding error handling execute SE24 and display the class CL_EXM_IM_MB_MIGO_BADI.
6. Place the cursor on the Method CHECK_ITEM and choose the menu path EDIT->Choose.
7. System will display the sample code.
Hope this helps you out. Reward accordingly.
Thanks and Regards,
Maddineni Bharath.

CProjects: Error when check in a big document (100 and more MB )

Hello,
when I try to check in a big document (in my case I made my own document which is about 100 MB) in cProjects the current cProject webpage turns to "This page could not be displayed...".
The exact path where I tried to check in the document is:
Projects -> Structure -> Documents -> New Document
To see if its an abap coding error I set a breakpoint at Web Dynpro Comp. "DPR_Document" View: "VI_UPLOADDETAIL" Method: "ONACTIONUPLOAD". Further I tried it in the Method "new_doc_create( )" of the component-controller.
The point is:
The abap coding which is called if you click on the "Check in"-button is NOT called if the document is about 100 or more MB. (I don't tried it with smaller documents e.g. 60 MB, but never mind about this because document with a size of 100 or more MB should work too.)
Furthermore I had a look at the trace file which can be found at SMICM -> Goto -> Trace File -> Display All. Every time I tried to check in such a big document three error messages appear there with the following content:
[Thr 1396738992] *** ERROR => request too big {00047108} [http_plg_mt.c 1969]
[Thr 1396738992] Address    Offset REQUEST:
[Thr 1396738992]
[Thr 1396738992] 0x4d78895c 000000 504f5354 202f7361 702f6263 2f776562 POST /sap/bc/web
[Thr 1396738992] 0x4d78896c 000016 64796e70 726f2f73 61702f63 70726f6a dynpro/sap/cproj
[Thr 1396738992] 0x4d78897c 000032 65637473 2f3f7361 702d636f 6e746578 ects/?sap-contex
[Thr 1396738992] 0x4d78898c 000048 7469643d 53494425 xxxxxxxx xxxx2533 tid=SID%xxxxxx%3
[Thr 1396738992] 0x4d78899c 000064 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxxxxxxxx%3
[Thr 1396738992] 0x4d7889ac 000080 6130314f 4e6d6551 61724445 767a6978 a01ONmeQarDEvzix
[Thr 1396738992] 0x4d7889bc 000096 525a7a45 48536763 58637863 76325738 RZzEHSgcXcxcv2W8
[Thr 1396738992] 0x4d7889cc 000112 45786f73 302d5835 6a2d4e45 57204854 Exos0-X5j-NEW HT
[Thr 1396738992] 0x4d7889dc 000128 54502f31 2e310d0a 61636365 70743a20 TP/1.1..accept:
[Thr 1396738992] 0x4d7889ec 000144 696d6167 652f6769 662c2069 6d616765 image/gif, image
[Thr 1396738992] 0x4d7889fc 000160 2f782d78 6269746d 61702c20 696d6167 /x-xbitmap, imag
[Thr 1396738992] 0x4d788a0c 000176 652f6a70 65672c20 696d6167 652f706a e/jpeg, image/pj
[Thr 1396738992] 0x4d788a1c 000192 7065672c 20617070 6c696361 74696f6e peg, application
[Thr 1396738992] 0x4d788a2c 000208 2f782d73 686f636b 77617665 2d666c61 /x-shockwave-fla
[Thr 1396738992] 0x4d788a3c 000224 73682c20 6170706c 69636174 696f6e2f sh, application/
[Thr 1396738992] 0x4d788a4c 000240 766e642e 6d732d65 7863656c 2c206170 vnd.ms-excel, ap
[Thr 1396738992]
[Thr 1398135728] Mon May 26 09:19:17 2008
[Thr 1398135728] *** ERROR => request too big {00087109} [http_plg_mt.c 1969]
[Thr 1398135728] Address    Offset REQUEST:
[Thr 1398135728]
[Thr 1398135728] 0x4d7688ec 000000 504f5354 202f7361 702f6263 2f776562 POST /sap/bc/web
[Thr 1398135728] 0x4d7688fc 000016 64796e70 726f2f73 61702f63 70726f6a dynpro/sap/cproj
[Thr 1398135728] 0x4d76890c 000032 65637473 2f3f7361 702d636f 6e746578 ects/?sap-contex
[Thr 1398135728] 0x4d76891c 000048 7469643d 53494425 xxxxxxxx xxxx2533 tid=SID%xxxxxx%3
[Thr 1398135728] 0x4d76892c 000064 xxxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxxxxxxxx%3
[Thr 1398135728] 0x4d76893c 000080 6130314f 4e6d6551 61724445 767a6978 a01ONmeQarDEvzix
[Thr 1398135728] 0x4d76894c 000096 525a7a45 48536763 58637863 76325738 RZzEHSgcXcxcv2W8
[Thr 1398135728] 0x4d76895c 000112 45786f73 302d5835 6a2d4e45 57204854 Exos0-X5j-NEW HT
[Thr 1398135728] 0x4d76896c 000128 54502f31 2e310d0a 61636365 70743a20 TP/1.1..accept:
[Thr 1398135728] 0x4d76897c 000144 2a2f2a0d 0a726566 65726572 3a206874 */*..referer: ht
[Thr 1398135728] 0x4d76898c 000160 74703a2f xxxxxxxx xxxxxxxx 7764662e tp://xxxxxx.wdf.
[Thr 1398135728] 0x4d76899c 000176 7361702e 636f7270 3a353030 36362f73 sap.corp:50066/s
[Thr 1398135728] 0x4d7689ac 000192 61702f62 632f7765 6264796e 70726f2f ap/bc/webdynpro/
[Thr 1398135728] 0x4d7689bc 000208 7361702f 6370726f 6a656374 732f3f73 sap/cprojects/?s
[Thr 1398135728] 0x4d7689cc 000224 61702d63 6f6e7465 78746964 3d534944 ap-contextid=SID
[Thr 1398135728] 0x4d7689dc 000240 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx %xxxxxx%xxxxxxxx
[Thr 1398135728]
[Thr 1395682224] Mon May 26 09:19:18 2008
[Thr 1395682224] *** ERROR => request too big {0008710c} [http_plg_mt.c 1969]
[Thr 1395682224] Address    Offset REQUEST:
[Thr 1395682224]
[Thr 1395682224] 0x4d7688ec 000000 504f5354 202f7361 702f6263 2f776562 POST /sap/bc/web
[Thr 1395682224] 0x4d7688fc 000016 64796e70 726f2f73 61702f63 70726f6a dynpro/sap/cproj
[Thr 1395682224] 0x4d76890c 000032 65637473 2f3f7361 702d636f 6e746578 ects/?sap-contex
[Thr 1395682224] 0x4d76891c 000048 7469643d 53494425 xxxxxxxx xxxx2533 tid=SID%xxxxxx%3
[Thr 1395682224] 0x4d76892c 000064 xxxxxxxx xxxxxxxx xxxxxxxx xxxx2533 xxxxxxxxxxxxxx%3
[Thr 1395682224] 0x4d76893c 000080 6130314f 4e6d6551 61724445 767a6978 a01ONmeQarDEvzix
[Thr 1395682224] 0x4d76894c 000096 525a7a45 48536763 58637863 76325738 RZzEHSgcXcxcv2W8
[Thr 1395682224] 0x4d76895c 000112 45786f73 302d5835 6a2d4e45 57204854 Exos0-X5j-NEW HT
[Thr 1395682224] 0x4d76896c 000128 54502f31 2e310d0a 61636365 70743a20 TP/1.1..accept:
[Thr 1395682224] 0x4d76897c 000144 2a2f2a0d 0a726566 65726572 3a206874 */*..referer: ht
[Thr 1395682224] 0x4d76898c 000160 74703a2f 2fxxxxxx xxxxxxxx xxxx662e tp://xxxxxx.wdf.
[Thr 1395682224] 0x4d76899c 000176 7361702e 636f7270 3a353030 36362f73 sap.corp:50066/s
[Thr 1395682224] 0x4d7689ac 000192 61702f62 632f7765 6264796e 70726f2f ap/bc/webdynpro/
[Thr 1395682224] 0x4d7689bc 000208 7361702f 6370726f 6a656374 732f3f73 sap/cprojects/?s
[Thr 1395682224] 0x4d7689cc 000224 61702d63 6f6e7465 78746964 3d534944 ap-contextid=SID
[Thr 1395682224] 0x4d7689dc 000240 2533xxxx xxxxxxxx 33xxxxxx xxxxxxxx %xxxxxx%3xxxxxxx
[Thr 1395682224]
As you can see this error sais that the request is too big. A look into the coding of this cProjects webpage (where you can check in documents (look above)) the document is sent with the http method POST. Usually every webserver has an option where you can restrict the size for uploading files. But in that case the won't be an error out of a piece of c-coding (-> http_plg_mt.c).
Has anybody have an idea about a solution?
Edited by: Johannes Gilbert on May 26, 2008 12:25 PM

Hi,
this is handled by the profile parameters of the R/3 System. Look at
icm/HTTP/max_request_size_KB or something like this.
Best regards, Stefan

Webdynpro enhancements

Hi experts,
I need to an enhancement in webdynpro.
i find out the component and know how to create a enhancement implemention.
But , my requirement is -- an error message should come when i click on a button (delete) in my screen.
i find out there is a method called "OnActionDelete" .. but how to write this code ...
thanks
sekhar

Hi Chandra Sekhar,
You can write in the OnAction delete Event Handler method.
Are you trying to display a pop up message or a normal message. Please let me know.
You can use the method create_pop_up_to_confirm of if_wd_window_manager. or
use report_t100_message.
Thank You,
Sai

Cproject error

Hi gurus,
After making some user setting in Cproject,
throwing error..
im unable to access Cproject
does anyone has any clue on this?
Error when processing your request
What has happened?
The URL http://#######.#####n.c#m:8##0/sap/bc/webdynpro/sap/cprojects/ was not called due to an error.
Note
The following error text was processed in the system PLD : Property GROUP_AGGREGATION with the value X is not allowed for key figure (PRIORITY) ⎌䅏　 ܀
The error occurred on the application server ######_PLD_20 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: ON_CHANGED_FIELD_SETTINGS of program CL_SALV_WD_CHECK_TABLE========CP
Method: ON_CHANGED of program CL_SALV_WD_CHECK_TABLE========CP
Method: IF_SALV_WD_CONFIG~ON_CHANGED of program CL_SALV_WD_A_MODEL_ITEM=======CP
Method: IF_SALV_WD_SORT~SET_GROUP_AGGREGATION_ALLOWED of program CL_SALV_WD_FIELD==============CP
Method: MAP_TO_MODEL_FIELD_SETTINGS of program CL_SALV_WD_PERSISTENCE========CP
Method: MAP_TO_MODEL of program CL_SALV_WD_PERSISTENCE========CP
Method: IF_SALV_WD_COMP_TABLE_PERS~LOAD of program CL_SALV_WD_C_TABLE============CP
Method: IF_SALV_WD_COMP_TABLE_PERS~GET_CONFIG_DATA of program CL_SALV_WD_C_TABLE============CP
Method: GET_CONFIG_DATA of program /1BCWDY/2AC75WRSMR9UQ8CMFUKH==CP
Method: IWCI_SALV_WD_TABLE~GET_CONFIG_DATA of program /1BCWDY/2AC75WRSMR9UQ8CMFUKH==CP
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system ##D in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server ######v_P##_20 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server ########_P##_20 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
thanks
Niranjan

Dear Vivek,
im not exactly sur eits b'coz of wat?
i did some changes in User settings >>
and one more thing
i changed Dashboard settings >> display
and it started throwing error
now i can not even logon to Cproject...
is there nay way to reset dashboard setting and or user settings
Niranjan

Runtime error in extractor enhancement

Hi,
I need to enhance the extractor 0WBS_ELEMT_ATTR with an additional field. The field is a Z field from the table PRPS.
Now PRPS is a base table for the extractor for this extractor, so simply adding this field into the append structure should suffice.
However, when I do this the extractor gives the following runtime error:
Syntax error in program "SAPLPSBW "
Component called ZZSO already exists.
The error is in the function call "e_fname".
I have found that the same Z field is used in another structure CNCI_PRPS. Could this be leading to the error?
Please let me know if any of you have any insights as to why this problem might be occurring.
TIA,
Amrita

Hi,
In my case the problem was caused because the same ZZ Field was used in two structures.
One for ECC and one for BI. This was causing some interference.
To solve this I changed the field name in my extract structure to ZZZSO and populated it via a CMOD routine.
Hope this helps.
Amrita

Display custom error message in enhancement spots

Hi all,
Is there someone here who've encountered having the need to display custom error message in an enhancement spot? Could you help me please.. I can't find any reference from the net.
Thanks in advance
Regards,
Aris

Hi,
The error message can be only displayed in enhancement spots based on thr program flow.
You have to determine where its getting called for ex: in PBO or PAI etc.....
You have to find the right place to display the error messages . for ex: using a memory id ......

Error opening Webdynpro view of NWDS 7.3

I just installed NWDS 7.3 patch 1. Installed JDK 1.6.0_07. NWDS is having problem showing Webdynpro view. When i open the webdynpro view and drag a UI control all i get is the below screen.
In the error log i get the below error message. I was able to compile and deploy the DC, but having problem see the webdynpro view in the Studio. Please help on what need to be done. I tried this on Windows XP and Windows 7 , and ran into the exact same issue.
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NoClassDefFoundError: com/sap/security/core/server/csi/XSSEncoder)
    at org.eclipse.swt.SWT.error(SWT.java:3884)
    at org.eclipse.swt.SWT.error(SWT.java:3799)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3885)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3506)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
Caused by: java.lang.NoClassDefFoundError: com/sap/security/core/server/csi/XSSEncoder
    at com.sap.tc.ls.renderer.base.AbstractRenderer.writeXmlEscaped(AbstractRenderer.java:1168)
    at com.sap.tc.ls.renderer.base.AbstractRenderer.writeXmlEscaped(AbstractRenderer.java:1118)
    at com.sap.tc.ls.renderer.base.AbstractRenderer.writeXmlEscaped(AbstractRenderer.java:1098)
    at com.sap.tc.ls.renderer.ie6.LSPageHeaderRenderer.renderPageHeaderFragment(LSPageHeaderRenderer.java:843)
    at com.sap.tc.ls.renderer.ie6.LSPageHeaderRenderer.render(LSPageHeaderRenderer.java:290)
    at com.sap.tc.ls.renderer.base.BaseRenderManager.render(BaseRenderManager.java:944)
    at com.sap.tc.webdynpro.clientimpl.designtime.LightspeedDesigntimeClient$RenderManager.render(LightspeedDesigntimeClient.java:48)
    at com.sap.tc.ls.renderer.ie6.LSFlowLayoutRenderer.renderFlowLayoutItemFragment(LSFlowLayoutRenderer.java:878)
    at com.sap.tc.ls.renderer.ie6.LSFlowLayoutRenderer.renderFlowLayoutFragment(LSFlowLayoutRenderer.java:812)
    at com.sap.tc.ls.renderer.ie6.LSFlowLayoutRenderer.render(LSFlowLayoutRenderer.java:252)
    at com.sap.tc.ls.renderer.base.BaseRenderManager.render(BaseRenderManager.java:944)
    at com.sap.tc.webdynpro.clientimpl.designtime.LightspeedDesigntimeClient$RenderManager.render(LightspeedDesigntimeClient.java:48)
    at com.sap.tc.ls.renderer.ie6.LSScrollContainerRenderer.renderScrollArea_RenderContent(LSScrollContainerRenderer.java:1574)
    at com.sap.tc.ls.renderer.ie6.LSScrollContainerRenderer.renderScrollAreaInnerFragment(LSScrollContainerRenderer.java:1456)
    at com.sap.tc.ls.renderer.ie6.LSScrollContainerRenderer.renderScrollContainerFragment(LSScrollContainerRenderer.java:984)
    at com.sap.tc.ls.renderer.ie6.LSScrollContainerRenderer.render(LSScrollContainerRenderer.java:358)
    at com.sap.tc.ls.renderer.base.BaseRenderManager.render(BaseRenderManager.java:944)
    at com.sap.tc.webdynpro.clientimpl.designtime.LightspeedDesigntimeClient$RenderManager.render(LightspeedDesigntimeClient.java:48)
    at com.sap.tc.webdynpro.clientimpl.designtime.LightspeedDesigntimeClient$1.run(LightspeedDesigntimeClient.java:158)
    at com.sap.ide.mmservices.core.general.MetamodelService.runWithCache(MetamodelService.java:53)
    at com.sap.tc.webdynpro.clientimpl.designtime.LightspeedDesigntimeClient.render(LightspeedDesigntimeClient.java:149)
    at com.sap.ide.webdynpro.viewdesigner.ur.RenderingService.renderDelta(RenderingService.java:462)
    at com.sap.ide.webdynpro.viewdesigner.ViewDesignerPart.renderDelta(ViewDesignerPart.java:2018)
    at com.sap.ide.webdynpro.viewdesigner.ViewDesignerPart.access$900(ViewDesignerPart.java:197)
    at com.sap.ide.webdynpro.viewdesigner.ViewDesignerPart$ViewChangedListener$1.run(ViewDesignerPart.java:2695)
    at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
    ... 22 more

Hi ,
I think your Jdk is not compatible with the NWDS version so please change it to 32 bit JDK and try.
I think this will sure work .
Thanks & Regards,
Meghal Shah

Error in webdynpro application

Dear gurus.
Im getting following error how to rectify it ?
we don't have Basis guy so im also doing the basis stuff and im new in it .
Error when processing your request
What has happened?
The URL http://sapr3dq:8000/sap/bc/webdynpro/sap/zsaptechnical_demo was not called due to an error.
Note
The following error text was processed in the system R3D : Die URL enthält keine vollständige Domainangabe (sapr3dq statt sapr3dq.<domain>.<ext>).
The error occurred on the application server sapr3dq_R3D_00 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: CHECK of program CX_FQDN=======================CP
Method: LATE_CONSTRUCTOR of program CL_WDR_UCF====================CP
Method: HANDLE_REQUEST of program CL_WDR_UCF====================CP
Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP
Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system R3D in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server sapr3dq_R3D_00 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server sapr3dq_R3D_00 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 100 -u: ABAPDEV -l: E -s: R3D -i: sapr3dq_R3D_00 -w: 0 -d: 20100225 -t: 140212 -v: RABAX_STATE -e: UNCAUGHT_EXCEPTION
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team

|Error analysis |
| An exception occurred which is explained in detail below. |
| The exception, which is assigned to class 'CX_FQDN', was not caught and |
| therefore caused a runtime error. |
| The reason for the exception is: |
| Die URL enthält keine vollständige Domainangabe (sapr3dq statt |
| sapr3dq.<domain>.<ext>). |
| |
|Information on where terminated |
| Termination occurred in the ABAP program "CX_FQDN=======================CP" - |
| in "CHECK". |
| The main program was "SAPMHTTP ". |
| |
| In the source code you have the termination point in line 10 |
| of the (Include) program "CX_FQDN=======================CM002". |

Error in WebDynpro with WebServices

Hi all,
Im getting some errors using applications deployed in WEB AS SP9 that runs as a WebDynpro IView in EP.
Running the application as standalone (out of EP) this works fine.
NetWeaver Developer Studio 2.0.9
WebDynpro application using WebServices that access Oracle 8i database in the follow sequence:
WebServices -> Session Bean stateless -> Entity Bean CMP (manage connections; generate sql code, etc.)
In WebDynpro application we import WebService Model by the follow sequence:
New Model - Import Web Service Model - Local Server for WSDL Source - <WebService deployed>
In each WebServices we have created these methods:
findByID(ID);
getAll();
insert(parameters);
remove(ID);
update(parameters);
We guess that the error is generated in Entity Bean because all WebServices generate these errors.
Error 1 - Application with WebServices Model
Error stacktrace:
com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Repository Object br.com.xxx.fluxo.Fluxo/ComponentInterface:FluxoInterface/InterfaceViews:CadastroSituacaoFluxoInterfaceView/InboundPlugs:Default associated via relation RepositoryObjectRelation(br.com.xxx.fluxo.application.CadastroSituacaoFluxoApp, StartupPlug) does not exist.
 at com.sap.tc.webdynpro.repository.RelationToOne.resolveTargets(RelationToOne.java:124)
 at com.sap.tc.webdynpro.repository.RelationToOne.mergeTargets(RelationToOne.java:108)
 at com.sap.tc.webdynpro.repository.RelationToOne.mergeTargets(RelationToOne.java:72)
 at com.sap.tc.webdynpro.repository.RelationToOne.getTarget(RelationToOne.java:174)
 at com.sap.tc.webdynpro.repository.RepositoryObject.getRelatedModelObject(RepositoryObject.java:349)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getStartupPlugInternal(IWDApplicationInfo.java:319)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:355)
 at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
 at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
-- end --
Error 2 - Application with WebServices Model
An error has occurred:
"Failed to process the request."
Please contact your system administrator.
Hide details
Web Dynpro client:
HTML Client
Web Dynpro client capabilities:
User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
Web Dynpro runtime:
Vendor: SAP, Build ID: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-19:21:48:59[UTC], changelist=290362, host=PWDFM026)
Web Dynpro code generators of DC local/Apontamentos:
SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:31:53[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:36:19[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:00[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:54:34[UTC], changelist=290362, host=PWDFM026)
SapWebDynproGenerationCTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:54:34[UTC], changelist=290362, host=PWDFM026)
SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:25:03[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:01[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:29:01[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:11[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:33[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates: (unknown)
Web Dynpro code generators of DC sap.com/tcwddispwda:
No information available
Web Dynpro code generators of DC sap.com/tcwdcorecomp:
No information available
J2EE Engine:
6.40 patchlevel 87037.313
Java VM:
Java HotSpot(TM) Server VM, version: 1.4.2_06-b03, vendor: Sun Microsystems Inc.
Operating system:
Windows 2000, version: 5.0, architecture: x86
Error stacktrace:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Did not find repository information for controller NotProductiveEventController
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.createCustomController(DelegatingComponent.java:55)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:428)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:371)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:400)
 at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:138)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:746)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
 at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
 at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:374)
 at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
 at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Error 3 - Application with RFC Model
An error has occurred:
"Failed to process the request."
Please contact your system administrator.
Hide details
Web Dynpro client:
HTML Client
Web Dynpro client capabilities:
User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
Web Dynpro runtime:
Vendor: SAP, Build ID: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-19:21:48:59[UTC], changelist=290362, host=PWDFM026)
Web Dynpro code generators of DC local/Apontamentos:
SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:31:53[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:36:19[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:00[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:54:34[UTC], changelist=290362, host=PWDFM026)
SapWebDynproGenerationCTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:54:34[UTC], changelist=290362, host=PWDFM026)
SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:25:03[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:01[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:29:01[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:11[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:33[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates: (unknown)
Web Dynpro code generators of DC sap.com/tcwddispwda:
No information available
Web Dynpro code generators of DC sap.com/tcwdcorecomp:
No information available
J2EE Engine:
6.40 patchlevel 87037.313
Java VM:
Java HotSpot(TM) Server VM, version: 1.4.2_06-b03, vendor: Sun Microsystems Inc.
Operating system:
Windows 2000, version: 5.0, architecture: x86
Error stacktrace:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Did not find repository information for controller ZMANPP012Controller
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.createCustomController(DelegatingComponent.java:55)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:428)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:371)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:400)
 at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:138)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:746)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
 at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
 at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:374)
 at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
 at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)

Hi,
I feel this error is nothing to do with webservice model.
Please check your application properties like startupPlug,Interface View etc. Set the properties correctly and deploy once again.
Regards, VIP

CProjects:Error in webdynpro enhancement

Similar Messages

Maybe you are looking for