Additional characteristics in Query Designer

Hi All,
I have created my own Customer Infocube (ZSD_C01_T) copied from BI content Infocube 0SD_C01. The customer dimension has only the Sold-to party characteristic. refer below.
But when i tried to create a report in Query Designer, I get additional characteristics - Business partner number for sold to party, Industry Sector, Sold to party country.
Can you please explain what are these additional characteristics?

Hi All,
Thanks for ur replies. Please find the query designer screenshot with the technical names.
I checked the Info provider 0CUSTOMER in BI and found that there are more navigational attributes which are not listed in the query designer. Can anyone explain the reason.

Similar Messages

Grouping Free Characteristics in Query Designer?

Hello,
I have a couple reports that per busniess have many free characteristics. So many that that they do not fit on one page and you must continue scrolling the page down to view all. This makes the report look sloppy but the business owner wants all of these free characteristics. I'm looking for a way to clean up the list of free characteristics without removing any selections. Can they be grouped up or consolidated through Query Designer or WAD?
Thank You,
Alex

Hi Alex,
Actually use of free characteristic will not slow down the report performance rather free characteristics are used to enable the user for dynamic drilldown and to improve the query performance for initial output display.
What you can suggest your users is to keep only required free characteristics and then remove the rest of the characteristics and from grouping perspective all the free characteristics in query designer output are shown alphabetically so you can not manipulate the group in designer.
Regards,
Durgesh.

BW 3.5, BEx Query designer issue with text of the characteristics

Hi All,
We are currently using BEx 3.5 Query Designer to design the queries. We have one of the ODS on which we are querying for.
We have 3 different types of Customer in this ODS. 0Customer, 0BBP_CUSTOMER and 0GN_CUSTOMER. The problem is when we open this ODS in Query designer we see their text name on the left hand side column where it shows data fields as the same text name Customer.
Now the our Power users have raised the issue that it is very confusing even when there are 3 different technical names for these characteristics.
2 Questions I have.
1) Why is something like this happening? is it some issue with the Patch or something. We will be migrating to new BI soon but in the mean time if I could resolve it that will be the best. Or does it even get resolved with new BI???
2) what is the way in which we can resolve it?
Thanks in advance and points will be given generously.

HI BI Consul!
Things like this happen, when it is called customer it could be different customers, 0customer is the standard R/3 customer and 0BBP_customer is objects from CRM and most likely 0GN_Customer might be customer from different system.
Sure, power users should be told which customer is customer and you could also change the discription of the object, to match the definition on the other system. You could also just create z object and replace the existing confusing object with something meaningful to users.
thanks.
Wond

Mapped characteristics in Multiprovider not available in Query Designer

Hi,
we have a multiprovider with approx 10 cubes and lot of characteristics, Navigational attributes mapped to it. I have added around 3 more characteristics and mapped to underlying cubes. But these added characteristics are not visible in Query designer. Is there maximum limit for the number of characteristics.
Thanks,

Disconnecting the BEx made it work. But i dont understand i added this yesterday in the multiprovider. But i also removed some navigational attributes from the mapping. I will re-map and check. Thanks for the tip.

Fiscal Year Period - Query Designer - Characteristics Value

Hi Experts,
In query designer, characteristics value for 0FISCPER by default shows value of fiscal year variant V9. But for Fiscal year variant V9, 002.2014 is November 2013.
Now user want to display the correct period and its description (002.2014 is February 2014) which implies need to use different variant. Please let me how this can be changed.
Regards
Suresh Kumar

Hi Suresh,
Try this
Path: Financial Accounting >> Financial Accounting Global settings >> Fiscal Year >> maintain Fiscal year variant (maintain shortened fiscal year)
Transaction Code: OB29
Regards,
Amit

How to display in query Designer in a query the characteristics values of an infoObject in one cell

Hello Community Members,
I have query with 3 characteristics and 2 key figures, and
want to expand the key figures values only with 2 characteristics, and display the different values of the 3. characteristic in the first cell at the corner of the query cell:
          C31,C32             C21                       C22                      C23
          C33, C34
           C11                  KF11    KF21           KF12    KF22      KF13    KF23
          C12                   KF14    KF24           KF15    KF25      KF16    KF26
          C13                   KF17    KF27           KF18    KF28      KF18    KF28
          C14
How to set the characteristic C3 in query designer, so that their values will all be displayed in the cell in the corner.
many thanks for helping
Arnaud

