Selection in Infopackage and delta

Hi Gurus/Experts..
If data for delta intialization is huge and if the data transfer is split by using selection in infopackage and later if i run the delta will it apply only for last selection of delta intialization or for the entire selection so far made ?
Many thanks in advance...

Hi Kanson,
A delta requested after several initializations, contains the sum of all the successful initial selections as a selection condition. This selection condition can then no longer be changed for the delta.
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/content.htm
Hope this helps...

Similar Messages

How to change date selections at Infopackage data selections in production sys

Hi All ,
we are loading data into Infocube from datasource ,one process chain for delta init with data transfor ,which has data selections at infopackage say 06.2014 and other process chain for delta which has same selections at infopackage . Now I want change this data selections at Infopackage level .
I Have tried to change these dates in data selections at infopackage level , tho I have changed and saved to future date at delta initial with data transfor ,it's keep coming back to 06.2014. Of course data selection at delta Infopackage level is faded .
I Want to set future date with delta int with disturbing delta loads . How to do it please .
regards
hari

Hi Ram,
We will load delta Intial with data transfer every weekend , and we run delta everyday , because we do delta init with data transfer with selections say ( 01.20011 to 12.2003 ) every weekend , hope I need to create new delta infopack with new data selections say ( 01.2004 to 12.9999) only to get update data in Infocube.
Please correct me if I am wrong .
Regards
hari

No selection in infopackage possible when Init-load

Hello all,
I have created a loading proccess from an ODS to an Infocube via delta-load. I want to restrict the data and therefore I want to use the selction tab from the infopackage menu. But this is just possible when I choose full-load. When I choose Init-load or delta-load, there is no restriction possible in the selection screen.
Ho can I restict data when i load via delta? the release is 3.5.
Any help would be great.
Best Regards,
Stefan from Munich/Germany

Dear Stefan,
You can not restrict an init/ delta load from an DSO, because the data loaded will correspond to the change log table of the DSO.
What you can do is a "fake" delta. You put a "changed date" in you DSO (filled by the sy-datum in the update rule) and then do a full load from your DSO to your cube with the selection you want and changed data = today. But you will have to be careful in case of reload...
Hope it helps,
Rodolphe

Delta get once and delta request wise?

hi friends,
what scenerio we use delta get once and delta by request at DTP in BI 7.0? i studied many threads, i didnt understand , get delta once some snapshot like? what is the meaning?
can u give me any example , its great?
regards
ss

Indicator: Only Get Delta Once
Source requests of a DTP for which this indicator is set are only transferred once, even if the DTP request is deleted in the target.
Use
If this indicator is set for a delta DTP, a snapshot scenario is built.
A scenario of this type may be required if you always want an InfoProvider to contain the most up-to-date dataset for a query but the DataSource on which it is based cannot deliver a delta (new, changed or deleted data records) for technical reasons. For this type of DataSource, the current dataset for the required selection can only be transferred using a 'full update'.
In this case, a DataStore object cannot usually be used to determine the missing delta information (overwrite and creation of delta). If this is not logically possible because, for example, data is deleted in the source without delivering reverse records, you can set this indicator and perform a snapshot scenario. Only the most up-to-date request for the DataSource is retained in the InfoProvider. Earlier requests for the DataSource are deleted from the (target) InfoProvider before a new one is requested (this is done by a process in a process chain, for example). They are not transferred again during the DTP delta process. When the system determines the delta when a new DTP is generated, these earlier (source) requests are seen as 'already fetched'.
Setting this indicator ensures that the content of the InfoProvider is an exact representation of the source data.
Dependencies
Requests that need to be fetched appear with this indicator in the where-used list of the PSA request, even is they have been deleted. Instead of a traffic light you have a delete indicator.
Get Data by Request
This indicator belongs to a DTP that gets data from a DataSource or InfoPackage in delta mode.
Use
If you set this indicator, a DTP request only gets data from an individual request in the source.
This is necessary, for example, if the dataset in the source is too large to be transferred to the target in a single request.
Dependencies
If you set this indicator, note that there is a risk of a backlog: If the source receives new requests faster than the DTP can fetch them, the amount of source requests to be transferred will increase steadily.
Source : https://forums.sdn.sap.com/click.jspa?searchID=5462958&messageID=3895665
Re: Diff between Only Get Delts Once and Get Data by Request
Check this blog as well : /people/community.user/blog/2007/06/21/sap-netweaver-70-bi-data-transfer-process-with-147only-get-delta-once148

