Dump ITAB_ILLEGAL_SORT_ORDER_BLK in program RBDAPP01

Hi Colleagues,
I am facing ITAB_ILLEGAL_SORT_ORDER_BLK dump while executing program RBDAPP01.
Please help me on this.
Thanks & Regards
Amit Sharma

Hi Savitha,
I have searched in SAP service market place. I found a total of 63 notes for dump ITAB_ILLEGAL_SORT_ORDER_BLK. But none of them will help me. This job is working fine but only one Idoc is in status 64, which is leading the job to dump. I have seen all Idocs are getting successfully processed except that one.Only solution I believe I have is to create a Idoc with same data in development system and debug in inbound function module mode. But for that I have to manually copy the idoc from production to development via WE19 Tcode. Is there any easier way to create a replica of Idoc.
Thanks & Regards
Amit Sharma

Similar Messages

Short dump in standard program

Hi Friends,
below description is short dump for standard program.
Please see the below and help me how to correct the program.
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).
Error analysis
Short text of error message:
Internal error: Program   , include   , form   .
Technical information about the message:
Diagnosis
     An unexpected error has occurred.
Procedure
     If you can reproduce the error, contact the SAP Hotline quoting the
     error number.
Message classe...... "GR"
Number.............. 214
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
"SAPFGRWE" or "FGRWEF80_F80_FILL_COL_TAB"
"F80_FILL_COL_TAB"
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.
Thanks & Regards,
Sree
Edited by: adepus on Oct 7, 2009 12:39 PM
Edited by: adepus on Oct 7, 2009 12:39 PM

Hi Clemens,
I am getting a dump error as shown below. Could you please find some resolution for this issue. we just made some changes to the transaction GS02(Just added a GL account to one of the sets).
Runtime Error MESSAGE_TYPE_X
ShrtText
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.
is especially useful if you want to keep a particular message.
Error analysis
Short text of error message:
Internal error: Program , include , form .
Technical information about the message:
Diagnosis
An unexpected error has occurred.
Procedure
If you can reproduce the error, contact the SAP Hotline quoting the
error number.
Message classe...... "GR"
Number.............. 214
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "
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
"SAPFGRWE" or "FGRWEF80_F80_FILL_COL_TAB"
"F80_FILL_COL_TAB"
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.
Source Code
79 MESSAGE x214.
80 ENDIF.
81 PERFORM e08_read_object_index(sapfgsb0)
82 USING fcolumns-dim_index.
83 IF c-subrc 0. MESSAGE x214. ENDIF.
84 c_dsentry = c-tval-from.
85 IF c_dsentry '='.
86 READ TABLE data_fields BINARY SEARCH
87 WITH KEY tab = rep_table
88 dsentry = c_dsentry.
>>>> IF sy-subrc 0. MESSAGE x214. ENDIF.
90 ENDIF.
91 WHEN OTHERS.
92 c_dsentry = '*'.
93 ENDCASE.
94 ENDIF.
Regards,
Pavan

Program rbdapp01 when called from a program is not working

Hi Guys,
I am calling the program rbdapp01 from a custom program to reprocess an inbound ASN with IDOC status of 64. The code is listed as below in the custom program.
SUBMIT rbdapp01
WITH docnum = i_report_tab-docnum
WITH p_output = C_FALSE
AND RETURN.
After the execution of the custom program, the IIDOC is not processed and it remains in the status 64 with a message "Re processing deleted , inbound delivery IDOC , ,". When I run the program in debug mode, I can see that the control is going into the rbdapp01 program. But some where along the line, it is failing for what ever may be the reason and it does not process the IDCO, but it only populates the message.
But when I execute the same program rbdapp01 for the same IDOC from SE38, the IDOC is processed fine.
Looks like, I am missing something when I am calling this program rbdapp01 in another custom program. Any advice is really appreciated.
Regards
Rupesh.

Hi,
Please make use of this method of submit
DATA : rspar_tab TYPE TABLE OF rsparams,
        rspar_line LIKE LINE OF rspar_tab.
rspar_line-selname = 'DOCNUM'.
    rspar_line-sign    = 'I'.
    rspar_line-option = EQ'.
    rspar_line-low     = .
    rspar_line-high     = .
    APPEND rspar_line TO rspar_tab.
SUBMIT RBDAPP01 WITH SELECTION-TABLE rspar_tab.
Try to implement this code, hope this help outs
Thanks & Regards
Suresh

What are the major situations to go to the short dump in abap programming?

What are the major situations to go to the short dump in abap programming?

