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

Similar Messages

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

Facing short dumps when trying to open session in CSA

Hi
All am facing Short dump when i am trying to open session in CSA
Error detials:
go to System Administration workcenter task management up CSA. Choose the Solution
got short dump:
Short text
    Length error occurred in IMPORT statement.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
     not caught in
    procedure "LOAD" "(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:
    During import the system discovered that the target object has
    a different length than the object to be imported.
Missing RAISING Clause in Interface
    Program                                 SAPLDSVAS_PROC
    Include                                 LDSVAS_PROCTAI
    Row                                     1.431
    Module type                             (METHOD)
    Module Name                             LOAD
Trigger Location of Exception
    Program                                 SAPLDSVAS_PROC
    Include                                 LDSVAS_PROCTAI
    Row                                     1.514
    Module type                             (METHOD)
    Module Name                             LOAD
Please help me to solve this problem
Regards,
Neni

Hello Neni
According to the information I saw in that post it could be caused by a sort of inconsistency of the program code vs a structure.
Wether that is a bug that is in your SAP Solution Manager release or something that is caused by administrative actions (perhaps solving SPAU entries after SP stack update or upgrade) I cannot tell.
I would recommend you either try and find a relative SAP note (narrowing down result to only your SAP Solution Manager system) and searching using the dump keywords. If you cannot find anything I would recommend you to open a customer message so SAP can take a look at the specific error.
If you give more information, perhaps someone on the forum can help you out abit better, which SAP Solution Manager version and so on.
You also didn't answer my question, any recent changes you are aware of ?
Kind regards
Tom

Short Dump when the Bex-Report scheduled for Broadcast

Hi Guru's
I am getting the short dump when I am scheduling the Bex-Report for Broadcasting. Need your help to reslove this issue.
Thanks
Navin
Note
The following error text was processed in the system BDV : The current application triggered a termination with a short dump.
The error occurred on the application server spdbwd01_BDV_05 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Form: INTERNAL_ERROR of program SAPLSDCL
Form: PHIO_GET_CONTENT_ACCESS of program SAPLSDCI
Function: SDOK_PHIO_GET_CONTENT_ACCESS of program SAPLSDCI
Function: SKWF_PHIO_CONTENT_ACCESS_GET of program SAPLSKWF_CONTENT
Method: COPY_MIME_TO_FOLDER of program CL_RSRA_KWF_UTILITIES=========CP
Method: GET_STYLESHEET of program CL_RSRA_KWF_TMPL==============CP
Method: CONSTRUCTOR of program CL_RSRA_KWF_TMPL==============CP
Method: SET_TEMPLATE_FOLDER of program CL_RSRA_ENGINE_BC=============CP
Method: CONSTRUCTOR of program CL_RSRA_ENGINE_BC=============CP
Method: EXECUTE_SINGLE of program CL_RSRA_JOB===================CP

HI Navin,
Check the short dump analysis in T-code ST22.
and also check the Information Broadcast Settings / Configuration
Check the error for Emails in t-code SCOT. BASIS Consultants will help you on this issue.
Regards
Daya Sagar

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

ASSERTION_FAILED short dump when Transporting Transformation from Dev to QA

Hi Experts,
I' am getting a short Dump when transporting the transformations, DSO & DTPs from Dev server to QA.
I got RC=12, Please have a look below....
Transport log...
    BCQ        System BCQ
               Selection for Import                     08.07.2010 15:28:59    (0) Successfully Completed
               Import                                   08.07.2010 15:35:14    (0) Successfully Completed
               Check Versions                           08.07.2010 15:35:14    (0) Successfully Completed
               Method Execution                         08.07.2010 15:36:20   (12) Canceled
               Import                                   08.07.2010 15:45:39    (0) Successfully Completed
               Check Versions                           08.07.2010 15:45:39    (0) Successfully Completed
               Method Execution                         08.07.2010 15:46:45   (12) Canceled
and the Log detalis.....
Date        Time      Message
08.07.2010 15:35:15 Job started
08.07.2010 15:35:15 Step 001 started (program RDDEXECL, variant , user ID DDIC)
08.07.2010 15:35:15 All DB buffers of application server sxcat136 were synchronized
08.07.2010 15:35:21 STDO: Log could not be written on output device T
08.07.2010 15:35:30 Replication completed successfully
08.07.2010 15:35:31 Struttura di comunicazione /BIC/CS8ZFIZIASA activated
08.07.2010 15:35:40 Regola(e) di trasm. 8ZFIZIASA_AA activated
08.07.2010 15:35:47 ABAP/4 processor: ASSERTION_FAILED
08.07.2010 15:35:47 Job cancelled
Even I've checked the entries on the table RSTRANRULE for those Transpormations but there I got...all the entries with...
RULEID = all numbers
GROUPID = '1' or '2'
GROUPTYPE = 'S' or 'T'
REF_RULE ='0'
we are in to SAP_BW Release 700, Level 0013, SP -SAPKW70013, SAP NetWeaver BI 7.0
Pls help if any one know's the solution for this.
Thanks in adv.
BR,
Ajay Kumar
Edited by: sap.ajaykumar on Jul 9, 2010 12:48 PM

