Compounding Characteristics

Hi:
I am having a unique problem. Hi:
I am having a unique problem. This has to do with 0PROFIT_CTR which has a componding char 0CONTROLLING_AREA.
This is what i have in the Cube:
Controlling Area/Profit Center     Amount
0001/100000                              1000.00
0001/200000                              1000.00
0002/100000                              2000.00
0002/200000                              2000.00
#/1000000                                 3000.00
#/2000000                                 3000.00
This is what i require as the output in the query:
Profit Center                              Amount
100000                                     6000.00
200000                                     6000.00
but this is what i am getting in the query:
100000                                     1000.00
100000                                     2000.00
100000                                     3000.00
200000                                     1000.00
200000                                     2000.00
200000                                     3000.00
I have brought in Controlling Area into the query marked it "No Display".
Can anyone let me know how to get the desired result without having to modify the Cube,
Thanks
EmJay

when u put the NO DISPLAY option it will not display in query execution but as the Controlling area is still in rows in query execution it will have 6 values as u suggested..
the only solution is to remove the Controlling area from the Rows.
if u intend controlling area for future use then u can bring it in free characteristics.
otherwise remove it even from there...
for experiment purpose so that u can understand wat is going on
try this
put controlling are in free chars
go to its properties and put it as NO DISPLAY
so upon query execution u will get ur desired result.
now bring controling area from free to rows
and see the output
u will see the output as undesired one and the one u r getting right now.....

Similar Messages

Table for compounded characteristics

Hi
Whats the table that contains details about 'compounded' characteristics? (I am creating an infoset that dispays the characteristic relationships in a cube, but in the source and target I am not seeing the compounded chracteristics.)
thanks

Hi,
table RSDIOBJCMP will tell you the compounding IObj of a compounded IObj.
table RSDCHA filtered to CMPSTA not empty will tell you the compounded characteristics.
hope this helps...
Olivier.

How to remove Compounded Characteristics ???

i have a custom characteristics companycode Levels
in its definition, CCode Levels is compounded with Companycode
so when i run the query it shows like this
CCode.....CCodeLevels....Amount
110............110/LVL2.........35
111............111/LVL3.........45
112............112/LVL4.........35
Now because CCode Level is compounded it also SHOWS CCode in Query result Data.
HOW CAN I AVOID THIS DISPLAY...
How can i just show LVL2 only in Query Data.

Hi,
Disturbing stabdard object is not recomendable levels are compoundeed with company code
u want like as below
CCode.....CCodeLevels....Amount
110............LVL2........ .35
111............LVL3........ . 45
112............LVL4........ .35
any way u are getting both the ccode and level through transactional data source then u can remove theccode as componding to the level at info object levle.
But u want to do at report level u keep both level and ccode in rows and on c code info object hide that company code and display level only
but u can get level alone #/lvl1 like this it will come again company code will not come. as experts said it is better to remove as compound.
otherwise u can do one thing in cube level add one more field with name as ccode and BURKS k load it that object and to this compound object of ccode
in rows newly added ccode and old ccode with hide option and level .
but all possibleities at cube level , i do not know exactly either it is feasible for you at cube level or not. Just i am shatring my view with you.
Thanks & Regards,
sathish

Issue with compounding characteristics in the query

Hello guyz
I have an issue with 2 chars one compounding the other in the query. The 2 chars are : Action Type and Action Reason in HR. Action type is the compounding char. for action reason.
For example: we have
Action Type    Action Reason
01                        A1
01                        A2
02                        A1
02                        A2
Now I want to restrict a key figure based on specific action reasons and types. But when I pick AT: 01, AR: A1, it selects AT: 02, AR: A1. The reason why it does this is because, there are 2 A1s under action reason and it picks the one at the end (ie last record with value A1 in the table)
But my compounding works when i create variables for the same and have them as user entry variables.
My question: How do i pick specific action reasons for specific action types (for restricting key figures) in the above example?
Thanks.

Well.. thank you Ashish for your help so far.
Now, these Chars. are coming directly from a data source to the cube. From my previous example again, the thing that i dont understand is:
When i try restrict the KF with AR, on the left hand side of the pop up window i see:
       AR
