Short dump while activating process chain

Please let me know the cause of short dump while activating process chain.. when trying to activate local process chains in metachain it is causing dump

Can you share more details about error.
Have you done any changes to local chain? or is this is new chain?
Try to remove meta chain from schedule, later activate your local chain and meta chain.
schedule your meta chain.

Similar Messages

  • Short Dump while activating Transformation through Program

    HI All,
    I am getting short dump while activating - Inactive Transformation through Program RSDG_TRFN_ACTIVATE.
    However while i can activate single Transformation but if run without selection, I am getting this dump.
    Short Description of Dump -
    Category          
    ABAP Programming Error
    Runtime Errors    
    ASSERTION_FAILED
    ABAP Program      
    CL_RSAR_FORMULAS==============CP
    Application Component  BW-WHM-DST
    Date and Time     
    Please Guide.
    Prasad

    Hi Prasad,
    Have you changed the 'Object Status' from INA to ACT when using the program RSDG_TRFN_ACTIVATE?
    You can also refer to the note SAP Note 1030987 - Activation of transformations dumps
    regards,
    Ashvin

  • Error while activating Process Chains

    Hi all,
    while activating the Process Chains, i am getting the following error "Job BI_PROCESS_PSAPROCESS could not be scheduled. Termination with returncode 8"
    when i double click on the error msg, i got the following help msg: "
    <i>Message no. RSPC065
    Diagnosis
    Program RSPROCESS is to be scheduled as job BI_PROCESS_PSAPROCESS under user ALEREMOTE.</i>
    Can any one please show some way to solve this problem? please do this favor, i have been suffering with error for a long time.
    Points will be given
    Thanks
    Ganesh

    Hi,
    Just analyze the error message that you get while activating the PC, don't give any server name.If you are trying to run process chain using Flat file, it won't work,
    and you should have source system R/3 or you have own datasources in BW system itself at that toime you can use PC to extract data. If your source system is Flat ile, it won't work. other wise you should place your flat file in application server, using AL11 tcode.
    <b>OSS : 511475</b>
    <b>Symptom</b>
    You cannot schedule or perform any batch jobs with the BW or source system background user.
    The error RSPC 065 occurs in the process chains:"Job could not be scheduled, termination with return code 8"
    <b>Other terms</b>
    RSPC065
    <b>Reason and Prerequisites</b>
    The user type is
    "CPIC" up to 4.6B
    "Communication" as of 4.6C
    This user type may not execute or start any batch jobs, irrespective of the user authorizations.
    <b>Solution</b>
    Set the type of background user to
    "Background" up to 4.6B
    "System" as of 4.6C
    This user type corresponds to the "Communication" type and may also perform background functions.
    Through the Customizing, the BW user is automatically created by mistake as a communication user.Depending on your BW system release, you can solve this problem as follows:
    BW 2.0B
               Import Support Package 24 for 2.0B (BW2.0B patch24 or SAPKW20B24) into your BW system. The Support Package is available once note 456551 with the short text "SAPBWNews BW 2.0B Support Package 24", which describes this Support Package in more detail, has been released for customers.
    BW 2.1C
               Import Support Package 16 for 2.1C (BW2.1C patch16 or SAPKW21C16) into your BW system. The Support Package is available once note 456566 with the short text "SAPBWNews BW 2.1C Support Package 16" has been released for customers.
    BW 3.0A
               Import Support Package 8 for 3.0A (BW3.0A patch08 or SAPKW30A08) into your BW system. The Support Package is available once note 452632 with the short text "SAPBWNews BW 3.0A Support Package 08" has been released for customers.
    <b></b>

  • DBIF_REPO_SQL_ERROR short dumps while activating data in ODS

    Hi All,
    We are using BW3.5 with Oracle 9.2 on AIX 5.3 box, from the past few days we are getting DBIF_REPO_SQL_ERROR short dumps frequently while activating data in ODS.
    Runtime Error          DBIF_REPO_SQL_ERROR
    Date and Time          08.01.2008 13:01:08
         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.
         Internal call code.........: "[REPO/*/43/LOAD/CX_SY_OPEN_SQL_DB=============CP
         Please check the entries in the system log (Transaction SM21).
         You may able to find an interim solution to the problem
         in the SAP note system. If you have access to the note system yourself,
         use the following search criteria:
         "DBIF_REPO_SQL_ERROR" C
         "SAPLRSSM_PROCESS" or "LRSSM_PROCESSF04"
         "CHECK_IF_ANALYZE_IS_NESSESSARY"
    System environment
        SAP Release.............. "640"
        Application server....... "psapdb"
        Network address.......... "158.58.65.11"
        Operating system......... "AIX"
        Release.................. "5.3"
        Hardware type............ "00CD615C4C00"
        Character length......... 16 Bits
        Pointer length........... 64 Bits
        Work process number...... 22
        Short dump setting....... "full"
        Database server.......... "psapdb"
        Database type............ "ORACLE"
        Database name............ "BWP"
        Database owner........... "SAPBWP"
        Character set............ "C"
        SAP kernel............... "640"
        Created on............... "Oct 29 2006 20:49:57"
        Created in............... "AIX 1 5 00538A4A4C00"
        Database version......... "OCI_920 "
        Patch level.............. "155"
        Patch text............... " "
        Supported environment....
        Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
         10.2.0.."
        SAP database version..... "640"
    Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
    Memory usage.............
    Roll..................... 16192
    EM....................... 16759424
    Heap..................... 0
    Page..................... 24576
    MM Used.................. 6604384
    MM Free.................. 1772536
    SAP Release.............. "640"
    User and Transaction
        Client.............. 200
        User................ "R3REMOTE"
        Language key........ "E"
        Transaction......... " "
        Program............. "SAPLRSSM_PROCESS"
        Screen.............. "SAPMSSY0 1000"
        Screen line......... 6
    Information on where terminated
        The termination occurred in the ABAP program "SAPLRSSM_PROCESS" in
         "CHECK_IF_ANALYZE_IS_NESSESSARY".
        The main program was "RSPROCESS ".
        The termination occurred in line 1143 of the source code of the (Include)
         program "LRSSM_PROCESSF04"
        of the source code of program "LRSSM_PROCESSF04" (when calling the editor
         11430).
        The program "SAPLRSSM_PROCESS" was started as a background job.
        Job name........ "BI_PROCESS_ODSACTIVAT"
        Job initiator... "RPRIYANKA"
        Job number...... 02010102
    Also we have a failed job here. Here is the job log.
    Job log overview for job:    BI_PROCESS_ODSACTIVAT / 02010102
    Date       Time     Message text
    08.01.2008 13:01:00 Job started
    08.01.2008 13:01:00 Step 001 started (program RSPROCESS, variant &0000000000188, user ID R3REMOTE)
    08.01.2008 13:01:02 Activation is running: Data target HBCS_O25, from 1,758 to 1,767
    08.01.2008 13:01:02 Data to be activated successfully checked against archiving objects
    08.01.2008 13:01:02 SQL: 01/08/2008 13:01:02 R3REMOTE
    08.01.2008 13:01:02 ANALYZE TABLE "/BIC/AHBCS_O2540" DELETE
    08.01.2008 13:01:02 STATISTICS
    08.01.2008 13:01:02 SQL-END: 01/08/2008 13:01:02 00:00:00
    08.01.2008 13:01:02 SQL: 01/08/2008 13:01:02 R3REMOTE
    08.01.2008 13:01:02 BEGIN DBMS_STATS.GATHER_TABLE_STATS ( OWNNAME =>
    08.01.2008 13:01:02 'SAPBWP', TABNAME => '"/BIC/AHBCS_O2540"',
    08.01.2008 13:01:02 ESTIMATE_PERCENT => 1 , METHOD_OPT => 'FOR ALL
    08.01.2008 13:01:02 INDEXED COLUMNS SIZE 75', DEGREE => 1 ,
    08.01.2008 13:01:02 GRANULARITY => 'ALL', CASCADE => TRUE ); END;
    08.01.2008 13:01:05 SQL-END: 01/08/2008 13:01:05 00:00:03
    08.01.2008 13:01:05     SQL-ERROR: 603 ORA-00603: ORACLE server session terminated by fat al error
    08.01.2008 13:01:05 System error: RSDU_ANALYZE_TABLE_ORA/ ORACLE
    08.01.2008 13:01:08 ABAP/4 processor: DBIF_REPO_SQL_ERROR
    08.01.2008 13:01:08 Job cancelled
    Listener is working fine, Checked the RFC connections, Tried restarting the system, tried adding space to the TEMP tablespace as well as PSAPBWP, but they didn't work.
    Please help.

    The problem got solved as there were DB errors like ORA-01114: IO error writing block to file 256 (block # 126218).
    Here the point to be notes is file 256. The number greater than 255 indicates a temp datafile. This indicates an issue with PSAPTEMP tablespace. When checked on PSAPTEMP tablespace, one of the filesystems where one temp data file sitting was full. The filesystem was 100% full. This will prevent the temp datafile to grow and shrink as and when required.
    So, adding more space to the filesystem solved the problem.
    Thanks to everyone who have shown interest in solving my problem.

  • Short Dump while Activating a Heirarchy

    Hi Experts,
    I have a hierarchy which is in M version, I am trying to copy hierarchy from Quality to Dev system.
    The hierarchy in DEV system is in M version. When I try to activate the Hierarchy I am getting a short dump which I am not able to understand.
    I have tried also with the ABAP programe to activate it but still I am getting this.
    Sorry to paste all the dump but can any one advise what could be reasons behind heirarchy not getting activated.
    Thanks,
    Tati.
    Please find the Dump message.
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "CL_RSSH_MESSAGE_HANDLER=======CP" had to be
         terminated because it has
        come across a statement that unfortunately cannot be executed.
    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
        Only message types A, E, I, W, S, and X are allowed.
    Information on where terminated
        Termination occurred in the ABAP program "CL_RSSH_MESSAGE_HANDLER=======CP" -
         in "CALL_MESSAGE".
        The main program was "RSSH_HIERM_START_NEU ".
        In the source code you have the termination point in line 11
        of the (Include) program "CL_RSSH_MESSAGE_HANDLER=======CM003".
    Source Code Extract
    Line  SourceCde
        1 METHOD call_message .
        2
        3   FIELD-SYMBOLS: <l_s_msg> TYPE gt_s_msg.
        4
        5   READ TABLE p_t_msg INDEX 1 ASSIGNING <l_s_msg>.
        6   IF sy-subrc <> 0.
        7     MESSAGE x000.
        8   ENDIF.
        9
       10   <l_s_msg>-handled = rs_c_true.
    >>>>>   MESSAGE ID <l_s_msg>-msgid TYPE <l_s_msg>-msgty NUMBER <l_s_msg>-msgno
       12     WITH <l_s_msg>-msgv1 <l_s_msg>-msgv2 <l_s_msg>-msgv3 <l_s_msg>-msgv4.
       13
       14
       15 ENDMETHOD.                    "CALL_MESSAGE

    Hi Prasad,
    Have you changed the 'Object Status' from INA to ACT when using the program RSDG_TRFN_ACTIVATE?
    You can also refer to the note SAP Note 1030987 - Activation of transformations dumps
    regards,
    Ashvin

  • OBJECTS_OBJREF_NOT_ASSIGNED Dump while Installing Process Chain

    Hi Gurus,
                 I got OBJECTS_OBJREF_NOT_ASSIGNED dump while installing Business Content process chian "0TCT_C2_INIT_P01".
    Also 6 info packages were not delivered in business content for the above chian.
    Any Help.
    Regards,
    Anil

    Check if this note helps..though it is for infoobjects
    <a href="https://websmp202.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1019055&_NLANG=E">Note 1019055 - Runtimer errors when activating InfoObjects</a>
    Message was edited by:
            Manga Paidikondala

  • Reg : Short Dump While Activating Workflow

    Hi All,
    This morning I added a condition step in my workflow and created two custom methods in the corresponding BO and used them in the task. Initially when i made the changes in the workflow and tested it, it was working fine. But after sometime, when I did the necessary binding and tried to activate the workflow, the workflow started resulting in short dump.
    Below is the dump analysis.
    SAPSQL_ARRAY_INSERT_DUPREC
    The ABAP/4 Open SQL array insert results in duplicate database records.
    000310        L_OTYPE EQ ORG_OBJTYPE_WORKFLOW.
    000320       LOOP AT ACT_LINES.
    000330         MOVE-CORRESPONDING ACT_WFDKEY TO ACT_LINES.
    000340         MOVE ACT_CLIENT TO ACT_LINES-CLIENT.
    000350         MODIFY ACT_LINES.
    000360       ENDLOOP.
    000370     ELSE.
    000380       MESSAGE E280 WITH L_OTYPE RAISING INVALID_OBJECT_TYPE.
    000390     ENDIF.
    000400
    000410   *- insert lines table
    ------>     INSERT SWD_LINES CLIENT SPECIFIED FROM TABLE ACT_LINES.
    000430     IF SY-SUBRC NE 0.
    000440       MESSAGE E281 WITH SY-SUBRC 'SWD_LINES'
    000450                    RAISING INTERNAL_DATABASE_ERROR.
    000460     ENDIF.
    000470
    000480   *- commit
    000490     IF DO_COMMIT NE ' '.
    000500       COMMIT WORK.
    000510     ENDIF.
    000520
    000530   ENDFUNCTION.
    I tried searching sdn. But all other posts were related to passing entries from internal table to DB. Also I'm not even sure if i can raise a OSS, because a few minutes back the system was working fine and all of sudden this started happening.
    So can you please guide me what I am missing and how can i fix this?
    Thanks & Regards,
    Raj

    Hi Rick,
    When I get acitvate the workflow, the workflow template is gettign active & saved and after that the system results into short dump. And also when i try creating a PR and test this workflow, in SWEL, i can see the below message in RFC status field.
    The ABAP/4 Open SQL array insert results in duplicate database records..
    I haven't done any duplicate binding. Also I checked what you suggested. Didn't work. Also checked my newly added code. But I'm not accessing database directly anywhere. All is done via SAP standard function module.
    Even if i try to display this workflow in PFTC, the system is resulting in the same short dump.
    What could be the reason?
    Regards,
    Raj
    Edited by: Raj  Karunanidhi on Feb 23, 2010 5:30 AM

  • Error while activating process chains from Business Content

    Hi All,
    I am trying to activate the SAP Business Content Process Chains, which load data to 0PM_DSO2 in Plant Maintenance Area -
    1.Delta Upload : MTTR / MTBR   (0PM_DELTA_P02)
    2.Initialisation  :   MTTR / MTBR  (0PM_INIT_P01 )
    And they are failing with the error
    "Object  0PAK_BZJNGI4SYTTJM5DXY8IPMHB0C could not be found in version
    Message no. RS_EXCEPTION280"
    "Message Text
    Object  0PAK_EYQGZ09K9SFFUMOFRQ0730LJ0 could not be found in version
    Technical Data
    Message type__________ E (Error)
    Message class_________ RS_EXCEPTION (Exception Messages)
    Message number________ 280
    Message variable 1____ 
    Message variable 2____ 0PAK_EYQGZ09K9SFFUMOFRQ0730LJ0
    Message variable 3____ 
    Message variable 4____  "
    In the collected objects, these two infopacks are not present also.
    Can you please let me know how to proceed?
    Many Thanks in Advance,
    Vineeth

    Hi
    Make sure these 2LIS_17_I0NOTIF and 2LIS_18_I0NOTIF datasources are being installed.
    Check these links.
    http://help.sap.com/saphelp_nw70/helpdata/EN/e7/082888ca2f994794986448568aec2d/frameset.htm
    http://help.sap.com/saphelp_nw70/helpdata/EN/e7/082888ca2f994794986448568aec2d/frameset.htm
    Chandu.
    Edited by: Chandu on Jan 22, 2009 2:24 PM

  • UNCAUGHT_EXCEPTION with msg CX_RSR_X_MESSAG while scheduling Process chain

    Hi Gurus,
    We are facing a short dump while scheduling process chains, as follows:
    <BR><BR>
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_RSR_X_MESSAGE
    <BR><BR>
    Error analysis
        An exception occurred which is explained in detail below.
        The exception, which is assigned to class 'CX_RSR_X_MESSAGE', was not caught
         and
        therefore caused a runtime error.
        The reason for the exception is:
        No text available for this exception
    <BR>
    Information on where terminated
        Termination occurred in the ABAP program "SAPLRRMS" - in "RRMS_X_MESSAGE".
        The main program was "RSPC_MAINTAIN_SINGLE ".
        In the source code you have the termination point in line 82
        of the (Include) program "LRRMSU13".
    <BR>
    We tried to schedule it as a remote process chain from some other system it cancelled the job there with an ERROR_MESSAGE. We checked the RFC Connections at the source system side but it is working properly. We then tried to schedule the chain manually, we had this exception. Then we tried to have a look at previous logs of the process chain. It had this exception. We tried to reactivate the chain it was successful but when tried to schedule the chain same issue again. We tried to run the Meta chains under the same chain separately. They too gave us the same exception.
    Please help.
    Regards,
    Sourabh Deo

    S Simran wrote:
    Hi,
    >
    > Ours is a fresh installation..
    >
    > When i am loading for the first time till PSA it is successful..
    >
    > As HR data sources are 3.5 datasources, i am loading cube via infopackage..
    >
    > When i start the load to cube it is giving me dump with exception CX_RSR_X_MESSAG.
    >
    > i checked note  615389 which talks about "buffering of number range object BIM9999998".  the 0REQID is not buffered, but it does not throw any error msg in RSRV to correct the error..
    >
    > and one more note 1157796 which talks about patches with version BI 7.0.
    >
    > Now we are in BI 730 with heighest level 0005.
    >
    > Not sure how to solve this error
    >
    > Any ideas?
    What's your SP? Are you having any master data updates left unattended? Check the Master data objects, check the flows. Related SAP Notes : 914304 / Check 967202(SP10) and 998673(SP11), 1157796, 763203 and 615389
    Edited by: Arun Bala G on Feb 12, 2012 9:50 PM

  • Errror when activating process chain

    Hi All,
    Geeting the error while activing process chains in Quality.
    Error is *'Node Characteristic 0classnum is not entered as hierarchy characteristic for 0material*
    can any one help on this.
    Thanks in Advance.
    Srinivas

    Hi
    This is not advisable to activate a process chain in quality directly. You should do it in development and then transport it across.
    This error is realated to hierarchy. Do you have a hierarchy load attached to this chain?
    Check the hierarcy first. Then activate the chain.
    Cheers
    Chanda

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

  • Short Dump while execuition of DTP.

    Hi,
    I got short dump while  execuiting the DTP.
    Error messages shows as below:
    1.The database returned a value containing an error
    2.An exception with the type CX_SY_OPEN_SQL_DB occurred, but was neither handled locally, nor declared in a RAISING clause
    3.Exception CX_SY_NO_HANDLER logged
    Could you please help us in solving this issue.
    Regards,
    Suman.

    hi,
    an error like this comes usually in 2 cases
    1) not enough resources are available to carry out loads.in this case increase no of parallel processes to 2-3 in dtp setting,check the option get delta request by request(if its a delta load) and decrease packet size to 10000(from default 50000)
    2)fileld to field assignment is not proper:
    u need to check if there is any source field with lenth lets say 5 ans is getting assisgned to a target field length lets say 4.in this case dumps will come
    please check the error message in st22 and here you can also check the termination point.please check in option Chosen variables /contents of system fileds where you can get temp values at point of termination.here you can pinpoint values at which prog is throwing dumps.

  • Short dump while navigate to second view :: "OBJECTS_OBJREF_NOT_ASSIGNED_NO

    Hi,
    Can anybody help me out as I am getting a short dump while navigating to particular screen.
    The error was triggered when i was binding an internal table to node in my second view.
    The short dump shows as below.
    ■The following error text was processed in the system EID : Zugriff über 'NULL' Objektreferenz nicht möglich.
    ■The error occurred on the application server ECCIDES_EID_00 and in the work process 1 .
    ■The termination type was: RABAX_STATE
    ■The ABAP call stack was:
    Method: HANDLEFROM_EXPORTS_INIT of program /1BCWDY/4QJM86ZSS4V4M81W8MTQ==CP
    Method: HANDLEFROM_EXPORTS_INIT of program /1BCWDY/4QJM86ZSS4V4M81W8MTQ==CP
    Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/4QJM86ZSS4V4M81W8MTQ==CP
    Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_VIEW========CP
    Method: NAVIGATE of program CL_WDR_CLIENT_APPLICATION=====CP
    Method: DO_NAVIGATION of program CL_WDR_WINDOW_PHASE_MODEL=====CP
    Method: PROCESS_REQUEST of program CL_WDR_WINDOW_PHASE_MODEL=====CP
    Method: PROCESS_REQUEST of program CL_WDR_WINDOW=================CP
    Method: EXECUTE of program CL_WDR_MAIN_TASK==============CP
    Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP
    What can I do?
    ■If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system EID in transaction ST22.
    ■If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server ECCIDES_EID_00 in transaction SM21.
    ■If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 1 in transaction ST11 on the application server ECCIDES_EID_00 . In some situations, you may also need to analyze the trace files of other work processes.
    ■If you do not yet have a user ID, contact your system administrator.
    Error code: ICF-IE-http -c: 700 -u: OBIZDEV -l: E -s: EID -i: ECCIDES_EID_00 -w: 1 -d: 20110723 -t: 161516 -v: RABAX_STATE -e: OBJECTS_OBJREF_NOT_ASSIGNED_NO
    HTTP 500 - Internal Server Error
    Your SAP Internet Communication Framework Team
    Please help.

    Hu Saravanan,
    Please find my code below in HANDLEFROM_EXPORTS_INIT and
    method HANDLEFROM_EXPORTS_INIT .
    data : WRK_DOC_CLAS type /OBIZ/ZXP_DOCCLS-DOC_CLAS.
    data : it_doc type TABLE OF /OBIZ/ZXP_SHPHD.
    DATA : doc_node type REF TO if_wd_context_node.
    BREAK-POINT.
    if doc_desc = 'Quotation'.
    WRK_DOC_CLAS = '0001'.
    elseif doc_desc = 'Sales Order'.
    WRK_DOC_CLAS = '0002'.
    elseif doc_desc = 'Delivery'.
    WRK_DOC_CLAS = '0003'.
    elseif doc_desc = 'Proforma Invoice'.
    WRK_DOC_CLAS = '0004'.
    elseif doc_desc = 'Billing'.
    WRK_DOC_CLAS = '0006'.
    ENDIF.
    select * INTO CORRESPONDING FIELDS OF TABLE
    it_doc FROM /OBIZ/ZXP_SHPHD WHERE doc_clas = WRK_DOC_CLAS.
    call METHOD doc_node->bind_table
    EXPORTING new_items = it_doc.
    endmethod.
    I have imported doc_desc via my inbound plug in the view.
    Regards
    Deric

  • Short dump while running Payroll

    Dear Experts,
    I am getting short dump while running the payroll for around 150 employees, but am not able to see the short dump also as it says that "process terminated".
    please help me in this regard and also let me know if there could be any configuration errors.
    Regards
    Shansar

    Thank you all for the response.
    The issue has been resolved.  i have learnt that log field should not be flagged when you are executing payroll for more than 50 employees.
    Regards
    Shansar

Maybe you are looking for

  • MacSudoku 2.2.2 no longer works

    This is the meat of an e-mail I received from the developer. Hopefully, Apple already knows about this. Hello all: Just a status update on the MacSudoku freezing/crashing issue that you have been experiencing. There's three of you (out of about 2500)

  • Windows can't wake up after closing the lid of a MBP?

    My Windows XP can't wake up after I close the lid of my MBP. When I open the lid, the screen is black and the latch light is out.

  • Maxl / Java

    I would like to know how to use Maxl with Java. I need to create/display filter in my java application and it's not possible with JAPI.thanks

  • Bookmarks Truncating in Acrobat

    I am converting from XML to PDF and lengthy bookmarks always seem to get truncated. How can I get Acrobat to stop truncating these bookmarks? Frank

  • TS1538 Computer not recognizing iPod Touch

    My computer or iTunes is not recognizing my iPod Touch but is recognizing another iPod touch.