Data with delta extraction.

Hi Gurus
I want a small clarification regarding data with delta extraction.
If today the data is extracted from r/3 system with delta to ODS object and the data is activated and datamarted to another ODS and Cube.
Now if tomorrow the same records had changes how will the old data will be changed i.e in cube if we compress the old data what is the scnerio.
Can anyone explain in detail starting from Delta queue to change taking place at cube.
Regards
Raju

Raju,
   Don't worry about compression of Cube... Even if you do delta after compression, nothing to worry about Data. Next time you compress it, it will Make 1 record.
Assume...
Initially... in ODS Document 45000001 Item 0001 qty 10 Amount 20
in Cube Document 45000001 Item 0001 qty 10 Amount 20 (After compression)
Qty changed to 5...
In ODS Document 45000001 Item 0001 qty 5 Amount 10. This record will create 2 delta records to Cube.
that is looks like this...
Document 45000001 Item 0001 qty -10 Amount -20 Record mode ' X' (Before Image)
in ODS Document 45000001 Item 0001 qty 5 Amount 10 Recordmode ' " (After Image)
Finally cube contains...
Document 45000001 Item 0001 qty 10 Amount 20
Document 45000001 Item 0001 qty 10 Amount -20
ODS Document 45000001 Item 0001 qty 5 Amount 10
If you compress cube... you will endup with last record.
all the best.
Nagesh Ganisetti.

