Dump While Executing ME21N, ME22N and ME23N

Hi,
when I try to do the same in my system SAP gives me an information message as follows:-
Changes to transported Business Add-In definitions are incompatible
Message no. ENHANCEMENT236
Diagnosis
This business add-in definition has already been transported. Subsequent changes could invalidate existing business add-in implementations.
System Response
The runtime behaviour is no longer predictable. Syntax errors or short dumps may occur.
Procedure
If possible, do not make these changes. Alternatively, create a new business add-in definition incorporating the changes and use it, along with the existing definition.
It clearly indicates that the BADI definition should not be changed if active implementations already exists.
I am really now not sure how to solve your issue.
Try deactiviting the standard BADI implementation.
Then again add the filter and then remove it.
And then try activating the BADI implementation once again.
Regards,
Ankur Parab

Similar Messages

EXIT BADI FOR ME21N ME22N AND ME23N

Hello Boys.
I want to change the field 'Tax code' (MWSKZ) in a Purchase order on transaction ME21N, ME22N AND ME23N.
I want to change thios field in a BADI, USER EXIT or ENHANCEMENT-POINT.
But I can't find where change this field.
thanks for your help.
Best regards.

Try Badi : ME_PROCESS_PO_CUST
    CALL METHOD im_item->get_data
      RECEIVING
        re_data = v_data_item.
Your code to change the tax code
CALL METHOD im_item->set_data( v_data_item ).
<REMOVED BY MODERATOR>
Edited by: Aparna Shekhar on Jun 12, 2008 11:33 AM
Edited by: Alvaro Tejada Galindo on Jun 12, 2008 12:52 PM

Hiding a customized tab (from header and item) in ME21N, ME22N and ME23N

Hi SAP gurus,
I need to make invisible a customized tab in Po creation(me21n), change(me22n) and display(me23n) in enjoySAP transaction for a particulat Doucument type.
Please let me know the possibility and the solution to implement.
Thanks,
Kishore P

Hi Kishore,
The customized tab cannot be made visible or invisible conditionally. Instead you can write some text inside the tab to distinguish between different document types.
Hope this helps.
Regards,
Abhijeet Kapgate

Short dump while executing few queries , which has got created on Infoset.

Hi,
We went to BI7.0 upgrade from BW3.x now.
We are getting short dump short dump while executing few queries and work book, which has got created on Infoset.
When i was executing work book where i was geting popup message saying that "Erro ZSD_XST_F00121 is invalid".When i click that message it went to dump.
I was getting this error while executing query on infoset.
We are currently SP Stack 13(Patch level 15).
I found some note 1067918 as per the shortdum,where it is saying that you need to apply SP Stack14(patch level16).
Please some one who had earlier this kind of issue.
I appreciate your answer.

Dear Krish,
Yes, It is the patch problem.
We too faced the same issue on Infosets.
Apply SP 15.
Regards,
Ram.

Short dump while change/display a PO ME22N and ME23N

while i try to use tcode ME21N it works but when try to use Tcode ME22N and ME23N it gives me a short dump
as i have pasted the short dump screen shot in this thread please have a look and reply .
offering points is against the forums RoE
Message was edited by: Suhas Saha

Did you check for OSS notes (as this seems to be a standard program) - e.g. 1930814 - Exception NOT_FOUND in the program /NFM/SAPLSELECTS. If no OSS note solved the problem, then raise an OSS message.
Regards,
Raymond
PS: And don't promise points, it's against The SCN Rules of Engagement

ABAP runtime error while doing ME21N, ME22N, ME23N, ME51N,ME52N, ME53N

Dear All Expert,
I am facing problem while doing ME21N, ME22N, ME23N, ME51N,ME52N, ME53N,
Please find the below ABAP Runtime Error.
Runtime Errors         LOAD_TYPE_VERSION_MISMATCH
Date and Time          10.02.2011 11:13:07
Short text
     Change of a Dictionary structure at runtime of a program.
What happened?
     Runtime error
     The current ABAP program "CL_IM_WRF_MM_PROC_PO==========CP" had to be
      terminated because one
     of the statements could not be executed at runtime.
