SM37 - GETWA_NOT_ASSIGNED

[HKany]

Hello everybody,

I guess I found a new bug concerning GETWA_NOT_ASSIGNED, because I have searched the SDN, OSS and the WWW for about 2 hours and couldn't find the solution. Please let me know when there is a solution (its a customer problem).

Error occurs in SM37 when job is running (every hour).

Runtime Errors GETWA_NOT_ASSIGNED

Field symbol has not yet been assigned

SAP Release.............. "640"

Information on where terminated

The termination occurred in the ABAP program "SAPLSF4E" in

"DD_EXTIDX_LOG_TO_INDX".

The main program was "DD_F4_START_INDX ".

The termination occurred in line 56 of the source code of the (Include)

program "LSF4EU19"

of the source code of program "LSF4EU19" (when calling the editor 560).

The program "SAPLSF4E" was started as a background job.

44 * The table index-ddixspras must contain at least one (dummy)

45 * language.

46 IF index-ddidxspras[] IS INITIAL.

47 RAISE internal_error.

48 ENDIF.

49

50 if index-mandtindep is initial.

51 * Index ist mandantenabhängig

52 keyfield_tab = index-ddkeymap_t[].

53 sort keyfield_tab by lposition.

54 read table keyfield_tab assigning .

58 endif.

59

[Former Member]

Hi,

Search for any SAP notes on service.sap.com

Hopefully there may be some notes...

[matt]

Look at Note 862548 - GETWA_NOT_ASSIGNED Dump in cvse_customizing.

Otherwise, as this is happening with standard SAP, raise a message with SAP to fix it.

matt

[Former Member]

Hi,

You can raise this issue with SAP...Because this is purely an upgrade error. The similar dump I have got twice in an upgrade project.

That dump was in the standard program which you have mentioned in your problem.

Regards,

Cooldeep.

[HKany]

solved.

problem was that since the job was installed, release changes brought 2 new parameter, who wasn't there before. so the 2 new need parameter were never filled. and then it crashed.