Restrictions in DataSource 0CRM_COMPLAINTS_I

Hi,
We are working with standard DataSource 0CRM_COMPLAINTS_I.
I've found out that it extracts only items with following OBJECT_TYPEs:
BUS2000160, BUS2000161, BUS2000162, BUS2000165 and BUS2000167.
But we need to upload all items.
When I'm trying to change this list in BWA1 (in tab "Selection Conditions") it doesn't help.
Is it possible to change restrictions without changes in standard SAP code (in mapping module CRM_BW_COMPLAINTS_I_MAP)?
Is there any reason for these restrictions? Why 0CRM_COMPLAINTS_I doesn't extract all items?
Thanks in advance,
Natallia

Adding object types to the selection conditions should help.If that doesn't work, try creaeting new Z Data Source withe Z Extract FM.

Similar Messages

  • Start routine 3.x  - 7.0

    Hello people,
    I'm working on DSO 0CRM_COM2 in BI 7.0.
    I created a transformation between DataSource 0CRM_COMPLAINTS_I and this DSO.
    I'm using the "same" routines used in standard update rules (3.x).
    But the start routine needs g_s_minfo-upmode, which seems to have disappeared in 7.0.
    So which is the corresponding field to upmode in BI 7 ?
    The code is the following one :
        DATA: lv_fsname(60)   TYPE c.
        FIELD-SYMBOLS: <fs_gsminfo> TYPE ANY.
        lv_fsname = 'g_s_minfo-updmode'.
        ASSIGN (lv_fsname) TO <fs_gsminfo>.
        IF <fs_gsminfo> = 'F'
        OR <fs_gsminfo> = 'C'.
          REFRESH source_package.
        ENDIF.
    Cheers,
    Vince.

    Hi Vince,
    this is actually a very interesting question. First of all I would not recommend to migrate this DataSource.
    Second, the field that the 3.X business content is using to determine the info what kind of load is processed is not available in 7.0 anymore.
    You know that we have now the InfoPackage that can handle init/delta and full uploads to the PSA and we have the DTP that can distinguish between a full and a delta from the PSA in the InfoProvider. We do not have a INIT for DTP's anymore. This makes it now a bit complex. Even if you load via full into the PSA, it would be a Delta for the DTP.
    Please have a look into my blog. I describe which info is available during the transformation.
    SAP NetWeaver 7.0 BI: Get runtime information of a Data Transfer Process (DTP) in a Transformation
    I would say there is no easy solution to determine in the transformation how the data has been loaded into the PSA. Do you kow why this is info is necessary?
    Best Michael

  • Load to ODS - Data missing

    Hi experts,
      I'm very new to BW. I have a problem which I hope you can help.
      I'm extending a Business Content structure (datasource = '0CRM_COMPLAINTS_I')with a character datafield of 60 chars (using append structure and modify user-exit EXIT_SAPLRSAP_001). From CRM, my extract checker RSA3 works fine, the new datafield is populated with the text as expected. On the BW side, I have done everything I can think of to the target data ODS (replicate Datasource, transfer structure, etc etc) but when running the extract, the new datafield is not populated at all (all the other existing datafields in the structure are populated, except this new datafield I'm adding).
      Please can someone tell me what I have done wrong ?
    Many thanks,
    Ruong

    Hi Ruong,
    Debugging is an option ...but as u have said the field does not appear in the PSA..? The filed is not getting replicated is it??
    As suggested above, please do check the mapping of the new field in the transfer rules side...
    also plz check that the field is not set to No Update in the update rules ..shouldnt be a problem as the field does not appear in the PSA.
    We just solved a similar issue yesterday,and it was the new fields were set to no update in the update rules of the ODS.
    Well....U can do the debugging in the following way..
    In the monitor ...choose ur data load ...select the details tab...right click on the data package row in the transfer or in the processing row and select simulate update.
    U can then select the checkbox activate debugging in update rules.
    Regards,
    Marc.
    Message was edited by: Marc

  • Memory overflow in RSA3 but not in FM on which datasource created

    Hi
    I am getting the short dump in the generic datasource extraction ( To extract CDPOS and CDHDR data) which is based on a FM. when i directly execute the FM its not giving any dump and giving me correct data, but when execute through RSA3, it gives following error. Please help me how can i correct this ?
    STORAGE_PARAMETERS_WRONG_SET and TSV_TNEW_PAGE_ALLOC_FAILED errors
    Below is the code, highlited is the code which is giving problem.
    Declaration
          OPEN CURSOR WITH HOLD S_CURSOR FOR
          SELECT MANDANT OBJECTCLAS OBJECTID CHANGENR USERNAME UDATE FROM CDHDR
                 WHERE OBJECTCLAS EQ 'EINKBELEG'
                   AND OBJECTID IN L_R_OBJECTID
                   AND UDATE    IN L_R_UDATE.
        FETCH NEXT CURSOR S_CURSOR
               APPENDING CORRESPONDING FIELDS
               OF TABLE IT_CDHDR
               PACKAGE SIZE S_S_IF-MAXSIZE.
        IF SY-SUBRC <> 0.
          CLOSE CURSOR S_CURSOR.
          RAISE NO_MORE_DATA.
        ENDIF.
        S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
      ENDIF.
    **************HERE IS SYSTEM GIVING DUMP
       SELECT * FROM CDPOS INTO TABLE IT_CDPOS
      FOR ALL ENTRIES IN IT_CDHDR
      WHERE OBJECTCLAS EQ IT_CDHDR-OBJECTCLAS
        AND OBJECTID EQ IT_CDHDR-OBJECTID
        AND CHANGENR EQ IT_CDHDR-CHANGENR
        AND TABNAME EQ 'EKKO'
        AND FNAME   EQ 'FRGZU'.
    **************HERE IS SYSTEM GIVING DUMP
    Further Processing
      LOOP AT IT_CDPOS INTO WA_CDPOS.
        READ TABLE IT_CDHDR INTO WA_CDHDR
         WITH KEY OBJECTCLAS = WA_CDPOS-OBJECTCLAS
                  CHANGENR = WA_CDPOS-CHANGENR
                  OBJECTID = WA_CDPOS-OBJECTID.
        WA_DATAPACKAGE-MANDANT = WA_CDPOS-MANDANT.
        WA_DATAPACKAGE-OBJECTCLAS = WA_CDPOS-OBJECTCLAS.
        WA_DATAPACKAGE-OBJECTID = WA_CDPOS-OBJECTID.
        WA_DATAPACKAGE-CHANGENR = WA_CDPOS-CHANGENR.
        WA_DATAPACKAGE-VALUE_NEW = WA_CDPOS-VALUE_NEW.
        WA_DATAPACKAGE-VALUE_OLD = WA_CDPOS-VALUE_OLD.
        WA_DATAPACKAGE-USERNAME = WA_CDHDR-USERNAME.
        WA_DATAPACKAGE-UDATE    = WA_CDHDR-UDATE.
        APPEND WA_DATAPACKAGE TO E_T_DATA.
        CLEAR: WA_DATAPACKAGE,WA_CDHDR,WA_CDPOS.
      ENDLOOP.
    ENDFUNCTION.
    Edited by: Tripple k on Oct 21, 2010 6:07 PM

    Hi Rahul
    I restricted to 1 data call and 1 record per call in RSA3, still i am getting the same problem.
    Regards
    Kamal
    > Hi,
    >
    > When your execute through RSA3, there is a limit to the number of records that can be held in the memory while extraction. So it may go for these dumps. You may restrict the number of records by changing Data Records / Calls & Display Extr. Calls while running RSA3.

  • 0HR_PT_1 Datasource doesnot extract New employees in Delta Load

    Hi Gurus,
    I did an initialization of delta based on Company code selection and calendar month range (01.2008 to 12.2009) in the month of Aug-09 around 60million records came into BI.The dataload was successfull (Info yellow but made into green). After that when the new employees created in ECC for these emplyoees there is no data being extracted through 0HR_PT_1 datasource.
    Gone through the following notes
    Note 670751 - Time management extractors and new employees
    This talks ablut selection range for Personnel Number which i have not given at the time of init. But now already data is there in BI and it will take hell out of time. Its not sure even though we did init selection with peronal Number ranges 10 years data is coming into BI.
    Note 353177 - Long-run. progr. at time data extrct. in delta mode
    This note talks about time frame which itself is a confict with the infotype 0439.
    Please suggest how to minimize the successfull initialization of delta with out missing the new employees workschedule data.

    If u click the 'Documentation' icon at the IMG node, u can see the following
    Define Time Frame for Transfer
    In this step, you define the time frame used to select time data for reports in the Business Warehouse. Only time data entered for a date or period within this time frame is transferred to BW.
    The time frame you specify is activated when you
    Request data for initializing the delta transfer
    Request the delta since the last request or repeat the delta request
    Transfer all requested data and do not restrict the required period in BW.
    Example
    1. You regularly use BW to gain an overview of the current calendar year.
    You enter January 1, 2001 as the earliest transfer date and December 31, 2001 as the latest transfer date. At the start of the next year, you set the dates forward one year.
    2. You want to have regular access to the current data. You also want to take account of time data that has changed in the last six months. You are also interested in absences that have been recorded for future periods.
    You therefore set the earliest transfer data to six months ago and the latest transfer date to six months in the future. Each month, you set the dates forward one month.
    Recommendation
    Make the time frame as small as possible to avoid unnecessarily long runtimes, and as large as necessary to transfer all relevant data.
    Activities
    1. Choose the Check Feature TIMMO activity.
    2. Check the modifiers specified. If you want to use special modifiers for BW, adjust the feature accordingly.
    3. Choose the Earliest Transfer Date activity and enter the date up to which
    a) Data is to be selected (when you request all data)
    b) All changes made after the last request are to be selected (for a delta request)
    4. Choose the Latest Transfer Date activity and enter the date up to which data entered for the future is to be selected.
    5. Note these activities (outside the SAP system) for your periodical activities so that you can update the time frame monthly or annually, for example.

  • How to restrict number of Data Records from Source system?

    Hi,
    How can I restrict the number of Data records from R3 source system that are being loaded into BI. For example I have 1000 source data records, but only wish to transfer the first 100. How can I achieve this? Is there some option in the DataSource definition or InfoPackage definition?
    Pls help,
    SD

    Hi SD,
    You can surely restrict the number of records, best and simplest way is, check which characteristics are present in selection screen of InfoPackage and check in R3, which characteristics if given a secection could fetch you the desired number of records. Use it as selection in InfoPackage.
    Regards,
    Pankaj

  • How to restrict number of rows display using ig:gridView

    Hi
    All
    How to restrict number of rows display using <ig:gridView datasource="{mybean.mylist}">
    i am getting 10 rows using data_row . i wanna show only first 5 rows .
    pageSize ="5" will be ok . but it displays remaining rows in next page. but i want to display only first 5 rows . is there any attribute to restrict number of rows.
    thanks
    rambhapuri

    I have no idea which component you're talking about. If want to discuss here about a non-Sun JSF component, then please mention about the name, version and build in detail. You can also consider posting this question at the website/forum/mailinglist of the component manfacturer rather than here. At least I can tell you that the Sun JSF h:dataTable has the 'rows' attribute for that. I can also suggest you to just take a look in the TLD documentation of the component in question. There should be all possible attributes listed with a detailed explanation about the behaviour.

  • Datasource error- while activating it- warnings occured

    Hi experts,
    I'm using the standard BC datasource 3FI_SL_7R to load the data into the cubes 0rtl_c01 & 0rtl_c03.
    while activating the data source in the R/3 the system displayed the below warnings:
    "Generating DataSource 3FI_SL_7R"
    "Delta process ABR for DataSource 3FI_SL_7Rrequires a cancellation field"
    by ignoring them i configured the whole data flow, but while i scheduled the data for extraction it showed the following errors in the monitor error message:
    "The extraction program does not support object"
    I again activated the function module, extractor and the datasource(again with warnings), and done the whole thing once again but i came across the same error in the monitor.
    Does any one have a solution for this PLZ HELP ME.
    UR HELP WILL BE HIGHLY APPRECIATED.
    thanks & regards

    Hi
    Here is the following note:
    Symptom
    You want to use the delta mode for the BW extraction of total record data from FI-SL or EC-PCA.
    Other terms
    0EC_PCA_1, 3FI_SL_
    Reason and Prerequisites
    Note the following prerequisites and restrictions:
    This note only applies to totals record DataSources.
    The R3 Release must be 4.0B or higher.
    The delta method is currently only available for actual data.
    The delta method uses the same transfer structure as the full upload, that is, only totals record fields are transferred.
    The BALANCE field of the transfer structure is not filled. To get the non-cumulative for balance sheet accounts, you can either create a non-cumulative value in the BW System, which is updated via values DEBIT/CREDIT, or accumulate the transactions of period 0 to n in the query definition.
    You must use the online through-posting for balance sheet accounts. You can create a separate InfoPackage that works in the full upload for balance sheet accounts that are transferred periodically.
    The line item update must be active for currency conversions in the FI System.
    Deleting transactions are not connected to the delta method:
    a) Periodic CO data transfer (transaction 0KE0) (use transaction 1KEA instead because this transaction cancels the data instead of deleting it).
    b) Rollup
    c) Delete transaction data (transaction 0KE1)
    d) Modification of SAPFGVTR balance carryforward program (transaction GVTR):
    After you implement the modification from note 182201, the ZZVTR001 delete program used there is not connected for the carryforward balances (TSLVT, HSLVT, KSLVT fields and so on).
                  This means:
                  Do not use these transactions if a delta method is initialized for the same selections because the deletion is not updated for the BW system.
                   If you absolutely have to use one of the transactions or you have used one of them by mistake, you must delete the initial requests and delta requests from the InfoCubes in the BW system and you must restart the delta method with an initial upload.
    Posting is not allowed during the initial upload. You must take organizational measures to make sure that no posting takes place at that time because there is no corresponding system check at present.
    If the delta method was initialized for a source system, you must regularly schedule a delta upload so that the delta queue does not overflow. If you want to stop the delta method you should also delete the initialization. You can display the delta queue in the source system via transaction RSA7.
    Enter the selection for the actual data in the information package (0VTYPE = 010). Planning data can be transferred with another InfoPackage in the full upload.
    Solution
    The solution is contained in the standard version as of Release 4.7A. The solution may be implemented in advance for lower releases:
    To activate the delta method for DataSource 0EC_PCA_1 and for 3FI_SL_* generated totals record DataSources, you must perform the following steps in the OLTP:
    Caution:
    Steps 1 and 2 are delivered in Support Packages with note 485264 and no longer have to be executed with the corresponding Support Package status.
    1. Create the following function modules in accordance with the correction instructions:
    a) OPEN_FI_PERFORM_00005030_P in function group BFFM2 (4.0B - 4.5B)
                               or in function group BFFM3 according to note 450079 (4.6B - 4.6C)
    b) OPEN_FI_PERFORM_00005040_P in function group BFFM2 (4.0B - 4.5B)
                               or in function group BFFM3 according to note 450079 (4.6B - 4.6C)
    c) SAMPLE_PROCESS_00005030 in function group BFFMSMPL2 (4.0B - 4.5B)
                                                     in function group BFFMSMPL3 (4.6B - 4.6C)
    d) SAMPLE_PROCESS_00005040 in function group BFFMSMPL2 (4.0B - 4.5B)
                                                     in function group BFFMSMPL3 (4.6B - 4.6C)
    and create the following data elements using transaction SE11:
    e) PR00005030
                  Text: Open FI process 00005030
                  Domain: XFELD
    f) PR00005040
                  Text: Open FI process 00005030
                  Domain: XFELD
    2. Add the following entries to table TPS01:
    PROCS INTERFACE Text1
    00005030 SAMPLE_PROCESS_00005030 BW delta extractor PCA FI-SL
    00005040 SAMPLE_PROCESS_00005040 BW delta extractor PCA FI-SL
    3. Implement the remaining corrections in accordance with the correction instructions in reports:
    a) FGIDBF24
    b) FGVTRF20 (up to and including Release 4.6B)
    c) RGUGVTR0 (up to and including Release 4.6B)
    d) and in function module G_BIW_GET_TRANSACTION_DATA (except for Release 4.0B)
    4. Regenerate the update modules
    a) Execute report SAPFGIDB using transaction SE38 with process type 1
    b) Execute report RGUGVTR0 using transaction SE38 (up to and including Release 4.6B)
    5. Implement the corrections from note 325824 (only Release 4.6C)
    6. Execute report GBIWDGEN by using transaction SE38 (you must implement note 407091 beforehand up to and including P2001.1)
    7. Change the data record in table ROOSOURCE for OLTPSOURCE = 0EC_PCA_1 and OBJVERS = A in field DELTA to 'ABR'. This may be done using report ZPCA_DELTA_FOR_0EC_PCA_1. Follow the same procedure for an FI-SL totals record DataSource.
    As of PI 2003.1, the delta mode 'ADDD' is used instead of 'ABR'; an indicator is also set in the T881IS_PI control table. If you have installed Plug-In Release 2003.1 or higher, use the attached ZGBIWPI_DELTA report instead of the ZPCA_DELTA_FOR_0EC_PCA_1 report.
    8. Replicate the DataSource in the BW System and activate it.
    Import the changes into the production system via transports and then perform steps 4, 6, 7 and 8 again.
    You will have to repeat step 6 again if you encounter problems after the Plug-In upgrade.
    When you upgrade the source system to Release 4.7, discard the modification of reports FGIDBF24, FGVTRF20 and RGUGVTR0 during the data comparison and use the delivered version of these programs. If you use this note for FI-SL DataSources, call transaction BW03 once and accept the conversion of the DataSources in the dialog box that appears. If you do so, an initialized delta method will continue to run successfully even after you upgrade the source system.

  • Flat File Hierarchy Datasources

    We are creating several flat file hierarchy datasources. The datasources will be maintained in an external database.
    I am familiar with the creation of flat file datasources for master and transactional data, but don't have good documentation for how the external flat file hierarchy is to be formatted.
    We have reviewed the 2004 Netweaver Document "How to Download Hierarchies in BW" and have used the program referenced there, Z_SAP_HIERARCHY_DOWNLOAD, to download our hierarchies to then test the upload.
    However, this has not worked.
    Does anyone have the record layout that the flat file must be in to upload a simple 2-level hierarchy (for example groupings of 0vendor)?
    Thanks, Doug

    I think the URL you mention is http://help.sap.com/saphelp_nw04/helpdata/en/fa/e92637c2cbf357e10000009b38f936/content.htm.
    This contains the record layout instructions as follows.
      5.      Maintaining the hierarchy:
    Choose Hierarchy Maintenance, and specify a technical name and a description of the hierarchy.
    PSA Transfer Method: You have the option here to set the Remove Leaf Value and Node InfoObjects indicator. As a result, characteristic values are not transferred into the hierarchy fields NODENAME, LEAFFROM and LEAFTO as is normally the case, but in their own transfer structure fields.  This option allows you to load characteristic values having a length greater than 32 characters.
    Characteristic values with a length > 32 can be loaded into the PSA, but they cannot be updated in characteristics that have a length >32.
    The node names for pure text nodes remain restricted to 32 characters in the hierarchy (0HIER_NODE characteristic).
    The system automatically generates a table with the following hierarchy format (for sorted hierarchies without removed leaf values and node InfoObjects):
    Description
    Field Name
    Length
    Type
    Node ID
    NODEID
    8
    NUMC
    InfoObject name
    INFOOBJECT
    30
    CHAR
    Node name
    NODENAME
    32
    CHAR
    Catalog ID
    LINK
    1
    CHAR
    Parent node
    PARENTID
    8
    NUMC
    First subnode
    CHILDID
    8
    NUMC
    Next adjacent node
    NEXTID
    8
    NUMC
    Language key
    LANGU
    1
    CHAR
    Description - short
    TXTSH
    20
    CHAR
    Description - medium
    TXTMD
    40
    CHAR
    Description- long
    TXTLG
    60
    CHAR

  • How to restrict erroneous material in 0MAT_SALES_LPRH_HIER in BW 3.1

    Hi Friends,
    There is one erroneous material which has junk characters in it. It has been marked as deleted in R/3. But still that material is getting pickedup into BI when I am doing full load for 0MAT_SALES_LPRH_HIER hierarchy datasource in BW 3.1. I have to restrict this material in 3.1 while loading the data. I have no other option other than restricting this in 3.1. Kindly suggest me if there is any option to achieve this.
    Regards,
    Steve.

    You can try Infopackage ABAP Code, to exclude the Material while doing a full load.
    Make sure the Material is a selection criteria for the extractor, then in selection  screen choose option '6' and write a code to exclude the material while doing the full load.
    Deepak

  • How to make Management of row level restrictions easy for webi reports?

    Hi all
    Our BO Product version is 12.3.0.601 (BO 3.1)
    We are applying row level security for webi reports at universe level...
    Since  Universes are more in Number we have to create same restrictions and apply it to the users lets take a restrictions on region....which is common across all universes.
    So the problem lies with the management of restrictions created at universe level.
    Can we have a setup in where we can centralized the restirctions at a place so that management would be easy ......???
    Shall we have to import the roles(restrictions) from R/3 or BW or Database level...?
    Then how we will restrict our report (webi) to a region?????
    So basically webi reports should run with the restrictions lets say region....How we will achieve this?/
    Thanks and Regards
    Ritu Raj

    Hi,
    what is your Datasource?
    If its SAP BW i would highly recommend you use the SAP Authentication in your  BOE XI 3.1 So the users log into BOE with their SAP Username and Password and than the Data restriction of your BW takes place when the users run their Reports.
    Informations on how to confiure the SAP Authentication you will find in the installation Guide of the SAP ITK.
    Regards
    -Seb.

  • How can I know the delta field for CO-PA datasource?

    Hi,folks:
        How can I know which is the field assigned as the delta field for CO-PA datasource,as is noticed in the note that after PI2004 the logic has been turned to general datasource,but I can't find the datasource through RSO2.
        Full points will be given to u.
    Martin Xie

    Dear Martin,
    The CO-PA DataSources generated use a separate time stamp method for the delta procedure. This procedure means that client-independent DataSources in CO-PA are normally restricted to the clients in which they were generated.
    See this link...
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/97/6f4d40cef71059e10000000a155106/frameset.htm
    Also check ROOSOURCE in R3, asmentioned by Dinesh.
    Hope it helps.

  • Selection Criteria in Infopackge for enhanced  field of DATASOURCE in R/3

    Hi All,
    My client requirement is Data has to be loaded on company wise .. means the respective responsible person only carryon loading person as per his profile(Authorisation)load has to be happen...this is one requirement,
    one more is (whether in this scenario can we go for Delta)
    we enhanced the Datasource with new field in R/3 and when we are trying to make it selction condition in infopackage we are not getting filtering as per that ..
    could u or anyone who knows through a light on this..
    Thanks in advance
    BRB

    Hi BRB,
    regarding your question about selection field I gave you an answer in one of yours previous post !
    Just some considerations about your authorizations requirements.
    If I right understood, you want to build a scenario in which there are different persons that, manually, have to access on the system to perform a data loading restricted to a particular company code (so, person A could load only data from company A, person B from company B and so on...)
    I think you can obtain this (also with a dedicated infopackages per person), but if you want to manage a delta (your second question) just remember that you can perform different init (with different selections), but the delta channel will be only one and only one will be your delta request management..so, your previous profiling will no longer make sense...
    Hope it helps.
    Bye,
    Roberto

  • How to restrict plant and companycode

    Hi all,
    My requirement is
    I have few questions on client requirement.
    -     FI (AP/AR/AA/GL) u2013 4 years of data, all open items, for company code 0013, 0022
    -     MM u2013 4 years of data for plants 0013, 0022
    -     COPA data, fiscal year 2010 onwards for operating concern CORP and 0030
    For COPA->Do I have to create 2 separate datasources one for each operating concern?
    How and where to restrict plants for MM?
    How and where to restrict Companycodes for FI?
    Will that be at IP level?
    Thanks all.

    Hi Harika,
    I guess you need to write ABAP routine for multiple Single value restrictions in Infopackage level.
    In Data selection tab, Type(as your requirement is to restrict the plant field with 2 fileds) select the type beside plant and select 6-ABAP Routine --> enter the routine name and write the logic.
    Use this above method as a standard practise. But for your requirement, (since only two plants are involved) you shall use two rows of plant and restrict them.
    If you need further help, feel free to post.
    Hope this helps.
    Regards,
    Guru

  • 0FI_AR_4  datasource is extraction 0 records during Init

    Hi,
    0FI_AR_4  datasource is extraction 0 records during Init. But if I run the Full-load I can get the data.
    I am not sure whether our extractors are uncoupled. 
    Currently we are using GL and AP extractors as well.
    We are on EEC6 and PI_BASIS 2005_1_700
    There were no selection fields defined 0FI_AR_4 to restrict the Init on Fiscal year period/ Company code.
    Not sure whether this note 551044 is applicable for the currect vesion of the component.
    Reagards
    Ajay
    Points will be assigned to all answers.

    Hi Anil,
    Thanks this is useful I have checked TPS31 Table the entry is maintained as described in your link.
    this table doesn't have any entries in it BWOM_SETTINGS ( Do we have entries only after running delta infopackage?
    When I tey to instral the datasource from RSA5
    The get the following error message.
    Units field HWAE2 for field H2STE of DataSource 0FI_AR_4 is hidden
    Units field HWAE3 for field H3STE of DataSource 0FI_AR_4 is hidden
    Units field HWAE2 for field ZLOCAL2 of DataSource 0FI_AR_4 is hidden
    Units field HWAE3 for field ZLOCAL3 of DataSource 0FI_AR_4 is hidden
    it will be great if you can help me out.
    Regards
    Ajay

Maybe you are looking for