What can you do?
     Restart the program.
     If the error persists, 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
     The ABAP runtime system detected that the Dictionary-type "WRF_POHF_KOMP_STY"
      changed
     during the flow of the transaction.
     As the type was already used in the old version
     and in the new type should be used in the same transaction in the new
      version, the transaction had to be cancelled to avoid inconsistencies.
How to correct the error
    Try to restart the program.
System environment
    SAP-Release 700
    Application server... "iqe"
    Network address...... "172.25.0.85"
    Operating system..... "Linux"
    Release.............. "2.6.9-55.ELsmp"
    Hardware type........ "x86_64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "iqe"
    Database type..... "ORACLE"
    Database name..... "IQE"
    Database user ID.. "SAPSR3"
    Terminal................. "MUMJML5727"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Dec 26 2010 20:17:07"
    create on........ "Linux GNU SLES-9 x86_64 cc3.3.3"
    Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 285
Patch text.. " "
Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"
SAP database version. 700
Operating system..... "Linux 2.6"
Memory consumption
Roll.... 16192
EM...... 25139088
Heap.... 0
Page.... 40960
MM Used. 8038136
MM Free. 4528408
User and Transaction
Client.............. 600
User................ "JKMM"
Language key........ "E"
Transaction......... " "
Transactions ID..... "4D524AD1FD7A42F9E1000000AC190055"
Program............. "CL_IM_WRF_MM_PROC_PO==========CP"
Screen.............. " "
Screen line......... " "
Information on where terminated
    The termination occurred during generation of the ABAP/4 program
     "CL_IM_WRF_MM_PROC_PO==========CP".
    The termination occurred in line 213
    of the source code of program "CL_IM_WRF_MM_PROC_PO==========CM007" (when
     calling the editor 2130).