ODS to ODS initialization and delta

Hi All BW Gurus,
We have recently started our BW implementation for COPA module and after successfully loading all the historical data, started running into issues with delta loads. Here is the scenario. R/3 --> PSA --> ODS1 --> ODS2/Cubes. Even though ODS1 and ODS2 are exactly the same, the reason for having ODS2 was to restrict drill down reporting to transaction level detail only for the last 6 months of data. The other advantage (I think) was to do a direct update instead of going through all the logic in the start routine again.
R/3 --> PSA --> ODS1 has been succesful so far with the full loads, initialization and delta updates. Full loads from ODS1 to ODS2 and Cubes have been successful too. Once we triggered initialization without data transfer from ODS1, it errors out with a message that ODS2 already has a full update and hence we cannot trigger an initialization. Researching OSS notes, found a note (689964) for the same issue but the solution was to change all full request loads to repair requests and then trigger the initialization. At the same time they mention that we could end up with other issues with this procedure where we might have duplicate records or even loose data if we ever have to run initialization again.
Any one face this issue? Solutions or work arounds?
Thank You.
Shri

Hi Sreedhar,
It would have been simplar to have followed the OSS 689964 by changing the full loads to repair requests. I ve done it in our production boxes and have not faced any issues yet. If an administrator takes good care of his dataloads then why would a question of duplicate records come in to picture.
But since data has been deleted from ODS2 already, you could follow the step1 and step2 as mentioned, it would work. If you see the Selection Criteria completely greyed out, then please right click on the Infopackage and choose the CHANGE option, this will enable the selection criteria for that Infopackage.
But if you ask my suggestion I would advice you to load the ODS2 using Full Loads from ODS1 and then use the OSS to change full to Repair Full, then run an Init Without Data transfer.
Hope this helps.
Thanks and Regards,
Praveen Mathew

Improvements regarding Infopackages and IDOCs during loads

Hi Experts,
                I have a questions regarding loading the data into cubes .. what improvements can we make regarding to infopackages and IDOCs.
Any ideas would be appreciated.
thks,
Sunil.

Hi ,
1. Limit the amount of created data packages for each load between 1000 -1500 as described in below mentioned SAP OSS note:
892513 - Consulting: Performance: Loading data, no of pkg, req size
Note: 1000-1500 = sum of data packages over all data targets, i.e. with three targets 350-500 packages
How to limit the amount of data packages for the delta load:
Go to transaction RSA1 select your dedicated infopackage -- menue-- DataS. Default Data transfer --enter the max. nummber of data packages to be created for each delta load.
2. Global level :Use Transaction RSCUSTV6 for changing configuration setting for all the infopackages globally   :
   (i).Frequency with which status Idocs are sent : It means how many data-IDocs are described by one Info-IDoc.In simple terms after how many data idocs 1 info idocs to be sent .The larger the packet size for a data IDoc, the smaller you should set the frequency. By doing this, you make it possible to get information on the respective data load status in relatively short time periods when uploading data.You should choose a frequency between 5 and 10 but not greater than 20.
