Report J_1IEWT_CERT getting cancelled, generating ABAP dump!

A long running report J_1IEWT_CERT in background mode is getting cancelled after running for a while and generating the following dump :
Error analysis
    When changing or deleting one or more lines of the internal table
    "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]" or when inserting in the table
     "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]", 0 was used as
    the line index. An index less than or equal to zero is not
    allowed.
    The error can occur when using the following options:
    1. "INDEX idx" for specifying the line number in the table
     "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]"
       where you want to change, insert or delete.
    2. "FROM idx" for specifying the start index when deleting a line
       area from or inserting a line area into the table
     "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]".
    3. "TO idx" for specifying the end index when deleting a line
       area from or inserting a line area into the table
     "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]".
    At the time of the termination, the table contained 17008 lines.
How to correct the error
    If the error occurred in your own ABAP program or in an SAP
    program you modified, try to remove the error.
    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:
    "TABLE_INVALID_INDEX" " "
    "J_1IEWT_CERT" or "J_1IEWT_CERT_F01"
    "FILTER_DATA"
    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".
Tried searching for some SAP Notes to fix the issue, no success as of now, Please help me out...

Have you checked these notes ?
363107 Short dump occurs during TDS certificate printing.
803806 Error while genrating TDS certificate 03.01.2005
1066049 J1INCERT - Error while generating TDS certificate
Regards,
Subhash

Similar Messages

SAP job SAP_COLLECTOR_FOR_PERFMONITOR getting failed with abap dump LOAD_PROGRAM_NOT_FOUND

Dear Experts,
Background job SAP_COLLECTOR_FOR_PERFMONITOR getting failed with abap dump LOAD_PROGRAM_NOT_FOUND.
As it is hourly scheduled job and it gets finished 22 times in a day but other 2 times fails with abap dump.
Finished Job log
Job started
Step 001 started (program RSCOLL00, variant , user ID Bharath)
Clean_Plan:Cleanup of DB13 Plannings
Clean_Plan:started by RSDBPREV                       on server
Clean_Plan:Cleaning up jobs of system DEV
Clean_Plan:finished
Job finished
Failed Job Log
Job started
Step 001 started (program RSCOLL00, variant , user ID Bharath)
Internal session terminated with a runtime error (see ST22).
Kindly suggest on this..
Thanks,
Bharath.

Dear Divyanshu,
Our system in ERP 6.0 EHP5 with SP level 10. The ABAP Dump shows below error.
|Short text                                                                                        |
|    Program "RSORA811" not found.                                                                 |
|What happened?                                                                                    |
|    There are several possibilities:                                                              |
|                                                                                                  |
|    Error in the ABAP Application Program                                                         |
|                                                                                                  |
|    The current ABAP program "RSCOLL00" had to be terminated because it has                       |
|    come across a statement that unfortunately cannot be executed.                                |
|    or                                                                                            |
|    Error in the SAP kernel.                                                                      |
|                                                                                                  |
|    The current ABAP "RSCOLL00" program had to be terminated because the                          |
|    ABAP processor detected an internal system error.                                             |
|What can you do?                                                                                  |
|    Note down which actions and inputs caused the error.                                          |
|                                                                                                  |
|                                                                                                  |
|    To process the problem further, contact you SAP system                                        |
|    administrator.                                                                                |
|                                                                                                  |
|    Using Transaction ST22 for ABAP Dump Analysis, you can look                                   |
|    at and manage termination messages, and you can also                                          |
|    keep them for a long time.                                                                    |
|Error analysis                                                                                    |
|    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 "RSORA811".                                                           |
|                                                                                                  |
|    However, program "RSORA811" 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                                                                            |
|Information on where terminated                                                                   |
|    Termination occurred in the ABAP program "RSCOLL00" - in                                      |
|     "LOOP_AT_SYSTEMS_AND_REPORTS".                                                               |
|    The main program was "RSCOLL00 ".                                                             |
|                                                                                                  |
|    In the source code you have the termination point in line 535                                 |
|    of the (Include) program "RSCOLL00".                                                          |
|    The program "RSCOLL00" was started as a background job.                                       |
|    Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"                                               |
|    Job Initiator.. " bharath"                                                                       |
|    Job Number..... 18243400
Kindly check and suggest..
Thanks,
Bharath.