Source Code Extract
Line SourceCde
183   DATA: l_flag TYPE wrf_pbas_boolean.
184
185   CALL FUNCTION 'WRF_POHF_MSG_READ_PREVIEW_FLAG'
186     IMPORTING
187       e_preview_flag = l_flag.
188
189   IF NOT l_flag IS INITIAL.
190
191     DATA: l_header TYPE REF TO cl_po_header_handle_mm.
192
193     MOVE im_header ?TO l_header.
194
195     CALL METHOD l_header->if_output_mm~preview( ).
196
197     CALL FUNCTION 'WRF_POHF_MSG_RESET_PREV_FLAG'.
198
199 ***$ Widening Cast for printing information.
200 **    CALL FUNCTION 'WRF_POHF_STORE_PRINT_INFO_SET'
201 **      EXPORTING
202 **        im_header = l_header.
203
204 * Printing Preview
205 * IF NOT gv_preview IS INITIAL.
206 *    CALL METHOD l_header->if_output_mm~overview( ).
207 *    CALL METHOD l_header->if_output_mm~preview( ).
208 * clear gv_preview.
209   ENDIF.
210
211 * ENDIF.
212
>>>>> ENDMETHOD.
Internal notes
    The termination was triggered in function "ab_RxDdicStruShareFailed"
    of the SAP kernel, in line 2539 of the module
     "//bas/700_REL/src/krn/runt/abtypload.c#11".
    The internal operation just processed is " ".
    Internal mode was started at 20110210111306.
    Name of the changed type......: "WRF_POHF_KOMP_STY"
    New version of the type.......: 20070508193207
    Old version of the type.......: 20070508193207
    New user......................: "Type" "WRF_POHF_KOMP_STY"
    Version of the new user.......: 20070508193207
    Old user......................: "???" "???"
    Version of the old user.......: "???"
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
(CTrcStack2+0x78)[0x6cbb78]
(CTrcStack+0xb)[0x6cc17b]
(ab_rabax+0x3be5)[0xb8d985]
(_Z24ab_RxDdicStruShareFailedPKtm4RUDIS0_S1_S0_+0x163)[0xb16823]
(_Z19ab_GetDdicTypeIndexPKtm4RUDI+0x1f6)[0xb0dbb6]
(_Z11ab_LoadViewPtjPKtPK11PROGRAMHEADPj+0x27e)[0xb16ede]
(_Z18ab_GetDdicTypeLoad4RUDI+0x6e)[0xb1705e]
(ab_GetView+0xc1d)[0xb0ee1d]
(_Z20CompressInitRcByDatajPK6CG_DIRjjS1_jj4RUDIPKhj+0x60d)[0xe32b2d]
(_Z21cg_CompressStackFrameP4TRIGjj+0x169)[0xe33399]
(_Z8cg_blkleP3ENV+0x75f)[0xe4779f]
(_Z9sc_cblklePKt8ENV_KINDP7SC_INFO+0x394)[0xe90024]
(sc_blkle+0xdd)[0xec6e4d]
(rs_oper_abap1729+0x37)[0x10eb237]
(rs_expan_abap+0xa1996)[0xfd7a2a]
(_Z8sc_expanj+0x76d)[0xe1d55d]
(_Z5parsejPi+0x258)[0xe19998]
(sc_check+0xb9c)[0xe1857c]
(sc_inclu+0x5fa)[0xe0d50a]
(rs_oper_abap2160+0x3a)[0x1115d6a]
(rs_expan_abap+0xcd41d)[0x10034b1]
(_Z8sc_expanj+0x76d)[0xe1d55d]
(_Z5parsejPi+0x258)[0xe19998]
(sc_check+0xb9c)[0xe1857c]
(sc_checkStart+0x41)[0xe1ac51]
(cg_generate+0xb65)[0xe57755]
(ab_gabap+0x14a)[0xb01a5a]
(dy_gen_abap+0x63c)[0x74428c]
(ab_genprog+0x13d3)[0xb03d13]
(_Z17ab_LoadProgOrTrfoPKtjPj+0xb56)[0x8f9ab6]
(_Z11ab_LoadProgPKtj+0x11)[0x8f9ca1]
(_Z15LoadGlobalClassPKtjjj9ClasState+0x24c)[0x958c2c]
(_Z11FillCfixIntPK4CREFP4CFIXjj9ClasState+0x214)[0x957404]
(_Z11ab_FillCfixtj+0x65)[0x957ae5]
(_Z26ab_CrefToCladId_ActivateOKtPh+0x7d)[0x957b6d]
(_Z8ab_jaboov+0x623)[0x959793]
(_Z8ab_extriv+0x607)[0x8ba9c7]
(_Z9ab_xeventPKt+0x1c1)[0xa1c021]
(_Z8ab_triggv+0x9c)[0xa1c77c]
(ab_run+0x97)[0xbde5c7]
(N_ab_run+0x9)[0x736359]
(dynpmcal+0x669)[0x7333b9]
(dynppai0+0x8eb)[0x734d9b]
(dynprctl+0x3e9)[0x733db9]
(dynpen00+0x4a5)[0x726eb5]
(Thdynpen00+0x359)[0x541bd9]
(TskhLoop+0xc49)[0x54d999]
(ThStart+0x20f)[0x55b29f]
(DpMain+0x2da)[0x4bd49a]
(nlsui_main+0x9)[0x4910c9]
(main+0x33)[0x491103]
/lib64/tls/libc.so.6(__libc_start_main+0xdb)[0x3cde51c3fb]
Please help me to resolve the issue.
Thanks & Regards
SKK

read this part again: The ABAP runtime system detected that the Dictionary-type "WRF_POHF_KOMP_STY" changed during the flow of the transaction. As the type was already used in the old version and in the new type should be used in the same transaction in the new version, the transaction had to be cancelled to avoid inconsistencies. How to correct the error Try to restart the program
how often had you restarted ME21N before you posted this message?
In best case this message appears only once, because the program / or dictionary was changed while you executed ME21N
If many times, then contact your ABAPer, because then he probably did not transport all objects that were changed, or the objects have to be regenerated in your system.

Dump while Executing Hrast_dT (Design time of HCM Process and Forms)

Hi All,
I am getting Syntax Error Dump while Executing Hrast_dT tcode (Design time of HCM Process and Forms) and here with i have mentioned the source code also ist contained in standard class.
*METHOD constructor.
DATA:
    badi_context          TYPE REF TO lcl_badi_context.
CALL METHOD super->constructor
    EXPORTING
      form_scenario         = form_scenario
      form_scenario_service = form_scenario_service.
DATA:
    t5asrfscnsrv_wa TYPE t5asrfscnsrv.
