PERFORM_PARAMETER_MISSING - continual short dump in BW

Hi All,
I am facing one strange issue.
Few days back there was a failure in delta load of CUSTOMER_TEXT. The load was corrected, but since then every 45 minutes or so I am getting a short dump in the system.
There is no active job in BW or R/3, but it seems there is something triggered in infinite loop, which gives the 2 entries in SM58 and a short dump in every few minutes.
SM58: -
Missing parameter with PERFORM.
ST22: -
Runtime Errors PERFORM_PARAMETER_MISSING
Exception CX_SY_DYN_CALL_PARAM_MISSING
Termination occurred in the ABAP program "SAPLRSAI" - in
"RSAR_TRFC_DATA_RECEIVED".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 247
of the (Include) program "LRSAIU06".
The termination is caused because exception "CX_SY_DYN_CALL_PARAM_MISSING"
occurred in
procedure "RSAR_TRFC_DATA_RECEIVED" "(FUNCTION)", but it was neither handled
locally nor declared
in the RAISING clause of its signature.
I have no idea how to stop this dump. Can somebody throw some light on this?
Thanks,
Manisha

Hi Manisha,
I think this is happening because the backgroud job in the source system was not ended.
This is happening because on the day that you deleted the Delta request you have failed to stop the bacground job in the source system.
Just login in the source system SM37 -> Job name as BI* give the date selection and check if there is any active BI job that is available.
If available select and delete it or stop it.This will solve the issue
Prathish

Similar Messages

Custom error message in user exit is giving Short dump

Hi All,
We have a scenario where in if any user try to create/Change/Delete particular types of contract in SAP system we have to issue error message
saying ZIN/ZIR contract creation/Change/Deletion is blocked in SAP. This has to be done from the web application. So we are putting below code
in user exit MV45AFZZ in the form USEREXIT_SAVE_DOCUMENT_PREPARE.
CONSTANTS: lc_vbcpic01 TYPE sy-uname VALUE u2018VBCPIC01u2019, u201CWeb application user ID
         lc_zin           TYPE vbak-auart VALUE u2018ZINu2019,
                     lc_zir            TYPE vbak-auart VALUE u2018ZIRu2019,
                     lc_text(32)    TYPE c VALUE u2018Check long text for more detailsu2019.
DATA: l_uname TYPE sy-uname.
CLEAR: l_uname.
MOVE sy-uname TO l_uname.
*If user ID is not the Web application ID then block the creation/Change/Deletion
IF   l_uname NE lc_vbcpic01
AND ( vbak-auart EQ lc_zin
OR    vbak-auart EQ lc_zir ).
MESSAGE e830(zv) WITH lc_text.
ENDIF.
This code is working fine while creating/Changing the contract i.e. Giving us error message so that user wonu2019t be able to create/change the contract.
But when we delete the contract from VA42, Control is coming to this message statement and is giving Short dump. Below is the error analysis of the dump.
Error Analysis:
During "Exit Command" processing, the program tried to send a " " message.
This is not allowed at this point in processing.
The program had to be terminated.
Screen name.............. "SAPMV45A"
Screen number............ 4001
If any one has come across such scenario/any work around for this problem please let me know your inputs. Your inputs are highly appreciated.
I am working on 4.6C version of SAP.
Note: When i issue information/Warning message contract is getting deleted after displaying the message.
Thanks,
Vinod.

I exactly replicated the same in DELETE_DOCUMENT also
I am getting the Dump. I tried with exit also , but it continued and deleted. To avoid deletion we have to use Leave program or LEAVE TO CURRENT TRANSACTION.
Delete Function is Defined as EXIT command. so it is not possible to give error message. To convice you i just copied demo program and raised the error message.
it is also giving the dump.
copy the demo program DEMO_DYNPRO_AT_EXIT_COMMAND and make this change , information to error .
MODULE cancel INPUT.
MESSAGE e888(sabapdocu) WITH text-001 ok_code input1 input2.
IF ok_code = 'CANCEL'.
    CLEAR ok_code.
    LEAVE PROGRAM.
ENDIF.
ENDMODULE.
and see...

In SMARTFORMS when openee a Text Node,   Giving a Short Dump

Hi
I am getting Short Dump in SMARTFORMS Transaction, when ever I opened a Text Node and made some changes in it.
With out opening a Text Node I can able to change and activate the SmartForm.
But if I open a Text Node I can able to make changes in the Text Node but later if i click on any other Node, it is giving a Short Dump.
But all other systems in my office are working fine.
I have tried the Utilities->Settings-> and changed the editor also.
I have also Installed the SAPGUI once again for this Issue. But still I am getting the same problem.
Can anyone Please help me on this Issue.
I am sending the error enalysis of the Short Dump.
Error analysis
    Short text of error message:
    Control Framework : Error processing control
    Long text of error message:
     Diagnosis
         An error occurred when the system tried to process the commands
         from the Automation Queue on the presentation server.
         There are several possible reasons for this:
         - The installation of the SAP GUI on the presentation server is
         faulty or obsolete.
         - There is an error in the application program
         - There is an error in the SAPGUI or an integrated control
     Procedure
         1. Make sure that you have imported the appropriate Support
         Package, the current kernel, and GUI patch for the release of your
         system
         2. Check whether the error occurs locally on one or a few PCs, or
         generally on all PCs. Note whether the error only occurs for some
         users, for example because of a specific Customizing setting.
         If it only occurs locally, this suggests an installation problem
         with the PC. Check the installation; if necessary, reinstall the
         software. In the dump, search for the SY-MSGLI field, since it may
         point to the cause of the error.
         3. Activate the Automation Trace (in accordance with SAP Note
         158985).
         4.Start the transaction and continue until the screen immediately
         before the dump.
         5. From the System -> Utilities menu, choose Autom. Queue,
         Synchronous Processing.
         The status bar of the GUI displays the text:
            "Automation synchron flush mode on"
         6. If you now proceed with the application, the short dump will
         display the ABAP call that caused the error; the Automation Trace
         will contain the error on the presentation server.
         7. If necessary, load the short dump and trace files on to
         sapservX, so that SAP can analyze them.
    Technical information about the message:
    Message class....... "CNDP"
    Number.............. 006
