ZGUIXT16 produces an ABAP short dump

Hi,
The program ZGUIXT16 (intended to generate the local value help files) always stops and produces an ABAP short dump. What could be the reason?
Thanks,
Varsha.

Hi,
ZGUIXT16 uses the SAP standard function CHECKTABLE_GET in order to generate the local value help. For some reason, this function aborts for several domains, depending on the R/3 release.
Solution: In ZGUIXT16 some domains are already excluded:
Exclude some domains (error in SAP value list generation):
CHECK DOM-DOMNAME NE: 'HIERANM', 'IM_POSNR', 'IWEXTSYMBL', 'P02_BTRTE'.
Here you can enumerate domains that lead to errors, and then restart the program.
Reward Points if found helpfull..
Cheers,
Chandra Sekhar.

Similar Messages

ABAP short dump with "CNTL_ERROR"

Hi,
I am getting an ABAP short dump with "CNTL_ERROR" while using an input script. What do I do?
Thanks,
Sreekar.

Hi,
Newer versions of SAP GUI and R/3 include external controls called as ActiveX (OCXs). ABAP code internally issues some commands to flush and refresh these controls. Since, when using GuiXT and input scripting, these controls are not created, and ABAP dumps. Use keyword "Enable controls" (without quotes on a separate line) in a screen block that has an ActiveX control.
Example:
Screen SAPLCOIH.3000
Enter "/Menu=4,1,5"
Screen SAPLSP01.0100
Enter "=No"
Screen RIPLKO10.1000
Enable controls
Set F[Group] "UG"
Enter "/8"
Reward Points if found helpfull..
Cheers,
Chandra Sekhar.

ABAP Short Dump Occurring

Hi All
We had do done a DBEXPORT of our R/3 4.6C while doing there was a increment conversion pending and we got error during the export, we finished the conversion and then started the DBEXPORT again and it completed successfully, however after this we are receiving ABAP Short dumps which says DBIF_RSQL_INTERNAL_ERROR, Internal error when accessing table "T179 ". Practically for any new entry we do in database.Kindly suggest how to go about.
Regards
Arun

Hi Micheal
we had done an incremental conversion for DBTABLOG table which is forbidden also was not complete,so we completed the conversion and removed a field which was added in the table (this was cause of error),we removed the field and activated teh table and the short dump was resolved.
Anyway thanks for your reply.
Arun

ABAP short dump error while creating an invoice

Hi All,
We are creating a delivery(Unit is EA) for the material for which the Unit Conversion is maintained as 1CS = 48 EA. So while creating a delivery If I maintain the delivered quantity is less than 24, I am not able to create an invoice.It's throwing an ABAP short dump error BCD zerodivide run time error.
If I deliver greater than or equal to 24, then the invoice is created without any issue
I have checked if there is any CMIR record but no record is maintained.
Can anyone help me out on this?
Regards,
Manjunath

Hi Manju,
Can you post the dump screen shot, which should contain the source code for that dump.
Regards,
Krishna

ABAP short dump when loading data into Infocube

Hello All,
I am getting an ABAP short dump error when loading data into Infocube. I tried to load data from PSA and ODS.
I ran the code to compress the Infocube, no improvement still getting the same error.
Error Analysis:
A raise statement in the program "SAPLRSDU_PART" raised in the exception.
Internal Notes:
The termination occured in the function "ab_i fune" of the SAP Basis system. Specifically in the line 2316 of the module "//bas/620/src/krn/runt/abfunc. C#18".
The internal operation just processed is "FUNE"
Advance thanks !!!
Siv

Hello Siv,
try to run program SAP_DROP_EMPTY_FPARTITIONS to display existing partitions. Then compare it to the number of uncompressed requests. Maybe there's a mismatch.
SAP notes that might help: 385163, 590370
Regards,
Marc
SAP NetWeaver RIG, US BI

SPAM update of DMIS stalled with ABAP Short Dump

Hi Experts,
Was wondering if someone could help me. I am trying to install DMIS on my NW 702 system. The installation sort of halted half way and now I am just not able to get into SPAM. Everytime I try to start SPAM the system loops for a good few minutes and it short dumps as below:
Category
ABAP Programming Error
Runtime Errors
TIME_OUT
ABAP Program
SAPLOCS_SEMAPHORE
Application Component BC-UPG-OCS
Trigger Location of Runtime Error
    Program                                 SAPLOCS_SEMAPHORE
    Include                                 LOCS_SEMAPHOREU02
    Row                                     85
    Module type                             (FUNCTION)
    Module Name                             OCS_QUEUE_SEMAPHORE