(ii)Datapacket size (Number of Data Records per Package) The basic setting should be between 5000 and 20000 depending on how many data records you want to load
.Recommendation :You should not divide up the quantity of data into too large a number of packets since this reduces performance when uploading. The number of data packets should not be more than 100 per loading process.
(III) ROIDOCPRMS : In order to make the RSCUSTV6 settings work you also need to do the related setting in ROIDOCPRMS in source system .
3. Increase the parallelization of the infopackage if possible
Got to transaction SBIW  increase the amount of wp which can be used.
Please read also OSS note:
595251 - Performance of data mart: Deactivating tRFC sending in BW
4.. Our Infopackage consists of 3 type of message types RSINFO , RSREQ , RSSEND etc. There is a standard program RSEOUT00 in the source system that is used to pushed IDOCS to OS layer .Therefore create variants for the above message type for this program   in the source system .Also create some Background job for this to be run after every 30 minutes .You should not increase the frequency more than this .
Hope this helps .
Regards
Kamal
Edited by: kamal mehta on Dec 25, 2011 1:10 PM

Get rid babylon and delta search, uninstall wont work because it doesn't show up, please help

I want to keep my firefox but have caught this babylon and delta search and no matter what i do it will not go

Remove Babylon Features:
Remove Toolbar (from Extensions)
1. Open Mozilla Firefox. Go to FF menu button.
2. Select Add-ons & than select Extensions. (delete excess text)
3. Remove/Disable the Babylon Toolbar 1.5.0.
4. Restart your browser.
Remove Toolbar (from Add/Remove Programs)
1. Click the Start button on your computer.
2. Select Add-ons & than select Extensions. (delete excess text)
3. Select Programs and Features.
4. Select Babylon Toolbar from the Programs list.
5. Right click to uninstall.
6. Press YES on the popup message.
Remove Search Provider
1. Open Mozilla Firefox. Click on the Search bar, located on the right side of your address bar
2. Press the F4 key and select Manage Search Engines from the drop down list that appears.
3. Select Search the Web (Babylon) and click on the Remove button.
4. Click OK to save your changes.
Remove/Change Home Page:
5. Open Mozilla Firefox. Click on the FF menu button.
6. Select Options.
7. Now select the General tab.
8. In the section of the popup labeled "Home Page," insert the URL of your desired Home Page.
9. Click OK to save the changes.
Remove Babylon Search from New Tab
If when you open a new tab in Firefox, Babylon Search still appears:
1. Type in the address bar line about:config and press enter.
2. Confirm the popup message.
3. In the search field, type "browser.search.selectedEngine". (remove excess text here)
5. Restart your Browser.

Routine for multiple selection in infopackage???

hello guys
I thought of creating one routine for Multiple selections aT Infopackage level....in Selections screen in infopackage,I found one option 'Use Conversion routine' with a check box and it is inactive.....Is it here I need to write my routine inorder to get multiple selection for a infoobject....or is it somehwhere else?How to activate thisoption?
Thanks,
Regards,
S

Hi,
Conversion routines are used in the BI system so that the characteristic values (key) of an InfoObject can be displayed or used in a different format to how they are stored in the database. They can also be stored in the database in a different format to how they are in their original form, and supposedly different values can be consolidated into one.
This will be there at info object level.
Eg : ALPHA: Fills purely numeric fields from the left with zeroes (0).
For multiple selections at info package , in data selection tab under type , u need to select 6 and write the code to select the value.When info package runs it takes the value from routine dynamically and extracts the data based on selection.
Eg: There is a field FISCAL PERIOD For data selection, if u write the code to select current fiscal period. then whenever info package runs it extracts the data for current fiscal period from data source to PSA.
Thanks,
Joseph.

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.

The sme variable in data selection of inpopackage and value in transfer rul

Hello
I would like to use the same variable in data selection of infopackage (1) and as a value in transfer rules (2).
Example :
If I pass 1 I want to see value1 in data selection of infopackage (1) and as a value in transfer rules (2).
If I pass 2 I want to see value2 in data selection of infopackage (1) and as a value in transfer rules (2).
How is possible?

Hi Aleks,
In the transfer routine your code would be something similar to this:
zvar is a variable
select LOW from RSLDPSEL into zvar where LOGDPID = '<Technical name of Infopackage>' and IOBJNM = '<The Info-object whose value you want to use>'.
*Now assign the value
RESULT = zvar.
Hope this helps.
Bye
Dinesh

Generic Delta: Init, Full Upload and Deltas...