Hi Arnaud,
Your query structure is not dependent on your aggregation level (I guess you are referring to the Exception aggregation or just the results and not AL in IP).
Number of columns will depend on the combination of C2 and C3 in this case. So columns will not be 6 but 24.
So I suggest you to create a work book based on two queries. One will just give you the values of C3. Use Macro to take its values and concatenate it and display in a new table along with the data of other query.
This solution is not flexible as workbooks usually have some restrictions on Bex Features. But your requirement is also not simple.
Regards,
Sujit.

Drilldown in BeX Query Designer

Hello,
I am new in SAP. I am having problem creating Drill down. I have this report where all the data is Transactional data. So I haven't created any Master Data. So I won't be able to use Navigational Attribute for Drill down purpose and I don't want to use Hierarchy. Is there any possibility of getting the Drill down in BeX Query Designer? Any help will be appreciated.
Warm Regards,
Debayan

Hi Debayan,
first of all, what is your requirement to create a drill down?
A drill down in BEx query means showing additional information from report output. There are 3 ways to drill down a query in BEx
1. Master data-Navigational Attributes
2. Master data- Hierarchies
3. Free characteristics
As you dont have any master data in the report (which is very strange) you can use the additional characteristics provided in the 'Free characteristics' to see how the drill down works in BEx.
Please share your exact requirement.
Hope this helps.
-Swati.

Two structures on same axis in query designer

Hi,
I developed a query with two structures column axis in Bex query designer (in BI 7)
when I open this query in report designer is showing this error
" The Report Designer does not support this query drill down. Column axis may contain one structure only: remove any additional dimensions "
Can you please help me on this issue.

Hi Ram,
sorry for the late reply, had a weekend break.
If a query (or query view) contain two structures and also one or
more characteristics then a dynamic section will be used. The dynamic
section will generate individual cells for each intersection of the two
structures, this means you will be able to re-position those cells freely.
Also you cannot use a query or query view which contains more than one
structure in the columns.
and you are having two structures in your columns, that is the reason you are getting the error message. It doesn't matter even if your query runs fine in WAD and Query designer, but your structure placements doesn't satisfy the Report Desinger specs.
Hope it helps,
Venkat
*thanks = points in SDN

Text value is not getting displayed in Query designer !!

Dear experts..,
i have created a new query in query designer using my info provider and then selected one field in default value and then trying to restrict that particular field while selecting the restriction in query designer am getting the exact text value but after generating the report instead of text value , key value is getting displayed....so how can i get text instead of key value??
please help me friends....
i have posted in OSS mesage also...i got a reply like...even i didnt understand his reply too...what he is trying to say?
whether can i get text display or not???
can any one help me in this regard???
SAP Reply----
Hello kumar,
After another analysis I have to inform you about general concept of
"compounded characteristics".
A compounded characteristic bounds two characteristics. The technical
name is generated by both technical names of the two characteristics
combined by two underlines "__".
An individual text is only available for one single combination of both
characteristics.
Example:
=======
Compounded characteristic "Famous family name" is a combination of
characteristic "COUNTRY" & "ETHNIC". Technical name: COUNTRY__ETHNIC
Values for Country: USA, Australia
Values for Ethnic: Asian, Latino
Possible value combinations with individual text:
USA & Asian; text: "Ling"
USA & Latino; text: "Sanchez"
Australia & Asian; text: "Chu"
Australia & Latino; text: "Garcia"
(Keep in mind the individual text only valid for the specific
combination.)
In analogy to the issue that you reported, you want to restrict this
compounded characteristic. In the window where you select the restrictedvalue (called Selector) you'll see on the left hand side all available
combinations of the characters with an individual text.
You select family name "Chu" and drag'n'drop it to the right side.
Actually you can only restrict the right compounded characteristic. In
our example you would restrict on characteristic "ETHNIC" with value
"Asian". (When you switch on technical names this comes more clear). Thetext "Chu" is displayed in the context of Selector because you selected
value combination Australia & Asian. But in the end it's just a
placeholder(!) for any combination of characteristic "ETHNIC" and value
#Asian#; in our example it could be USA & Asian "Ling" or Australia &
Asian "Chu").
By leaving the Selector the individual text is gone because now the
context is lost between the two characteristics. You have just a
restriction on characteristic "ETHNIC" with value "Asian". An individualtext can't be displayed because the compounded characteristic is not
specified for this restriction.
You're right, it is confusing when "loosing" the text of a restriction.
But accoring to the concepts of the compounded characteristics it
is a correct behavior.