55 *   OCS is locked, remember this
56     ev_locked = on.
57 *   check if OCS is locked by other (OCS) tools
58     IF iv_tool = space.   "maybe were are called in batch, check
59       IF sy-batch = off OR
60          ls_pat10-btch_state NA gc_batch_states.
61 *       IV_TOOL = space but no batch processing
62 *       -> foreign lock, you are not allowed to proceed
63         cs_sema = ls_pat10.
64         RAISE foreign_lock.
65       ENDIF.
66     ELSE.
67       IF ls_pat10-ocs_tool <> iv_tool.
68 *       foreign lock, you are not allowed to proceed
69         cs_sema = ls_pat10.
70         RAISE foreign_lock.
71       ENDIF.
72     ENDIF.
73
74 *   we are either in batch processing or IV_TOOL matches PAT10
75 *   --> own lock, return it
76     IF iv_read_only <> space.
77       cs_sema = ls_pat10.
78       EXIT.
79     ENDIF.
   79
ENDIF.
   80 *   update it
   81
ls_pat10 = cs_sema.
   82
ls_pat10-responsibl = sy-uname.
   83
ls_pat10-imple_date = sy-datum.
   84
ls_pat10-imple_time = sy-uzeit.
>>>>>
UPDATE pat10 FROM ls_pat10.
   86
cs_sema = ls_pat10.
   87   ENDIF.   "sy-subrc = 4
   88
   89 ENDFUNCTION.
4 FUNCTION
SAPLOCS_SEMAPHORE
LOCS_SEMAPHOREU02
85
   OCS_QUEUE_SEMAPHORE
3 FUNCTION
SAPLOCS_BATCH
LOCS_BATCHU07
186
   OCS_DELETE_BATCH_SEMAPHORE
2 FORM
SAPMSPAM
MSPAMF06
190
   READ_N_CHECK_BATCH_JOBS
1 MODULE (PBO) SAPMSPAM
MSPAMO01
776
   READ_BATCH_JOBS
Would appreciate if someone can help and has faced something similar.
Regards,
Manish

Hi
The Abap programs get a timeout when trying to update table PAT10 ( OCS Semaphore).
Check in SM12 if there are locks on that table
Check also that table contents, there should be only one entry, what is in field OCS_TOOL ?
DMIS should be installed using transaction SAINT (in client 000) and not SPAM.
Regards
1468391 - Installation and delta upgrade of DMIS 2010_1

ABAP short dump after BI upgrade

hi all,
While executing any program in SE38, it is giving Short dump while same program executing in SA38, it is executing .
Firstly, we got short dump in TCode - RSRT, while executing report.
Regards,
Prasad
Edited by: Prasad Mahindrakar on Apr 14, 2010 8:15 AM

Kindly find the Error, which is generating at time of Report Execution
Error Analysis:
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_PROGRAM_NOT_FOUND', was not
caught in
procedure "WRITE_DATA" "(METHOD)", 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:
On account of a branch in the program
(CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)
or a transaction call, another ABAP/4 program
is to be loaded, namely "GP42LSZTOVG57DGEB7BO763P3PN ".
However, program "GP42LSZTOVG57DGEB7BO763P3PN " does not exist in the library.
Possible reasons:
a) Wrong program name specified in an external PERFORM or
SUBMIT or, when defining a new transaction, a new
dialog module or a new function module.
b) Transport error

ABAP Short Dump - COMPUTE_BCD_OVERFLOW - CX_SY_ARITHMETIC_OVERFLOW

Runtime errors      COMPUTE_BCD_OVERFLOW
Exception              CX_SY_ARITHMETIC_OVERFLOW
I want to move Currency variable with 4 decimals to another currency variable with 2 decimals. Please advice me with a suitable solution without causing short dump.
Appreciate Your Help in Advance.
Thanks.
Kannan.

