Excel CUBESET across multiple dimensions returns #VALUE

Simplified question:
All the cubeset examples I'm finding seem to be limited to one "criteria"
http://office.microsoft.com/en-us/excel-help/cubeset-function-HA010083019.aspx
Ultimately I need a cubevalue that is based on multiple criteria. When I use a CUBEVALUE pointed to 4 different Cubeset cells, I get a #VALUE error.
* Should I be trying to combine my sets before I feed them to the CUBEVALUE, or should it matter?
* What conditions or circumstances would result in not being able to get a value from CUBEVALUE taking into account multiple CUBESET sources (I have independently identified that there are real values to return)
* If it would be better to combine all the criteria in one CUBESET before feeding that to the CUBEVALUE, what is the syntax (bracket placement) for including more than one condition from other cells that each contain a single cubeset condition? e.g.
=CUBESET("Cubename",({A1, A5, C10, B14}))
Thank you!
Note: two of my source cubesets are overlapping, I wouldn't think this is a problem- I'd expect the combination to work like a Venn diagram; one is "All members except APPLES", and the other is "All members except KIWI" so I'd expect
the combination of the two to result in "All members except Apples OR Kiwi"... please clarify if that isn't correct

Hi Keith,
That seems the value is not getting fetched from the right place. This is a different behavior and to maintain only one issue on a single thread
I would advise you to pursue the other thread you have just opened and will help us avoid duplication of the same issue.
Please reach out to us if you have any questions on this issue and we will glad to work on it.
Regards,
Abhijeet.