Hi,
The major situations that an ABAP Program can result a dumb are as follows...
1) Poor coding i.e., if the data in the data base is less, then even a poor code can give you the result. But when you transport the program into Production, then there the same program will give you a dump, resulting 'TIMED OUT' error. So performance tunning is required for each and every program.
2) while calling a function module.
3) extracting of data into fields which are not type casted.
4) in case of x/y value, one should check the value of 'y' should not be zero, else a dump will result.
these are few which i can give for time being........

Get Idoc Types Processed by Jobs Running Programs RBDAPP01 or RBDMANI2

Hi Everyone! I would just like to ask if there is a way I can identify all background jobs which are processing a specific idoc type in SAP?
For example, I want to get the Jobs that are processing inbound idoc type WMMBXY using program RBDAPP01 or RBDMANI2.
Is there a way to extract this information?
Thanks in advance!

Vincent, we have a conservative approach RE those programs that re-process IDOCs in pending or error status : we do not define those jobs with open selections, instead we are specific in terms of message type and partner where applicable. We also set a limit in the number or attempts on a failed IDOC by setting a 'rolling start date' (like current date - 7). Besides audit considerations about lingering processes, you also need to take into account the impact of this process on the tale size. Each time the job runs and the IDOC fails, a status record will be added to the EDIDS table for each of those IDOC. If you do not pay attention, you may end up with large amounts of data. This is not only going to unplease your BASIS and DB administrator but eventually put in jeopardy your archiving process (wchich could lead to a system crash !!).
We usually aslo complement those jobs with a status change step (moving from error to no further processing) ; the date parameter can be set to something like anythiing with a creation date > current date + 3 months
To come back to your question : SM37 using the program name as parameter will help you find the associated jobs, but you might need to look into the step(s) and associated variant to get the messages those jobs / steps are processing

GETWA_NOT_ASSIGNED dump error in program SAPLSLVC

Hi,
    I am using REUSE_ALV_GRID_DISPLAY FM to print ALV report and getting GETWA_NOT_ASSIGNED dump error in program SAPLSLVC.
I check the SAP Note for this error.. no luck..
Any one face similar issue.
Cheers
Senthil

Hi,
    Here is my source code.
Layout
it_layout-no_input          = 'X'.
it_layout-colwidth_optimize = 'X'.
it_layout-zebra = 'X'.
it_layout-get_selinfos = 'X'.
it_layout-box_fieldname = 'SEL'.
it_layout-detail_initial_lines = 'X'.
it_layout-detail_titlebar = 'Details'.
ALV
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
            i_callback_pf_status_set = y_pfstatus
            i_callback_program      = y_repid
           i_callback_user_command = 'USER_COMMAND'
            i_grid_title           = y_outtext
            is_layout               = it_layout
            it_fieldcat             = it_fieldcat[]
            i_save                  = 'X'
       TABLES
            t_outtab                = it_out
       EXCEPTIONS
            program_error           = 1
            OTHERS                  = 2.
I am still getting dump error.
Any parameter missing..!
Thanks
Senthil

ABAP Dump : TSV_TNEW_PAGE_ALLOC_FAILED in program SAPLCOM_PARTNER_OB

Hi All,
            I am getting the dump TSV_TNEW_PAGE_ALLOC_FAILED in program SAPLCOM_PARTNER_OB in LCOM_PARTNER_OB in line 165.
Short text
    No more storage space available for extending an internal table.
What happened
You attempted to extend an internal table, but the required space was not available.
The error is occuring in line
INSERT GS_CURRENT_PARTNERSET INTO TABLE GT_PARTNERSETS.
CT_PARTNER[] = GS_CURRENT_PARTNERSET-PARTNER[]. "#EC ENHOK
ENDIF.
   The amount of storage space (in bytes) filled at termination time was:
   Roll area...................... 6221152
   Extended memory (EM)........... 3909511400
   Assigned memory (HEAP)......... 2000692032
   Short area..................... " "
   Paging area.................... 417792
   Maximum address space.......... 18446697117078316543
The dump is occuring in the standard program. Is there any note for this.
Kindly help.
Thanks,

>             I am getting the dump TSV_TNEW_PAGE_ALLOC_FAILED in program SAPLCOM_PARTNER_OB in LCOM_PARTNER_OB in line 165.
>    Extended memory (EM)........... 3909511400
>    Assigned memory (HEAP)......... 2000692032
> The dump is occuring in the standard program. Is there any note for this.
Did you try a notes search?
This program is already using roughly 6 GB of RAM which seems quite a lot.
What transaction/process is triggering this error? It may be that a user just selects too much data.
Markus

