ODS to InfoCube delta data load problem........?

Hi
i have a problem here from ODS to InfoCube delta load. In Process Chain,
the process loading has failed from ODS to InfoCube yesterday. so the QM status for the yesterday's ods is red. so activation also failed for today & yesterday.
now i want to load for today's & yesterday's data to Cube.
Please let me know how can i solve this without missing any data.
Regards
swetha

Swatha
First Delete the incorrect "Red" Requests from infocube .
then, Goto infopackge and schedule the load again , The system will ask you for "Repeat Delta " , Click "Yes" . This procedure will update the failed requests along with further delta records to your cube .
Howevr, if your INIT is deactivated; First Execute Initialize delta withour Data Transfer , and then execute delta
This should solve your problem
Priya

Similar Messages

  • Full and delta Data loads in SAP BI 7.0

    Hi,
    Kindly explain me the difference between full and delta data loads in cube and DSO.
    When do we select change log or active table(with or without archive) with full/delta in DTP for DSO.
    Please explain the differences in data load for above different combinations.
    With thanks and regards,
    Mukul

    Please search the forums. This topic has already been discussed a lot of times.

  • Delta data upliad problem

    Hi,
    I am facing problem delta data uploading.  Following steps as follows which I have done :
    1.     First I have upload the data with Initialize delta process ( Initialization with Data transfer )
    It was working fine and uploaded data to ODS.
    2.      Send I have upload the data with delta update option.
    It is working but no data is being uploaded.
    In customize data source I have selected delta specific field CPU_DT( Date field ).
    Can any one help me what I have done mistake.
    Thanks in advance,
    Regards,
    Goutam

    HI,
    Possibly you must have done the Init with Data transfer.....so all the records available has come to BI system.....now again you are running the delta.....but there is no changed or new records available in source system.....that why it must be coming with 0 records........
    You can manually change the records in base table or add some new records....then execute the delta.... you will get some records in BI.....................
    The other option to check your delta functionality is to delate all the data and also delete the Init.....................
    Now you again run the IP with Init and without data transfer...............in this case it will enable the next load for delta .....now you run the delta IP........it should get the records in BI.....
    Thanks
    Mayank

  • Data load problem - BW and Source System on the same AS

    Hi experts,
    I’m starting with BW (7.0) in a sandbox environment where BW and the source system are installed on the same server (same AS). The source system is the SRM (Supplier Relationship Management) 5.0.
    BW is working on client 001 while SRM is on client 100 and I want to load data from the SRM into BW.
    I’ve configured the RFC connections and the BWREMOTE users with their corresponding profiles in both clients, added a SAP source system (named SRMCLNT100), installed SRM Business Content, replicated the data sources from this source system and everything worked fine.
    Now I want to load data from SRM (client 100) into BW (client 001) using standard data sources and extractors. To do this, I’ve created an  InfoPackage in one standard metadata data source (with data, checked through RSA3 on client 100 – source system). I’ve started the data load process, but the monitor says that “no Idocs arrived from the source system” and keeps the status yellow forever.
    Additional information:
    <u><b>BW Monitor Status:</b></u>
    Request still running
    Diagnosis
    No errors could be found. The current process has probably not finished yet.
    System Response
    The ALE inbox of the SAP BW is identical to the ALE outbox of the source system
    and/or
    the maximum wait time for this request has not yet run out
    and/or
    the batch job in the source system has not yet ended.
    Current status
    No Idocs arrived from the source system.
    <b><u>BW Monitor Details:</u></b>
    0 from 0 records
    – but there are 2 records on RSA3 for this data source
    Overall status: Missing messages or warnings
    -     Requests (messages): Everything OK
    o     Data request arranged
    o     Confirmed with: OK
    -     Extraction (messages): Missing messages
    o     Missing message: Request received
    o     Missing message: Number of sent records
    o     Missing message: Selection completed
    -     Transfer (IDocs and TRFC): Missing messages or warnings
    o     Request IDoc: sent, not arrived ; Data passed to port OK
    -     Processing (data packet): No data
    <b><u>Transactional RFC (sm58):</u></b>
    Function Module: IDOC_INBOUND_ASYNCHRONOUS
    Target System: SRMCLNT100
    Date Time: 08.03.2006 14:55:56
    Status text: No service for system SAPSRM, client 001 in Integration Directory
    Transaction ID: C8C415C718DC440F1AAC064E
    Host: srm
    Program: SAPMSSY1
    Client: 001
    Rpts: 0000
    <b><u>System Log (sm21):</u></b>
    14:55:56 DIA  000 100 BWREMOTE  D0  1 Transaction Canceled IDOC_ADAPTER 601 ( SAPSRM 001 )
    Documentation for system log message D0 1 :
    The transaction has been terminated.  This may be caused by a termination message from the application (MESSAGE Axxx) or by an error detected by the SAP System due to which it makes no sense to proceed with the transaction.  The actual reason for the termination is indicated by the T100 message and the parameters.
    Additional documentation for message IDOC_ADAPTER        601 No service for system &1, client &2 in Integration Directory No documentation exists for message ID601
    <b><u>RFC Destinations (sm59):</u></b>
    Both RFC destinations look fine, with connection and authorization tests successful.
    <b><u>RFC Users (su01):</u></b>
    BW: BWREMOTE with profile S_BI-WHM_RFC (plus SAP_ALL and SAP_NEW temporarily)
    Source System: BWREMOTE with profile S_BI-WX_RFCA (plus SAP_ALL and SAP_NEW temporarily)
    Someone could help ?
    Thanks,
    Guilherme

    Guilherme
    I didn't see any reason why it's not bringing. Are you doing full extraction or Delta. If delta extraction please check the extractor is delta enabled or not. Some times this may cause problems.
    Also check this weblog on data Load errors basic checks. it may help
    /people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
    Thanks
    Sat

  • Data load problems

    Hello friends
    I am facing a problem in the data load. I modified a cube by adding few Characteristics. The characteristics were first added in the communication structure and in the transfer rules. Then I reactivated the update routine. Finally, I deleted any previous data load request for the cube and did a full load. However i wasn't able to find any data for the newly added fields in the Cube.
    Did I miss something. Any help will be appreciated in this regard.
    Thanks
    Rishi

    how come ODS came in to picture,this was not mentioned in ur prev post,are u loading it from ODS to CUbe and having problems??
    looks u are not using DTP ,in that case check the change log for the newly added fields and then have data flow as ODS>PSA>Cube and check the PSA if those fields are present ..if yes check for update rules in debugging mode of those gets deleted
    Hope it Helps
    Chetan
    @CP..

  • Data load problem with Sales Header and Item

    Hi all,
    The delta loads have failed, so I want to reload the delta again.  I deleted the failed requests in data targets and then trying to reload the data.  I am getting a message saying
    Last delta update is not yet completed
    Therefore, no new delta update is possible.You can start the request again if the last delta request is red or green in the monitor (QM activity)
    Is it in RSA7, that I have to make the delta red?  Please let me know where I have to do this.  The data is going to an ODS object.
    thanks
    Sabrina.

    Hi Sabrina,
    Hope you have sorted it out by now, as there are other responses as well. Assuming that you now know the cause of failure.
    For the below message "If you set a 'red' delta upload to green,with the next request, BW sends a delta request to the source system and this delivers the next delta data.
    The data from the 'red' delta load is then no longer available (even with a repeat). This can lead to loss of data.Do you want to execute a QM Action?" -- Say OK and and set the QM status to red (status not ok) and when prompted for activation of M records, say "no" (as indicated in my previous post).
    However, to be able to load this request from PSA you need to have this request in PSA (depending on the processing options), so goto RSA1> Modeling> PSA--> find your request under the relevant application component, and right click -->start the update immediately.
    Hope it helps,
    Sree

  • Is there any setting in ODS to accelerate the data loads to ODS?

    Someone mentions that there is somewhere in ODS setting that make the data load to this ODS much faster.  Don't know if there is kind of settings there.
    Any idea?
    Thanks

    hi Kevin,
    think you are looking for transaction RSCUSTA2,
    Note 565725 - Optimizing the performance of ODS objects in BW 3.0B
    also check Note 670208 - Package size with delta extraction of ODS data, Note 567747 - Composite note BW 3.x performance: Extraction & loading
    hope this helps.
    565725 - Optimizing the performance of ODS objects in BW 3.0B
    Solution
    To obtain a good load performance for ODS objects, we recommend that you note the following:
    1. Activating data in the ODS object
                   In the Implementation Guide in the BW Customizing, you can implement different settings under Business Information Warehouse -> General BW settings -> Settings for the ODS object that will improve performance when you activate data in the ODS object.
    2. Creating SIDs
                   The creation of SIDs is time-consuming and may be avoided in the following cases:
    a) You should not set the indicator for BEx Reporting if you are only using the ODS object as a data store.Otherwise, SIDs are created for all new characteristic values by setting this indicator.
    b) If you are using line items (for example, document number, time stamp and so on) as characteristics in the ODS object, you should mark these as 'Attribute only' in the characteristics maintenance.
                   SIDs are created at the same time if parallel activation is activated (see above).They are then created using the same number of parallel processes as those set for the activation. However:if you specify a server group or a special server in the Customizing, these specifications only apply to activation and not the creation of SIDs.The creation of SIDs runs on the application server on which the batch job is also running.
    3. DB partitioning on the table for active data (technical name:
                   The process of deleting data from the ODS object may be accelerated by partitioning on the database level.Select the characteristic after which you want deletion to occur as a partitioning criterion.For more details on partitioning database tables, see the database documentation (DBMS CD).Partitioning is supported with the following databases:Oracle, DB2/390, Informix.
    4. Indexing
                   Selection criteria should be used for queries on ODS objects.The existing primary index is used if the key fields are specified.As a result, the characteristic that is accessed more frequently should be left justified.If the key fields are only partially specified in the selection criteria (recognizable in the SQL trace), the query runtime may be optimized by creating additional indexes.You can create these secondary indexes in the ODS object maintenance.
    5. Loading unique data records
                   If you only load unique data records (that is, data records with a one-time key combination) into the ODS object, the load performance will improve if you set the 'Unique data record' indicator in the ODS object maintenance.

  • Zero Record Data Load Problem

    Hi,
    Please give your suggestion for following problem.
    we are loading data from ETL (Flat File - Data Stage) into SAP BW 3.1.
    data may contain Zero records. When we try to push the data into BW. At ETL side, it is showing successful data transfer. At, BW side it is showing "Processing state" (Yellow light). and all BW resources are hang-up.
    When we try to send another data load from ETL side, We could not push the data as BW resources are hang up by the previous process.
    Whenever we are getting this kind of problem, we are killing the process and continuing with another data Re-load. But this is not a permanent solution. This is happening more often.
    What is the solution for this problem?
    One of my colleague suggested following suggestion. Shall I consider this one?
    Summary:  when loading with empty files, data may be in the processing state in BW 
    Details:  When user load with empty file(must be empty, can not have any line returns, user can check the data file in binary mode), data is loaded into BW with 0 records. BW will show be in yellow state(processing state) with 0 record showing, and in the PSA inside BW, 1 datapacket will show there with nothing inside. Depends on how user configured their system, BW server can either accept the 0 record packet or deny it. When BW server is configured to accept it, this load request will change to green state(finished state). When the BW server is configured to deny it, this load request will be in the yellow state.
    Please give me ur suggestions.
    Thanks in advance.
    Regards,
    VPR

    hi VPR,
    have you tried to set the light 'judge'ment
    go to monitor of one request and menu settings->evaluation of requests(traffic light), in next screen 'evaluation of requests', 'if no data is avaible in the system, the request' -> choose option 'is judged to be successful' (green).
    Set delta load to complete when no delta data
    hope this helps.

  • After recent patch upgrade, BW delta Data loads for 2LIS_02_ITM failing

    Hi All
    We have patched our BW 3.5 system from 16 to 25. After updating patches, I am geetting delta load issues.
    2lis_02_itm and 2lis_02_scl delta loads are taking long long time. Deltas are failing even for 3000  records . some time it is taking 14 hours .  Delta loads are failing  and I am getting below message. Please advise.
    I am still getting below dump and i could not find any errors in
    ST22. Please see below error.
    Processing in Warehouse timed out; processing steps mising
    Diagnosis
    Processing the request in the BW system is taking a long time and the
    processing step Update rules has still not been executed.
    System response
    <DS:DE.RSCALLER>Caller is still missing.
    Procedure
    Check in the process overview in the BW system whether processes are
    running in the BW system under the background user.
    If this is not the case, check the short dump overview in the BW system.
    Thanks
    Pramod

    Hello Pramod,
    Is this load is to load to initial level ODS? If Yes I understand that you have issue in loading but not at activation of the ODS?
    Normally this kind of issue comes during the activation of ODS.
    1. If you are getting this during the data loads, then try to check loading only to PSA first and then from PSA to target? And check how much time that it's taking as this will help to track the issue whether its present in Source or in BW?
    2. If the load is fine till PSA then try loading the same to ODS and then check whether this issue is present or not?
    3. At the same you need to check the source side the system load and the number of processors which are available?
    4. Did you perform the delta queue draining before the stack upgrade in R/3 or not? Normally as a pre-requisite this needs to be done if not then you will have issues in extracting the data!
    5. Finally this can be avoided by having Initwithout data transfer and then performing the Delta loads. BUt for this need to first extract all the data from Source to BW and then take a down time in R/3 for few min and perform this activity so that the Init Timstamp will be reset properly and the Delta should work fine for you.
    Do get back to us with more details.
    Thanks
    Murali M

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

  • Delta data load for huge table in Data Services XI R3

    Hi,
    We have a project requirement of pulling delta data once in a week from table which has around 44 million records but it doesn't have any last modified column.
    In such case we have to use table comparison transform, but it will be very time consuming.
    Please provide some suggestions to meet this requirement.
    The source of DS job is a snapshot(the source table is in a remote database).
    Thanks!

    Because SAP Business Objects Data Services XI 3.x doesn't have any built-in delta-enablement mechanism with R3/ECC, the only possibility right now is to do a table compare. Given that this is only a weekly activity, while maybe time-consuming, it may be sufficient.
    In the future, you may want to consider activating the related SAP BW standard content DataSource(s) to extract into Data Services prior to loading to the target repositories. This may provide delta-enablement for the data that you're extracting.

  • Data loading problem with Movement types

    Hi Friends,
            I extarcted data using the data source General Ledger : Line itemdata (0fi_gl_4) to BW side.
        Problem is Movement Types for some documents missing.
    But i checked in rsa3 that time showing correctly.
    i restricted the data in bw side infopackage level only particular document that time data loading perfecly.
    this data source having 53,460 records.among all the records 400 records doc type 'we' movement types are missing.
    please give me solution for this how to loading the data with movement types.
    i checked particular document of 50000313 in RSA3 it is showing movement types. then i loaded data in bw side that time that movement types are not comming to be side. then i gave the particular doc 50000313 in infopackage level loading the data that time movement types are loading correctly. this extaractor having 55000 records.
    this is very urgent problem.Please give me reply urgenty. i am waiting for your's replys.
    Thanks & Regards,
    Guna.
    Edited by: gunasekhar raya on May 8, 2008 9:40 AM

    Hi,
    we enhanced Mvement type field(MSEG-BWART) General ledger (0FI_GL_4) extractor.
    this field populated with data all the ACC. Doc . number.
    Only 50000295 to 50000615  in this range we are not getting the movement types values.
    we didn't write any routines in transfer and update rules level.
    just we mapped to BWART field 0MOVETYPE info object.
    we restrict the particular doc no 50000313 infopackage level that time loading the the data into cube with movement types.
    but we remove the restriction infopackage level then loading the data that time we missing the movement types data of particular doc no 50000295 to 50000615.
    Please give mesolution for this. i need to solve this very urgently.
    i am witing for your reply.
    Thanks,
    Guna.

  • 0CO_PC_ACT_05 datasource no delta data load

    Hi friends,
    0CO_PC_ACT_05 datasource have only full load.(no delta)
    I don't use the filter so the data load takes a long time.
    Every day will install and delete for last year
    how to create a process? (prosess steps,filter, abap code...)
    Previous years will remain.
    System BI 7.0
    Very thanks.

    Hi Mti,
    Thanks for reply.
    I need to create a generic datasource on RESB and MBEW table
    fields from the RESB table is
    BDTER
    BDMNG
    MATNR
    WERKS
    AUFNR
    EBELN
    EBELP
    PLNUM
    fields from the MBEW table is
    VERPR
    LBKUM
    PEINH
    SALK3
    Please tell me how to create a database view on these table.  and tell me the joining conditon for the view.
    And which field i need to take for 'delta field' in datasource.
    Thanks in advance

  • ERPI: Data Loading problem Hyperion Planning & Oracle EBS

    Hi
    I am trying to load data from Oracle EBS to Hyperion Planning.
    When i push data Zero rows are inserted in Target.
    When i look at Table " SELECT * FROM TDATASEG "
    It is showing me data but it is not comminting data in Target application.
    The reason is Data difference in Source (EBS) and Target.
    In my source Year is 2013 but in Target 'FY14' so for Entity Source is '21' but Target is '2143213'
    Can you please let me know how to solve this issue?
    can i place a Lookup table for this in EPRI.
    i am using EPRI and ODI to push data.
    Regards
    Sher

    Have you setup the data load mapping correctly to map the source value to the proper target value? Based on what you are describing it seems that the system generated * to * map is being used, if you are mapping a source to a different target, this needs to be added to the data load mapping.

  • EIS data load problem

    Hi,
    I use user defined sql to do a data load using EIS 7x
    When i run the sql in toad just to see the data I see 70000 rows
    But when I use the same sql in the userdefined sql and try to load data...I dont know why EIS says that it loaded around 69000 rows and also I see no rejections...
    I even made some sql changes to find out what are the records that are not being loaded..and I see some rows when I run a sql in toad and if i use the same in EIS its not loading those rows which I can see in toad for the same sql ...
    This is very strange.. Can any one help me with this,..??

    Glenn-
    I dont think there is anything unique about the missing rows..
    Actually the a part of code has been added to the previously working view(which i use to load data) to bring in some additional data...
    I took that part and tried to load data...and I see no data being loaded or rejected..
    It just says that records loaded "0"..rejected 0...
    but the same part brings in the required additional data... when exectued in toad..
    and about the excel sheet lock and send..I did that a week and as you said to my surprise it loads everything....
    This was the test bu which I figured out that EIS is not even able to load a part of data...and I found the exact part of data by going through it closely..
    So I think this is something to do with sql interface..
    And I did not understand the last lines in your post...
    /////I know when I do regular Sql interface some data types don;t load and I have to convert them to varchar tto get them to work. If the Excel file and Flat file loads work, look at that//////
    what did convert to varchar???
    Excel load works fine..So I think its something similar to what you mentioned in your post...
    Can you please explain it ...

Maybe you are looking for