DTP Delta and Full Load...

Dear All,
I'm working with SAP BW 7.3 and I have a standard data flow, starting with DataSource, DSO and InfoCube. My process chain faced an error and for last week or so I could not fetch deltas. To remove the error I had deleted all records from InfoCube, since I had all requests available into DSO. Then I manually loaded Full Load from DSO to InfuCube. But next day when my process chain executed it brought all precious and new records again into InfoCube, as the delta was properly fetched into DSO but it did not come into InfoCube, as it was coming before. When I checked Active and Change Log tables of DSO these two had same number of records.
1. What could be the reason that delta DTP between DSO and InfoCube is not fetching only delta records, it was fetching deltas records before full load?
2. Have I made a mistake or missed any setting in DTP while executing full Load DTP between DSO and InfoCube?
3. What are these options for in Extraction Tab of DTP and when we use following options and why:
    i.   Active Table (with Archive)
    ii.  Acitve Table (Without)
    iii. Archive (Full Extraction only)
    iv. Change Log
I will appreciate your reply.
Many thanks!
Tariq Ashraf

Hi Tariq,
Please check the below:
Delta Init. Extraction from
Active Table (with Archive)
The data is read from the DSO active table and from the archived data.
Active Table (Without Archive)
The data is only read from the active table of a DSO. If there is data in the archive or in near-line storage at the time of extraction, this data is not extracted.
Archive (Full Extraction Only)
The data is only read from the archive data store. Data is not extracted from the active table.
Change Log
the data is read from the change log and not the active table of the DSO.
Hope this answers your question. Let me know if any required.
Regarsd
Ramesh V