Similar Messages

  • AWM Calculated Measure for Percent of Total Across Multiple Dimensions?

    I noticed that AWM has a Share function that gives me a percent total of a grain from a specific hierarchy's Top of Hierarchy, but is there any way to do that with multiple dimensions? For example, if I had a Share of Dimension X = 55% Where Time = 1/1/2013 and a Share of Dimension Y = 32% Where Time = 1/1/2013, then could I have a Share of both Dimension X and Dimension Y = 16% Where Time = 1/1/2013?

    I had used an alternate solution which is a bit more cumbersome using native OLAP_DML formulae/expression.
    The above expression using OLAP Expression Syntax is much better (if it works).
    I was not aware of this OLAP expression syntax when i needed to create a kpi for similar requirement.
    We had Qty measure and Share along dimension like "Qty - Share at Year level", "Qty - Share of Total Customer".
    We needed to get "Qty - Share at Total Customer, Year".
    Cube= SALESCUBE
    Base Meas = QTY
    Step 1) Create Measure which represents "Qty - Total Customer, Year" which will work in any reporting context ...
    Note: For time=day1/2/3/ within same year and customer=cust1/2/3/... or Total Customer, the expression result will be constant (result fixed for any dimension members/status along the 2 dimensions - TIME and CUST). Denominator Value changes each year since we have constrainted time dimension to the ancestor of current cell at YR level. If we choose anscestor at TOP level TOTTIME say then the value is fixed for all time dimension members/values.
    olap dml expression: QUAL(SALESCUBE_QTY, CUSTOMER limit(CUSTOMER to CUSTOMER_LEVELREL 'TCUST'), TIME limit(limit(TIME to ANCESTORS USING TIME_PARENTREL TIME(TIME TIME)) KEEP TIME_LEVELREL eq 'YR'))
    in awxml - this becomes:
    ETMeasureColumnName="QTY_TCUST_YR"
    Name="QTY_TCUST_YR"
    MeasureExpression="OLAP_DML_EXPRESSION('QUAL(SALESCUBE_QTY, CUSTOMER limit(CUSTOMER to CUSTOMER_LEVELREL ''TCUST''), TIME limit(limit(TIME to ANCESTORS USING TIME_PARENTREL TIME(TIME TIME)) KEEP TIME_LEVELREL eq ''YR''))', NUMBER)">
    <Classification
    Value="AwmDescriptionType=OLAP_DML_CALC"/>
    <Description
    Type="LongDescription"
    Language="AMERICAN"
    Value="Qty - Total Customer, Year">
    Step 2) Define the share measure explicitly since we have already calculated the denominator needed for composite share.
    Check for division by 0 error before performing the share calculation explicitly as Numerator= Qty (for current cell/reporting context) and Denominator = Qty - Total Customer, Year (from Step 1)
    olap dml expression: if SALESCUBE_QTY_TCUST_YR ne 0 then SALESCUBE_QTY / SALESCUBE_QTY_TCUST_YR else na
    in awxml - this becomes:
    ETMeasureColumnName="QTY_SHARE_TCUST_YR"
    Name="QTY_SHARE_TCUST_YR"
    MeasureExpression="OLAP_DML_EXPRESSION(&apos;if SALESCUBE_QTY_TCUST_YR ne 0 then SALESCUBE_QTY / SALESCUBE_QTY_TCUST_YR else na&apos;, NUMBER)">
    <Classification
    Value="AwmDescriptionType=OLAP_DML_CALC"/>
    <Description
    Type="LongDescription"
    Language="AMERICAN"
    Value="Qty - Share of Total Customer, Year">
    </Description>
    Report needs to use measure QTY_SHARE_TCUST_YR (Qty - Share of Total Customer, Year) defined in Step 2. It may be useful to expose/display intermediate measure QTY_TCUST_YR also so as to make the basis of calculation very clear to the user.
    Nick,
    If you customize above soln. to use Total Time, Total Prod and Total Organization (along 3 dimensions)... I am sure the fact table has a time dimension which should also be factored in in your calc/defn.
    If you have missed out the join to Time dimension from fact in your queries, in olap reporting terms, its similar to Time Dimension selection of Time level = TTIME Total Time (1 node at TOP).
    You need:
    Step 1) Qty - Total Time, Total Product and Total Org
    Step 2) Qty - Share of Total Time, Total Product and Total Org
    Then the example you gave should be covered via QTY and QTY_SHARE_TTIME_TPROD_TORG (Step 2)
    SUM(quantity)
    2875should be QTY, QTY_SHARE_TTIME_TPROD_TORG (=100%) at Time level = TTIME, Product level = TPROD, Org level = TORG
    SUM(quantity)
    345 [12% of all products sold]should be QTY, QTY_SHARE_TTIME_TPROD_TORG (=12% hopefully) at Time level = TTIME, Product level = PROD with report filter on product = 'CX-867054', Org level = TORG
    SUM(quantity)
    977 [34% of all products sold]should be QTY, QTY_SHARE_TTIME_TPROD_TORG (=34% hopefully) at Time level = TTIME, Product level = TPROD, Org level = STORE with report filter on store = 'NY_ALBA_013'
    SUM(quantity)
    88 [3.06% of all products sold]should be QTY, QTY_SHARE_TTIME_TPROD_TORG (=3.06% hopefully) at Time level = TTIME, Product level = PROD with report filter on product = 'CX-867054', Org level = STORE with report filter on store = 'NY_ALBA_013'
    HTH
    Shankar

  • How to set hierachy to drill across multiple dimensions?

    Hello
    I have a situation:
    There are 3 tables: Credit Manager Dim, Customer Dim and Sales Fact
    There are 3 columns: Credit Manager ID, Customer ID and Document Number (from sales fact).
    The request is to create a hierachy so that the report can drill from credit manager to Customers (for that credit manager) and then to all the document numbers for that customer.
    I think I will need to create one hierachy that uses these 3 columns in each of the level. However, the challenge now is that one dimensional hierachy can only accept columns from one dimension tables.
    Please advice
    Thank you

    Thanks for the reply Dbettinger.
    For now I am ignoring document number part for testing purpose. In my credit manager dim, the lowest level is detail level where credit manager code is assigned under (Credit Manager Code is key enabled for drill-down). I have set the 'prefer drill path' of this level to point to Customer Dim- Detail level (where customer ID is assigned) as you suggested.
    However, when I tried running the reports, the credit manager code column is still not drillable. I think it is because this column is already at the lowest level of credit manager dim hierarchy and BI server doesn't take the preferred path of deeper level (customer dim)..
    This is where I am stuck.
    Any idea on how to make it work?
    Thanks

  • Calculating turn-rates across multiple dimensions

    hi,
    I am having some problems calculating the turn-rates of e.g. inventory. The cube is 6 dimensional, with seperate dimensions for months (which aggregate to Quarters etc), year and scenario (other dims are accounts, organization and countries).
    The turn-rates must be based on 12 month moving average revenue from the account dimension and must consider the three dimensions month, year and scenario (which have a member for actuals and several different forecast members).
    The calculation must use
    1) information from the months in the current year and months in the previous year.
    2) In addition, the scenario dimensions must consider if it is a forecast, that it includes actuals from the past periods and use data from the forecast dimension for future periods.
    At the moment I have problems getting the cube to do 2), while it has been possible to use IF functions in the outline to calculate 1). If I need to use IF functions in the outline for 2), it will be very complex and difficult to maintain, as I we have 13 different forecast versions in the scenario dimension.
    Any help is highly appreciated.
    Best
    Soeren

    Hi,
    unfortunately, this purpose-built datamart was built within the company RPD. It has been deleted since then. These are the two reasons why I can't post it.
    My advice is to take the time to read the help about how to build logical tables in the Administrator tool.
    Here's a quick walkthrough:
    - create your logical tables and join them in the business model diagram
    - create dimensions (hierarchies) for all your dimension tables with at least a total level and a detail level. Thins can be done automatically by right-clicking the dimension table and selecting "Create Dimension"
    - in the dimension tables, select the source table (in the source subfolder of the dimension table) and edit its properties : in the properties dialog box, select the content tab and in front of the dimension name, select the lowest (or apropriate) logical level
    - in some complex BM (logical levels), it might also be necessary to apply similar settings to the fact table: This time, when you edit a fact table source, you will see the list of all dimensions available in the contents tab. There, for each dimension your fact table is related to, you will select the apropriate dimension level. if there isn't any join between you fact table and a given dimension, leave the logical level blank.
    I hope this helps.
    Ced.

  • UML notation: Class operation return value multiplicity

    Hallo,
    how would you write function from example below using UML notation on implementation level, please:
    class Coin {
      public String[] getSideNames() {
        return new String{ "Odd", "Even" };
    }Multiplicity in return value is troubling me. I've tried +getSideNames( ) : String [ 2 ] but my tool just created new class named "String[2]" :-( To be precise I know that return value of function is array of MyClass with one or more element (1..*) so created class name was "MyClass[1..*]" -- nasty name to pass to javac isn't it? :-)
    Is is possible to write multiplicity of return value this way? I couldn't find anything in omg's "UML: supertructure document" :-( I am not telling that it's not written there :-)))
    Thank You.

    jschell>
    Unfortunately [n] behaves in same fashion as [*] =>
    creating class named MyClass[1..n]" :-(
    duffymo> what's the point?
    this was only sample, real application is far more
    complex than that. Even "nature" of result was just
    made up. How am I or anyone else who responds supposed to know that?
    >
    duffymo> you can have cardinality in a class diagram
    that shows exactly two values are available.
    yup, i ended like that but there's still problem coz
    return value class is "Object[]" :-(Sounds like a bad design, but I haven't seen the code, so I can't tell.
    duffymo> personally, i don't think that exposing the
    side names as ...
    "side names" were just example :-) IMHO there are
    certain situations where one could say "screw the
    abstraction" :-D E.g. for final classes from one
    package that cooperate on single time critical task.
    :)"screw the abstraction" - good luck as an object-oriented designer with that attitude.
    Either you're doing real-time work where time really is critical, or you're just another yutz who is congratulating himself on recognizing a time critical task without doing profiling or getting any real data. (A common mistake.) The maintainence and development time might be more critical here.
    Gotta admit that I'm not much interested in commenting on your poor approximation of the real problem.
    %

  • Concatenate a column value across multiple rows - PDW

    We are using PDW based on SQL2014. We require an efficient logic on how to concatenate a column value across multiple rows. We have the following table
    T1
    (CompanyID, StateCD)
    Having following rows:
    1              NY
    1              NJ
    1              CT
    2              MA
    2              NJ
    2              VA
    3              FL
    3              CA
    We need a code snippet which will return following result set:
    1                    
    CT,NJ,NY
    2                    
    MA,NJ,VA
    3                    
    CA,FL
    We have tried built-in function STUFF with FOR XML PATH clause and it is not supported in PDW. So, we need a fast alternative.

    Hi Try this:
    SELECT * INTO #ABC
    FROM 
    SELECT 1 AS ID,'NY' AS NAME
    UNION 
    SELECT 1 AS ID,'NJ' AS NAME
    UNION 
    SELECT 1 AS ID,'CT' AS NAME
    UNION 
    SELECT 2 AS ID,'MA' AS NAME
    UNION 
    SELECT 2 AS ID,'NJ' AS NAME
    UNION 
    SELECT 2 AS ID,'VA' AS NAME
    UNION 
    SELECT 3 AS ID,'FL' AS NAME
    UNION 
    SELECT 3 AS ID,'CA' AS NAME
    )A
    CREATE TABLE ##CDB (ID INT, NAME NVARCHAR(800)) 
    DECLARE @TMP VARCHAR(MAX), 
            @V_MIN INT,
    @V_MAX INT,
    @V_COUNT INT
    SELECT @V_MIN=MIN(ID),@V_MAX=MAX(ID) FROM #ABC 
    SET @V_COUNT=@V_MIN
    WHILE @V_COUNT<=@V_MAX
    BEGIN
    SET @TMP = '' SELECT @TMP = @TMP + CONVERT(VARCHAR,NAME) + ', ' FROM #ABC 
    WHERE ID=@V_COUNT
    INSERT INTO ##CDB (ID, NAME) SELECT @V_COUNT AS ID ,CAST(SUBSTRING(@TMP, 0, LEN(@TMP)) AS VARCHAR(8000)) AS NAME 
    SET @V_COUNT=@V_COUNT+1
    END
    SELECT * FROM ##CDB
    OR
    SELECT * INTO #ABC
    FROM 
    SELECT 1 AS ID,'NY' AS NAME
    UNION 
    SELECT 1 AS ID,'NJ' AS NAME
    UNION 
    SELECT 1 AS ID,'CT' AS NAME
    UNION 
    SELECT 2 AS ID,'MA' AS NAME
    UNION 
    SELECT 2 AS ID,'NJ' AS NAME
    UNION 
    SELECT 2 AS ID,'VA' AS NAME
    UNION 
    SELECT 3 AS ID,'FL' AS NAME
    UNION 
    SELECT 3 AS ID,'CA' AS NAME
    UNION 
    SELECT 5 AS ID,'LG' AS NAME
    UNION 
    SELECT 5 AS ID,'AP' AS NAME
    )A
    CREATE TABLE ##CDB (ID INT, NAME NVARCHAR(800)) 
    DECLARE @TMP VARCHAR(MAX), 
            @V_MIN INT,
    @V_MAX INT,
    @V_COUNT INT
    SELECT @V_MIN=MIN(ID),@V_MAX=MAX(ID) FROM #ABC 
    SET @V_COUNT=@V_MIN
    WHILE @V_COUNT<=@V_MAX
    BEGIN
    SET @TMP = '' SELECT @TMP = @TMP + CONVERT(VARCHAR,NAME) + ', ' FROM #ABC 
    WHERE ID=@V_COUNT
    SELECT @V_COUNT AS ID ,CAST(SUBSTRING(@TMP, 0, LEN(@TMP)) AS VARCHAR(8000)) AS NAME INTO #TEMP 
    INSERT INTO ##CDB (ID, NAME) SELECT ID, NAME FROM #TEMP WHERE NAME<>''
    DROP TABLE #TEMP
    SET @V_COUNT=@V_COUNT+1
    END
    SELECT * FROM ##CDB
    Thanks Shiven:) If Answer is Helpful, Please Vote

  • Multiple return values (Bug-ID 4222792)

    I had exactly the same request for the same 3 reasons: strong type safety and code correctness verification at compile-time, code readability and ease of mantenance, performance.
    Here is what Sun replied to me:
    Autoboxing and varargs are provided as part of
    JSRs 14 and 201
    http://jcp.org/en/jsr/detail?id=14
    http://jcp.org/en/jsr/detail?id=201
    See also:
    http://forum.java.sun.com/forum.jsp?forum=316
    http://developer.java.sun.com/developer/earlyAccess/adding_generics/index.html
    Multiple return values is covered by Bug-ID 4222792
    Typically this is done by returning an array.
    http://developer.java.sun.com/developer/bugParade/bugs/4222792.html
    That's exactly the problem: we dynamically create instances of array objects that would better fit well within the operand stack without stressing the garbage collector with temporary Array object instances (and with their backing store: 2 separate allocations that need to be recycled when it is clearly a pollution that the operand stack would clean up more efficiently)
    If you would like to engage in a discussion with the Java Language developers, the Generics forum would be a better place:
    http://forum.java.sun.com/forum.jsp?forum=316
    I know that (my report was already refering to the JSR for language extension) Generics is not what I was refering to (even if a generic could handle multiple return values, it would still be an allocated Object
    instance to pack them, i.e. just less convenient than using a static class for type safety.
    The most common case of multiple return values involve values that have known static datatypes and that should be checked with strong typesafety.
    The simple case that involves returning two ints then will require at least two object instances and will not solve the garbage collection overhead.
    Using a array of variable objects is exactly similar, except that it requires two instances for the components and one instance for the generic array container. Using extra method parameters with Integer, Byte, ... boxing objects is more efficient, but for now the only practical solution (which causes the least pollution in the VM allocator and garbage collector) is to use a custom class to store the return values in a single instance.
    This is not natural, and needlessly complexifies many interfaces.
    So to avoid this pollution, some solutions are used such as packing two ints into a long and returning a long, depacking the long after return (not quite clean but still much faster at run-time for methods that need to be used with high frequencies within the application. In some case, the only way to cut down the overhead is to inline methods within the caller code, and this does not help code maintenance by splitting the implementation into small methods (something that C++ can do very easily, both because it supports native types parameters by reference, and because it also supports inline methods).
    Finally, suppose we don't want to use tricky code, difficult to maintain, then we'll have to use boxing Object types to allow passing arguments by reference. Shamely boxed native types cannot be allocated on the operand stack as local variables, so we need to instanciate these local variables before call, and we loose the capacity to track the cases where these local variables are not really initialized by an effective call to the method that will assign them. This does not help debugging, and is against the concept of a strongly typed language like Java should be:
    Java makes lots of efforts to track uninitialized variables, but has no way to determine if an already instanciated Object instance refered in a local variable has effectively received an effective assignment because only the instanciation is kept. A typical code will then need to be written like this:
    Integer a = null;
    Integer b = null;
    if (some condition) {
    //call.method(a, b, 0, 1, "dummy input arg");
    // the method is supposed to have assigned a value to a and b,
    // but can't if a and b have not been instanciated, so we perform:
    call.method(a = new Integer(), b = new Integer(), 0, 1, "dummy input
    arg");
    // we must suppose that the method has modified (not initialized!)
    the value
    // of a and b instances.
    now.use(a.value(), b.value())
    // are we sure here that a and b have received a value????
    // the code may be detected at run-time (a null exception)
    // or completely undetected (the method() above was called but it
    // forgot to assign a value to its referenced objects a and b, in which
    // case we are calling in fact: now.use(0, 0); with the default values
    // or a and b, assigned when they were instanciated)
    Very tricky... Hard to debug. It would be much simpler if we just used:
    int a;
    int b;
    if (some condition) {
    (a, b) = call.method(0, 1, "dummy input arg");
    now.use(a, b);
    The compiler would immediately detect the case where a and b are in fact not always initialized (possible use bere initialization), and the first invoked call.method() would not have to check if its arguments are not null, it would not compile if it forgets to return two values in some code path...
    There's no need to provide extra boxing objects in the source as well as at run-time, and there's no stress added to the VM allocator or garbage collector simply because return values are only allocated on the perand stack by the caller, directly instanciated within the callee which MUST (checked at compile-time) create such instances by using the return statement to instanciate them, and the caller now just needs to use directly the variables which were referenced before call (here a and b). Clean and mean. And it allows strong typechecking as well (so this is a real help for programmers.
    Note that the signature of the method() above is:
    class call {
    (int, int) method(int, int, String) { ... }
    id est:
    class "call", member name "method", member type "(IILjava.lang.string;)II"
    This last signature means that the method can only be called by returning the value into a pair of variables of type int, or using the return value as a pair of actual arguments for another method call such as:
    call.method(call.method("dummy input arg"), "other dummy input arg")
    This is strongly typed and convenient to write and debug and very efficient at run-time...

    Can anyone give me some real-world examples where
    multiple return values aren't better captured in a
    class that logically groups those values? I can of
    course give hundreds of examples for why it's better
    to capture method arguments as multiple values instead
    of as one "logical object", but whenever I've hankered
    for multiple return values, I end up rethinking my
    strategy and rewriting my code to be better Object
    Oriented.I'd personally say you're usually right. There's almost always a O-O way of avoiding the situation.
    Sometimes though, you really do just want to return "two ints" from a function. There's no logical object you can think of to put them in. So you end up polluting the namespace:
    public class MyUsefulClass {
    public TwoInts calculateSomething(int a, int b, int c) {
    public static class TwoInts {
        //now, do I use two public int fields here, making it
        //in essence a struct?
       //or do I make my two ints private & final, which
       //requires a constructor & two getters?
      //and while I'm at it, is it worth implementing
      //equals(), how about hashCode()? clone()?
      //readResolve() ?
    }The answer to most of the questions for something as simple as "TwoInts" is usually "no: its not worth implementing those methods", but I still have to think about them.
    More to the point, the TwoInts class looks so ugly polluting the top level namespace like that, MyUsefulClass.TwoInts is public, that I don't think I've ever actually created that class. I always find some way to avoid it, even if the workaround is just as ugly.
    For myself, I'd like to see some simple pass-by-value "Tuple" type. My fear is it'd be abused as a way for lazy programmers to avoid creating objects when they should have a logical type for readability & maintainability.
    Anyone who has maintained code where someone has passed in all their arguments as (mutable!) Maps, Collections and/or Arrays and "returned" values by mutating those structures knows what a nightmare it can be. Which I suppose is an argument that cuts both ways: on the one hand you can say: "why add Tuples which would be another easy thing to abuse", on the other: "why not add Tuples, given Arrays and the Collections framework already allow bad programmers to produce unmainable mush. One more feature isn't going to make a difference either way".
    Ho hum.

  • Invalid navigation state. Multiple dimension values from model

    We are getting following error on the endeca server in production environment and we are not able to reproduce it in the lower environment, can some body expains what this error means and how this occurs
    WARN 03/17/13 20:59:39.418 UTC (1363553979418) DGRAPH {dgraph} Error processing HTTP exchange 797486: Invalid input : Invalid navigation state. Multiple dimension values from model (18,"Product Aisle") in query nav state.
    WARN 03/17/13 21:00:27.575 UTC (1363554027575) DGRAPH {dgraph} Error processing HTTP exchange 798401: Invalid input : Invalid navigation state. Multiple dimension values from model (18,"Product Aisle") in query nav state.
    WARN 03/17/13 21:01:31.394 UTC (1363554091394) DGRAPH {dgraph} Error processing HTTP exchange 800340: Invalid input : Invalid navigation state. Multiple dimension values from model (18,"Product Aisle") in query nav state.
    WARN 03/17/13 21:01:43.216 UTC (1363554103216) DGRAPH {dgraph} Error processing HTTP exchange 800577: Invalid input : Invalid navigation state. Multiple dimension values from model (18,"Product Aisle") in query nav state.
    WARN 03/17/13 21:02:39.912 UTC (1363554159912) DGRAPH {dgraph} Error processing HTTP exchange 801775: Invalid input : Invalid navigation state. Multiple dimension values from model (4,"Form") in query nav state.

    Hello Tijomon,
    Looking at the warning it seems the query being build is not good. Some possibilities are:
    ~ you have multi select enabled in the front end on a single select dimension
    ~ the index was moved from one environment to other and some of the dimension values do not match (due to the state being different)
    HTH,
    Pankaj.

  • How to pass a function with the same argument multiple times and return values in variables?

    The problem I have is I created a function which really is some kind of database.  Basically a bunch of:
    if (a.value == "this number"){
    b.value = "this expression";
    Inside the form are 2 dropdown lists that return numerical values which I want to process through that function and put the return value inside separate variables.
    var a = this.getField("OPE003.EVEN.1.MIP");
    Mip(a);
    var result1 = Mip();
    I tried to overwriting *a* to process the second field
    a = this.getField("OPE003.EVEN.2.MIP");
    Mip(a);
    var result2 = Mip();
    result1 and result2 are put in an array, joined as a string.
    Doing so, I always get the last processing twice as the final result.
    Can I use a function as a batch processing tool that way?

    You are right, I changed the code to what you said but how do I pass another value through my fonction so I can get Result1 and Result2?
    is it
    var a = this.getField("OPE003.EVEN.1.MIP");
    var b = this.getField("OPE003.EVEN.2.MIP");
    var result1 = Mip(a);
    var result2 = Mip(b);
    var c = new Array[result1, result2]

  • Assigning LOV return Value to multiple text items

    Hi all
    I have a custom form on which i have 10 text items
    text item 1,text item 2 ....text item10
    I have a table xx_querywith fields
    text_item,query
    i have inserted into the xx_query table
    insert into xx_query(text_item,query)
    values(text_item1,'select sysdate from dual');
    insert into xx_query(text_item,query)
    values(text_item2,'select sysdate-1 from dual');
    I have created a record group dynamically and i am getting the query from the query column of the xx_query table into the record group(say test_rg)
    I have created a LOV test_lov and thr set_lov_property i have populated the test_rg query into the test_LOV
    is it possible for me to set the return item of the LOV dynamically so that i can get the LOV on the item which i want to ?
    thanks
    _

    Hi All
    thanks for your responses
    I have Created a control item and assigned the return value of the LOV to the control item
    and i have assigned the LOV to the text item that i want
    Currently when i navigate to the text item the LOV is visible
    but when i select a value from the LOV the value is not getting populated into the text item
    I have assigned the value of the control item to the text item
    but i am not sure in which trigger to write the code so as when i select the value from the LOV the value should be shown on the form populating in the text item
    Thanks

  • LOV problem with multiple return values.

    I created a ViewObject and in it a transient attribute.
    I create a ViewAccessor for another field and a LOV for it (default InputText with Lov Value).
    In List Return Values I added also my tranient attribute in order to receive another attribute from the accesor VO.
    When I run it from the Application browser I see my transient attribute emtpty even if the "source" attribute is not empty.
    If I change the value from the LOV the source value changes bit the transient is still empty.
    What's wrong ?
    Tks
    Tullio

    Repost.

  • Multiple return values in Customized elementary search help

    Hello,
      I have a requirement when i select the value from F4 . It should populate the more than one return values in ALV grid in different rows .  
       Any FM or help search exit  is available to do this .
    Regards,
    kevin

    Hi Kevin,
    About your first question, for filling several fields of an ALV from a single F4 search help, I think that you should register F4 event to call the search help yourself (F4IF_INT_TABLE_VALUE_REQUEST for instance), and fill the ALV fields inside your F4 handler method. If you used REUSE_ALV_GRID_DISPLAY, then I am not sure how you can handle F4, but you can do it using CL_GUI_ALV_GRID or SALV classes. See BCALV_TEST_GRID_F4_HELP.
    About the second question, for filling automatically another field in the same row in the ALV grid, it should work automatically, as for normal dynpros, i.e. the search help must have these 2 fields defined as exporting, and these 2 fields of the ALV field catalog must refer to the same DDic structure, the search help must be assigned there to the field, and fill in the 2 exporting parameters too.
    Sandra

  • How to pass multiple query string values using the same parameter in Query String (URL) Filter Web Part

    Hi,
    I want to pass multiple query string values using the same parameter in Query String (URL) Filter Web Part like mentioned below:
    http://server/pages/Default.aspx?Title=Arup&Title=Ratan
    But it always return those items whose "Title" value is "Arup". It is not returned any items whose "Title" is "Ratan".
    I have followed the
    http://office.microsoft.com/en-us/sharepointserver/HA102509991033.aspx#1
    Please suggest me.
    Thanks | Arup
    THanks! Arup R(MCTS)
    SucCeSS DoEs NOT MatTer.

    Hi DH, sorry for not being clear.
    It works when I create the connection from that web part that you want to be connected with the Query String Filter Web part. So let's say you created a web part page. Then you could connect a parameterized Excel Workbook to an Excel Web Access Web Part
    (or a Performance Point Dashboard etc.) and you insert it into your page and add
    a Query String Filter Web Part . Then you can connect them by editing the Query String Filter Web Part but also by editing the Excel Web Access Web Part. And only when I created from the latter it worked
    with multiple values for one parameter. If you have any more questions let me know. See you, Ingo

  • Forecast Roll-Over Script across multiple years

    Hello Experts,
    I currently have the below Script and Prompt but it only works for one Fiscal year and I need help changing it so that it can be used across multiple years, my issue is below:
    If I have project TEST and it started in 2013.011 and ends in 2014.004, I have forecast values for all periods so when I run the script I'm prompted to "select forecast year" and "select forecast version based on previous period"
    So when I run from 2013.11 (forecast version P11) to 2013.12 (forecast version P12) that works fine but it's not working to roll-over from 2013.012 to 2014.001
    Any help is much appreciated.
    Thx,
    Shane
    *****SCRIPT*****
    //%CATEGORY_SET% - contains P9, STARTMNTH = 10, PREVFC=P8
    *SELECT(%SM%,"[STARTMNTH]",F_CATEGORY,"[ID]='%F_CATEGORY_SET%')
    //$YY$ - contain planning year selected by user from DM combobox
    *SELECT(%FCSTMNTH%,"[ID]",TIME,"[ID]>'$YY$.%SM%' AND [YEAR]='$YY$' AND [CALC]='N'")
    *SELECT(%ACTMNTH%,"[ID]",TIME,"[ID]<'$YY$.%SM%' AND [YEAR]='$YY$' AND [CALC]='N'")
    *SELECT(%PF%,"[PREVFCST]",F_CATEGORY,"[ID]='%F_CATEGORY_SET%')
    //To copy FORECAST XX we use
    *XDIM_MEMBERSET F_CATEGORY=%PF%
    *XDIM_MEMBERSET TIME=$YY$.%SM%,%FCSTMNTH%
    *WHEN F_CATEGORY
    *IS *
    *REC(EXPRESSION=%VALUE%,F_CATEGORY=%F_CATEGORY_SET%)
    *ENDWHEN
    //To copy ACTUAL we use
    *XDIM_MEMBERSET F_CATEGORY=ACTUAL
    *XDIM_MEMBERSET TIME=%ACTMNTH%
    *WHEN F_CATEGORY
    *IS *
    *REC(EXPRESSION=%VALUE%,F_CATEGORY=%F_CATEGORY_SET%)
    *ENDWHEN
    *****PROMPT*****
    PROMPT(MESSAGE,"Create Forecast Based on Previous")
    PROMPT(COMBOBOX,%YY%,"Select Forecast Year:",0,,{2014,2015,2016,2017,2018})
    PROMPT(SELECTINPUT,%SELECTION%,,"Select the Forecast Version:","F_CATEGORY")
    TASK(/CPMB/DEFAULT_FORMULAS_LOGIC,SUSER,%USER%)
    TASK(/CPMB/DEFAULT_FORMULAS_LOGIC,SAPPSET,%APPSET%)
    TASK(/CPMB/DEFAULT_FORMULAS_LOGIC,SAPP,%APP%)
    INFO(%EQU%,=)
    INFO(%TAB%,;)
    TASK(/CPMB/DEFAULT_FORMULAS_LOGIC,TAB,%TAB%)
    TASK(/CPMB/DEFAULT_FORMULAS_LOGIC,EQU,%EQU%)
    TASK(/CPMB/DEFAULT_FORMULAS_LOGIC,SELECTION,%SELECTION%)
    TASK(/CPMB/DEFAULT_FORMULAS_LOGIC,LOGICFILENAME,FORECAST.LGF)
    TASK(/CPMB/DEFAULT_FORMULAS_LOGIC,REPLACEPARAM,YY%EQU%%YY%)

    OK - I'll try explain this another way, I have 2 records for "ACTUALS" in 2013 (this is DEV system)
    1st record - Project A-000001 / 2013.010 for $2000
    2nd record - Project A-000036 / 2013.012 for $5000
    Prompts
    PARAM - YY=2013
    DATA REGION - F_CATEGORY=P12
    Here's the Script:
    //%CATEGORY_SET% - contains P9, STARTMNTH = 10, PREVFC=P8
    *SELECT(%SM%,"[STARTMNTH]",F_CATEGORY,"[ID]='%F_CATEGORY_SET%')
    //$YY$ - contain planning year selected by user from DM combobox
    *SELECT(%FCSTMNTH%,"[ID]",TIME,"[ID]>'$YY$.%SM%' AND [CALC]='N'")
    *SELECT(%ACTMNTH%,"[ID]",TIME,"[ID]<'$YY$.%SM%' AND [YEAR]='$YY$' AND [CALC]='N'")
    *SELECT(%PF%,"[PREVFCST]",F_CATEGORY,"[ID]='%F_CATEGORY_SET%')
    //To copy FORECAST XX we use
    *XDIM_MEMBERSET F_CATEGORY=%PF%
    *XDIM_MEMBERSET TIME=$YY$.%SM%,%FCSTMNTH%
    *WHEN F_CATEGORY
    *IS *
    *REC(EXPRESSION=%VALUE%,F_CATEGORY=%F_CATEGORY_SET%)
    *ENDWHEN
    //To copy ACTUAL we use
    *XDIM_MEMBERSET F_CATEGORY=ACTUAL
    *XDIM_MEMBERSET TIME=%ACTMNTH%
    *WHEN F_CATEGORY
    *IS *
    *REC(EXPRESSION=%VALUE%,F_CATEGORY=%F_CATEGORY_SET%)
    *ENDWHEN
    RESULT
    PLS note that there is only 1 record for "ACTUAL" and that's the 1st record - Project A-000001 / 2013.010 for $2000
    2nd record - Project A-000036 / 2013.012 for $5000 is MISSING
    LGX:
    *XDIM_MEMBERSET F_CATEGORY=P11
    *XDIM_MEMBERSET TIME=2013.012,2014.001,2014.002,2014.003,2014.004,2014.005,2014.006,2014.007,2014.008,2014.009,2014.010,2014.011,2014.012,2015.001,2015.002,2015.003,2015.004,2015.005,2015.006,2015.007,2015.008,2015.009,2015.010,2015.011,2015.012,2016.001,2016.002,2016.003,2016.004,2016.005,2016.006,2016.007,2016.008,2016.009,2016.010,2016.011,2016.012,2017.001,2017.002,2017.003,2017.004,2017.005,2017.006,2017.007,2017.008,2017.009,2017.010,2017.011,2017.012,2018.001,2018.002,2018.003,2018.004,2018.005,2018.006,2018.007,2018.008,2018.009,2018.010,2018.011,2018.012,2019.001,2019.002,2019.003,2019.004,2019.005,2019.006,2019.007,2019.008,2019.009,2019.010,2019.011,2019.012,2020.001,2020.002,2020.003,2020.004,2020.005,2020.006,2020.007,2020.008,2020.009,2020.010,2020.011,2020.012
    *WHEN F_CATEGORY
    *IS *
    *REC(EXPRESSION=%VALUE%,F_CATEGORY=P12)
    *ENDWHEN
    *XDIM_MEMBERSET F_CATEGORY=ACTUAL
    *XDIM_MEMBERSET TIME=2013.001,2013.002,2013.003,2013.004,2013.005,2013.006,2013.007,2013.008,2013.009,2013.010,2013.011
    *WHEN F_CATEGORY
    *IS *
    *REC(EXPRESSION=%VALUE%,F_CATEGORY=P12)
    *ENDWHEN
    LOG:
    LOG BEGIN TIME:2014-03-14 09:36:23
    FILE:\ROOT\WEBFOLDERS\F_COUNCIL \ADMINAPP\Forecasting\TEST.LGF
    USER:096655
    APPSET:F_COUNCIL
    APPLICATION:Forecasting
    [INFO] GET_DIM_LIST(): I_APPL_ID="Forecasting", #dimensions=8
    F_CATEGORY,F_ENTITY,F_PERSON,F_PROJECT,F_SECTION,F_WBSE,MEASURES,TIME
    #dim_memberset=2
    F_CATEGORY:P11,1 in total.
    TIME:2013.012,2014.001,2014.002,2014.003,2014.004,...85 in total.
    REC :%VALUE%
    CALCULATION BEGIN:
    QUERY PROCESSING DATA
    QUERY TIME : 1235.46 ms. 285  RECORDS QUERIED OUT.
    QUERY REFERENCE DATA
    CALCULATION TIME IN TOTAL :672.78 ms.
    285  RECORDS ARE GENERATED.
    CALCULATION END.
    ENDWHEN ACCUMULATION: 285  RECORDS ARE GENERATED.
    DATA TO WRITE BACK:
    F_CATEGORY    F_ENTITY    F_PERSON    F_PROJECT    F_SECTION    F_WBSE    TIME    SIGNEDDATA
    P12    4000    000000    A-000036    000    A-000036.1.01    2013.012    103.00
    P12    4000    000000    A-000036    000    A-000036.1.01    2014.001    104.00
    P12    4000    000000    A-000036    000    A-000036.1.01    2014.002    105.00
    P12    4000    000000    A-000036    000    A-000036.1.01    2014.003    106.00
    P12    4000    000000    A-000036    000    A-000036.1.01    2014.004    107.00
    P12    4000    000000    A-000036    000    A-000036.1.01    2014.005    108.00
    P12    4000    000000    A-000036    000    A-000036.1.01    2014.006    109.00
    P12    4000    000000    A-000036    000    A-000036.1.01    2014.007    110.00
    P12    4000    000000    A-000036    000    A-000036.1.01    2014.008    111.00
    P12    4000    000000    A-000036    000    A-000036.1.01    2014.009    112.00
    P12    4000    000000    A-000036    000    A-000036.1.01    2014.010    113.00
    P12    4000    000000    A-000036    000    A-000036.1.01    2014.011    114.00
    P12    4000    000000    A-000036    000    A-000036.1.01    2014.012    115.00
    P12    4000    000000    A-000036    000    A-000036.1.01    2015.001    116.00
    P12    4000    000000    A-000036    000    A-000036.1.01    2015.002    117.00
    P12    4000    000000    A-000036    000    A-000036.1.01    2015.003    118.00
    P12    4000    000000    A-000036    000    A-000036.1.01    2015.004    119.00
    P12    4000    000000    A-000036    000    A-000036.1.01    2015.005    120.00
    P12    4000    000000    A-000036    000    A-000036.1.01    2015.006    121.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01    2013.012    235.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01    2014.001    236.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01    2014.002    237.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01    2014.003    238.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01    2014.004    239.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01    2014.005    240.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01    2014.006    241.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01    2014.007    242.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01    2014.008    243.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01    2014.009    244.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01    2014.010    245.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01    2014.011    246.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01    2014.012    247.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01    2015.001    248.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01    2015.002    249.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01    2015.003    250.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01    2015.004    251.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01    2015.005    252.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01    2015.006    253.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.01    2013.012    344.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.001    345.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.002    346.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.003    347.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.004    348.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.005    349.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.006    350.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.007    351.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.008    352.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.009    353.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.010    354.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.011    355.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.012    356.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.01    2015.001    357.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.01    2015.002    358.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.01    2015.003    359.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.01    2015.004    360.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.01    2015.005    361.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.01    2015.006    362.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.02    2013.012    494.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.001    495.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.002    496.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.003    497.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.004    498.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.005    499.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.006    500.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.007    501.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.008    502.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.009    503.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.010    504.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.011    505.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.012    506.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.02    2015.001    507.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.02    2015.002    508.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.02    2015.003    509.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.02    2015.004    510.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.02    2015.005    511.00
    P12    4000    000000    A-000036    000    A-000036.1.01.01.02    2015.006    512.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02    2013.012    573.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02    2014.001    574.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02    2014.002    575.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02    2014.003    576.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02    2014.004    577.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02    2014.005    578.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02    2014.006    579.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02    2014.007    580.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02    2014.008    581.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02    2014.009    582.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02    2014.010    583.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02    2014.011    584.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02    2014.012    585.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02    2015.001    586.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02    2015.002    587.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02    2015.003    588.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02    2015.004    589.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02    2015.005    590.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02    2015.006    591.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.01    2013.012    663.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.001    664.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.002    665.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.003    666.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.004    667.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.005    668.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.006    669.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.007    670.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.008    671.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.009    672.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.010    673.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.011    674.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.012    675.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.01    2015.001    676.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.01    2015.002    677.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.01    2015.003    678.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.01    2015.004    679.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.01    2015.005    680.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.01    2015.006    404.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.02    2013.012    765.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.001    766.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.002    767.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.003    768.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.004    769.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.005    770.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.006    771.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.007    772.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.008    773.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.009    774.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.010    775.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.011    776.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.012    777.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.02    2015.001    778.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.02    2015.002    779.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.02    2015.003    780.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.02    2015.004    781.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.02    2015.005    782.00
    P12    4000    000000    A-000036    000    A-000036.1.01.02.02    2015.006    493.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03    2013.012    430.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03    2014.001    431.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03    2014.002    432.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03    2014.003    433.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03    2014.004    434.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03    2014.005    435.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03    2014.006    436.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03    2014.007    437.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03    2014.008    438.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03    2014.009    439.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03    2014.010    440.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03    2014.011    441.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03    2014.012    442.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03    2015.001    443.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03    2015.002    444.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03    2015.003    445.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03    2015.004    446.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03    2015.005    447.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03    2015.006    448.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.01    2013.012    584.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.001    585.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.002    586.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.003    587.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.004    588.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.005    589.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.006    590.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.007    591.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.008    592.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.009    593.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.010    594.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.011    595.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.012    596.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.01    2015.001    597.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.01    2015.002    598.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.01    2015.003    599.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.01    2015.004    600.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.01    2015.005    601.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.01    2015.006    602.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.02    2013.012    606.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.001    607.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.002    608.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.003    609.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.004    610.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.005    611.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.006    612.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.007    613.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.008    614.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.009    615.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.010    616.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.011    617.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.012    618.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.02    2015.001    619.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.02    2015.002    620.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.02    2015.003    621.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.02    2015.004    622.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.02    2015.005    623.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.02    2015.006    624.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.03    2013.012    824.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.001    825.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.002    826.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.003    827.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.004    828.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.005    829.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.006    830.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.007    831.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.008    832.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.009    833.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.010    834.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.011    835.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.012    836.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.03    2015.001    837.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.03    2015.002    838.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.03    2015.003    839.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.03    2015.004    840.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.03    2015.005    841.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.03    2015.006    842.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.04    2013.012    125.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.04    2014.001    126.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.04    2014.002    127.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.04    2014.003    128.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.04    2014.004    129.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.04    2014.005    130.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.04    2014.006    131.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.04    2014.007    132.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.04    2014.008    133.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.04    2014.009    134.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.04    2014.010    135.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.04    2014.011    136.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.04    2014.012    137.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.04    2015.001    138.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.04    2015.002    139.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.04    2015.003    140.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.04    2015.004    141.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.04    2015.005    142.00
    P12    4000    000000    A-000036    000    A-000036.1.01.03.04    2015.006    143.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.01    2013.012    407.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.01    2014.001    408.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.01    2014.002    409.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.01    2014.003    410.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.01    2014.004    411.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.01    2014.005    412.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.01    2014.006    413.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.01    2014.007    414.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.01    2014.008    415.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.01    2014.009    416.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.01    2014.010    417.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.01    2014.011    418.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.01    2014.012    419.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.01    2015.001    420.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.01    2015.002    421.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.01    2015.003    422.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.01    2015.004    423.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.01    2015.005    424.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.01    2015.006    425.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.02    2013.012    606.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.02    2014.001    607.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.02    2014.002    608.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.02    2014.003    609.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.02    2014.004    610.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.02    2014.005    611.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.02    2014.006    612.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.02    2014.007    613.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.02    2014.008    614.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.02    2014.009    615.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.02    2014.010    616.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.02    2014.011    617.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.02    2014.012    618.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.02    2015.001    619.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.02    2015.002    620.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.02    2015.003    621.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.02    2015.004    622.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.02    2015.005    623.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.02    2015.006    624.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.03    2013.012    726.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.03    2014.001    727.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.03    2014.002    728.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.03    2014.003    729.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.03    2014.004    730.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.03    2014.005    731.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.03    2014.006    732.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.03    2014.007    733.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.03    2014.008    734.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.03    2014.009    735.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.03    2014.010    736.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.03    2014.011    737.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.03    2014.012    738.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.03    2015.001    739.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.03    2015.002    740.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.03    2015.003    741.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.03    2015.004    742.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.03    2015.005    743.00
    P12    4000    000000    A-000036    000    A-000036.1.01.05.03    2015.006    744.00
    285  RECORDS HAVE BEEN WRITTEN BACK.
    WRITING TIME :543.97  ms.
    [INFO] GET_DIM_LIST(): I_APPL_ID="Forecasting", #dimensions=8
    F_CATEGORY,F_ENTITY,F_PERSON,F_PROJECT,F_SECTION,F_WBSE,MEASURES,TIME
    #dim_memberset=2
    F_CATEGORY:ACTUAL,1 in total.
    TIME:2013.001,2013.002,2013.003,2013.004,2013.005,...11 in total.
    REC :%VALUE%
    CALCULATION BEGIN:
    QUERY PROCESSING DATA
    QUERY TIME : 1019.73 ms. 1  RECORDS QUERIED OUT.
    QUERY REFERENCE DATA
    CALCULATION TIME IN TOTAL :140.35 ms.
    1  RECORDS ARE GENERATED.
    CALCULATION END.
    ENDWHEN ACCUMULATION: 1  RECORDS ARE GENERATED.
    DATA TO WRITE BACK:
    F_CATEGORY    F_ENTITY    F_PERSON    F_PROJECT    F_SECTION    F_WBSE    TIME    SIGNEDDATA
    P12    4000    000000    A-000001    000    A-000001.1.01    2013.010    2000.00
    1  RECORDS HAVE BEEN WRITTEN BACK.
    WRITING TIME :480.96  ms.
    SCRIPT RUNNING TIME IN TOTAL:5.07 s.
    LOG END TIME:2014-03-14 09:36:28
    Prompts
    PARAM - YY=2014
    DATA REGION - F_CATEGORY=P1
    RESULT
    PLS NOTE - The 2nd record "ACTUAL" - Project A-000036 / 2013.012 for $5000 is MISSING
    LGX:
    *XDIM_MEMBERSET F_CATEGORY=P12
    *XDIM_MEMBERSET TIME=2014.001,2014.002,2014.003,2014.004,2014.005,2014.006,2014.007,2014.008,2014.009,2014.010,2014.011,2014.012,2015.001,2015.002,2015.003,2015.004,2015.005,2015.006,2015.007,2015.008,2015.009,2015.010,2015.011,2015.012,2016.001,2016.002,2016.003,2016.004,2016.005,2016.006,2016.007,2016.008,2016.009,2016.010,2016.011,2016.012,2017.001,2017.002,2017.003,2017.004,2017.005,2017.006,2017.007,2017.008,2017.009,2017.010,2017.011,2017.012,2018.001,2018.002,2018.003,2018.004,2018.005,2018.006,2018.007,2018.008,2018.009,2018.010,2018.011,2018.012,2019.001,2019.002,2019.003,2019.004,2019.005,2019.006,2019.007,2019.008,2019.009,2019.010,2019.011,2019.012,2020.001,2020.002,2020.003,2020.004,2020.005,2020.006,2020.007,2020.008,2020.009,2020.010,2020.011,2020.012
    *WHEN F_CATEGORY
    *IS *
    *REC(EXPRESSION=%VALUE%,F_CATEGORY=P1)
    *ENDWHEN
    *XDIM_MEMBERSET F_CATEGORY=ACTUAL
    *XDIM_MEMBERSET TIME=
    *WHEN F_CATEGORY
    *IS *
    *REC(EXPRESSION=%VALUE%,F_CATEGORY=P1)
    *ENDWHEN
    LOG:
    LOG BEGIN TIME:2014-03-14 09:40:55
    FILE:\ROOT\WEBFOLDERS\F_COUNCIL \ADMINAPP\Forecasting\TEST.LGF
    USER:096655
    APPSET:F_COUNCIL
    APPLICATION:Forecasting
    [INFO] GET_DIM_LIST(): I_APPL_ID="Forecasting", #dimensions=8
    F_CATEGORY,F_ENTITY,F_PERSON,F_PROJECT,F_SECTION,F_WBSE,MEASURES,TIME
    #dim_memberset=2
    F_CATEGORY:P12,1 in total.
    TIME:2014.001,2014.002,2014.003,2014.004,2014.005,...84 in total.
    REC :%VALUE%
    CALCULATION BEGIN:
    QUERY PROCESSING DATA
    QUERY TIME : 1342.07 ms. 270  RECORDS QUERIED OUT.
    QUERY REFERENCE DATA
    CALCULATION TIME IN TOTAL :716.94 ms.
    270  RECORDS ARE GENERATED.
    CALCULATION END.
    ENDWHEN ACCUMULATION: 270  RECORDS ARE GENERATED.
    DATA TO WRITE BACK:
    F_CATEGORY    F_ENTITY    F_PERSON    F_PROJECT    F_SECTION    F_WBSE    TIME    SIGNEDDATA
    P1    4000    000000    A-000036    000    A-000036.1.01    2014.001    104.00
    P1    4000    000000    A-000036    000    A-000036.1.01    2014.002    105.00
    P1    4000    000000    A-000036    000    A-000036.1.01    2014.003    106.00
    P1    4000    000000    A-000036    000    A-000036.1.01    2014.004    107.00
    P1    4000    000000    A-000036    000    A-000036.1.01    2014.005    108.00
    P1    4000    000000    A-000036    000    A-000036.1.01    2014.006    109.00
    P1    4000    000000    A-000036    000    A-000036.1.01    2014.007    110.00
    P1    4000    000000    A-000036    000    A-000036.1.01    2014.008    111.00
    P1    4000    000000    A-000036    000    A-000036.1.01    2014.009    112.00
    P1    4000    000000    A-000036    000    A-000036.1.01    2014.010    113.00
    P1    4000    000000    A-000036    000    A-000036.1.01    2014.011    114.00
    P1    4000    000000    A-000036    000    A-000036.1.01    2014.012    115.00
    P1    4000    000000    A-000036    000    A-000036.1.01    2015.001    116.00
    P1    4000    000000    A-000036    000    A-000036.1.01    2015.002    117.00
    P1    4000    000000    A-000036    000    A-000036.1.01    2015.003    118.00
    P1    4000    000000    A-000036    000    A-000036.1.01    2015.004    119.00
    P1    4000    000000    A-000036    000    A-000036.1.01    2015.005    120.00
    P1    4000    000000    A-000036    000    A-000036.1.01    2015.006    121.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01    2014.001    236.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01    2014.002    237.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01    2014.003    238.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01    2014.004    239.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01    2014.005    240.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01    2014.006    241.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01    2014.007    242.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01    2014.008    243.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01    2014.009    244.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01    2014.010    245.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01    2014.011    246.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01    2014.012    247.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01    2015.001    248.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01    2015.002    249.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01    2015.003    250.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01    2015.004    251.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01    2015.005    252.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01    2015.006    253.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.001    345.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.002    346.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.003    347.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.004    348.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.005    349.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.006    350.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.007    351.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.008    352.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.009    353.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.010    354.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.011    355.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.01    2014.012    356.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.01    2015.001    357.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.01    2015.002    358.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.01    2015.003    359.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.01    2015.004    360.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.01    2015.005    361.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.01    2015.006    362.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.001    495.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.002    496.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.003    497.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.004    498.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.005    499.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.006    500.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.007    501.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.008    502.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.009    503.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.010    504.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.011    505.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.02    2014.012    506.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.02    2015.001    507.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.02    2015.002    508.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.02    2015.003    509.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.02    2015.004    510.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.02    2015.005    511.00
    P1    4000    000000    A-000036    000    A-000036.1.01.01.02    2015.006    512.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02    2014.001    574.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02    2014.002    575.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02    2014.003    576.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02    2014.004    577.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02    2014.005    578.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02    2014.006    579.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02    2014.007    580.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02    2014.008    581.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02    2014.009    582.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02    2014.010    583.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02    2014.011    584.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02    2014.012    585.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02    2015.001    586.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02    2015.002    587.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02    2015.003    588.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02    2015.004    589.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02    2015.005    590.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02    2015.006    591.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.001    664.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.002    665.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.003    666.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.004    667.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.005    668.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.006    669.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.007    670.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.008    671.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.009    672.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.010    673.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.011    674.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.01    2014.012    675.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.01    2015.001    676.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.01    2015.002    677.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.01    2015.003    678.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.01    2015.004    679.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.01    2015.005    680.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.01    2015.006    404.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.001    766.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.002    767.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.003    768.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.004    769.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.005    770.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.006    771.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.007    772.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.008    773.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.009    774.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.010    775.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.011    776.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.02    2014.012    777.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.02    2015.001    778.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.02    2015.002    779.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.02    2015.003    780.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.02    2015.004    781.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.02    2015.005    782.00
    P1    4000    000000    A-000036    000    A-000036.1.01.02.02    2015.006    493.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03    2014.001    431.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03    2014.002    432.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03    2014.003    433.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03    2014.004    434.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03    2014.005    435.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03    2014.006    436.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03    2014.007    437.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03    2014.008    438.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03    2014.009    439.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03    2014.010    440.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03    2014.011    441.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03    2014.012    442.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03    2015.001    443.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03    2015.002    444.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03    2015.003    445.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03    2015.004    446.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03    2015.005    447.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03    2015.006    448.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.001    585.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.002    586.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.003    587.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.004    588.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.005    589.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.006    590.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.007    591.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.008    592.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.009    593.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.010    594.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.011    595.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.01    2014.012    596.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.01    2015.001    597.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.01    2015.002    598.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.01    2015.003    599.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.01    2015.004    600.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.01    2015.005    601.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.01    2015.006    602.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.001    607.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.002    608.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.003    609.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.004    610.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.005    611.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.006    612.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.007    613.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.008    614.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.009    615.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.010    616.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.011    617.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.02    2014.012    618.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.02    2015.001    619.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.02    2015.002    620.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.02    2015.003    621.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.02    2015.004    622.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.02    2015.005    623.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.02    2015.006    624.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.001    825.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.002    826.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.003    827.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.004    828.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.005    829.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.006    830.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.007    831.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.008    832.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.009    833.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.010    834.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.011    835.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.03    2014.012    836.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.03    2015.001    837.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.03    2015.002    838.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.03    2015.003    839.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.03    2015.004    840.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.03    2015.005    841.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.03    2015.006    842.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.04    2014.001    126.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.04    2014.002    127.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.04    2014.003    128.00
    P1    4000    000000    A-000036    000    A-000036.1.01.03.04    2014.004 

  • Tag instances - same instance being used across multiple tags

    Hi
              I am using BEA WebLogic Server 6.1 SP2
              Problem:
              Tag instances - same instance being used across multiple tags
              The problem is that when I use the same jsp tag several times in a page,
              The tag is being instantiated only one time, as a result the class
              attributes
              retain their values when activating the tags.
              Example:
              A code that demonstrates the problem (not sure that it is compiled)
              public FooTag extends TagSupport {
              private boolean isValid = true;
              private String name;
              public setName(String x){
              name = x;
              public int doStartTag() throws JspException
              if (name.equals("x"){
              isValid = false;
              return SKIP_BODY;
              public int doEndTag() {
              if (isValid){
              return EVAL_PAGE;
              <table>
              <tr>
              <td><mpower:FOOTAG name="x"/>
              <!-- isValid attribute is set to false -->
              A FOOTAG implmented in FooTag </td>
              </tr>
              <tr>
              <td><mpower:FOOTAG name="y"/>
              <!-- isValid attribute still false (we expected it to be true) ! -->
              A FOOTAG implmented in FooTag </td>
              </tr>
              </table>
              P.S.
              I am using the same tags library with Tomcat and iPlanet Application severs,
              I did not get this problem there !!
              

              What should I do to reinitialize the tag? We have the same problem on custom tag.
              We have TabSet tag, which contains a set of Tab tag. In Weblogic 5.1, everything
              works ok, however when we run it in weblogic 6.1, Tab object seems like share the
              same instance, say if I have 2 Tabs in the TabSet, it ends up shows 2 same tabs with
              the apperance of the last tab added to the tabset on the web browser. We do implement
              release() method to call super.release() of TagSupport class.
              Any help is very appreciated.
              Thanks,
              Kimberly
              "Simon Spruzen" <[email protected]> wrote:
              >
              >This is allowed. You must implement public void release() on your tag, and
              >WLS will
              >call it before this method if WLS elects to reuse the tag instance. Your
              >release
              >method just reinitialises the tag as required.
              >
              >simon.
              >
              >"Eyal H" <[email protected]> wrote:
              >>Hi
              >>
              >>I am using BEA WebLogic Server 6.1 SP2
              >>
              >>Problem:
              >>
              >>Tag instances - same instance being used across multiple tags
              >>
              >>The problem is that when I use the same jsp tag several times in a page,
              >>
              >>The tag is being instantiated only one time, as a result the class
              >>
              >>attributes
              >>
              >>retain their values when activating the tags.
              >>
              >>Example:
              >>
              >>A code that demonstrates the problem (not sure that it is compiled)
              >>
              >>public FooTag extends TagSupport {
              >>
              >>private boolean isValid = true;
              >>
              >>private String name;
              >>
              >>public setName(String x){
              >>
              >>name = x;
              >>
              >>}
              >>
              >>public int doStartTag() throws JspException
              >>
              >>if (name.equals("x"){
              >>
              >>isValid = false;
              >>
              >>}
              >>
              >>return SKIP_BODY;
              >>
              >>}
              >>
              >>public int doEndTag() {
              >>
              >>if (isValid){
              >>
              >>......
              >>
              >>}
              >>
              >>return EVAL_PAGE;
              >>
              >>}
              >>
              >>}
              >>
              >>
              >>
              >>
              >>
              >><table>
              >>
              >><tr>
              >>
              >><td><mpower:FOOTAG name="x"/>
              >>
              >><!-- isValid attribute is set to false -->
              >>
              >>A FOOTAG implmented in FooTag </td>
              >>
              >></tr>
              >>
              >><tr>
              >>
              >><td><mpower:FOOTAG name="y"/>
              >>
              >><!-- isValid attribute still false (we expected it to be true) ! -->
              >>
              >>A FOOTAG implmented in FooTag </td>
              >>
              >></tr>
              >>
              >></table>
              >>
              >>
              >>
              >>P.S.
              >>
              >>I am using the same tags library with Tomcat and iPlanet Application severs,
              >>
              >>I did not get this problem there !!
              >>
              >>
              >>
              >
              

Maybe you are looking for

  • Payment advice problem in F-30. Awaiting for your great reply....

    Hi, Can anyone let me know how should i make payment advice in F-30. I have a problem while making payment advice in TC: FBE1. in FBE1, if i can fill document no. field as invoice no. then while doing F-30 system will clear respective invoice automat

  • Backup on External Hard Drive

    Hi, Just wondering, if I were to buy an external HDD to take my backup for the MAC, would it also be possible to use the same external hard drive to take a backup of two machines - one a MAC and another a Linux system. OR does the HDD only allow one.

  • Use of multiple components in ABAP WEB DYNPRO

    Hi, Am  new to  abap web dynpro and I just want to know whether  we  can  use  multiple components for an application in web dynpro. Thanks , Dhaya.G Edited by: Dhayalinie Ganesh on Feb 22, 2012 12:06 PM

  • UDF are not populating in design console

    Hi, I have created UDF in admin console and mapped then in self service form as well. Fields are now reflecting in the user creation form. I have also published the sand box but these fields are not populating in design console. Please help me in res

  • Page Navigation Woes

    So I love this tool, and desperately need it for my project. I'm a huge fan. BUT - I have troubles with what appeared to me to be a JSF idiom re: navigation. I have had to add by hand (in the source view) of my page navigation something like: <naviga