Transaction RSMO - Data Load A Monitor Start

When you have a request in the Monitor - Administrator Workbench that shows
"Request still running", is there a way to stop the request?
I know you can change the" Set Status" to "Status Not Ok" but that doesn't stop the requset from running; but how do you stop a request that is running?

Hi Newbie 
U need to take care abt two considerations here
1) If u r loading the data from Source sytem End . So me cases U need to kill the
Job @ u r source system SM 37 .and Kill the relevant process In SM50 By
selecting the process--> Cancel With core and then subsequently do the same in
BW end.
2) If its updating from BW it self then u need just kill the job In SM37 and process
@ SM50.
And then Restart the process Manually..
Hope itz Helps..!
Regards
R M K
**Winners don't do different things,They do things differently...!**
> When you have a request in the Monitor -
> Administrator Workbench that shows
> "Request still running", is there a way to stop the
> request?
>
> I know you can change the" Set Status" to "Status Not
> Ok" but that doesn't stop the requset from running;
> but how do you stop a request that is running?

Similar Messages

  • Data Load Statistics - Monitoring

    Hello All
    I have a quick questions on how to check the no of records LOADED into INFPKG (PSA) --> DTP (DSO) --> DTP (CUBE).
    1) Meaning, I can individually but is there any automated program / transaction / table that can tell me no of records LOADED into PSA --> DSO --> CUBE for any paricular process chain?
    2) If I mistakenly deleted a request from Cube/DSO/PSA, how would I retrieve it ?
    Thanks in advance

    Hi,
    1) Meaning, I can individually but is there any automated program / transaction / table that can tell me no of records LOADED into PSA --> DSO --> CUBE for any paricular process chain?
    --> Table: RSMONICTAB -- Monitor, Data Targets(Infocube/ODS) Table, request related info
    2) If I mistakenly deleted a request from Cube/DSO/PSA, how would I retrieve it ?
    --> If data loading : PSA > DSO> Cube then..
    If data lost in cube, can be loaded from DSO,
    If data lost in DSO, and available at PSA can be loaded/reconstruct from PSA
    If data not available in PSA cant possible. Need to reload from source.
    Hope it Helps
    Srini

  • How to data load without monitor entry?

    Hello,
    the atttibuts of a character are filled daily. There is no Request.
    Does anyone know, how I can find out from where the Data comes without monitor entrys?
    Thank you!
    SW

    Hi
    You can check whether any customised ABAP coding is used to fetch data from some data source and fill the related master data
    RSRD_ATTR_DEP - dependencies of attributes.....
    Like this, there can be some link tables which could be used in custom ABAP code to automatically fill the attribute values
    Bye
    N Ganesh
    assign points if useful**

  • Issue in Data Loading in BW

    Dear BW GURUS,
    We are facing data loading in BW. When we start process chain. it is showing Job id.  But the data loading is not starting.  We could not trace the log files for the same.
    Please throw some light on this.  Any pointers would be appreciable.
    Thanks in advance.
    Regards,
    Mohankumar.G

    Hi Mohan,
    By buffering the number ranges, the system reduces the number of database reads to the NRIV table, thus speeding up large data loads.
    The SAP BW system uses number ranges when loading master data or transactional data into BW. The system uses a unique master data number ID for each loaded record. Each new record reads the number range table NRIV to determine the next number in sequence. This ensures that there are no duplicate numbers. Not using unique number range values could compromise the datau2019s integrity.
    Number ranges can cause significant overhead when loading large volumes of data as the system repeatedly accesses the number range table NRIV to establish a unique number range. If a large volume of data is waiting for these values, then the data loading process becomes slow.
    One way to alleviate this bottleneck is for the system to take a packet of number range values from the table and place them into memory. This way, the system can read many of the new records from memory rather than repeatedly accessing and reading table NRIV. This speeds the data load.
    Regards,
    Vamsi Krishna Chandolu

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

  • What are the possible errors that can happen in data loads(rsmo monitor)?

    hi all,
    what could be the error that could result in red color in the RSMO  monitor of data load transaction?
    1. request everything ok
    (what are the possible error type which make here red)
    2. extraction everything ok
    (what are the possible error type which make here red)
    3. transfer (idocs and trfc) error occured?
    (what are the possible error type which make here red)
    4. processing
        - data package
    5. process chain
    (what are the possible error type which make here red)
    6 other messages.
    (what are the possible error type which make here red)
    thanks
    pooja

    Hi,
    I can tell you the most common reasons of these failures.
    1. request everything ok
    Here it will be telling you if the request was properly send to source system and got triggered there.
    2. extraction everything ok
    In this step the actual extraction of data happens, issue slike sysfail or CPIC error may cause this to fail.
    3. transfer (idocs and trfc) error occured?
    When extraction is complete and data is being send to BW. But if dur to some reason it fails, error may come here.
    4. processing
    Processing in BW fails for each data packet is displayed here.
    This can also happen when you have sysfail in source.
    5. process chain
    This can show the logs of the chain here and also status of subsequent process.
    6 other messages.
    Any other error message.
    Refer
    What is the information we can get the through details tab in RSMO
    working with RSMO errors
    http://help.sap.com/saphelp_nw70/helpdata/en/12/43074208ae2a38e10000000a1550b0/frameset.htm
    Also
    Data Load Errors
    /people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
    Data Load issues
    Errors in loading
    data loading errors
    load Errors
    Process Chain Errors
    /people/mona.kapur/blog/2008/01/14/process-chain-errors
    Common Process chain errors
    process chain issues or errors
    Hope this helps.
    Thanks,
    JituK

  • Automated data load from APO to SEM transactional cube

    Hi ,
    We have BW-SEM system integrated with APO system.
    I could see automated data loads from APO to SEM transactional cube ..
    Infopackage name as "Request loaded using the APO interface without monitor log" ..
    I don't see any infopackage by this name in both the systems ( APO & SEM )..
    I am not sure how it configured ..
    Appreciate any inputs on how its happens .....
    Thanks in advance

    Hi,
    As I mentioned the starting point will be the tcode BPS0. There will be 2 planning areas created (if I am correct) one for SEM cube and the other for APO cube. The better way to find it will be goto tcode se16 and enter UPC_BW_AREA and key in the cube names in the cube field. this will give you the planning area names now look for a multiplanning area which has the 2 areas included in them (this is available in table UPC_AREAM).
    then goto BPS0 and you will have to find which function is being used to post the data.
    thanks

  • BW Data Load Monitoring

    Hi,
    Could anybody say me how to monitoring a load from R3(4.6C) to BW(3.5)?
    I need to know the size in MB transfered in a load. In transaction RSMON i can see the records transfered but i don´t know how to calculate the mb. I need to know the size of the records to calculate this. Or there is a transaction where can i find the information?
    Thanks.

    Hi,
    The perfect way to calculate the size of your daily data load in MB is to.
    Goto Transaction DB02
    Press the Space Statistics which you can find at the end of the screen..
    A small pop window will open - in that select table statistics
    Now a new screen will open, give the name of your table(PSA, DSO, Cube ) and make sure you give the technical name that starts with /BIC/ and you can see
    the size and other details for a day, week and month.
    Regards,
    Kadriks

  • Data Load Monitoring.

    Dear Experts,
    I would like to know on what circumstances we should use following Data load monitoring tools:
    1.     RSMO
    2.     SSA/BWT
    3.     ST13
    4.     RZ20
    It would be more helpfull if you can describe pros and cons of each tool.
    Regards
    Vivek Tripathi

    Hi Vivek,
    RSMO is used to monitor the dataloads coming into the BI system. Here you can find the details for each and Every load happened.
    SSA/BWT is a Program which provide you the details about Process Chain Analysis, Detailed Request Analysis ,Aggregate Toolset etc.
    Refer this Wiki for more details.
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/bi/bw%252btools
    ST13- This provides a set of tools which talk mostly about Performance of the BI system.
    Refer this Blog
    Overview important BI performance transactions
    Regarding RZ20 - It is called as CCMS Monitor Sets
    Here in CCMS you have different monitoring tools for different components.
    If  BI is concerned you can monitor the details about BI Accelerator Monitor,BI Key Performance Indicators ,BI Monitor etc.
    Regards
    Karthik

  • Error 8 when starting the extracting the program-data load error:status 51

    Dear all,
    <b>I am facing a data exracton problem while extracting data from SAP source system (Development Client 220). </b>The scenario and related setting are as the flowings:
    A. Setting:
    We have created 2 source system one for the development and another for the quality in BW development client
    1. BW server: SAP NetWeaver 2004s BI 7
    PI_BASIS: 2005_1_700 Level: 12
    SAP_BW: 700 Level:13
    Source system (Development Client 220)
    2. SAP ERP: SAP ERP Central Component 6.0
    PI_BASIS: 2005_1_700 Level: 12
    OS: SunOS
    Source system (Quality Client 300)
    2. SAP ERP: SAP ERP Central Component 6.0
    PI_BASIS: 2005_1_700 Level: 12
    OS: HP-UX
    B. The scenario:
    I was abele to load the Info provider from the Source system (Development Client 220), late we create another Source system (Quality Client 300) and abele to load the Info provider from that,
    After creating the another Source system (Quality Client 300), initially I abele to load the info provider from both the Source system – , but now I am unable to load the Info provider from the (Development Client 220),
    Source system Creation:
    For both 220 and 300, back ground user in source system is same with system type with same authorization (sap_all, sap_new, S_BI-WX_RFC) And user for source system to bw connection is dialog type (S_BI-WX_RFC, S_BI-WHM_RFC, SAP_ALL, SAP_NEW)
    1: Now while at the Info Package : Start data load immediately and then get the
    e-mail sent by user RFCUSER, and the content:
    Error message from the source system
    Diagnosis
    An error occurred in the source system.
    System Response
    Caller 09 contains an error message.
    Further analysis:
    The error occurred in Service API .
    2:Error in the detail tab of the call monitor as under,
    <b>bi data upload error:status 51 - error: Error 8 when starting the extracting the program </b>
    Extraction (messages): Errors occurred
      Error occurred in the data selection
    Transfer (IDocs and TRFC): Errors occurred
    Request IDoc : Application document not posted (red)
      bw side: status 03: "IDoc: 0000000000007088 Status: Data passed to port OK,
                                    IDoc sent to SAP system or external program"
      r<b>/3 side: status 51:  IDoc: 0000000000012140 Status: Application document not posted
                                   Error 8 when starting the extraction program</b>
    Info IDoc 1 : Application document posted (green)
       r/3 side: "IDoc: 0000000000012141 Status: Data passed to port OK
                     IDoc sent to SAP system or external program"
       bw side: "IDoc: 0000000000007089 Status: Application document posted,
                     IDoc was successfully transferred to the monitor updating"
    Have attached screen shots showing error at BW side.
    •     check connection is ok, tried to restore the setting for bw-r3 connection – though same problem
    •     Have checked partner profile.
    <b>what's wrong with the process? </b>
    Best regards,
    dushyant.

    Hi,
       Refer note 140147.
    Regards,
    Meiy

  • 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

  • Transaction Data Load from BW info provider

    Hi gurus,
    I am doing a transaction dat aload from the BW data feed to BPC cube. When I did the validation of the transformation file the task was sucessfully completed with some skipped records as expected based on the conversion files.
    ValidateRecords = YES
    [List of conversion file]
    Conversion file: DataManager\ConversionFiles\EXAMPLES\TIMECONV.XLS!CONVERSION
    Conversion file: DataManager\ConversionFiles\EXAMPLES\VERSIONCONV.XLS!CONVERSION
    Conversion file: DataManager\ConversionFiles\EXAMPLES\ACCOUNTCONV.XLS!CONVERSION
    Conversion file: DataManager\ConversionFiles\EXAMPLES\ENTITY.XLS!CONVERSION
    Record count: 25
    Accept count: 13
    Reject count: 0
    Skip count: 12
    This task has successfully completed
    but when did run package, load fails.
    /CPMB/MODIFY completed in 0 seconds
    /CPMB/INFOPROVIDER_CONVERT completed in 0 seconds
    /CPMB/CLEAR completed in 0 seconds
    [Selection]
    InforProvide=ZPCAOB01
    TRANSFORMATION= DATAMANAGER\TRANSFORMATIONFILES\EXAMPLES\ABF_TRANS_LOAD.xls
    CLEARDATA= Yes
    RUNLOGIC= No
    CHECKLCK= No
    [Messages]
    Task name CONVERT:
    No 1 Round:
    Error occurs when loading transaction data from other cube
    Application: TEST Package status: ERROR
    This is a fresh system and we are doing the data load for the first time.  we are using BPC NW 7.5 with SP4
    Is there something which we are missing which is supposed to be performed before starting the load for the first time.
    my transformation file is as below
    *MAPPING
    Account=0ACCOUNT
    Currency=0CURRENCY
    DataSrc=*NEWCOL(INPUT)
    Entity=ZPCCCPLN
    ICP=*NEWCOL(ICP_NONE)
    Scenario=0VERSION
    Time=0FISCPER
    SIGNEDDATA=0AMOUNT
    *CONVERSION
    TIME=EXAMPLES\TIMECONV.XLS
    SCENARIO=EXAMPLES\VERSIONCONV.XLS
    ACCOUNT=EXAMPLES\ACCOUNTCONV.XLS
    ENTITY=EXAMPLES\entity.xls
    Thanks a lot in advance.
    Regards
    Sharavan

    Hi Gersh,
    Thanks for the quick response.
    I checked in SLG1 and i have the below error in the log.
    Class: CL_UJD_TRANSFORM_PROXY:CONSTRUCTOR Log:DATATYPE 3
    Class: CL_UJD_TRANSFORM_PROXY:CONSTRUCTOR Log:CURRENT_ROUND 1
    Error occurs when loading transaction data from other cube
    Message no. UJD_EXCEPTION137
    we are on SP4, BPC NW 7.5. Please advice
    Regards
    Sharavan.

  • Shipping dates(Loading start,Loading End,shipment start...)

    Hi,
    In the shipment transaction(VT01n) what (Configuration)settings are required to populate the fields
    Loading start,Loading End,shipment start, and shipment end dates  in the Planning side.
    REgards
    Rahul

    Yes. Its called Inferred member concept or Early Arriving facts
    You can handle them as follows
    1. In the ETL for fact identify cases where you've dimension key value coming but reference missing from the corresponding dimension table
    2. Insert those records to dimension table with just the available business key value and retrieve the generated surrogate key. For all the other attributes put some default value. Have a bit field called IsInferred in the table with default value 0. Set
    it to 1 for the above records. This would avoid missing reference error for FK
    3. In the ETL for the dimension include one step to look for cases where IsInferred = 1 and do an update of all attribute values except business key. Also make sure IsInferred is reset to 0. This will make sure the missing information gets automatically
    added during the next ETL run for the dimensions
    4. If you make use of standard SCD task available in SSIS it can take care of this scenario by itself
    See
    http://www.mssqltips.com/sqlservertip/1446/handle-early-arriving-facts-in-sql-server-integration-services-ssis/
    http://chandunayakwadi.blogspot.in/2013/01/handling-inferred-members-in-ssis.html
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • Transaction data load

    Hi,
    I am loading transaction data(i.e.initializing delta)on Q.A and getting the following error:
    Data Package 8 : arrived in BW ; Processing : Selected number does not agree with transferred n
    selected number of records shown in the monitor:1,40,000
    and transferred records are 1,11,000 ...remaining data is not able to transfer.
    where as data loaded successfully on development system.
    but after transporting it to Q.A, and while loading data getting the above error.
    please give the reason and solution of this error.
    Thanks in advance.
    Regards,

    Hi Vishvesh,
    But the option with which i loaded the data is "data targets only" and initialize delta transfer only for full load so plz can u tell me where i can see the manual update option...?
    i right clicked on the datapackage in monitor under details but i can see only these 2 options:
    1.help for node
    2.display processing
    so where to get manual update option?

  • Essbase Error(1003050): Data Load Transaction Aborted With Error (1220000)

    Hi
    We are using 10.1.3.6, and got the following error for just one of the thousands of transactions last night.
    cannot end dataload. Essbase Error(1003050): Data Load Transaction Aborted With Error (1220000)
    The data seems to have loaded, regardless of the error. Should we be concerned, and does this suggest something is not right somewhere?
    Your assistance is appreciated.
    Cheers

    Hi John
    Not using a load rule.
    There were two other records which rejected based on absentee members. The error message was different for them, and easily fixed.
    But this error doesn't tell us much. I will monitor the next run to see if the problem persists.
    Thanks

Maybe you are looking for

  • File payload is empty

    I'm using an FTP adapter to fetch a file. This is to be passed on to another service for processing the contents. Both the FTP Adapter and web service payloads are defined using the same schema 1) I put a mediator in between the two components and ha

  • How to adjust R/W rules to display images inline?

    Hi all, out of the box, when I insert an image in a paragraph (DITA 1.2) then FrameMaker 12 uses the "below line" display setting. I need to display it inline, at the insertion point. When I adjust the settings of the anchored frame then the inline s

  • How to Read a File into a Byte Array??

    I want to make an array of data objects that works as a byffer to write from a file to another file do you have any sygestions?

  • IDOCS not reaching XI

    Dear all, I found a peculiar issue. A set idocs are being posted from SAP to XI. Always the last IDOC in that set doesn't reach XI. But the status of that IDOC in we02 is 03. I've even checked for SM58 in SAP, it also clear. At XI, everything is fine

  • OVD - Suppress OU's in Adapter

    Hello, I have a requirement to suppress a series of OU's in an LDAP Adapter. I am federating two separate Active Directories in which one is a subset of the other. I want my final federated OVD LDAP to look like this: dc=federated,dc=com + Root + + O