Data load eoor , ple solve asap

hi
i am getting this error please let me know solutions
in details tab getting this error also
Extraction (messages): Missing messages
Missing message: Request received
Missing message: Number of sent records
Missing message: Selection completed
Non-updated Idocs found in Business Information Warehouse
Diagnosis
IDocs were found in the ALE inbox for Business Information Warehouse that are not updated.
Processing is overdue.
Error correction:
Attempt to process the IDocs manually. You can process the IDocs manually using the Wizard or by selecting the IDocs with incorrect status and processing them manually.
ple let me know ans
can i goto sm58 and run luw for both r/3 and idoc ?
regards
suneel.

Hi,
In RSMO, select the particular load you want to monitor.
In the menu bar, Environment >>> Transact. RFC >>> Select whichever is required, BW or Source System.
In the next screen you can select the Execute button and the IDOCS will be displayed.
Check Note 561880 - Requests hang because IDocs are not processed.
OR
Transact RFC  - status running Yellow for long time (Transact RFC will be enabled in Status tab in RSMO).
Step 1:  Goto Details, Status get the IDoc number,and go to BD87 in R/3,place the cursor in the RED IDoc entroes in tRFC
queue thats under outbound processing and click on display the IDOC which is on the menu bar.
Step 2: In the next screen click on Display tRFC calls (will take you to SM58 particular TRFC call)
place the cursor on the particular Transaction ID and go to EDIT in the menu bar --> press 'Execute LUW'
(Display tRFC calls (will take you to SM58 particular TRFC call) ---> select the TrasnID ---> EDIT ---> Execute LUW)
Rather than going to SM58 and executing LUW directly it is safer to go through BD87 giving the IDOC name as it will take you
to the particular TRFC request for that Idoc.
OR
Go into the JOB Overview of the Load there you should be able to find the Data Package ID.
(For this in RSMO Screen> Environment> there is a option for Job overview.)
This Data Package TID is  Transaction ID in SM58.
OR
SM58 > Give * / user name or background  (Aleremote) user name and execute.It will show you all the pending TRFC with
Transaction ID.
In the Status Text column you can see two status
Transation Recorded and Transaction Executing
Don't disturb, if the status is second one Transaction Executing. If the status is first one (Transation Recorded) manually
execute the "Execute LUWs"
OR
Directly go to SM58 > Give * / user name or background  (Aleremote) user name and execute. It will show TRFCs to be executed
for that user. Find the particular TRFC (SM37 > Req name > TID from data packet with sysfail).select the TrasnID (SM58) --->
EDIT ---> Execute LUW
Hope this helps.
Thanks,
JituK

