Customer defined mass changes on contracts

[Former Member]

Hi,

Anybody having succes in following the instructions to define a new

mass change on SRM contracts.

http://help.sap.com/saphelp_srm70/helpdata/en/8d/3a9442bf2d1031e10000000a1550b0/frameset.htm

I am stuck when implmenting the BADI method CTR_DEFINE_UI:

data: ls_params type ihttpnvp,

lt_params type tihttpnvp.

ls_params-name = /sapsrm/if_pdo_ctr_mc_c=>gc_abap_wd_component .

ls_params-value = 'ZWDC_CTR_MASS_UPD_START'.

append ls_params to lt_params.

clear ls_params.

ls_params-name = /sapsrm/if_pdo_ctr_mc_c=>gc_abap_wd_view .

ls_params-value = 'ZWDC_CTR_MASS_START'.

append ls_params to lt_params.

clear ls_params.

ls_params-name = /sapsrm/if_pdo_ctr_mc_c=>gc_abap_wd_plug.

ls_params-value = 'I_V_PROD_START'.

append ls_params to lt_params.

et_params = lt_params.

ev_ttype_name = 'ZREGH_T_PDO_CTR_PRD_START'.

Here you name your component, view and plug. All 3 are defined, but i get a short dump:

-

---

Runtime Errors UNCAUGHT_EXCEPTION

Exception CX_WDR_RR_EXCEPTION

Date and Time 26.04.2011 09:28:17

What happened?

The exception 'CX_WDR_RR_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 'SAPLWDR_RUNTIME_REPOSITORY'

has to be

terminated.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

An exception occurred which is explained in detail below.

The exception, which is assigned to class 'CX_WDR_RR_EXCEPTION', was not caught

and

therefore caused a runtime error.

The reason for the exception is:

View I_V_PROD_START does not exist within the component ZWDC_CTR_MASS_UPD_START

-

---

The plug and the view seems to be mixed up. It thinks that the name of

the plug is the view. Found the following coding i SAP Standard:

Method ONACTIONSELECT_ROW_ITEM in the view V_AO_CTRM_MAIN,line 185:

l_view_controller_api->prepare_dynamic_navigation(

source_window_name = lc_window_name

source_vusage_name = lc_vusage_name

source_plug_name = lc_oplug_name

target_component_name = lv_component_name

target_component_usage = lc_comp_usg

target_view_name = lv_plug_name <----

---

target_plug_name = lc_plug_name

target_embedding_position = lc_embed_posn ).

Here the plug name is given as parameter to the view. Anyone having

experience/problems in this area.

[Former Member · Accepted solution]

got official answer fra SAP by Customer Message.

The View has to delivered as a plug. By Coding this means:

ls_params-name = /sapsrm/if_pdo_ctr_mc_c=>gc_abap_wd_plug.

ls_params-value = 'I_V_PROD_START'.

append ls_params to lt_params.

has to change to

ls_params-name = /sapsrm/if_pdo_ctr_mc_c=>gc_abap_wd_plug.

ls_params-value = 'ZWDC_CTR_MASS_START'.

append ls_params to lt_params.

Found i am not the first to be confused by this:

[preeti_negi · Accepted solution]

Hello Martin Molz,

I have worked on these issues for various customers and have also tested this in internal SAP

systems

The parameter you need to pass is window name that you have to copy from your wd component

eg class 'ZCL_CTR_HEADER_MASS_CHANGE' method:

/SAPSRM/IF_EX_CTR_MASS_BADI~CTR_DEFINE_UI,

i.e. ls_params-value = 'I_V_PURCH_DATA' with:-

ls_params-value = 'ZWDC_UI_AO_CT_MC_HDR'.

( The parameter you are passing is inbound plug, which is wrong and you

need to pass window name ZWDC_UI_AO_CT_MC_HDR instead ).

This will definitely solve the dump and functionality will work.

Best Regards,

Preeti