Application Development and Automation 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: 
Read only

Runtime Error only in Background Job - Dynamically Created ALV Layout

Former Member
0 Likes
1,122

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.

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

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.

3 REPLIES 3
Read only

Former Member
0 Likes
646

Hi,

This type of runtime error will come mainly because of the Filedcatalog.

means while creating fieldcatalog you have to take care of some points like

1.Field name shoud be in capitol letters.

2.that perticular field should exist in the internal table what you are specifying in the fieldcatalog.

3.If you are working in the ECC6 while declaring the field catalog for Quantity and currency fields you have to give the refernce.

The above are the some of the situations you will get this type of runtime error.Check the above points and reschedule the job again.

Thanks

Mani

Read only

0 Likes
646

Hi Mani. Yes. it is a currency field error in dynamically build field catelog. I have fixed. Thanks for your help.

Read only

0 Likes
646

Thanks, Works for me.