Thanks in Advance.

Hi
I think dump is because of SAP GUI. If you are ECC 6.0 then install SAP GUI 710 with patch level 2 or more and check
Regards
Shiva

Short dump when I do total or sub total in the ALV report

Hi,
When I do total or sub-total on the currency field in the ALV report, it'll give a short dump like
" 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)".
   Short text of error message:
   Technical information about the message:
   Message classe...... "0K"
   Number.............. 000
   Variable 1.......... " "
   Variable 2.......... " "
   Variable 3.......... " "
   Variable 4.......... " "
   Variable 3.......... " "
   Variable 4.......... " "
Trigger Location of Runtime Error
    Program                                 SAPLSLVC
    Include                                 LSLVCF36
    Row                                     2,726
    Module type                             (FORM)
    Module Name                             FILL_DATA_TABLE
sometime when I do the page down on the ALV report, the same short dump is coming.
Can anyone help me out.
Thanks
Selva

Hi,
I'm getting this short dump in the standard program.
I'm getting ALV report display perfectly. the problem is, when I do total or subtotal on the currency fields.
2704
2705 ************************************
2706 * Column per Fieldcat Entry
2707 ************************************
2708         ls_lvc_data-value = space.
2709         clear ls_lvc_data-style.
2710         loop at it_fcat_local assigning <ls_fcat>
2711                 where tech ne 'X' and no_out ne 'X'.
2712           if l_invisible eq 'X'.
2713             clear l_invisible.
2714             if <ls_fcat>-do_sum is initial.
2715               continue.
2716             else.
2717               clear ls_lvc_data-col_pos.
2718             endif.
2719           endif.
2720
2721           add 1 to ls_lvc_data-col_pos.
2722
2723           assign component <ls_fcat>-fieldname
2724                            of structure <ls_data> to <l_field_value>.
2725           if sy-subrc ne 0.
>>>>>             message x000(0k).
2727           endif.
2728
in this standard program, I'm getting the dump. the line is mentioned above in the code.

Getting short dumps while reading bulky data from excel sheet

Hi all,
We have converted our non-unicode based sap system (R/3 4.7, Windows 2003,
SQL 2000) into a unicode based system recently. We are facing two peculiar
problems for last few days.
*Problem 1 - *Whenever we want to upload the data from excel sheet, the
system throws a dump after reading about 400 entries, while last week the
same system used to read about 8000 entries in a single go.
*Problem 2 - *Also, whenever we realease a transport requst from development
containing a lot of changes, the request will reach the quality system but
without the changes. but if i ll try to import the changes into quality
system after generating more than one request containing small small
changes, they get reflected in QAS immediately. Is there any size
constraint in transporting a request fro DEV->QAS->PRD.
Please suggest some ways.
I am pasting the dump (that I am getting while data uploading from Excel).
~~~~~~~~~~~~~~~~~~
Runtime errors
MESSAGE_TYPE_X*
Occurred on
22.02.2008 at
13:21:02*
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:
Control Framework : Error processing control
Technical information about the message:
Diagnosis
An error occurred when the system tried to process the commands
from the Automation Queue on the presentation server.
There are several possible reasons for this:
- The installation of the SAP GUI on the presentation server is
faulty or obsolete.
- There is an error in the application program
- There is an error in the SAPGUI or an integrated control
Procedure
1. Make sure that you have imported the appropriate Support
Package, the current kernel, and GUI patch for the release of your
System
2. Check whether the error occurs locally on one or a few PCs, or
generally on all PCs. Note whether the error only occurs for some
users, for example because of a specific Customizing setting.
If it only occurs locally, this suggests an installation problem
with the PC. Check the installation; if necessary, reinstall the
software. In the dump, search for the SY-MSGLI field, since it may
point to the cause of the error.
3. Activate the Automation Trace (in accordance with SAP Note
158985).
4.Start the transaction and continue until the screen immediately
before the dump.
5. From the System -> Utilities menu, choose Autom. Queue,
Synchronous Processing.
The status bar of the GUI displays the text:
"Automation synchron flush mode on"
6. If you now proceed with the application, the short dump will
display the ABAP call that caused the error; the Automation Trace
will contain the error on the presentation server.
7. If necessary, load the short dump and trace files on to
sapservX, so that SAP can analyze them.
Message classe...... "CNDP"
Number.............. 006
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
"SAPLOLEA" or "LOLEAU02"
"AC_SYSTEM_FLUSH"
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....... "nhbho930"
Network address.......... "192.168.0.30"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 801586"
Character length......... 16 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "NHBHO930"
Database type............ "MSSQL"
Database name............ "DEV"
Database owner........... "dev"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Aug 17 2007 00:18:58"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "SQL_Server_8.00 "
Patch level.............. "196"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0"
User, transaction...
Client.............. 300
User................ "NHBABAP"
Language key........ "E"
Transaction......... "SE38 "
Program............. "SAPLOLEA"
Screen.............. "SAPMSDYP 0010"
Screen line......... 0
Information on where terminated
The termination occurred in the ABAP program "SAPLOLEA" in
"AC_SYSTEM_FLUSH".
The main program was "ZBDC_CONTRACT ".
The termination occurred in line 29 of the source code of the (Include)
program "LOLEAU02"
of the source code of program "LOLEAU02" (when calling the editor 290).
~~~~~~~~~~~~~~~~~~~~~
Thank you all.
Cheers.
Mitra __.____._