Job getting cancelled with Tbale_illegal_statement dump

hello,
Hi Experts,
i have a background job scheduled for a standard transaction SARA .it is getting cancelled and giving the following error:
"TABLE_ILLEGAL_STATEMENT"
Information on where terminated
The termination occurred in the ABAP program "SAPLCKMLLAARCH" in
"CKMLLA_INIT_READ".
The main program was "RKSARCDL ".
The termination occurred in line 253 of the source code of the (Include)
program "LCKMLLAARCHF01"
of the source code of program "LCKMLLAARCHF01" (when calling the editor 2530).
The program "SAPLCKMLLAARCH" was started as a background job.
The line it is giving Dump Is > INSERT handle_tab.
I have tried to debug the transaction but the execution is not ata all going to the program
SAPLCKMLLAARCH where it is giving dump.Propably because that program is running in Background.
So please let me know how I can fix this issue..Please

Hi Prashanth,
Were you able to resolve the issue ? Because, i am also facing the same problem, when I am triggering the Delete step for CO_CCMAST archiving object.
Regards,
Shail.

RDDGENOL job getting cancelled with huge number of ABAP dumps

Hi,
In our Production system, we had applied Kernel upto patch level 263 and while
applying SPAM 30 for release 640 it failed. We tried applying Basis patch 15 still
it did not went through.
Since then we are getting around 1500-2500 dumps daily. The job RDDGENOLis getting cancelled and the dumps RAISE_EXCEPTION and SYNTAX_ERROR is displayed in ST22. Today, there were around 2500 dumps in the system.
When I now run the Database <-> ABAP Dictionary consistency check in
DB02, I see number of errors for missing objects in the database. There
are around of dozens of Primary Indexes, secondary Indexes, Tables,
Views listed in the result:
Objects Missing in database No.
=========================== ===
Primary indexes 6
Secondary indexes 14
Tables 37
Views 26
When I try to create each of them using SE16 or using SQL utility on OS
level, it gives an SQL system error. We are also getting thousands of
dumps each day (attached alongwith this message). Also I see the CPF327E error
in the OS Level Joblog.
Also we cannot transport any requests. There is some problem with or
due to the conversions. Is it a problem with Kernel, ABAP dictionary or
database.
Following is the extract of the dumps due to DDIC in 000:
============================================================
Runtime Error          SYNTAX_ERROR
Date and Time
ShrtText
Syntax error in program "CL_WB_CROSSREFERENCE==========CP ".
What happened?
Error in ABAP application program.
The current ABAP program "SAPLSEWB" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
In program "CL_WB_CROSSREFERENCE==========CP ", the following syntax error
occurred
in the Include "CL_WB_CROSSREFERENCE==========CM00D " in line 8:
|    "The type "KEYWORD_TAB" is unknown."
============================================================
============================================================
Runtime Error          RAISE_EXCEPTION
Date and Time
ShrtText
Exception condition "DESTINATION_NOT_OPEN" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
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.
is especially useful if you want to keep a particular message.
Error analysis
A RAISE statement in the program "SAPLCRFC" raised the exception
condition "DESTINATION_NOT_OPEN".
Since the exception was not intercepted by a superior program
in the hierarchy, processing was terminated.
Short description of exception condition:
Specified destination is not open.
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
How to correct the error
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:
"RAISE_EXCEPTION" C
"SAPLCRFC" or "LCRFCU20"
"RFC_CONNECTION_CLOSE"
or
"SAPLCRFC" "DESTINATION_NOT_OPEN"
or
"RADBAT01 " "DESTINATION_NOT_OPEN"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "640"
Application server....... "TXTPDSAP"
Network address.......... "172.16.0.140"
Operating system......... "OS400"
Release.................. "5.3"
Hardware type............ "0065000655EC"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 35
Short dump setting....... "full"
Database server.......... "TXTPDSAP"
Database type............ "DB400"
Database name............ "TXT"
Database owner........... "R3TXTDATA"
Character set............ "en_US.ISO8859-1"
SAP kernel............... "640"
Created on............... "Dec 11 2008 23:06:45"
Created in............... "AIX 1 5 00538A4A4C00 (IBM iSeries with OS400)"
Database version......... "DB4_52"
Patch level.............. "263"
Patch text............... " "
Supported environment....
Database................. "V5R2, V5R3, V5R4, V6R1"
SAP database version..... "640"
Operating system......... "OS400 2 5, OS400 3 5, OS400 4 5, OS400 1 6"
Memory usage.............
Roll..................... 696832
EM....................... 16759712
Heap..................... 0
Page..................... 32768
MM Used.................. 1383120
MM Free.................. 3483600
SAP Release.............. "640"
User and Transaction
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Program............. "SAPLCRFC"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "SAPLCRFC" in
"RFC_CONNECTION_CLOSE".
The main program was "RADBAT01 ".
The termination occurred in line 22 of the source code of the (Include)
program "LCRFCU20"
of the source code of program "LCRFCU20" (when calling the editor 220).
The program "SAPLCRFC" was started as a background job.
Job name........ "RDDGEN0L"
Job initiator... "DDIC"
|    Job number...... 00032101
============================================================
Kindly let me know the immediate fix. Thanks!
Regards,
Nick

