Urgent : InfoCube/Dimension

Step 1 :  In development box, the Cube was empty and did the few changes as below
From Dimension1 (already have 4 characteristics)
Deleted 3 characteristics from InfoCube via remodeling toolboox  - Check the scheduled conversion and it was successful
added 1 characteristic to InfoCube manually just by dragging
Checked the dimension table and the changes are reflecting in the dimension table
Step 2 : The InfoCube ZIBSDPR01 moved to Quality
Note : There is data in the quality box
The transport failed returning the Error Code 8
The below text was highlighted in yellow (warnings)
1) Enhancement category for table missing
2) Enhancement category for include or subtype missing
The below text was highlighted in Red (error)
Dimension1 table could not be activated
But the InfoCube structure got changed (showing only 2 chars in dimension1
- (4 of earlier - 3 (of deleted)  +1 (newly added))
Kindly let me know what could be reason for failing the transport request.
Is the error because of manually adding the char by dragging
Any information will be appreciated.
Thanks

DPN,
As you said the reason might be that. But you should remodel using only remodeling toolkit.

Similar Messages

  • Infocube Dimension tables manual modification

    Hi all,
    I have a curiosity: has anyone ever modified manually a dimension table associated with an infocube?
    Supposing a situation where an infocube has the dimension ORDER ATTRIBUTES with the fields "Order type" and "Order reason". Dimension table is valorized with 3 tuples:
    ( TypeA, Reason1)
    ( TypeB, Reason2)
    ( TypeC, Reason3)
    I should substitute the correspondence ( TypeC, Reason3) with the correspondence (TypeD, Reason1).
    I know that it is not the right way to proceed, but I wanted to know if anyone ever faced this issue.
    Thanks all,
    Edited by: Gianluca Maresca on Feb 7, 2008 11:44 AM

    Hi,
    if I understod you correctly you don'T want to change the data model but the content of the dimension table itself. For this you should know that the dimension table is set up like dimid, order type sid, reason sid. The Fact table is jioned with the dimension table. So of course you could change the values of the table with an ABAP (but take care you have to look up the SIDs from the corresponding characterisitcs SID table). The disadvantage nobody knows what has happened and you can get possible errors if you try to reconsteuct the cube or want to rebook a request to the cube.
    The standard and recommended way is to delete the cube content and reload data.
    Regards,
    Juergen

  • Infocube  Dimension Design Help

    Hi All,
    We are working to design an new infoCube.Unfortunately we donot have the luxury to use Line Itme Dimension.So we have decided to use the characteristics in a dimension which are most accessed order.Please suggest a way to find out the most used charactoristic in a dimension
    Regards,
    Ravi

    Hi,
    Out of my knowledge, the only way to see which characteristic is being mostly used is to see the queries on that data target.
    Hope the following points helps you:
    1. The order of characteristics in a dimension does not effect the performance, its the characteristics used in the dimension which effects the performance.
    2. See the relation i.e (1:1, 1: Many, Many:1, Many:Many, etc) between the characteristics in the dimension, and then decide whether to keep all the characteristics in the same dimension or keep them in different dimensions.
    3. Once you know the relation between these characteristics, you can judge, what will be the size of the dimension table if we keep all the characteristics in the same dimension and what will be the size if we keep them in different dimensions.
    4. Also, functionally know why that cube was built? what data this cube holds? what kind of reports are bulit on this cube? How much data will this cube hold? If we have answers for all these questions then you can derive the answer for yor question.
    Regards,
    Sekhar

  • Urgent New Dimension to be added

    Hi All,
    i have to add new dimension to the existing cube using EIS 7.1.2 and SQL server 2005
    IncludeInReport
    Member Names
    NoCloseClaims
    CloseClaims
    IncludeInReport itself is a column and it is having only 0's and 1's.
    and they had given specifications as
    The “NoCloseClaims” member is 0 and matches all records where the “IncludeInReport” column = 0;
    and the “CloseClaims” member is 1 and matches all records where the “IncludeInReport” column = 1.
    please let me know how to create these members in EIS and fulfil these two conditions.
    Is it possible to create members under IncludeInReport?
    Thanks in advance
    prathap

    Asad,
    The other way could be to use the BuPaController to find the values like ROLES, GROUPS etc. from Customizing.
    Use the code below to access the ROLE for a BP.
      DATA: lv_bupacontroller TYPE REF TO cl_crm_ic_bupacontroller_impl.
      DATA: ls_profile TYPE crmc_ic_bpident.
      lv_bupacontroller ?= get_custom_controller( 'BuPaController' ).
      CHECK lv_bupacontroller IS BOUND.
      ls_profile = lv_bupacontroller->get_profile( ).
    The field <b>ls_profile-BPROLE_CREATE</b> has the role which you want.
    Cheers,
    Ankur

  • InfoCube Dimensions

    Hello SDN'ers,
    I have query on cube dimensions.
    I have a cube where 13 dimensions excluding the predefined have been in use.
    I have checked the relevant cube under the program SAP_INFOCUBE_DESIGNS or transaction RSRV to find how the dimensions are maintained.
    Based on that, I have found that two of my dimensions have got ratios 98% and 27% (i.e) above the size of fact table, which is against the thumb rule.
    Now, I am planning to create a new cube to hold data for the next 3 years and maintain the dimensions properly.
    I have found that I cant maintain any of the Infoobjects whihc are grouped under these dimensions as Line item as they are not MASTER Data IO.
    One option which I am thinking about is to pull out some of the InfoObjects from these Dimensions and maintain them under some other Dimensions which is somewhat similar(meaningful) to these dimensions.
    Any suggestions is appreciated.
    Regards,
    Vinoth V

    Master data is updated with SIDs and has no relevances with the size of your cube. All the ratios are mere figure of the transactional data & links it has to make with the respective masters. If you feel there a lot of line items for a particular master, you can choose to mark them as Line items. In the last statement you had inquired on creating similar masters; Yes, its possible if you use the relevant settings during the IOBject creation in RSD1. You have to copy from either the object or if you want to base your infoobject on that data, you must then choose it as reference category. The latter case does not copy M table data.

  • InfoCube with degenerative dimensions

    I have an InfoCube that has a significant performance problem due to a very large (degenerative) dimension.  I am working in a 7.0 SPS 13 environment.  I want to reconfigure the InfoCube dimensions without having to reload the InfoCube from the source system.  Please provide a step by step process for completing this task.  In addition, this InfoCube receives it's dataload from an DSO.  This DSO is huge, and is very slow when utilizing the report to report interface.  So, I believe I should partition the DSO and I believe the only option is a "physical" partition?  I wonder if there is a "logical" partition method similar to what is available for an InfoCube? 
    Thank you so much for your help.

    Remodeling the cube can be done using the remodeling toolbox option - you can search the forums on how to achieve this.
    DSO cannot be logicallly partitioned - you can physically partition the same in the backend using the tablees created in the DB or archive older data out of the DSO if you feel you no longer need the same.
    As for partitioning the DSO - your BASIS DBA should be able to do that.

  • Urgent regarding E & F fact table

    Hi all,
    How and where we find E & F partition fact table having size larger than 30.
    It's very urgent.
    Thanks & Regards,
    Priya.

    Hi,
    You can find the table related to InfoCube by following the below mention naming convention.
    <b>/BI<C OR DIGIT>/<TABLE CODE><INFOCUBE><DIMENSION>
    <C or digit>: C = Customer-defined InfoCube
    Digit = SAP-defined InfoCube
    <table code>: D = Dimension table
    E = Compressed fact table
    F = Uncompressed fact table
    <InfoCube>: The name of the InfoCube without leading digits (if any)
    <dimension>: (only used for dimension tables)
    P = Package dimension
    U = Unit dimension
    T = Time dimension
    0-9, A, B, C = User-defined dimension tables</b>
    And you can find info about the size of infocube:
    Calculating size of CUBE & ODS
    regards,
    Pruthvi R

  • Voyager hangs out when trying to display data from an InfoCube

    Hi experts,
    I'm trying to use Voyager for first time in a new installed environment. From the CMC I've created a connection against a BI InfoCube. Then, I create a new Voyager Workspace based on this InfoCube. All InfoCube Dimensions and Infoobjects are displayed in the left pane. Then I try to drag one of the Characteristics to the right pane, but Voyager seems to hang Showing a message "processing". No data data is displayed, and I can't drag more characteristics or key figures...
    There is any known issue about what could be happening? InfoCube has data and I've already built Universes & WebIntelligence reports based on this InfoCube with success. Then the problem seems to lay on Voyager layer, not in data/OLAP layer.
    Thank you very much!

    Hi
    When Voyager creates the initial data view (i.e. when you drop the first dimension on the cross-tab) it has to go and get all the dimensions, all the hierarchies and all the level zero members of the default hierarchies. Although this isn't a large number of items, there are some circumstances that the API call to SAP, say to get the hierarchies for a particular dimension, takes a very long time. The other tools won't necessarily experience this problem as they are more selective about what initial meta-data they load up. For example, they will only load up the dimensions and hierarchies needed for the query.
    The first step in trouble shooting this will be to profile the calls Voyager makes in the SAP OLAP BAPI to see if there are any of these calls that are taking a very long time. You can profile this either from the SAP end or by turning on the logging for the Voyager data access component.
    If you identify a SAP API call which is taking a long time, you then need to see if there are any messages concerning fixes to such problems. I know there have been fixes to correct calls to get hierarchies in certain circumstances which have been taking too long.
    Reuben

  • InfoCube design - high granularity by inclusion of document level detail

    When considering the inclusion of sales document level detail in an infocube (0DOC_NUMBER/0S_ORD_ITEM), two possible high-level designs come to mind:
    1. Make sales document number/sales order item master data carrying infoobjects and include in infocube as line item dimensions. Activate all necessary characteristic navigational attributes for reporting.
    2. Model infocube dimensions to contain all necessary charactistics for reporting with inclusion of characteristics sales document number/sales order item therefore, fact table will have highest level of granularity.
    Knowing the 'textbook' does not suggest the above designs, has anyone attempted maximum granularity in infocube design with success or otherwise? If successful, has this design outperformed DSO or InfoSet reporting performance?
    Thank you - Brendan.

    Hi Brendan,
    we have implemented both solutions; it all depends on the number of documents. if it is much more than 1 mio; I recommend storing your data in the target; if it is 1 or 2 mio you can have master data (more flexible).
    We have some 4 mio records in 0MAT_PLANT and are starting having performance issues.
    by the way; if you are using ORACLE, NEVER mark a dimension with high cardinality; that doesn't work.
    hope that helps
    Olivier.
    Message was edited by:
            Olivier Cora

  • Inactive Dimension Tables for Cube

    Hi Gurus ,
               I am transporting a cube from one system to another and the transport fails becasue the dimension tables are in active in the target system. Now since this system is read only I cannot manually activate it , last resort I even trioed opening the system and activating it and re transported the transport. I get the same error saying that table /BIC/ZXXXXX is inactive.
    Can anyone help....please....

    hi Sanjeev,
    did you change any dimensions in dev ?
    like delete some characteristics from existing dimension,
    or add new characteristic or move from one to another
    dimension ?
    if so, you may need to delete production data first,
    to avoid this, please change back characteristics to previous dimension, and create a new dimension and add new characteristic to the new create dimension.
    another possibility is database problem, try to search oss note for infocube dimension inactive.
    hope this helps.

  • Delete the dimension data

    Hi Experts,
                   How can we delete the dimension data from RSRV?
    Regards,
    Vali

    Hi,
    Apart from what is said above try this also.
    You can clean-up the dimensions in transaction RSRV with the check -> elementary tests -> transaction data -> Entries not used in the dimension of an InfoCube
    Dimension tables have a huge impact on InfoCube performance. The star schema design works best when the database can assume minimal records in the dimension tables and larger volumes in the fact table.
    Each dimension should be of approximately equal size and that the file size of each dimension should not make up more than 10 percent of the associated fact table.
    You may have performance issues when DIM tables are bigger than the FACT tables  (degenerative dimension). This can happen if you regularly delete data from the cube, because the data is only deleted in the fact-tables and not in the dimensions.
    You can clean up them using the above method.
    Hope it helps.
    Thanks,
    JituK

  • Key Fields, Data Fields, Key Figures and Characteristis, Dimesions & Key Fi

    Hi All,
    Can any one please describe more about the below terms and with the Example....
    Like when we identify which one is Key filelds and Data fileds, how to distingush creating new dimesions (Is it based on user reporting) Key figures in Dimestions...
    DSO/ODS:  Key fields, Data Fields
    InfoCube: Dimensions, Key Figures
    Infoobjects: Key figures, Characteritics
    Regards,
    Prem

    Hi,
    Search through SDN for more information on these concepts,
    Re: ods data fields or key fields?
    Re: Key Fields and Data Fields in ODS
    defining Key -field and data fields
    Regards,
    Mani

  • QuickSizer BI

    hello Gurus
    I want to do the sizing with the quick sizer from marketplace, but i don t have clearly the terms, please send me info about sizing in BI, the help indicates:
    <b>Business Intelligence
    SAP NetWeaver Business Intelligence      Find information about SAP NetWeaver Business Intelligence at  the Service Marketplace -> Business Intelligence, for example information about Performance Tuning.
    User Groups Business Planning
    Planning 1,
    Planning 2,
    Planning 3      Definition
    The general idea is to define user groups which are determined by the number and size of data records they work with and the types of planning functions they execute. If you are not sure exactly how many data are involved, you can take the proposed values, which are  based on internal measurements and customer feedback.
    Specifics for User Groups Business Planning
    Users
          Estimate the highest number of active users per hour. Opposed to other sizing approaches in the Quick Sizer you can arbitrarily include users in a specific group. Normally the user groups reflect the fact that you have power, medium and occasional users (example at "Planning steps per user").
    Planning steps per user
          Estimate the peak number of planning steps per user and hour.
          Example for "Users" and "Planning steps per user"
          A user carries out six planning functions, the first three work on the same set of data (5,000 records), the other ones each work on separate set of 600 records. If this sequence is carried out every 20 minutes, we were faced with 18 planning steps per hour and user.
    Average number of data records per planning step
          A planning step always contains exactly one planning function, for example a formula function. If that planning sequences are used, these cannot be calculated as a planning step, instead the number of planning functions contained must be entered.  The average number of data records manipulated by one single planning step has an impact on the CPU time consumed by a user.
          Example
          In our example we have an average of 2,800 ( = (3 * 5,000 + 3 * 600) / 6) records per planning step.
          Note
              o The term planning step is often understood from a business view, where it means a total run of a planning area. Here, we take a functional perspective.
              o The memory requirement and CPU consumption is estimated on the basis of this data. To determine memory requirements, we assume that there is an average data record length of 1KB.
    Maximum data per planning step
          Estimate the maximum number of data records manipulated by one single planning step.
          Example
          As mentioned above the planning functions work through different sets of data. The maximum number is 5,000 per hour and user.
    Maximum data per user
          Estimate the maximum number of data records a user holds in memory simultaneously. This is needed to estimate the memory consumption of a user.
          Example
          Take the example mentioned above. If the user doesn't leave the transaction, he holds 6,800 (5,000 + 600 + 600 + 600) records in memory. Please keep in mind, that the set of data is the sum of records read and records created
    Comment
    Editing/creating data records is achieved by planning functions or manual planning. We do not differentiate between these two types for sizing, as both of them are used to manipulate data records.
    We only size "User Groups Business Planning". NetWeaver BI server must be sized separately.  However, the sizing result includes the part of NetWeaver BI that is used to deliver the transaction data to "User Groups Business Planning". For sizing the load generated on the NetWeaver BI system by "User Groups Business Planning" we assume that 30% of all executed planning steps access NetWeaver BI. For the remaining 70% of the planning steps we assume that they manipulate data records which have already been read by NetWeaver BI.
    BI Users
    BI-INFO,
    BI-BUSIN.,
    BI EXPERT      Definition
    In NetWeaver BI, we distinguish roughly between user types according to their frequency of activity and the reporting they will normally do.
    Active User Type       Navigation Steps per Hour       This user will predominantly ...
    Information Consumer      1      ... view predefined and static reports
    Business User      11      ... navigate within reports, do slicing and dicing, but usually hit aggregates
    BI  Expert       33 and more      ... run ad-hoc queries with a high probability of full table scans
    A navigation step includes drilling down in the reports and corresponds to nine dialog steps in the SD benchmark. If you don't know the user distribution, a typical ratio in the NetWeaver BI environment is 71% : 26% : 3% (Information Consumer : Business User : BI Expert).
    Comment
    The system automatically calculates the Java parts which are shown at the result level.
    If BI Java is not used, you should add 5 % to the SAPS of the application server.
    User Groups Reporting & Analysis
         Definition
    Collection of a selection of characteristics and key figures (InfoObjects) for the analysis of the data of an InfoProvider. A query always refers exactly to one InfoProvider, whereas you can define as many queries as you like for each InfoProvider.
    For sizing purposes we distinguish between three query types which are defined by the load they create in the system.
    Report Viewing: Predefined, static, reports using optimal aggregates
    OLAP Analysis: Slicing and dicing, navigating in reports, using various aggregates
    Data Exploration: Data mining, that is ad-hoc reports with unpredictable navigation paths, access of detail data, full table scans
    Any user can do any type of query. However, experience shows a certain activity pattern, as you can see in the table below.
    Query Type       Report Viewing      OLAP Analysis      Data Exploration      Total Percent
    Information Consumer      80%      20%      0%      100%
    Business User      50%      50%      0%      100%
    BI Expert       0%      0%      100%      100%
    Data Upload
    UPLOAD      Definition
    In this section you can specify how many records you need to upload within your peak time interval.
    InfoCube
    INFOCUBE
    IC-APO
    IC-CO
    IC-CRM
    IC-FI
    IC-HR
    IC-MM
    IC-PP
    IC-PS
    IC-SD
    IC-SEM
         Definition
    The central objects upon which reports and analyses in NetWeaver BI are based, are called InfoCubes. An InfoCube describes (from a reporting point of view) a self-contained dataset, for example, of a business-orientated area.
    An InfoCube has a particular type:
    BasicCube which is a collection of relational tables arranged according to the star schema: A large fact table in the center, surrounded by several dimension tables.
    MultiCube which is based on the basic cube. It combines data from several BasicCubes/RemoteCubes, and brings it together into one context. The MultiCube itself does not contain any data; its data comes exclusively from the BasicCubes it is based on.
    RemoteCube to carry out reporting using data in external systems without having to physically store transaction data in NetWeaver BI.
    Only BasicCubes physically contain data on the database. MultiCubes and RemoteCubes simply display logical views of a dataset. The InfoCube type is not important, as far as reporting is concerned. A query definition always refers to one InfoCube. The difference between the InfoCube types becomes important at the point when you select data for the query.
    InfoCube types: From the list below you can choose additional InfoCubes, just take the information and fill it in the questionnaire.
    Long Text      Short Name      Cube name      Dimensions      Key Figures      Length
    Aerospace & Defense      A&D      0AD_C01      6      2      94
    Apparel and Footwear      AFS      0AFMM_C01      8      48      896
    Automotive           0AUPPC_3      12      11      307
    Business Planning and Simulation           0SEM_C09      5      14      288
    Category Management           0CM_C07      7      34      648
    Consumer Products Industry      CP      0CP_PURC1      8      52      964
    Distribution Channel-Specific A           0CRM_CTI2      3      16      302
    E-Analytics           0WEB_C01      12      5      205
    External Market Data           0DB_MC01      9      5      175
    Financials Management & Control           0FITV_C02      12      13      341
    Healthcare           0HC_C01      9      16      362
    Insurance           0IS_CS_C1      9      8      226
    Inventory Management           0COPC_C04      7      6      172
    Investment Management           0IMFA_C02      7      3      121
    Marketing           0CRM_MC05      12      43      851
    Marketplace           0MA_OP_C1      9      13      311
    Media Enterprises           0MEMAMC04      11      16      382
    Mobile Sales      MSA      0MSA_C05      8      6      182
    Oil & Gas      Oil & Gas      0OI_SSC01      9      16      362
    Personnel Management           0PACM_C01      10      17      389
    Point of sale      POS      0RT_C06      9      33      651
    Retail - Logistics           0RT_C41      7      183      3181
    Sales and Distribution Analyses           0CSAL_C09      12      29      613
    Service           0CRM_PRI      14      47      939
    Strategic Enterprise Management      SEM      0SEMPA_C2      13      68      1286
    Strategic Enterprise Management           0SEM_MC01      6      9      213
    Traffic Analysis           0MA_C02      15      21      507
    Treasury      TR      0TRCM_MC1      6      2      94
    Utility Company           0UCSA_C01      12      20      460
    Specifics for InfoCubes
    Dimension
          A grouping of those evaluation groups (characteristics) that belong together, as regards contents, in one generic term. With the definition of an InfoCube, characteristics are summarized into dimensions in order to store them in a table of the star schema (dimension table). An InfoCube has no more than 16 dimensions, of which three are standard (package, time, unit) and included in the sizing by default. You can therefore enter only 13 dimensions at most.
    Key figures
          Values or quantities, such as sales revenue, fixed costs, sales quantity, or number of employees.
          In addition to the key figures saved on the database, you have the option of defining derived (calculated) key figures in the query definition in the Business Explorer. Such key figures are calculated using a formula from the key figures of the InfoCube.
          Examples of derived key figures are "sales revenue per employee" (sales revenue divided by number of employees), "variance as a percentage", or "contribution margin".
    Initial load & periodic load
          Initial load: Specify the estimated number of records which you plan to load into the cube initially.
          Periodical load: Specify the estimated number of records which are loaded in your periodical upload process. You should take into account that you upload data volume grows with time.
    Number of periods
          Specify the total number of uploads which will be kept in the InfoCube. Example: if you want to keep weekly data for 5 years, you should enter 260 (52*5)
    Short text
          If you have several different InfoCubes of the same type, use short text to attribute names in order to identify them more easily.
    DataStore Object
    DS OBJECT      Definition
    A DataStore Object serves to store consolidated and debugged transaction data at a document level (atomic level). It describes a consolidated dataset from one or more InfoSources. This dataset can be analyzed with a BEx Query or InfoSet Query.
    A DataStore contains a key (for example, document number/item) as well as data fields that can also contain character fields (for example, order status, customer) as key figures. The data of a DataStore Object can be updated with a delta update into InfoCubes and/or other DataStore Objects in the same system or across systems.
    In contrast to multi-dimensional data storage with InfoCubes, the data in DataStore Objects is stored in transparent, flat database tables.</b>

    Hi,
    BPS ;- Here you need to decide if you r really going to use this...If your are not going to use Business planning and simulation then skip this part.
    In case of no. of users ....Take information from your client that how many no. of users will be there and then distribute these user as per gide lines given by sap. ( In quick sizer this help is available on market place )
    Then decide which modules u r going to take in BW.
    ( In our case BW implementation is limited to SD, FI and CO. )
    After this talk to your functional people and decided how many records will be generated per day for each module and for each functionality.
    This is required to decide disk space.
    Then list down all the infocubes and ods which are installed count dim. and key fig. for each cube. For ods count key fields and data fields.
    Hope this helps....
    Regards,
    Mahendra

  • Line item...Card H

    hi guys,
    while creating infocube dimensions...I found some things I didnot understand...
    1.Line Item Dim
    2.Card H Dim
    what are they and where do we use them in real time....
    thanks and rgds
    Surekha

    Hi
    Line item: This means the dimension contains precisely one characteristic. This means that the system does not create a dimension table. Instead, the SID table of the characteristic takes on the role of dimension table. Removing the dimension table has the following advantages:
    ○ When loading transaction data, no IDs are generated for the entries in the dimension table. This number range operation can compromise performance precisely in the case where a degenerated dimension is involved.
    this can be created when you are creating dimension in infocube.
    select dimension tab in infocube declarationselect creategive 1. description for thatin the same line you find a check box called line itemcheck that-then select assign tabinclude charactertics for that dimension--activate it.
    Cardinality High
    When you select high cardinality for a dimension (usually when dimension table is >20% the size of the fact table), the system depending on the database, will create a different type of index (btrees instead of bitmap), which enhances selection from these structures by queries.
    On your second query, on compression, the requests will be visible in the manage screen, but will not be visible in the cube and data will be compressed/summarised/aggregated). So it will not be possible to delete data from the cube based on request selection.
    Please find an link for SAP Help
    http://help.sap.com/saphelp_nw04/helpdata/en/a7/d50f395fc8cb7fe10000000a11402f/frameset.htm
    Many thanks
    kiran

  • Filter value selection for the query execution

    Dear experts!
    I am working with an input ready query (which is over an aggregation level), and we need to display in the selection variable screen the values for a charateristic from the InfroProvider, not from the Master Data.  I don't mind how to do this, but I need to do it and for the moment it seems impossible.  I've read note 984229 and in there it says that:
    <i>'Only Values in InfoProvider'
    In this case, only values of characteristics that are posted in the InfoCube dimensions or in the DataStore are used for the input value request. This D-mode is valid for InfoCubes or the DataStore as an InfoProvider and for MultiProviders that have only InfoCubes and/or a DataStore as part providers. An exception to this is characteristics that are modeled as a Line Item Dimension. D-mode is not supported for this.</i>
    I am over an aggregation level, and thus SAP says it is not possible with the F4, but I don't mind if I have to code whatever, but I need someway to do this.......
    I need whatever type of solution......I am open to any kind of help you can provide me...... =) please!!!!
    Points will be given to helpful answers
    Thanks and kind regards.
    Cecilia

    Could you please check as per Note 1565809 and make sure the F4 mode is really M mode in each level settings?

Maybe you are looking for