cancel
Showing results for 
Search instead for 
Did you mean: 

GETWA_NOT_ASSIGNED

Former Member
0 Kudos

Hi, all.

I have some problem.

Infosource 0G_CWWREP_TXT was well run before.

But, suddenly. The infosource 0G_CWWREP_TXT was not running.

Error list's bellow.

Could you give me a some Guide?

-


Runtime Errors GETWA_NOT_ASSIGNED

What happened?

Error in the ABAP Application Program

The current ABAP program "CL_RSDMD_UPDATE_MASTER_DATA===CP" had to be

terminated because it has

come across a statement that unfortunately cannot be executed.

Error analysis

You attempted to access an unassigned field symbol

(data segment 32787).

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.

Trigger Location of Runtime Error

Program CL_RSDMD_UPDATE_MASTER_DATA===CP

Include CL_RSDMD_UPDATE_MASTER_DATA===CM00E

Row 87

Module type (METHOD)

Module Name UPDATETEXTS_KERNL_T

-


Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

It's resolved.^-.

Former Member
0 Kudos

Hi,

Could u know me how u solved it, plz.

I'm also facing same problem in Tcode fagl_fc_val, when I click on configure button. I gets error GETWA_NOT_ASSIGN

Error line is discribe table <gt_iem_list> lines sy-tfill.

what is probelm.. its a SAP standart program then y error or dump coming.. pls help me to solve it.

Regards

Waqkas

Former Member
0 Kudos

Hi.

I was met that problem in BW.

Perhaps, You mention that is R3.

I has solving following process.

(It's SAP OSS guide message.

By Kitty Liang

Support Consultant - BW

SAP Active Global Support China)

-


The problem is most likely due to an inconsistency in the infoobject,

perhaps during activation.

In order to solve this problem, you should do the following:

1) Go to transaction RSD1

2) make a "dummy" change to the infoobject 0G_CWWREP, for example, by

adding a "." to the long description of the infoobject

3) save this change and activate the infoobject.

4) now change the text back to original text

5) save this change and activate the infoobject again

6) now reactivate the transfer rules for this

7) now try the load again

-


Hope I could help you.

Thanks.