short dump in SQ02 to create infoset

[Former Member]

Hi, all, when i used SQ02 to create infoset with data source 'Table join using base table', i am facing a short dump caused by message X001. But when i choose data source 'Direct read of table', it is ok. By the way, version of SAP is ECC5.0. Could anybody give me some advice? Thanks in advance.

[Former Member]

Hi,

Please check that you have metioned the Secondary Table name.

The dump can also come if there is no common Key between the two tables.

Please check if this solves your problem.

Regards,

Amit.

[Former Member]

Hi, Amit, thanks for your kindly reply, short dump is appeared when click the 'OK' button in the initial screen, i just choose the source, and input the table name like MARC. I am sure there is nothing wrong with table type.

[Former Member]

Hello Rick.

Can you provide some more (line at which the error message was triggered) details of the dump.

It may even be some GUI problem.

Or else it can be one more thing.

I did this way and it works fine.

1. Go To Transaction SQ02.

2. Create and enter the details.

3. Under the "Table join using BASIS table" radiobutton enter the table name (say) MARA.

4.Click on insert table.

5. In Add table - Table name - (say) MARC.

There it goes the Join has been created.

Good Luck & Regards.

Harsh Dave

[Former Member]

Hi, Harsh, sorry to response so late, because i can't logon SAP until today, below is the detail information about the short dump:

Runtime errors         MESSAGE_TYPE_X
       Occurred on     10.09.2008 at   12:47:29
------------------------------------------------------------------------------------------

The current application triggered a termination with a short dump.

--------------
What happened?
--------------

The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).

----------------
What can you do?
----------------

Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.

To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
 termination messages, especially those beyond their normal deletion
date.


--------------
Error analysis
--------------

Short text of error message:
Activity terminated

Technical information about the message:
Message classe...... "AQQIS_CNTRL"
Number.............. 001
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "

------------------------
How to correct the error
------------------------

Probably the only way to eliminate the error is to correct the program.
-

You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:

------------------------------------------------------------------------
"MESSAGE_TYPE_X" C
"CL_GUI_AQQGRAPHIC_NETPLAN=====CP" or "CL_GUI_AQQGRAPHIC_NETPLAN=====CM001"
"CONSTRUCTOR"
------------------------------------------------------------------------
If you cannot solve the problem yourself, please send the
following documents to SAP:

1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
-

2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.

3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.

4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.

------------------
System environment
------------------

SAP Release.............. "620"

Application server....... "i39main"
Network address.......... "10.2.7.173"
Operating system......... "HP-UX"
Release.................. "B.11.23"
Hardware type............ "ia64"
Character length......... 16 Bits
Pointer length........... 64 Bits
Work process number...... 1
Short dump setting....... "full"

Database server.......... "jesu2003"
Database type............ "ORACLE"
Database name............ "I39"
Database owner........... "SAPR3"

Character set............ "C"

SAP kernel............... "640"
Created on............... "Dec 10 2006 20:41:59"
Created in............... "HP-UX B.11.23 U ia64"
Database version......... "OCI_920 "

Patch level.............. "161"
Patch text............... " "

Supported environment....
Database................. "ORACLE 9.2.0.*.*, ORACLE 10.1.0.*.*, ORACLE
 10.2.0.*.*"
SAP database version..... "640"
Operating system......... "HP-UX B.11"

--------------------
User, transaction...
--------------------

Client.............. 030
User................ "XVIJOLIA"
Language key........ "E"
Transaction......... "SQ02 "
Program............. "CL_GUI_AQQGRAPHIC_NETPLAN=====CP"
Screen.............. "SAPLAQJD_CNTRL 0200"
Screen line......... 2

-------------------------------
Information on where terminated
-------------------------------

The termination occurred in the ABAP program "CL_GUI_AQQGRAPHIC_NETPLAN=====CP"
 in "CONSTRUCTOR".
The main program was "SAPMS38O ".

The termination occurred in line 11 of the source code of the (Include)
 program "CL_GUI_AQQGRAPHIC_NETPLAN=====CM001"
of the source code of program "CL_GUI_AQQGRAPHIC_NETPLAN=====CM001" (when
 calling the editor 110).

-------------------
Source code extract
-------------------

000010   method CONSTRUCTOR .
000020
000030     SUPER->CONSTRUCTOR( EXPORTING  I_R_PARENT        = i_r_parent
000040                         EXCEPTIONS CNTL_ERROR        = 1
000050                                    CNTL_SYSTEM_ERROR = 2
000060                                    CREATE_ERROR      = 3
000070                                    LIFETIME_ERROR    = 4
000080                                    CANCELED          = 5
000090                                    others            = 6 ).
000100     IF SY-SUBRC <> 0.
----->       message x001.
000120     ENDIF.
000130
000140   * benötigte Kontextmenüs
000150     P_S_CTXMNU_USE = i_S_CTXMNU_USE.
000160
000170     me->SET_REGISTERED_EVENTS( EXPORTING  EVENTS                    = i_t_
000180                                EXCEPTIONS CNTL_ERROR                = 1
000190                                           CNTL_SYSTEM_ERROR         = 2
000200                                           ILLEGAL_EVENT_COMBINATION = 3
000210                                           others                    = 4 ).
000220     IF SY-SUBRC <> 0.
000230       MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
000240                  WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
000250       message x000.
000260     ENDIF.
000270
000280   * Tabellenabstand:
000290     ME->IF_GUI_aqqGRAPHIC~SET_TABLEDISTANCE( ).
000300

<EDITED BY MODERATOR - THERE'S NO NEED TO COPY THE WHOLE ST22 LOG>

Edited by: Alvaro Tejada Galindo on Oct 9, 2008 3:57 PM

[Former Member]

Hi Rick

Did you ever get this resolved? I am having the same problem and can't find an answer.

In Harsh Dave's response, he mentioned click the Insert table button. I don't see any such button. I am on R3 4.7.

Ron

[Former Member]

Hi Rick

I think I found the answer. Check out OSS note 681568.

I registered icjoin.ocx but it still didn't work. Then I registered wdbdadptjoin.ocx and that seems to have solved the problem.

Ron

[Former Member]

Hi, Ron, thanks. I will try follow your steps.