Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Issue with S_TABU_LIN

Former Member
0 Kudos

Hi,

I have implemented S_TABU_LIN object with Z Organisational level ( region specifc) to restrict access to few z tables at line item level.

Usually before implementing S_tabu_lin , during execution of Z transactions a pop up used to come to select the region. now after implementing S_TABU_LIN the region values are picked up from this object and values specifc to the region are displayed without the popup anymore.

its working for most of the transactions, but we are facing a issue with one transaction, the region is picked up from the S_tabu_lin object but sitill the popup comes and when we click on F4 for help its throwing the below dump

Runtime Errors GETWA_NOT_ASSIGNED

Date and Time 07.07.2011 23:06:46

Short text

Field symbol has not yet been assigned.

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLSVIX" 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 32773).

This error may occur if

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.

w to correct the error

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"GETWA_NOT_ASSIGNED" " "

"SAPLSVIX" or "LSVIXHXX"

"CALLBACK_F4"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

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.

w to correct the error

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"GETWA_NOT_ASSIGNED" " "

"SAPLSVIX" or "LSVIXHXX"

"CALLBACK_F4"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

Also the issue is faced by users who are having access to S_tabu_lin implemented roles. other users are able to execute the transaction with out any dump.

If any one of you has faced a similar issue, please help me in resolving this issue.

Thanks,

Sanketh.

1 REPLY 1

Former Member
0 Kudos

Hi Sanketh,

This issue occurs if there are any inconsistencies with the Function modules (FM) used in the program that was associated to the custom transaction code. Please check with the ABAPer to identify the root cause, since it is not an issue related to Security.

They will be able to quickly help you out with the solution.

Regards,

Raghu