Hi Nick,
I would say, you are having a slight missperception of this forum ... it should not replace your basis ressources in your company.
What you are doing is pretty complex (and the mixtrure of SPAM Update AND Basis SP seems to be wrong to me) and therefore, it will not be possible, to help you, just based on such a short dump.
Sorry,
Volker Gueldenpfennig, consolut international ag
http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

GR55 Report / Abap Dump

Hello,
I'm working on issue where I have two users who are executing the same transaction but getting back different results. One users gets back the output of the report another gets back an abap run time errror.
The run time error for short text reads, " Time limit exceeded"
I thought this was due to missing authorization however I ruled this out when I tried running this report under my profile that has sap_all & sap_new and got an abap dump error indicating time limit exceeded.
The transaction i'm running is GR55, once there I choose the report group. Next screen i enter in the year and period. I using period 1 which is one month of data and I still get the dump. The user who can run this report goes up to 9 periods and gets an output every time.
I can run this same report in our Q/A without any issues. I pulled the dump in ST22 and from reading it appears the paremeter for rdisp/max_wprun_time is set to 1200 secs and when I run this report i'm exceeding 1200secs which triggers the dump.
This all make sense however I don't understand how one user doesn't run into the same issue and one does.

GR55 is not performance optimized coding. It is only "best guess coding"...
Your production system might have more data (or even other config, if there are inconsistencies...).
Additionally, the load balancing is might be different (with the server instances having different instance profiles)?
If the user has the ability to schedule jobs with different priorities in PRD, then this can also have an effect.
I dont think this is security related (does not make sense, unless the ABAPers did something stupid...) so I take the liberty of moving it to the NW Admin forum...
Cheers,
Julius

Thousands of abap dumps RFC_NO_AUTHORITY

Hello All,
Today suddenly we are getting thousands of abap dumps in Prdocution system and the details are below :
RFC_NO_AUTHORITY
What happened?
    The user "PLIM" attempted to execute a function module from
    the function group "SDIFRUNTIME", but does not have the appropriate
    RFC authorization.
    Error in the ABAP Application Program
    The current ABAP program "SAPLSDIFRUNTIME" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    The ABAP program "SAPLSDIFRUNTIME" attempated to execute a statem
    the system automatically checks authorizations and for which the
    user "PLIM" has no authorization.
    The application program did not take the missing authorization
    into consideration and the program must therefore be terminated.
And we checked the RFC conncection and its fine.
Please help me to resolve this ASAP as its an high priority issue.
Chinna.

hi,
Please check the following
http://help.sap.com/saphelp_nw04s/helpdata/en/9b/ac6440549ac249e10000000a1550b0/content.htm
and also provide the user with full RFC authorizations.
Thanks
Suresh Aithagani