[01, A1] --> Very good
[01, A2] --> Good
[02, A3[ --> OK
[02, A4] --> Bad
[02, A1] --> Very Bad
But, when i drag 'A1' (Very Good) to restrict on the KF on the right hand side of the window, I only get:
A1 (Very good), what i want to drag is [01, A1] --> very good.. action type value should come along with action reason.. right??
when i save the query, logout and log back in, I see:
A1 (Very Bad)
Question: Why dosen't Action type char come along with action reason on the right hand side.. its a compounding char right?? So it should determine what value action reason takes?
Any idea??

BICS and Compounding Characteristics

Hi Experts,
I was expecting with the new BICS connectivity the compounding characteristic behavior could be smoother:
The compounding concept it comes mainly with Business content objects and concerns big grouping of values of one characteristic as 0ACCOUNT against another as 0CHRT_ACCTS.
Users mostly they donu2019t want to have the 0CHRT_ACCTS/0ACCOUNT key in the reports they just want 0ACCOUNT.
Mainly in BEX what we were doing up to know to eliminate the 0CHRT_ACCTS within the key of 0ACCOUNT was: either we had both available at the rows section or we restricted 0CHRT_ACCTS to a particular chart of account. This was quite acceptable I would also expect a clearer option at the BEX query designer as we have in the display options of the WEB Analyzer like display Key (Not Compounded) but I guess the CREATOR has its reasons.
However I am trying the BICS with Web intelligence and OLAP analysis for the web in BO 4, and the result is still disappointing and it seems there is no easy way to eliminate the compounding characteristic behavior by just restricting or have them both available in your result set at your BEX query or in BO query, or some setting somewhere.
I canu2019t believe that with the BICS connectivity which is now so widely available in Business Objects 4 , where SAP tries with it to reduce the TCO, we still have to deal with the compounding values and try to find workarounds for that.
Anyone?
Regards,
Theodore
Edited by: Theodoros Papadopoulos on Dec 22, 2011 12:30 PM
Edited by: Theodoros Papadopoulos on Dec 22, 2011 12:32 PM

HI,
In BW Side:
We can hide the compounded objects in Bex side thru the following option.
Ex:
0CUST_SALES has 2 compounding attibutes Sales organisation nd Distribution channel.
in the rows panel of Bex, drag all the 3 objects and place sales org and distri channel just above cust sales, then change the dispay properties of sales org and distri channel as No display
and the result row as Suppress Results for the 2 objects sales org and distr chanl.
Now if you execute, only cust sales would be shown in bex output.
In BO Side:
We have to workaround with substr function till SP4.
With SP5, SAP has come out with a soution for this limitation.
Please see the link below for more details:
http://scn.sap.com/community/businessobjects-web-intelligence/blog/2013/02/03/all-you-need-to-know-about-compounded-objects
Cheers,
Prabhith

Non displayed texts of compound characteristics

Hi,
Web Application is not displaying the text of a specified variable (using a compound characteristic).
We populated a variable with an exit function module and we are using this variable as a restriction of values.
For example, we use a variable PRFOLIO in the web interface builder; the formatting is set to &C_PRFOLIO-TEXT (&C_PRFOLIO-VALUE), but the web does not display the text information, only the value.
Has anyone else experienced this?
For information, we are using web interface and SEM-BW 3.1B version.
Thanks in advance

Thanks Anand,
We have already customized the web interface builder as you described it in your preview post. Unfortunately, it doesn't work.
In our case we have two compounded characteristic:
- Portfolio is coumpounded with region
- GR is compounded with Region and Portfolio.
These variables are not displaying the text even with this customizing..
We have tried all the standards settings and also different exits but nothing seem to fix our issues.
Does it come from the BPS version, the exit draw up...?
Many thanks for your attention.
Best Regards.

Display compounded InfoObject value in BEX selection screen

Hi people,
Problem in 7.0
I have Costcenter compounded with Plant and I am using Costcenter for Selections in the BEx varaible screen.
After running the report, in the selection screen value help, only the value of Costcenter is displayed, not the compounded value (So it becomes very difficult to identify from which plant the costcenter is from)
What should I do so that the User sees as Plant/Costcenter in the Value help?
Problem in 3.5
The above issue is not there in 3.5, but.......
I select COSTCENTER X from PLANT A and execute the report. In the report output, I do not see the records only for COSTCENTER X from PLANT A, but for COSTCENTER X from all Plants
why is this? Is it how this works or is it a bug?
Please help. I appreciate your assistance very much.
Thanks,
Shameem

Hey there,
Please understand the behaviour of compounded keys from the below notes:
1111632   Problem with text display in BEx Query Designer
1080863   FAQ: Input helps in Netweaver BI
541253    Restricting characteristics with compound characteristics
575563    Selecting filter values for compound characteristics
Hope this can help,
Diego Seben

BI 7 Upgrade - Problem with Authorisation Variable on Compounded Char

Dear All,
We have just upgraded our DEV environment from 3.5 to BI7 and have encountered a weird problem with 1 of our authorization variables.
Our authorization check variable checks the values from a table that the users are allowed to use (which includes the selection screen). There are 2 variables 1 for the uncompounded char and 1 for the compounded char, the uncompounded variable is working just fine but not the other. When the user tries to pick a value, they are presented with not just their restricted list but ALL the values.
Can anyone explain this? Has BI 7 changes the way authorizations work with Compounded Characteristics ?
Before anyone asks, these variables work just fine on 3.5 and are working just fine in our QA and PRD environments.
Help required urgently.
Thanks
Craig

Hi,
Yes authorisations in BI 7.0 are a bit different from the ones in BW 3.5. Here is the link which will help you know every thing in BI 7.0
bw 7.0
Regards,
Habeeb
Assign points if helpful.

Compounding query

hi
I have created a infoobject(zcomp), It has an attribute which has text values.
Zcomp has a compounding characteristic(Ocomp_code),
I added zcomp into a cube, in this cube, zcomp display as 0000234322. but in query level
it display like 0010/234322. where 0010 is company code. but the texts of 234322 is not displayed.
I think it may happen while adding compounding characteristics, so I want to get texts for Zcomp.
help me

hi,
right click the char in the query and display as Name else in the display option of infoobject definition choose display as text.
Ramesh
Edited by: ramesh kumar on Mar 3, 2008 12:31 PM

How to suppress compounded characteristic data in 7.0

Hi,
In 3.x I could choose a filter value for the compounded characteristics and the values would not display on the query. In 7.0 it doesn't seem to be the case anymore. Has SAP changed the way this works?
For example, in the BI Statistics, I am trying to display user name and the query displays System/User name compounded. I just want to display the user name. In my example, I restricted the values for system by our client (ABP100), however, on the query I still see client/username -- ABP100/FRED. I just want to see FRED.
Thank you,
Brian

Hi Brian,
Its very simple to achieve. Place your Compounded char (that you dont want to display ) just above the char (that u want to display) in row.
In the property of the main char set it to "No display" and "result suppress". then u will get the desired output.
For e.g char B is compounded with char A.
and output comes like A/B, whereas u want to only see B.
Put both A & B in row.
Place A above B and set A's display properties as suggested above, u will get the desired output.
Thanks
Dipika

Master Data: Transformation and DTP for compounded characteristic

Good day
Please assist, I am not sure what is the correct way.
I extract master data from a db via DB connect.
There are three fields in the db view for extraction. (1) Code (2) Kind and (3) Code Text.
What I have done is the following. I created a datasource with transformation and DTP for master data text for (1) and (3), and then a datasource master data attribute transformation and DTP for (1) and (3).
Is this the correct way to handle extracts of compounded characteristics?
Your assistance ill be appreciated.
Thanks
Cj

Hello,
if the char ' Code' is compounded with 'Kind'.
then for text datasource u shld have 1, 2 and 3. the table for this datasource should have 'code' and 'kind' as keys.
for the attribute datasource u shld have 1 ,2 followed by the reqd attributes of 'Code'.
Reagrds,
Dhanya

SAPKW70016 bugs with reference characteristics and attributes

Hi, experts!
I have very big problem.
When we've imported SAP BW SP 16 somthing went wrong as of reference characteristic and attributes.
1) If InfoSet contains reference characteristic, it can't be activated. (Error message RSO404)
2) If transformation rule is "read master data" and source characteristic contain compounded characteristic wiht same attribute as target field, and componded characteristic is above lexicographical then source characteristic. When you save this transformation this source field is removed from transformation rules? transformation can't be activated!!!
3) When you use in compounded characteristics which are reference characteristic and you want to use this source characteristic in rule "read master data" you'll get dump.
Now about reason and trials to resolve this problems.
2) The reason is incorrect sorting and reading internal tables with characters in source fields in transformation with attribute target field. Problem is resolved with using rule "ABAP", FM "RSAU_READ_MASTER_DATA".
3) and 1) The reason is program look for name REFERENCE character in table in field BASE characteristics names. Problem was resolved only fo happen 3) with disable "better" functionality "lookup_master_data" (note 1092539).
Problem 1) is still open...
What can I do?
Thanks for all replies!
P.S. Notes 1116379, 1112742, 1125321 have been implemented.
Best regards,
Antoshkin Vitaly.