Runn time error "CNTL_ERROR" for batch job created for program RBDAPP01

We have encounter run time error and the batch job for program RBDAPP01 was terminated.
Information on where terminated
    Termination occurred in the ABAP program "CL_GUI_CUSTOM_CONTAINER=======CP" -
     in "CONSTRUCTOR".
    The main program was "RBDAPP01 ".
    In the source code you have the termination point in line 62
    of the (Include) program "CL_GUI_CUSTOM_CONTAINER=======CM001".
    The program "CL_GUI_CUSTOM_CONTAINER=======CP" was started as a background job.
Can any member reachout help in identifying the reason.

Hi Amol,
Check the following link.
Call Transaction 'VL32N' in background: termination with Exception
Regards,
Raju.

Parallel processing of the IDOCs through the program RBDAPP01

Hello All,
We are prcoessing the inbound IDOCS using the program RBDAPP01 by scheduling but this processing is taking lot of time to process the IDOCs.
Please let me know how do we improove the performance of this program RBDAPP01 by making use of
parallel processing of IDOCS?I read some documentation in this forum but not understand clearly.
Please give some info regarding this who have already done this requirement earlier.
Regards
Mahesh

Hi,
Thanks a lot for your quick reply just by giving the package size it will initiate parallel processing?
in our partner profiles we have setting to trigger through back ground only.
How to use parallel processing tab in the selection screen of the program RBDAPP01?
Regards
Mahesh

Parallel processing for program RBDAPP01

Hi All,
I am running this program RBDAPP01 daily after every 30minutes to clear the error I Docs (Status 51 Application document not posted) Status Message u201CObject requested is currently locked by user ADMINJOBSu201D when I run this job it only clears few Idocs because of the Status Message u201CObject requested is currently locked by user ADMINJOBSu201D Means when one Idoc is getting updated the second one tries to update the same time for same order, same customer, same material and same plant but different ship to party it finds locked and cannot be posted.
Can any one tell me what parallel processing is and will it help my case.
Thanks

You didn't specfiy which release you use so I can just give some suggestions:
Note 547253 - ALE: Wait for end of parallel processing with RBDAPP01
Note 715851 - IDoc: RBDAPP01 with parallel processing
Markus

Get output of Program RBDAPP01

Hi All,
I will be calling Program RBDAPP01 within my custom program to process all the IDocs with status 64 of basic type ISU_MR_UPLOAD.
I have few questions regarding it:
1. Do i need to Submit program for each Idoc as below
SUBMIT rbdapp01   VIA JOB g_jobname
                        NUMBER g_jobcount
                        WITH docnum = t_edidc-docnum
                        AND RETURN.
or i can Submit the program for all the Idoc at once. But i thnk there is some check that if the number of Idocs is more than 100.
Can any please help me with this?
2. As i am calling this program within my custom program, is there any way i can get the Status of the Idoc that have been processed afer submitting the program. Like an output list of the program RBDAPP01. (The other way i know is to get the status of all the IDocs from EDIDC table)
Thanks

Hi,
No worries. To answer your latest questions: it really depends on the volume of IDocs you are working with.
If you're talking about hundreds then you should be fine with exporting the list to memory and then retrieve the list from there.
If you're talking about a bigger number, I'd consider querying table EDIDC using a database cursor:
OPEN CURSOR zcursornmae FOR DB QUERY
and then fech the entries using the cursor and defining a PACKAGE SIZE of around 500 (this is just a suggested number).
By doing this, you'll avoid retrieving say 1 million entries at once.
Cheers.

A short dump in the program with a certain error message...

Hi all,
I'd run a program to do an insertion into a customized table.
During the run, it popped up a short dump error messages below :
value larger than specified precision allows for this column#TC020 %M
I've search for that column #TCO20 .... and i couldn't find it in my custom table...
Why SAP gave such a hard description on the error found? I can't determine which field/column in my table that is causing the error dump during INSERT event in my program.
Is there any explanation on that message that could help me?
Thanks
William Wilstroth

Hi,
Better u seee again where u r getting error i the code . still if u r not getting see in dump analysys(ST22) and select
no:8 -- which is source code extract where u can get correct error inf.
Plz reply me.
Regards
Durgaprasad.

Short Dump-Syntax error program"CL_RSD_MULTIPROV==CP" after EHP1SP5 upgrade