ABAP Dump ASSIGN LENGTH 0 SAPLSNR3 LOCAL Buffer - BI content installation

Hi all,
I get the following ABAP dump while installing the BI content and choosing the grouping ' in dataflow before' in Bi 7.0 SP 13
Short text
    Program error: ASSIGN with length 0 in program "SAPLSNR3".
Error analysis
     In an ASSIGN statement in the program "SAPLSNR3" a field symbol with
     length 0 should have been created. However, this is not possible.
     length 0. This is not possible     s
Trigger Location of Runtime Error
     Program                                 SAPLSNR3
     Include                                 LSNR3F01
     Row                                     178
     Module type                             (FORM)
     Module Name                             LOCAL_BUFFER
How to correct the error
    If the error occurred in your own ABAP program or in an SAP
    program you modified, try to remove the error.
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:
"ASSIGN_LENGTH_0" " "
    "SAPLSNR3" or "LSNR3F01"
    "LOCAL_BUFFER"
I did search for the same error discussion in the forum. However most of them are dealing with "LOCAL_ENTRY_EXISTS" while this dump is related to "LOCAL_BUFFER".
Kindly let me know if anyone has similar issue and got it resolved.
Thanks in advance
Kee

For anyone who come across the same error - here is the solution.
Assign the number ranges for objects
BI_TS , BI_TSDTEL, BI_TSDOMA and BI_CS in tcode SNUM as below
No. From Number To Number      Currenct Number
01    0000000001    9999999999    1
You can surpass this error.
Thanks
Kee

ABAP Dump when calling Function Module Starting New Task

Hi all. I have a tricky situation now, I am doing a POC on parallel processing.
I am getting an ABAP dump on the following Call Function line which is in class lcl_steer_114numc (See below for full program):
METHOD start.
    CALL FUNCTION 'Z_ZZCLS_STEER_114NUMC'
      STARTING NEW TASK me->id
      CALLING me->finish ON END OF TASK.
ENDMETHOD.                    "start
However I get the following ABAP dump:
Short text
    Statement "CALL FUNCTION .. DESTINATION/STARTING NEW TASK/IN BACKGROUND TASK"
The function module only contains a wait statement to simulate parallel processing. It is strange that it dumps here, because when I change the FM call to another call that has been triggered successfully from other classes, it still produces the same ABAP dump.
The background of the Proof Of Concept is to see if I can get an event to trigger the next process that depends on the outcome of the previous process. Parallel processes are run in the start methods by calling RFC.
<Garbled code removed>
Moderator Message: Please post relevant portions of the code only.
Edited by: Suhas Saha on Jul 17, 2011 1:17 PM

Well, the thing is I did manage to run 3 other Function Modules asynchronously succeesfully prior to that function call, with the same exact function call syntax. Further more, I have tried editing it with your suggestion but I get the exact same dump.
The complete function group can be downloaded here (slinkee file):
https://docs.google.com/leaf?id=0B3sua1Bw4XK4ZmFhNzcwMTgtYzQ0Mi00NzQ4LTg5YTMtNDNlNWUxYTM2NTg3&hl=en_US
The complete program can be downloaded here (slinkee file):
https://docs.google.com/leaf?id=0B3sua1Bw4XK4YWJmNjU3ODYtODRmMy00Nzg2LThkNTUtZjNkNDRhZGQ3MTUw&hl=en_US
The complete ST22 dump can be found here:
https://docs.google.com/leaf?id=0B3sua1Bw4XK4ZDU1YmFkZDAtOTU5MS00ZTgwLWFlZTktNWZhMDUxMzJlZWNl&hl=en_US
Basically I ST22 gives me the following:
Runtime Errors         RPERF_ILLEGAL_STATEMENT
Date and Time          17.07.2011 05:29:54
|Short text                                                                                |
|    Statement "CALL FUNCTION .. DESTINATION/STARTING NEW TASK/IN BACKGROUND TASK"                 |
|What happened?                                                                                |
|    Error in the ABAP Application Program                                                         |
|                                                                                |
|    The current ABAP program "Z_ZZB1_CLOSE_PERIOD_TEST2" had to be terminated                     |
|     because it has                                                                               |
|    come across a statement that unfortunately cannot be executed.                                |
And it explains it here (but is not helpful / relevant at all) as I ran the program from SE38.
|Error analysis                                                                                |
|    There is probably an error in the program                                                     |
|    "Z_ZZB1_CLOSE_PERIOD_TEST2".                                                                  |
|    The program was probably called in a conversion exit                                          |
|    or in a field exit. These are implemented by                                                  |
|    function modules called CONVERSION_EXIT_xxxxx_INPUT/OUTPUT or                                 |
|    USER_EXIT_xxxxx_INPUT.                                                                        |
|    Conversion exits are triggered during screen field transports or                              |
|    WRITE statements, field exits during field transports from the                                |
|    screen to the ABAP/4 program.                                                                 |
|    In this connection, the following ABAP/4 statements are not allowed:                          |
|                                                                                |
I hope you try to download the slinkee files and you will notice the call function I performed was no different than the other call function RFC calls that really are working.

