Restrict formula by characteristic

Hi forum,
For an accounts receivable report I need to show two KFs by customer:
1. Balance on a key date
2. days overdue (i.e. how many days the customer is late). This CKF should only be shown for document type = DR (invoice).
KF 2 I get through formula: IF (net due date < key date) THEN (key date - net due date).
However, how do I get the additional restriction document type = DR into the formula?
As far as I know, you cannot restrict formulas by a characteristic, but if I set a global filter for document type, it will affect KF 1 (balance). I also investigated Constant selection, but it doesn't work.
Any idea, how this could be solved?
Thanks in advance.
BR, Alex

Hi Alexendar,
This is possible !!!
1)Create new Selection
2)Drag the char  document type on the Right side
3)Click on it and restrict it with DR.
4)create a new formula and use this New selection.
It will be applicable to only that KF.
Rgds
SVU123

Similar Messages

  • Restrict values of characteristic in input-ready new rows query

    Hello all
    We are creating an input-ready new rows query. So we added characteristic as row.
    We need the values in F4 (while choosing value in this row) are to be restricted by hierarchy (or just restricted by some algorithm - list of values). But if we choose "hierarchy" for that characteristic, it will also appear in rows, so not one posted value will appear, but full hierarchy for this value. How to make F4 for choosing restricted values of any characteristic.
    Reason: we have different account plans for different years and don't want users to choose "old" positions.
    Cheers, Yuri

    Hello, Yuri!!!
    Try to use next variants:
    1) Authorization
    restrict you characteristic in RSECADMIN
    2) COMPAUND
    You can add compaund characteristic to you main characteristic, and if you restrict this compaund  characteristic in filter, then in query you'll see only appropriate values
    3) FILTER
    You can restrict not only fixed values, but you can use prequery for you characteristic. For example make DSO in which will be calmonth and account in key. And make query to take accounts for calmonth. After that in you main query restrict you account through variables with replace path type (set query for accunts for month).
    4) Relation in RSPLAN
    Create DSO(as in case 3) and try to use relation for you realtime cube in RSPLAN.
    Anton.
    Edited by: Anton Moskvichev on Nov 27, 2008 9:51 AM

  • What is an "empty restriction formula"?

    Users are getting a popup window when opening some of the (ALCM imported) Web Analysis documents. (11.1.2.2)"
    The popup contains a message:
    "The empty restriction formula has been removed.
    If they (or I) click OK and save the document the message is "gone for ever". So thats good news.
    But I do not understand what the message is refering to. I guess its a essbase message, but perhaps you can help m clarify matters.
    Thanks in advance
    Detlev

    In previous Web Analysis releases (up to 11.1.1.3) it was possible to add a "Restrict Data" definition with empty restrict formula body.
    For the latest releases, there was a bug request that WA should automatically remove the empty "Restrict Data" definitions from the reports created in previous product releases.
    So it recommended to show a warning to end users notifying them about invalid "Restrict Data" DTO removal.
    Implementation for removing empty Restrict Data was added with additional notification "The empty restriction formula has been removed".

  • BI IP - Planning Function Type Formula Error "Characteristic not Supported"

    Hi all,
    I have created a planning function type formula with very simple code. The code was copied from SAP Library and FISCPER was replaced with 0CALDAY. I continue to get an error 'Characteristic 0CALDAY is not supported".
    The characteristic 0CALDAY is in the Infoprovider and the aggregation level. I have tried 'To Characteristic Usage' with both changed and in condition.
    DATA D1 TYPE D.
    DATA D2 TYPE D.
    DATA I1 TYPE I.
    DATA I2 TYPE I.
    DATA CALDAY TYPE 0CALDAY.
    FOREACH CALDAY.
    CALCULATE 1ST DAY OF ZCALEND
    D1 = C2DATE( CALDAY, S ).
    CALCULATE LAST DAY OF CALDAY
    D2 = C2DATE( CALDAY, E ).
    CALCULATE THE DIFFERENCE BETWEEN LAST AND 1ST DAY MINUS TWO DAYS
    I2 = 2.
    I1 = D2 - D1 - I2.
        MESSAGE I001(UPF) WITH 'DIFFERENCE' I1.
    ENDFOR.
    Thank you in advance for any help.
    Teri

    Thank you very much for your reply. What would you suggest? I must use 0CALDAY.  As you can tell I am very new to IP, I have tried other options for example:
    DATA ZDAYS TYPE I.
    DATA ZDT TYPE ZCALSTART.
    DATA ZDF TYPE ZCALEND.
    ZDT = ZCALSTART.
    ZDF = ZCALEND.
    ZDAYS = ZDT-ZDF.
    {KF,ZDT,ZDF} = ZDAYS.
    I received an error "ZCALSTART could not be recognized"
    I also tried to call a function. 'FIMA_DAYS_AND_MONTHS_AND_YEARS'.
    DATA D1 TYPE D.
    DATA D2 TYPE D.
    DATA DD TYPE I.
    DATA CALS TYPE ZCALSTART.
    DATA CALE TYPE ZCALEND.
    D1 = CALS.
    D2 = CALE.
    CALL FUNCTION 'FIMA_DAYS_AND_MONTHS_AND_YEARS'
      EXPORTING
        I_DATE_FROM          = D1
      I_KEY_DAY_FROM       =
        I_DATE_TO            = D2
      I_KEY_DAY_TO         =
      I_FLG_SEPARATE       = ' '
    IMPORTING
       E_DAYS               = DD.
      E_MONTHS             =
      E_YEARS              =
    I received an error "Types of parameter I_DATE_FROM () and variable D1(D) are inconsistent".  From what I could find they should be consistant.  Please provide any suggestions. Thank you!
    Teri
    Edited by: teri chandler on Mar 30, 2010 3:26 PM

  • Formula at characteristic level

    Hi All,
    I have a scenario in which I need to implement the formula in BeX at characteristic level. For example
    Comp Code     Plant     Material     Sales     Qty     Actual Rate(Sales/Qty)     Target Rate     Variance (Actual Rate - Target Rate) * Qty
    1001               TT01     ABC          100        10      10 (Rs/Kg)                         5 Rs/Kg           5 * 10 = 50Rs
    1001               TT01     ABC          500        10      50 (Rs/Kg)                         5 Rs/Kg           45 * 10 = 450Rs
    1001               TT01     BCA           900        10     90 (Rs/kg)                         100 Rs/kg        -10 * 10 = -100 Rs
    From above calculations, total variance is 50 + 450 - 100 = 400 Rs
    So, I need to make one report in which there is only one selection 'Variance' and it should display 400 Rs
    i.e.
    Variance = 400 Rs
    Please help how should I create such requirement in BeX.
    Thanks.

    Hi Sameer,
    I think in bex level you can't do it if your requirement is showing 450 when removing the material characteristic. You can add a KYF to your infoprovider and do the calculation through transformation and in the query that will work fine.
    Regards
    Yasemin...

  • Creating restricted Key Fig: characteristic Not availlable for selection

    Hi,
    I am creating a restricted key figure  and some of the restricions values are not available fr selections. When I try to type the missing options it only enter them as the first 2 characters.
    In one case it basically gives a message that it is not in the master data and but that it will allow for selectinons but I needed to go to the master data to make entries.
    What could be going on here?
    Thanks

    hi Amanda,
    would make sense if you want to restrict with the values that exist in infoprovider only or from all master data (if exist in master data and not in infoprovider, no data come when reporting), if you restrict with value not exist in infoprovider then no data will be displayed.
    first 2 character .. your characteristic may have length 2 only, it's key, try to right click 'technical names'.
    when restrict, you can click 'display other values' button (yellow right arrow),
    then there's option to restrict only infoprovider.
    however, of course we are allowed restrict with values that not exist,
    data in bw development/quality may differ from production,
    we may want to restrict values that exist in production but not in dev/QA,
    and we need to transport the query from dev to QA/prod.
    hope this helps.

  • Restrict Formula Calls in Sales Order Pricing

    Hi All,
    I have created a pricing conditon formula to get the price for the real time contract price from a third party Contract management system through a RFC call, and assigned the formula to a condition type.
    In this formula, if there was an error i am exporting the error message to a memory and importing the value from that memory to set a billing block in the user exit SAVE_PREPARE_DOCUMENT (MV45AFZZ).
    The problem i am facing is that the formula is getting called many times uncessarily for eg. when you click pricing etc
    and not necessarily updates the price all times. Actually the price is not updated when called from the following routine and is basically because of the following code.
    Form: xkomv_bewerten.
    IF xkomv-kofrm NE 0 AND wertformel EQ space AND komp-kposn NE 0.* rettkomv = xkomv*.
    xkwert = xkomv-kwert. frm_kondi_wert-nr = xkomv-kofrm. PERFORM (frm_kondi_wert) IN PROGRAM saplv61a IF FOUND. xkomv = rettkomv.
    ENDIF.
    During Change Sales Order, because of this even a billing block is set before, it is getting cleared without updating the price.
    Can somone help me with this?
    Thanks.
    Martin

    I coded  this logic in a 906 pricing routine... and I did not have any problem bcoz of multiple hits... SAP is taking care of when to update values as per the calculations I am doing here....
    if I remember right SAPLV61A is the main program which will be included with all sorts of code related to routines..
    * Call the RFC wrapper in a new task
      CALL FUNCTION 'ZTEST'
        STARTING NEW TASK taskname
        DESTINATION 'NONE'
        PERFORMING ret ON END OF TASK
        EXPORTING
          comm_head_i           = wa_komk_i
          comm_item_i           = wa_komp_i
        EXCEPTIONS
          communication_failure = 1
          system_failure        = 2
          resource_failure      = 3.
      IF sy-subrc EQ 0.
        WAIT UP TO 1 SECONDS.
      ENDIF.
    * Get the values from the RFC shared memory export
      CONCATENATE 'ZTESTVPRS' sy-uname INTO memid1.
      IMPORT lt_komp = comm_item_e
      FROM SHARED BUFFER indx(st) ID memid1.
      wa_komp_o = comm_item_e.
      IF sy-subrc EQ 0.
        DELETE FROM SHARED BUFFER indx(st) ID memid1.
      ENDIF.
    * Get the Header level from RFC shared memory
      CONCATENATE 'ZTESTVPRS_H' sy-uname INTO memid2.
      IMPORT lt_komk = comm_head_e
      FROM SHARED BUFFER indx(st) ID memid2.
      wa_komk_o = comm_head_e.
      IF sy-subrc EQ 0.
        DELETE FROM SHARED BUFFER indx(st) ID memid2.
      ENDIF.

  • Formulas and restrictions on characteristics in a query

    Hi Guys
    This might seem like a strange question but can you perform formulas on characteristics in a query or just key Figures.  
    For instance for one query I have to substring the key to just the last two characters and on another I'd like to be able to display the product id twice based on the product type (like a restricted key figure)
    I can't see how to do this in the query is there a way or should this be done in the info cube or in the report once the results have been obtained?

    hi rachel,
    u can create in routine in either transfer rules or the update rules that would restrict your characteristic value to only the last two characters.Now it is up to you to decide whether to restrict the original characteristic or create another characteristic which gets its value from these routine.
    for the second part of your question i think the restricted keyfigure will do its job.
    reward if it helps,
    ajay

  • Restricting a characteristic & query time out problem

    Hi. We have the follwoing problem:
    Before our BI upgrade, we have had a number of users querying different info areas, that are now having difficulty restricting on a characteristic in a query.  This was performed with no problems before the upgrade. 
    Many times, the list of records for the particular characteristic is quite small.  Either it takes 20-30 minutes for the list to appear, or the query times out (after 6000 seconds).
    Any ideas?

    Any time you have an existing query that has been running quickly in production, and it suddenly starts to run much longer, you should be suspicious of some change to DB statisitics and or indexes.
    So the first thing to do is work with your DBA to make sure the DB statistics are current for the tables involved in the query, then get an Explain Plan for the query which will show you how the DB is trying to execute the query, what indexes it uses, etc.  Perhaps stats are not being refreshed after the upgrade, or something happened to an index

  • Time characteristic restriction in BW BPS

    Hi to all,
    I got one question for BW-BPS. This was happened after upgrade of Netweaver
    service pack. Before that it was fine. My question is as follow:
    Under DW workbench when I create an InfoProvider which included time dimension
    that consist of fiscal year, fiscal year/period, posting period, calendar
    year, calender year/ month. I try to select fiscal year, fiscal year/period
    under a planning level, then I select unassigned(#) time characteristic for
    fiscal year/period and save it. System allow for this restriction under time
    characteristic fiscal year/period. However, if I deselect fiscal year, fiscal
    year/period under a planning level and select calendar year, calender year/
    month under the same planning level, then I select unassigned(#) time
    characteristic for calender year/ month and save it. System was not allow for
    this restriction for time characteristic and generate the following message:  
      Message: UPC003- Value# is not permitted for characteristic calendar
    year/month.
    There was no characteristic relationship set for time dimension
    characteristics. I still not understand why system is not allow for
    unassigned(#) time characteristic selection for calender year/ month
    Therefore, I would like to need a support for this. Is it a system error?

    Hi Gupta,
    Thanks for your guide. I already try as per your instruction but not work because when I create a planning level with only 0calmonth, system still not allow me to include unassigned (#) for time restriction. May be I could explain to you why I need to select unassigned (#)  for 0calmonth.
    My explanation is as follows:
      Actually I already create a planning level with selected time characteristic calender year only for example Year 2008 and input value. Now I want to distribute the yearly figure to monthly, therefore I need to create another planning level and perform top down distribution. In the top down planning level, I have to select calender year/month for time characteristic and restrict the period to Jan 2008 to Dec 2008 and include unassigned(#) for the purpose of running distribution function.
    As I have told you in the earlier note which mentioned that the above task was actually worked in the beginning time before we have upgrade our Netweaver service pack. Unfortunately, it not work anymore after the upgrading of Netweaver .
    Do you have any idea regarding the scenario of before and after upgrading of Netweaver. Does it affect the previous settings?
    Hope you can help me to find out more on this.
    Tq.

  • Restricting a Characteristic in a Querry!!!

    Hi ,
    I have querry in which for a characterstic combination,the Material is having 0Dummy* values.
    Material is also a characteristic and is used in select option in the querry.
    So,I am not able to restrict the 0Dummy* values and also not able to filter those values out.
    Can anyone please help me out in restricting the Material characteristic for 0Dummy* values .
    Thanks,
    Amit.

    Hi Amit,
    Restricting a charecteristic values in Query, if you do this by default the Query is executed with this restrited value.
    in 3.X you can do at rows and free characteristics.
    in BI 7.0 default vales.
    in selection screen with select options you have different options like Exclue, include range..  or even after you can keep this filter in query output.
    Regards
    Daya Sagar

  • Variable (optional) and exclude value(#) for single characteristic

    Hi,
    In the reporting i want to apply variable and also fixed value restriction for one characteristic.
    Example: I want to apply variable(single and optional) for plant  and also restrict not assigned values(#)
    I created variable (given single and optional)and also excluded #  for plant but at the run time the variable act as a mandatory variable.
    please help me.
    Thanks
    vijj

    Hi Vijj
    in your case that is not possible.here i am providing diagnosis of the SAP in which cases the optional is not possible.so try creating a customer exit variable.
    Diagnosis
    An optional entry for is not possible in the following cases:
    is used in a selection row with Exclude (SIGN = E).
    v1& is used in a selection row whose operation is not EQ or BETWEEN.
    The selection row is an interval and both the from value and the to value are optional variables.
    The selection is a structure element (FEMS >0) and comprises multiple rows for the same characteristic.
    System response
    Procedure
    If you are able to accept the mandatory entry, you need not do anything. In the third case, you can use an optional interval variable. In the latter case, you define two or more (not visible) selection
    elements that you combine with a formula element.
    Procedure for System Administration
    Praveen.
    Message was edited by:
            praveen

  • RRI sending restrictions issue in BEx Analyzer - Known SP Issue?

    We have two queries linked through an RRI interface that is designed to "send" a restriction of one characteristic when the user right clicks on the cell containing the value they want to see in the second ("Goto") query and selects "Goto" and the second query's name. This interface works fine on my machine with both my ID and the test ID the users are using to test these reports. My machine is on SP8, Patch 1 Revision 1443. However, when the users execute the same query and try the RRI they see the second query with all of the values in that column, not just the one they "selected". They are on SP7, Patch 1 Revision 1352. Is this a known issue with this version of Analyzer? I have been searching around and can't find any documentation saying so, but something "official" from SAP that documents this would be perfect to recommend and upgrade to SP8 to fix this problem.
    Thanks!

    Hi Somenath,
    Are you sure that all the data in cube is affected? I mean also the data loaded in cube before GUI upgrade?
    I have a feeling that instead of GUI upgrade something happened to the background user that is extracting the data in source system. E.g. this user master data has changed - in decimal format.
    So check the user and check data loaded before/after change of GUI.
    BR
    m./

  • Filtering characteristic / ODBO

    hello,
    I want to restrict a characteristic to certain values, e.g. restrict the product characteristic to only show values for a certain product group. The characteristic is used as a free characteristic in the query. I added a filter selecting this product group. BEX Analyzer only shows products of the filtered product group, as expected, but when using an arbitrary ODBO client, the product hierarchy still shows all values. Is this by design? Can I use such a filter to restrict metadata or is it just for filtering data values?
    Thanks in advance.
    Guido

    here's my MDX query for retrieving the members of the product dimension.
    SELECT {[PRODUCTS                      ALLE PRODUKTE].Members} ON AXIS(0), {} ON AXIS(1) FROM [ANALYSIS/TEST_BISSANTZ] CELL PROPERTIES VALUE SAP VARIABLES [WINTER2] INCLUDING [PRODUCTS                      ALLE PRODUKTE].[CAR TIRES WINTER                PRODCAT]
    there are several product groups (summer tires, winter tires, all season etc.). the variable should restrict the products to winter tires but I always get all products.

  • Unable to restrict a rolling char field in MDX Universe.

    Hello!
    I am trying to create a restricted Characteristic in a SAP BW OLAP Universe. The chararcteristic is a Quarter field and has to be restricted for some reports to not display the last quarter in a rolling quarter period.There are a few menthods I followed inorder to achieve this, which are as below:
    1) Object - SELECT CLAUSE : <EXPRESSION>EXCEPT( [0CALQTR].[LEVEL01],[0CALQTR].[LEVEL01].CurrentMember.LastSibling)</EXPRESSION>. This gives and error messsage that the MDX expression is not valid.
    2) Object - WHERE CLAUSE : <EXPRESSION>EXCEPT( [0CALQTR].[LEVEL01],[0CALQTR].[LEVEL01].CurrentMember.LastSibling)</EXPRESSION>. This gives and error messsage that the MDX expression is not valid.
    3) Pre-Defined Filter -
    <FILTER KEY="[0CALQTR].[LEVEL01]">
    <CONDITION
    OPERATORCONDITION="NotEqual">
    <CONSTANT CAPTION="[0CALQTR].[LEVEL01].CurrentMember.LastSibling"/>
    </CONDITION>
    </FILTER>. This also does not work giving a MDX statement not valid error message.
    However, the only thing that works in all of the above the is the predefined filter with the following expressions:
    <FILTER KEY="@Select(Fisc. Year/Quarter\L01 Fisc. Year/Quarter)">
    <CONDITION
    OPERATORCONDITION="NotEqual">
    <CONSTANT CAPTION="@Prompt('L01
    Quarter','A','L01 Fisc. Year/Quarter',mono,constrained)"/>
    </CONDITION>
    </FILTER>.
    Kindly suggest if I can avoid using the prompt and just restrict the Quarter characteristic (with rolling quarters) to avoid displaying the last quarter.
    Any inputs are highly appreciated.
    Thanks,
    Vivek.

    Hi,
    I believe you have to explicitly include a validate activity...
    http://docs.oracle.com/cd/E25054_01/dev.1111/e10224/bp_appx_ref.htm#BABJDHEH
    Cheers,
    Vlad

Maybe you are looking for

  • (V7.3)RDBMS 7.3 Enterprise Edition NEW FEATURE에 대한 Q&A

    제품 : ORACLE SERVER 작성날짜 : 2004-08-13 (V7.3)RDBMS 7.3 Enterprise Edition NEW FEATURE에 대한 Q&A ========================================================= 1. Q) Oracle 7 Release 7.3의 new feature들을 간단하게 알고 싶습니다. A) 다음과 같이 요약하여 설명드리겠습니다. New features of 7.3

  • Are Time Machine, Mountain Lion and Retina able to work together?

    I have been using for a while Time Machines with various Mac's and OS X systems with no problem. But Time Machine (backing up on a 2TB Time Capsule) + Mountain Lion (10.8.2) + a Retina Mac Book Pro have been not able to appropriately work together fo

  • If I never turned on Time Machine and later zeroed out my HD can anything be recovered, ever?

    I recently sold my Macbook Pro and I'm wondering if files can be recovered evern after I zeroed out my HD? I did a one pass zero out because I read that one pass is good enough, but I'm a bit concerned that Time Machine will be able to recover files.

  • Speakable items help

    this is completely pointless but i think it would be cool. I like to use the speech tools to just talk to my mac and have it open things for me. It would be cool if after doing something I could say "Thank you" and my mac would say "You're welcome".

  • Scans are not viewing properly

    The pics & doc scans on an HP All In One are not viewing properly after saving in the folders, they do view properly in the HP scan app though Is this a Mavericks issue