Before aggregation with boolean operators

Hi gurus,
does someone know if there is a way to force a bex formula, defined by a boolean operator, to be executed in "before aggregation" mode?
For example, let A and B two propositions, and KF1 and . We define the following formula key figure 
<b>(A) * KF1 + (B) * KF2</b>
where (A) = 1 if A is true and (A) = 0 if A is false.
My question is: is there a way to force this formula to act before aggregation.
Thank you very much
Matteo

I cannot do that, because you can set "before aggregation" property only for KF that are built on basis KF. But I have to built my formula using boolean operators that are not basis KF.
That's why i cannote use "before aggregation" in the properties of my KF.
thank you
matteo

Similar Messages

  • Writing formula with boolean operators

    Hi,
    I need to write a formula that will, for a key figure, recognize if the cell is blank and if so convert it to zero. So for example,
    if (keyfig = ' ') , then (keyfig = '0')
    How do I do this using the boolean operators supplied to us for writing formulas and calculated key figures????
    Thank you!

    Hello CM,
    Have a look at this:
    http://help.sap.com/saphelp_nw04/helpdata/en/23/17f13a2f160f28e10000000a114084/content.htm
    Please, remember to use the search option on this forum, as I think that a lot of threads already mention this.
    Hope it helps,

  • Vector app with boolean operators

    not expecting much, I need some form of vector based (lines, plines, oval, squares etc...) that also has the ability to do basic boolean operations on those shapes, (addition/merging, subtraction, etc...). I would be sending these back to the main computer for more detailed work and conversion to graphic formats to use in programs, but want to work where I want to on the ipad and create the core shapes and drawings.
    Any suggestions would be great. I currently use an app called Touchdraw that does everything except the booleans, which would make my life a whole lot easier.
    Thanks
    Jason

    Fyi, eveloper of touch draw let me know at booleans are coming in a future update.

  • How to work force calculation before aggregation in 2004s

    I have a calculated key figure that has a variable in the calculation entered at time of query execution.  I have tried every setting I can think of to force the calculation before aggregation with no luck.  If I create the CKF in 3.5 without a variable it will work, but I cannot get this to work in 2004s.
    Does anyone know how in 2004s to force the calculation to take place at the automic level before aggregation and indepenent of drill-downs?
    I have referred to note:922727 but none of the exception aggregation options seem to behave as 3.5 does with calculate before aggregation.

    Hi, Sudeepta
    Thanks for your reply.
    I did try to set 'No display' for 'Hour'. The result is that the Characteristics 'Hour' doesn't appear on the query result, but the detailed line of key figures still display on the result. It looks like the followings: (I put summaries on the top/right)
    Date  1/1  1/2  Overall result
    KPI1    10        11   22  (sum line)
    KPI2    20        21   41  (sum line)
    KPI1    12        13   25  (detailed line)
    KPI2    13        13   26  (detailed line)
    KPI1    11        12   23  (detailed line)
    KPI2    12        12   24  (detailed line)
    I want to suppress all the detailed lines and leave sum lines on the result.

  • Aggregation Befre Calculation with Boolean Operator (BW3.5)

    Dear All,
      Here I am trying to create a 'Calculated Key Figure' with some logical expression to verify the value of other columns(ie: stock value = 0, market value = 0...etc) and I would like to calculate the result 'Before Aggregation'; Somehow, the calculated key figure with Boolean Operator can not be chosen as 'Before Aggregation'. I tried to create 2nd CKF to include the 1st CKF so that I am able to select the 2nd CKF as 'Before Aggregation', but the result just dont seem to be right.
      Any Idea to do this kinda calculation? Thanks a lot.
    B.R
    Charlie

    Instead of creating a calculated Key Figure, create a formula in the query and try whether it is giving a desired output??

  • Warning "Time of Calculation 'Before Aggregation' is obsolete" in BI 7.0

    Hi Friends,
    We have recently upgraded our BW system from BW 3.1 to BI 7.0. While executing one of the query in BI 7.0 i am getting the Warning Message "Time of Calculation 'Before Aggregation' is obsolete". I can run the query by ignoring the message and get the results. But I am not getting the correct result for some of the calculated key figures which has setting for Time of calculation as "Before Aggregation".
    After doing some research i found that before aggregation is not allowed in BI 7.0. We are using queries created in 3.x environment. There is some work around which talks about creating new calculated key figure with after aggregation setting and all. But in my case it not feasible as there are so many queries based on those calculated key figures.
    Does any one had the similar situation? Is there any other way to correct this problem?
    I would appreciate your help in this regards.
    Thanks,
    Manmit

    Hi
    Try SAP notes 935903.
    Symptom
    Calculated Key Figures "Existance Indicator" with aggregation behaviour "Before Aggregation" will get now with NW 2004s warning popup "Time of calculation 'Before Aggregation' is obsolete" during execution.
    this may be helpful.
    Also Check the below thread
    /message/2986338#2986338 [original link is broken]
    Regards
    Shilpa
    Edited by: Shilpa Vinayak on Oct 10, 2008 4:23 AM

  • Regular expressions with boolean connectives (AND, OR, NOT) in Java?

    I'd like to use regular expression patterns that are made up of simple regex patterns connected via AND, OR, or NOT operators, in order to do some keyword-style pattern matching.
    A pattern could look like this:
    (.*Is there.*) && (.*library.*) && !((.*badword.*) || (^$))
    Is there any Java regex library that allows these operators?
    I know that in principle these operators should be available, since Regular languages are closed under union, intersection, and complement.

    AND is implicit,
    xy -- means x AND yThat's not what I need, though, since this is just
    concatenation of a regex.
    Thus, /xy/ would not match the string "a y a x",
    because y precedes x.So it has to contain both x and y, but they could be
    in any order?
    You can't do that easily or generally.
    "x.*y|y.*x" wouldll work here, but obviously
    it will get ugly factorially fast as you add more
    terms.You got that right: AND means the regex operands can appear in any order.
    That's why I'm looking for some regex library that does all this ugly work for me. Again, from a theoretical point of view, it IS possible to express the described semantics of AND with regular expressions, although they will get rather obfuscated.
    Unless somebody has done something similar in java (e.g., for C++, there's Ragel: http://www.cs.queensu.ca/~thurston/ragel/) , I will probably use some finite-state-machine libraries and compile the complex regex's into automata (which can be minimized using well-defined operations on FSMs).
    >
    You'd probably just be better off doing multiple
    calls to matches() or whatever. Yes, that's another possibility, do the boolean operators in Java itself.
    Of course, if you
    really are just looking for literals, then you can
    just use str.contains(a) && !str.contains(b) &&
    (str.contains(c) || str.contains(d)). You don't
    seem to need regex--at least not from your example.OK, bad example, I do have "real" regexp's in there :)

  • XML Boolean Operators in fsiuser

    Hi All,
    We define BatchingByRecip batches in our fsiuser file, and we often write custom XPATH statements to use input data to send certain transactions to a certain recipient group. We've had good luck with very simple XPATH statements, such as:
    Batch_Recip_Def = !/Transaction/Confirm/CompanyInfo[CompanyCode='0002'];"BatchGroup1";Client
    However, we've recently had some requirements to add multiple conditions to these XPATH statements, and we haven't been able to get boolean operators to work. We're trying to do something like this:
    Batch_Recip_Def = !/Transaction/Confirm/CompanyInfo[((CompanyCode= '0001' or CompanyCode = '0003'))];"MINNESOTA";Client
    This seems like a reasonable requirement, but we haven't been able to get this to behave correctly. Has anyone been successful with something like this? Thanks for any help!

    You can mix DAL usage with this sort of rule like this:
    < BatchingByRecip >
    Batch_Recip_Def = =DAL("My_Script"); ... ; ...
    Basically, most places that accept a search mask of ?token or typically the xpath starting with ! will also accept the =DAL() or =GVM() type macro call. The "=" macro feature has a number of options like:
    =(expression) returns the value of a DAL symbol represented by "expression"
    =DAL(expression) returns the value of a DAL script named by "expression"
    =GVM(expression) returns the value of a GVM symbol named by the expression
    =@(expression) returns the value of a source field
    So, in the DAL script you can do whatever you need to do - write a complex IF with as many XPATHs as you need connected with AND or OR, etc, and be sure to return "TRUE" if you want this batch.
    Not sure how far back the equal sign macro feature goes, so if not in 11.3, my apologies in advance.

  • Calculated key figures from multicubes before aggregation

    Hi,
    I am calculating a total using a calculated key figure
    that has one key figure from a multicube and two other key figures from another multicube.
    Also I factor the total using a variable with a replacement path on the dummy attribute (Constant) to "force" the calculation at the material level.
    Cost = Cost(CUBE1) / Quantity(CUBE1) * Quantity(Cube2) * ZVRMATER1
    Problem:
    If I split the calculation this works before aggregation at the material level. Also this works fine using calculations that use key figures that must be calculated before aggregation if they all are from the same cube at the time.  The required formula above will not work (zero divide) since during selection the OLAP processor retrieves in phases and with value 0 from the key figure of CUBE2.
    Any suggestion on how to solve this without new back-end development?
    Thanks.

    Hi,
    I am calculating a total using a calculated key figure
    that has one key figure from a multicube and two other key figures from another multicube.
    Also I factor the total using a variable with a replacement path on the dummy attribute (Constant) to "force" the calculation at the material level.
    Cost = Cost(CUBE1) / Quantity(CUBE1) * Quantity(Cube2) * ZVRMATER1
    Problem:
    If I split the calculation this works before aggregation at the material level. Also this works fine using calculations that use key figures that must be calculated before aggregation if they all are from the same cube at the time.  The required formula above will not work (zero divide) since during selection the OLAP processor retrieves in phases and with value 0 from the key figure of CUBE2.
    Any suggestion on how to solve this without new back-end development?
    Thanks.

  • Calculated key figures before aggregation

    Hi,
    I'm having trouble creating a new calculated key figure. Here's the situation.
    I have two key figures: stock, value A. Now I want to create a new calculated key figure (in 3.x) using both key figures. The calculation would look something like: "stock * (value A == 0)". Now I want this key figure to work before aggregation. When creating this calculated key figure however I am unable to set the aggregation setting to before aggregation. Now, with any other key figure besides stock, this is no problem. Something like "profit * value A == 0)" works fine and I can set the aggregation setting to before aggregation. I suspect the reason I can't use stock in a calculated key figure set the calculate before aggregation is because of the exception aggregation of the stock key figure. It's set to last value in exception aggregation.
    Does anyone know how to solve this problem? Thanks in advance.
    Alex

    Hi Alex,
    please read this:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/75/21054da1392649948e5b94e4fc4bce/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a62f8e07211d2acb80000e829fbfe/frameset.htm
    The reason that somtimes the propertie is available or not depends on the key figure type - e.g. if it is complex or not. I think that here is a lot of info available in the forum.
    Regards,
    Adem

  • Implementing Boolean operators during find object for qualification

    Hi Team
    We would like to maintain requirements profiles for PD object (position,job etc.) in terms of qualifications (Q) using complicated boolean operators , for example :
    ((Q=English>4 OR (Q=French=5 and Q=Spanish>2)) OR (Q=German=6 and english<3) and Q=education # 2
    The complicated boolean operators could be also : range,excluded from the range,equal,not equal,not exits.
    We would like to execute the search for qualification ,profile matchup based on this complicated boolean requirments profile.
    Is there any custom development or configuration to make this happen ?
    Best Regards
    Dror

    Is this still true if the Collection generics elements are an interface type? For example, in the
    code I sent earlier, I have:
    /** The authorities granted to this account. */
    private Set<Authority> authorities;
    But Authority is an interface that is implemented by the DefaultAuthority class (maybe others
    eventually). I was under the impression that in this situation, the metadata does have to provide
    the actual type that will be in the collection.
    But even if it works in Kodo, one of the requirements of my project is that the JDO implementation
    be swapable with JPOX. When I started working on it, both Kodo and JPOX were at a much earlier stage
    of implementing JDO 2, and if I recall correctly, JPOX required the implementation class (though I
    don't know if it had to be fully qualified). I'm not sure that requirement has been removed from
    JPOX yet, though I haven't checked in a while.
    Thanks for your help with the default value settings though. Is there any place where I could have
    found that behavior documented (Kodo docs, JDO2 spec, etc.)?
    Mark
    Abe White wrote:
    p.s. You don't need to set the element-type in metadata if you're using
    Java 5 generics; we can get the element type from the field declaration.
    Also, when you do have to declare an element-type in metadata, you
    don't need to fully qualify the class name if the element class is in
    the same package as the field's owner (the current <package>), or in
    java.util, java.math, java.lang.

  • Bex Issue : before aggregation

    Hi,
    I have a problem in Bex that I thought to solve with the "before aggregration" option in Bex Analyzer but this doesn't seem to be possible.
    My query looks initially like this for 1 shipment 1344601 that is linked to 2 deliveries
    Shipment Delivery Del.Quantity Counter Del.Quantity/Count
    1344601   81209721  41.160 KG     2      20.580 KG      
    1344601   81209722  14.840 KG     1      14.840 KG
    Resultrow .............56.000 KG     3       35.420 KG
    This 35.420 KG is the right total delivery quantity for shipment 1344601. Note that counter is calculated via a formula with before aggregation. Also the Del. Quantity is included in a formula with before calculation.
    When I now remove the drilldown on the delivery my result is wrong :
    Shipment      Del.Quantity Counter Del.Quantity/Count
    1344601       56.000 KG    3       18.666.67 KG
    Resultrw     56.000 KG    3       18.666.67 KG
    The system is dividing 56.000 KG by 3 which leads to an incorrect result of 18.666.67 KG.
    ==> My problem is that I can't put the Del.Quantity/Count on calculation before aggregation, although Del.Quantity and Counter that are used in the calculation have both calculation before aggregation.
    Via a little trick (include the calculation in a new calculated keyfigure where I multiply it by 1) I could put it on calculation before aggregation but then the query execution fails.
    Does anyone know a solution for this behaviour as I think lots of you might have faced similar situations and I would like to avoid to solve this in data staging as this doesn't seem unsolvable in Bex to me...
    Message was edited by: Wim

    Hi,
    As per the my knowledge, we can use the properties of Before Aggregation in Bex Analyser.
    for ex. when u excute your query, by default the result of the calculated key figure is generated after aggregation. But we can change this property to before aggregation by going to context menu of the calculated key figure for the analyer.
    But it is considered as a bad practice in SAP.
    If you want to use this option in query designer it not available,
    because when we use calculated key figure in formulas it calculate as after aggregation. If you want to change it, we can change at analyser level.
    Hope u understood.
    Regards,
    Vamsi
    Assign points if useful.

  • Warning Time calculation "Before Aggregation" is obsolete

    Hi,
    Recently in our project we have upgraded BW 3.0B to BI7.
    After upgrade to BI7,  when we run some of the reports we are getting a warning message as below -
    Warning Time calculation "Before Aggregation" is obsolete.
    Pls refer to the attachment.
    Any of our satyam colleagues encounter this warning, if so what was the solution you applied.
    Note : I found some notes in Forum like saying use ' Exception Aggregation' for the Before Aggregation.. etc etc., but my problem is in our project thre are many CKFs are there which are using 'Before Aggregation'.
    Please let me know if you have any other alternatives.
    Thanks !!!!!!!!!

    Hi,
    Try SAP notes 935903.
    Symptom
    Calculated Key Figures "Existance Indicator" with aggregation behaviour "Before Aggregation" will get now with NW 2004s warning popup "Time of calculation 'Before Aggregation' is obsolete" during execution.
    this may be helpful.
    thanks,
    JituK

  • Before Aggregation in NW2004s(BI7)

    Hi Bex Gurus,
      We have upgraded our BI System to NW2004s and Bex version is still 3.5.
      Now we are also planning to migrate Bex to new version(NW2004s ).
      We have used "Before Aggregation" in some of the calculated KFs in the queries.  "Before Aggregation" is obsolete in NW2004s. So, I want to know whether these calculated KFs will give the same result when we migrate our front end to NW2004s.
    Please provide your experience.
    Regards
    MB

    Peter,
    Thank you for your reply.
    Is there a automatic way to do what you mentioned in below sentance?.
    " Using the new front end tools you can apply exception aggregation to all calculated key figures including those with formulas in them"
    Our scenario is,
    We have a many CKFs with "Before Aggregation" setting in BW 3.5 version.
    Example : CKF1 with "Before Aggregation" setting. This works irrespective of the drill down ( i.e Palnt, country or region) in BW 3.5. But, when I migrate the query  to NW2004s, CKF1 is not giving the expected result when we drill down on Palnt, country or region.
    So, Do I need to create three new CKFs (on Plant, Country and Region)  using exception aggregation and use corresponding CKF based on drill down  to get correct result in NW2004s?.
    Appreciate your help.
    Regards,
    Madhukar

  • Time of calculation before aggregation is obsolete

    Hi Gurus,
    I have this message when i try to ejecute my query, can anyone help me to resolve this problem, i have the SAP 7.0 EHP 1, and i just have the upgrade from SAP 3.5.
    I have a lot of CKF's in my queries and all of those use BEFORE AGGREGATION option, when i put in the propietries of my CKF the option after aggregation and then i check my query i have a message "time of calculation before aggregation is obsolete", and then when i put the option before aggregation in my CKF i have the message "CALLATE = 0 is not allowed".
    I hope that someone have the same issue and can help me with this.
    note: i'm using the BEX 3.5 and the BW 7.01 because the client wants that.
    tnks
    regards
    Odiseo
    Edited by: Odiseo BW on Oct 18, 2010 7:46 PM

    hmmm... how about checking the differences between 3.X & 7.X???
    before aggregation is no longer possible in 7.X, hence the error messages

Maybe you are looking for

  • Automate OneDrive for Business 2013

    Can anyone refer any link or resource location to automate OneDrive for Business with SharePoint Online. I need to fetch the libraries already added to "OneDrive for Business", also allow from a custom screen to add new library or delete an existing

  • What datatype should i use to store imaq image in sql database?

    Hi there i am thinking of saving the imaq image into database for retrieval in my website so that it's like a stream but i don't like what datatype does labview store the image as.

  • Photoshop Elements 7 Editor Error & 10 trial error

    Photoshop Elements 7 Editor Error Hello, Yesterday I did a clean install of Windows 7 (x64) on my PC & have completely updated it through Windows Updater, I than installed PSE7 (disk that I brought new 3 years ago & has worked fine up till now) & fol

  • Display a PDF file from local drive

    Hi, I would like to display a pdf file that is actually stored on the portal server hard drive. What I have tried to do is link an iFrame element to the url of the file: "D: MyFolder myFile.pdf" But it doesn't work. I have the following error when tr

  • Has anyone else experienced blue screens and continuous reboots on 5S

    I picked up my silver 5S 32 GB at the Verizon store Friday morning.  Throughout the morning I noticed that I would hit the home button and it would be powered down.  I loaded the .1 patch assuming maybe it was a glitch.  I went through the rest of th