Hi,
MultiProvider Activation/Display data is resulting into short dump with following text
Error in the ABAP Application Program
The current ABAP program "CL_RSD_MULTIPROV_CHECK========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"CL_RSD_MULTIPROV==============CP " in include
"CL_RSD_MULTIPROV==============CM010 " in
line 1:
"Method "CHECK_LINITFL" is not declared or inherited in class "CL_RSD_M"
"ULTIPROV". -"
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "CL_RSD_MULTIPROV_CHECK========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
We have recently upgraded to EHP1SP5. We noticed this issue just after that.
Regards,
PD

Hi,
Please check the note 1461401.
1461401 - System error in the program CL_RSD_MULTIPROV_CHECK
This note should help you.
Regards,
Rafael

Short dump error in program SAPMV50A after modification

Dear gurus
i have done some modification in vl02n through Badi and it is working fine in Development server.
when i transport it to quality server and test it
it giving a short dump in vl02n while vl01n is working perfectly fine and showing my modification too..
below is the error mentioned
Database error text........: "Unsupported database type in parameter/column
    (168)."
   Internal call code.........: "[RSQL/READ/LIKP ]"
   Please check the entries in the system log (Transaction SM21).
   If the error occures in a non-modified SAP program, you may be able t
   find an interim solution in an SAP Note.
   If you have access to SAP Notes, carry out a search with the followin
   keywords:
   "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
   "SAPMV50A" or "MV50AFDB"
   "LIKP_SELECT"
   If you cannot solve the problem yourself and want to send an error
   notification to SAP, include the following information:
Please help
Regards
Saad Nisar

i have created two append structure in standard tables of LIKP & LIPS which are activated and so as LIKP and LIPS
my Badi is also activated and my customized program is also activated.
While making outbound delivery in Quality server it works fine but when i want to make changes in that created delivery it throws dump error
short text
   SQL error in the database when accessing a table.
issing RAISING Clause in Interface
   Program                                 SAPMV50A
   Include                                 MV50AFDB
   Row                                     14
   Module type                             (FORM)
   Module Name                             LIKP_SELECT
rigger Location of Exception
   Program                                 SAPMV50A
   Include                                 MV50AFDB
   Row                                     20
   Module type                             (FORM)
   Module Name                             LIKP_SELECT

ABAP Dump GETWA_NOT_ASSIGNED_RANGE for program /SDF/CL_EM_DUMP_COLLECTOR=====CP

Hello,
I am getting ABAP runtime error GETWA_NOT_ASSIGNED_RANGE every 10 minutes in my ECC Production system. This dump is occurring for program /SDF/CL_EM_DUMP_COLLECTOR=====CP with short text as "Field symbol is not assigned".
Error Analysis:
"A field symbol that was not assigned was accessed
(data segment no. "-1").
The field symbol is no longer assigned because there was an attempt
makde previously in a Unicode program to set the field symbol using
ASSIGN with offset and/or length specification. Here, the memory
addressed by the offset/length specification was not within the
allowed area."
Information on where terminated:
"Termination occurred in the ABAP program "/SDF/CL_EM_DUMP_COLLECTOR=====CP" -
     in "GET_FIELDTABLE".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 51
    of the (Include) program "/SDF/CL_EM_DUMP_COLLECTOR=====CM005"."
Server-Side Connection Information:
"Information on caller of Remote Function Call (RFC):
    System.............. "Solution Manager"
    Installation Number. " "
    Database Release.... 702
    Kernel Release...... 720
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "synchronous and non-transactional (emode 0, imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "
    Client.............. Prod Client
    User................ "SolMan user"
    Transaction......... " "
    Call Program........."SAPLE2EEM_DATA_COLLECTION"
    Function Module..... "/SDF/E2EEM_GET_DATA"
    Call Destination.... "SM_<ECC_PROD>_READ"
    Source Server....... "Solution Manager"
    Source IP Address... "Solution Manager"
    Additional information on RFC logon:
    Trusted Relationship " "
    Logon Return Code... 0
    Trusted Return Code. 0"
I searched for SAP notes and other SCN discussion but could not find relevant information. Can someone please assist me? Thanks.
Tanay

Hi Srivastava,
What process or transaction you are executing, when you got this dump, please share the detail.
In SAP there so many areas where we can have this ABAP dump, please also share the snap shot in ST22 " How to Correct" part of dump which carries the exact program name e.g. in below snapshot program name, short text, etc is given to search SAP note.
Please also refer to the following sap notes:
1840910 - Dump CHECK_SELOPT_ILLEGAL_SIGN
1729771 - Collective corrections as of ST-PI 2008_1 SP06
1011229 - ST-PI: Corrections for E2E Diagnostics
Regards
Javed

Dump ITAB_ILLEGAL_SORT_ORDER_BLK in program RBDAPP01

Similar Messages

Maybe you are looking for