Consequences of using unconstrained query variables?

I'm trying to determine what the consequences are (if any) of using
unconstrained query variables vs using variables with a contains clause in
order to navigate through collection fields.
In the Java Data Objects book the example given for collection field
navigation is as follows...
String filter = "customer.orders.contains(o) && o.dispatched == false";
q.declareVariables("Order o");
Using uncontrained variables this could be rewritten as...
String filter = "customer.orders.dispatched == false";
I'm using kodo 2.5.5 and need to navigate through multiple collection
fields. It is far simpler and easier for me to do this using the second
example above, but I can't find any documentation describing whether its a
good idea or not. So far the queries generated are correct.
Regards
Nathan

Hi Marc,
Using the query form with the variable is portable at present, but I can't
help wonder whether the spec will change in the future to make using QL
simpler. All of the examples given in both the JDO book and Kodo
documenation only ever demonstrate the simplest example. Trying to construct
a query that spans multiple collections is very time consuming as the
smallest error in the QL seems to result in "red herring" error messages.
I've constructed and example for you that uses both methods and produces
exactly the same SQL. I'm very tempted to continue using the unconstrained
method because it works and is so simple. Note that in the generated SQL,
the reason that the table "BOA" is joined to most of the other tables is due
to vertical inheritance. The example data model is a very cut down diagram
purely to show the relationships.
"Marc Prud'hommeaux" <[email protected]> wrote in message
news:[email protected]...
Nathan-
You should use the query form with the variable, since it is portable
and spec compliant.
I'm actually a little surprised that the second filter works at all.
What is the SQL that results from both the queries?
In article <[email protected]>, nathan boyes wrote:
I'm trying to determine what the consequences are (if any) of using
unconstrained query variables vs using variables with a contains clause
in
order to navigate through collection fields.
In the Java Data Objects book the example given for collection field
navigation is as follows...
String filter = "customer.orders.contains(o) && o.dispatched == false";
q.declareVariables("Order o");
Using uncontrained variables this could be rewritten as...
String filter = "customer.orders.dispatched == false";
I'm using kodo 2.5.5 and need to navigate through multiple collection
fields. It is far simpler and easier for me to do this using the second
example above, but I can't find any documentation describing whether itsa
good idea or not. So far the queries generated are correct.
Regards
Nathan
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com
begin 666 query syntax.txt
M"7!R:79A=&4@=F]I9"!P<F]J96-T475E<GE5;F-O;G-T<F%I;F5D*$ET96T@
M:71E;2E[#0H)"0T*"0E%>'1E;G0@97@@/2!C;VYT97AT+F=E=%!E<G-I<W0H
M*2YG971%>'1E;G0H4')O:F5C="YC;&%S<RP@=')U92D[#0H)"5%U97)Y('$[
M#0H)"4-O;&QE8W1I;VX@8V]L(#T@;G5L;#L-"@D)4W1R:6YG0G5F9F5R(&9I
M;'1E<B ](&YE=R!3=')I;F="=69F97(H*3L-"@T*"0EF:6QT97(N87!P96YD
M*")H;VUE1F]L9&5R+G)O;W1&;VQD97(N:6YD:7)E8W1#:&EL9')E;BYF;VQD
M97))=&5M<RYI=&5M(#T]('!A<DET96TB*3L-"@D)#0H)"7$@/2!C;VYT97AT
M+F=E=%!E<G-I<W0H*2YN97=1=65R>2AE>"D[#0H)"7$N9&5C;&%R94EM<&]R
M=',H(FEM<&]R="!A82YC;W)R97-P;VYD96YC92Y)=&5M.R(I.PT*"0EQ+F1E
M8VQA<F5087)A;65T97)S*"))=&5M('!A<DET96TB*3L-"@D)<2YS971&:6QT
M97(@*&9I;'1E<BYT;U-T<FEN9R@I*3L-"@D)#0H)"6-O;" ]("A#;VQL96-T
M:6]N*2!Q+F5X96-U=&4H:71E;2D[#0H)"0T*"7T-"@T*"7!R:79A=&4@=F]I
M9"!P<F]J96-T475E<GE5<VEN9U9A<FEA8FQE<RA)=&5M(&ET96TI>PT*"0D-
M"@D)17AT96YT(&5X(#T@8V]N=&5X="YG971097)S:7-T*"DN9V5T17AT96YT
M*%!R;VIE8W0N8VQA<W,L('1R=64I.PT*"0E1=65R>2!Q.PT*"0E#;VQL96-T
M:6]N(&-O;" ](&YU;&P[#0H-"@D)4W1R:6YG0G5F9F5R(&9I;'1E<B ](&YE
M=R!3=')I;F="=69F97(H*3L-"@D)4W1R:6YG0G5F9F5R(&EM<&]R=',@/2!N
M97<@4W1R:6YG0G5F9F5R*"D[#0H)"5-T<FEN9T)U9F9E<B!V87)I86)L97,@
M/2!N97<@4W1R:6YG0G5F9F5R*"D[#0H)"0T*"0EI;7!O<G1S+F%P<&5N9"@B
M:6UP;W)T(&%A+F-O<G)E<W!O;F1E;F-E+DET96T[("(I.PT*"0EI;7!O<G1S
M+F%P<&5N9"@B:6UP;W)T(&%A+F9O;&1E<BY&;VQD97))=&5M.R B*3L-"@D)
M:6UP;W)T<RYA<'!E;F0H(FEM<&]R="!A82YF;VQD97(N1F]L9&5R.R(I.PT*
M#0H)"79A<FEA8FQE<RYA<'!E;F0H(D9O;&1E<B!V87));F1I<F5C=$-H:6QD
M1F]L9&5R.R(I.PT*"0EV87)I86)L97,N87!P96YD*")&;VQD97))=&5M('9A
M<D9O;&1E<DET96TB*3L-"@D)"0D-"@D)9FEL=&5R+F%P<&5N9"@B:&]M949O
M;&1E<BYR;V]T1F]L9&5R+FEN9&ER96-T0VAI;&1R96XN8V]N=&%I;G,H=F%R
M26YD:7)E8W1#:&EL9$9O;&1E<BD@)B8@(BD[#0H)"69I;'1E<BYA<'!E;F0H
M(G9A<DEN9&ER96-T0VAI;&1&;VQD97(N9F]L9&5R271E;7,N8V]N=&%I;G,H
M=F%R1F]L9&5R271E;2D@)B8@(BD[#0H)"69I;'1E<BYA<'!E;F0H(G9A<D9O
M;&1E<DET96TN:71E;2 ]/2!P87))=&5M(BD[#0H)"0T*"0EQ(#T@8V]N=&5X
M="YG971097)S:7-T*"DN;F5W475E<[email protected]*"0EQ+F1E8VQA<F5);7!O
M<G1S*&EM<&]R=',N=&]3=')I;F<H*2D[#0H)"7$N9&5C;&%R95!A<F%M971E
M<G,H(DET96T@<&%R271E;2(I.PT*"0EQ+F1E8VQA<F5687)I86)L97,H=F%R
M:6%B;&5S+G1O4W1R:6YG*"DI.PT*"0EQ+G-E=$9I;'1E<B H9FEL=&5R+G1O
M4W1R:6YG*"DI.PT*"0D-"@D)8V]L(#T@*$-O;&QE8W1I;VXI('$N97AE8W5T
692AI=&5M*3L-"@D)#0H)"0T*"7T-"@``
`
end
begin 666 generatedQuery.sql
M4T5,14-4($1)4U1)3D-4( T*"70P+DE$+" -"@ET,2Y*1$]#3$%34U@L( T*
M"70Q+DI$3TQ/0TM8+" -"@ET,2Y#55)214Y404Q415)!5$E/3DE$+" -"@ET
M,"Y!0U1)5D5?1"P@#0H)=# N8V]M<&]N96YT260L( T*"70P+F1A=&52;VQE
M365M8F5R<TUO9&EF:65D7V0L( T*"70P+DAO;65&;VQD97))1"P@#0H)=# N
M3U))1TE.04Q04D]*14-4240L( T*"70P+G!R;VIE8W13=&%T=7,L( T*"70P
M+E)%1D5214Y#15]$+" -"@ET,"Y32$]25$1%4T-27T0@#0I&4D]-( T*"5!2
M3TI%0U0@=# @24Y.15(@2D])3B -"@E"3T$@=#$@3TX@=# N240@/2!T,2Y)
M1"!)3DY%4B!*3TE.( T*"4A/345&3TQ$15(@=#(@3TX@=# N2&]M949O;&1E
M<DE$(#T@=#([email protected](@2D])3B -"@E"3T$@=#,@3TX@=#(N240@/2!T
M,RY)1"!)3DY%4B!*3TE.( T*"49/3$1%4B!T-"!/3B!T,BYR;V]T1F]L9&5R
M240@/2!T-"Y)1"!)3DY%4B!*3TE.( T*"4)/02!T-2!/3B!T-"Y)1" ]('0U
M+DE$($E.3D52($I/24X@#0H)26YD:7)E8W1#:&EL9$9O;&1E<B!T-B!/3B!T
M-"Y)1" ]('0V+FEN9&ER96-T4&%[email protected](@2D])3B -"@E&3TQ$
M15(@=#<@3TX@=#8N:6YD:7)E8W1#:&EL9$ED(#T@=#<[email protected](@2D])
M3B -"@E"3T$@=#@@3TX@=#<N240@/2!T."Y)1"!)3DY%4B!*3TE.( T*"49/
M3$1%4DE414T@=#D@3TX@=#<N240@/2!T.2YP87)E;G1F;VQD97)I9"!)3DY%
M4B!*3TE.( T*"4)/02!T,3 @3TX@=#DN240@/2!T,3 N240@#0I72$5212 -
M"@DH=#DN:71E;6ED(#T@/RD@04Y$( T*"70Q+DI$3T-,05-36" ](#\I.B!;
M<F5U<V5D/3$[<&%R86US/7LH:6YT*3,Q,3$L*%-T<FEN9REC;VTN;6%L;&5S
C;VYS+G-E<G9I8V5N970N86$N<')O:F5C="Y0<F]J96-T?5T`
`
end
begin 666 example datamodel.doc
MT,\1X*&Q&N$`````````````````````/@`#`/[_"0`&```````````````!
M````(@``````````$ ``) ````$```#^____`````"$```#_____________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M____________________________________________________________
M_______________________LI<$`"R )! ``\!*_````````$ ``````! ``
M?@0```X`8FIB:N `X `````````````````````````)!!8`+@P``()J`0""
M:@$`% ``````````````````````````````:0````````#__P\`````````
M``#__P\```````````#__P\``````````````````````&P``````*@`````
M````J ```*@`````````J `````````8`@```````!@"````````& (``!0`
M`````````````$P"````````? (```````!\`@```````'P"````````? (`
M``P```"(`@``# ```$P"````````X@X``+8```"@`@```````* "````````
MH (```````"@`@```````* "````````A0L```````"%"P```````(4+````
M````80X```(```!C#@```````&,.````````8PX```````!C#@```````&,.
M````````8PX``"0```"8#P``( (``+@1``!&````APX``!4`````````````
M````````````& (```````"%"P````````````````````````````!'"0``
M/@(``(4+````````A0L```````"%"P```````(<.````````40P```````"H
M`````````*@`````````H (``````````````````* "``"G!@``G X``!8`
M``!1# ```````%$,````````40P```````"%"P``0 ```*@````(`0``H (`
M```````8`@```````* "````````80X``````````````````%$,````````
M````````````````````````````````````````````````````````````
M````A0L```````!A#@```````%$,```0`@``40P``````````````````&$.
M````````L $``&@````8`@``````````````````````````````````````
M````````````````````````````````````````````80X```````"@`@``
M`````)0"```,````,*'_R.K3PP%,`@``, ```'P"````````Q0L``#H```!A
M#@``````````````````80X```````"R#@``, ```.(.````````80X`````
M``#^$0```````/\+``!2````_A$```````!A#@```````%$,````````+ (`
M`!(````^`@``#@```*@`````````J ````````"H`````````*@`````````
M`@#9````" @(" @(" @(" @(" @(" @(" UP<F]J96-T#0UH;VUE1F]L9&5R
M#0U2;V]T1F]L9&5R("A&;VQD97(@;V)J96-T*0T-26YD:7)E8W1#:&EL9')E
M;B H1F]L9&5R(&]B:F5C="D-#69O;&1E<DET96T-#6ET96T-#0T-#0T-````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````! ``$P0``'X$``#Q````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M`````````````!P#:@````!#2A0`50@!;4@`!&Y(``1S2 D$=0@!`@`$```4
M! ``' 0``!T$```H! ``*00``$0$``!%! ``9@0``&<$``!R! ``<P0``'@$
M``!Y! ``>@0``'L$``!\! ``?00``'X$``#]````````````````_0``````
M`````````/T```````````````#]````````````````_0``````````````
M`/T```````````````#]````````````````_0```````````````/T`````
M``````````#]````````````````_0```````````````/T`````````````
M``#]````````````````_0```````````````/T```````````````#]````
M````````````_0```````````````/T`````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M``````````$````2``0``!0$``!]! ``_?T`````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M```````````````````````````````$! `!`0(L`#&0: $?L((N(+#&02&P
M" <BL @'(Y"@!220H 4EL ``%[#$`ABPQ (,D,0"````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````% `/``H``0!I``\``P```````````#@``$#Q
M_P(`. `,``8`3@!O`'(`;0!A`&P````"````& !#2A@`7T@!!&%*& !M2 D,
M<T@)#'1("00````````````````````````\`$% \O^A`#P`# `6`$0`90!F
M`&$`=0!L`'0`( !0`&$`<@!A`&<`<@!A`' `: `@`$8`;P!N`'0`````````
M``````````````D````5````,0```%,```!?````90```&8```!G````: ``
M`'X````!````````````_____P($`````````0```````````/____\#! ``
M``````$```````````#_____! 0````````!````````````_____P4$````
M`````0```````````/____\&! ````````$```````````#_____!P0`````
M```(`````0````$`_____P``````````!@````(````!`/____\`````````
M`/____\``````0#_____```````````'`````P``````````````````````
M``````D````5````,0```%,```!?````90```&8```!G````: ```&L`````
M```````!```````"```````#```````$```````%```````&``````@'````
M``@(``````C__P``````````?@````0```P```4`_____P$````&(/__`0`B
M)J,```````````!^`````````````````!0```!_````G@``````````````
M`( ```" F@```````````````( ```" ``0``'X$```#``````0``'X$```$
M``````0``'T$```%````#P``\#@```````;P& ```"($```"````& ````$`
M```!````(@```$ `'O$0````__\`````_P" @( `]P``$ `/``+P7@8``! `
M"/ (````% ```"$$```/``/P_ 4```\`!/ H`````0`)\! `````````````
M`````````````@`*\ @`````! ``!0````\`!/!"````$@`*\ @````"! ``
M``H``!,`"_ &````@ ````$````0\ 0````/```````1\ 0````$```````-
M\ 0```````$`#P`$\$(````2``KP" ````,$````"@``$P`+\ 8```" ````
M`@```!#P! ```! ``````!'P! ````4```````WP! ```````@`/``3P0@``
M`!(`"O (````! 0````*```3``OP!@```( ````#````$/ $`````0``````
M$? $````#0``````#? $```````#``\`!/!"````$@`*\ @````%! ````H`
M`!,`"_ &````@ ````0````0\ 0````````````1\ 0````-```````-\ 0`
M``````0`#P`$\$(````2``KP" ````8$````"@``$P`+\ 8```" ````!0``
M`!#P! ```!$``````!'P! ````H```````WP! ``````!0`/``3P0@```!(`
M"O (````!P0````*```3``OP!@```( ````&````$/ $````$@``````$? $
M````"P``````#? $```````&``\`!/!(````0@$*\ @````)! ````H``$,`
M"_ 8````1 $$````?P$```$`OP$``! `_P$0`! ````0\ 0````.```````1
M\ 0````#````#P`$\$@```!"`0KP" ````H$````"@``0P`+\!@```!$`00`
M``!_`0```0"_`0``$ #_`1 `$ ```!#P! ````T``````!'P! ````,````/
M``3P2 ```$(!"O (````"P0````*``!#``OP& ```$0!! ```'\!```!`+\!
M```0`/\!$ `0````$/ $````# ``````$? $`````P````\`!/!(````0@$*
M\ @````,! ````H``$,`"_ 8````1 $$````?P$```$`OP$``! `_P$0`! `
M```0\ 0````+```````1\ 0````#````#P`$\$@```!"`0KP" ````T$````
M"@``0P`+\!@```!$`00```!_`0```0"_`0``$ #_`1 `$ ```!#P! ````H`
M`````!'P! ````,````/``3P2 ```$(!"O (````& 0``$ *``!#``OP& ``
M`$0!! ```'\!```!`+\!```0`/\!$ `0````$/ $````" ``````$? $````
M!0````\`!/!(````0@$*\ @````9! ````H``$,`"_ 8````1 $$````?P$`
M``$`OP$``! `_P$0`! ````0\ 0````)```````1\ 0````&````#P`$\$@`
M``!"`0KP" ```!L$``! "@``0P`+\!@```!$`00```!_`0```0"_`0``$ #_
M`1 `$ ```!#P! ````<``````!'P! ````4````/``3P2 ```$(!"O (````
M' 0````*``!#``OP& ```$0!! ```'\!```!`+\!```0`/\!$ `0````$/ $
M````!@``````$? $````!0````\`!/!(````0@$*\ @````=! ````H``$,`
M"_ 8````1 $$````?P$```$`OP$``! `_P$0`! ````0\ 0````%```````1
M\ 0````%````#P`$\$@```!"`0KP" ```!X$``! "@``0P`+\!@```!$`00`
M``!_`0```0"_`0``$ #_`1 `$ ```!#P! ````0``````!'P! ````4````/
M``3P2 ```$(!"O (````'P0````*``!#``OP& ```$0!! ```'\!```!`+\!
M```0`/\!$ `0````$/ $`````P``````$? $````!0````\`!/!(````0@$*
M\ @````@! ``0 H``$,`"_ 8````1 $$````?P$```$`OP$``! `_P$0`! `
M```0\ 0````"```````1\ 0````%````#P`$\$(````2``KP" ````$$````
M#@``4P`+\!X```"_`0``$ #+`0````#_`0``" `$`PD````_`P$``0```!'P
M! ````$``````````0````(````#````! ````4````&````!P````@````)
M````"@````L````,````#0````X````/````$ ```!$````2````?@````4$
M```(!P``S!4``&04``#H%P``= ``````! 0```@'```L$ ``_!(``$@2``!T
M```````@! ``) D``&P;``#8"0``(!P``'0``````!\$``#8"0``;!L``(P*
M```@' ``= ``````'@0``"0)```8%0``V D``,P5``!T```````=! ``V D`
M`!@5``","@``S!4``'0``````!P$```D"0``/!X``-@)``#P'@``= ``````
M&P0``-@)```\'@``C H``/ >``!T```````8! ``V D``$@2``","@``_!(`
M`'0``````!D$```D"0``2!(``-@)``#\$@``= ``````#00``-@)```\'@``
MV D``'0B``!T```````,! ``V D``.@7``#8"0``(!P``'0```````L$``#8
M"0``2!(``-@)``#,%0``= ``````"@0``-@)``"H# ``V D``"P0``!T````
M```)! ``V D``%0&``#8"0``C H``'0```````($```(!P``. 0``%P-``!4
M!@``= ```````P0```@'``","@``7 T``*@,``!T```````&! ``" <``" <
M``!<#0``/!X``'0```````<$```(!P``="(``%P-``"0) ``= ``````````
M`!0````=````)P```"D````S````10```%4```!G````<0```'\````'``<`
M' `'`!P`!P`<``<`' `'```````4````&P```!T````G````9P```'$```!S
M````=P```'\````'`#H`!P`Z``<`.@`'`#H`!P````````````$````!````
M`@````H````1````$0```!,````4````&P```!T```!\````?P````0``P`$
M``,`! `#``0``P`'``0``P`$``,`__\&````!P!N`&$`8@!O`'D`90!S`&P`
M0P`Z`%P`1 !O`&,`=0!M`&4`;@!T`',`( !A`&X`9 `@`%,`90!T`'0`:0!N
M`&<`<P!<`&X`80!B`&\`>0!E`',`7 !!`' `< !L`&D`8P!A`'0`:0!O`&X`
M( !$`&$`= !A`%P`30!I`&,`<@!O`',`;P!F`'0`7 !7`&\`<@!D`%P`00!U
M`'0`;P!2`&4`8P!O`'8`90!R`'D`( !S`&$`=@!E`" `;P!F`" `90!X`&$`
M;0!P`&P`90`@`&0`80!T`&$`;0!O`&0`90!L`"X`80!S`&0`!P!N`&$`8@!O
M`'D`90!S`#\`0P`Z`%P`1 !O`&,`=0!M`&4`;@!T`',`( !A`&X`9 `@`%,`
M90!T`'0`:0!N`&<`<P!<`&X`80!B`&\`>0!E`',`7 !$`&4`<P!K`'0`;P!P
M`%P`90!X`&$`;0!P`&P`90`@`&0`80!T`&$`;0!O`&0`90!L`"X`9 !O`&,`
M!P!N`&$`8@!O`'D`90!S`#\`0P`Z`%P`1 !O`&,`=0!M`&4`;@!T`',`( !A
M`&X`9 `@`%,`90!T`'0`:0!N`&<`<P!<`&X`80!B`&\`>0!E`',`7 !$`&4`
M<P!K`'0`;P!P`%P`90!X`&$`;0!P`&P`90`@`&0`80!T`&$`;0!O`&0`90!L
M`"X`9 !O`&,`_T #@ $````````````0`/(#`0`!````````````````````
M```"$ ````````!^````0 ``" ! ``#__P$````'`%4`;@!K`&X`;P!W`&X`
M__\!``@``````````````/__`0``````__\```(`__\`````__\```(`__\`
M`````P```$<6D $```("!@,%! 4"`P2'>@`@````@ @`````````_P$`````
M``!4`&D`;0!E`',`( !.`&4`=P`@`%(`;P!M`&$`;@```#46D $"``4%`0(!
M!P8"!0<`````````$ ``````````````@ ````!3`'D`;0!B`&\`; ```#,F
MD $```(+!@0"`@("`@2'>@`@````@ @`````````_P$```````!!`'(`:0!A
M`&P````B``0`<0B(& #PT (``&@!`````-,R@4;3,H%&``````,`!P``````
M`````````0`!````! `#$ $```````````````$``0````$`````````(0,`
M\! `````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M" >@!;0`M "!@3(P````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M``````(```!3`P``````,H,1`/ 0``@`````````````````````````````
M````````````__\2````````````````````!P!N`&$`8@!O`'D`90!S``<`
M;@!A`&(`;P!Y`&4`<P``````````````````````````````_O\```4!`@``
M`````````````````````0```."%G_+Y3V@0JY$(`"LGL]DP````5 $``! `
M```!````B ````(```"0`````P```)P````$````J ````4```"X````!P``
M`,0````(````V ````D```#H````$@```/0````*````$ $```P````<`0``
M#0```"@!```.````- $```\````\`0``$ ```$0!```3````3 $```(```#D
M! ``'@````$``````',`'@````$``````',`'@````@```!N86)O>65S`!X`
M```!`````&%B;QX````+````3F]R;6%L+F1O= ``'@````@```!N86)O>65S
M`!X````"````,P!B;QX````3````36EC<F]S;V9T(%=O<[email protected]``! ````
M`.I6^@````! `````/* KNK3PP% `````/* KNK3PP$#`````0````,`````
M`````P`````````#````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M`````````````````````````````````````````````````/[_```%`0(`
M``````````````````````$````"U<W5G"X;$).7" `K+/FN, `````!```,
M`````0```&@````/````< ````4```"4````!@```)P````1````I ```!<`
M``"L````"P```+0````0````O ```!,```#$````%@```,P````-````U ``
M``P```#A`````@```.0$```>````&@```$UA;&QE<V]N<R!3=&5P:&5N($IA
M8W%U97,`( `#`````0````,````!`````P`````````#````#AL)``L`````
M````"P`````````+``````````L`````````'A ```$````!``````P0```"
M````'@````8```!4:71L90`#`````0``````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M```````````````````````````````````````````````````!`````@``
M``,````$````!0````8````'````_O___PD````*````"P````P````-````
M#@````\````0````_O___Q(````3````% ```!4````6````%P```!@```#^
M____&@```!L````<````'0```!X````?````( ```/[____]____(P```/[_
M___^_____O____________

Similar Messages

WebI Prompts using BEx Query Variables

Hello,
I have the following issues with WebI report selection input paramaters (prompts) that use BW BEx Query variables. Could anyone please assist?
Issue 1:
The WebI report has one mandatory and two optional input paramaters (all paramaters from BW BEx Query). When I execute the report via WebI rich client directly, enter the value for mandatory input parameter and leave blanks for both optional input parameters, the report ran OK and has no issue. However, when I ran it through CMC a strange thing happen: I could not select the value for mandatory input paramater as it requires to have values for both optional input paramaters first (which I wish to have them blank and optional). When I refersh values for the mandatory paramater, it says "List of Values for current prompt requires values for following prompts:...(ie. the two optional parameters).
Anyone has any idea - it seems like it is a CMC issue for the WebI...
Issue 2:
Take the same WebI report above, the issue here is the order sequence of the prompts (ie. the selection input parameters). How can we change/control the sequence of the prompts? Whatever sequence of the varaiables (input paramters) in BW BEx Query, the WebI ignores it. Please advise.
Thanks & Regards,
Andy

I did not see separate thread for issue #1, therefore I'll us this thread.
I am running into similar issue when I get an error message ''List of Values for current prompt requires values for following prompts: <Name of the prompt>".
We are using BO V4, SP2, Patch 10 with SAP BW as DB via BEx queries.
I opened support ticket for this issue since obviousely it's still an issue after applying patch 10.
It's not an issue when 'Rich Internet Application' option is selected to view report in 'Reading' mode (via Launchpad Preferences then Web Inteligence; defautl value for viewing is 'Web').
I have not tried to use Client tools but even if it works with Client tools - it is not a solution for us. Our company does not plan to install client tools on end user computers.
Bigger issue us is that report scheduling invokes Web version (not Rich Internet Application). Therefore we cannot schedule report that is giving us problem described. I tried scheduling report from Launchpad and from CMC and both game me error highlighted.

BW Authorizations - Query variable with processing mode as "customer exit"

Hi,
Iam new to BW authorizations and have not yet worked on customer exit before. I was going through the documentation at various sites but I could not get the end to end description on how the query process( when using a variable for an InfoObject) works in case of customer exit.
Let's assume that I am using a query variable with processing mode as "customer exit" and at the exit I write some code to extract user's authorizations from a z table. if this is the case, then when an end user runs a query,how will the the system know what value needs to be filled in the variable for the requesting user. Are the user details also sent to the code along with the query variable? If so how. If I mis-understood the process then forgive me and let me know the correct process.

Hi!
welcome to SDN!
customer exit variables need programing by user. so if you create a customer exit variable, you got to right a program which extracts values into this variable. we can do what ever we want in program, SAP will not deal anything ´with customer exits.
with regards
ashwin
PS n: Assigning point to the helpful answers is the way of saying thanks in SDN. you can assign points by clicking on the appropriate radio button displayed next to the answers for your question. yellow for 2, green for 6 points(2)and blue for 10 points and to close the question and marked as problem solved. closing the threads which has a solution will help the members to deal with open issues with out wasting time on problems which has a solution and also to the people who encounter the same porblem in future. This is just to give you information as you are a new user.

Search query variable not working

Apologies for this essay but I felt it may be best if I include all the details in order to describe the issue I'm experiencing.
I have two site collections in one web app called Library and Store respectively. The library site collection has a content type called Book which is made available to the Store site collection through the content type syndication. The Book content type
has a site column in it called Book Author which is of managed metadata type (the term set has a few terms representing authors). The parent content type of the Book is the out of the box Article Page and the Store site collection has custom page layout associated
with the Book content type.
I then add a page and switch its page layout to my custom layout based on the Book content type and on the page, I put a content search web part. I have a managed property called BookAuthor which is mapped to the crawled property pointing at the Book Author
field and this is where things start to go awry. The query I use in the content search web part looks something like this:
ContentType:Book BookAuthor:{Page.Book Author}
According to the documentation of the query variables and FQL (http://technet.microsoft.com/en-us/library/jj683123(v=office.15).aspx), this should return items that are of the Book content type where the BookAuthor is the value of the Book Author field on
the current page that the content search web part resides on. In this case, my query returns no results. In order to test if it actually works, I manually typed in the value of the author for the BookAuthor property so it looked something like this:
ContentType:Book BookAuthor:John Doe
The second query returned the results I expected, but the first one didn't. I've come across a similar problem to this and previously, I found out that SharePoint had duplicated the Book Author field in the content type such that one was named "Book
Author" and the type showing was TaxonomyFIeldTypeMulti while the other one was named "Book Author_0" and the type showing was Note. I used the following powershell script to determine the names of the fields in the content type:
$site = new-object Microsoft.SharePoint.SPSite("http://www.yousite.com/")
$web = $site.OpenWeb()
$list = $web.Lists["YourList"]
$list.Fields | Format-Table Title, InternalName, TypeAsString
Previously when I encountered this problem, I simply tried both fields and one would always work. For example, I would try BookAuthor:{Book Author} and BookAuthor{Book Author_0} and one of them would work. In this case, I've tried both and none of them seem
to yield any results in my query. I noticed that I always seem to get duplicated fields only when I'm using columns of managed metadata type. I know my managed properties work because I can specify manual values and that yields the results I expect, but as
soon as I try to use the query variable from the page fields, it doesn't work. Strangely enough, I can use the Title or any other non-managed metadata fields of the page in my query variable (e.g. {Page.Title}) and I can get results that way. I've done index
resets and full crawls but nothing seems to fix this. Any help or insight on this would be greatly appreciated as it is driving me nuts!

Hi,
Please refer to the following post:
Infoobject F4 help in the Query takes lot of time and hangs
F4 Process takes a long time to show the values
There are several SAP notes on performance improvement for F4 help as mentioned in the first post. You may refer to the SAP notes as well.
Hope it helps,
Thanks,
Abhishek.

Dynamic filtering with BEx query variables in WebI 3.1

Hi experts.
Can anybody help me ?
1) I use BEx query variables in WebI 3.1 . But i can't understand how to order fields of selection screen in WebI reports
2) How can i use Dynamic filtering with BEx query variables in WebI 3.1 ?
It's need that list of second field on selection screen will be accoding to result of selection first field on selection screen and so on .
Need i use BEx user-exit variables ?
Thank you

Hi,
1) Variable sequence isn't respected in XI3.1 - and can't be modified in OLAP.unv (this enhancement exists in 4.0 )
2) Dynamic filtering? Yes, Exit routines are the best way to go for this.
Regards,
H

How to use a global variable for reading a query resultset in JDBC lookup?

Hi Friends,
Using JDBC lookup, I am trying to read from a table Emp1 using a user defined function. In PI 7.0, this function returns values of a single column only even if you fire a " Select * " query. I am planning to use a global variable(array) that stores individual column values of the records returned by a "select *" query. Need pointers on as to how a global variable can be declared and used to acheive the above scenario. Kindly explain with an example. Any help would be appreciated.
Thanks,
Amit.

Hi Amit,
Sounds like a good idea but then you would need an external db and update the table in a thread safe way !.
Regarding your question as to how to work with global variable please refer https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/1352. [original link is broken] [original link is broken] [original link is broken]
Rgds
joel

Copying Variables in BPEL using XPath Query

Hi,
I am new to BPEL and i want to know if it is possible to copy data from one variable to another using XPath Query in the <from> <to> tags, when the two variables are of different message types.
I am trying to create a sample BPEL that would receive a String through the receive tag tied to one partner link (WSDl) and then invoke a different webservice using the <invoke> tag tied to another partner link (WSDL) by passing the received variable.
I have pasted the BPEL File and the two WSDl files involved.
My Issue is that when I send a soap request to the BPEL, it is passed as null to the webservice invoked.
Probably because the copy tags don't work.
Please help.
BPEL File

<process name="HelloWorld2"
targetNamespace="http://ode/bpel/unit-test"
xmlns="http://docs.oasis-open.org/wsbpel/2.0/process/executable"
xmlns:tns="http://ode/bpel/unit-test"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:test="http://ode/bpel/unit-test.wsdl"
xmlns:ns0="http://poc.com"
queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath2.0"
expressionLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath2.0">
<import location="HelloWorld2.wsdl"
namespace="http://ode/bpel/unit-test.wsdl"
importType="http://schemas.xmlsoap.org/wsdl/" />
<import location="sayHello.wsdl"
namespace="http://poc.com"
importType="http://schemas.xmlsoap.org/wsdl/" />
<partnerLinks>
<partnerLink name="helloPartnerLink"
partnerLinkType="test:HelloPartnerLinkType"
myRole="me" />
<partnerLink name="sayHelloBPELPL"
partnerLinkType="ns0:sayHelloPLT"
partnerRole="you" initializePartnerRole="yes" />
</partnerLinks>
<variables>
<variable name="myVar" messageType="test:HelloMessage"/>
<variable name="tmpVar" messageType="test:HelloMessage"/>
<variable name="inVar" messageType="ns0:sayHelloRequest"/>
<variable name="outVar" messageType="ns0:sayHelloResponse"/>
</variables>
<sequence>
<receive
name="start"
partnerLink="helloPartnerLink"
portType="test:HelloPortType"
operation="hello"
variable="myVar"
createInstance="yes"/>
<assign name="ass1">
<copy>
<from variable = "myVar" part = "TestPart"/>
<to variable = "inVar"
part = "parameters"
query= "/sayHello/ns0:param0" />
</copy>
</assign>
<invoke partnerLink = "sayHelloBPELPL"
portType = "ns0:sayHelloPortType"
inputVariable = "inVar"
operation = "sayHello"
outputVariable = "outVar">
</invoke>
<assign name="ass2">
<copy>
<from variable = "outVar"
part = "parameters"
query= "/sayHelloResponse/ns0:return" />
<to variable = "tmpVar" part="TestPart"/>
</copy>
</assign>
<reply name="end"
partnerLink="helloPartnerLink"
portType="test:HelloPortType"
operation="hello"
variable="tmpVar"/>
</sequence>
</process>
WSDL File1
<?xml version="1.0" encoding="utf-8" ?>

<wsdl:definitions
targetNamespace="http://ode/bpel/unit-test.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://ode/bpel/unit-test.wsdl"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype"
xmlns:ns0="http://poc.com">
<wsdl:message name="HelloMessage">
<wsdl:part name="TestPart" type="xsd:string"/>
</wsdl:message>
<wsdl:portType name="HelloPortType">
<wsdl:operation name="hello">
<wsdl:input message="tns:HelloMessage" name="TestIn"/>
<wsdl:output message="tns:HelloMessage" name="TestOut"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloSoapBinding" type="tns:HelloPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="hello">
<soap:operation soapAction="" style="rpc"/>
<wsdl:input>
<soap:body
namespace="http://ode/bpel/unit-test.wsdl"
use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body
namespace="http://ode/bpel/unit-test.wsdl"
use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloService">
<wsdl:port name="HelloPort" binding="tns:HelloSoapBinding">
<soap:address location="http://localhost:8082/ode/processes/helloWorld"/>
</wsdl:port>
</wsdl:service>
<plnk:partnerLinkType name="HelloPartnerLinkType">
<plnk:role name="me" portType="tns:HelloPortType"/>
<plnk:role name="you" portType="tns:HelloPortType"/>
</plnk:partnerLinkType>
</wsdl:definitions>
WSDL File 2
<?xml version="1.0" encoding="UTF-8" ?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:ns0="http://poc.com"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:ns1="http://org.apache.axis2/xsd"
xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype"
targetNamespace="http://poc.com">
<wsdl:types>
<xs:schema xmlns:ns="http://poc.com" attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://poc.com">
<xs:element name="sayHello">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="param0" nillable="true" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="sayHelloResponse">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="return" nillable="true" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
</wsdl:types>
<wsdl:message name="sayHelloRequest">
<wsdl:part name="parameters" element="ns0:sayHello" />
</wsdl:message>
<wsdl:message name="sayHelloResponse">
<wsdl:part name="parameters" element="ns0:sayHelloResponse" />
</wsdl:message>
<wsdl:portType name="sayHelloPortType">
<wsdl:operation name="sayHello">
<wsdl:input message="ns0:sayHelloRequest" wsaw:Action="urn:sayHello" />
<wsdl:output message="ns0:sayHelloResponse" wsaw:Action="urn:sayHelloResponse" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="sayHelloSOAP11Binding" type="ns0:sayHelloPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<soap:operation soapAction="urn:sayHello" style="document"/>
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="sayHello">
<wsdl:port name="sayHelloPort" binding="ns0:sayHelloSOAP11Binding">
<soap:address location="http://localhost:8082/ode/processes/sayHello" />
</wsdl:port>
</wsdl:service>
<plnk:partnerLinkType name="sayHelloPLT">
<plnk:role name="me" portType="ns0:sayHelloPortType"/>
<plnk:role name="you" portType="ns0:sayHelloPortType"/>
</plnk:partnerLinkType>
</wsdl:definitions>

Hi,
Yes, it very much is possible.
Xpath query provides a lot many data type conversion functions(string to int, string to date etc), which can be used in copying variables.
thanks
Saurabh

Query rule using query variables

Hi All,
I am working on a query rule in SharePoint 2013. I am trying to build a query text using query variables to provide profile based results to the users. The query text which I am using in the query builder is of the following format:
{SearchBoxQuery} CombinedLanguage:{User.PreferredContentLanguage}
but its not taking the user.preferredcontentlanguage value. Has any one worked on similar type of query rules using query variables? Please share your suggestions.
Thanks !!

Hi,
As I understand, you cannot get the user.preferredcontentlanguage value.
1. Make sure you have set the value of query variable {user.preferredcontentlanguage}, it will return -1 if not set.
2. Make sure you search in the right result source.
3. Please check the crawled property mapped to the managed property CombinedLanguage and make sure that there is at least one value indexed by the crawled property equal to the {user.preferredcontentlanguage}.
The article below is about the query variables.
https://technet.microsoft.com/en-us/library/jj683123.aspx
The article below is about the different query variables return different result examples.
http://techmikael.blogspot.in/2014/05/s15e03-query-variables-constant-trouble.html
Best regards
Sara Fan
TechNet Community Support

Using collections / Bind variables with a PL/SQL functio returning a query

I have this code, which is supposed to assign collection variables as column names
FOR i in 1 .. Collection_count -1
LOOP
SELECT c002 into :P341_M1 FROM APEX_collections WHERE collection_name = 'MA_SKILLS' AND seq_id=i;
SELECT c002 into varholder FROM APEX_collections WHERE collection_name = 'MA_SKILLS' AND seq_id=i;
vQuery:= vQuery || 'SUM(decode(label, ''Aware'', product_'|| i || ', ''Expert'', product_' || i || ', ''Proficient'', product_' || i || ', ''Advanced(Demo)'', product_' || i || ' )) as ';
vQuery:=vQuery || varholder || ', ' ;
END LOOP;
I've tried &P341_M1. , :P341_M1, ':P341_M1', varholder
When I try '&P341_M1' it returns the whole SUM(decode... line as the label
Basically Im having a hard time using bind variables with the PL/SQL returning a query...anybody?

Ok so working through this problem more I have realized that the problem is using the for loop i as an index value
This will get a value:
SELECT c002 into :P341_M1 FROM APEX_collections WHERE collection_name = 'MA_SKILLS' AND seq_id=2;
But this won't
SELECT c002 into :P341_M1 FROM APEX_collections WHERE collection_name = 'MA_SKILLS' AND seq_id=i;
I'm in the for loop, and use the i variable in other places within this loop...Is there a reason why I can't compare seq_id to i?
My new code as follows:
FOR i in 1 .. Collection_count -1 --apex_application.g_f01.COUNT - 1
LOOP
varholder:=i;
SELECT c002 into :P341_M1 FROM APEX_collections WHERE collection_name = 'MA_SKILLS' AND seq_id=2;
SELECT c002 into varholder FROM APEX_collections WHERE collection_name = 'MA_SKILLS' AND seq_id=4;
vQuery:= vQuery || 'SUM(decode(label, ''Aware'', product_'|| i || ', ''Expert'', product_' || i || ', ''Proficient'', product_' || i || ', ''Advanced(Demo)'', product_' || i || ' )) as f';
vQuery:=vQuery || :P341_M1 ||i||', ' ;
END LOOP;

No Query Result After Using Hierarchy Node Variable (Customer Exit)

Hi
I have problem at my query. It doesn't show anything in BEx but when i check the data in BW using tcode LISTCUBE i can display the data.
This problem happen when i change the restrictions for one of characteristic in filter value.
The characteristic is custom Infoobject (ZCPARTNER), which like Infoobject Partner Unit.
Previously I set the restriction with constant value, example : A500,A700,A710,A720,A730,A740 and it worked before.
But when I change it using hierarchy node variable (customer exit), this problem is arise.
Here is my code at ZXRSRU01
WHEN 'ZHIEPART'. --> hierarchy node variable
   BREAK-POINT.
    IF i_step = 2.
    Read from ZZCONSGR information
      LOOP AT i_t_var_range INTO loc_var_range
         WHERE vnam = 'ZZCONSGR' OR vnam = 'ZOCONSGR'. --> read input value from consolidation group variable
        CLEAR l_s_range.
        CLEAR l_s_range-low.
        IF loc_var_range-low EQ '000000000000030000'
           OR loc_var_range-low EQ '000000000000010130'.
          l_s_range-low = 'MEZBUNITMDI'.
          l_s_range-high = '0HIER_NODE'.
        ELSEIF loc_var_range-low EQ '000000000000040000'
           OR loc_var_range-low EQ '000000000000010160'.
          l_s_range-low = 'MEZBUNITMPI'.
          l_s_range-high = '0HIER_NODE'.
        ENDIF.
        l_s_range-sign = 'I'.
        l_s_range-opt = 'EQ'.
        APPEND l_s_range TO e_t_range.
        EXIT.
      ENDLOOP.
    ENDIF.
Here the hierarchy in BW system:
XXX Cons Unit Hierarchy Set; InfoObject ; Node Name
- XXX Cons Unit Hierarchy Set; 0HIER_NODE; ZBUNITALL
- XXX DownStream ... ; OHIER_NODE; MEZBUNITMDI
     - ME/A730; 0CS_UNIT; MEA730
     - ME/A740; 0CS_UNIT; MEA740
- XXX Power ; OHIER_NODE; MEZBUNITMPI
    - ME A800 - A808; OHIER_NODE; MEZBUNITMPI
    - PT Mitra xxx; 0CS_UNIT; MEA820
Anyone can help my problem? Thank you
Regards,
Satria B Tandyono

Hi Satria,
Instead of following code ---
CLEAR l_s_range-low.
IF loc_var_range-low EQ '000000000000030000'
OR loc_var_range-low EQ '000000000000010130'.
l_s_range-low = 'MEZBUNITMDI'.
l_s_range-high = '0HIER_NODE'.
ELSEIF loc_var_range-low EQ '000000000000040000'
OR loc_var_range-low EQ '000000000000010160'.
l_s_range-low = 'MEZBUNITMPI'.
l_s_range-high = '0HIER_NODE'.
ENDIF.
try this ---
IF loc_var_range-low EQ '000000000000030000'
OR loc_var_range-low EQ '000000000000010130'.
l_s_range-low = 'MEZBUNITMDI'.
ELSEIF loc_var_range-low EQ '000000000000040000'
OR loc_var_range-low EQ '000000000000010160'.
l_s_range-low = 'MEZBUNITMPI'.
ENDIF.
Note : whenver the option is EQ, the system takes only low value.

Variable not used in query

HI
I am making a query in which I am using a variable 'Zfiscper' in calcualting a formula variable. but while running , it displays an error message - 'zfiscper' not BEing used in query.
Can ne one tell y this msg is comin??

Hi i know how to use char as a KF in the report but i am asking did use the Fisyear varaible in the formula with replacement path??? It id not possible to do so. Just try to drag that fiscal year variable in the report and excute the querry.
If not possible by doing so then just drag the fiscal year in the rows. And run the querry.
Khaja

Crystal Reports with BEx Query using Custom Exit Variable

Hi,
We have BW BEx Query using Customer User Exit variable to derive the Fiscal Week for Last Year (called it VAR2) based on another user input variable Current Fiscal Week (called it VAR1).
VAR2 is derived from VAR1 in CMOD via some codings and thus it DOES NOT have the "Variable is Ready for Input" flag ticked in the BEx. VAR1 is user input variable, so it has "Variable is Ready for Input" flag ticked in the BEx.
When we create a Crystal Reports with the BEx Query using variable VAR2, and when we run it we got an error message saying "Failed to execute query; '[]<java.lang.UnsupportedOperationException: No Selection State Support!ZP_MI_LYPUBWEEK>'. Redesign your query or contact the data source maintainer to solve the problem". (note: ZP_MI_LYPUBWEEK is VAR2 in this case).
Could anyone please assist? Surely, CR supports BEx customer user exit variables like the above, right?. I also refer to the forum below as it seems to have a similar issue (except mine with an error message), but it does not provide a solution in it.
Crystal Reports with BEx Query using Custom Exit Variable
Thanks,
Andy

Hi Vibhav,
We have the SAP Crystal Reports for Enterprise XI4.0 Version 14.0.0. Not sure if SP0 or other SP, got to check with Basis Team later.
We tried that "mandatory" option and did not work either.
Anyway, SAP has now come back again saying it is something they will fix it in next release/version. We got a phone call from them and a reply below to our OSS.
23.08.2011 - 08:20:49 CET - Info for Customer by SAP
I have raised this issue on the Idea#s Place as an enhancement request
on the below link:
https://cw.sdn.sap.com/cw/ideas/5586
This ER contains the information of including the customer exit
variables in the report without checking the #input for ready# option.
This ER can be considered for being implemented in the future
versions. You can refer to SAP Note: 1515837 - How To: Enhancement
Request Process - "Idea Place" for more information regarding the Idea
Place.
Cheers,
Andy

How to create/use SAP Exit variable of Query designer

Hello experts,
Can you please guide me on how to create/use SAP Exit variables ?
Is there any way we can transport customer exit include in which we write all codes related to customer exit variables?
Kindly provide your valuable inputs on this.
Thanks,
Mitesh

Hello Gautam,
I think you should first implement the user-exit via the transaction SMOD/CMOD and the SAP-Enhancement RSR00001 User-Exit ( BW Reporting )
For the concrete implementation I would suggest to encapsulate the variables, as it is described here
Easy implementation of BEx-Userexit-Variables
and here: BEx-Userexits reloaded
Kind regards,
Hendrik

How do I use an array variable in the assignment target?

Hi,
I am creating a BPEL process in which I have to use an array variable. The array variable needs to be initialized based on some condition.
The issue is I cannot find a way to set the value of the array variable. There are ways to GET the value of an array variable indexing into it.
But how do I set the value by using the Array variable in the <to> tag?
Any help is appreciated. I am using BPEL 10.1.2.0.2.
Thanks.

You can declare a variable of type integer which will server as your index. Figure out based on some condition in your process which index of array to update. Assign to your integer variable you created.
And have Assign copy operation like this -
<copy>
<from variable="Var_Output_FetchDueDate"
part="OutputParameters"
query="/ns18:OutputParameters/ns18:DUEDATE"/>
<to variable="outputVariable" part="payload"
query="/client:GetCustomerAccountInformationProcessResponse/client:customer/client:accounts/client:account[$Var_Counter]/client:dueDate"/>
</copy>
I have been using this in my processes.

Text lines in the BW query variables screen

Hi gurus.
The bw users ask me to display some text lines in the BW query variables prompt.
The text lines are saved in a custom table.
The only idea that I've got is to use customer exit text variables and fill them in CMOD when I_step = 1.
I don't like this solution (I should have more the 10 text lines and so I have to mantain more than 10 Text variables) but I can't find any other solution.
Any new idea or solution?
Is there in Bex enviroment a functionality (that I don't know) for doing somenthing like this ?
Thanks fo any help.
S.

Hi,
to resolve it you should create all the prompts in the BW query. You are using a query with 2 parameters and then a dynamic list of values. the dynamic list of values can only work after you entered the other values.
Ingo

Consequences of using unconstrained query variables?

Similar Messages

Maybe you are looking for