Skip to Content
author's profile photo Former Member
Former Member

Variable Issue

Hi,

I have an issue using variables in Query Designer.

My question is, "Can't we use same variable on Characteristic (0SEG_LEV1) and navigation attribute (0BPARTNER__0SEG_LEV1) ?"

If I use the same variable as stated above, In the Development system, it is throwing an error saying "Variable 'Segment Level1' is used for two different characteristics" but in the Production System & Quality System, it looks fine.

When I execute the query in RSRT, it is not giving me any errors that are shown up at the time of checking the query.

I don't understand if I am doing something wrong ?

Please help me out on this.

Thanks,

Sai.

Add a comment
10|10000 characters needed characters exceeded

Related questions

5 Answers

  • Best Answer
    Posted on Sep 02, 2013 at 12:18 PM

    Hi Sai,

    you may not use the same variable within one query, but you can use them in several queries separately.

    If you use the same variable separatly in different queries - once for char and once for navi, you will still get the error message, but you can ignore it.

    If you need exactly the same restriction within one query - then use the variable for the char and create a new variable for the navi, type replacement path and replace the value from your first variable.

    regards

    Cornelia

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Saideep,

      I want to correct you about your Nav Attr.

      If your main char is ZBRAN and its Nav Attr is 0plant then your Nav Attr will look like ZBRAN__0PLANT but not 0PLANT__ZBRAN.

      Thanks for understanding and agreeing to all my replies. Please cross check your variables and queries with respect to my explanations. Then, you will get the complete picture.

      Regards,

      Suman

  • author's profile photo Former Member
    Former Member
    Posted on Sep 04, 2013 at 03:31 PM

    Hi Saideep,

    Nice question. It will help us to think in several ways.

    We can use same variable on Characteristic (0SEG_LEV1) and navigation attribute (0BPARTNER__0SEG_LEV1).

    Note: The variable would have been created on one object and the same has been reflected at all places. There will not be any issue with the overall result.

    • Since we have same master data, you will get blank entries in BPARTNER case if you restrict with 0SEG_LEV1 alone - for the places where there is no PARTNER entries.
    • You will get only PARTNER related segment levels only if you restrict with 0BPARTNER__0SEG_LEV1 (v/v)

    In the Development system, it will show warnings (with red or yellow color). But it is just for our reference and the same warnings wont come further or in execution.

    During transports it will not give any problem, because variable originated from some master object, that would have been transported before and also it will consider developed procedure instaed of usage behaviour.

    Hope this provide you clarification.

    regards,

    kumar

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 02, 2013 at 12:02 PM

    Actually, it is not possible to use same variable. It doesn't show in the available list of variables. How come it is ok in Qua and Prod? Please check there might be using different variables in Qua and Prod.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 02, 2013 at 12:03 PM

    Hi,

    Yes you may not use the same variable for two different characteristics.

    You can create two different variables and specify the value of one variable and with the help of replacement path you can pass the same value to other variable.

    Please share your exact requirement for more inputs on the same.

    Regards,

    AL

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Sep 02, 2013 at 12:10 PM

    Hi Suman & Anshu,

    Thanks for the reply.

    But the info object used is the same. The only difference is, in the first place, the characteristic is directly used in the report but in the second place, the characteristic is coming as navigation attribute of a master data object.

    Thanks,

    Sai.

    Add a comment
    10|10000 characters needed characters exceeded

    • As far as Bex is concerned, infoobject and Nav Attr will be treated as separate objects. Since the main infoobject is same, you would not get the same variable under the available list of variables to use in both the objects.

      Why don't you create a new one similar to the existing one and use it, right?

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.