for the 50 millionth time: Excel spreadsheets are NOT databases, you should NOT try to use them as such and NEVER access them using JDBC.
You should also under NO condition use the JDBC-ODBC bridge driver (that was actually the 78 millionth time that was told someone).

"DATA_LENGTH_0" Short dump

Hi SAP experts!
We will appreciate a lot if you could help us with your expertise to solve an short dump loading data.
Trying to load Master data for one object, when we do only to PSA everything is fine. However, if we want to continue to its data target, we got a message of "DATA_LENGTH_0" short dump, making us impossible to contineu.
the information that the system gives us is just below of this Email.
Thank you very much in advance for your support!
Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_RANGE_OUT_OF_BOUNDS',
     was neither
    caught nor passed along using a RAISING clause, in the procedure "ROUTINE_9998"
     "(FORM)"
    Since the caller of the procedure could not have expected this exception
     to occur, the running program was terminated.
    The reason for the exception is:
    In program "GP40TYLPX0VKPP4E1JQZ7JCWSKY" the system tried to access field
     "LV_NODENAME" with length 0.
    Partial field access to fields with length 0 is not allowed, however.
How to correct the error
    Please use a positive length value when trying to access a partial field
    "LV_NODENAME" zugegriffen werden soll.
    If the error occurred in one of your own programs or in an SAP program
    that you modified, try to correct it yourself.

Tahnk you very much Santosh!
That note recomens us to install in Support Package 14, but we got already installed the 21.
Any other idea?
Thank you very much!

Short Dump while Complete deletion of data Contents from a Cube.

Hello Experts,
I am facing a runtime Short dump whenever i attempt to delete data from a Cube. Shown Below:-
Runtime Errors         MESSAGE_TYPE_X
Error analysis
    Short text of error message:
Data request to the OLTP
    Long text of error message:
    Technical information about t
    Message class....... "RSM"
    Number.............. 000
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "MESSAGE_TYPE_X" " "
    "SAPLRSM1" or "LRSM1U43"
    "RSSM_UPDATE_RSBKREQUEST"
Information on where terminated
    Termination occurred in the ABAP program "SAPLRSM1" - in
     "RSSM_UPDATE_RSBKREQUEST".
    The main program was "RSAWBN_START ".
    In the source code you have the termination point in line 117
    of the (Include) program "LRSM1U43".
Line SourceCde
   87   call function 'RSSTATMAN_GET_TYPE_FOR_DTA'
   88     exporting
   89       i_dta = l_dta
   90     importing
   91       e_type = l_dta_type
   92     exceptions
   93       error = 1
   94       others = 2.
   95   if sy-subrc <> 0.
   96     message id sy-msgid type sy-msgty number sy-msgno
   97             with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
   98   endif.
   99   call function 'RSSTATMAN_DELETE_STATUS'
100     exporting
101       i_dta      = l_dta
102       i_dta_type = l_dta_type
103       i_process = 'ALL'.
104
105   sort l_t_iccont by rnsidlast ascending.
106   loop at l_t_iccont.
107     data: l_s_reqdone like rsreqdone.
108     select single * from rsreqdone into l_s_reqdone where
109            rnr = l_t_iccont-rnr.
110     if sy-subrc <> 0.
111       read table l_h_dtpreq with key
112            requid = l_t_iccont-rnsidlast.
113       if sy-subrc = 0 and
114          ( l_h_dtpreq-ustate = '0' or l_h_dtpreq-tstate = '0' ).
115         clear l_s_reqdone-archived.
116       else.
>>>>>         message x000.
   118       endif.
119     endif.
120     if l_s_reqdone-archived <> rs_c_false.
121       call function 'RSREQARCH_RELOAD_REQUEST'
122         exporting
123           i_rnr         = l_t_iccont-rnr.
124     endif.
125     select single * from rsbkrequest into l_s_req where
126            requid = l_t_iccont-rnsidlast.
127     if sy-subrc <> 0.
128       continue.
129     endif.
130
131     read table l_h_rsbkdtp with table key
132          dtp = l_s_req-dtp.
133     if sy-subrc <> 0.
134       l_h_rsbkdtp-dtp = l_s_req-dtp.
135       insert table l_h_rsbkdtp.
136     endif.
This issue only exists in Production system not QTY or development thr Cube deletion is working fine.
So far I have tried Deleting Index's and then deleting the Cube Contents & Run Elementary Checks from RSRV but not find any lead yet.Also unable to find appropriate notes for this issue aswell I am using SAP_Bw comp 700 with SP26.
Any suggestion would be of great help .
Thanks & Regards
Aman

Hi Ap_SAP & Arvind,
Any recent upgrades or system refresh done?
In recent update just from SP24 to SP26 was updated and a DB stats Referesh was carried on.But this proublem existed before these activities.
Except deleting can you able to perform all other operations like loading data..etc?
Other than deletion I am able to do load data into cube extract from R3 and also i can delete data from PSA.Only deletion giving dump.
You are trying to delete transactional or master data.
I am tring for transaction data.
WHen I try to delete request by request it also lead to the same short dump.
@ arvind : I checked Sm12 there i see not table which has been locked.
Thanks
Aman

Short Dump while INSERTING to a DB Z table