Dear All,
Last week on 10.04.2014 I've created "Generic DataSource with Generic Delta" and used CalDay as Delta-Specific Field and lower limit kept to blank and upper limit to 1. On 11.04.2014 I've initialized the Delta with Data Transfer using Process Chain: Time 1:15 p.m (Note: Posting was on)
see below screen shot:
Result: Process Chain was scheduled to immediate and it executed and initialized the delta and brought records as well. See below screen shot of RSA7:
Q: 1: Why generic delta current status is 10.04.2014, as I'v scheduled delta through process chain on 11.04.2014 @ 20:50: and why Total column is showing 0 records? Even I've checked Display Data Entries with Delta Repetition, but could not find any records?
Following is the InfoPackages which I created for Delta Loads and used in another Process Chain for Delta scheduled (daily @ 20: 50).
Following is the DTP used into Delta Process Chain:
On 12/04/2014 when I checked my InfoCube, and found that same number of records being loaded again despite InfoPackage and DTP were created as Delta, see screen shot:
On 12/04/2014 See below PSA table:
On 14/04/2014 when I checked InfoCube and I saw deltas being loaded successfully: see below screen shot:
On 14/04/2014 see below PSA table:
On 14/04/2014 see below RSA7 BW Delta Queue Maintenance screen shot:
Q: 2: Why am I unable to load the Delta records on the day(11/04/2014) when I initialized it with Data and why same number of records being loaded again on 11/04/2014?
Q: 3: On 11/04/2014, around 1:15 p.m I've initialized Delta with Data successfully and the same day (11/04/2014) was my first load of delta records (Time: 20: 50), could this be a problem? as the posting period was on when I initialized and I tried to load the delta on the same day?
Q: 4: Why the pointer is showing me Current Status: 12/04/2014 today and this time around I can find last delta records from "Display Data" option with Delta Repetition?
Q: 5: Have I missed something in the design or data flow?
Q: 6: How can I verify deltas records accuracy on daily basis; is it from RSA3?
or How can I verify daily deltas with ECC delta records?
Q: 7: What is the best practice when you load full data and initialized delta and schedule deltas for Generic DataSources with CalDay as delta specific field?
I will appreciate your replies.
Many Thanks!!!
Tariq Ashraf

I clearly got ur point.....But
If i have situation like ....." I loaded the LO data from R/3 with Init delta......then i loaded 5 loads of delta too.......due to some error in data now i am trying to load all th data......In this case if i do Full upload it is going to bring all the data till 5 th delta load .......If i do Init delta again it is going to bring the same data as full upload..........In LO while loading both Full load or delta init load we need to lock R/3 users....I believe we can load delta even after full upload by using "Init delta without data transfer"............So that wont be the barrier....then what is the difference or how should i figure out which load should i do.............If i am wrong please correct me.......
Thanks

Deletion selection in infoPackage setting

Hi, experts,
    I noticed two options of "selection Area" in deletion selection in infoPackage
    1.Same or More Comprehensive
    2.Overlapping
who can tell me what the exactly difference between these two options? the help of them is quict same.
   in my case, one infoPackage setting period: 1 ~ 8 and country is China. if another infoPackage with setting Period:8 and country is china. it should to delete data in old request with period 8 and country is china. right? but in here, I think both setting is work in this case. then, how was the different usage of this option.
    Thanks in advance.

Let me see if i can help u there.
1. Same or More comprehansive:
Lets say that you ran job yesterday with selection conditions Period: 8 and Country:China.
If you run a job again today with conditions Period: 1 to 8 and Country: China.
The second load is more comprehensive than the first one. Then it'll delete the yesterday load.
2. Overlapping: Lets say yesteday u ran a load with conditions Period: 1 - 8 and Country: China
Today u ran a job again with conditions Period: 3-9 and Country: China. This will delete the yesterday load. If you have selections like this, and if u select the first option "same or more comprehansive", your yesterday load is not deleted.
Is it clear now? Or give me the exact scenario how your loads going to be, i'll see if i can come up with an answer

Sample routine for dynamic flatfile selection in infopackage?