SAP catch the exception like this :
CATCH SYSTEM-EXCEPTIONS conversion_errors = 1
                                    arithmetic_errors = 5.
              xkwert = xkomv-kwert * 1000 * xkomv-kpein / komp-mgame.
              xkomv-kbetr = xkwert.
            ENDCATCH.
            IF sy-subrc = 1 OR sy-subrc = 5.
              xkomv-kbetr = 0.
              xkomv-fxmsg = '802'.
              komp-fxmsg = '802'.
            ENDIF.

Abap short dump

Hi BW experts,
when i goto to t-code st22, i find number of runtime errors with name of runtime error as " Message_type_X" and also when i open a msg it says "the current application detected a situation which really shld not occur. Therfore a termionation with a short dump .......""
Can anyone suggest whats happening?? Thank you
Dave

Hi Dave,
Now when you know the load has failed for the load you did from 1 infoprovider to other then go to the monitor of the failed request and then under status tab you will have short dump pushbutton at the bottom click on that which will take you to the dump after giving R/s ID and p/w there you check the error reason of the dump as said under error analysis.
Or go to RSMO there check out the load for today and try identifying the data target you loaded and then follow the above steps.
Hope it will help..
Regards,
Rohini

CP Segment - Missing Segments-BIGS2- abap short dump

hi,
i am facing a very typical problem, when i copy character set 8300 from 4.6c to ECC 6 and do the SCP, i have not problem in consistency check but when do the copy of 8300 ->9300 in 4.6c and then export to ECC6 and then run the SCP i have the error BIGS2 - Doesnot exits and when tried to check, it is throwing ABAP DUMP, please find the attached file for more detailed error update
I dont know how to attached the screen shot of the error, please let me know if any more information needed.

Hello,
as of WebAS 6.10. the structure of code pages changed.
For that reason, all customer defined code pages (i.e. code pages starting with 9) need to be converted to comply with the new structure, otherwise errors might occur. As you copied SAP Code Page 8300 to 9300, you have to convert this code page with report RSCP0126. Please refer to SAP Note 485455 for details. The application help in transaction SCP also contains a short description.
Hope this helps.
Best Regards,
Michaela

ABAP short dump when posting to FICO

We are testing payroll on a upgraded version of our live system and recieving an abap error stating an issue with object "COSTS" . This is only occuring when trying to post the results to FICO and only for one particular employee. On searching we have found SAP note 890828 which seems a rather larger problem than just affecting one employee.
Anyone have any idea's?

Hi
The ABAP dump should be as follows:
Runtime errors CONNE_IMPORT_WRONG_STRUCTURE
Exception CX_SY_IMPORT_MISMATCH_ERROR
Error when importing object "COSTS".
You need to follow the instructions in note 890828.
The CLASS CL_HR_PAY_RESULT_GB is used by RPCIPE00 in release your upgrade release
You have two choices in the note.
1) a modification in SAP standard to "ignore structure boundaries".
2) run the conversion program RPUSTRCL_COSTS.
Regards

Error "ERROR_PERIOD_VERSION" when loading DTP - Abap short dump

Hi,
I got this Error when loading with DTP. it occured in the transformation end routine.
I have this function module in my End routine. * REBW_FIRST_DAY_OF_PERIOD_GET*
Information on where terminated
    Termination occurred in the ABAP program "SAPLREBW_UTIL" - in
     "REBW_FIRST_DAY_OF_PERIOD_GET".
    The main program was "RSAWBN_START ".
    In the source code you have the termination point in line 41
    of the (Include) program "LREBW_UTILU03".
Source Code Extract
Line SourceCde
   11 *"     REFERENCE(E_SPERIOD) TYPE XFELD
   12 *" EXCEPTIONS
   13 *"      ERROR_PERIOD
   14 *"      ERROR_PERIOD_VERSION
   15 *"      FIRSTDAY_NOT_DEFINED
   16 *"      PERIOD_NOT_DEFINED
   17 *"----
   18 DATA:
   19     DATUM(8),
   20     TAG(2),
   21     IMONAT     TYPE I,
   22     JAHR       type rsfiscyear,
   23     DATE       type rscalday,
   24     PERZAHL(4) TYPE N,
   25     IRC(1)     TYPE N,
   26     ls_t009    like t009,
   27     ls_t009y   like t009y,
   28     ls_t009b   like t009b.
   29
   30 *
   31 * Version der Periodenermittlung nachlesen
   32 *
   33   IF I_FISCVAR NE ls_T009-PERIV.
   34     SELECT SINGLE * FROM T009
   35                     into ls_t009
   36                     WHERE PERIV = I_fiscvar.
   37     IF SY-SUBRC NE 0.
   38 *
   39 *     In Tabelle $ fehlt der Eintrag $
   40 *