Hi, did you try to implement this following notes ?
1158243     InfoSet in MultiProvider: Error message R7I 135
1157410     InfoObject as InfoProvider: Follow-on note for Note 1063194
1152136     Error during master data reading (ERROR_IN_MD_BUFFERING)
1147263     Temporal hier. join characteristic, compounding, attributes
1119777     THJ characteristic for referenced characteristic is missing
1118497     Incorrect where-used list for referencing characteristics
It´s have important corrections for SAPKW70016 version.
I hope that this notes can be helpful.
Best regards,
Walter Oliveira.

ABOUT COMPOUNDING ATTRIBUTE.

Hi
Can 1 InfoObject have more than one Compounding Attribute?
Please let me know.
Thanks in advance

Hi,
Yes one infoobject can have upto 14 infoobjects as Compunding.
You determine whether you want to compound the characteristic to other InfoObjects. You sometimes need to compound InfoObjects in order to map the data model. Some InfoObjects cannot be defined uniquely without compounding.
For example, if storage location A for plant B is not the same as storage location A for plant C, you can only evaluate the characteristic Storage Location in connection with Plant. In this case, compound characteristic Storage Location to Plant, so that the characteristic is unique.
One particular option with compounding is the possibility of compounding characteristics to the source system ID. You can do this by setting the Master data is valid locally for the source system indicator. You may need to do this if there are identical characteristic values for the same characteristic in different source systems, but these values indicate different objects.
Using compounded InfoObjects extensively, particularly if you include a lot of InfoObjects in compounding, can influence performance. Do not try to display hierarchical links through compounding. Use hierarchies instead.
A maximum of 13 characteristics can be compounded for an InfoObject. Note that characteristic values can also have a maximum of 60 characters. This includes the concatenated value, meaning the total length of the characteristic in compounding plus the length of the characteristic itself.
Hope it helps.
Thanks in advance,
V Praveen

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

