Selection Criteria in Infopackage

Hello,
  Is there a way to use a single infopackage by passing different selection conditions thru' abap routine, for delta init.  We require this as we have to extract data based on the logged-in user.
  Any help is highly appreciated.
Thank you very much,
Raj

Fake Delta means simulate Delta mechanism using Selcetion Conditions in InfoPackage ... So it's up to up the determination of the value data to be loaded: e.g. using FISCPER it's up to you the matter of loading data about 06.2004, 07.2004 ...
You can input Selection Conditions manually, or via ABAP coding in your InfoPackage: for one or more fields you can set "TYPE" = 6 and then write your coding in order to set conditions .... Press "Routine Info" on top of the screen to get more info about.
Hope it helps.
GFV

Similar Messages

  • Navigational Attributes as Selection Criteria in Infopackage?

    Is it possible to use navigational attributes as selection criteria in the infopackage?  I have the MRP cube that only does full loads.  I would like to ONLY load the material type FERT (finished goods).  0MATERIAL has 0MATL_TYPE as a navigational attribute.  I would like to put 0MATL_TYPE in the selection criteria in the infopackage.
    If this is possible, please let me know.  The only other way I have come up to do this is to load in one cube and then use and APD to load into another cube.  I would like to avoid this if possible. 
    Thanks,
    Brent

    Hi there,
    you can try this:
    create a routine in 0material infoobject.
    And put this code in the routine after the part where this appears:
    *       Insert source code to current selection field
    *$*$ begin of routine - insert your code only below this line        *-*
    data: l_idx like sy-tabix.
    read table l_t_range with key
         fieldname = 'MATNR'.
    l_idx = sy-tabix.
    after the *.... delete all the code there and insert this one:
      data: i_table like /BI0/PMATERIAL occurs 0 with header line.
      data: t_range TYPE rssdlrange.
    select * from /BI0/PMATERIAL INTO TABLE i_table
      WHERE OBJVERS = 'A' and MATL_TYPE = 'FERT'.
      clear t_range.
      t_range-IOBJNM = '0MATERIAL'.
      t_range-FIELDNAME = 'MATNR'.
      t_range-SIGN = 'I'.
      t_range-OPTION = 'EQ'.
      LOOP at i_table.
        t_range-LOW = i_table-MATERIAL.
        APPEND t_range to l_t_range.
      endloop.
    p_subrc = 0.
    Save it and execute the InfoPackage. It might take a while to execute the infopackage.
    Diogo.

  • Selection criteria for infopackage using 7.0 datasource

    Is it possible to have selection criteria on  7.0 flat file DataSource ?
    I have selected fields as Key Fields, Set the X in select DataSource  and chosen options of selections permitted, but still my InfoPackage  do not contain criteria for my key fields.  
    If this is possible, please let me know what steps are required?
    Thanks,
    Curt Timmerman

    Hello Curt
    this must be possible. Go to RSA1 and change your flatfile DataSource. On the tab "Fields" you can insert an "X" in the colum "selection". In addition to that, you can also add selection options. After these steps, the selection field should be visible in the infopackage.
    Best regards
    Martin

  • How to change Selection Criteria for a Business Content Data Source

    Hi Experts
    I am extracting data using 0CO_OM_CCA_9 Datasource. I would like to be able to select a range of Company Code (BUKRS) to pull in, but I cannot find a way to make certain fields available as selection criteria. When I go into "Change DataSource", I can unselect fields, and even select certain fields, but the option for most is grayed out.
    How can I make this field available as selection criteria in Infopackage?
    Thanks for the help.

    Its not that simple to enable a new selection for a Business Content Datasource, if its not already provided by SAP. Enabling new fields for selection should be accompanied by corresponding extractor code changes to process those field selections and use those selections throughout the extraction process.
    Solution for your problem would be create a custom extractor with all the logic of standard extractor (function module BWOMD_GET_CTRCSTA1 for 0CO_OM_CCA_9) and extra logic to process the new fields for selection.
    Hope it helps!

  • BW ignores selection criteria in a Infopackage after transport

    Hi all,
    After transporting Infopackages with selection criteria the target system ignores them. If I create further Infopackages on the target system everthing is fine. It seems as if the criteria were not transported but they are displayed. I replaced the criteria, saved the infopackage again but this didn't solve my issue.
    We are using BW 7.0 Level 14.
    Any ideas?
    Many thanks, Dennis

    Hi Srini,
    thanks for your quick repsonse. I am talking about 10 Infopackages. I transported some of them again but always the same issue. I created new infopackages on production and indeed it works but I use them in process chains and therefoe I might change the chains on production. This is something I don't want to do.
    Any other ideas?
    Cheers, Dennis

  • How To Add InfoObject in the Data Selection Tab of InfoPackages in 2004s

    Hi Y'all!
    I would like to ask how to add an infoobject in the Data Selection Tab of the InfoPackage in 2004s.  It says its optional, this definintion of selection criteria for the infopackage.
    My apologies, I don't understand how this is done.  Surely, I would like, however, to understand how to add an infoobject in this data selection Tab of the InfoPackage in 2004s.
    Can any kind soul out there (gurus) please lend me your thoughts?
    Regards,
    Philips

    Hello Rajani!
    Thank you very mcuh for that!  I super appreciate it!  Can you prescribe how I can do this step by step please?  Where exactly in the DS can I locate this "field for selection" option in the DataSource?
    Regards!
    Philips

  • Regarding Selection Criteria features in BI7 Info package maintenance

    Hi,
    In BI7.0, I have to load data from the Business content ODS, 0FIGL_O02 to Customized ODS by restricting the data as per the document types.
    Do we have that feature in BI7, to restrict the data in info package maintenance's selection criteria.Please let me know, when we dont have that feature...where can i apply this restriction for loading one data target to another data target.
    Thanks,

    In BI 7.0 you will be using DTPs to load data from one DSO to the other.  There will be no Infopackages involved.
    You can filter based on Document types in two ways. 
    1.  Build the filter in the start routine of your transformation itself  to delete datapackage whenever document type is not equal to what you want.
    2.  DTPs have a filter button.  When you go in change mode you will be able to choose the infoobjects on which you want to filter.  You can enter the required Document types in the filter here.
    If helpful, assign points

  • Automatic population of selection criteria in Infopakage

    Hi Experts,
    I have a Full Load Infopakage in a process chain that runs daily. I want to automatically populate posting date in the selection criteria of this Infopakage.
    For example:
    If the process chain runs on 20 July'08, then the posting date should be 19 July'08 (system date - 1).
    Currently we have to manually enter the posting date in the Infopakage selection criteria, but our requirement is to populate it automatically using some routine or formula. How can we do this?
    Points will be rewarded.

    Senoy, take a look at the following post
    [Routines in infopackage|Re: Can i interactively input data in a infopackage in a Process Chain?;

  • Change to Selection criteria in Datasource, do we need to re-init?

    Hello all,
    We are planning to change the selection criteria for a datasource, we want the year to be one of the selection criteria so we can load data only for particular years.
    Now this datasource is in production for some time, so once we do this change will we have to re-init the extractor or the delta that is working will keep working fine?
    Please let me know.
    Thanks,

    Hi Kiran
    Its worth mentioning that if its a V3 datasource like logistics then you need to load the setup table with the required data before extraction.
    Also ensure that the measures in your DSO are in overwrite mode unless the year that you are loading does not currently exists in the DSO. (ie. its a new year)
    The Full Repair Request option is under the Scheduler menu on the infopackage.
    Hope this helps. <removed by moderator>
    If you need more help let me know.
    Asif
    Edited by: Siegfried Szameitat on Jun 15, 2009 5:17 PM

  • Complex Data Selection Criteria

    Is it possible to do complex Data Selection Criteria invloving more than one InfoObject in Data Selection tab of the InfoPackage?
    Eg  :
    (Controlling area = 'ABC' and Fiscal Period between 001/2005 & 003/2005)
    OR
    (Controlling area = 'AAA' and Fiscal Period between 004/2005 & 008/2005)
    OR
    (Controlling area = 'XYZ' and Fiscal Period between 003/2005 & 008/2005)
    We are currently planning to use 3 different InfoPackages to do the same and checking if it can be done in 1 InfoPackage.
    Thanks!

    BAPI_IPAK_CHANGE is a good option, but will not give you the flexibility you are looking for as it will change the selection criteria, but will not give you the AND, OR (complex selection)option, that you are looking for. What you will end up havig to do if you follow this route is to call the same selection package 3 times with modified selection criteria for each using BAPI_IPAK_CHANGE, or have to use BAPI_IPAK_CREATE to create the infopack with these selection for every load. This will eliminate all or any delta loading hopes that you may have.
    I feel that infopackage group will work nicely for you and with minimal effort of maintenance in the future.
    Rishi
    Message was edited by: Rishi Joseph

  • Non-capital letters in selection criteria

    hi,
    in infopackage, in selection criteria I want to choose 'j' but not 'J' but system changes it to capital letter in IDoc.
    Does somebody knows how to deal with this?
    Regards,
    Andrzej

    hi,
    your code was almost ok. I used this:
    data: l_idx like sy-tabix.
              read table l_t_range with key
                   fieldname = 'VBTYP_N'.
              l_idx = sy-tabix.
             DELETE l_t_range
             WHERE fieldname = 'VBTYP_N'.
              L_t_RANGE-SIGN = 'I'.
              L_t_RANGE-OPTION = 'EQ'.
              L_t_RANGE-LOW = 'h'.
             append l_t_range.
              modify l_t_range index l_idx.
              p_subrc = 0.
    thanks
    Andrzej
    Message was edited by: Aksik

  • Delta re-initialisation - cannot enter selection criteria

    Hi Brains Trust,
    We have an existing delta load from an SD ODS to a cube.
    Due to corrupt dates we want to start the initilisation again from a particular billing document number.
    We have deleted the existing delta.
    When we go to set up the delta init infopackage it does not allow us to enter any selections (for a full load we can select but when we choose Delta init  the selection options become unavailable).
    Any ideas?
    Peter

    Hello Peter,
    Actually yes, you can't change any selection criteria in a delta infopackage, beacause it automatically keeps the ones from the Init.
    Have you tried to make a Full Repair based on your billing document only ?
    You just have to create an Infopackage Full, and select it as Full Repair in the Menu -> Scheduler.
    It will work fine !
    Regards,
    Mickael

  • Extraction ignores selection criteria

    I am extracting data from Infotypes in R/3.  I only want the current record, i.e., the one whose ENDDA equals infinity, i.e., 12/31/9999. So given thousands of employee records, I only want to extract one per employee.
    In the Selection tab of the infoPackage, I enter a range that covers around 100 employees, for test purposes; and in the field entitled ENDDA, I enter 12/31/9999.
    When I specify these selection criteria in RSA3 as a test in the source system, I get exactly what I specified, my 100 or so records, each one with ENDDA = 12/31/9999.
    But when I run the extraction in BW, it pulls in almost 900 records, with every record for each employee. 
    What can I do to exclude the non-infinity records??
    And why are these records pulled when selection criteria does not specify them?

    Thanks guys for the answers, but I have indeed tried every way possible to enter these selection values, in the first field for ENDDA, and in both the ‘from’ and ‘to’ fields.
    Also, I tried entering 99991231, but hitting the ‘Check’ button reverts it back to the proper format of 12/31/9999; I did check the debugger option while testing it in RSA3, and indeed internally ‘ENDDA’ has the value ‘99991231’.
    I tried starting the infoObject with no PERNR values, with only the infinity date as selection, but the job bombed. Why does it work in RSA3, but not when invoked with an RFC? From BW ?
    I have tried every way possible, and I still get a boatload of records for each employee, when all I want is the one with an infinity date of 12/31/9999.

  • Error "Overlapping selection criteria with DTP" when transporting DTP

    When transporting a DTP from Dev to QA I get the following error in the trasnport log:
    Overlapping selection criteria with DTP DTP_4APJZSGKYQLUQYBCDBWK707JO
    Message no. RSBK019
    Diagnosis
    The selection criteria for the DTP to be activated overlap with the selection criteria of DTP DTP_4APJZSGKYQLUQYBCDBWK707JO in field , for example, with regard to value . Delta transfer from a source object to a target object is only allowed to transfer each record oncce. However, this cannot be guaranteed if two DTPs have overlapping selection criteria with the 'Delta' extraction mode.
    System Response
    You cannot activate the DTP with the current selection criteria.
    Procedure
    Restrict the selection criteria so that they do not overlap with the selection criteria for DTP DTP_4APJZSGKYQLUQYBCDBWK707JO.
    The DTP is a delta process which loads data from one infocube into an DSO. I understand that the error is that it is transporting the Delta parameters (something similar to a Delta initialization of infopackages I suppose) but I don´t how to access the information of the delta (selection criteria) of a DTP.
    Any suggestions? or similar experiences?
    Thanks in advance
    nicolá

    Hello,
    You can modify a parameter to create and modify dtp in Production. Like normally is done with Infopackages. There is no reason to make the changes in Dev in the Infopackages and DTP, and transport to Production. This transports normally cause that kind of errors because the id's are different in Dev, QA and Prod, and it is difficult to change dtp in that way.
    To change the parameter do like this:
    Execute Trx. RSA1 -> Transport Connection -> Tab Object Changeability -> Change DTPA to Everything Changeable.
    Do this in Dev, QA and Prod.
    Regards,
    Jorge Diogo

  • Thread: There are no PSA tables for these selection criteria - RSAODS209

    Hello,
    i'm trying to run an infopackage (0GL_ACCOUNT_T011_HIER_ME_FULL_R3) to load complete upload of hierarchy (0GL_ACCOUNT-HIERARCHIES 0GL_ACCOUNT )  extraction via PSA and then in corresponding info object. The load seems to work fine between ECC and PSA but it doesn't:
    I lok at PSA and the monitor-request-status is RED and the message: "There are no PSA tables for these selection criteria - RSAODS209". 
    these are the messages:
    Processing (data packet): Errors occurred
    Data Package 1 ( 2370 Records ) : Errors occurred
    Update PSA ( 2370  Records posted ) : Errors occurred
    Data save in PSA started
    2370 records written in PSA
    There are no PSA tables for these selection criteria
    I've created a new package only for loading the PSA (not the final object)  but the same error appears.
    I have also see this thread but I have no solution yet...
    There are no PSA tables for these selection criteria - RSAODS209
    thanks for your help!!

    Hi Marcel,
    Check whether you have any RED requests in your PSA--> If so delete them
    Make sure your DS, transfer rules/Transformation are active.
    Also once replicate your DS & activate. Also activate transfer structure. Then try loading.
    Hope it helps!
    Regards,
    Pavan

Maybe you are looking for