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

Similar Messages

  • Error when inital load to cuble

    we are in 3.5,
    and I am doing a delta lode into a cube from ODS and it gives error says
    "Incorrect records were discovered. The incorrect records could not be written into a PSA.
    Time conversion from 0CALDAY to 0FISCPER (fiscal year K4) failed with value 13020601
    Error 5 in the update"
    Any idea? and how can I fix it.
    Please advice me

    your DSO has an incorrect CALDAY of 13020601 and there is an automatic conversion of CALDAY to FISCPER in your cube update rules .
    Either delete this entry from the active data / change log of the DSO or correct the same and put necessary filters in the infopackage to load into cube.
    Edited by: Arun Varadarajan on Feb 2, 2009 10:40 PM

  • Is it possible to tag a pdf with 'reject', so when it loads into Bridge, it will be pre-rejected?

    Is it possible to tag a pdf with 'reject', so when it loads into Bridge, it will be pre-rejected and not view (so long as 'show reject files' is unchecked in Bridge)? - Please see screen shot.
    We're wanting to have all pdf's initially set, so they don't view in Bridge, until the 'reject' tag is then removed.
    Any help would be great! Thanks.

    Well, not possible directly because the Acrobat interface doesn't allow changing Bridge's ratings and labels.  But as Omke Oudeman showed over in the Bridge Scripting forum, they are stored in the XMP metadata, where "Reject" seems to be an xmp:Rating of -1.  Thus you may be able to add this bit of metadata within Acrobat Pro by using the Append... [XMP template] command -- assuming you can come up with an XMP template, and can find the command buried in the interface (in Acrobat 9 it is behind the Additional Metadata button on the Properties/ Description tab, and then from there under Advanced).  Another route might be via Javascript.  Either way, before investing much time you should consider that most software won't see labels and ratings you add to the XMP metadata, and, as Omke mentions in that thread, their rendering seems somewhat fragile even in Bridge.
    Another route might be adapting a metadata category already available in Acrobt's interface: Keywords, say, "Approved" and "NotApproved".  (If you can't touch the Keywords, maybe you could re-purpose another of Acrobat's categories; and of course my suggestions are not related to Acrobat's stock stamps "Approved" and "Not Approved," a different kettle of fish).  Keywords might suffice for you to filter views in Bridge, but if you really want Bridge to show files with "Reject" then they must carry that tag.  If neither an XMP template nor an Acrobat Javascript serves, I imagine a Bridge script could apply "Reject" to files with the keyword NotApproved.  Of course, for any PDFs whose status changes you'd need to adjust both the Reject (xmp:Rating -1) and the keyword; perhaps another script could un-Reject and change the keyword to Approved in one step.

  • Checked some items of multiple-selection list box when form loaded in infopath

    Hi
    I customize sharepoint list with infopath. I have multiple-selection list box and want to checked some items of that automatically when form loaded. how can do this?
    Thanks.

    Hi,
    According to your description, my understanding is that you want to pre-select some items in the Multiple-Selection List Box.
    I recommend to follow the steps below to achieve this goal:
    Click Default Values under Data tab in InfoPath, expand the dataFields and navigate to the Multiple-Selection List Box field.
    Set the Default Value of the Multiple-Selection List Box field.
    Right click the field under the Multiple-Selection List Box group, then select Add another Value Below and set the Default Value for this field.
    Repeat step3 based on the number of the items that you want to be pre-selected.
    More information are provided in the link below:
    http://www.bizsupportonline.net/infopath2010/pre-select-items-multiple-selection-list-box-infopath-2010.htm
    Best regards.
    Thanks
    Victoria Xia
    TechNet Community Support

  • I bought a movie on iTunes and when it loads up I can only play the bonus features and not the actual film. The title screen is also glitched and merges with the scene selection. I don't think it downloaded properly. what can I do?

    I bought a movie on iTunes and when it loads up I can only play the bonus features and not the actual film. The title screen is also glitched and merges with the scene selection. I don't think it downloaded properly. what can I do?

    It happens sometimes. Delete the current copies, don't hide from iTunes in the cloud if prompted, close iTunes, reopen, download from iTunes Store > Quicklinks > Purchased > Music > Not on this computer.
    While downloading click the download icon at the top right and uncheck Enable simultaneous downloads. You may find it more reliable that way.
    tt2

  • Difference: Full load, Delta Load & INIT load in BW

    Hi Experts,
    I am new to SAP BW Data warehousing.
    What is the difference between Full load, Delta Load & INIT load in BW.
    Regards
    Praveen

    Hi Pravin,
    Hope the below helps you...
    Full update:
    A full update requests all the data that corresponds with the selection criteria you have determined in the scheduler.
    You can indicate that a request with full update mode is a full repair request using the scheduler menu. This request can be posted to every data target, even if the data target already contains data from an initialization run or delta for this DataSource/source system combination, and has overlapping selection conditions.
    If you use the full repair request to reload the data into the DataStore object after you have selectively deleted data from the DataStore object, note that this can lead to inconsistencies in the data target. If the selections for the repair request do not correspond with the selections you made when selectively deleting data from the DataStore object, posting this request can lead to duplicated data records in the data target.
    Initialization of the delta process
    Initializing the delta process is a precondition for requesting the delta.
    More than one initialization selection is possible for different, non-overlapping selection conditions to initialize the delta process when scheduling InfoPackages for data from an SAP system. This gives you the option of loading the data
    relevant for the delta process to the Business Information Warehouse in steps.
    For example, you could load the data for cost center 1000 to BI in one step and the data for cost center 2000 in another.
    The delta requested after several initializations contains the upper amount of all the successful init selections as the selection criterion. After this, the selection condition for the delta can no longer be changed. In the example, data for cost
    centers 1000 and 2000 were loaded to BI during a delta.
    Delta update
    A delta update requests only the data that has appeared since the last delta. Before you can request a delta update you first have to initialize the delta process. A delta update is only possible for loading from SAP source systems. If a delta update fails (status red in the monitor), or the overall status of the delta request was set to red manually, the next data request is carried out in repeat mode. With a repeat request, the data that was loaded incorrectly or incompletely in the failed delta request is extracted along with the data that has accrued from this point on. A repeat can only be requested in the dialog screen. If the data from the failed delta request has already been updated to data targets, delete the data from the data targets in question. If you do not delete the data from the data targets, this could lead to duplicated data records after the repeat request.
    Repeat delta update
    If the loading process fails, the delta for the DataSource is requested again.
    Early delta initialization : This is a advanced concept, but just for your information ...
    With early delta initialization you can already write the data to the delta queue or to the delta tables in the application while the initialization is requested in the source system. This enables you to initialize the delta process, in other
    words, the init request, without having to stop posting the data in the source system. You can only carry out early delta initialization if this is supported by the extractor for the DataSource that is called in the source system with this data
    request. Extractors that support early delta initialization were first supplied with.

  • Date selection in Infopackage

    Hi Folks,
      I have a new info provider. Its not been loaded yet. I have to load data from 01/01/2007 to current date. I have done init load from 01/01/2007 to 11/22/2007 by selection option. It went successfully. Now when I am doing delta loads its bringing changed data only from 01/01/2007 to 11/22/2007.Its not bringing data from Nov 22 i.e its not loading any new data from nov 22. In delta infopackage its automatically converting the selection date  01/01/2007 to 11/22/2007 which is similar to init.What I need is changed data from 01/01/2007 to current date.Any help.

    Hi,
    Do one thing.Do a full load with selection condition from 01/01/2007 to current date.Then do init without data transfer.Then run the delta.So what all changes happened in the data will be laoded into the Cube.
    I think since this is a new data target,there is no harm if u do without selection conditions in the init.
    Since if you do init with selection conditions,the delta will run with based on the seletion paramteres which you gave in the init.
    Thanks & Regards,
    Suchitra.V

  • Appended field in the datasource as selection in infopackage

    Hi,
    I have appended a field in my datasource, say for example, country (ZZCOUNTRY). I set ZZCOUNTRY as selection in the datasource so i can filter by country in my infopackage.  When i check my datasource, ZZCOUNTRY is there. But when i use it in filter, the system is ignoring it.
    Example, if i load all data, i get 5 records. 1 is US, and 4 for CA. when i filter by country US and load my infopackage, i am expecting to get only 1 record, but i still get 5 records.
    do you know if it's possible to use appended field as infopackage filter?
    Thanks
    jti

    Hi
    if u want to enchance your datasouce u are suppose to  maintain the DS in RSA6,and then enable the fields for selections.
    i suppose if the fields are appended fields you can't enable those for selection.
    please check if these fields are enables before u proceed.
    hope this helps
    --- Rashmi

  • BIG Question regarding INIT Loads..I am scratching my head for past 2 days

    Hello All,
    I have one big question regarding the INIT load. Let me explain you my question with an example:
    I have a datasource say 2LIS_02_ITM for which I ran the setup tables on JAN 2008. The setup table is filled with say 10,000 records. After that we are running Delta loads everyday till today (almost 30,000 records). Everything is going fine.
    Imagine I lost a delta (delta failed and did'nt I do a repeat delta for 3 days, by then next delta came), Hence I am planning to do a Init load again without deleting / filling the setup tables. Now my question is :
    1) Will I get the 10,000 records which got filled initially in the setup tables or will I get 40,000 records (that 10,000  + 30,000 records)
    2) If it bring 40,000 how is that possible as I hav'nt filled the setup tables?
    3) Is it each time I need to fill the setup tables to start the Init load.
    Waiting for your guidance.........

    Yes...to answer your question
    But...agin I will suggest not to go by that method. Only one delta had failed so why do you want to wipe away the timestamp of the last init just becasue of 1 delta failure? it is possible to correct it
    First of all  i hope you have stopped the process chain or put a hold to Delta jobs
    Now, To answer your doubt, about the status red ..See you mark the status red in each of the the data target before delting the failed request from there (I usually do not just delete the requests frm data targets - I mark them red and then delte it to be safe).
    Do not forget to delete subsequent requests afterthe failed delta (agin I always mark them red  before doing so)
    Regarding the actual reuest itself...you need not mark it red in the monitor..You have got to correct this request and successful - it will automatically turn green.
    If after successfully correcting the request, it still does not turn green, you can set qm status green. The next delta will recognize this a successful request and bring in the next delta (this happens in cases where you have the infopackage in a process chian when it shows green because subsequent processes were not completed etc).
    Let me know in case you have any questions.

  • 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

  • Several single value selection in InfoPackage Data selection using Routine

    Hi,
    I am trying to extract data from a table(containing Ticket data) in R/3 using Generic extractor with table. As the table is not supporting the delta functionality i have to do daily full load for more than 5 lak records.
    I dont want all the tickets from R/3, i just need the tickets which are open. Unfortunately there is no field in R/3 table which indicates Ticket status. But in BW i have a DSO where i can get the tickets along with their status.
    Now what i want to do is:
    in the Infopackage i want to give the dataselection for ticket, whose status is open which will be calculated in ABAP code by lookup to the DSO. Is this possible?
    I know that in ABAP routine for Data selection we can give single values and range values. but here i just want to give several single values. That means if suppose i have 4 tickets T1,T2,T3,T4 in the DSO and if T1 and T4 are open tickets, then i have to get the data from R/3 just for T1 and T4.
    in the above case if we use range then the low and high values in the range will be T1 and T4 respectively and the data pulled from R/3 will be from T1 - T4 ie all T1,T2,T3 & T4. but i need just T1 and T4.
    Please share your ideas. also please send the code as i am not an ABAPer.
    If Several single value selection is not possible at least send the code for the range values.
    Thanks,
    Cnu.

    you can write a code like this in the ABAP routine in data selection in front of ticket characteristic
    types: Begin of s_ticket,
         ticket type <type of ticket characterisitcs>,
          End of s_ticket.
    data: l_idx like sy-tabix,
          wa_ticket type s_ticket,
          it_ticket type standard table of s_ticket,
          l_s_range type rsrdrange.
    You can declare
    read table l_t_range with key
         fieldname = '<your field name for ticket>'.
    l_s_range-infoobject = '<infoobject name>'.
    l_s_range-fieldname = '<field name of ticket cahracteristics>'.
    l_s_range-sign = 'I'.
    l_s_range-option = 'EQ'.
    select * from <ODS active table> into table it_ticket where status = <value for open status>.
    if sy-subrc = 0.
         loop at it_ticket into wa-ticket.
              l_s_range-low = wa_ticket-ticket.
              append l_s_range to l_t_range.
         endloop.
    end if.
    p_subrc = 0.
    you need to modify it as per your requirements, i hope this might help you.

  • Fixed time interval selection in Infopackage

    Hi Guys,
    I have a generic data source from PA0315 table that I am using to supply master data 0EMPLOYEE. In the update tab of the infopackage it has a fixed time interval selection with Start Date and End Date. I enter 01.01.1900 to 31.12.9999 so that I can capture the entire data for every load.
    But when ever I enter that selection option it always returns with '0' data. But if I enter specific date ranges it returns with data. But being specific does not help me b/c I want the entire date range.
    Has anybody come across this before and have an idea on a solution to capture all the data.
    Any response will be appreciated.
    K.

    Hi,
    I'm facing a similar problem. I would really appreciate if anyone can help in this regard.
    We have a table in R/3 which has time-dependent data. For example, for a single OBJID we could have multiple records with different BEGDA/ENDDA. When we try to load this data into BW InfoObject, we see a time-dependent data selection in update tab of infopackage. We need to select BEGDA/ENDDA since otherwise during loads we would get a "DUPLICATE RECORDS" load error in BW.
    The problem is when we enter a Fixed-time interval Start Data and End Date in the InfoPackage, only the records with that StartDate and EndDate are loaded. Ideally I would want to see all the records whose BEGDA/ENDDA falls in the range of StartDate and EndDate.
    I tried modifying the ROOSFIELD table for the data source. I made the BEGDA SELOPTS as GE(16) and ENNDA SELOPTS as LE(64). But still it doesn't seem to work. I tried the same in RSA3. Unless we give a range for BEGDA it doesn't seem to behave as expected. Could someone let me know how I can load all records to BW whose BEGDA/ENDDA fall in the range of StarteDate and EndDate.
    Thanks,
    Anil

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

  • Init Load and RSA3

    I have carried out a transport to Q/A and part of the transport included an Init InfoPackage which was created on Development.  I have used this package to schedule an immediate Init load.  It is not extracted anything so far but should have, could this be because the package was created on Development?  If so how do I resolve.
    As a test I went to RSA3 to see if I could carry out a test extract, nothing is being extracted in the sense that the process is still running, could this be because I am extracting on B/W or is there no relationship in that sense? Thanks

    Hi,
    First of all, count the entries in setup table MC11VA0ITMSETUP, if it has zero records then fill the set up table using tcode OLI7BW.Execute the job in back ground here. And also select the termination date in future.
    Do not start the execution of Info package till the job is completed for filling the set up table.
    With rgds,
    Anil Kumar Sharma .P

  • Init load very long runtime 0CRM_COMPLAINTS SALES Analyses

    Hi,
    We have launched a init load (infopackage 0CRM_COMPLAINTS)(BI 7.0) which extract 180201 claims from our CRM 2007 system.
    The first packet (data package size 5000 records) have been extracted in 5minutes, but when it begins the 10 packets, it last 20min and 30 between each of them.
    This treatment lasted 12 hours (we don't see optimization point at the moment)
    The first thought is to decrease packet size but I don't find specific note about this problem, or any lead.
    Any help will be grateful.
    Chris

    HI
    you check the SAP Note 692195 - Question 1 ( shown below )
    Question 1 : The Extraction from CRM to BW takes a very long time. What can be done? (Performance Issues)
    Suggestion 1: Please implement notes  653645 (Collective note) and 639072(Parallel  Processing).
    The performance could be slow because of the wrong control parameters used for packaging.
    You can change the package size for the data extraction.
    Also note that changing the package size in the transaction SBIW would imply a change for all the extractors. Instead, you could follow the path in the bw system.
    Infopackage (scheduler)    > Menu 'Scheduler'   > 'DataS. default data transfer'   > maintain the value as 1500 or 1000(This value is variable)
    The package size depends on the Resources available at the customer side (The no of parallel processes that could be assigned = 1.5 times the no of CPU's available approx.)
    Regards,
    Sathya

Maybe you are looking for