Skip to Content
0
Apr 07, 2016 at 03:10 PM

ITSM : Dump in Category Modeler

77 Views

Dear Experts,

I have just finished setting up a new client in solution manager and I am trying to create a new categorization schema in that new client. While assigning a new Application area, as soon as select the Application ID as "Service Request/Incident" and Parameter as "Transaction type/Catalog category", I get a dump message stating

500 SAP Internal Server Error

Error: Field symbol has not yet been assigned.

It also registers a GETWA_NOT_ASSIGNED dump in ST22.

Category ABAP Programming Error
Runtime Errors GETWA_NOT_ASSIGNED
ABAP Program CL_CRM_CATEGO_GENIL===========CP
Application Component CRM
Date and Time 07.04.2016 22:52:21


Short text Field symbol has not yet been assigned.


What happened? Error in the ABAP Application Program The current ABAP program "CL_CRM_CATEGO_GENIL===========CP" had to be terminated because it has come across a statement that unfortunately cannot be executed.


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 You attempted to access an unassigned field symbol (data segment "-1"). This error may occur if - You address a typed field symbol before it has been set with ASSIGN - You address a field symbol that pointed to the line of an internal table that was deleted - You address a field symbol that was previously reset using UNASSIGN or that pointed to a local field that no longer exists - You address a global function interface, although the respective function module is not active - that is, is not in the list of active calls. The list of active calls can be taken from this short dump.

Could you help me overcome this error to proceed further?

Also, for your information, category modeler works in the existing client without any issues and this problem is occurring only in the new client that is recently built.

Thanks,

Dinesh