There is one report that we are running in production. Earlier it was taking about 2hrs to run and now it's taking about 14-15 hours to run after we applied the Support Pack. I must agree that the report is not well written by the previous developers and I have been asked to rewrite it but in the meanwhile, they want to continue running the old one.
This report deletes all the existing records first and then updates a Z table. Last week when they tried to run the report as batch job it got cancelled after running 22000 secounds and my basis team told me that logs are getting saturated and we need to use Truncate Statement instead of DELETE from table statement and that is what I did but again when they tried running the report in production it got cancelled again and this time after 55000 secs and this time it's getting cancelled in the last step when we are inserting the records back to the table from the internal table.
So can you please tell me how can I take care of this.
My Findings:
1. Report updates a Z table for 700K records which is really not a very big size.
2. Z table size category is customized for upto 48K to 93K . Does this matter when I try to update 700K records at a time.
3. There is no foreign key relations in the Z table
4. I feel that, it could be a basis problem like, memory related. Any light on this?
5. The program currently uses INSERT statement.Can I try for a success using MODIFY statement. All validations are handled before inserting to remove the duplicates.So I dont see any issues using INSERT statement
6. Can we use a commit statement after INSERT or MODIFY?
7. From SAP help, I see that there is a limitation on the number of records can be inserted or modified. Any idea on the number?
Thanks & Best Regards,
Kiran Babu Dasari