Similar Messages

  • 3FI_SL_C1_TT - Procedure of extracting data with delta

    Dear experts,
    I try to load FI-SL data with delta.
    We use extractor 3FI_SL_C1_TT and have implemented the start routine from note 577644 to create 0balance within the transformation.
    Delta is only available for actuals so we select data only for valuetype 10 as recommended.
    I read that I have to do a full update of the closed periods.
    To load the carryforward from 2014 I have to select 000.2015 and load it with a full load.
    Till now every thing is clear.
    But what are the next steps?
    What do I have to select within the infopackage for the init load of the open periods (current year)?
    After executing the init load: how do I have to define the delta load?
    Thanks for your help.
    Best regards
    Mirjam

    Hi Leszek,
    we use cube for each year.
    So when the periods of the previous year (2014) is not closed, too, I have to work with them
    the same as with cube for current year and do at first an init for the whole year and after that a Delta for whole year.
    For current year cube I try do init/Delta with 001.2015 - 016.9999. But what do I do with the carryforward -
    I can´t do only once a full, case with every new data record for 2014 it will Change.
    What is the best practise with carryforward in this case?
    Regards,
    Mirjam

  • No purchasing date in delta extraction (2LIS_02_ITM, 2LIS_02_SCL)

    Hi.
    We have been experiencing some issues with delta extraction of purchasing data, using 2LIS_02_ITM and 2LIS_02_ITM.
    In particular, the posting date's field (BUDAT) is not always filled: for example, I noticed that when users set the final delivery flag even if the purchase delivered quantity does not correspond to the whole order's quantity or the flag has been set later than the change of the delivery date, the field (BUDAT) in the delta queue is not filled.
    By this way, the field may be overwritten: however, we need to keep the posting date value.
    I am wondering whether I am correct and, in this case, it is possible to keep that value: however, it seems that the only way is to use a full extraction of data.
    Thanks a lot

    Roberto Negro,
    While filling setup table by using T-code OLI3BW (Purchasing) it is taking very long time.
    Please let me is there any way to rerduce this time.
    We are at BW 7.3 version.
    Regards,

  • Problems with Delta Extraction for 0CRM_OPPT_H (no data found)

    Hi,
    I've some problems with the Delta Extraction of the Infosource 0crm_oppt_h (CRM Opportunities Header). After initialization I get no delta data from the CRM system.
    What I already did:
    Activated 0crm_oppt_h Data Source (checked functionality with rsa3)
    Started Info Package (Init) on BW side (worked fine)
    Checked the status of the Data Source on the CRM system using BWA7 ("initial upload" is unmarked; "delta active" is marked and what makes me worry is that the column "Queue exists" in <i>unmarked</i>...)
    If I change anything (like Phase, Expected Sales Vol.) in the opportunity, the Delta Extraction get no changes.
    Could You help me out, please?
    Best regards,
    Markus Svec

    hi Markus,
    try to check oss note 788172
    Release Status Released for Customer
    Released on 23.03.2005
    Priority Correction with high priority
    Category Program error
    Symptom
    No data exists in delta extraction from the CRM server to the BW system for business transactions, if parallel processing is applied as per note 639072. But Data is extracted if parallel processing is switched off.ie. when BWA_NUMBER_OFF_PROCESSES is set to 1,there is data during delta. This applies to the following DataSources:
    0BBP_TD_CONTR_1
    0CRM_COMPLAINTS_I
    0CRM_LEAD_ATTR
    0CRM_LEAD_H
    0CRM_LEAD_I
    0CRM_OPPT_ATTR
    0CRM_OPPT_H
    0CRM_OPP T_I
    0CRM_QUOTATION_I
    0CRM_QUOTA_ORDER_I
    0CRM_SALES_ACT_1
    0CRM_SALES_CONTR_I
    0CRM_SALES_ORDER_I
    0CRM_SRV_CODES
    0 CRM_SRV_CONFIRM_H
    0CRM_SRV_CONFIRM_I
    0CRM_SRV_CONTRACT_H
    0CRM_SRV_PROCESS_H
    0CRM_SRV_PROCESS_I
    Other terms
    DataSources, BWA, initial extraction, delta init, parallel processing, no data in delta.
    Reason and Prerequisites
    There is an update on the generated delta table which causes data corruption in running delta initializations as the changed delta sets will be deleted with every further update on documents. An open cursor statement is there without fetch data in SMOX3_GET_DATA.
    Solution
    The problem is solved with the attached corrections.After applying the corrections a new initialization of the affected datasources is necessary.

  • Load data with Delta

    Hello Expert,
    I loaded data from SAP R/3 into PSA using Delta mode and found that a new record which was  just created was not loaded into SAP BI. What could be possible?
    Step of loading
    1. Initial without data into PSA
    2. Full load with criteria Fiscal Period (e.g. 001.2009 - 016.2009) into PSA
    3. Load data from PSA into DSO with update mode = Delta
    4. Create a new transaction from SAP R/3
    5. Load data from SAP R/3 into SAP BI-PSA with update mode = Delta
    Expected Result: A new record should be loaded into PSA.
    Actual Result: There was no record loaded.
    After initial loading without data, is it necessary to full load with all fiscal period. And then load with Delta mode?
    I have never seen this kind of problem before.
    Is anyone familiar with this kind of problem? How did you resolve it?
    Any suggestion would be appreciated.
    Thank you very much
    W.J.

    Hi,
    Is your Datasource is Logistics? if so how the job has been scheduled in LO cockpit (hourly / daily)
    Did you check the record in Delta Queue(RSA7) ?? 
    After initial loading without data, is it necessary to full load with all fiscal period. And then load with Delta mode?
    I have never seen this kind of problem before.
    If you have specific selections you have to do it by repair full load .. and it doesn't impact delta loads

  • Pl/sql to extract data  with form: extract data is a text file

    Hi dear all,
    to be straightforward here is the problem: we currenlty developing with oracle tools :" Developer Suite 10g version 10.1.2.0.2" an interface .
    Using oracle forms, we would like to program a command button that will be in charge of pooling the data from the database and offer the client to save it on his desktop. The extracted data should be a one single flat text file having a one single continuous row. and the data extracted are from a 10 g database( one table having one column(varchar2(240); and 192 rows );
    attached with this mail is ou current script link with the command " when-button-pressed"
    PROCEDURE EXTRACTION_FICHIER_FIC_BDF IS
    n_bouton number;
    LF$File CLIENT_TEXT_IO.FILE_TYPE;
    LC$Name Varchar2(100) ;
    LC$Fic Varchar2(100) ;
    LN$Lines Pls_integer := 0 ;
    LC$Line Varchar2(4000) ;
    -- cursor --
    Cursor C_CUR Is
    SELECT ENREGISTREMENT_BDF
    FROM ops$admO7.fic_bdf
    ORDER BY 1;
    BEGIN
    LC$Name := 'd:\AA1217.bdf';
    LC$Fic := WEBUTIL_FILE.FILE_SAVE_DIALOG
    'd:\',
    LC$Name,
    'Choisir l''emplacement du fichier à sauvegarder'
    If LC$Fic is null Then
    Return ;
    End if ;
    -- Open the file --
    Begin
    LF$File := CLIENT_TEXT_IO.FOPEN( LC$Fic, 'W');
    Exception
    when others then
    message( 'OPEN FILE ERROR ' || LC$Fic );
    raise form_trigger_failure;
    End ;
    -- Write the lines --
    For Cur In C_CUR Loop
    LC$Line := Cur.ENREGISTREMENT_BDF;
    CLIENT_TEXT_IO.PUT_LINE( LF$File, LC$Line ) ;
    LN$Lines := C_CUR%ROWCOUNT ;
    End loop ;
    -- Close the file --
    CLIENT_TEXT_IO.FCLOSE( LF$File ) ;
    set_alert_property('AL_MESSAGE',alert_message_text,'Export terminé avec succès');
    n_bouton :=show_alert('AL_MESSAGE');
    synchronize ;
    Exception
    When form_trigger_failure Then
    CLIENT_TEXT_IO.FCLOSE( LF$File ) ;
    Raise ;
    END;
    thanks if advance !!!!!

    Hello,
    what's your problem with this? You posted a lot of useful information like version infos and code (Hint: when you post code you can do this with the tags so it gets formated), but I cannot see what exactly is failing or behaving unexpected, so you might share that too ;)
    cheers                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • Help!  Problems with delta extraction

    Hi All,
    We've been trying to run a delta load of material master data and because there are so many change records (2.6m) it has been failing on memory errors.  We have now run full load and it completed successfully.  Ran delta again expecting that it would pull 0 records but it is still trying to pull all 2.6m records.  Ran init w/o data.  Ran delta again - still pulling 2.6m and failing. 
    Since we have successfully run full load, is it okay to delete the records from BDCP/BDCPS??
    Other suggestions??

    If you are not using it for other uses (eg. ALE with change pointers), it would be safe to remove the change pointers. You can use BD22 to delete them.

  • BI 7.3 delta extraction with SQL Server 2008

    Hi experts,
    I'm trying to extract data with delta update from a SQL Server with UD Connect, i test this ways:
    Field DateTime in SQL Server: The problem is I only can delta within a day, no changes detected in the same day because SAP detects two fields here date and time, and can only can reference date field as a delta field.
    Field TimesTamp in SQL Server: The problem seems the same, SAP recognize this as a date and time field.
    Can any explain here the correct way for a delta implementation with SQL Server 2008? I would be very grateful.
    Regards,

    Hi Fernando
    That is what I need to do.
    Create a Model from an existing SQL Server database with the Import data Dictionary option , be able to modify tables structures, extended properties in the model, and then sync those changes with the database.
    So far I can't import the extended properties with DM 3.1.1. If you find a way , please let me know.
    Thanks,
    Jorge

  • Delta extraction for FI (AR & AP) data sources

    I tried extracting the data from 2 standard SAP data sources under FI module for Accounts Receivable.
    0FI_AR_10(Customer payment history via delta extraction)
    0FI_AR_5 (customer payment history)
    The data to be extracted into 0FIAR_C05(payment history) info cube.I assigned the 2 data sources to an info source and pumped the data into the cube via an ODS.Now the problem is with delta extraction.No records are picked in the delta extraction.So I checked in extractor checker RSA3 with delta update mode.I got the following error.
    "Could not determine BW release of logical system"
    Could some one resolve the issue?Thanks in advance.
    Thanks & Regards
    Vinay

    Hi ,
    Please go through 493422 note  once . see if suits to your requirement  follow it  accordingly .
    Thanks ,
    Anil

  • Issue with delta queue initialization

    Hello
    I am having a problem with an initialization of the delta queue for a certain extractor. The initialization was successfull, and I can see the extractor in the delta queue maintenance (RSA7) in ECC, but when users are posting transactions in ECC, they are not coming into RSA7.
    The extractor is 0CO_OM_WBS_6, so its not standard LO cockpit where we have V3 (background) jobs which have to be triggered.
    One more thing, the record which was posted was backdated, ie the date is sometime in the past. But I think the delta queue still picks the records. Can i know how the delta queue funtions based on the time stamp?
    Please advise.

    Here is the OOS note fro FI Datasources.
    OSS 485958:
    Symptom
    The FI line item delta DataSources can identify new and changed data only to the day because the source tables only contain the CPU date and not the time as time characteristic for the change.
    This results in a safety interval of at least one day.
    This can cause problems if the batch processing of the period-end closing is still running on the day following the period-end closing and all data of the closed period is to be extracted into BW on this day.
    Example:
    The fiscal year of the company ends on December 31, 2002.
    On January 01, 2003, all data of the closed fiscal year is to be extracted into BW.In this case, the FI line item delta DataSources only extract the data with a safety interval of at least one day.
    This is the data that was posted with a CPU date up to December 31, 2002.
    However, the batch programs for closing the 2002 fiscal year are still running on January 01, 2003.
    The postings created by these programs with a January 01 date for the 2002 fiscal year can therefore only be extracted with delta extraction on January 02, 2003. However, extraction should already be possible on January 01, 2003.
    Other terms
    FI line item delta DataSources
    0FI_AP_4; 0FI_AR_4; 0FI_GL_4
    Reason and Prerequisites
    This problem is caused by the program design.
    Solution
    The functions are enhanced as of PI 2002.1, standard version.
    Due to a customized setting, it is now possible for the FI line item extractors to read the data up to the current date during the delta runs.
    During the next delta run, the data is then read again from the day when the previous extraction was called, up to the current day of the call for the new extraction.This means that the delta extraction of the data always occurs with time intervals overlapping by one day.
    The delta calculation by the ODS objects ensures that the repeatedly extracted data does not cause duplicate values in the InfoCube.
    Activate the new functions as follows:
    1. PI 2001.1 or PI 2001.2:
    Implement the new functions with the correction instructions in this note.As of PI 2002.1, these changes are already implemented in the standard version.
    1. Start a test run for an FI line item DataSource via transaction RSA3.
    2. Two new parameters are now available in the BWOM_SETTINGS table.
    3. Parameter BWFIOVERLA (Default _)
    Set this parameter to "X" using transaction SE16, to activate the new function of overlapping time intervals.
    Caution
    The new function also uses a safety interval of one day to determine the To value of the selection, if the time limit set by BWFITIMBOR is not reached.This means that only data up to the day before the extraction was called is selected, if the extraction starts before 02:00:00 (default for BWFITIMBOR).
    Correction: Parameter BWFITIMBOR (Format HH:MM:SS, default 020000)
    The default value for this parameter is 02:00:00.Do not change this value.
    If this time limit is not reached, only data up to the previous day (with BWFIOVERLA = 'X') or the day before this day (with BWFIOVERLA = ' ') is selected.
    This logic prevents records with a CPU date of the previous day being contained in the posting when the extraction is executed.
    Check any OSS notes for your data source.

  • 0FI_GL_6 delta extraction

    Hello Guys,
    i have a problem with delta extraction for datasource 0FI_GL_6. With full extraction we have no problem but delta doesn't work.
    Seems the problem is in table  BWFI_AEDA2, in this table we should have all changed document (probably registered by the change pointer) with table key GLT0 but we have no entry with this key and we dont' know Why
    Do you know if we have to activate something? , why we have no entry in table BWFI_AEDA2 with GLT0 key ?
    Thanks in advance
    Boris

    Hi Boris
    Have you made an initialisation?
    Regards
    C.

  • Error while doing DELTA Extraction (generic data source)

    Hi BW Experts,
    In my R/3, I have a generic data source ZBUT_VW.
    It receives data from a View which is created based on couple tables.
    When I do full load to the corresponding ODS, it is successful.
    But after that I delete the ODS and created CUBE with DELTA
    I have Initialized delta.
    When I do DELTA extraction, it fails.
    The error “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.”
    I delete the initialization load and trying to do DELTA extraction again and it Fails.
    With the same error
    Please let me know how can I resolve this problem.
    URGENT
    gaurav

    I dont think it is possible to have to additive delta with creation date.
    Try a full load to cube to check if the extractor is working.

  • Extraction, Flat File, Generic Data Source, Delta Initialization

    Extraction, Flat File, Generic Data Source, Delta Initialization
    I have couple of questions regarding data extraction.
    1.     If you have Data Source a Flat File e.g. Excel file I know that you have to create Data Source at BW side. How do you upload updates, by selecting Delta Update when executing next Data Load? Do you ever u201Cconvertu201D this Excel file into Application Tables to become SAP Source 
    2.     Can you please give me example of situation where you had to create Generic Data Source? What is difference between Time Stamp, Calend. Day and Numeric Pointer. Which one is most common to select?
    3.     I read somewhere that Generic Data Source does not have Setup Table. I thought that you have to have Setup Table in order to load transaction Data otherwise you will lock the Application Tables. Where am I going wrong im my thinking please?
    4.     What are steps in terms of IP before, under and after Delta Initialization. I belive that you can do two ways:
    Full Update - Initialize Delta Process (without Data Transfer) u2013 Delta Update  or
    Initialize Delta Process (with Data Transfer) u2013 Delta Update
    Am I right? What is most common method and why?
    5.     If you want to add a filed in Data Source after 6 month using it, you want to do it without re-init Delta Queue. You add field in RSA6, then provide info for ABAP to populate new filed (info u2013 name of Data Source, Extract Structure, field added, name of Application Table which contains the field). How does it work now as there is no SetUp table it has been deleted after Initialisation? How does Delta Queue know that it is going to receive data which has been  expanded by one field or it may does not need to know at all?
    THANKSSSSSSSSSs

    Hi,
    1. If you have Data Source a Flat File e.g. Excel file I know that you have to create Data Source at BW side. How do you upload updates, by selecting Delta Update when executing next Data Load? Do you ever u201Cconvertu201D this Excel file into Application Tables to become SAP Source
    Once you create Datasource for A flat file extraction then it is file source system specific hence you cont change to Application table source Data source
    In info package you can change the source as application server instead of desktop no need to change the DS
    2. Can you please give me example of situation where you had to create Generic Data Source? What is difference between Time Stamp, Calend. Day and Numeric Pointer. Which one is most common to select?
    When we don't find any standard extractor then we can go for Generic(if i want information sales along with finance information in a data source then generally we dont get standard one hence we can go for generic DS)
    Check the below link for More about generic DS .
    http://wiki.sdn.sap.com/wiki/display/BI/Generic+Extraction
    for Delta capturing you can use
    Timestamp(if the table has time stamp filed  so it can stamp the last changed record in that table hence it is easy to get delta based on the time stamp)
    Calday- (If the table doesn't have the Timestamp filed then search for Calday where you can stamp the delta based on the date when documents are changed )
    Numericpointer : If the table doesn't above both then we go for this option where you can the numeric value change stamp )
    3. I read somewhere that Generic Data Source does not have Setup Table. I thought that you have to have Setup Table in order to load transaction Data otherwise you will lock the Application Tables. Where am I going wrong im my thinking please?
    Generic datasource nothing but we extracting data directly from the database table without any interface between the application/systems
    4. What are steps in terms of IP before, under and after Delta Initialization. I belive that you can do two ways:
    Full Update - Initialize Delta Process (without Data Transfer) u2013 Delta Update or
    Initialize Delta Process (with Data Transfer) u2013 Delta Update
    Am I right? What is most common method and why?
    Correct
    5. If you want to add a filed in Data Source after 6 month using it, you want to do it without re-init Delta Queue. You add field in RSA6, then provide info for ABAP to populate new filed (info u2013 name of Data Source, Extract Structure, field added, name of Application Table which contains the field). How does it work now as there is no SetUp table it has been deleted after Initialisation? How does Delta Queue know that it is going to receive data which has been expanded by one field or it may does not need to know at all?
    Once you add the new field to structure(DS) you will get the data as on date onwards not historical data hence what is the concept of setup table  ( delta records come from the Delta Que not from the setup table )
    If you want histaric data to new field then you need to setp table deletion ...etc...
    Hope it is clear..
    Regards,
    Satya

  • Generic Data Source delta is not extracted

    Hi,
    There is a problem in extracting the delta records using Generic Data Source. Delta records ( New / Modified records ) are not posted in the RSA7.
    I'll Explain you the Scenario I have done. Created a generic data source in R/3 using view. In the view there is a field Sales Order No. I have enabled the delta update for this field. In the generic delta i have chosen delta type as Numeric pointer.
    Extracted the entire record using full update and after initializing the Delta, it extracts the delta record well ie. it only extracts the sequence of Sale Order No. First I extracted nine records(i.e 10001 to 10009) using full update. again I entered a record in underlying table with sale order no as 10011-10013. It extracts those records into BW system. Then again I made an entry in the table with sales order no 10010. But the record is not extracted. Even though I tried of specifying safety lower limit as -3. Still it not extracting the record(10010).
    And what if I posted a value of sale order 10014 with the same. what should I do?? Help on this plz.
    --Durai.S

    Hi SVS,
    Thanks for your reply.
    I followed this in my scenario. But I don't understand why it is not extracting? even I specified the safety limit of upper and lower values in the generic delta.
    Here the below explanation shows that the delta record can be extracted even  if the pointer value is greater than the posted value.
    Numeric pointer (last extracted value 10011; Data in underlying table (Max value = 10025) )
    Data would be extracted from a min-value of 10010 (lower limit adjusts the last counter 10011 by specified value u2013 1)
    max-value of 10020 (after adjustment for upper safety limit u2013 by 5). The current pointer would now indicate 10020 in
    RSA7.
    --Durai.S

  • Intervals with generic delta extraction

    Hello,
    Can some1 explain when do we use intervals in generic delta extraction with a good example?
    Thanks in advance.
    Regards,
    KS

    Hi,
    Safety Interval Upper Limit
    The delta-relevant field is a timestamp.
    The timestamp that was read last is 12:00:00. Delta extraction begins at 12:30:00. The safety interval for the upper limit is 120 seconds. The safety interval for the delta request is: 12:00:00 to 12:28:00. Upon completion of the extraction, the pointer is set to 12:28:00.
    Safety Interval Lower Limit
    The delta-relevant field is a timestamp. After images are transferred. In other words, the record is overwritten with the status after the change in BW, for example for master data. Any duplicate records that appear have no effect upon the BW system.
    The last changed timestamp is 12:28:00. Delta extraction begins at 13:00. The safety interval for the lower limit is 180secs. The safety interval for the delta request is: 12:25:00 to 13:00:00. Upon completion of the extraction, the pointer is set to 13:00:00.
    refer to this link.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/frameset.htm
    Hareesh

Maybe you are looking for