Similar Messages

  • Perform INIT, DELTA, and FULL Load from R3 to BI 7.0

    Hi,
    Could anyone please give me the information about how to perform the following to load data from the R3 system to the BI 7.0 system:
    1. INIT Load
    2. Delta Load
    3. Full Load
    4. RealTime Data Acquisition
    Where can I find the settings for all the above in DTP?
    For Real Time Data Acquisition; Don't I have to load the data from the data soruce to the PSA........
    Does the data goes directly from the data source to the data target throguh Daemon Process?  I read the SAP Help doc's but still little confused.......could any one please explain it in your clear way.
    Thank, I will assign the points.

    the first three are similar to 3.5
    check out this blog by KJ for RDA
    Real-Time Data Acquisition -BI@2004s

  • Delta AND Full load on 2LIS_11 Extractor

    Dear All,
    I have a 2LIS_11** extractor in place which loads data via delta. Now I want to add a full load through the same extractor to a new infoprovider.
    What is the scenario to do this? I know that I need to fill the setup tables, but won't that conflict with my delta load?
    Your response will be appreciated and rewarded.

    Hi,
    as long as you don't load the data into your already existing ODS you will be fine.
    regards
    Siggi

  • Delta and Full Load question for cube and ODS

    Hi all,
    I need to push full load from Delta ODS.
    I have process chain.... in which the steps are like below,
    1. R/3 extractor for ODS1 (delta)
    2. ODS1 to ODS2 (delta)
    3. ODS2 to Cube ---> needs to be full load
    Now when i run process chain by further processing automatically ODS2 does init/delta for Cube.
    How can i make it possible for full load ??
    can any one guide anything in this ?
    Thanks,
    KS

    Hi,
    1. R/3 extractor for ODS1 (delta) :  This is OK, normally you can put the Delta InfoPack in Process Chian
    2. ODS1 to ODS2 (delta): It automatically flow from ODS1 to ODS2 (you need to select Update Data automaticall in the Targets at the time of ODS creation)
    3. ODS2 to Cube ---> needs to be full load  :
    This you create a Update rules from ODS1 to Cube then Create InfoPackage in between ODS2 and Cube then do full loads. You can delete the data in the CUbe before the load ann dthen do Full load to Cube.
    Note: In ODS2 don't select Upadate Data autmaticlly to Data Targets
    Thanks
    Reddy
    Edited by: Surendra Reddy on Nov 21, 2008 1:57 PM

  • Delta and Full load from a single Delta ODS

    I have delivered 0DS 0GT_DS01 that is being loaded from R/3 as a delta update. This ODS is then loaded to a delivered InfoCube 0GT_C01 as a delta.
    My question is this, can I create update rules and a Infopackage to do a full load from 0GT_DS01 ODS to my custom ODS ZGT_DS01?
    I kind of remember from my BW310 class that in release 3.5,  if I have an ODS to InfoCube Delta update all other updates from that ODS must be a delta also.
    Regards,
    Mike...

    Siva,
    I created my update rule without a problem.
    I created the Infopackage with my ZGT_DS01 ODS at the target, the update mode as FULL and I saved the InfoPackage. After SAVE I went to the drop-down menu, Scheduler ==> Initialization For This Datasource and there is a Delta present.
    The Infopackage works OK when I run is from RSA1, but when I put the Infopackage in Process ChainI get and error "Delta upload is only possible after successful initialization". What I see in the Manage screen for my ZGT_DS01 ODS is a request for a full load followed by a request for a Delta.
    Any Ideas why the infopackage works in RSA1 but not in a process chain?
    Regards,
    Mike...

  • Delta and Full load Process Chain

    Hi Guru`s,
    I have a one standard target (infocube) which is fetching data from the 3 datasources. Out of 3 datasources 2 are standard datasources and 1 is Generic datasource (Custom datasource).
    These 2 standard datasources have Delta load and Generic datasource have full load.
    I have to design the process chain by using Full load and Delta load.
    Can any body tell me how could I achieve  this requirement.
    Thanks in Advance,
    Venkat

    Hi,
    Please check the follwing steps,
    Delta chain:
    Step- 1 Start varitant
    Step- 2 Delete PSA request(Full- ur Genric DS)
    Step- 3 delta infopackage1
    Step- 4 delta infopackage2
    Step- 5 full infopackage(Genric DS)
    Step- 6 DTP1
    Step- 7 DTP2
    Step- 8 DTP3
    Full chain:
    Step- 1 Start varitant
    Step- 2 Delete PSA request for PSA1
    Step- 3 Delete PSA request for PSA2
    Step- 4Delete PSA request for PSA3
    Step- 5 FUll IP1
    Step- 6 Full IP2
    Step- 7 Full IP3
    Step- 8 DTP1
    Step- 9 DTP2
    Step- 10 DTP3
    I have given steps upto DSO only.
    Thanks,Girish

  • BW Delta and Full load

    Hi !
    This is a simple question with BW 3.5 :
    A standard extractor with Delta is extracting everyday delta to 1st level ODS -> 2nd level ODS -> Cube.
    Now i want to add 2 ODSes in same flow and they should also catch all these delta. Along with that I want to load for remaining period of this month (ex. Full load from 1st to today of the month and then onwards delta)
    So new structure would be
    0CRM_SALES_ACT_1 -> Level 1 existing ODS delta -> Level 2 existing ODS Delta
                                      -> New level 1 ODS with delta -> New Level 2 ODS with delta
    Can you please let me know how to do that ?
    Full , delta info package ?
    (FYI - i loaded full load for history and then tried delta, but delta failed saying Full load is already there in system)
    Please do not post duplicate threads
    Edited by: Pravender on Apr 12, 2011 7:08 PM

    Partik,
    My suggestion is load data from exiting Level 1 DSO to 2 New DSO's instead of loading directly from source to New DSO's.
    To do that... removed initialization from Level1 DSO to 2nd level DSO and Re-Initialize WITHOUT data transfer by considering new DSO's also and continue delta's.
    Use full load infopackages to load historic data from Level 1 DSO to 2 new DSO's.
    Flow now should be:
    0CRM_SALES_ACT_1 -> Level 1 existing ODS delta -> Level 2 existing ODS Delta
    Level 1 existing ODS delta -> New DSO's
    If FULL loads already there in DSO's further delta's wont work. Convert FULL loads to repair full load using Program: RSSM_SET_REPAIR_FULL_FLAG.
    Then continue delta's.
    Hope it Helps
    Srini

  • Need a single point of view on date selections for Delta and Full load IP's

    Hi Experts,
    Every year we are facing issues on date selections for data extraction, for example the Delta or Full selections for particular IP is like 2005 to 2008 , in this situation, for the year 2009, this IP is picking 0 records as the selections are upto 2008 only.
    My requirement is, I need to check the selections of all the IP's in the system and want to change on need base if the selections are getting expired instead of going and checking manually to each and every IP as the system is having around 3000 IP's, which is a tedious job.
    Guys, please let us know if there exits a Table/Program or any other way to check it.
    Inputs appreciated.
    Regards
    Nandu

    Hi
    Persistent through module RSSM_SHIP_PSEUDO_DVERSION_WRI
    Primary table RSLDPIOSH
    RSLDPIO Links datasource to infopackages
    RSLDPIOT InfoPackage Text Description
    RSLDPRULE ABAP source code for InfoPackages
    RSLDPSEL Hardcoded selections in InfoPackages
    RSMONICDP Contains the request-id number by data target
    RSPAKPOS List of InfoPackage Groups / InfoPackages
    http://help.sap.com/saphelp_nw70/helpdata/en/2e/20d704d45be7458582cdfcc5487090/frameset.htm
    Hope it helps

  • Differentiating factor between delta and full load

    Hi All,
    I have a requirement where i need to abort the load if it is a delta. Currently we are doing a full load . I need to write an ABAP code for this, but what is the factor(field) to decide whether the load is full or delta ?

    If it is an update rule, field g_s_minfo-updmode should have what you look for.
    I am not sure of your requirements but this seems inefficient.

  • COPA delta and Full load inconsistent result

    Hi ,
    whn i do a Full load for COPA(datasource 1_CO_PA1159000) for one particular order number, it returned 5 line items.but when i tried to do Initialization load  it returned only 4line items. One line item is missing.
    Can anyone let me know what could cause this inconsistence between a full load and initialization load on the same datasource extraction.
    Appreciate feedback from anyone.
    Thanks.
    Regards,
    Maili

    Hi,
    Data could be picked from summarization levels or the base tables. The source of data may vary for Full/Init. Please check section 3.4 Data source for CO-PA extraction in the How to CO-PA extraction doc....
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sapportals.km.docs/library/business-intelligence/g-i/how%20to%20connect%20between%20co-pa%20and%20sap%20bw%20for%20a%20replication%20model.0x

  • Delta and Full load in RSA3

    Hi I have managed to extract data for 2LIS_13_VDITM if the load is full.  However, when I try the Delta it gives 0 records.  Do I just need to modify some documents or do I need to create a queue in RSA7, where there is no entry for the 2LIS_13_VDITM.  If I need to create a queue entry in RSA7 could you outline the steps.  Thanks

    Hi venkat,
    There seems to be some confusion. What i suggest is to go for a re-init. The following steps might help you doing that.
    1. In the source system, goto LBWE and for the application component 13, run a V3 update immediately.
    2. In the BW system, pull the delta( even if it 0 records fine )
    3. Delete the content of the data target and delete the init fkag for the data source.
    4. Go back to source system. Delete the content of the setup table and run the setup table again.
    5. In BW, initialise the datasource.
    6. Go back to source system and schedule the V3 update job.
    7. Now you can pull the deltas with delta IP.
    If in any step ur having problem, pls post it.
    Sriram
    Message was edited by: Sriram k

  • Init load, delta load and full load

    Hi BW,
    Please when can I use init delta, delta and full load in a data load process.
    Which of them is suppose to be in a process chain and which one is manual.
    Regards.

    Hi,
    When you want to run delta, you have to initialize it first, thats when you run the init delta.Here you have 2 options with data transfer and without data transfer. If the data target is empty and there's no data, you can run the init with data transfer. This'll act as a full pull and also set up the initialization. If there's data already present, then you are better off running the init w/o data transfer. This dosen't pull over any data, but just sets up the initialization.
    Then you can start using the delta pulls.That'll just bring over the changes and any new records rather than the whole data and is much more efficient.
    You can use full pulls for say generic datasources that are not delta enabled or during a first time data load, or if there is a specific business requirement that needs you to pull over the full data everyday. Or in cases where the std datasource is not delta enabled.
    Cheers,
    Kedar

  • Delta Load and Full load

    What is the difference between delta load and full load?when are they used?

    Hi,
    Delta loads - Brings only the changed or newly added data to the data target...
    Full loads - Brings all the data whether it is old, new or changed data to the data target...
    Full loads are usually used to load master data since it wont change in course of time and delta loads are used when there are large amount of data to be extracted from the source system. It entirely depends on the requirement...
    Regards,
    Kishore

  • Diff b/n Repair full and Full load

    Experts
      Please explain diff b/n Repair full request and Full load.
    If I do Repair full request instead of Full load ,is there any problem in the data ?
    Many thanks
    Manoj

    Hi Manoj,
    You can use a request that was selected as a repair request via Scheduler ® Repair Full Request to carry out a full update in any data target. This also applies to data requests that already contain data from an initialization run or deltas for this DataSource/source system combination, and that have overlapping selection criteria.
    The difference between a Full Load and a Full Repair load is only evident in the case of loading to an ODS (to which you are also loading Init and Delta from the same datasource). If you ODS has the Init request active and you load a Full request, the data will not be activated. You should always use a Full Repair request when you want to load a full load to the ODS. For a cube it does not make a difference as the sequence of data loads is in important in a cube.
    If you have accidentally not marked the request as a repair request, you can convert is using SE38 > RSSM_SET_REPAIR_FULL_FLAG
    Hope this helps...

  • Diffrance between full repair and Full load .

    hello ,
    could you please let me know , what is the diffrance between full repair and Full load .
    Regards

    Hi,
    Full Repair :
    If you indicate a request in full update mode as a repair request, then it is able to update that request in data targets even if they already contain data from initial runs or deltas for this DataSource / source system combination and with overlapping selections.
    Consequently, a repair request can be updated to ODS without checking the sequence of delta requests. The system supports loading in an ODS object by using the repair request without having to check the data for overlapping or request sequencing.
    Full load :
    Pulls the entire data from the source system to the BI system
    Assign points if it helps
    Thanks & Regards
    santo

Maybe you are looking for