hello guys,
I tried to find one sample routine for Dynamic Flatfile selection at Infopackage level in forums,internet...but couldnot find it....(something like....we give one flatfile everyday...process chain runs everday...and whenever Infopackage executes...it selects that days flatfile basing on date or something and loads the data)....
can anyone give that sample routine ?
Thanks,
Rgards,
S

Hi,
You can select the dynamic flat file using routine at info package.
The routine here is to create dynamic file name, click the routine button beside the name of flat file.
create name and write the related code.
Eg: concatenate 'D:\BIFLATFILES\PRODUCTDATA_' SY-DATUM '.CSV' INTO P_FILENAME.
In this path you have to paste your file with name PRODUCTDATA_09.10.2009.CSV.
So if it is daily load we need change the file name with that date.Infopackage automatically picks up this file and loads the data.
Based on your requirement you need to change the code to select file with path.
Thanks,
Joseph

All Hierarchy selection in Infopackage

Hi Everybody.
Can anybody help me in selecting all the available hierarchy in infopackage for hierarchy extraction.
Thanks n regards
Raghavendra D

Hi everybody.
I manage to do that by ABAP using BAPIs.
Pre-condition:
You have to first create an InfoPackage, and click the button of "Available Hierarchies from OLTP". After that, mark those you'll want to load data in the option "Relevant for BW". Save the InfoPackage.
Create the following program in transaction se38:
+*&----
*& Report ZAUTO_CHANGE_IP                                             *
REPORT ZAUTO_CHANGE_IP                         .
DATA: S_HIER_PAR type BAPI6109HIE.
DATA: count type i.
DATA: I_T_RETURN type BAPIRET2 occurs 0,
      S_RSOSOHIE type RSOSOHIE occurs 0.
field-symbols: -HIECLASS.
Executa BAPI BAPI_IPAK_CHANGE
Altera a selecção da hierarquia
CALL FUNCTION 'BAPI_IPAK_CHANGE'
EXPORTING
    INFOPACKAGE = IPCKGE
    HIE_PARAMS = S_HIER_PAR
TABLES
    RETURN = I_T_RETURN.
if sy-subrc = 0.
Executa BAPI BAPI_IPAK_START
Executa o InfoPackage
    CALL FUNCTION 'BAPI_IPAK_START'
    EXPORTING
      INFOPACKAGE = IPCKGE
    TABLES
      RETURN = I_T_RETURN.
    if sy-subrc = 0.
      if count = 10.
        count = 0.
        WAIT UP TO 60 SECONDS.
      endif.
    endif.
endif.
count = count + 1.
endloop.
+
When you execute the program you'll have to insert the technical name of the datasource where the infopackage is created and the technical name of the infopackage.
The program loads all the hierarchies and it sleeps after 10 requests by a minute so it won't consume all the processes.
Change it as you like.
It worked for me, because i want to load 913 hierarchies, and this is the better and faster way.
Best wishes,
Diogo from Portugal.

Selective data load and transformations

Hi,
Can youu2019ll pls clarify me this
1.Selective data load and transformations can be done in
    A.     Data package
    B.     Source system
    C.     Routine
    D.     Transformation Library-formulas
    E.     BI7 rule details
    F.     Anywhere else?
If above is correct what is the order in performance wise
2.Can anyone tell me why not all the fields are not appear in the data package data selection tab even though many include in datasource and data target.
Tks in advance
Suneth

Hi Wijey,
1.If you are talking about selective data load, you need to write a ABAP Program in the infopackage for the field for which you want to select. Otherway is to write a start routine in the transformations and delete all the records which you do not want. In the second method, you get all the data but delete unwanted data so that you process only the required data. Performancewise, you need to observe. If the selection logic is complicated and taks a lot of time, the second option is better.You try both and decide yourself as to which is better.
2. Only the fields that are marked as available for selection in the DS are available as selection in the data package. That is how the system is.
Thanks and Regards
Subray Hegde

Selection in Infopackage and delta

Similar Messages

Maybe you are looking for