SELECT SINGLE * FROM t5asrfscnsrv INTO t5asrfscnsrv_wa WHERE form_scen_srv EQ form_scenari
ASSERT sy-subrc EQ 0.
ASSERT t5asrfscnsrv_wa-service_type = 'GENSRV'.
fill_table_metadata( ).*
i followed this link also..its not working for me..
[Re: Assertion_Failed dump when accessing Design Time for Processes & Forms EP3]
Regards,
Parthi

Hello Parthasarathi,
Please, try to implement the note 1075650.

Dump while executing the query on MProvider on Stock and Billing

Hi,
I am getting this dump while executing a Query on Multiprovider. Here Multiprovider is on Billing cube(z-cube) and 0IC_C03 cubes. In the report , I have KF of both cubes. I am sure I never faced this type of problem in version 3.5. It seems we are going back day by day because of version 7.0.
A:
1) I am not getting any error if I take Kfs of only Billing cube in the
report on the multiprovider.
2) But I am getting this problem by taking only KF from 0IC_c03 on this multiprovider .
3) And also this problem is not raising in any queries(ofcourse same type) of those 2 cubes.
4) Here Fiscal Variant is constant filter, and User will enter the Fiscal year.
5) In the Columns area ,I have taken 12 selections each one restricted with one CALMONTH2.
6) in Rows part I have 3 selections. Here 2 selections have Billing KF and other selection has Blockd Stock qty KF.
B:
The above dump is not raising if I take 12 selections on columns with a restriction on 0CALMONTH with Customer exit varible , but different offsets in selections. Here the Customer exit variable gets April of the User entered Financial year as the value. But the problem is For all columns it is giving same Value for Stock KF even though we have different values in the system. Surprisingly issue is , Sales figures are comming proper.
I am on Version 7 and patch 13. And I am using Querydesigner 3.5.
Dump message: GETWA_NOT_ASSIGNED
<i>Short text:
    Field symbol has not yet been assigned.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "RSDRC_NCUM_ROUTINES" had to be terminated because it has come across a statement that unfortunately cannot be executed.
keywords:
"GETWA_NOT_ASSIGNED" " "
"RSDRC_NCUM_ROUTINES" or "RSDRC_NCUM_ROUTINES"
"FILTER_SELDR"</i>
Thanks and Regards,
Anil Kumar Sharma .P
Message was edited by:
        Anil Kumar Sharma
Message was edited by:
        Anil Kumar Sharma

OK,
I come back to my question: you said "<i>But the problem is For all columns it is giving same Value for Stock KF even though we have different values in the system</i>"
Can you say to which period this value correspond?
This looks like you are missing some characteristic identification in your multi.
Can you assess that?
Do you have the same time periods in both cubes? I mean, do you have at least the periods used in your RKF / query in both cubes? Would you mind pasting your identification for time IObjs from table RSDICMULTIIOBJ?
please see hereunder my identification for a sales and stock multicube
INFOCUBE                       OBJVERS IOBJNM                         PARTCUBE                       PARTIOBJ
ZMC021                         A       0CALDAY                        ZICRT_C07                      0CALDAY
ZMC021                         A       0CALMONTH                      ZICRT_020                      0CALMONTH
ZMC021                         A       0CALMONTH                      ZICRT_C07                      0CALMONTH
ZMC021                         A       0CALMONTH2                     ZICRT_020                      0CALMONTH2
ZMC021                         A       0CALMONTH2                     ZICRT_C07                      0CALMONTH2
ZMC021                         A       0CALQUART1                     ZICRT_020                      0CALQUART1
ZMC021                         A       0CALQUART1                     ZICRT_C07                      0CALQUART1
ZMC021                         A       0CALQUARTER                    ZICRT_020                      0CALQUARTER
ZMC021                         A       0CALQUARTER                    ZICRT_C07                      0CALQUARTER
ZMC021                         A       0CALWEEK                       ZICRT_C07                      0CALWEEK
ZMC021                         A       0CALYEAR                       ZICRT_020                      0CALYEAR
ZMC021                         A       0CALYEAR                       ZICRT_C07                      0CALYEAR
ZMC021                         A       0FISCPER                       ZICRT_020                      0FISCPER
ZMC021                         A       0FISCPER                       ZICRT_C07                      0FISCPER
ZMC021                         A       0FISCPER3                      ZICRT_020                      0FISCPER3
ZMC021                         A       0FISCVARNT                     ZICRT_020                      0FISCVARNT
ZMC021                         A       0FISCVARNT                     ZICRT_C07                      0FISCVARNT
ZMC021                         A       0FISCYEAR                      ZICRT_020                      0FISCYEAR
ZMC021                         A       0FISCYEAR                      ZICRT_C07                      0FISCYEAR
note that here ZICRT_020 is a monthly stock cube.
hope that helps...
Olivier.

