Dump when selecting SoS after adding new column in SoS tab in SRM7.0 SC

[ramakrishna_vishnubhatla]

Hi Experts,

We are using Classic Scenario with ECC6.04.

We added 2 extra column ( Plant & Sto Loc) in the Source of Supply Tab in the SRM Shopping Cart.

I added these fields in webdynpro/SAPSRM/WDC_DODC_SC_I_SOS in the view V_DODC_SC_I_SOS

Appended these two field in the structure /SAPSRM/S_PDO_APP_SOS_VEN and added the logic to get plant and storage location

in WDDOINIT method.

When system proposes any B/E SoS ( Contract or PIR) it shows value of Plant or Sto Location from respective SoS in the respective Column correctly.

But when we select any Contract or PIR row other than 1st , then system throws below dump

100209

sgsgsav0s2003

https://sgsgsav0s2003.ad.internal:44300/sap/bc/webdynpro/sapsrm/wda_l_fpm_oif

GETWA_NOT_ASSIGNED

Field symbol has not yet been assigned.

Method: UPDATE_META_DATA of program /SAPSRM/CL_CH_WD_MAP_META_HDLRCP

Method: /SAPSRM/IF_CLL_DODM_SC_I_SOS~LEAD_SELECTION of program /SAPSRM/CL_CH_WD_DODM_SC_I_SOSCP

Method: ONACTIONLEAD_SELECTION of program /1BCWDY/T2R7E4WKA5D7C8DML3PR==CP

Method: ONACTIONLEAD_SELECTION of program /1BCWDY/T2R7E4WKA5D7C8DML3PR==CP

Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/T2R7E4WKA5D7C8DML3PR==CP

Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_VIEW========CP

Method: IF_WDR_ACTION~FIRE of program CL_WDR_ACTION=================CP

Method: DO_HANDLE_ACTION_EVENT of program CL_WDR_WINDOW_PHASE_MODEL=====CP

Method: PROCESS_REQUEST of program CL_WDR_WINDOW_PHASE_MODEL=====CP

Method: PROCESS_REQUEST of program CL_WDR_WINDOW=================CP

Please suggest the solution whether I am missing anything .

Thanks and Regards,

Rama.

[former_member806541]

Can you please let us know how did you resolve it?

[christian_zeuch]

Dear Rama

This error usally happens when you call an ITS transaction through SRM portal using SRM 7.0, which is based on Web Dynpro. This is a common error regarding customer fields and upgrade from SRM 5.0 to SRM 7.0.

It can also be a role issue. For example, the user that is getting the dump has an old role (SRM 5.0) assigned to him instead of a new role (SRM 7.0).

I hope this helps.

Best regards,

Christian Zeuch