Follow the steps mentioned in OSS note 998730.
FYI.. Solution:
Call transaction SE16 (Table Browser) and the 'RSTRANRULE' table with the following selection parameters:
GROUPID = 'space'
GROUPTYPE = 'space'
REF_RULE 'space'
If there are inconsistent entries in the RSTRANRULE table such as this:
TRANID *
OBJVERS *
RULEID *
SEQNR *
GROUPID 00
GROUPTYPE space
RULETYPE space
REF RULE *
Delete these entries from the table.
Activate the affected transformations.
Also check the OSS note: 1006658.
Follow the steps mentioned in OSS note 998730.
FYI.. Solution:
Call transaction SE16 (Table Browser) and the 'RSTRANRULE' table with the following selection parameters:
GROUPID = 'space'
GROUPTYPE = 'space'
REF_RULE 'space'
If there are inconsistent entries in the RSTRANRULE table such as this:
TRANID *
OBJVERS *
RULEID *
SEQNR *
GROUPID 00
GROUPTYPE space
RULETYPE space
REF RULE *
Delete these entries from the table.
Activate the affected transformations.
Also check the OSS note: 1006658.
Follow the steps mentioned in OSS note 998730.
FYI.. Solution:
Call transaction SE16 (Table Browser) and the 'RSTRANRULE' table with the following selection parameters:
GROUPID = 'space'
GROUPTYPE = 'space'
REF_RULE 'space'
If there are inconsistent entries in the RSTRANRULE table such as this:
TRANID *
OBJVERS *
RULEID *
SEQNR *
GROUPID 00
GROUPTYPE space
RULETYPE space
REF RULE *
Delete these entries from the table.
Activate the affected transformations.
Also check the OSS note: 1006658.
Also check the oSS note : Note 975675 - Transformation cannot be activated

Short Dump When Installing Key Figure Catalog from BI Content

Hi Friends,
I get a Short dump when trying to Install a Key Figure Catalog (in Purchasing) from the BI content. This is what the Error Says ,
" You Attempted to Use a "NULL" object reference (Points to nothing) access a component (variable : " "). An Object reference must point to an object (an instance of class ) before it can be used to access components.
Any input will be greatly appreciated,

Hi Michal,
this bug hits only patch level 201 of the DBSL. Please update the DBSl.
Regarding the ABAP code I do not believe that the hint helps in this case but it should not cause any problems either. If this hint is applied more PREPARE calls are neccessary since before every execution a new statement text is assembled.
The advantage of SUBSTITUTE_VALUES hints is that the database optimizer get more information through the statement text. The downside is that a new statement is generated every time. E.g. you won't find the statement as a top scorer in a SQL cache analysis if the access plan is still bad.
Regards
Frank

Short Dump when trying to open C-project due to status

Hi,
We have a daily batch job in CRM that reports all the project ID's and
sends e-mails out to recipients.
As part of this report it retrieves the statuses for the project ID's,
however the report short dumps when retrieving the status for one of
the projects because it is not finding an active status.
When we try and open the project in C-projects we get the same short
dump error: CX_DPR_FATAL_ERROR so we cannot view or update the status.
When we investigate this issue we find that in table CRM_JCDS there are
3 entries for this project ID. One of the statuses is inactive (I1703)
but there is another status that is active (I1701). The two status
entries were created at exactly the same date and time and by the same
user.
In table CRM_JEST there is only one entry shown which shows an inactive
status and we believe this to be the wrong status. Please can you
advise if this status conflict is causing the problem and also how to
resolve this issue?

Hi Paul,
generally, the project and its elements must have an active status in table CRM_JEST, however, at this point it is not clear how this inconsistency arised. There is no SAP standard report or a 'generally valid' solution that could solve this issue, however, I found a customer message that you have opened in September with exactly the same problem. A colleague from the development team already provided you with a correction report, but there was no feedback from your side if it helped or not.
It is very difficult to provide help as inconsistencies can have several different causes, so the best would be to have this checked in a customer message with an example.
Regards,
Silvia