Similar Messages

  • Data Load error Please respond ASAP

    Hi ,
    When i am trying to load data for year 07 using rule files its showing an error and aborting the data load
    Error Msg " Data Value [2007] Encountered before all dimensions Selected,[5] Records Completed"
    Any help greatly appreciated.
    Thanks

    Key here is that 5 records were loaded before failing on the 6th, indicating it's not a header issue on the load rule.
    Check the first 5 records and see how the column containing 2007 differs between them and the failing 6th record. Perhaps the 6th record has a null (as indicated eariler) or prehaps 2007 is not the name of the member in the outline.
    I have had both issues give similar error results.
    J

  • Most common BW data load errors in production and how to solve them ..

    Hi All,
    Most common BW data load errors in production and how to solve them ..
    Any doc on it ,if so plz send it across to this id [email protected]
    Thanks in advance.
    Rgrds
    shoba

    hi
    1) RFC connection lost.
    2) Invalid characters while loading.
    3) ALEREMOTE user is locked.
    4) Lower case letters not allowed.
    5) While loading the data i am getting messeage that 'Record
    the field mentioned in the errror message is not mapped to any infoboject in the transfer rule.
    6) object locked.
    7) "Non-updated Idocs found in Source System".
    8) While loading master data, one of the datapackage has a red light error message:
    Master data/text of characteristic 'so and so' already deleted .
    9) extraction job aborted in r3
    10) request couldnt be activated because theres another request in the psa with a smaller sid
    11) repeat of last delta not possible
    12) datasource not replicated
    13) datasource/transfer structure not active ´
    14) Idoc Or Trfc Error
    15. ODS Activation Error

  • Ple correct my variables?its great if solve asap

    hi friends,how are you, past 2 days i am trying this problem , i am not getting . ple solve my problem
    1st query  (sender)
    Customer   quantity
    c1         1000
    c2         2000
    c3         3000
    i created variable charracter with user entry/default( customet right click variable)
    2nd query (receiver)
    Material  Customer Sales
    m1         c1            100
    m2         c2            200
    m3         c3            300
    now i selected customer selected replacement path is processing type and gave sender query name in this variable.
    now i went rsbbs joined 2 queries.
    now my doubts is with variable and without variables i am getting same answer.
    here how my character with replacement path  is effected.
    ple correct and solve.

    Hi Suneel,
    On the receiving Query, you need to restrict the customer by the variable value.
    The value for the variable will be passed by the first Query....When you "jump to target"..
    When you jump from Query1  to Query2....you will get the Materials and the sales amounts
    only for the Customer that you selected in   Query1.
    Good luck, BB

  • Data Loading Error for cube 0TCT_C22

    Dear Colleagues,
    I am working on BI 7.0 / SP09.
    I am loading technical content cube 0TCT_C22 from datasource 0TCT_DS22. Till PSA, there is no problem with data load. But from PSA to data target, data load fails. Went to monitor and it shows teh error "Error calling number range object 0TCTPRCSCHN for dimension D2 (  ). Message no: RSAU023".
    I tried to find the SAP notes fro this, but no success. Also checked the Dump and application logs, but nothing is there.
    Please advice ASAP.
    Regards
    PS

    Hi Pank,
    I just solved the very similar issue. Try what I did to see if it works for you.  For each dimension in each Infocube a number range is created. For some weird reason during the activation of the Infocube the number range for the dimension giving troubles was not created. Look for it in TCODE SNRO and you should find a number range per each dimension in the cube but the one giving you error.
    To solve it, (the easiest way I found) just add any characteristic to the problematic dimension. Activate the Infocube. After that, modify again you Infocube and remove the characteristic you just added to leave the dimension how you need it. Activate the Infocube again. By doing that you will force the regeneration of the dimension and with it the number range. You can chek in TCODE SNRO and the number range should be there. Try loading your data again and it should work.
    One thing I don't understand is why that number range sometimes is not created during activation
    Good luck, I hope you can solve it!!!
    Regards,
    Raimundo Alvarez

  • Master Data loading got failed: error "Update mode R is not supported by th

    Hello Experts,
    I use to load master data for 0Customer_Attr though daily process chain, it was running successfully.
    For last 2 days master data loading for 0Customer_Attr got failed and it gives following error message:
    "Update mode R is not supported by the extraction API"
    Can anyone tell me what is that error for? how to resolve this issue?
    Regards,
    Nirav

    Hi
    Update mode R error will come in the below case
    You are running a delta (for master data) which afils due to some error. to resolve that error, you make the load red and try to repeat the load.
    This time the load will fail with update mode R.
    As repeat delta is not supported.
    So, now, the only thing you can do is to reinit the delta(as told in above posts) and then you can proceed. The earlier problem has nothing to do with update mode R.
    example your fiorst delta failed with replication issue.
    only replicating and repeaing will not solve the update mode R.
    you will have to do both replication of the data source and re-int for the update mode R.
    One more thing I would like to add is.
    If the the delat which failed with error the first time(not update mode R), then
    you have to do init with data transfer
    if it failed without picking any records,
    then do init without data transfer.
    Hope this helps
    Regards
    Shilpa
    Edited by: Shilpa Vinayak on Oct 14, 2008 12:48 PM

  • CALL_FUNCTION_CONFLICT_TYPE Standard Data loading

    Hi,
    I am facing a data loading problem using Business content on CPS_DATE infocube (0PS_DAT_MLS datasource).
    The R/3 extraction processes without any error, but the problem occurs in the update rules while updating the milestone date. Please find hereunder the log from the ST22.
    The real weird thing is that the process works perfectly in development environment and not in integration one (the patch levels are strongly the same: BW 3.5 Patch #16).
    I apologise for the long message below... this is a part of the system log.
    For information the routine_0004 is a standard one.
    Thanks a lot in advanced!
    Cheers.
       CALL_FUNCTION_CONFLICT_TYPE                                                 
    Except.                CX_SY_DYN_CALL_ILLEGAL_TYPE                             
    Symptoms.                                                Type conflict when calling a function module
    Causes                                                        Error in ABAP application program.   
         The current ABAP program "GP420EQ35FHFOCVEBCR6RWPVQBR" had to be terminated because one of the statements could not be executed.                                 
         This is probably due to an error in the ABAP program.                                 
         A function module was called incorrectly.
    Errors analysis
         An exception occurred. This exception is dealt with in more detail below                      
         . The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_TYPE', was neither caught nor passed along using a RAISING clause, in the procedure "ROUTINE_0004"               
         "(FORM)" .                                    
        Since the caller of the procedure could not have expected this exception                      
         to occur, the running program was terminated.                                                  The reason for the exception is:     
        The call to the function module "RS_BCT_TIMCONV_PS_CONV" is incorrect:
    The function module interface allows you to specify only fields of a particular type under "E_FISCPER".
        The field "RESULT" specified here is a different field type.
    How to correct the error.
      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:                                
        "CALL_FUNCTION_CONFLICT_TYPE" CX_SY_DYN_CALL_ILLEGAL_TYPEC                                    
        "GP420EQ35FHFOCVEBCR6RWPVQBR" or "GP420EQ35FHFOCVEBCR6RWPVQBR"                                
        "ROUTINE_0004"                                                                               
        If you cannot solve the problem yourself and you wish to send                                 
        an error message to SAP, include the following documents:                                  
        1. A printout of the problem description (short dump)                                         
           To obtain this, select in the current display "System->List->                              
           Save->Local File (unconverted)".                                              2. A suitable printout of the system log To obtain this, call the system log through transaction SM21.  Limit the time interval to 10 minutes before and 5 minutes  after the short dump. In the display, then select the function                                    
           "System->List->Save->Local File (unconverted)".                                       
        3. If the programs are your own programs or modified SAP programs, supply the source code.               
           To do this, select the Editor function "Further Utilities->  Upload/Download->Download".                                        
        4. Details regarding the conditions under which the error occurred                            
           or which actions and input led to the error.                                               
        The exception must either be prevented, caught within the procedure                           
         "ROUTINE_0004"                                    
        "(FORM)", or declared in the procedure's RAISING clause.                                      
        To prevent the exception, note the following:                                    
    Environment system SAP Release.............. "640"
    Operating system......... "SunOS"   Release.................. "5.9"
    Hardware type............ "sun4u"
    Character length......... 8 Bits     
    Pointer length........... 64 Bits             
    Work process number...... 2        
    Short dump setting....... "full"   
    Database type............ "ORACLE" 
    Database name............ "BWI"  
    Database owner........... "SAPTB1"  
    Character set............ "fr" 
    SAP kernel............... "640"   
    Created on............... "Jan 15 2006 21:42:36"   Created in............... "SunOS 5.8 Generic_108528-16 sun4u" 
    Database version......... "OCI_920 " 
    Patch level.............. "109"    
    Patch text............... " "        
    Supported environment....     
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."             
    SAP database version..... "640"
    Operating system......... "SunOS 5.8, SunOS 5.9, SunOS 5.10"
    SAP Release.............. "640"  
    The termination occurred in the ABAP program "GP420EQ35FHFOCVEBCR6RWPVQBR" in      
         "ROUTINE_0004". 
       The main program was "RSMO1_RSM2 ".  
    The termination occurred in line 702 of the source code of the (Include)           
         program "GP420EQ35FHFOCVEBCR6RWPVQBR"                                             
        of the source code of program "GP420EQ35FHFOCVEBCR6RWPVQBR" (when calling the editor 7020).
       Processing was terminated because the exception "CX_SY_DYN_CALL_ILLEGAL_TYPE" occurred in the procedure "ROUTINE_0004" "(FORM)" but was not handled locally, not declared in  the RAISING clause of the procedure. 
        The procedure is in the program "GP420EQ35FHFOCVEBCR6RWPVQBR ". Its source code starts in line 685 of the (Include) program "GP420EQ35FHFOCVEBCR6RWPVQBR ".
    672      'ROUTINE_0003' g_s_is-recno 
    673      rs_c_false rs_c_false g_s_is-recno  
    674      changing c_abort.   
    675     catch cx_foev_error_in_function. 
    676     perform error_message using 'RSAU' 'E' '510'  
    677             'ROUTINE_0003' g_s_is-recno
    678             rs_c_false rs_c_false g_s_is-recno
    679             changing c_abort.
    680   endtry.              
    681 endform.
    682 ************************************************************************ 
    683 * routine no.: 0004
    684 ************************************************************************ 
    685 form routine_0004 
    686   changing 
    687   result  type g_s_hashed_cube-FISCPER3
    688   returncode     like sy-subrc 
    689     c_t_idocstate  type rsarr_t_idocstate
    690     c_subrc        like sy-subrc 
    691     c_abort        like sy-subrc. "#EC *  
    692   data:
    693     l_t_rsmondata like rsmonview occurs 0 with header line. "#EC * 
    694                    
    695  try.             
    696 * init
    variables 
    697   move-corresponding g_s_is to comm_structure.
    698                     
    699 * fill the internal table "MONITOR", to make monitor entries  
    700                     
    701 * result value of the routine
    >>>>    CALL FUNCTION 'RS_BCT_TIMCONV_PS_CONV'  
    703          EXPORTING      
    704               I_TIMNM_FROM       = '0CALDAY'  
    705               I_TIMNM_TO         = '0FISCPER'  
    706               I_TIMVL            = COMM_STRUCTURE-CALDAY
    707               I_FISCVARNT        = gd_fiscvarnt
    708          IMPORTING 
    709               E_FISCPER          = RESULT.                               
    710 * if the returncode is not equal zero, the result will not be updated 
    711   RETURNCODE = 0. 
    712 * if abort is not equal zero, the update process will be canceled
    713   ABORT = 0.
    714              
    715   catch cx_sy_conversion_error   
    716         cx_sy_arithmetic_error.
    717     perform error_message using 'RSAU' 'E' '507'
    718             'ROUTINE_0004' g_s_is-recno
    719             rs_c_false rs_c_false g_s_is-recno
    720             changing c_abort.
    721   catch cx_foev_error_in_function.
    System zones content
    Name                Val.                                                                               
    SY-SUBRC           0                                         
    SY-INDEX           2                                         
    SY-TABIX           0                                         
    SY-DBCNT           0                                         
    SY-FDPOS           65                                        
    SY-LSIND           0                                         
    SY-PAGNO           0                                         
    SY-LINNO           1                                         
    SY-COLNO           1                                         
    SY-PFKEY           0400                                      
    SY-UCOMM           OK                                        
    SY-TITLE           Moniteur - Atelier d'administration       
    SY-MSGTY           E                                         
    SY-MSGID           RSAU                                      
    SY-MSGNO           583                                       
    SY-MSGV1           BATVC  0000000000                         
    SY-MSGV2           0PROJECT                                  
    SY-MSGV3                                           
    SY-MSGV4                                           
    Selected variables
    Nº       23 Tpe          FORM
    Name    ROUTINE_0004           
    GD_FISCVARNT                                 
        22
        00 RS_C_INFO                                                      I
          4
          9                                
    COMM_STRUCTURE-CALDAY
    20060303
    33333333
    20060303  
    SYST-REPID GP420EQ35FHFOCVEBCR6RWPVQBR   4533345334444454445355555452222222222222 704205135686F365232627061220000000000000
    RESULT
    000
    333
    00

    You have an update routine in which youar callin FM 'RS_BCT_TIMCONV_PS_CONV'. Parameter e_fiscper must be the same that type of the variable you use (you can see the data tyoe in FM definition, transaction se37). You should do somethin like the following.
    DATA: var type <the same that e_fiscper in FM definition>
    CALL FUNCTION 'RS_BCT_TIMCONV_PS_CONV'
    EXPORTING
    I_TIMNM_FROM = '0CALDAY'
    I_TIMNM_TO = '0FISCPER'
    I_TIMVL = COMM_STRUCTURE-CALDAY
    I_FISCVARNT = gd_fiscvarnt
    IMPORTING
    E_FISCPER = var.
    result = var.
    --- ASSIGN POINTS IS USEFUL.

  • Problem with Master Data Load

    Dear Experts,
    If somebody can help me by the following case, please give me some solution. Iu2019m working in a project BI 7.0 were needed to delete master data for an InfoObject material. The way that I took for this was through tcode u201CS14u201D. After that, I have tried to load again the master data, but the process was broken and the load done to half data.
    This it is the error:
    Second attempt to write record 'YY99993' to /BIC/PYYYY00006 failed
    Message no. RSDMD218
    Diagnosis
    During the master data update, the master data tables are read to determine which records of the data package that was passed have to be inserted, updated, or modified. Some records are inserted in the master data table by a concurrently running request between reading the tables at the start of package processing and the actual record insertion at the end of package processing.
    The master data update tries to overwrite the records inserted by the concurrently running process, but the database record modification returns an unexpected error.
    Procedure
    u2022     Check if the values of the master data record with the key specified in this message are updated correctly.
    u2022     Run the RSRV master data test "Time Overlaps of Load Requests" and enter the current request to analyze which requests are running concurrently and may have affected the master data update process.
    u2022     Re-schedule the master data load process to avoid such situations in future.
    u2022     Read SAP note 668466 to get more information about master data update scheduling.
    Other hand, the SID table in the master data product is empty.
    Thanks for you well!
    Luis

    Dear Daya,
    Thank for your help, but I was applied your suggesting. I sent to OSS with the following details:
    We are on BI 7.0 (system ID DXX)
    While loading Master Data for infoobject XXXX00001 (main characteristic in our system u2013 like material) we are facing the following error:
    Yellow warning u201CSecond attempt to write record u20182.347.263u2019 to BIC/ XXXX00001 was successfulu201D
    We are loading the Master data from data source ZD_BW_XXXXXXX (from APO system) through the DTP ZD_BW_XXXXX / XXX130 -> XXXX00001
    The Master Data tables (S, P, X) are not updated properly.
    The following reparing actions have been taken so far:
    1.     Delete all related transactional and master data, by checking all relation (tcode SLG1 à RSDMD, MD_DEL)
    2.     Follow instructions from OSS 632931 (tcode RSRV)
    3.     Run report RSDMD_CHECKPRG_ALL from tcode SE38 (using both check and repair options).
    After deleting all data, the previous tests were ok, but once we load new master data, the same problem appears again, and the report RSDMD_CHECKPRG_ALL gives the following error.
    u201CCharacteristic XXXX00001: error fund during this test.u201D
    The RSRV check for u201CCompare sizes of P and X and/or Q and Y tables for characteristic XXXX00001u201D is shown below:
    Characteristic XXXX00001: Table /BIC/ PXXXX00001, /BIC/ XXXXX00001 are not consistent 351.196 derivation.
    It seems that our problem is described in OSS 1143433 (SP13), even if we already are in SP16.
    Could somebody please help us, and let us know how to solve the problem?
    Thank for all,
    Luis

  • Material Master Data Loading Error

    Hi All,
    I am loading master data for material. i got the following error.
    1. 0material_attr :
        Record 1 :0MATERIAL : Data record 1 ('000000000000010220 '): Version '000000000000010220 ' is not   valid
        Process :   If this message appears during a data load, maintain the attribute in
                         the PSA maintenance screens. If this message appears in the master data
                         maintenance screens, leave the transaction and call it again. This
    2.0material_text : Data record 1 ('000000000000010220E '): Version '000000000000010220 ' is not valid
       Process :  Same as above.
    I have applied RSKC tcode in BI with ALL_CAPITAL, ALL_CAPITAL_PLUS_HEX, and one special character string. but still getting the same error.
    Regards,
    Komik Shah

    Hi All,
    Thanks for the reply. i have solved most of errors. but there are some errors like this
    Diagnosis
        Data record 261 & with the key '000000000000132559 &' is invalid in
        value '10x8x5 &' of the attribute/characteristic 0SIZE_DIM &.
    System Response
        The system has recognized that the value mentioned above is invalid, and
        has processed this general error message. A subsequent message may give
        you more information on the error. This message refers to the same
        value, even though it does not state this explicitly.
    Procedure
        If this message appears during a data load, maintain the attribute in
        the PSA maintenance screens. If this message appears in the master data
        maintenance screens, leave the transaction and call it again. This allows to maintain your masterdata
    which string i should have to add in RSKC to remove this error ? i have already added  the ALL_CAPITAL, ALL_CAPITAL_PLUS_HEX.
    I have assigned points.
    Regards,
    Komik Shah

  • 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

  • Error in Setting lock for Master Data Load

    Hi Team,
    I encounter the following error while uploading the Masterdata
    "Lock NOT set for: Loading master data attributes
    Attributes of characteristic 0BPARTNER are locked by terminated change run 465451241"
    I Performed the following steps
    1) Checked if any active jobs (change run jobs) running in the system. But no jobs running.
    2) RSATTR->infoobject list-> no infoobject found
    3)Tried after sometime ,but load continue to fail
    Could anyone help to solve the problem
    thanks
    Bala

    Hi Bala,
    Check in SM12 if there are any locks exist with the change run number?
    First check if there are any Master data loads running related to it?
    Check in the Attribute change run screen if there are any change run steps are running?
    Once after checking the above if no locks exist and no master data is running then check the below steps
    1. Run RSA1 transaction
    2. Tools -> Apply Hierarchy/Attibutes Change(or direct transaction RSATTR)... menu option
    3. Click at "Monitor and Start terminated Change Runs" button (at the bottom of the screen)
    4. Click "Reset Status" button at Run ID 465451241
    NOTE: this is not recommended, to unlock the locks better to wait till the locks get relased.
    If still the error message persists then we can use a FM in se37 in serious cases which was not recommended by SAP...
    Use RSDDS_AGGR_MOD_CLOSE in se37 and execute--->there give ur failed change run no(465451241) beside I_CNSID and execute...
    It releases all the locks by that change run....and continue with your further work/jobs...
    Regards
    KP

  • Multiple data loads in PSA with write optimized DSO objects

    Dear all,
    Could someone tell me how to deal with this situation?
    We are using write optimized DSO objects in our staging area. These DSO are filled with full loads from a BOB SAP environment.
    The content of these DSO u2013objects are deleted before loading, but we would like to keep the data in the PSA for error tracking and solving. This also provides the opportunity to see what are the differences between two data loads.
    For the normal operation the most recent package in the PSA should be loaded into these DSO-objects (as normal data staging in BW 3.5 and before) .
    As far as we can see, it is not possible to load only the most recent data into the staging layer. This will cause duplicate record errors when there are more data loads in the PSA.
    We all ready tried the functionality in the DTP with u201Call new records, but that only loads the oldest data package and is not processing the new PSA loads.
    Does any of you have a solution for this?
    Thanks in advance.
    Harald

    Hi Ajax,
    I did think about this, but it is more a work around. Call me naive but it should be working as it did in BW3.5!
    The proposed solution will ask a lot of maintenance afterwards. Beside that you also get a problem with changing PSA id's after the have been changed. If you use the posibility to delete the content of a PSA table via the process chain, it will fail when the datasourcese is changed due to a newly generated PSA table ID.
    Regards,
    Harald

  • Data load problem in Apex 3.2

    Hi
    Apex 3.2:
    Using Utilities>Data Load/Unload I am trying to load spreadsheet data. Despite reducing the data down to the simplest possible example I keep getting all rows rejected with
    ORA-00926: missing VALUES keyword     
    I have tried tab delimited and comma delimited. I can't find any other users hitting this problem, and I have been pleasantly surprised when I lasted used this facility many months ago on 3.1.2 when it worked like a dream.
    Any thoughts?
    thanks...

    PROBLEM SOLVED
    The schema and the workspace names were in the form:
    AAAAAAAAA-AA
    I found that data imports worked OK for other workspaces which happened to have simpler naming. I created a new workspace and schema (shorter and without the hyphen) and everything works OK.
    I then tried the same with a new schema and tablespace both called TEST-AB and the load failed with the same error
    I'm guessing that this is probably a known issue? It would be nice if Apex could reject illegal schema/tablespace names!
    I am gratefull for help offered from other replies and hope this observation will help others...

  • Data Load Issue "Request is in obsolete version of DataSource"

    Hello,
    I am getting a very strange data load issue in production, I am able to load the data upto PSA, but when I am running the DTP to load the data into 0EMPLOYEE ( Master data Object) getting bellow msg
    Request REQU_1IGEUD6M8EZH8V65JTENZGQHD not extracted; request is in obsolete version of DataSource
    The request REQU_1IGEUD6M8EZH8V65JTENZGQHD was loaded into the PSA table when the DataSource had a different structure to the current one. Incompatible changes have been made to the DataSource since then and the request cannot be extracted with the DTP anymore.
    I have taken the follwoing action
    1. Replicated the data source
    2. Deleted all request from PSA
    2. Activated the data source using (RSDS_DATASOURCE_ACTIVATE_ALL)
    3. Re transported the datasource , transformation, DTP
    Still getting the same issue
    If you have any idea please reply asap.
    Samit

    Hi
    Generate your datasource in R/3 then replicate and activate the transfer rules.
    Regards,
    Chandu.

  • Data Load to BI (7.0 SP 9) from R3(ECC 6.0 SP-Basis 9)

    Dear All,
    We have new instance of Devlopment BW System with version 7.0 and R/3 upgraded to ECC6.0. We connected the source system. When we extract the data through DTP the data load is sucessful with 0 Records.
    This is case with all the extractors.
    The data base is on Oracle 10.2
    Observations for this:
    0) Source system connection check OK.
    1) When I test in RSA3 for the same extract I could fetch some data there.
    2) I could transfer the global setting
    3) I could not see any of the iDoc generated in BW and received in R/3
    4) No back ground job is generated in R/3 in SM37
    5) I could extract the data from other Source System(SEM) instance based on 3.5 technology.
    As a progress on this issue I could load the load sucessfully by 3.X methodolgy (Using update rules) but not by BI7.0 Methodology(Using Transformation).
    As a standards by the client we have to use 7.0 Methodology so still need to find a solution for the same.
    No clue on how to solve and what is going on wrong. Help me in solve this issue.
    Thanks in Advance,
    PV
    Message was edited by:
            USERPV

    I am not sure if you have followed all the necessary steps to do a data load to the infocube. I also wish I had more information about your system and the error message you are getting. A data load can fail due to a variety of reasons -- depending on the BW version, system settings and the procedure you followed. Please use the data load monitor transaction rsmo, identify the error message and take the necessary action.
    if it may be useful reward point are appreciated

Maybe you are looking for

  • New to Macs with problems after 10.4.9 Update

    Greetings. This is my first post on these forums, so please forgive the newbieness.. I received a brand new 15" MacBook Pro 2.13GHZ less than a week ago. I have since installed another 1GB of memory in it and it has been running absolutely beautifull

  • Video Output on iPod Classic

    I recently upgraded from my older 30GB iPod to the 120GB iPod Classic. The gym I have a membership at has TV's built into all of the machines, and with my older iPod I could easily hook it up for video out. With the iPod classic, it simply keeps tell

  • Using JNI in Oracle Reports

    Hi. I have some difficulties understanding the Oracle Reports mechanism of JNI. The problem I have is the report job is crashed when I use the imported java class. I am using Oracle Reports 11.1.2.1 on Oracle Linux The scenario of generating report i

  • WD Livewire 200 - Return from holiday, and now they wont sync up.

    Hi there. I've been using my WD Livewire 200 kits for years, one in the bedroom where the router is (i know...**bleep** australian housing?) and one in the study - which is supplying internet to my and my wifes office PCs. We've just returned from a

  • Selection Criteria page printing in the inventory reports

    Hi, Selection Criteria page printing in the inventory reports only. How to avoid that? For example: batch number transaction report. Thanks, Olga