Dump:
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Date and Time          01/01/2009 10:17:22
Short text
SQL error in the database when accessing a table.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
How to correct the error
Database error text........: "SQL0964C The transaction log for the database is
full. SQLSTATE=57011 row=1"
Internal call code.........: "[RSQL/INSR/ZTMM_PU_FOR_BW ]"
Please check the entries in the system log (Transaction SM21).
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
"ZPMM_BWLOAD_R_V2" or "ZPMM_BWLOAD_INC02"
"FILL_ZTMM_PU_FOR_BW"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"FILL_ZTMM_PU_FOR_BW" "(FORM)", or its possible occurrence must be declared in
the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "ucerp13"
Network address...... "192.168.254.23"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "00C4B5BE4C00"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 34
Shortdump setting.... "full"
Database server... "ucerp10"
Database type..... "DB6"
Database name..... "RP1"
Database user ID.. "SAPRP1"
Terminal................. " "
Char.set.... "C"
SAP kernel....... 700
created (date)... "Oct 26 2008 20:51:39"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "DB6_81 "
Patch level. 183
Patch text.. " "
Database............. "DB6 08.02., DB6 09."
SAP database version. 700
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
Memory consumption
Roll.... 16192
EM...... 234631488
Heap.... 0
Page.... 24576
MM Used. 28706288
MM Free. 197532304
User and Transaction
Client.............. 400
User................ "BATCHUC"
Language key........ "E"
Transaction......... " "
Transactions ID..... "49597E9619C40076E1008000C0A8FE17"
Program............. "ZPMM_BWLOAD_R_V2"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "ZPMM_BWLOAD_R_V2" - in
"FILL_ZTMM_PU_FOR_BW".
The main program was "ZPMM_BWLOAD_R_V2 ".
In the source code you have the termination point in line 2886
of the (Include) program "ZPMM_BWLOAD_INC02".
The program "ZPMM_BWLOAD_R_V2" was started as a background job.
Job Name....... "ZPMM_BWLOAD_R_V2"
Job Initiator.. "BATCHSCHED"
Job Number..... 10261500
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "FILL_ZTMM_PU_FOR_BW" "(FORM)", but it was neither handled locally
nor declared
in the RAISING clause of its signature.
The procedure is in program "ZPMM_BWLOAD_R_V2 "; its source code begins in line
2751 of the (Include program "ZPMM_BWLOAD_INC02 ".
Source Code Extract
Line
SourceCde
2856
itab_result-rec_no   = recnum.
2857
ENDIF.
2858
2859
11/30/05 - Change it back after sorting
2860
IF linetype = 'AAA'.
2861
itab_result-linetype = 'INI'.
2862
ENDIF.
2863
itab_result-extractdate = e_sdate.
2864
itab_result-mandant     = sy-mandt.
2865
MODIFY itab_result INDEX indx.
2866
2867
SELECT SINGLE
2868
rec_no
2869
ponumber
2870
FROM ztmm_pu_for_bw
2871
INTO CORRESPONDING FIELDS OF itab_duprec
2872
WHERE rec_no     = recnum
2873
AND ponumber   = pono
2874
AND   linetype = linetype
2875
AND   line_no = lineno
2876
AND   changenr = chgno
2877
AND   chgind_h = indh
2878
AND   chgind_p = indp
2879
AND   tblname = tbl
2880
AND   fldname = fld.
2881
IF sy-subrc <> 0.
2882
MOVE-CORRESPONDING itab_result TO itab_result_bw.
2883
APPEND itab_result_bw.
2884
nrecs_results = nrecs_results + 1.
2885
>>>>>
INSERT ztmm_pu_for_bw FROM TABLE itab_result_bw.
2887
      INSERT zztmm_pu_for_bw FROM TABLE itab_result_bw.
2888
2889
CLEAR itab_result_bw.
2890
REFRESH itab_result_bw.
2891
ENDIF.
2892
ENDLOOP.
2893
*change to array insert for performance
2894
      INSERT ZZTMM_PU_FOR_BW FROM TABLE itab_result_bw.
2895
2896
ENDFORM.                    " fill_ztmm_pu_for_bw
Contents of system fields
Name
Val.
SY-SUBRC
4
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Load Purchasing Info. for BW Reporting
SY-MSGTY
E
SY-MSGID
TD
SY-MSGNO
600
SY-MSGV1
T710-08L04
SY-MSGV2
K01
SY-MSGV3
EN
SY-MSGV4
SY-MODNO
0
SY-DATUM
20081231
SY-UZEIT
190013
SY-XPROG
SAPCNVE
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
2 FORM         ZPMM_BWLOAD_R_V2                    ZPMM_BWLOAD_INC02                    2886
FILL_ZTMM_PU_FOR_BW
1 EVENT        ZPMM_BWLOAD_R_V2                    ZPMM_BWLOAD_R_V2                      192
START-OF-SELECTION
Chosen variables
Name
Val.
No.       2 Ty.          FORM
Name FILL_ZTMM_PU_FOR_BW
SY
#######ৡ###################A###P#################ż#############################T#######린 u#̀##
00000000000000000000000000000000000000010000000000000000000000000000000000000000000000FB000000
000000090000000000000000000000000000000A0000000001000000000000000000000000000000000000F9000300
0000000E0000000000000000000400050000000B0000000007000000000000000000000000000105000000FB270000
0000010100000000000000000101010000000000000000040C000000000000000000000000000604000000F005000C
ITAB_RESULT_BW-WAERS
USD
00000
00000
55422
53400
ITAB_RESULT-WAERS
USD
00000
00000
55422
53400
ITAB_RESULT_BW+5358(10)
#U#C# #
0205040202
0005030000
ITAB_RESULT+4160(10)
#U#C# #
0205040202
0005030000
AMTCRCHGPOSREGUA2
00000000000
0000000000C
ITAB_RESULT_BW+5378(572)
#S#h#i#p#p#i#n#g# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
0205060607070606060202020202020202020202020202020202020202020202020202020202020202020202020202
000308090000090E070000000000000000000000000000000000000000000000000000000000000000000000000000
ITAB_RESULT+4170(572)
#S#h#i#p#p#i#n#g# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
0205060607070606060202020202020202020202020202020202020202020202020202020202020202020202020202
000308090000090E070000000000000000000000000000000000000000000000000000000000000000000000000000
C_INITIAL
@0E@
000000
000000
434422
005000
ITAB_RESULT_BW-ORT01
Cincinnati
00000000000000000000000000000000000
00000000000000000000000000000000000
46666666762222222222222222222222222
39E39EE1490000000000000000000000000
ITAB_RESULT-ORT01
Cincinnati
00000000000000000000000000000000000
00000000000000000000000000000000000
46666666762222222222222222222222222
39E39EE1490000000000000000000000000
ITAB_RESULT_BW-PSTLZ
45206
0000000000
0000000000
3333322222
4520600000
ITAB_RESULT-PSTLZ
45206
0000000000
0000000000
3333322222
4520600000
ITAB_RESULT_BW-REGIO
OH
000
000
442
F80
ITAB_RESULT-REGIO
OH
000
000
442
F80
ITAB_RESULT_BW-STRAS
2709 Woodburn Ave.
00000000000000000000000000000000000
00000000000000000000000000000000000
33332566667762476222222222222222222
270907FF4252E0165E00000000000000000
ITAB_RESULT-STRAS
2709 Woodburn Ave.
00000000000000000000000000000000000
00000000000000000000000000000000000
33332566667762476222222222222222222
270907FF4252E0165E00000000000000000
%_SPACE
0
0
2
0
ITAB_RESULT_BW+6154(4)
0202
0000
ITAB_RESULT+4908(4)
0202
0000
LW_LINES
164
000A
0004
ITAB_RESULT_BW-TELF1
961-1122
0000000000000000
0000000000000000
3332333322222222
961D112200000000
ITAB_RESULT-TELF1
961-1122
0000000000000000
0000000000000000
3332333322222222
961D112200000000
ITAB_RESULT_BW-LAND1
US
000
000
552
530
ITAB_RESULT-LAND1
US
000
000
552
530
COUNTROCHGNEGCONOVER1K2
0
0000
0000
ITAB_RESULT_BW+6158(337)
#0#3#6#0#-#0#0# # # # # # # # # # # # # #M#R#O# #&# #C#o#n#s#t#r#u#c#t#i#o#n#A#t#h#l#e#t#i#c
0203030303020303020202020202020202020202020405040202020406060707070706070606060407060606070606
00000306000D0000000000000000000000000000000D020F000600030F0E030402050304090F0E0104080C05040903
ITAB_RESULT+4950(337)
#0#3#6#0#-#0#0# # # # # # # # # # # # # #M#R#O# #&# #C#o#n#s#t#r#u#c#t#i#o#n#A#t#h#l#e#t#i#c
0203030303020303020202020202020202020202020405040202020406060707070706070606060407060606070606
00000306000D0000000000000000000000000000000D020F000600030F0E030402050304090F0E0104080C05040903
ITAB_CHGLOG[]
Table IT_33[587x1576]
\PROGRAM=ZPMM_BWLOAD_R_V2\DATA=ITAB_CHGLOG[]
Table reference: 25
TABH+ 0(20) = 070000009070DB38000000000000000000000000
TABH+ 20(20) = 00000019000000210000024B00000628FFFFFFFF
TABH+ 40(16) = 040000000000149000082C9401800000
store        = 0x070000009070DB38
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id           = 25    (0x00000019)
label        = 33    (0x00000021)
fill         = 587   (0x0000024B)
leng         = 1576 (0x00000628)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000095
occu         = 8     (0x00000008)
access       = 1     (ItAccessStandard)
idxKind      = 1     (ItIndexLinear)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x07000000A0E13E70
pgHook       = 0x07000000B2EBC728
idxPtr       = 0x07000000906BA5E0
shmTabhSet   = 0x0000000000000000
id           = 32    (0x00000020)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 1024 (0x00000400)
lineAlloc    = 592   (0x00000250)
shmVersId    = 0     (0x00000000)
shmRefCount = 469   (0x000001D5)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
collHook     = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
ITAB_RESULT_BW+3592(1026)
0202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ITAB_RESULT+5798(1026)
0202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ITAB_RESULT_BW-MANDANT
400
000
000
333
400
ITAB_RESULT-MANDANT
400
000
000
333
400
AMTTCCHGPOSREGST2
00000000000
0000000000C
ITAB_RESULT_BW[]
Table IT_132[1x6760]
\PROGRAM=ZPMM_BWLOAD_R_V2\DATA=ITAB_RESULT_BW[]
Table reference: 51
TABH+ 0(20) = 07000000A9A1FEA8000000000000000000000000
TABH+ 20(20) = 00000033000000840000000100001A68FFFFFFFF
TABH+ 40(16) = 0400000000003140000224C401800000
store        = 0x07000000A9A1FEA8
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id           = 51    (0x00000033)
label        = 132   (0x00000084)
fill         = 1     (0x00000001)
leng         = 6760 (0x00001A68)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000248
occu         = 2     (0x00000002)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x07000000A283E980
pgHook       = 0x0000000000000000
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 141   (0x0000008D)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 2     (0x00000002)
lineAlloc    = 2     (0x00000002)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x00000001)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
collHook     = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
ITAB_RESULT_BW
400##͒4500034945
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000030000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3330053333333333222222222222222222222222222222222222222222222222222222222222222222222222222222
4000024500034945000000000000000000000000000000000000000000000000000000000000000000000000000000
%_DUMMY$$
0000
0000
2222
0000
COUNTTCCHGNEGCONST3
0
0000
0000
<%_TABLE_ZTMM_PU_FOR_BW>
AMTTOTAL3
00000000000
0000000000C
No.       1 Ty.          EVENT
Name START-OF-SELECTION
T023T
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
T024
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
T161
00000                                   00000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222223333322222222222222222222222222222222222333332222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
TWLAD
000000000000000000000000
000000000000000000000000
222222222222222222222222
000000000000000000000000
ZTMM_BOA
0000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222223333333333333333222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ZTMM_PU_FOR_BW
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2220002222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ZTPU_DOCTYPE
0000000000000000000000000000000000
0000000000000000000000000000000000
2222222222222222222222222222222222
0000000000000000000000000000000000
USR02
####0000000000000000             #                        000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222220000333333333333333322222222222220222222222222222222222222333333333333333333333
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SSCRFIELDS
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
C_BLUESQUAREX
@3X@
000000
000000
435422
038000
Internal notes
The termination was triggered in function "HandleRsqlErrors"
of the SAP kernel, in line 786 of the module
"//bas/700_REL/src/krn/runt/absapsql.c#11".
The internal operation just processed is "SQLS".
Internal mode was started at 20081231190002.
Internal call code.........: "[RSQL/INSR/ZTMM_PU_FOR_BW ]"
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit      = unlimited
=> Stack limit     = 4294967296
=> Core limit      = 1073741312
=> File size limit = unlimited
=> Heap address = 0x0x11c0f5d60
=> Stack address = 0xfffffffffff8040
=> Stack low     = 0xfffffffffff8040
=> Stack high    = 0xffffffffffff800
=> Stack Trace:
     AixStack() at 0x1000c945c
     CTrcStack2() at 0x1000c9554
     rabax_CStackSave__Fv() at 0x1000b3ee0
     ab_rabax() at 0x1000b0628
     ab_rsqlerr__FPCUsiT1P11RS_HEADER94T1Pv() at 0x10058c010
     HandleRsqlErrors__F9RsqlError9CloseMode() at 0x1017f1e94
     SqlsExecuteCall__FUcP11DynCallInfo() at 0x1017efc68
     ab_jsqls__Fv() at 0x1017ea82c
     ab_extri__Fv() at 0x100419ca0
     ab_xevent__FPCUs() at 0x10094e47c
     ab_trigg__Fv() at 0x10094e168
     ab_run() at 0x1011aabb8
     N_ab_run() at 0x100f6edc0
     dynpmcal() at 0x100f6d9c4
     dynppai0() at 0x100f6b2c8
     dynprctl() at 0x100f7375c
     dynpen00() at 0x100f6761c
     Thdynpen00() at 0x1000e3c6c
     TskhLoop() at 0x1000e5b64
     ThStart() at 0x1001000c0
     DpMain() at 0x101301d34
     nlsui_main() at 0x101abea68
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
ZPMM_BWLOAD_R_V2
0
12/31/2008
10:10:08
409600
E
1
Prg
SAPMSSY0
1
05/30/2008
12:59:05
92160
E
2
Prg
SAPMSSYD
1
08/16/2006
12:06:37
21504
E
3
Prg
SAPFSYSCALLS
1
09/09/2004
14:18:32
7168
E
4
Prg
RSDBRUNT
0
12/13/2008
02:15:03
254976
E
5
Prg
SAPLSPRI
5
12/13/2008
02:14:06
342016
E
6
Typ
PRI_PARAMS
0
11/02/1998
09:46:12
5120
7
Typ
ARC_PARAMS
0
08/28/1997
08:36:28
6144
8
Typ
PRI_LAYOUT
0
11/06/2003
20:30:04
2048
9
Typ
PRIPAR_EXT
0
05/18/2004
14:07:03
3072
10
Typ
PRIPAR_EX2
0
11/09/2000
14:10:39
2048
11
Typ
PRIPAR_EX3
0
05/18/2004
14:07:03
5120
12
Typ
TPRI_DEF
0
11/09/2000
14:24:28
5120
13
Typ
USR01
0
05/30/2008
19:06:47
4096
14
Typ
TSP1D
0
11/15/2000
17:58:02
5120
15
Prg
SAPLSPOO
15
12/13/2008
02:14:06
160768
E
16
Prg
SAPLRSPOLSTDRV
16
12/13/2008
02:13:54
58368
E
17
Typ
TSPOPTIONS
0
01/29/1997
19:13:56
2048
18
Typ
TSP03
0
11/02/1998
09:57:05
5120
19
Typ
TSP0A
0
11/15/2000
17:58:02
6144
20
Typ
TSP03C
0
11/21/2003
11:41:10
7168
21
Typ
TSP03T
0
03/23/1998
18:21:38
6144
22
Typ
TSP06A
0
11/15/2000
17:58:02
7168
23
Prg
SAPCNVE
23
09/09/2004
14:36:10
8192
E
24
Prg
SAPLSPOC
24
12/13/2008
02:15:07
137216
E
25
Typ
TSP03L
0
07/10/1997
00:46:18
2048
26
Typ
RSPOCHECK
0
08/13/1997
12:53:10
4096
27
Typ
TSP03A
0
07/10/1997
00:46:15
3072
28
Prg
SAPLSPOR
28
12/13/2008
02:15:07
39936
E
29
Prg
SAPLSPOB
29
05/30/2008
09:36:14
67584
E
30
Prg
SAPLSDEX
30
09/09/2004
14:20:42
22528
E
31
Typ
DD07T
0
05/30/2008
00:38:18
3072
32
Typ
DEVPAR
0
12/04/2000
12:46:11
3072
33
Typ
RSPOATTR
0
11/10/1999
17:44:19
2048
34
Typ
RSSCR
0
03/30/2005
10:21:45
5120
35
Prg
RSDBSPBL
0
03/30/2005
10:21:58
72704
E
36
Prg
SAPDB__S
0
03/30/2005
10:22:01
19456
E
37
Typ
VARID
0
05/12/1997
16:51:30
4096
38
Typ
SSCRFIELDS
0
05/13/1997
12:54:26
5120
39
Prg
%_CSYDB0
0
03/30/2005
10:21:45
35840
E
40
Prg
RSDBSPVA
0
12/13/2008
02:15:03
133120
E
41
Typ
RSVAMEMKEY
0
05/07/1997
13:07:49
5120
42
Prg
RSDBSPMC
0
08/16/2006
11:55:58
79872
E
43
Typ
DDSHDESCR
0
09/03/1997
03:05:16
4096
44
Typ
SPPARAMS
0
05/07/1997
13:10:38
2048
45
Prg
SAPLICON
45
05/30/2008
13:22:44
27648
E
46
Prg
%_CICON
45
05/30/2008
13:22:44
107520
E
47
Typ
ICONT
0
08/16/2006
11:55:57
2048
48
Prg
SAPLSABE
48
09/09/2004
14:18:36
12288
E
49
Prg
SAPLSECU
49
05/30/2008
11:07:13
87040
E
50
Typ
RSSUBINFO
0
10/14/1999
22:01:03
2048
51
Typ
RSEXFCODE
0
08/13/1997
12:52:57
2048
52
Prg
SAPLDSYA
52
05/30/2008
12:53:05
45056
E
53
Prg
SAPFSDS1
52
03/30/2005
10:22:01
52224
E
54
Typ
TDCLD
0
11/02/1998
09:51:35
6144
55
Prg
SAPLSDOD
55
01/25/2006
10:59:45
45056
E
56
Typ
DOKIL
0
05/12/1997
16:46:17
3072
57
Prg
SAPLLANG
57
09/09/2004
14:18:35
10240
E
58
Typ
T002
0
05/30/2008
00:53:58
2048
59
Prg
SAPFSPOR
0