>>>>>       RAISE ERROR_PERIOD_VERSION.
   42     ENDIF.
   43   ENDIF.
   44 *
   45 * Periode überprüfen
   46 *
   47   PERZAHL = ls_T009-ANZBP + ls_T009-ANZSP.
   48   IF I_FISCPER < 1 OR I_FISCPER > PERZAHL.
   49 *
does any knows how I can resolve it.
thanks

check table t009, it seems you have some entries missing (based on fiscal variant)
you can solve this, by going to the source system tree, right-click on your source system and choose transfer global settings.
you can transfer all settings now...
M.

Native sql DBCO, CONNECT statement short dump

Hi ALL ,
I am facing the problem here. please help me out in this.
i am trying to connce to the external database MSS, i made all the entries in the DBCO t-code and writing the follwoing native sql statement.
EXEC SQL.
CONNECT TO 'AAJ' AS 'V'
ENDEXEC.
EXEC SQL.
SET CONNECTION 'V'
ENDEXEC.
The above statement is not giving any error when i activate it but when i execute it is giving me shortdump error .
I already maintan   entries in DBCON table or DBCO t-code
And also tel me once it is connect how can i access the data from MSS (Microsoft sql server)i mean what kind of statement.
helpfull answer will be rewarded.
Anees
9886358645
Message was edited by:
        anees jawad

Native SQL
Open SQL allows you to access database tables declared in the ABAP Dictionary regardless of the database platform that you R/3 System is using. Native SQL allows you to use database-specific SQL statements in an ABAP program. This means that you can use database tables that are not administered by the ABAP Dictionary, and therefore integrate data that is not part of the R/3 System.
As a rule, an ABAP program containing database-specific SQL statements will not run under different database systems. If your program will be used on more than one database platform, only use Open SQL statements.
Native SQL Statements in ABAP Programs
To use a Native SQL statement, you must precede it with the EXEC SQL statement, and follow it with the ENDEXEC statement as follows:
EXEC SQL [PERFORMING )
The parameters are separated by commas. You must also specify whether the parameter is for input (IN), output (OUT) or input and output (INOUT). For further information, refer to SAP Note 44977.
EXEC SQL
   EXECUTE PROCEDURE proc1 ( IN , OUT :y )
