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: 

Dynamic ALV gives Runtime Error only in Background

Former Member
0 Kudos

Hi,

This is a Custom Development (Z*), wherein I build the field catalog and output table dynamically and populate the output table using field symbols assignment.  It works perfectly all right in foreground. Due to the huge volume of records, there is a demand from client to create the ALV output as a spool in background job. But to a great disappointment, the job gets cancelled and it gives run time error in background. The ST22 looks below. If there are any issue with field catalog or output data table, then it supposed to give error in the foreground as well.  But it gives error only in background and I am not sure whether it is because of the dynamically build field catalog and output table. I am not able to figure out the issue and It is driving me crazy as I am struggling for the past 2 days. Please help me with a suitable solution. I use FM: REUSE_ALV_GRID_DISPLAY.

Appreciate all your help in advance.

*-----------------------------------------------------------------------------------------------------------------------------*

Runtime Errors         GETWA_NOT_ASSIGNED

Date and Time          03/07/2013 16:36:46

Short text

     Field symbol has not yet been assigned.

What happened?

     Error in the ABAP Application Program

     The current ABAP program "SAPLKKBL" 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 "-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.

*---------------------------------------------------------------------------------------------------------*

7 REPLIES 7

Former Member
0 Kudos

Could you please paste the portion of the code where this error is coming?

gouravkumar64
Active Contributor
0 Kudos

Hi,

In this type of error,always check consistency check in Alv.

try to debug ur program.

Check field catalog,spelling,capital letters present or not.

Check ALV container ,empty or not.

At last check sap notes 926446-it may helps.

check sap help

http://help.sap.com/saphelp_470/helpdata//EN/d6/23253963143e6ae10000000a11402f/frameset.htm

Hope it will helps.

Thanks

Gourav.

0 Kudos

Thanks Gourav. It was a dynimically build field catelog and there was an error with currency fields. It is fixed and works now. Thank you very mcuh for your help.

0 Kudos

Hi,

Then, Close this thread & mark it as answered.

Thanks

Gourav.

I had this exact problem. The ALV ran fine in foreground mode but gave the above error in background mode. I ran a consistency check and it showed me the exact spot where the issue was. In my case I typed one of my field names incorrectly when defining fieldcatalog.

To run inconsistency check, I ran my program in FOREGROUND mode first. When the output showed up on screen I scrolled to the right of my output fields where there was some blank area, held down the SHIFT key on my keyboard and DOUBLE RIGHT-CLICKED (not left click). The consistency check ran and showed me the incorrect field name in my fieldcatalog.

Former Member
0 Kudos

Hi,

Generally, you will get this kind of dump when there is problem with wrong data type assignment and also unassigned  field symbols.

And also you check your GUISTATUS, if you copied the standard application tool bar, you should call it to your custom program.

Thanks.

Pavan.

0 Kudos

Thanks Pavan. It was a dynimically build field catelog and there was an error with currency fields. It is fixed and works now. Thank you very mcuh for your help.