Hi anandkumar,
I belive this issue can be resolved by changing the Query proprties for the perticular field.
Kindly check the Field proerties in query designer and ensure that Text is enabled ather than Key.
__Field property check up:__Go to query designer->click onn the field-> Right hand side in properties click on display tab-> select Text in drop down menu of Display as tab.
FURTHER CHECK UP: check the master data avaiulability for the perticular info object, if masterdata is not available, do the text data for txt data availability in report level.
Hope this helps you!!
Best Regards,
Maruthi

Structres and cells in Bex query designer?? urgent plz

hi experts,
could you please give me the useful info. regarding structres and cells with the examples.
thanks in advance
regards
vadlamudi

1. In the Query Designer, choose Cells (open) from the toolbar or use the menu option under View to reach the Cell Editor functions.
2. You can now use four different functions.
New Selection
u2022 Select a cell in the Cells dialog box, and use the right mouse
button to choose New Selection.
u2022 Define the required selection.
u2022 Enter a description for the selection and choose OK.
New Formula
u2022 Select a cell in the Cell dialog box, and use the right mouse button to choose New Formula.
u2022 Define the required formula. Enter a description for the formula
and choose OK.
New Cell Reference
Each cell that you define can be reused in formulas. If you want to reuse the value of the implicit generic cell definition that automatically occurs at the intersection of two structure parts of a query, select this cell in the Cell Definition dialog box, and choose New Cell Reference using the right mouse button. The description arising from the two structure parts
automatically appears in the cell. You can now refer to this cell.
Additional cells
Click on the cell adjacent to the Help Cells and choose the required option if you need additional cells for auxiliary selections or formulas which are not already included in the query structure you have defined from the construction of rows and columns.
Ashok

New ratio doesn't appear in Bex Query designer

Hello Experts,
I added 2 ratios to my infocube. It activated without any problem. I then added these 2 ratios to my multiprovider and activated it after affecting them to the previous infocube.
Then I connected to the Bex query designer and loaded a report in order to add these ratios, but there are not available for selection in the Ratio menu of the multiprovider.
Has anyone faced this problem?
Thanks

Try reactivating the Multiprovider again and see if that works !
I had this issue earlier, where I couldn't see two of the newly added characteristics in the multiprovider. But simply reactivating the multiprovider solved my issue.
- Danny

Usage of formulas in conditions in BEx Query Designer

Hi guys,
does anybody of you guys know, if it's possible to use the results of formulas in conditions? I tried it, but the result of the query was "No applicable data found", but there are data for the selection.
When I'm defining the condition with the key figure (no restricted or calculated key figure), then the query can be executed.
In my case, I like to define a condition based on a formula result. The value should only be displayed, when the result is greater than 30.
Any ideas or are there any bugy in the BEx Query Designer?
Thanks a lot + best regards,
Clemens

Hi Clemens,
I have created a condition in my own system based on formula and it works perfectly fine. Please check following points in your condition change mode,
1) Condition is marked as Active.
2) In the block "Evaluate condition below for" you will have to select "All characteristics in drilldown Independently". If you have selected combination of characteristics then you will have to maintain proper sequence otherwise your condition will not work.
3) In the next block when you set the condition, click on new, in the first block select your Formula from dropdown and set the proper operator in your case you will have to select "Greater than" in the next column set the value of key figure and just trasnfer it.
Now you are ready to use the condition.
Regards,
Durgesh.

Problem with Queries Structures in Bex Query Designer and Universe Designer

Hi everyone,
I have a problem when i try to do a Universe from a Bex Query Designer.
When I use a Characteristic Restrictions in a Structure, the universe only show me the structure without the objects inside it.
EJ:
1) Bex Query Designer
Colunms
(Structure) ZSRT_123
                      - (Characteristic Restrictions) Reg Guayana
>          (InfoObject)     0Product = 'XXX'
>          (InfoObject)     0Country = 'YYY'
     - (Characteristic Restrictions) Reg Caracas
>          (InfoObject)     0Product = 'AAA'
>          (InfoObject)     0Country = 'BBB'
Rows
(Structure) ZSRT_456
               (Key Figure)     Net Sales
2) Universe designer
(Class) ZSRT_456
>(Measure)      Net Sale
(Class)     ZSRT_123
>(Dimension)      ZSRT_123
The universe dont translate the two Characteristic Restrictions in the structure ZSRT_123.
Any information would be much appreciated. Thank you.

