Characteristic Relationship - displaying data

Hi All,
I implemented characteristic relationship (through ABAP class) and it is working fine except one thing.
It displays the desired combinations, but also posted data in infoprovider in planning mode, that were suppose to be hidden (according to char. rel. logic).
I set for all the relevant characteristics "characteristic relationship" in query designer....
Any idea what I am doing wrong?
Many Thanks!
Pavel

Hi Pavel,
sorry, maybe your exist does not work in all cases (implementation of the check method).
From your description it seems that you want to control access or maybe only make something not input ready. In the first case use authorization, in the latter use data slices.
When you say 'measures' it is also not clear for me whether you mean 'key figures'. You can not control key figures with characteristics relations, except you are using a characteristic to model key figures (account model). But again, characteristic relationships are a means to control the valid combination in the cube (so to say they define the 'truth' in the cube or what are 'consistent' data records). Data slices are a concept to protect data from being changed (typical example: lock a planning version).
Regards,
Gregor

Similar Messages

  • IP - characteristic relationship/ data slices

    Hi Guys,
    I am very new to IP and would like to have some help regarding the following with some simple example
    1) characteristic relationship
    2) data slices
    3) locking
    Some examples with the above is much appreciated.
    where can i get some good document explaining this ?
    Thanks in advance...

    Hi,
      Please find below the examples for characteristic relationship and data slice,
    1. Characteristic relationship:
                 Consider that you have characteristics called "Country" and "Continent" in your report (also in aggreagtion level).
    You cannot always expect the end user to enter the correct continent for a country. In this case, you can create a char rel
    based on the relastionship between these two characteristics (attribute, hierarchy or relationship data loaded to a DSO),where the source is "Country" and the target is "Continent". So when ever the user enters country and continent the char rel validates the entry based on the reference data (master data, hierrarchy or DSO data) and throws error if it s wrong. Apart from this by creating "With derivation" char rel, you can even derive continent value from country with out the user even entering the value in thye report.
    2. Data Slice:
              Consider that your planning requirement is you need to plan on a monthly basis which is like during current month you caa plan for the next month. In this case all other months except the next month should not be available for planning. In this case you can create a daat slice of type "Selection" where in you select '0CALMNONTH' and then filter it to the variable '0CMONTH' +1
    where in you "Exclude" this selection. So now all the other months except next month at any point of time will be disabled for planning.
    You can go through the following links for your reference,
    Char rel - [http://help.sap.com/SAPHELP_NW04s/helpdata/EN/43/1c3d0f31b70701e10000000a422035/frameset.htm]
    Data slice - [http://help.sap.com/SAPHELP_NW04s/helpdata/EN/43/1c3d0f31b70701e10000000a422035/frameset.htm]
    Hope this solves your doubt.
    Regards,
    Balajee

  • Characteristic Relationship Challenges in IP

    All,
    I'm having a bit of a problem with characteristic relationships in IP.
    We have a simple planning cube with no data.  It has the characteristics 0CALMONTH, 0MATERIAL, 0SALESORG, 0SALES_GRP, 0SALES_OFFICE, and 0PAYER.  We want to build a query which allows us to plan on specifically designated valid combinations of 0SALESORG, 0SALES_GRP, 0SALES_OFFICE, and 0PAYER.  However, instead of displaying only the valid combinations we desire, things seem to be showing up as the Cartesian Product of the characteristics.
    We thought we could accomplish this through a characteristic relationship and we tried establishing one (first by creating a DSO and then by creating a hierarchy).  But all combinations seem to yield only one of the following results:
    *Only the first level of the hierarchy
    *The Cartesian product
    *The 2nd level of the hierarchy (and only the 2nd level) but unfortunately containing ALL options in master data
    Has anyone here ever managed to do in IP what I'm trying to do (display only certain valid combinations of characteristics)?  If so can you give me a step by step outline of how you did it?
    According to SAP hosting we have all of the latest Service Packs.

    All, the issue is partially corrected.  Instead of fighting with hierarchies, I stepped back and re-attacked this problem by creating a characteristic relationship based on a DSO.  (I had tried this initially but it failed for a reason I will explain below.)
    We do top-down planning and so I need these valid combinations at each level of granularity.  I created a DSO with the key 0SALESORG, 0SALES_GRP, 0SALES_OFFICE, 0PAYER, and populated it with the valid combinations.  However, when I tried to create the characteristic relationship it does not allow me to select 0PAYER as a "Source Characteristic".  This results the relationship being inconsistent.
    So then I created a DSO with the key 0SALESORG, 0SALES_GRP, 0SALES_OFFICE, and populated the valid combinations.  It worked perfectly for my query at that level of granularity but not for the higher level of simply 0SALESORG and 0SALES_GRP and so I found myself creating another DSO and characteristic relationship to handle that level.
    Now I have the valid combinations down to a certain level of granularity displaying properly, but not all the way to the 0PAYER level.  I'm not sure why it has a problem aside from perhaps the fact that 0PAYER is a reference char based on 0CUSTOMER.  Does anyone know why it has this problem with 0PAYER?
    Additionally I have found that I can no longer execute a simple copy function on my cube because it "cannot find reference data for characteristic combination" in an insistance when I planned on a characteristic with a blank value.

  • Characteristic relationship with Exit class is not applied correctly

    We are using a characteristic relationship (with derivation) type Exit class. For that we have created class ZCL_RSPLS_ARTICLE_FROM_PLMOD as a copy of the standard class CL_RSPLS_CR_EXIT_BASE.
    Target and source characteristics are members of the aggregation level.
    We want to generate a list of valid combinations of characteristics planning models and articles which should be planned in the planning query.
    For that we are using the method IF_RSPLS_CR_METHODS~CREATE:
    Source is characteristic Model ZMATMOD and we determine in the exit class all active articles ZMATART.
    We get a list of active (planning relevant) models and articles in our exit class (table e_th_chas).
    --> For instance 6 combinations
    Until here everything works fine.
    The problem is that in the query 8 combinations are displayed.
    We have no idea why more than the generated combinations are displayed.
    One reason could be that the characteristic article ZMATART is an attribute from characteristic model ZMATMOD.
    So from a master data point of view 8 combinations would be relevant.
    But we use the exit class in order to reduce the number of combinations to planning relevant items.
    If we use the method IF_RSPLS_CR_METHODS~CHECK we could flag the 2 combinations which are not planning relevant to not valid.
    But these are then displayed in the query. 6 combinations in change mode; 2 combinations in display mode. This would not help us.
    We would like to see only the planning relevant combinations  6 combinations
    Can anyone please help me urgently?
    Best regards
    Martin

    Hi,
    set a break-point in the factory method get_instance to check whether the class is called. In the planning modeler make sure that you  use an external break-point.
    Or use rsrt an change a cell value: Derivation is called in the delta buffer to derive from the fields contained in the aggregation level. So check also that the source fields are contained in the aggregation level or can be derived via a a chain of derivations.
    Also make sure that all source fields have to be non-initial. The system will not call derivation for initial source fields since in this case there is not unique target, cf. http://help.sap.com/saphelp_nw70/helpdata/en/43/1c3d0f31b70701e10000000a422035/frameset.htm
    Remark: The attached document of note 994853 is about the disaggregation feature but it also contains a section about the characteristic relationships. Observe also that the template exit classes are documented in SE24.
    Regards,
    Gregor

  • Characteristic Relationship BI-IP

    Hi,
    I am trying to create the following characteristic relationship on real time planning cube.
    Within the realtime cube I have 0fiscper and 0fiscvarnt being populated.
    I also want to calculate 0calquarter and 0halfyear1.
    For this I have created a DSO which has 0fiscper and 0fiscvarnt as the key and 0calquarter and 0halfyear1 as the data fields. I am populating 0fiscper and 0fiscvarnt during the upload and calculating 0calquarter and 0halfyear1 via a routine.
    I am now trying to create the characteristic relationship, but when I enter the DSO technical name, I get the following error message:
    DataStore object '....' does not have a data field from the InfoProvider; this object is invalid here.
    Any ideas why this happening, all the fields in the DSO exist in the realtime cube.
    Thanks
    DJL

    Hi
    For time characteristics, there are standard characteristic relationships.. dont see why need to create them.
    if it is for fiscvarnt-fiscper combination: guess no need for other things.
    Also if u r specifying DSO name in planning modeler, I guess u can look up the DSO thru F4 help.
    rgds
    Deepak

  • Fields missing in Characteristic Relationship

    Hi Experts,
    I want to derive Currency Key from Company code using Characteristic Relationship. I am using 'With Derivation' and master data attributes. But in the source fields I see only two fields Cost Center and Controlling Area. Not sure why I am missing rest of the fields from the Cube. Does this mean, I have to have Aggregation levels maintained before I look at Characteristic Relationships??
    Thanks,
    DV

    Hi,
    derivation is used to fill characteristic values from other characteristics in the InfoCube. So to derive 'Currency Key' from 'Company Code' means that both characteristics have to be inculded in your InfoCube. I think, Currency Key is an attribute of Company code, so you can create a derivation relation based on characteristic Company Code.
    If you don't need 'Currency Key' in the InfoCube, you also may use Currency Key as a navigation attribute. Then you need not characteristic relationship for this, the system automatically know about the link between Company Code and Currency Key.
    Regards,
    Gregor

  • Display data problem in MP

    Hi all,
            Infoset is included in multiprovider. There is a keyfigure which has 0calyear in exception aggregation.Infoset is displaying without any error. 0CALyear is already present in Multiprovider.
    What could be the reason to display that error message.
              When I am trying to display data of multiprovider, it is showing following msg   InfoProvider "ZINFOMP" does not contain characteristic 0CALYEAR. The exception aggregation for
    keyfigure can therefore not be applied.
    Thanks in advance!

    hi vivek,
       plz go through the link and maintain the settings.
    further issue on this,try to revert it back.
    https://websmp203.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012006153200001735542002
    regards,
    meiy

  • Display data problem

    Hi all,
    Infoset is included in multiprovider. There is a keyfigure which has 0calyear in exception aggregation.Infoset is displaying without any error. 0CALyear is already present in Multiprovider.
    When I am trying to display data of multiprovider, it is showing following msg InfoProvider "ZINFOMP" does not contain characteristic 0CALYEAR. The exception aggregation for
    keyfigure can therefore not be applied.But when I create a query on multiprovider,it is showing data properly.
    What could be the reason to display that error message.

    Change your query to display both Infoprovider & CalYear. Retry.

  • Characteristic  Relationship in BI-IP

    Hi
    We have an issue creating Characteristic Relationship in BI-IP. We are on BI-7.0 with SPS-12.
    When I am selecting Char. Rel without DerivationChar Combinations Based on HierarchyThe Variable Hierarchy button which was getting displayed before is disappearing. We have more than one hierarchy for Internal Orders, Cost Elements.
    Please let me know how to go about.
    Appreciate your response.
    Regards
    Srinivas

    Hello Srinivas,
    I tried it and it seems to be a bug. Please open a customer message so SAP support can analyze the issue.
    Regards,
    Marc
    SAP NetWeaver RIG

  • BI IP-Characteristic Relationship- invalid combinations are shown

    Dear all,
    we need to create a query ready for input but we need to avoid that the invalid combinations of two characteristic on wors are shown.
    In fact the system presents the inconsistent combination as not editable.
    Could you please suggest how to avoid this?
    Many thanks in advance for help!
    Stefania

    Hi
    the link is ueseful, but I try to explane what we really need.
    We have in the level two chars (ZC1 and ZC2; ZC2 is attribute of ZC1) and here you can see the values
    ZC1               ZC2 
    PREVAI     AI    
    GUASAI     AI    
    PREVBT     BT   
    GUASBT     BT   
    The requiremet is that the user can plan by ZC1 and ZC2, but that he has a total row by ZC2 (not editable).
    That's why I defined a structure on the rows with restrictions for ZC1 and ZC2, according to the master data relationship, and put the structure on the rows.
    I defined a hierarchy for ZC1 where nodes are values of char ZC2 and I set this in the characteristic relationship for the provider. here is the hierarchy.
    AI
        PREVAI
        GUASAI
    BT
        PREVBT
        GUASBT
    The result is that in the best option I see in the query invalid combinations such as BT PREVAI.
    Any suggestion?

  • Characteristic relationship not working

    Hi All,
    I created a characteristic relationship using Datastore object considering two infoobjects that were available both in my real cube as well as the ods.
    Bcos of this i was able to generate(through reporting on cube) a valid combination of these two objects which were there in Datastore but not in Cube.
    Yesterday i created this and the query was working fine.After that i deleted the char relationship and recreted again and did some more enhancements like suppressing result rows etc, adding more characteristics in filter.
    But the query is not displaying any results now for objects present only in DSO and not in cube.
    What could have changed because of which it is not working?
    Any help is appreciated.
    Ajay

    Hello, the link should work, here a clickable link:
    http://pwmather.wordpress.com/2013/07/04/projectserver-ps2013-excel-pivot-table-limitation/
    Paul
    Paul Mather | Twitter |
    http://pwmather.wordpress.com | CPS

  • Characteristic relationships with derivation. I don't quite understand...

    Hi, experts!
    I'm trying to figure out all about using derivation in characteristic relationships and even though I seem to generally understand what it's for, some moments are still unclear.
    Let me describe the task: I have, for example, 10 item categories, all of them are in the real time info-cube. I have unique combinations for them, which are loaded into the DSO and I'm trying to create char. rel-ps based on that DSO.
    In the first aggregation level I'm using only the first 3 levels of item categories. The other 7 are not included.
    Let's assume I've planned my key figures for those 3 levels, and saved the plan. I need the system to distribute (disaggregate) the values among the remaining 7 category levels, so when I open another plan, based on an aggregation level that includes all 10 item categories, I would see all the data correctly and all the necessary combinations.
    As I understand, in that case I need to have characteristic relationships with derivation.
    But SAP demands that all the "target" characteristics should be held in the "Data Fields" section of DSO. And therefore they won't be key fields.
    I don't really get it - why should they be "data fields"? If I use them as "Data Fields" in the DSO, I won't be able to load all the possible combinations, because in some cases these 3 item categories that are the keys of the DSO, will match, only the remaining 7 will be different...
    How do I solve the described task?
    Thanks.
    Best regards,
    Andrey

    Hi Andrey,
    derivation is a function, given the source fields the derive functions fills the target fields. In other words, given a relation with two characteristics A, B with A source and B target the derive function F modeled in the relation 'calculates'  F(a) = b with a, b members of A,B, respecitvely. Since F is a function for a given a there are not two differen b1, b2 with F(a) = b1 and F(a) = b2.
    Using a derivation relation modeled in a data store the function F is defined by the active table of the data store. So A has to be the key and B has to be a an attribute (non-key). If this is not the case and A, B are key fields you can have the combinations
    A    B
    a    b1
    a    b2
    and this is by defintion not a derivation relation, but an n:m relation.
    On other words derivation fills redundant fields.
    It seems that you want to do just the opposite. It is a common problem to plan on a 'higher level' and to disaggregate from the higher level to lower levels, but of course only valid combinations should get values. You can use planning functions or the disaggregation feature in the query. Characteristic relationships are used to model the valid combinations.
    An example is as follows: We have Product -> Product Group -> Product line, the arrows indicate a derivation relation. The query uses all three characteristics in the aggregation level but has only Product Line and Product Group in the rows. Using disaggregation in the query changed key figure values will be disaggregated to Product (and maybe other characteristics used in the aggregation level). The system uses characteristic relationships that can be applied for the aggregation level to check the consistency of the records. Observe that a derivation relations can also be used to check the consistency of a combinations if both source and target fields are filled. Observe that for disaggregation of the above mentiond fields are filled and thus can and have to be checked using the derivation relations (and maybe other modeled relations).If 'access mode for result values' based on characteristic relationships is used in the query the relations can also be used to create all valid combinations needed for disaggregation.
    So you have to check whether the constraints you need are really of type n:m, then all fields have to be key in the data store or whether you have a derivation relation. By the way, derivations can be combined as in the Product -> Product Group (first relation) and Product Group -> Product Line (secdond relation) example.
    Regards,
    Gregor

  • Lookup Characteristic on IP data post (FUNDS_CTR- COMP_CODE)

    Hello.
    In my case, funds centers belong to appropriate company code, say
    FUNDS_CTR1,  FUNDS_CTR2, FUNDS_CTR3 belong to COMP_CODE1
    FUNDS_CTR4,  FUNDS_CTR5, FUNDS_CTR6 belong to COMP_CODE2
    FUNDS_CTR10,  FUNDS_CTR11 belong to COMP_CODE3
    etc.
    I got IP-enabled InfoProvider with 0COMP_CODE and 0FUNDS_CTR. I've created aggregation level on 0FUNDS_CTR. Is it possible to create lookup mechanizm (by ABAP or some type of hierarchy or whatever) to get comp. code by funds center on data post to the InfoProvider? Back to the example:
    Then user chooses FUNDS_CTR4 I post this value with COMP_CODE2 value
    Then user chooses FUNDS_CTR11 I post this value with COMP_CODE3 value
    etc.
    thanx in advance,
    points will be awarded

    Hi Gediminas,
    please check the follwing link:
    http://help.sap.com/saphelp_nw70/helpdata/en/43/1c3d0f31b70701e10000000a422035/frameset.htm
    Please search in this forum as well for characterist relationships. You will find useful information about this topic.
    Regards Matthias Nutt
    SAP Consulting Switzerland

  • Multiprovider display data issue

    Hello,
    I'm using BI7.0 and created Multiprovider using Custom DSO and Infocube1.
    the problem is, when i use display data through multiprovider, I'm not able to see data from DSO .
    I have considered all common fields from DSO and Cube and assigned in multiprovider.
    basically I'm selecting all IO and Keyfigures from Infocube1 and few IO from DSO
    some reason I am not able to see data from DSO when i view data through multi provider.
    Please help me to view data from both cube and dso through multi provider.
    Thanks
    Ganga

    Hi Ganga,
    Please check whether there is any restrictions for the field 0PROVIDER. There may be restriction to get the data only from cube.
    If there is no any restrictions then here may be your problem.
    You need to maintain atleast one key figure in both targets.
    Since there is no any key fig coming from DSO
    please create a dummy key fig and try to check once again.
    please go through the link.
    Re: MULTIPROVIDER NOT GETTING DATA
    hope this helps u.
    Thanks,
    Sai Chand

  • Need Suggestion in displaying data in ALV.

    Hi All Experts,
    I have a scepic scenario for which I need your inputs. I am preparing a report which will display data foe entries made in time sheet. The entries in time sheet can be made for anything like a change request on an incident etc. It will have various output fields
    And also dates for which entries are made. So it can have date from 1 to 31. This all is
    to be displayed in ALV. Now the report can be displayed in two Summarised ways.
    One summary can be for a user and another for the  object type(incident, change request).
    Now if the user wants to see this report for a period more than a month  then I have to summarise it against a month too. So am not sure how to handle this. Which type of ALV function module to be used to display this?
    Regards,
    Saket

    hello,
    I would suggest to go for GRID display - for that you can use either function module or class.
    Tips:
    If it also need to be summarised by month then add an extra field in fieldcatalog as monthid / monthname.
    also it's better to have an extra field for object tyoe (Incident/ change)...
    Thanks.

Maybe you are looking for