GETWA_NOT_ASSIGNED short dump when load business partner master data

Hi
I've this error GETWA_NOT_ASSIGNED short dump when load business partner master data, it's running in BI 7.0 with support package 12.
The error is because the field symbol is that pointed to the line of an internal table that was deleted.
I think that it's an incompatibility between subroutine and unicode.
Do you have idea about correct this error?
Regards
Jose.

Hi Ravi
Yes, it's a dump
It's when running a process chain to load Business partner master data
The error say:
-.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 exist.
-. 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.
I think that it's for the unicode corversion because I've the last support package 12 installed and the rest of the process chain are running perfect.
My hotmail mail is [email protected] if you need the screen shot.
Regards and thanks a lot
Jose

Short dump when we write more than 4 routines or formulas 4 one source fld

Hi Experts ,
We have one source field in a DSO which supplies data to 9 other characteristics present in the cube via formulas. But the system throws a short dump when we write more than 4 routines or formulas.
Please let us know if there is any restriction in BI 7 as to let only 4 formulas to be written for one source field.
The below is the description of the short dump
RUNTIME ERROR : SAP SQL_ARRAY_INSERT_DUPREC
EXCEPTION : CX_SY_OPEN_SQL_DB
Help done would be assigned points ...
Thanks,
Santosh ...

Hi,
thanks for your input
Rd, rt,re and rs are ranges.
Select ranges
RANGES: rd FOR ZMOBILEDATA-COMPID,
          rs FOR ZMOBILEDATA-SUBSCRIBERS,
          rt FOR ZMOBILEDATA-TURNOVER,
          re FOR ZMOBILEDATA-ENTRYDATE.
thanks'

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.

Short dump when assigning revision to notification (iw22)

Hello!
We have a short dump when we try to assign a revision to a notification in iw22.
The dump occurs when we save after assigning a revision. We have the lollowing message:
Message CO888 : Error when reading order header with index
Include LCOBHIC2, line 39
The OSS note 1101437 doesn't solve our problem.
Can you help me?
Thanks by advance,
Laurent.

I tried your tests.
I haven't a dump neither for the first test nor for the second one.
The dump occurs only when:
- I create a notification
- i create an order and assign it to this notification.
- i save the notification and the order
- i assign a revision to the notifiaction and save
There isn't dump if i assign revision number before the order creation. In fact, the dump only occurs if a assign a revision number after the assignment of the order to the notifiation.
I'm checking user exit.
Thanks,
Laurent.

Screen dump when posting debit balances to an expense account

dear experts.
A screen dump is produced when saving or posting debit balances to expense accounts for only certain periods and for a certain fiscal year in this case year 2006. what might be the problem. can the problem be solved form the ABAP side or FI side?
its urgent

below is part of the screen dump:
ABAP/4 runtime error                                                            DBIF_RSQL_SQL_ERROR
                    Occurred on                                        26.02.2007                              at          08:26:04
