An interesting abap dump in MV45AFZZ  when delete order

Hi all.
In 'userexit_save_document_prepare' form of MV45AFZZ which is the SO order save uerer exit, I insert 'message e398(00)...'.
When I save the order , the message does work.
When I delete the order , program dump on message .
Because ...
During "Exit Command" processing, the program tried to send a " " message.
    This is not allowed at this point in processing.
    The program had to be terminated.
I think SAP dump it with reason.
Delete is "Exit Command"
But how can I stop the  'delete' process in MV45AFZZ.
Is there a globe variable names like 'NOT_SAVE' or a standard message table to collect my message instead of  message it directly.
Edited by: shen yu on Jun 4, 2008 5:46 AM
Edited by: shen yu on Jun 4, 2008 5:46 AM
Edited by: shen yu on Jun 4, 2008 5:47 AM

Hi Shen,
Bypass the logic of error message when saving the order in user exit 'userexit_save_document_prepare' by checking the value of the field T180-TRTYP.
then try inserting the same logic for error message in the user exit USEREXIT_DELETE_DOCUMENT (checking the value of the field T180-TRTYP)
Rewards points if this is helpful,
Regards,
Dwaraka.

Similar Messages

  • ABAP Dump is encountered when doing the negative subsequent adjustment

    Hi Experts !!!
    An ABAP Dump is encountered when doing the negative subsequent adjustment (posting a 102 movt type) on a Purchase Order via the Z function module. The dump only happens if the scenario satisfies the following conditions:
    1.Material is either (but may not be limited to) 3000000234, 4000000121, 3000000210 (These are the only reported materials)
    2.Order unit in Purchase Order is in MT
    3.At 2nd weigh, Net Weight is less than PO Order Qty.
    Note: No error occurs if same process is done via MIGO.
    Initial Analysis:
    An exception/error occurs when calling function u201CMB_CREATE_MATERIAL_DOCUMENT_UTu201D .
    Please see below error anlysis report from after executin Zfunction module code.
    Error analysis
       Short text of error message:
       Material 3000000234 / US01 Column 0001: MSEG-BPMNG not in quantity table
       /not consistent
       Long text of error message:
        Diagnosis
            Before the system posts a material document for an HPM/TDP material
            (MARA-CMETH = 1 or 2), it performs the following consistency
            checks:
            o   For each unit of measure in the Unit of Measure Group
                (MARC-UOMGR), a line item  has to be present  in the additional
                quantity appendix table (Table MSEGO2)
            o   For each unit of measure in the main core table MSEG that is
                not initial a line item, has to be present in the additional
                quantity appendix  table (Table MSEGO2) and the corresponding
                packed format quantities have to be identical.
                This way, inconsistent stock level updates can be prevented.
        System Response
            The system stops processing.
        Procedure
            If the error is reproducible, contact your system administrator.
        Procedure for System Administration
            The inconsitency can have several reasons, for example:
            o   Incorrect postings from external systems using function module
                MB_CREATE_GOODS_MOVEMENT
            o   Handling errors
            o   Application programming errors
       Technical information about the message:
    Message class....... "O3"
    Number.............. 359
    Variable 1.......... 3000000234
    Variable 2.......... "US01"
    Variable 3.......... 0001
    Variable 4.......... "BPMNG"
    Please let me know,if you want some other details.

    Problem Issolved

  • ABAP dump Error while creating service order in PCUI.

    Hi Experts,
                     We are getting following ABAP dump error while creating service order in PCUI which is working fine in GUI.
    Runtime Errors         RAISE_EXCEPTION
    Date and Time          02.01.2008 14:55:38
    Short text
    Exception condition "TYPE_NOT_FOUND" raised.
    What happened?
    The current ABAP/4 program encountered an unexpected
    situation.
    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
    A RAISE statement in the program "CL_CRM_ELEMDESCR==============CP" raised the
    exception
    condition "TYPE_NOT_FOUND".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    Short description of exception condition:
    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.     
    We have added custom fields in the service application. these custom fields with Z-structure & data elements  are included in BSP structure CRMT_BSP_SRV_OIC_SRCHRES in development system.But the same Z structure & custom fields are exist in the production system but not included in BSP Structue CRMT_BSP_SRV_OIC_SRCHRES.
    This may be the reason resulting this ABAP dump error in PCUI while creating Service order.
    How these Z structures can be included in the BSP Structure CRMT_BSP_SRV_OIC_SRCHRES in production system?
    Helpful answers would be rewrded max points as it is high priority issue.
    Regards,
    Basavaraj Patil

    Hi Thirumala,
    Thnaks for the reply.
                I have enhanced service application using transaction EEWB to add new custom fields. these fields are there in Z structure created by the system in production system. All the transports are moved to target system. Problem is that Z structure( contains custom fields)  created while doing  EEWB is not included in BSP structure.
    I f transports are missed to move to target system, Is there any other alternative to solve this problem?
    Regards,
    Basavaraj Patil

  • Abap dump error while release Production order

    Dear Gurus,
                          Abap dump error is creating while release production order , pour some light on this issue.
    Regards,
    Kamal

    Hello,
      use transaction ST22 to analyze the error type. There you have the detail of the error message, the program and the line of the ABAP code where the dump was triggered.
    Best regards,
    Andrea

  • ABAP Dump ITAB_DUPLICATE_KEY deleting ODS data

    Hi,
    We've got an abap dump while trying to delete the ODS data content. The abap dumps registers a ITAB_DUPLICATE_KEY in the program SAPLRSAODS function module RSAR_ODS_GET. We're using BW3.5 patch 4.
    Tried looking at the OSS notes but could not find any relevant oss notes that is on BW3.5. Has anyone manage to solve/experience this issue ?

    look at these previous threads
    What does this runtime error mean?
    "Runtime Error ITAB_DUPLICATE_KEY"
    ITAB_DUPLICATE_KEY dump in the PSA tree or search
    Hope it helps.
    Regards

  • ABAP dump is coimg in PA

    HI Experts,
    ABAP dump is coming when i click on profitabiliy segemny in accounting document.
    And dump says:Profitabilty segment "xxxxxxx" does not exist in operating conern "xxxx"
    the system tried to find characteristics from the segment table "CE41000" using the segment number  "xxxxxxx" in operating concern.
    But profitability analysis document is posted in the system for both the line items.
    Please help me.
    Thanks,
    vani

    Hi,
       I believe you are getting KE499 error.
      Normally a KE499 error is caused by one of the following:
    - 1) The assignment between controlling area and operating concern was changed.
    (for that please see SAP Note 199959)
    - 2) Data was deleted / archived from table CE41000;
    - 3) Profitability segments were deactivated i.e table CE41000 was archived
    If during the program run the respective operating concern are posted to, it can result in problems with abnormal terminations with error message KE499.
    > you read request for that the corresponding stage in SAP Note 383728.
    Please check if any of the above activities were done at your end.
    regards
    Waman

  • ABAP dump in ECC 6.0 - Need OSS notes

    ABAP dump is coming when retriving data between select-endselect.
    Runtime Errors         DBIF_RSQL_INVALID_CURSOR
    Except.                CX_SY_OPEN_SQL_DB
    The problem cannot be resolved without correcting the application
    program.
    The statements MESSAGE, COMMIT WORK, ROLLBACK WORK, CALL SCREEN,
    BREAK-POINT, WAIT, CALL FUNCTION ... DESTINATION, CALL FUNCTION ...
    STARTING NEW TASK, RECEIVE RESULTS, CALL SELECTION-SCREEN, CALL
    DIALOG, CALL TRANSACTION cannot be used within a database
    loop.
    You can collect the data needed for these statements together in an
    internal table and process them
    in a loop.
    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:
    "DBIF_RSQL_INVALID_CURSOR" "CX_SY_OPEN_SQL_DB"
    Can you please give the OSS notes no. if anything is available.

    Hi Sreedevi..
    In the dump report, the piece of code where the dump occured will be shown
    something with >>>>>> sign in the line...
    Please copy and paste this peice of code..
    Thanks and Best Regards,
    Vikas Bittera.
    **Reward if useful**

  • 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

  • Delivery Can not Delete Delivery due to ABAP Dump

    I have a strange situation on a delviery that is in our production client.  We rec;d an APAB dump whenposting goods issue in  delivery (successfully posted but still ABAP'd out) this was  due to the sales unit field calculated to high of a qty due to a material master setting in the price unit qty,  This has been fixed in the material master but we can not get to the delivery to delete it.  I have succefully reversed goods issue and successfully cancelled TO confirmation.  I can not get to the delivery to delete it.  I can not reject line items on the sales order due to it having subsequent documents.  Does anyone know how this can be accomplished?  Please advise/comment experiences.  It would be GREATLY appreciated.  See Below ABAP dump if it helps....
    Kim
    Runtime Errors         DYNPRO_FIELD_CONVERSION
    Date and Time          05/16/2011 11:05:21
                       Screen name.............. "SAPMV50A"
                       Screen number............ 1102
                       Screen field............. "LIPSD-PIKMG"
                       Error text............... "FX015: Sign lost."
         Other 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".
         4. Details about the conditions under which the error occurred or which
         actions and input led to the error.

    Symptom
    A Warehouse Management-relevant (WM-relevant) delivery item is picked, and then the WM transfer order is canceled again using LT0G.
    If the storage location for the delivery is changed to a non-WM-relevant storage location and a pick quantity is entered in the delivery, this pick quantity is assigned to the document flow record for the cancellation of the WM transfer order. This is incorrect.
    The incorrect document flow record is stored in the database when you save the delivery.
    This results in the ABAP runtime error "DYNPRO_FIELD_CONVERSION" when the delivery is processed again with VL02 or VL02N.
    Other terms
    PIKMG, WM-TA, Warehouse Management (WM) transfer order (TO), VBFA, RFMNG, SAPMV50A, MV50AO0F, FELDAUSWAHL, MV50AO0F, LIPSD-PIKMG
    Reason and Prerequisites
    This problem is caused by a program error.
    Solution
    Implement the specified correction to prevent this inconsistency in the table VBFA from occurring again.
    Correction report Z_CORRECT_VBFA_FROM_LTAP:
    Implement the correction report specified below with transaction SE38 using the attributes:
    Title            Correction report for note 435274
    Type            1  Executable program
    Status                T    Test program
    Application              V     Sales
    Input parameters for execution of the report:
    P_VBELN: Document number of the delivery that has document flows
             for the WM transfer order that are to be corrected.
            While the report is running, make sure that
            no changes are made to the relevant
            document.
    P_TEST = 'X': Analysis:   Analysis of the missing document flow records;
                            no changes in the document.
    P_TEST = ' ': Correction: Document flow records between delivery and
                            WM transfer order are corrected.
    refer SAP Note 435274 - Negative pick quantity in the delivery

  • ABAP Dump when executing DTP

    Dear gurus:
           I just faced an annoying problem when executing DTP in t-code RSA1. It appears an  ABAP dump here. The ABAP dump is briefly shown below. And I found that it seems to be an authorization problem, because when I use a new account which has SAP_ALL authorization, then it works. So it may lack of some authorizations, but it's hard to figure it out. T-code su53 cannot check it properly. Need your help and thanks a lot.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          2007.06.20 11:17:30
    Short text
         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:
         Invalid program status
         Long text of error message:
         Technical information about the message:
         Message class....... "RSBK"
         Number.............. 299
         Variable 1.......... " "
         Variable 2.......... " "
         Variable 3.......... " "
         Variable 4.......... " "

    Hai Wei,
    This dump is due missing of OCX files while installing SAP GUI Front end just find out the exact files and copy and paste them in the Front end files files then ur prob will be solved.......
    If in case any issues let me know.
    Regards
    Madhavi

  • ABAP dump when user login in to PRD system

    Hi Experts,
    From today morning our users are facing one severe issue.The users when ever they login into the system the ABAP dump is occuring like "Database inconsistency: Start transaction SICK ",when i execute the SICK t-code it is showing errors.
    SAP System Check
    no application server offers an VB service
    Severe problems were detected during initial system check.
    Please, do not use that system before fixing these problems.
    our go live was before one month only,now we are facing this issue.our kernel release is 740 and DB sybase ASE 15.7.0.1010. please suggest us what can we do.
    regards,
    Patan Thavaheer.

    |15.05.2014                        Active parameters                        12:47:40                                                                                                                                                                                                                         |
    |Parameter Name                             |Parameter value                                                                                                                 Parameter Value - Continued                                                                                                     |
    |login/disable_multi_gui_login              |1                                                                                                                                                                                                                                                               |
    |rdisp/wp_no_enq                            |1                                                                                                                                                                                                                                                               |
    |login/no_automatic_user_sapstar            |0                                                                                                                                                                                                                                                               |
    |SAPSYSTEMNAME                              |XXX                                                                                                                                                                                                                                                          |
    |SAPGLOBALHOST                              |XXXXXX                                                                                                                                                                                                                                                          |
    |SAPSYSTEM                                  |00                                                                                                                                                                                                                                                              |
    |INSTANCE_NAME                              |DVEBMGS00                                                                                                                                                                                                                                                       |
    |DIR_CT_RUN                                 |$(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64                                                                                                                                                                                                                           |
    |DIR_EXECUTABLE                             |$(DIR_INSTANCE)\exe                                                                                                                                                                                                                                             |
    |DIR_PROFILE                                |\\XXXXXX\sapmnt\XXX\SYS\profile                                                                                                                                                                                                                                 |
    |_PF                                        |$(DIR_PROFILE)\XXX_DVEBMGS00_XXXXXX                                                                                                                                                                                                                             |
    |SETENV_00                                  |PATH=$(DIR_EXECUTABLE);%PATH%                                                                                                                                                                                                                                   |
    |Start_Program_00                           |immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF)                                                                                                                                                                                                               |
    |_CPARG0                                    |list:$(DIR_GLOBAL)/syb/NTAMD64/cpe_sybjdbc.lst                                                                                                                                                                                                                  |
    |_CPARG1                                    |source:$(DIR_GLOBAL)/syb/NTAMD64                                                                                                                                                                                                                                |
    |Start_Program_01                           |immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG0) $(_CPARG1)                                                                                                                                                                                         |
    |Start_Program_02                           |immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF)                                                                                                                                                                                                               |
    |_CPARG2                                    |list:$(DIR_GLOBAL)/syb/NTAMD64/cpe_sybodbc.lst                                                                                                                                                                                                                  |
    |_CPARG3                                    |source:$(DIR_GLOBAL)/syb/NTAMD64/sybodbc                                                                                                                                                                                                                        |
    |Start_Program_03                           |immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG2) $(_CPARG3)                                                                                                                                                                                         |
    |_CPARG4                                    |list:$(DIR_CT_RUN)/sapcrypto.lst                                                                                                                                                                                                                                |
    |Start_Program_04                           |immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG4)                                                                                                                                                                                                    |
    |SAPJVM_VERSION                             |6.1.048                                                                                                                                                                                                                                                         |
    |DIR_SAPJVM                                 |$(DIR_EXECUTABLE)$(DIR_SEP)sapjvm_6                                                                                                                                                                                                                             |
    |jstartup/vm/home                           |$(DIR_SAPJVM)                                                                                                                                                                                                                                                   |
    |Start_Program_05                           |immediate $(DIR_CT_RUN)\strdbs.cmd XXX                                                                                                                                                                                                                          |
    |sec/libsapsecu                             |$(ssl/ssl_lib)                                                                                                                                                                                                                                                  |
    |ssf/ssfapi_lib                             |$(ssl/ssl_lib)                                                                                                                                                                                                                                                  |
    |rdisp/wp_no_dia                            |10                                                                                                                                                                                                                                                              |
    |rdisp/wp_no_btc                            |3                                                                                                                                                                                                                                                               |
    |_DW                                        |$(DIR_EXECUTABLE)\disp+work$(FT_EXE)                                                                                                                                                                                                                            |
    |Start_Program_06                           |local $(_DW) pf=$(_PF)                                                                                                                                                                                                                                          |
    |_IG                                        |$(DIR_EXECUTABLE)\igswd$(FT_EXE)                                                                                                                                                                                                                                |
    |Start_Program_07                           |local $(_IG) -mode=profile pf=$(_PF)                                                                                                                                                                                                                            |
    |rdisp/wp_no_vb                             |1                                                                                                                                                                                                                                                               |
    |rdisp/wp_no_vb2                            |1                                                                                                                                                                                                                                                               |
    |rdisp/wp_no_spo                            |1                                                                                                                                                                                                                                                               |
    |ssl/ssl_lib                                |$(DIR_EXECUTABLE)$(DIR_SEP)$(FT_DLL_PREFIX)sapcrypto$(FT_DLL)                                                                                                                                                                                                   |
    |SETENV_01                                  |SECUDIR=$(DIR_INSTANCE)/sec                                                                                                                                                                                                                                     |

  • Deleting XI Messages - Abap dump in Delete job

    Hi all,
    I would like to know if we could directly delete xml messages without archiving. We are working on a sandbox system.
    I tried to schedule a delete job  ARCDEL_Delete_20080612115401 / 11540100.
    It cancelled giving an abap dump CALL_FUNCTION_NOT_FOUND.
    the abap dump is as follows:
        The function module " " is called,
        but cannot be found in the library.
        Error in the ABAP Application Program
        The current ABAP program "ARCDEL_DELETE_PARA" had to be terminated because it
         has
        come across a statement that unfortunately cannot be executed.
    Any idea why a function module with no name is called?
    Thank you.
    Regards,
    Raghavan

    Hi Raghvan,
    There are few ABAP report for that
    RSXMB_DELETE_MESSAGES
    RSXMB_DELETE_ARCHIVED_MESSAGES
    check this blog for reference :
    /people/gourav.khare2/blog/2007/12/21/mass-cancellation-of-error-messages--xi
    Sachin

  • Regarding ABAP Dump found when saving the job.

    Hi all,
    Generally we create a job and once the job is created,we rasie Sales Order,Purchase Order and so on.
    When we create a job we give the details of the Sold -to-party,client,parent and child job text,advertising category,project type, sales organisation,Cost and profit center,person incharge and purchase division.
    After submitting these details the job gets created and the job number will be generated.
    But now we have created a new Sales Organisation, which is leading to ABAP Dump.
    The functional people have concluded that there is nothing wrong in the configaration settings.
    If we enter an existing sales organisation in the job creation process the job is getting created and the job number is displayed.
    But if we try to enter a new sales organisation the ABAP Dump is comming.
    After debugging we came to know that BAPI function Module called
    Bapi Project Maintain Call and inside that there is another bapi call called
    BAPI_PROJECT_MAINTAIN which is taking some structures as inputs among them
    this new sales org is there.

    Hi all,
    Is there any answer regarding this question.
    Thanx in advance

  • ABAP Dump when running S_ALR_87100205 (RFHABU00N)

    Hi,
    We are implementing New GL for a company code in Turkey. When I trying to run the report RFHABU00N for non-leading ledger, I am getting an abap dump because the program is not able to report the output for non-leading ledger documents. The report outputs correct information when executed for the leading ledger.
    has any one else faced this issue in the past and if so how was it resolved.
    We are currently on SAP ECC 6.04.
    Thanks,
    Nitin

    Hi,
    What is the dump message exactly? Anyway, for execution of this report for non-leading ledger, please, consult the following notes:
    1883338 - RFHABU00N Long runtimes and termination
    1965855 - RFHABU00/RFHABU00N: General Ledger View
    1965562 - SAPDBBRF: Fiscal year not correctly delimited for non-leading ledgers
    1939154 - RFHABU00N: Documents from non-leading ledgers ignored
    Regards,
    Eli

  • 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.

Maybe you are looking for