Multiprovider design

dear all,
The dimension design of infocube are important for performance and each dimension will link to some master data and SID id.
but is this concept still true for a multiprovider? thanks.

Hello,
Check this Thread:
Analysis and Performance tuning of a query
u2022 When the reporting scenario is to be extended, use a MultiProvider as central interface between
query definition and basic InfoProviders. When another InfoProvider is added to the MultiProvider
definition, the technical name of a query based on the MultiProvider remains unchanged.
u2022 Use a MultiProvider to reduce the size of the basic InfoProviders. Advantages: parallel access to
underlying basic InfoProviders, load balancing, resource utilization, query pruning.
u2022 Make sure that your MultiProvider only retrieves data from relevant basic InfoProviders at query
runtime by
o Using constants in the design of the basic InfoProviders
o Using different key figures in the design of the basic InfoProviders
o Using characteristic 0INFOPROV when designing a query on the MultiProvider
u2022 Are you planning to use a MultiProvider? If so, you have to ensure that the characteristics you want
to report exist in all basic InfoProviders.
u2022 Do not use more than one non-cumulative InfoCube (InfoCube with at least one non-cumulative key
figure) because this could lead to incorrect query results.
u2022 Do not use calculations before aggregation on MultiProvider because this may lead to wrong query
results.
u2022 Do not combine basic InfoProviders having inhomogeneous data models in a MultiProvider. Use the
report-report interface between queries defined on the basic InfoProvider instead.
u2022 Avoid using only parts of compound characteristics in the constituent basic InfoProvider of a
MultiProvider. For more information, see SAP note 702542.
Assign points if this helps,
Regards,
Jorge Diogo

Compounding Characteristics

Similar Messages

Maybe you are looking for