ABAP Dump on Approving Travel Request

Hello,
We are implementing MSS and when a manager is trying to open a Workitem to Approve a Travel request he gets the following ABAP Dump.
The following error text was processed in system R3Q : Value null of URL parameter SAP_FITV_PERSNO has the wrong type
The error occurred on application server <Hostname> and in work process 0 .
The termination type was: RABAX_STATE
The ABAP call hierarchy was:
Method: GET_REQUEST_INPLUG_PARAMETERS of program CL_WDR_CLIENT_APPLICATION=====CP
Method: INIT of program CL_WDR_CLIENT_APPLICATION=====CP
Method: IF_WDR_RUNTIME~CREATE of program CL_WDR_MAIN_TASK==============CP
Method: HANDLE_REQUEST of program CL_WDR_CLIENT_ABSTRACT_HTTP===CP
Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP
Method: EXECUTE_REQUEST_FROM_MEMORY of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP
Don;t know what's causing it.
Any help would be highly appreciated.
Edited by: SAPEPDeveloper on Mar 16, 2011 9:28 PM

Thanks for the reply.
According to the note : 1076144 I uploaded the valid XML Configuration file, still it gives the same error.
The Other Note : 1239932 is valid for ESS in MSS scenario , right?
Pls reply.
Regards

How to download run time ABAP dump in production environment

Hello,
I am getting run time ABAP dump in production environment. Please guide me onHow to download run time ABAP dump in production environment?
Also, please tell me how best can analyze that dump. Like there are tools like gdb, purify etc. to analyze problems in other languages.
Regards,
Sameer.

Hi,
Go to ST22, and Double click on the error line, It will show you the detailed analysis.
See the section How to correct the error for details on error correction and the instructions to download the log( you can download in the format you want - HTML would be a nice option).
And there are no tools to analyze errors but ST22 has a large data regarding the location of the error, the reason and the source code which caused. So you need to use the debugger to reproduce the error and check the source code,
Regards
Karthik D

ABAP dump during workstatus chaning in SAP BPC 7.5

Hi, Experts
We are working with SAP BPC 7.5 Ramp-up version. We faced a problem - during changing workstatus the system generates ABAP Dump.
We checked ST22 with ABAP Dumps. It contains the following:
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_UJW_WORK_STATUS_DAO========CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
ABAP errors are created in the following code:
FIELD-SYMBOLS:
        <fs_line> TYPE ANY.
