08-22-2013 5:01 PM
Hi Team,
Category ABAP Programming Error
GETWA_NOT_ASSIGNED
ABAP Program SAPLKKBL, LKKBLF99
We found one SAP NOTE Note 1783865 - DBACockpit: Dump GETWA_NOT_ASSIGNED in segments (aggregated)
But basis team reverted back saying this SAP Note is valid for the DBA Cockpit on Oracle.
The note mentioned above is not applicable in the present scenario as we are running on DB2 presently.
Team any Solution or help ???
Regards,
Rahul
08-22-2013 9:01 PM
What are u trying to do ? The SAP program SAPLKKBL is regarding output reports. Are you trying to write an ALV ? Could you please paste your code here ? Maybe the fieldcat table is not filled correctly.
08-23-2013 11:34 AM
Hi Arthur.
We have a custom report which when executed displays a standard ALV output.
When we execute it
It runs without any dump.
Now if we deselect the Requisition of Po from column set as shown below.
Now we encounter a dump.
Also if we try to add other columns to the column set keeping Requisition of PO in the column set it doesnot give dump but in case we add any column but exclude Requisition of PO it gives up dump.
Regards,
Rahul
We are executing this for Downloading spreadsheet as local file.
08-23-2013 1:08 PM
It looks like the fieldcat definition of Requisitioner of PO is not correct. When you change the layout, the report automatically regenerate the ALV with all fields selected. The error shown by the compiler says that was not possible to assign the field of your internal table with the fieldname passed by fieldcat table.
E.g.:
CLEAR t_fieldcat.
t_fieldcat-fieldname = 'AFNAM' . << " check in your code
" this point, if the
" name definition is
" the same in your
" output table
t_fieldcat-tabname = 'OUTPUT_TABLE .
t_fieldcat-reptext_ddic = 'your text here' .
t_fieldcat-inttype = 'C' .
t_fieldcat-outputlen = 12 .
APPEND t_fieldcat.
09-10-2013 8:02 AM
Runtime error GETWA_NOT_ASSIGNED is thrown if there are any mismatches between the field properties being passed to field catalogue and output table.
Pass the field names and other field attributes in field catalogue same as declared in output table and make sure it is in upper case.
09-08-2013 12:01 PM
Can you please share your Field Catalog... specifically Requestion No.
Regards,
Venkat
09-09-2013 12:10 PM
As you are able to display the ALV grid, execute the Consistency Check, that will display in-consistency errors between the internal table fields names and content of structures like the field catalog or the layout.
One of most frequent beginner's error is the affectation of the BOX field to the internal table (often after copy of other's sources), also when you change a structure in development, use report BALVBUFDEL to reset ALV buffers.
Regards,
Raymond
09-12-2013 2:18 PM
You know that this check will execute in some seconds only, and that you should have now already solved the problem
09-10-2013 7:52 AM
Hi Rahul,
The error 'Field symbol has not yet been assigned' or
GETWA_NOT_ASSIGNED can occur if the field in your output table is a
type P field but the description for this field in the fieldcatalog is
defined as a character field.So if the problem happens in a customer
program,please make sure that for this fieldname the DATATYPE or INTTYPE
in the fieldcatalog is the same as that in your output table.
Please also check note 504384 ALV-SOS: Consistency check.
Kelly
09-11-2013 11:57 AM
09-12-2013 6:48 AM
Dear Rahul,
Based on your sreen shot, it is clear that, field catalog definition is missing for that field.
Please check your Field Catalog Definitions
You might have missed for the column Requisitionor of PO.
Please add field catalog definition for this field as well.
Regards,
Venkat
09-12-2013 2:08 PM
09-13-2013 11:06 AM
Hi Rahul,
This dump is because of Feildsymbols.
Please check whether fieldsymbol is assigned or not before passing value to another variable or fieldsymbol as per your requirement.
Refer to below example.
Assign (c_txt) to <fs_txt>
If <fs_txt> is assigned.
Assign <fs_txt> to <fs_txt1> .
endif.
Thanks,
Pavani.
09-24-2014 9:48 AM
Hi Rahul,
I guess you've already fixed this... but just comment my case and how I've solved same issue.
This problem is related with FIELDCATALOG and/or LAYOUT of your ALV and you get this error only when execute in background...
As debugging in background would be complex I suggest to set a breakpoint in your program at moment of ALV is called. It could be at FM: REUSE_ALV_GRID_DISPLAY_LVC or REUSE_ALV_GRID_DISPLAY or in OO scenario at method SET_TABLE_FOR_FIRST_DISPLAY
Then set variable SY-BATCH = 'X' (this way ALV will behave as runs in background mode).
Then you will be able to set another breakpoint in program SAPLKKBL (LKKBLF99) and see exactly the field is causing your inconsistency.
Regards,
Alfonso.