SHORT DUMP WHILE EXECUTING DTP.

Hi Gurus,
I have got a short dump while executing DTP the Error is as Follows.
Runtime Error: MESSAGE_TYPE_X.
Reasons for Error: 1.The installation of the SAP GUI on the present server is faulty or obselete
2.There is a error in the application program
And i have sent the sreen shot of the Short Dump to BASIS TEAM and they have replied me that they have to install some patches and it will take some time.
But i have no much time and i have to someway or the other execute the DTP and load the data.
Is there any shortcuts for this i mean to say without the involvement of Basis team that i can do in th BI System
Regards
Amar.

Hi Amar,
If the problem is with with System itself, how can we all have a short cut in that case. You may give it another trial, but you have to wait for the patches to be applied. Ask your basis team to get it done ASAP.
Thanks..
Shambhu

Short Dump while executing New Hire (action type) in PA40

Hi All,
i am getting short dump while executing PA40 for new hire action type can anyone look into this and guide as i am new to HCM.
Category               ABAP Programming Error
Runtime Errors         SYNTAX_ERROR
ABAP Program           /1PAPAXX/HDR_21000A
Application Component Not Assigned
Date and Time          21.08.2014 14:07:03
Short text
    Syntax error in program "/1PAPAXX/HDR_21000A ".
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPFP50M" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "/1PAPAXX/HDR_21000A " in
    include "/1PAPAXX/HDR_21000AO01 " in
    line 52:
    ""LV_LENGTH" has already been declared"
    The include has been created and last changed by:
    Created by: "HCM04 "
    Last changed by: "HCM03 "
    Error in the ABAP Application Program
    The current ABAP program "SAPFP50M" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
What can you do?
    Please eliminate the error by performing a syntax check
    (or an extended program check) on the program "/1PAPAXX/HDR_21000A ".
    You can also perform the syntax check from the ABAP Editor.
    If the problem persists, proceed as follows:
    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
    The following syntax error was found in the program /1PAPAXX/HDR_21000A :
    ""LV_LENGTH" has already been declared"
How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    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.
System environment
    SAP Release..... 731
    SAP Basis Level. 0007
    Application server... "dc-ds-erp"
    Network address...... "172.16.23.111"
    Operating system..... "Linux"
    Release.............. "3.0.13-0.27-default"
    Hardware type........ "x86_64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "dc-ds-erp"
    Database type..... "ORACLE"
    Database name..... "ECD"
    Database user ID.. "SAPSR3"
    Terminal.......... "NLC-HP"
    Char.set.... "C"
    SAP kernel....... 720
    created (date)... "Sep 14 2013 06:16:24"
    create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr130820"
    Database version. "OCI_112, 11.2.0.3.0, V1, default"
    Patch level. 500
    Patch text.. " "
    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
    SAP database version. 720
    Operating system..... "Linux 2.6, Linux 3"
    Memory consumption
    Roll.... 0
    EM...... 37708200
    Heap.... 0
    Page.... 106496
    MM Used. 4666776
    MM Free. 3709976
User and Transaction
    Client.............. 210
    User................ "HCM03"
    Language key........ "E"
    Transaction......... "PA40 "
    Transaction ID...... "53EF470299AB5D67E1000000AC10176F"
    EPP Whole Context ID.... "005056A301D11EE48A9D08B337F884E3"
    EPP Connection ID....... 00000000000000000000000000000000
    EPP Caller Counter...... 0
    Program............. "SAPFP50M"
    Screen.............. "MP000000 1000"
    Screen Line......... 3
    Debugger Active..... "none"
Information on where terminated
    Termination occurred in the ABAP program "SAPFP50M" - in
    "GET_HEADER_WITH_TCLAS".
    The main program was "MP000000 ".
    In the source code you have the termination point in line 146
    of the (Include) program "FP50MDHD".