CREATE DATA lr_line TYPE (i_tabname).
ASSIGN lr_line->* to <fs_line>.
l_where = 'APPSET = i_appset'. "#EC NOTEXT
LOOP AT it_dim_mem INTO ls_dim_mem.
    CONCATENATE
      l_where ' AND ' ls_dim_mem-dimension ' = ''' ls_dim_mem-member ''''
      INTO l_where RESPECTING BLANKS.
ENDLOOP.
*SELECT SINGLE * INTO CORRESPONDING FIELDS OF es_lock_info FROM (i_tabname) WHERE (l_where).*
* fill lock information
CLEAR ls_ujw_statcode.
CALL METHOD me->read_status_code(
               EXPORTING i_appset = i_appset
                         i_status = es_lock_info-status
                         i_spras = 'E'
               IMPORTING es_ujw_statcode = ls_ujw_statcode ).
ABAP dump says that in "SELECT SINGLE * INTO CORRESPONDING FIELDS OF es_lock_info FROM (i_tabname) WHERE (l_where).*" exist a dynamically specified column name which is unknown.
Does somebody have the same problems?
Regards,
Pavel

Hi Pavel,
This is obviously a bug and it looks like from the code block you copied into the forum that there is an issue with the actual select statements dynamic where clause. I haven't specifically seen this bug but I recommend you do an SAP Note search on the following component EPM-BPC-NW-WS (for work status) in your search criteria put the class name that you found in the dump. This should help you find whether or not a correction has been created (i.e. an SAP note) that solves your issue.
Cheers, Scott

RFC_NO_AUTHORITY ABAP dumps coming very frequently

Hello
We are getting abap dumps in Production system and the details are below :
RFC_NO_AUTHORITY
ABAP dumps RFC_NO_AUTHORITY are coming very frequently in the Production system. The dumps are occurring for user ID "SOLM_REMOTE" in DBCI only. This dumps comes every hour from Sep to till date. Also in the short text it has mentioned, User "User "SOLM_REMOTE" has no RFC authorization for function group "TMW_TRACKING". The termination occurred in the ABAP/4 program "SAPLTMW_TRACKING " in "TMW_VERSION_TEST". The main program was "SAPMSSY1 ".
Provided the RFC authorization for function group "TMW_TRACKING" for the user SOLM_REMOTE.
The user SOLM_REMOTE has all the authorizations.From the authorization perspective everything seems to be fine.
But still we are getting many RFC_NO_AUTHORITY abap dumps frequently in production system.
Please help me in this regard.
Many thanks in Advance.
Regards
Sreedhar Reddy.

Hai,
Please check the below link, it might help you.
http://help.sap.com/saphelp_nw04/helpdata/en/4f/b541d812aea34695d54758cec0796f/frameset.htm
Regards,
Yoganand.V

ABAP dump DDIC_TYPE_INCONSISTENCY

Hi Expert,
we are getting the below abap dump DDIC_TYPE_INCONSISTENCY frequently.
Runtime Errors         DDIC_TYPE_INCONSISTENCY
Date and Time          10.06.2008 12:11:34
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.
Error analysis
     There is an internal system error.
     eliminated with ABAP/4.
How to correct the error
     The internal system error cannot be fixed by ABAP means only.
     You may be able to find a solution in the SAP note system. If you have
     access to the SAP note system, try searching for the following terms:
      "DDIC_TYPE_INCONSISTENCY" " "
      "SAPLMEACCTVI" or "LMEACCTVITOP"
     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:
     "DDIC_TYPE_INCONSISTENCY" " "
     "SAPLMEACCTVI" or "LMEACCTVITOP"
     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.
Please help me to fix this issue.
Thanks & Regards,
Reddy V

Hi Antoni,
Please note the below sm21 log
Details Page 2 Line 27 System Log: Local Analysis of UBSDEV                   1
Time     Type Nr   Clt   User   TCode   Grp N      Text
12:11:34 DIA   001 120 VSALI            AB 0       Run-time error   "DDIC_TYPE_INCONSISTENCY" occurred
Run-time error "DDIC_TYPE_INCONSISTENCY" occurred
Details
Recording at local and central time........................ 10.06.2008 12:11:34
Task...... Process                     User...... Terminal Session TCode Program Cl Problem cl          Package
29480      Dialog work process No. 001 VSALI      acerdev0       1               T Transaction Problem SABP
Further details for this message type
Module nam   Line     Error text
abucutil        1053 ab_RxDdicTypeError
Documentation for system log message AB 0 :
The specified runtime error has occurred in the system.
Parameter
abcdefghijklmnopqrstuvwxyz .. DDIC_TYPE_INCONSISTENCY
Technical details
File Offset   RecFm    System log type        Grp     N
40    319860   l            Error (Module, Row)    AB     0
variable message data
ab_RxDdicTypeError                                  abucutil1053
Regards,
Reddy V

Getting ABAP dump while cancelling invoice through MR8M

Hi Experts,
When i try to cancel the invoice through MR8M i am getting the ABAP dump saying "Conversion error Occured".
Could u please help me to resolve this.
Infact the error is coming when i press "display doc" after giving the invoice details.
Thanks,
Amar Y.
Edited by: amaranath yerragunta on Apr 19, 2010 10:34 AM

Hi ,
Is the any enhanemnet done for MR8M Tcode?
I think in the enhancement code converion is wrong.
Regards,
Pravin

ABAP dump when running an ALV report in a portal

Hi,
I have an ABAP report created in SAP R/3 4.7. Am using the ALV function module REUSE_ALV_GRID_DISPLAY to display the output. The programs runs correctly when run in R/3 using the SAP GUI.
When the report is run in the portal, I get a runtime error 'MESSAGE_TYPE_X'.
Please let me know if anybody has faced such issues.
I checked the OSS note 702732 which talks about increasing the threshold value of the start parameter. But this is not agreed by the BASIS team.
Thanks,
Best regards,
Ajith
The ST22 error log is as follows:
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:
Data volume (84.550.400 bytes) is too large. (abap/alvgrid/size_nodod_mb
Technical information about the message:
Diagnosis
     You tried to send a data record to the front-end that contains
     84.550.400 bytes. However, the data volume is restricted to
     52.428.800 bytes.
System Response
     The running application program was terminated with a runtime
     error.
Procedure
     Restrict the data selection if possible or contact your system
     administrator.
Procedure for System Administration
     You can set the maximum size of these data volumes using the kernel
     parameter 'abap/alvgrid/size_nodod_mb' (in megabytes).
Message classe...... "S>"
Number.............. 890
Variable 1.......... "84.550.400"
Variable 2.......... "52.428.800"
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
"SAPLAWRT" or "LAWRTU22"
"ITS_CHECK_ALV_DATA_SIZE"
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.
Information on where terminated
The termination occurred in the ABAP program "SAPLAWRT" in
"ITS_CHECK_ALV_DATA_SIZE".
The main program was "Z_BW_RECON_INV_RPT ".
The termination occurred in line 25 of the source code of the (Include)
program "LAWRTU22"
of the source code of program "LAWRTU22" (when calling the editor 250).
Source code extract
000010   FUNCTION ITS_CHECK_ALV_DATA_SIZE.
000020   *"
000030   ""Lokale Schnittstelle:
000040   *" IMPORTING
000050   *"     REFERENCE(DATA_TABLE) TYPE TABLE
000060   *"
000070
000080     data n type i.
000090     data currsize type i.
000100     statics maxsize type i.
000110     data par_value(56).
000120     if maxsize is initial.
000130       sy-subrc = 0.
000140       CALL 'C_SAPGPARAM' ID 'NAME' FIELD 'abap/alvgrid/size_nodod_MB'
000150                           id 'VALUE' field par_value.
000160       if sy-subrc ne 0.
000170         maxsize = 52428800.       " Default 50 MB
000180       else.
000190         maxsize = 1048576 * par_value.
000200       endif.
000210     endif.
000220     describe table data_table lines n.
000230     currsize = sy-tfill * sy-tleng.
000240     if currsize gt maxsize.
     >       message x890(s>) with currsize maxsize.
000260     endif.
000270   ENDFUNCTION.

HI,
This is a Memory problem.
System is allocated with a Max Memory of 50 MB,(see the dump code, in the last it is hardcoded in the std code)
The data of your report is coming around 83 MB.
Restrict your selection criteria of the Object and run the same report and see. it will work.
Regards,
Anji

Report J_1IEWT_CERT getting cancelled, generating ABAP dump!

Similar Messages

Maybe you are looking for