‎2013 Sep 06 8:03 AM
Hi experts,
When I was running CON2 transaction in my QAS system, it run into a runtime error GETWA_NOT_ASSIGNED, see the details below.
When doing the same in PRD system, everything was OK.
From the dump analysis, it seems something wrong with calling FM OBJECT_KEY_MOVE.
Background is: I just upgraded the QAS system to ERP 6.0 from R3, PRD is still in R/3.
Can anybody help me figure out the root cause of the dump?
|Short text |
| Field symbol has not yet been assigned. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What happened? |
| Error in the ABAP Application Program |
| |
| The current ABAP program "SAPLBO00" 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 "-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. |
| |
----------------------------------------------------------------------------------------------------
|Information on where terminated |
| Termination occurred in the ABAP program "SAPLBO00" - in "OBJECT_KEY_MOVE". |
| The main program was "SAPLKAZB ". |
| |
| In the source code you have the termination point in line 1 |
| of the (Include) program "LBO00U05". |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Source Code Extract |
----------------------------------------------------------------------------------------------------
|Line |SourceCde |
----------------------------------------------------------------------------------------------------
|>>>>>|FUNCTION object_key_move. |
| 2|*"---------------------------------------------------------------------- |
| 3|*"*"Lokale Schnittstelle: |
| 4|*" IMPORTING |
| 5|*" REFERENCE(I_SOURCE_KEY) |
| 6|*" VALUE(I_OBJNR) TYPE J_OBJNR |
| 7|*" VALUE(I_RCODE) TYPE J_RCODE OPTIONAL |
| 8|*" EXPORTING |
| 9|*" REFERENCE(E_RESULT_KEY) |
| 10|*" EXCEPTIONS |
| 11|*" OBART_NOT_FOUND |
| 12|*" SOURCE_KEY_INVALID |
| 13|*" RESULT_KEY_INVALID |
| 14|*"---------------------------------------------------------------------- |
| 15| |
| 16| STATICS: s_tbo00 LIKE tbo00. |
| 17| |
| 18| DATA: l_obart TYPE j_obart, |
| 19| l_keyxx LIKE tbo00-key01, |
| 20| l_source_key_invalid TYPE c, |
‎2013 Sep 06 10:05 AM
Hi Danny,
This is clearly a standard SAP Issue. Kindly search for relevant OSS notes in Service market place for your system details by program SAPLBO00 or Function object_key_move.
Rewards points if helpful.
Regards,
Vasanth
‎2013 Sep 06 11:06 AM
Hi Vasanth,
I found 2 notes by searching "object_key_move + getwa_not_assigned", I analyzed the notes they are changing different Function Modules which is not the object_key_move, so I'm not sure whether these notes can help.
Thanks for your quick response!
Danny
‎2013 Sep 06 12:19 PM
Hi Danny,
One more suggestion.If the Function module Object_key_move does not work. Refine your search term based on the program SAPLBO00 or transaction CON2. the issue might not exactly in the FM based on the above log guess the issue is because of the data passed to FM and field-symbols are not assigned accordingly.
Also always search based on your system details so that you will get only valid OSS Notes applicable based on your system.
Confirm if that works.
Regards,
Vasanth