Source Code Extract
Line
SourceCde
116
CALL FUNCTION 'HR_HEADER_GET'
117
      EXPORTING
118
           DHDID                    = FHD_HID
119
           BEGDA                    = BEGDA
120
           TCLAS                    = TCLAS
121
* Es wird nur einer der folgenden 3 Parameter benutzt.
122
* Ausgewertet wird zunaechst MOLGA, dann P0001 dann PERNR.
123
* Der erste der nicht initial ist wird ausgewertet.
124
*           MOLGA                   =
125
           P0001                    = P0001
126
           PERNR                    = PSPAR-PERNR
127
      IMPORTING
128
           PROG                     = HEADER_PROG
129
           DNUM                     = HEADER_DYNNR
130
       EXCEPTIONS
131
            HEADER_DEACTIVATED          = 1
132
            HEADER_UNKNOWN              = 2
133
            HEADER_GENERATE_DEACTIVATED = 3
134
            HEADER_GENERATE_FAILED      = 4
135
            INTERNAL_ERROR              = 5
136
            OTHERS                      = 6.
137
138
IF NOT SY-SUBRC IS INITIAL.
139
* Bei Problemen gibt's eben ein leeres Dynpro.
140
    HEADER_PROG = 'SAPMP50A'.
141
    HEADER_DYNNR = '0090'.
142
ELSE. " NOT sy-subrc IS INITIAL.                                   "
143
* Dann setzen wir jetzt auch noch das Datum fest.
144
    PERFORM HEADER_BEGDA_SET IN PROGRAM (HEADER_PROG) USING BEGDA.
145
* Und schalten auf Uebergabe der PERNR mit globalen Variablen.
>>>>>
    PERFORM HEADER_LAZY_ON IN PROGRAM (HEADER_PROG).
147
ENDIF. " (ELSE) NOT sy-subrc IS INITIAL.                           "
148
* Merken wie der Header heisst. Damit MPPERS00 sich erinnern kann.

Hi,
Error Log: Syntax error
""LV_LENGTH" has already been declared"
please check LV_LENGTH variable declaration.
It may be declared more once!

Short dump while executing info package in 3.5 data flow?

Hi,
i am getting short dump while executing info package while executing info package. it was working perfectly 2 days back suddenly it is giving this problem. it is a full load for info object text data and i have only 600 records. when i tried with " only info package" it is working perfectly n bringing the data into PSA. But when i use "PSA and the into data target" it is giving short dump.
i replicated Data source and also i activated transfer rules, update rules still it is not working. When i check with another info objects it is working perfectly fine. i dont know what is wrong with only particular info object.
Please find attached short dump.
Thanks

Hi,
When you load transaction data I think there is a deadlock.
Check in the process overview (transaction SM50) the waiting processes are in program SAPLSENA .
The program SAPLSENA is the lock handler tool.
Also check if ACR is running on this target while your load is happening.
Check in SM12 if there are any lock entries for the Infoobject to which you are loading data and on RSICCONT table .
Try reloading after deleting the locks manually.
Regards.

Dump while Executing the Report HINUINFU

Dear All
I am getting Dump while executing the T.Code - HRPBSIN_IN_INFU (HINUINFU). As per my Configuration it should update the IT0267 and the IT0582. While debugging the We found out that its updating the IT0267 internally. But while reaching to IT0582 its reflecting on the feature 40CEA and the T549D.
here we are having the Telephone Reimbursement for this i copied the Tax code SEXM to ZTEL and assigned to my wage type
I also maintaied this Subtype to the feature 40CEA.
Checked also the IT0582 and its subtype time constraint.
Still the the DUMP persisisting. Please provide the solutions if any of you come across with the same situation.
Thanks & Regards
Srikanth Reddy

Hi
Issue has been resoved internally. Return value to feature set as HINUOSD0 to MOLGA. hence closing the thread
Regards
Srikanth Reddy

Dump while executing the report in the background!!!