>> Short dump has not been completely stored. It is too big.
SQL error 1438 occurred when accessing table "GLT0 ".
What happened?
When writing a data record to the database (i.e. when
updating the database), only part of the data field was
written (updated). The rest was truncated.
What can you do?
If the error occurred in Open SQL, there is probably an inconsistency
between the NAMETAB and the ABAP/4 Dictionary.
Compare the length specifications of the fields in the NAMETAB with
those in the ABAP/4 Dictionary and contact someone who is able to
perform a consistency check and eliminate the problem.
In most cases, this person will be your SAP consultant.
Please make a note of the actions and input which caused the error.
To resolve the problem, contact your
SAP system administrator.
Select the "Print" function to obtain a hardcopy of the
current termination message.
Error analysis
The problem has arisen because, within the database interface,
one of the data buffers made available for the INSERT (UPDATE)
is longer than the maximum defined in the database.
On the other hand, it may be that the length in the NAMETAB
does not match the maximum length defined in the database.
(In this case, the length in the NAMETAB is longer.)
How to correct the error
Database error text........: "ORA-01438: value larger than specified precision
allows for this column?"
Internal call code.........: "[RSQL/UPDT/GLT0 ]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem in the
SAP note system. If you have access to the SAP note system yourself,
please use the following search criteria:
"DBIF_RSQL_SQL_ERROR"
"SAPLGIVA" or "LGIVAF10"
"UPDATE_TT_GLT0"
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.............. "31H"
Application server....... "umprod"
Network address.......... "10.1.1.9"
Operating system......... "Windows NT"
Release.................. "0"
Hardware type............ "PENTIUM"
Database server.......... "UMPROD"
Database type............ "ORACLE"
Database name............ "UMP"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "31I"
Created on............... "Jun 21 1999 04:44:28"
Created in............... "NT 4.0 1381 Service Pack 3 x86"
Database version......... "ora OCI_73211"
Patch level.............. "315"
Patch text............... " "
Supported environment....
Database................. "ORACLE 7.2..., ORACLE 7.3..., ORACLE
8.0...*"
SAP database version..... "31I"
Operating system......... "Windows NT 51 3, Windows NT 0 4"
User, transaction...
Client.............. 600
User................ "HAVIREO"
Language key........ "E"
Transaction......... "FB01"
Program............. "SAPLGIVA"
Screen.............. "RSM130003000"
Screen line......... 2
Information on where termination occurred
The termination occurred in the ABAP/4 program "SAPLGIVA" in
"UPDATE_TT_GLT0".
The main program was "RSM13000".
The termination occurred in line 542
of the source code of program "LGIVAF10" (when calling the editor 5420).
The program "SAPLGIVA" was started in the update system.
Source code extract
005120                               HSL10 = HSL10 + TAB_GLT0-HSL10
005130                               KSL10 = KSL10 + TAB_GLT0-KSL10
005140                               TSL11 = TSL11 + TAB_GLT0-TSL11
005150                               HSL11 = HSL11 + TAB_GLT0-HSL11
005160                               KSL11 = KSL11 + TAB_GLT0-KSL11
005170                               TSL12 = TSL12 + TAB_GLT0-TSL12
005180                               HSL12 = HSL12 + TAB_GLT0-HSL12
005190                               KSL12 = KSL12 + TAB_GLT0-KSL12
005200                               TSL13 = TSL13 + TAB_GLT0-TSL13
005210                               HSL13 = HSL13 + TAB_GLT0-HSL13
005220                               KSL13 = KSL13 + TAB_GLT0-KSL13
005230                               TSL14 = TSL14 + TAB_GLT0-TSL14
005240                               HSL14 = HSL14 + TAB_GLT0-HSL14
005250                               KSL14 = KSL14 + TAB_GLT0-KSL14
005260                               TSL15 = TSL15 + TAB_GLT0-TSL15
005270                               HSL15 = HSL15 + TAB_GLT0-HSL15
005280                               KSL15 = KSL15 + TAB_GLT0-KSL15
005290                               TSL16 = TSL16 + TAB_GLT0-TSL16
005300                               HSL16 = HSL16 + TAB_GLT0-HSL16
005310                               KSL16 = KSL16 + TAB_GLT0-KSL16
005320                           WHERE
005330                           RLDNR                   = TAB_GLT0-RLDNR                  AND
005340                           RRCTY                   = TAB_GLT0-RRCTY                  AND
005350                           RVERS                   = TAB_GLT0-RVERS                  AND
005360                           BUKRS                   = TAB_GLT0-BUKRS                  AND
005370                           RYEAR                   = TAB_GLT0-RYEAR                  AND
005380                           RACCT                   = TAB_GLT0-RACCT                  AND
005390                           RBUSA                   = TAB_GLT0-RBUSA                  AND
005400                           RTCUR                   = TAB_GLT0-RTCUR                  AND
005410                           DRCRK                   = TAB_GLT0-DRCRK                  AND
          >                 RPMAX                   = TAB_GLT0-RPMAX                  .
005430                         ENDFORM.
005440                         *eject
005450                         *                                                                                                                                            *
005460                         *
005470                         *                                                                                                                                            *
005480                         *         FORM UPDATE_TT USING UTP_TAB.
005490                         *         Diese Form fuehrt die Tabellenupdates durch
005500                         *         Dabei wird die optimierte Form von UPDATE
005510                         *         verwendet
005520                         *                                                                                                                                            *
005530
005540                         FORM UPDATE_TT_GLT3      .
005550                           DATA: W_0 LIKE GLU1-TSL VALUE 0.
005560                           UPDATE GLT3
005570                           SET TSLVT = TSLVT + TAB_GLT3-TSLVT
005580                               HSLVT = HSLVT + TAB_GLT3-HSLVT
005590                               KSLVT = KSLVT + TAB_GLT3-KSLVT
005600                               TSL01 = TSL01 + TAB_GLT3-TSL01
005610                               HSL01 = HSL01 + TAB_GLT3-HSL01

ABAP short dump when posting to FICO

Similar Messages

Maybe you are looking for