Hi,
I assume that you are using BOE XI 3.1 SP2.
We have added an option in SP2 to generate or not the L00 level.
Unfortunately this option applies not only on characteristics but also on hierarchies, hierarchies variables and structures: that's the reason why you have no elements belonging to the structure generated.
I recommend to always generate L00 in order to have your structure generated correctly.
This issue will be fixed in SP3.
Regards,
Didier

In Bex Query designer - Flat is not supported

Hi all,
In Bex query designer,
While execution of the query, the following error is coming .
Failed to process request; contact your system administrator
Error Summary
Exception occured while processing the current request; this exception cannot be handled by the application or framework
If the information on this page does not help you locate and correct the cause of the problem, contact your system administrator
To facilitate analysis of the problem, keep a copy of this error page Hint: Most Web browsers allow you to select all content, and copy and paste it into an empty document (such as in an email or simple text file)
Root Cause
The initial exception that caused the request to fail was:
Flat mode is not supported!
java.lang.UnsupportedOperationException: Flat mode is not supported!
at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.Characteristic.setHierarchy(Characteristic.java:330)
at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.Characteristic.readStateFromDomNode(Characteristic.java:542)
at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.QvCharacteristic.readStateFromDomNode(QvCharacteristic.java:379)
at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.QvStructure.readStateFromDomNode(QvStructure.java:106)
at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.AttributeContainer.readStateFromDom(AttributeContainer.java:297)
Details: Full Exception Chain
Most important error.
regards
Selvan

Hello,
I have the same problem with Flat mode is not supported! at ... Characteristic.setHierarchy(Characteristic.java:335):
Open, close, reload of the query does not help.
Other SDN-thread "500 Internal Sever - Flat Mode is not Supported!" related to transaction RSRT.
Execution of query via RSRT works, but the problem still persists in the BEx Web Analyzer.
Could be related to a BEx Web Analyzer "bookmark" ("Personalize Web Application").
I have not deleted any item. We use SAP BW 7.0 with a patch level approx. 09.2009.
The "flat-mode" seems to be the "BEx table mode".
SAP hints do not seem to fit here:
- 715820 BW 3.x Front-End Patch 14 (we use BW 7.0)
- 874825 SAPBWNews for BW 3.x Front-End Support Package 19
- 874827 SAPBWNews for BW 3.5 Front-End Patch 08 (we use BW 7.0)
- 905229 update to SAPTableTree
- 909824 Termination in flat mode when an object is deleted (old?)
- 909827 Incorrect InfoProvider-dependent characteristic values
- 910602 Condition includes too many characteristics (usage of deleted elements)
- 915215 Termination when a query definition is changed (old? visibility of elements?)
- 968273 Cache with flat files: Exception is not caught (does not apply to given error)
Any new solutions?
Best regards
Thomas

Condition (Defintion) in BEX Query Designer

Hi Experts,
I am trying to define a condition in BEX Query Designer.
I defined my condition and bit confused with Characterstic Assignment
What Happens if is select 9What is the difference)
1) All Characterstic in the Drilldown Independtly
2)Most Detailed Characterstic Along the Rows
3)Most Detailed Characterstic Along Columns and
4)Individual Chars and Chars.Combinations
Thanks

Hi,
● All Characteristics in the Drilldown Independently
This setting allows you to apply a condition in a general way. Depending on which characteristics you use in the drilldown, you obtain different results.
Note that the characteristics that are already used in an active condition for characteristic combinations are not included.
This option is optimized for ranked list conditions, but can also be used for threshold value conditions with relative values.
●Most Detailed Characteristic Along the Rows or Columns
This option is optimized for threshold value conditions. The condition is applied to the most detailed characteristic of the rows or columns.
Note that this function is not supported when executing the query in the BEx Analyzer. For more information, see Restrictions in the BEx Analyzer.
● Single Characteristics and Characteristic Combinations
This setting allows you to evaluate the condition for characteristics or characteristic combinations defined for specific drilldowns only. You can select any characteristic (of the characteristics used in the query in rows, columns, or in the free characteristics) or a characteristic combination.
○ If you only want to evaluate the condition when a certain characteristic is present in the drilldown, select this characteristic.
○ If you want to evaluate the condition for characteristic combinations, select multiple characteristics.
Source:
help.sap.com
For more information and examples please check the following link:
http://help.sap.com/saphelp_nw70/helpdata/EN/73/702e39074dc93de10000000a114084/frameset.htm
Hope it helps.

Additional characteristics in Query Designer

Similar Messages

Maybe you are looking for