Hi Experts,
I have created one report which is calling the "HRASR_TEST_PROCESS" (HR form process) thru BDC.
Its running fine while executing via SE38 (foreground) but getting dump while executing from the background with same variant.
The dump is follows,
Short Text
Exception condition "CNTL_ERROR" raised.
ERROR ANALYSIS
A RAISE statement in the program "CL_GUI_CUSTOM_CONTAINER=======CP" raised the exception condition "CNTL_ERROR". Since the exception was not intercepted by a superior program, processing was terminated.
Line        Source Code
32         WHEN 1.
   33           RAISE CNTL_SYSTEM_ERROR.
   34         WHEN 2.
   35           RAISE CNTL_ERROR.
   36         WHEN 3.
   37           class cl_gui_cfw definition load.
   38           message id 'DC' type 'W' number cl_gui_cfw=>reason_no_init
   39             raising create_error.
   40         WHEN 4.
   41           RAISE LIFETIME_ERROR.
   42         WHEN 5.
   43           RAISE LIFETIME_DYNPRO_DYNPRO_LINK.
   44         WHEN OTHERS.
   45           RAISE CNTL_ERROR.
   46       ENDCASE.
   47
   48       m_container_type = CONTAINER_TYPE_CUSTOM.
   49
   50       CALL METHOD SET_VISIBLE
   51           EXPORTING
   52               VISIBLE = '1'
   53           EXCEPTIONS
   54               CNTL_SYSTEM_ERROR = 1
   55               CNTL_ERROR = 2.
   56
   57       CASE SY-SUBRC.
   58         WHEN 0.
   59         WHEN 1.
   60           RAISE CNTL_SYSTEM_ERROR.
   61         WHEN 2.
>>>>>           RAISE CNTL_ERROR.
   63         WHEN OTHERS.
   64           RAISE CNTL_ERROR.
   65       ENDCASE.
   66
   67       m_name = container_name.
   68       call method set_window_property
   69            exporting property_id = property_name
   70                      value       = m_name
   71                      keep_cache = 'X'
   72            exceptions others = 1.
   73       if sy-subrc ne 0.
   74         clear m_name.
   75         raise cntl_error.
   76       endif.
   77
   78       CALL METHOD ME->REGISTER_CACHED_W_PROPERTY
   79         EXPORTING
   80           PROPERTY_ID             = property_height
   81         EXCEPTIONS
Kindly let me know, what is the problem and how can i solve it.
Thanks in advance.
Regards,
Harish

Hello Zhou,
indeed, as you mention the ALV grid, there are some workarounds in the system, but there is no global solution. For example, the function module REUSE_ALV_GRID_DISPLAY detects internally whether it is called in background mode, and in this case it forwards the call to REUSE_ALV_LIST_DISPLAY which is runnable in background mode, since it creates an ABAP list.
But normally, when using objects of the control framework in your program, you are restricted to dialog mode.
Kind regards,
Rüdiger

Getting a dump while executing the standard report BUSCHDOC

Hi,
I am getting a dump while executing the standard report BUSCHDOC.
I am specifying the following values:-
Application Object : BUPA
Business partner:<some business partner>
Changed on: <some date>
Changed by:<some userid>
Below are the dump details
Short text
CREATE DATA: The specified type "BUSSRCH_401BUPAT" is no valid data type.
Any suggestions to avoid the dump are welcome.
Thanks,
Ravindra

Hi Ravindra,
Can you execute report BUP_BUSSRCHGF_REPAIR and try again ?
Also, go to transaction BUS10, click the button Geneate Selection. On next screen, give Application object = BUPA, Max no. of tables per view = 1.
Regards,
Rishu.

System Throws short dump while executing data source 2LIS_11_VASCL in RSA3.

Hello Experts,
I got short dump while executing data source 2LIS_11_VASCL in RSA3.
The details are as follow.
When importing object "MC11VA0SCL_TAB", the structure did not match the
structure of the target object. The error occurred in component
no. 567.
This may be due to one of the following reasons:
- the structure is actually different (the next field has, for
example, a different data type) or
- the same sequence of components were exported and imported,
but the fields were from other include units.
I have checked source and target fields and those are of same length and data type.
Could you please give some points why this short dump occurs.
Thanks
Konda Reddy

Hi,
This error is not between BI and R/3. It is within R/3. You may have setup data and then modified the datasource.
Delete setup data, generate your datasource again. Setup data and try again.
If you are on a live system with data setup after a downtime and you do not want to delete it, then bring your datasource to the original state when you setup data and pull data.
Cheers....

Dump While Executing ME21N, ME22N and ME23N

Similar Messages

Maybe you are looking for