Data load InfoPackage gets shot dumps

This is related to the solution Vijay provided in the link What is the functionality of 0FYTLFP [Cumulated to Last Fiscal Year/Period
I encounter the problem again for Data Mart load that I created different initial load InfoPackages with different data selection and ran them separatedly that the initial data packet are messed up and whenever I try to creat a new InfoPackage, always get short dumps. RSA7 on BW system itself doesn't give the fault entry.
I try to use the program RSSM_OLTP_INIT_DELTA_UPDATE you provided, get three parameters:
LOGSYS (required)
DATASOUR (required)
ALWAYS (not required)
I fill in LOGSYS with our BW system source system name that's in the InfoPackage and fill in DATASOUR with the datasource name 80PUR_C01. But it goes nowhere when clicking the execution button!
Then I tried another option you suggested by checking the entries in the following three tables:
ROOSPRMS Control Parameters Per DataSource
ROOSPRMSC Control Parameter Per DataSource Channel
ROOSPRMSF Control Parameters Per DataSource
I find there is no any entry for 1st table with datasource 80PUR_C01, but find two entries in each of the 2nd and 3rd tables. I need to go ahead to delete these two entries for these two tables, right?
Thanks

hey Paolo,
I tried RSSM_OLTP_INIT_DELTA_UPDATE, but there are two required input fields:
LOGSYS (required)
DATASOUR (required)
I fill in LOGSYS with our BW system source system name that's in the InfoPackage and fill in DATASOUR with the datasource name 80PUR_C01. But it goes nowhere when clicking the execution button!  The LOGSYS value I input is correct by filling in with the BW system source system name in InfoPackage?   Also I tried to run this program many times, a little better, but still abnormal.  Maybe I need to try to delete the last two control table entries?
There is problem with giving reward points now with this website, I will give you reward points later.
Thanks

Similar Messages

  • Data mart data load InfoPackage gets shot dumps

    This is related to the solution Vijay provided in the link What is the functionality of 0FYTLFP [Cumulated to Last Fiscal Year/Period
    I encounter the problem again for Data Mart load that I created different initial load InfoPackages with different data selection and ran them separatedly that the initial data packet are messed up and whenever I try to creat a new InfoPackage, always get short dumps. RSA7 on BW system itself doesn't give the fault entry.
    I try to use the program RSSM_OLTP_INIT_DELTA_UPDATE you provided, get three parameters:
    LOGSYS (required)
    DATASOUR (required)
    ALWAYS (not required)
    I fill in LOGSYS with our BW system source system name that's in the InfoPackage and fill in DATASOUR with the datasource name 80PUR_C01. But it goes nowhere when clicking the execution button!
    Then I tried another option you suggested by checking the entries in the following three tables:
    ROOSPRMS Control Parameters Per DataSource
    ROOSPRMSC Control Parameter Per DataSource Channel
    ROOSPRMSF Control Parameters Per DataSource
    I find there is no any entry for 1st table with datasource 80PUR_C01, but find two entries in each of the 2nd and 3rd tables. I need to go ahead to delete these two entries for these two tables, right?
    Thanks

    Kevin,
    sorry, I didn't follow your problem/question, but pay attention when you want to modify these tables content !!!
    Since there is an high risk of inconsistencies...(why don't you ask for some SAP support in OSS for this situation?)
    Hope it helps!
    Bye,
    Roberto

  • Infocube data loads fail with UNCAUGHT_EXCEPTION dump after BI 7.01 upgrade

    Hi folks,
    We're in the middle of upgrading our BW landscape from 3.5 to to 7.01. The Support pack we have in the system is SAPKW70103.
    Since the upgrade any of the data loads going to infocubes are failing with the following
    ABAP dump UNCAUGHT_EXCEPTION     
    CX_RSR_COB_PRO_NOT_FOUND.
    Error analysis                                                                  
        An exception occurred which is explained in detail below.                   
        The exception, which is assigned to class 'CX_RSR_COB_PRO_NOT_FOUND', was not
         caught and                                                                 
        therefore caused a runtime error.                                           
        The reason for the exception is:                                            
        0REQUEST is not a valid characteristic for InfoProvider                     
    Has anyone come accross this issue and if so any resolutions you adopted to fix this. Appreciate any help in this regard.
    Thanks
    Mujeeb

    hi experts,
    i have exactly the same problem.
    But I can`t find a test for infoobjects in rsrv. How can I repair the infoobject 0REQUEST`?
    Thx for all answers!
    kind regards
    Edited by: Marian Bielefeld on Jul 7, 2009 8:04 AM
    Edited by: Marian Bielefeld on Jul 7, 2009 8:04 AM

  • Data load - InfoPackage

    Hi guys,
    Can any one explain the differece in options 'Start Data Load Immediately' and 'Start Later in Background' with 'Immediate Start' in an InfoPackage?
    Thank You,
    Troy

    hi Troy,
      If you select the option 'Start Data Load immediately' then the data load will start immediately and you can monitor the data load by going to the monitor.
      But the use of selecting the option, 'Start Later in the Background' with 'Immediate Start' is that the data load will be assigned a job name for the background process and you can track the data load by the job name in the SM37.I do it because i can track by the job name in SM37 and know the status of the data load.
    Hope it helps.

  • Data load getting failed due to DBIF_RSQL_SQL_ERROR error

    Hi
    while loading the data from one cube to another cube data loading is getting failed by giving the below dump
    Runtime Errors         DBIF_RSQL_SQL_ERROR
    Except.                CX_SY_OPEN_SQL_DB
    An exception occurred that is explained in detail below.                                      |
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
    in
    procedure "WRITE_ICFACT" "(FORM)", nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    The database system recognized that your last operation on the database
    would have led to a deadlock.
    Therefore, your transaction was rolled back
    to avoid this.
    ORACLE always terminates any transaction that would result in deadlock.
    The other transactions involved in this potential deadlock
    |    are not affected by the termination.   
    Please help us in solving above problem

    Hi Kiran,
    Check the below given thread,
    [DBIF_RSQL_SQL_ERROR" with exception CX_SY_OPEN_SQL_DBC;
    Regards,
    Durgesh.

  • Data Load Error

    Everytime i try to run data load i get the following error,
    Object [7905367] is locked by user [user3k]
    Unable to load database, locales [English_UnitedStates.Latin1@Binary] and [English_UnitedStates.US-ASCII@Binary] are not compatible
    Object [7905367] unlocked by user [user3k]
    Unexpected Essbase error 1019057
    The rule file is validating successfully.

    Not sure where the difference in ESSLANG is occuring. Is the ESSLANG variable on the EAS server different to the Essbase server?
    Gee

  • Referencing a substitution variable in data load rule header definition

    Hi All,
    Im trying to add a substitution variable to the header definition of a DLR.
    the sub var is &CurrMonth.
    When I execute the data load I get an "unknown member error" with a list of all members in the header definition, including Oct which is my current month.
    It looks like the DLR is resolving the sub var but for some reason it is refusing to load data.
    We are on 9.2.0.1.
    Are sub vars referenced differently for DLR?
    Thanks for your help.
    Seb

    Hi Seb!
    Hope you're well. You're doing everything right with the subvars so the issue must be elsewhere. Is the list comma separated? Sorry I can' help more :(
    Gee

  • Shot Dump while updating record in ETTIFN using the FM ISU_DB_ETTIFN_UPDATE

    Hi All,
    Am getting shot dump while trying to update an entry in ETTIFN database table using the FM ISU_DB_ETTIFN_UPDATE.
    If this FM fails to update then it tries to  raise error message using the macro 
    MAC_MSG_PUTX CO_MSG_PROGRAMMING_ERROR '016' 'E9'
           'ETTIFN' SPACE SPACE SPACE
           SPACE .
    Runtime Errors         MESSAGE_TYPE_X
    Error analysis
        Short text of error message:
        Error in changing table ETTIFN
        Long text of error message:
         Diagnosis
             An error occurred when one or more table entries were being
             changed. This error was reported by the database system.
         System Response
             The system does not permit changes to one or more table entries.
             It is possible that an SAP short dump has been written from the SAP
             basis system.
         Procedure
             Find out if the SAP short dump provides additional information.
             You can view SAP short dumps using Transaction SM21.
        Technical information about the message:
        Message class....... "E9"
        Number.............. 016
        Variable 1.......... "ETTIFN"
        Variable 2.......... " "
        Variable 3.......... " "
        Variable 4.......... " "
    Please advice inorder to fix the same.
    Regards,
    Deepthi

    Hi Deepthi,
    Updating database using statement update can give dumps because of below issues:
    "At least one line was not able to be changed, either because no appropriate line was found, or because the change would generate a line that leads to double entries in the primary key or a unique secondary index in the database table."
    I would rather suggest you to call the FM in Mode 'M', i.e. Modify so if entry in table is not there to update, it will insert that record and also won't give dump.
    Thanks.
    Ravi

  • Message while data load is in progress

    Hi,
    We are loading the data in the infocube every day twice i.e in the morning and the afternoon.
    Loading methodology is always delete and load. At any given point we have only one request in the cube. Data Load takes arround 20-30 minutes.
    When the user runs the query during the data load, he gets the message 'No Applicable Data Found'. Can anyone please advise, how do we show the proper message like 'Data is updating in the system..Please try after some time...' etc.
    We are using BEx Browser with a template and a query attached to the template.
    Please advise.
    Regards
    Ramesh Ganji

    Hi,
    Tell the time of the data load to the users so that they are aware that the loads are in progress and data will not be available for reportting as of now and prohibit themselves from running the report give a buffer time of around 15-20 mins as there might be some issue some where down the line. Ask them to run the report other than the time data loads are happening
    You could also reschedule the timings of the process chain to finish before the users comes in.
    As far as the functionaly you are referring to i am not sure if we are able to acheive this..
    Regards
    Puneet

  • Error is Master Data load.

    Hi Experts,
    From last 1 month the ( 0MAT_UNIT ) master data load is getting failed. Its a full load. So the the target is not updated from last one month( August)
    Now the problem is , when I am checking a report. The materials which are new or changed are not getting the data properly. It is because of the master data got stucked at PSA level.And I cant rectify at PSA level because, There is 673 errorneous record in 1 package.
    I tried to find the invalid character , but didn't get anything.
    Please suggest.
    Thanks,
    TapuKumar

    Hi Anand,
            This is the long text msg
    Data records in the PSA were marked for data package 1 . Here there were
    673 errors. The system wrote information or warnings for the remaining 
    data records.
                                                                                    System response                                                                               
    The data package was not updated.                                                                               
    Procedure                                                                               
    Correct the incorrect data records of the data package (for example by   
         manually editing them in the PSA maintenance). You can find the error    
         message for each of the records in the PSA by double-clicking on the     
         status of the record.                                                                               
    Note                                                                               
    Note that you are only allowed to edit and manually update the request   
         if it is contained in the request list in the data target. Where         
         necessary, first delete it from the data target.                         
    And it is a master data load( Full ), The data target is a INFO OBJECT.
    Please suggest, I can't rectify each and every reecord. Because the number of record id very high..
    Thanks,
    Tapu Kumar.
    Edited by: NewToBW on Sep 2, 2010 1:42 PM

  • Data loading delay

    Hi Friends.,
               Shall i have an answer for one error,
    The Issue is: Every day i load to one info cube, whatever the cube it is, it takes 2 Hours for every load, but once it has taken 5 Hours, what might be the reason? just confusing with that, can anybody let me clarify !!!!
    Regards.,
    Balaji Reddy K.

    Reddy,
    1. Is the time taken for loading to PSA or to load from PSA to cube ? if it is to oad to PSA then  uaually the problem lies at the extractor
    2. If it is loading to the cube.. then check out if statistics are being maintained for the cube and they would give an accurate picture of where the dataload is taking up most time.
    Do an SQL trace during the data load and if you find a lot of aster Data Lookups .. make sure that master data is loaded and if there are a lot of looups to Table NRIV check if number range buffering is on so that dim IDs get generated faster
    Check if the data load happens fast if you drop any existing indexes...
    Are you loading any agregates after the data load ? check fi th aggregates are necessary or if they have been enabled for delta loads..
    If you have indexes active and there is a huge data loa , depending on the index , the data load can get delayed..
    If the cube is not compressd , some times the data load can get delayed..
    Also when the data load is going on check in SM50 and SM37 to see if the jobs are active - this means that the data load is active from both sides...
    Always update the statistics for the cube before the load and ater the load , this helps in deciphering the time it takes for the data load... after activating the statistics .. check table RSDDSTAT or the standard reports available as part of BW tecnical content..
    Hope it helps..
    Arun
    Assgn points if helpful

  • Getting short dump at the time of loading data from R/3 to ODS

    Hi BW Grurus,
    I am trying to load data from R/3 to ODS, but after running for a few minutes it is getting into the short dump and displays the following run time error. So please give me solution how I can load data without getting short dump. I tried thrice but it is giving the same and failed.
    Run time error : TSV_TNEW_PAGE_ALLOC_FAILED

    Hi,
    Check, is start routine or individual routine in present in update/transfer rule?
    May be read large amount data (select * from) another ODS and put into internal table cause these type of error.
    Regards,
    Saran

  • Shot dump while opening the Infopackage

    Hi Guys,
    In Testing system. i have first started a Init load but it got fail. So the messge it gave me is to replicate the datasource.and i did replicated and activated the trasferstructure.
    After that when i want to open the IP to re init again its going to "Shot Dump" and Its not allowing me te create a new IP and not allowing me to open the other IPs  for this datasource.0FI_AA_12.
    Error analysis                                                                               
    Short text of error message:            
    Data request to the OLTP ***        
    Technical information about the message:
    Message classe...... "RSM"              
    Number.............. 000                
    Variable 1.......... " "                
    Variable 2.......... " "                
    Variable 3.......... " "                
    Variable 4.......... " "                
    Variable 3.......... " "                
    Variable 4.......... " "                
    "MESSAGE_TYPE_X" C             
    "SAPLRSSM" or "LRSSMU36"       
    "RSSM_OLTPSOURCE_SELECTIONS"   
    kindly help me on this.
    regards
    KA
    Message was edited by: A K

    Hi
    At this its getting dump. what might be the reason....can u please help me.                                                    
       data: l_field(70).                                            
       clear l_field.                                                
       concatenate 'DELTA-DELE:' i_logsys '/' i_oltpsource           
                   into l_field.                                     
       call 'C_WRITE_SYSLOG_ENTRY' id 'TYP' field ' '                
             id 'KEY'  field 'TE1'                                   
             id 'DATA' field l_field.                                
       loop at l_t_rssdlinit_oltpdel.                                
         concatenate 'DELTA-DELE-REQU:' l_t_rssdlinit_oltpdel-rnr    
                     into l_field.                                   
         call 'C_WRITE_SYSLOG_ENTRY' id 'TYP' field ' '              
               id 'KEY'  field 'TE1'                                 
               id 'DATA' field l_field.                              
       endloop.                                                      
       message x000.                                                 
       perform del_source_system_init tables l_t_rssdlinit_oltpdel   
                                      using  i_logsys                
                                             i_oltpsource            
                                    'RSSM_OLTPSOURCE_SELECTIONS'     
                                             '410'                   
                                    changing l_subrc.                
    endif.                                                                               
    l_oltp_read_done = 'X'.                                         
    call function 'RSSM_GET_SEL_INT'                                
          exporting                                                  
               i_dest           = i_dest                             
               i_rlogsys        = i_rlogsys                          
               i_oltpsource     = i_oltpsource                       
               i_oltp_read_done = l_oltp_read_done                   
          importing                                                  
               e_changed        = e_changed                          
    Regards
    KA

  • Error while starting data loading on InfoPackage

    Hi everybody,
    I'm new at SAP BW and I'm working in the "Step-By-Step: From Data Model to the BI Application in the web" document from SAP.
    I'm having a problem at the (Chapter 9 in the item c - Starting Data Load Immediately).
    If anyone can help me:
    Thanks,
    Thiago
    Below are the copy of the error from my SAP GUI.
    <><><><><><><><><><<><><><><><><><><><><><><><><><><><><><><><>
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          19.01.2009 14:41:22
    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).
    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
    Short text of error message:
    Batch - Manager for BW Processes ***********
    Long text of error message:
    Technical information about the message:
    Message class....... "RSBATCH"
    Number.............. 000
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    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:
    "MESSAGE_TYPE_X" " "
    "SAPLRSBATCH" or "LRSBATCHU01"
    "RSBATCH_START_PROCESS"
    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 701
    Application server... "sun"
    Network address...... "174.16.5.194"
    Operating system..... "Windows NT"
    Release.............. "5.1"
    Hardware type........ "2x Intel 801586"
    Character length.... 8 Bits
    Pointer length....... 32 Bits
    Work process number.. 2
    Shortdump setting.... "full"
    Database server... "localhost"
    Database type..... "ADABAS D"
    Database name..... "NSP"
    Database user ID.. "SAPNSP"
    Terminal.......... "sun"
    Char.set.... "English_United State"
    SAP kernel....... 701
    created (date)... "Jul 16 2008 23:09:09"
    create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
    Database version. "SQLDBC 7.6.4.014 CL 188347 "
    Patch level. 7
    Patch text.. " "
    Database............. "MaxDB 7.6, MaxDB 7.7"
    SAP database version. 701
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
    NT 6.0"
    Memory consumption
    Roll.... 8112
    EM...... 11498256
    Heap.... 0
    Page.... 65536
    MM Used. 6229800
    MM Free. 1085264
    User and Transaction
    Client.............. 001
    User................ "THIAGO"
    Language key........ "E"
    Transaction......... "RSA1 "
    Transactions ID..... "CD47E6DDD55EF199B4E6001B782D539C"
    Program............. "SAPLRSBATCH"
    Screen.............. "SAPLRSS1 2500"
    Screen line......... 7
    Information on where terminated
    Termination occurred in the ABAP program "SAPLRSBATCH" - in
    "RSBATCH_START_PROCESS".
    The main program was "RSAWBN_START ".
    In the source code you have the termination point in line 340
    of the (Include) program "LRSBATCHU01".
    Source Code Extract
    Line
    SourceCde
    310
    endif.
    311
    l_lnr_callstack = l_lnr_callstack - 1.
    312
    endloop.      " at l_t_callstack
    313
    endif.
    314
    315
    *---- Eintrag für RSBATCHHEADER -
    316
    l_s_rsbatchheader-batch_id    = i_batch_id.
    317
    call function 'GET_JOB_RUNTIME_INFO'
    318
    importing
    319
    jobcount        = l_s_rsbatchheader-jobcount
    320
    jobname         = l_s_rsbatchheader-jobname
    321
    exceptions
    322
    no_runtime_info = 1
    323
    others          = 2.
    324
    call function 'TH_SERVER_LIST'
    325
    tables
    326
    list           = l_t_server
    327
    exceptions
    328
    no_server_list = 1
    329
    others         = 2.
    330
    data: l_myname type msname2.
    331
    call 'C_SAPGPARAM' id 'NAME'  field 'rdisp/myname'
    332
    id 'VALUE' field l_myname.
    333
    read table l_t_server with key
    334
    name = l_myname.
    335
    if sy-subrc = 0.
    336
    l_s_rsbatchheader-host   = l_t_server-host.
    337
    l_s_rsbatchheader-server = l_myname.
    338
    refresh l_t_server.
    339
    else.
    >>>>>
    message x000.
    341
    endif.
    342
    data: l_wp_index type i.
    343
    call function 'TH_GET_OWN_WP_NO'
    344
    importing
    345
    subrc    = l_subrc
    346
    wp_index = l_wp_index
    347
    wp_pid   = l_s_rsbatchheader-wp_pid.
    348
    if l_subrc <> 0.
    349
    message x000.
    350
    endif.
    351
    l_s_rsbatchheader-wp_no           = l_wp_index.
    352
    l_s_rsbatchheader-ts_start        = l_tstamps.
    353
    l_s_rsbatchheader-uname           = sy-uname.
    354
    l_s_rsbatchheader-module_name     = l_module_name.
    355
    l_s_rsbatchheader-module_type     = l_module_type.
    356
    l_s_rsbatchheader-pc_variant      = i_pc_variant.
    357
    l_s_rsbatchheader-pc_instance     = i_pc_instance.
    358
    l_s_rsbatchheader-pc_logid        = i_pc_logid.
    359
    l_s_rsbatchheader-pc_callback     = i_pc_callback_at_end.

    Hi,
    i am also getting related this issue kindly see this below short dump description.
    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).
    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
        Short text of error message:
        Variant RSPROCESS0000000000705 does not exist
        Long text of error message:
         Diagnosis
             You selected variant 00000000705 for program RSPROCESS.
             This variant does not exist.
         System Response
         Procedure
             Correct the entry.
        Technical information about the message:
        Message class....... "DB"
    Number.............. 612
        Variable 1.......... "&0000000000705"
        Variable 2.......... "RSPROCESS"
        Variable 3.......... " "
        Variable 4.......... " "
    How to correct the error
        Probably the only way to eliminate the error is to correct the program.
        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:
    "MESSAGE_TYPE_X" " "
    "SAPLRSPC_BACKEND" or "LRSPC_BACKENDU05"
    "RSPC_PROCESS_FINISH"
        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 701
        Application server... "CMCBIPRD"
        Network address...... "192.168.50.12"
        Operating system..... "Windows NT"
    Release.............. "6.1"
        Hardware type........ "16x AMD64 Level"
        Character length.... 16 Bits
        Pointer length....... 64 Bits
        Work process number.. 0
        Shortdump setting.... "full"
        Database server... "CMCBIPRD"
        Database type..... "MSSQL"
        Database name..... "BIP"
        Database user ID.. "bip"
        Terminal.......... "CMCBIPRD"
      Char.set.... "C"
      SAP kernel....... 701
      created (date)... "Sep 9 2012 23:43:54"
      create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00"
      Database version. "SQL_Server_8.00 "
      Patch level. 196
      Patch text.. " "
    Database............. "MSSQL 9.00.2047 or higher"
      SAP database version. 701
      Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
       NT 6.0, Windows NT 6.1, Windows NT 6.2"
      Memory consumption
      Roll.... 16192
      EM...... 4189840
      Heap.... 0
      Page.... 16384
      MM Used. 2143680
      MM Free. 2043536
    User and Transaction
    Client.............. 001
    User................ "BWREMOTE"
        Language Key........ "E"
    Transaction......... " "
        Transactions ID..... "9C109BE2C9FBF18BBD4BE61F13CE9693"
    Program............. "SAPLRSPC_BACKEND"
    Screen.............. "SAPMSSY1 3004"
        Screen Line......... 2
        Information on caller of Remote Function Call (RFC):
    System.............. "BIP"
        Database Release.... 701
        Kernel Release...... 701
        Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
        Call Type........... "asynchron without reply and transactional (emode 0, imode
         0)"
        Inbound TID.........." "
        Inbound Queue Name..." "
        Outbound TID........." "
        Outbound Queue Name.." "
    Information on where terminated
        Termination occurred in the ABAP program "SAPLRSPC_BACKEND" - in
    "RSPC_PROCESS_FINISH".
        The main program was "SAPMSSY1 ".
        In the source code you have the termination point in line 75
        of the (Include) program "LRSPC_BACKENDU05".
    Source Code Extract
    Line  SourceCde
       45         l_t_info        TYPE rs_t_rscedst,
       46         l_s_info        TYPE rscedst,
       47         l_s_mon         TYPE rsmonpc,
       48         l_synchronous   TYPE rs_bool,
       49         l_sync_debug    TYPE rs_bool,
       50         l_eventp        TYPE btcevtparm,
       51         l_eventno       TYPE rspc_eventno,
       52         l_t_recipients  TYPE rsra_t_recipient,
    52 l_t_recipients  TYPE rsra_t_recipient,
    53         l_s_recipients  TYPE rsra_s_recipient,
    54         l_sms           TYPE rs_bool,
    55         l_t_text        TYPE rspc_t_text.
    56
    57   IF i_dump_at_error = rs_c_true.
    58 * ==== Dump at error? => Recursive Call catching errors ====
    59     CALL FUNCTION 'RSPC_PROCESS_FINISH'
    60       EXPORTING
    61         i_logid       = i_logid
    62         i_chain       = i_chain
    63         i_type        = i_type
    64         i_variant     = i_variant
    65         i_instance    = i_instance
    66         i_state       = i_state
    67         i_eventno     = i_eventno
    68         i_hold        = i_hold
    69         i_job_count   = i_job_count
    70         i_batchdate   = i_batchdate
    71         i_batchtime   = i_batchtime
    72       EXCEPTIONS
    73         error_message = 1.
    74     IF sy-subrc <> 0.
    >>> MESSAGE ID sy-msgid TYPE 'X' NUMBER sy-msgno
    76               WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    77     ELSE.
    78       EXIT.
    79     ENDIF.
    80   ENDIF.
    81 * ==== Cleanup ====
    82   COMMIT WORK.
    83 * ==== Get Chain ====
    84   IF i_chain IS INITIAL.
    85     SELECT SINGLE chain_id FROM rspclogchain INTO l_chain
    86            WHERE log_id = i_logid.
    87   ELSE.
    88     l_chain = i_chain.
    89   ENDIF.
    90 * ==== Lock ====
    91 * ---- Lock process ----
    92   DO.
    93     CALL FUNCTION 'ENQUEUE_ERSPCPROCESS'
    94       EXPORTING
    If we do this
    Use table RSSDLINIT and in OLTPSOURCRE: enter the name of the data  source
    And in the logsys enter the name of the source system and delete the entry for that info package. what will happen is process chain will run suceesfully and short dump will not come or what kindly give the detail explanation about this RSSDLINIT.
    Regards,
    poluru

  • Memory dump in contract data load

    Hi,
    e are doing CRM service contract data load from flat file to CRM using
    BAPI_BUSPROCESSND_CREATEMULTI and it is giving ABAP memory dump.Please
    see attached file for more details about dump.
    Following steps we are doing.
    1.Call following functional modules in loop to create service contract.
    2. call
      call function 'BAPI_BUSPROCESSND_CREATEMULTI'
        tables
          header          = lt_header
          item            = lt_item
          sales           = lt_sales
          partner         = lt_partner
          appointment     = lt_appointment
          status          = lt_status
          input_fields    = lt_input_fields
          created_process = lt_created_process
          return          = lt_return
          scheduleline    = lt_scheduleline
          pricing         = lt_pricing
          billing         = lt_billing
          objects         = lt_objects
          condition_create = lt_condition_create
         billplan        = lt_billplan
         billplan_date   = lt_billplan_date
           cancel          = lt_cancel
          document_flow   = lt_docflow.
    2.call
          call function 'CRM_ORDER_SAVE'
        exporting
          it_objects_to_save = lt_objects_to_save
          iv_no_bdoc_send    = 'X'
        exceptions
          document_not_saved = 1
          others             = 2.
    3. call
              call function 'BAPI_TRANSACTION_COMMIT'
        exporting
          wait = 'X'.
    4.call
               call function 'CRM_ORDER_INITIALIZE'
        exporting
          it_guids_to_init           = lt_guid_16
          iv_initialize_whole_buffer = 'X'
          iv_init_frame_log          = 'X'
        exceptions
          error_occurred             = 1
          others                     = 2.
    5.close the loop.
    Though we are every time calling 'CRM_ORDER_INITIALIZE' it's still
    giving following dump. Looks like 'CRM_ORDER_INITIALIZE' is not
    initializing the memory.
    Dump details
    STORAGE_PARAMETERS_WRONG_SET
    &INCLUDE INCL_INSTALLATION_ERROR
    What happened?
    The current program had to be terminated because of an
    error when installing the R/3 System.
    The program had already requested 256701152 bytes from the operating
    system with 'malloc' when the operating system reported after a
    further memory request that there was no more memory space
    available.
    Could you please suggest how to clear the memory?
    -Kavitha

    Hi Kavitha,
    What are the approx. number of records you are trying to Populate? You can follow the below given sequence for loading the data.
    1. call function 'BAPI_BUSPROCESSND_CREATEMULTI'
    2. CALL FUNCTION 'BAPI_BUSPROCESSND_SAVE'
    Example:  
    call function 'BAPI_BUSPROCESSND_SAVE'
          EXPORTING
            update_task_local = false
            save_frame_log    = true
         IMPORTING
          log_handle        = lv_loghandle
          TABLES
            objects_to_save   = lt_objects_to_save
            saved_objects     = lt_saved_objects
            return            = lt_return.
    3.   CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    i think this would work without problem. Let me know whether you still get ABAP Dump.
    Regards
    Abinash

Maybe you are looking for

  • Supplier Replication from MM to SUS

    Hi Experts, We are working on SRM 701 & ECC 600 EHP5 & PI 7.01. Requirement is to replicate suppliers from the ERP system to the SUS system through PI. Which integration scenario should I use in PI to do the required configuration? I tried with the i

  • Message From Win Event Viewer - do I have a problem?

    I have just got myself a new PC and it keeps crashing.  Mooching about in Windows Event Viewer (not that I know what I am doing) I noticed this error: Date:          15/07/2009 17:47:50 Event ID:      78 Task Category: None Level:         Error Keywo

  • Trouble shooting and Error handling / Alert Messages

    Hi, SAP - Xi - File or File - XI - SAP 1. I am presumming that when SAP is down then alert management can send message to receiver . 2. But when XI is down can I send alert to receiver that XI is down, how can I acheive this. Please provide me the st

  • Bridge showing XMP DS.Store files

    For some reason Bridge CS4 is showing XMP and DS.Store files. If I rate an image the XMP file immediately appears below the image in the Content pane. This really gets in the way of proper work flow. If there is 500 images in a folder and each image

  • Javascript open() function returns undefined

    The javascript function open() specs like "fullscreen", "width", "height", seem not to work under Safari while they do under Firefox, Opera and even Explorer. So, I open a popup with : Win=open("<url>","","") and then , I use Win.resizeTo(<width>,<he