Short dumps in every transaction during the Support pack import

I am in the middle of applying support packs SP12 on NetWeaver 7.0. In SPAM, during the import, I received short dumps. I get short dump for all transactions i excute now. I am unable to go to SPAM to continue the SPAM, all I get short dumps. This is our new training system that we are building. I had same issues before, and I got help from SAP for this issue, where they suggested tp command wiht lots of options to run at the OS level. Since I moved company I am not able access the same ticket. Do anyone of you guys know the OS tp command to continue the SPAM import phase?
Please and thanks
Kumar

Hi,
SAP does not recommend to run SP's at OS level. Most of time when u r running SAP_BASIS , u will receive ABAP dumps. then option is to run SP at using tp command & you have to analyze many things before running this command.
<removed_by_moderator>
Please read the Rules of Engagement
Edited by: Juan Reyes on Jul 28, 2008 10:12 AM

Short dump GETWA_NOT_ASSIGNED - Field symbol FS_ENVDLIST not assigned

Hi Experts,
I need your help. Currently i am getting a short in CIC0 transaction.
Please find steps executed which result in short dump.
Search for a BP with BD display as the active tab. This search will be successful.
Press u2018End Contactu2019 Now search for 2nd BP with BD display as the active tab.
This will result in a dump.
Now if I again execute the t-code CIC0 & enter the same BP it will be successful
On debugging, I found out that the program cannot identify the data environment since the field symbol <fs_envdlist> does not get assigned when BD_DISPLAY tab is active. But the program still continues to use this field symbol which results in a dump
CRM Version - 4.0 - Patch level 10
Please let me know if the below link is not accessible
[http://imageshack.us/photo/my-images/685/page3uk.jpg/]
[http://imageshack.us/photo/my-images/338/page2dr.jpg]
[http://imageshack.us/photo/my-images/510/page1up.jpg/]
[http://imageshack.us/photo/my-images/140/page4fa.jpg/]
[http://imageshack.us/photo/my-images/845/screenshotsxq.jpg/]

Hi Andrei,
Thank you for the reply, but both this note are applicable to me
1144076 u2013 Talks about dump when too many hits are returned - I do not have any such message
996915 u2013 Talks about searching for the premise for a point of delivery without entering any search parameters - again in my scenario, input data is always provided.
Is there any solution, i did get note 1254404 which is closest to my issue, but its valid from crm 5.0 and we are on CRM 4.0

Short dump OBJECTS_OBJREF_NOT_ASSIGNED when activating infoobjects

Hi Experts,
We are getting a short dump when activating bussiness content infoobject which contain attributes, for e.g. 0COSTCENTER.
We are not getting the same dump when activating infoobjects whith out attributes.
We found a note 1019055 that recomends install sp13 or install six or seven notes for an emergency issue.
The problem is that if we install sp13 we will get out of stack.
What is your recomendation in this case? we are afraid that the problems will continue until we don't implement the sp13.
Thanks!

use t-code SNOTE to implement the OSS note you mentioned ,if it doesnt work you can always revert back to old status by doing Reset.
Hope it Helps
Chetan
@CP..

Short dump in BW side

Hi All,
When I a am Extracting data from R/3 to BW. short damp happend in BW side as Runtime Error DBIF_RSQL_SQL_ERROR
Except. CX_SY_OPEN_SQL_DB
please any one help me and let me know the reasons why it happens short dump in BW side.
Adavance Thanks,
Achari

Problem:
DBIF_RSQL_SQL_ERROR error
ORA-00060
Solution:
ORA-00060 deadlock detected while waiting for resource
Cause: Your session and another session are waiting for a resource locked by the other.
This condition is known as a deadlock.
To resolve the deadlock, one or more statements were rolled back for the other session to continue work.
Action: Either:
Enter a ROLLBACK statement and re-execute all statements since the last
commit or
Wait until the lock is released, possibly a few minutes, and then re-execute
the rolled back statements.
<u>As per my knowledge,</u>
In this case the error has occured @ inserting the record to the facttable and
a lock situation has occured. So as said in the solution.....
<b>To resolve the deadlock, one or more statements were rolled back for the other session to continue work.</b>
need to restart (rollback) the failed step again.
*Check the SQL statement and identify where the lock situation is.
in ST22, check the source code extract where the code will be displayed, and the error will be shown near the arrow (----
>) mark
*Wait untill lock gets released.
*Repeat the failed process step.
****The solution I got form the Oracle 8i error messages.****
Regards,
Vijay

Short dump in BAPI_PO_CHANGE

HI all,
   I am using BAPI_PO_CHANGE to change the Quantity and Item text of PO items .
The following is the function call :
Loop at loop at z_i_item assigning <z_f_item>.
call function 'BAPI_PO_CHANGE'
      exporting
        purchaseorder                = <z_f_item>-ebeln
     tables
       return                        = z_i_return
       poitem                        = z_i_poitem
       poitemx                       = z_i_poitemx
      poschedule                     = z_i_posch
      poschedulex                    = z_i_poschx
       potextitem                = z_i_itemtxt .
Endloop.
Am filling all the internal tables in the " tables parameter " for every loop of z_i_item.
But it throws a short dump as soon as the BAPI is executed .
"   The current ABAP "SAPLMEPO" program had to be terminated because the
     ABAP processor detected an internal system error.
     When exporting the structure description, the structure
     components overlapped. The error occured in the
      description of the object "XEKPO".     "

Hi
You can change the approach to get the better pefromance.
try as below:
Loop at item table.
Move all the related items of PO into another ITAB.
Use AT END of EBELN and call the BAPI pass EBELN and ITAB and use commit.
The above will have better performance.
if you wish continue the current appraoch then,
Put some wait after iteration and also use comit based on the return of SY-SUBRC.
Use WAIT UPTO 2 SECONDS. (please check correct stmt)
Regards
Shiva

Short dump 'Table does not exist in database'

Hello All,
When a report is executing it is going to short dump by saying 'Table does not exist in database'. As per the short dump analysis this issue is happening because of the following   Native SQL statement statement :
Program : %_T050N0 (This is a dynamic program generating by SAP )
Form Name : DYN_LIC_SEL_TOT
exec sql performing LOOP_MOVE_WRITE_ISAP.
select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty into :dcat-lplate, :dcat-matnr,
:dcat-werks, :dcat-charg, :dcat-holdflag,
:dcat-qty from ZLICENSE_R2 where itm_num   = :p_matnr and
                model_lot = :p_charg
endexec.
As per the customer this issue occurring since they migrated the SAP back-end data base from Oralce to DB6. Here I felt that ZLICENSE_R2 is not migrated from the Oracle to DB6. But as per the BASIS Team, even this table was not maintained in Oracle also. If the table was not maintained in the Oracle, this issue should have been there even before migration also.
Following is the short dump details:
Short text
    Table does not exist in database.
What happened?
    The table or view name used does not
    exist in the database.
    The error occurred in the current database connection "DEFAULT".
What can you do?
    Check the spelling of the table names in your report.
    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
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_NATIVE_SQL_ERROR', was not
     caught in
   procedure "DYN_LIC_SEL_TOT" "(FORM)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
Triggering SQL statement: "select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty from ZLICENSE_R2 where itm_num = ? and model_lot = ? "
Database error code: "-204"
Could you please let me know what might be the reason for this issue.
Many Thanks in Advance.

Transaction SE11, input ZLICENSE_R2 for table name, and display the table. Did the table display? If not, that is the main problem.
If the table displays, go to menu item Utilities -> Database Object -> Database Utility
In the resulting screen, under the "Status" fields, you should see text "Exists in the database." If you don't, then the table exists in the dictionary, but doesn't exist in the database system. Click the "Create database table" button and then you should be able to run the program.
You may need basis team's help to carryout some of these actions.

Short Dump while scrolling in a maintenance view

A maintenance view has one field, defined as "Radiobutton".
1) Select the radiobutton for one entry.
2) Scroll down so that in the new page (i.e. the entries displayed in the new page) the entry selected in the first step is not visible.
3) Select any radiobutton again corresponding to any of the entries displayed in the new page.
4) On scrolling up again the short dump occurs.
The short dump text says "More than one radio button is active".
Any inputs in this regards are appreciated.
Thanks.
Gajendra.

Hi,
that means you are trying to make two radio buttons active.
parameters: ra radiobutton group g1 default = 'X',
rb radiobutton group g1.
ra = 'X'.
and rb = 'X'.
in your case so obviously it will dump.
check your coding..
and show your code...
Regards
vijay

PERFORM_PARAMETER_MISSING - continual short dump in BW

Similar Messages

Maybe you are looking for