ENDEXEC.
Cursor Processing
Cursor processing in Native SQL is similar to that in Open SQL:
OPEN
ENDIF.
ENDDO.
EXEC SQL.
CLOSE c1
ENDEXEC.
This example opens a cursor, reads data line by line, and closes the cursor again. As in Open SQL, SY-SUBRC indicates whether a line could be read.
Data Types and Conversions
Using Native SQL, you can
Transfer values from ABAP fields to the database
Read data from the database and process it in ABAP programs.
Native SQL works without the administrative data about database tables stored in the ABAP Dictionary. Consequently, it cannot perform all of the consistency checks used in Open SQL. This places a larger degree of responsibility on application developers to work with ABAP fields of the correct type. You should always ensure that the ABAP data type and the type of the database column are identical.
If the database table is not defined in the ABAP Dictionary, you cannot refer directly to its data type. In this case, you should create a uniform type description in the ABAP Dictionary, which can then be used by all application programs.
If the table is defined in the ABAP Dictionary, you should remember that the sequence of fields in the ABAP Dictionary definition may not be the same as the actual sequence of fields in the database. Using the asterisk (*) in the SELECT clause to read all columns into a corresponding work area would lead to meaningless results. In the worst case, it would cause an error.
The Native SQL module of the database interface passes a description of the type, size, and memory location of the ABAP fields used to the database system. The relevant database system operations are usually used to access and convert the data. You can find details of these operations in the manuals for the programming interface of the relevant database system. In some cases, Native SQL also performs other compatibility checks.
The documentation from the various database manufacturers provides detailed lists of combinations of ABAP data types and database column types, both for storing ABAP field values in database tables (INSERT, UPDATE) and for reading database contents into ABAP fields (SELECT). You can also apply these descriptions for the input and output parameters of database procedures. Any combinations not listed there are undefined, and should not be used.
The following sections provide details of the data types and conversions for individual databases. Although they are database-specific, there are also some common features.
Recommended type combinations are underlined. Only for these combinations is behavior guaranteed from release to release. For any other combinations, you should assume that the description only applies to the specified release.
The results of conversions are listed in a results column:
"OK": The conversion can be performed without loss of data.
Operations that fail are indicated by their SQL error code. Errors of this kind always lead to program termination and an ABAP short dump.
In some cases, data is transferred without an SQL error occurring. However, the data is truncated, rounded, or otherwise unusable:
Right truncation.
"Left" or "right" applies to the normal way of writing a value. So, for example, if a number is truncated, its decimal places are affected.
: Left truncation
: Number is rounded up or down during conversion
: A number that was "too small" is rounded to 0 (underflow)
: The conversion result is undefined.
There are several possible results. The concrete result is either not known at all, or can only be described using a set of rules that is too complicated for practical use.
: The conversion returns the SQL value NULL.
: The conversion is performed without fields and unchecked.
The original data is converted, but without its format being checked. The result may therefore be a value invalid for the result type, which cannot be processed further. An example of this is a date field containing the value "99999999" or "abcdefgh" after conversion.
Combinations of ABAP data type and database column type can be divided into finer subcategories. Here, for example, using the transfer direction ABAP ® database (INSERT, UPDATE):
If the width of the ABAP field is greater than that of the database column, the ABAP field may contain values for which there is not enough space in the database column. This can produce other cases: The concrete data value in ABAP finds space in the database column, or not.
If the ABAP field is at most as long as the database column, there is always space for the ABAP value in the database column.
Some types, such as numeric columns, expect values in a particular format. This is particularly important in connection with character types, for example, when you want to write an ABAP character field (type C) into an integer column.
Native SQL for Oracle
Native SQL for Informix
Native SQL for DB2 Common Server
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3b8b358411d1829f0000e829fbfe/content.htm

Short Dump While creating a Value Driver Tree

Hi all,
I am trying to create a value driver tree in CPM. i am on SEM verion 3.1b. I am able to create the value driver tree but when i goto the graphical view it generates a ABAP short dump. does anybody have any idea on this

hi srini,
Elaborate it clearly .
Regards ,
Muneeh Gitta.

Short dump with TPM_TRD1 000

hi everyone,
when I run the Tcode:TBB1，i come across a ABAP short dump error.
my system environment is:
PC
windows2003NT
oracle10.2
independant system without SLD control
The error info as follow:
Note 837202 - TPM_MIGRATION:tpm18: Short dump with TPM_TRD1 000
Summary
Symptom
You migrate from Release CFM or Enterprise 1.10 to ERP 2.0 or higher. There are already parallel valuation areas in use. In tpm_migration_cat, you specify a key date. In the test system, the following short dump occurs for the parallel valuation areas:
Error message short text:
Internal error: SLD
Message class: "TPM_TRD1"
Number: 000
Variable 1: "SLD"
Other terms
CL_DISTRIBUTOR_SLD, TPM_TRD1000
Solution
In the production system, you have to carry out tpm18 before the technical upgrade for all business transactions that are before the key date from tpm_migration_cat.
I do not understand how to do with the soluton
eg.what is "tpm18"?
Do need your helps,
Thank you very much
Peter

Hi Peter,
I guess you found note 837202 when you were looking for a solution for the TBB1 dump you encountered.
This note deals with a special situation when executing tpm18 (which is the transaction for fixing and posting derived flows) in a test system after migration and it tells you you should run tpm18 in production before the technical upgrade.
I am not sure if this really applies to your situation, maybe you should rather check if note 821854 and the solution therein can be helpful.
But without more information (e.g. knowing more about your release, your 'migration history' and the part of the coding where the dump is raised), it is quite difficult to give a diagnosis.
Maybe you should think of sending a customer message to SAP support via the SAP marketplace if you cannot get rid of this problem on your own.

ZGUIXT16 produces an ABAP short dump

Similar Messages

Maybe you are looking for