Long Description and Short Description

Dear All,
I have a dimension with three levels.
1. District (district_id, district_name)
2. Council(Council_id, council_name)
3. Address(person_id, address, postcode, phone....)
I have set the district_id, council_id and person_id as SHORT DESCRIPTION and the district_name, council_name, and address as LONG DESCRIPTION.
BUT when I view the data (right click dimension -> Data) It shows me the surrogate id (which are negative ids) instead of the Textual fields i.e. district_name, council_name and Address.
Please, tell me how can I see all the textual fields instead of seeing the surrogate keys?
regards
P.S. I am using OWB 11g on SUSE

Hi
OWB provides the mechanics to extract from a bunch of resources, design schemas and models as well as load into them but it is not a reporting tool. The metadata that is used by the OWB data viewer is also used by this excel component and it works right off the database (as far as I remember). This will let you build cool reports right off the bat from the models built and loaded by OWB.
Cheers
David

Similar Messages

My screen is now long horizontally and short from top to bottom.

so now all the cars I search for are long! my friend who is computer savvy tried to help.
HELP,
Stranded in looooongville,
Duckydoodle
PS i still have the buttons at the top.

Try to disable hardware acceleration in Firefox (you need to close and restart Firefox).
*Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"
*https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
You can rename (or delete) the content-prefs.sqlite file to content-prefs.sqlite.old in the Firefox profile folder to reset the page zoom for all websites.
You can use this button to go to the Firefox profile folder:
*Help > Troubleshooting Information > Profile Directory: Show Folder (Linux: Open Directory; Mac: Show in Finder)
*http://kb.mozillazine.org/Profile_folder_-_Firefox

Equivalent rect long and short sides

Not so sure if anybody else already came across this problem or not. Any suggestion is welcome.
I have a simple isolated object to be fitted into an ideal rectangle which will then be used for a metrology purpose in following step. I was trying to make use of the equivalent rect long and shot sides from particle analysis operation, but it seems the particle analysis always gives a same value to the long side and short side. Attached picture shows the calculation results from vision assistant. I tried to calculate the equivalent rect sides from the given area and perimeter. The results tends to become complex values as the perimeter seems smaller than it should be(i.e.. P^2 smaller than 16*A). It may be one reason to produce same value to equivalent rect long and short side.
PS: the expression for calculation of equivalent rect long and short side in the page: http://zone.ni.com/reference/en-XX/help/372916L-01/nivisionconcepts/particle_measurements/ seems not right. It should be (P-sqrt(P^2-16A))/4, rather than P/4-sqrt(P^2-16A).
Attachments:
results from vision assistant.jpg ‏131 KB
ROI.jpg ‏8 KB

Hi paris_sun,
I am assuming you are using the latest version of Vision Assistant 2011 SP1.
I would just like to clarify what you are trying to achieve. This is to measure the long and short (length and width) side of a rectangular shape in your image by using:
Processing Functions: Binary >> Particle analysis
Something I could suggest is to play around with a more definative rectangle and see if this helps. I have tried using a rectangle and the measurements have come out fine.
The shape you are measuring happens to have the same size dimensions i.e. a square.
Where are you acquiring your image from? And are you expecting it to be a square?
With regards to the formulas being incorrect I will look into this for you.
Kev R
Kevin R
Applications Engineer
National Instruments UK&Ireland
Attachments:
NI Vision Rectangle.jpg ‏373 KB
Rectangle.jpg ‏8 KB

Alert description and short text

Hi Masters,
I configured BPM alerts in my scenario with alert category define in ALRTCATDEF and I have selected dynamic test. I am getting the alert and long text as I given in BPM alert message that is good. But in my alert, message description and Short text is displaying as ' Process <xxxxxxx>'.
So can I get the same message as long text in messsage description and short text and how to change the description.
Please help me to find out the soultion for this
Reg,
Shiv

Is any other way to get the message description

Display Key and Long Description

Is there any way to display the Key and Long Description for a hierarcy in a query? It looks like the only option is to display Key and short description or Long Description only.
Thanks,
Ron

Hi
These are the basic steps:
1. upgrade to BW 3.5
2. choose to display as key and text
3. choose key + long text
the following links says the step by step procedure to do it:
http://help.sap.com/saphelp_nw04/helpdata/en/22/27813b731fd60ee10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/af/27813b731fd60ee10000000a114084/frameset.htm
Regards,
Naveen P

Short, long Description not showing up when loading Catalogs

Hello:
When I load the internal catalogs, the short and long description is not coming over. It seems like a bug since I can see it sometimes.
We are current up to date on the SRM/CCM patches but we are still <b>not</b> getting the description data.
Has anyone experience the same situation?
Thanks again in advance!

Hi Mike,
You say you are loading internal catalog and next you talk of SRM/CCM patches.
Hence I assume you generating SRM_EXTRACTED_CATALOG.
(you can load internal catalog from R/3 also.)
Pl. check whether these short and long description are present in SRM transaction COMMPR01
because if present there then only you can see in your catalog.
BR
Dinesh

Need table with Variant ID and Long Description

Hello,
I have a list of ZPAK_* infopackages that I want to translate to their Long Description names. I can search by the Variant ID in RSA1 and find the name but this is a long process and I have over 100 infopackages.
Does anyone know of a table that has both of these fields?
Thank you

Thank you
You saved me an afternoon of mindless cutting and pasting

Multi Language Description and Long description update.

Hi Guru,
I would like to know the possible ways to upload the description and long description in multiple languages for the existing items in mass. For newly created items, we can enter the data in language form tied to the description.
Is it possible to do with APC WebADI.? or any other suggestion would be highly appreciable.
Venkatesh

I solved the problem by myself. It's a customizing with OBVU.
Hope it can help others.
Andy

Problem in choosing Long Description Attribute in AWM

While creating a dimension,both Short Description Attribute and Long Description Attribute can not be checked in simultaneously.Even though I tried to check both the options while creating but during data mapping it is showing only short description attribite.
Is there any workaround you can give me to declare both Short and Long Description Attribute simultaneously.

Never seen before. What version?

InfoSet Query - Long Description while selecting variable values

Dear Experts,
We have an InfoSet Query on different InfoObjects like 0CUSTOMER, 0CUST_COMPC etc and the common link between these InfoObjects is CUSTOMER.
We have a variable created on this CUSTOMER. The requirement is that when this query is executed, user should be able to select a value of Customer (F4 help) and at that time, he should be able to view both Key and Long Text of Customer.
We know that if we change the CUSTOMER InfoObject --> BEx Properties tab, then we can display Long Text and Key in Query Selection Screens. However we can not do that because it would affect all queries in which this InfoObject is used.
If we go to Query Design, and choose "Long Text and Key" in properties of Customer, then system displays Long Text and Key of Customer but after the report execution is done.
We want to display the Long Text of Customer to User at the time of selection and that too without making any InfoObject level change.
If it was InfoProvider, we could have done it using "Provider specific properties of Characteristic" option. But this is InfoSet and that option does not appear here.
Please suggest the solution.
Regards
P

Rohit,
Are you looking to display long text for infoobject instead of short description ?
Then go tp rsd1>infoobject>display/change-->master data/texts -->text table properties -->check long text exists.
It supports a long text field with a length of 60 characters
Activate the infoobject
--Doodle
Message was edited by: Doodle

Discoverer Plus not showing changed Long Description Attribute for dimesion

We have created Discoverer reports on OLAP AWM cubes.
We modified Long description and short description for one dimension.
Now in Analytical Workspace it shows correctly modified Long and short labels.
However Discoverer report still shows Old Value. When we try to create new report on same cube, then also it shows old long and short label.
We are using 10g AWM.
Can anyone help.

We have created Discoverer reports on OLAP AWM cubes.
We modified Long description and short description for one dimension.
Now in Analytical Workspace it shows correctly modified Long and short labels.
However Discoverer report still shows Old Value. When we try to create new report on same cube, then also it shows old long and short label.
We are using 10g AWM.
Can anyone help.

Show Material Group Long Description in SRM Product Category ?

Hi,
We have entered Short and Long Decriptions for Material Groups in R/3 and we have run the replication too. We want to show the Long Description of the Product Category to the users on the web screens.
We know there is a setting in SRM to do this but we don't know what it is.
Please let me know if any one has idea.
Thanks
venkatesh p

Hi Venkatesh,
You can only transfer one of the two descriptions, if you want Long desc, go to
SM30
COMC_HIERARCHY
NEW ENTRIES
SELECT TRANSFER 60 CHAR DESC.
Thanks
Ravi

Material group long description

In the item overview section of a PO we're only able to see the short description of a material group when a search is done. However, when we go to the item detail section of the PO and do a search on the material group field there, we get both the short and long description. Is there a way to get both the long and short descriptions when you do a search on any material group field?

Hi Eric;
I'm in version ECC 7 - and both the short/long description are available at the item search by material group in the PO. What version are you on? Have you looked through SAP Notes (p.k.a. OSS Notes) for the patch that may resolve this issue?
Good luck!
Edited by: DeLong Gina on Jan 8, 2008 6:48 PM
Edited by: DeLong Gina on Jan 8, 2008 6:52 PM

Long description

How can we findout the technical name and short,long description of an infoobject?.
Regards,
Srinivas,

Just double click on the object..
Regards --- Kumar Sarvepalli

Dimension with 2 Hierarchies, Lowest Member w/ Different Long Descriptions

I'm trying to create a dimension that would allow Discoverer For OLAP users to choose between different LONG DESCRIPTIONs, and I am trying to accomplish this by using multiple hierarchies.
For example, when a user is trying to create a report and eventually stumbles upon the Dimensions part of the Workbook creation, he can choose a different description other than the default by choosing from the Hierarchy drop down list.
The following is the dimension details:
Dimension: TEST_DIM
Hierarchy #1: HIER_NAME
Levels: TOTAL_DIM_NAME
        TEST_LVL_NAME
Hierarchy #2: HIER_CODE
Levels: TOTAL_DIM_CODE
        TEST_LVL_CODE
Dimension View: V_TEST_DIM
Fields: TOTAL_DIMENSION_NAME_ID   ---mapped to--> TOTAL_DIM_NAME
        TOTAL_DIMENSION_NAME_DESC ---mapped to--> TOTAL_DIM_NAME_LONG_DESCRIPTION
        NAME_LEVEL_ID             ---mapped to--> TEST_LVL_NAME
        NAME_LEVEL_DESC           ---mapped to--> TEST_LVL_NAME_LONG_DESCRIPTION
        TOTAL_DIMENSION_CODE_ID   ---mapped to--> TOTAL_DIM_CODE
        TOTAL_DIMENSION_CODE_DESC ---mapped to--> TOTAL_DIM_CODE_LONG_DESCRIPTION
        CODE_LEVEL_ID             ---mapped to--> TEST_LVL_CODE
        CODE_LEVEL_DESC           ---mapped to--> TEST_LVL_CODE_LONG_DESCRIPTION
Cube: TEST_CUBE
Measure: TEST_MEASURE
-----------------------------------------------------------------------------------------With the above dimension having 2 hierarchies, Discoverer users can choose between HIER_NAME or HIER_CODE. The problem with this setup is that for this to work, different fields must be mapped to the lowest levels of each hierarchy, because the values of NAME_LEVEL_ID and CODE_LEVEL_ID fields from the V_TEST_DIM dimension view are different from each other, even though they share the same set of records, which means they can be considered as one.
The values of NAME_LEVEL_ID and CODE_LEVEL_ID must be different, because if they are not, I receive the following error during maintenance:
***Error Occured: Data for at least One of the Hierarchies for TEST_DIM.DIMENSION controdicts the Definition of such Hierarchy as Level
Based.After making the NAME_LEVEL_ID and CODE_LEVEL_ID values different from each other, I tried mapping the fact table to the cube. Mapping details are as follows:
Cube View: V_TEST_CUBE
Fields: TEST_VALUE       --mapped to--> TEST_MEASURE
        NAME_LEVEL_ID    --mapped to--> TEST_DIM.TEST_LVL_NAME.NAME_LEVEL_ID
     CODE_LEVEL_ID    --mapped to--> TEST_DIM.TEST_LVL_CODE.CODE_LEVEL_ID
-----------------------------------------------------------------------------------------Unfortunately, the above mappings does not work, because I get the following error when I do so:
Invalid Mapping:
Levels in a dimension TEST_DIM have to be mapped to the same column for summary fact_tableBut despite the error(s) above, I've actually made this work, by leaving the one ID field (NAME_LEVEL_ID or CODE_LEVEL_ID) unmapped. Say, I map NAME_LEVEL_ID to TEST_DIM.TEST_LVL_NAME.NAME_LEVEL_ID but leave CODE_LEVEL_ID unmapped, then maintain to load data for TEST_DIM (HIER_NAME hierarchy). Then I unmap NAME_LEVEL_ID and map CODE_LEVEL_ID. I maintain the cube again to load data for the other hierarchy which is HIER_CODE.
Now, if that works, why won't AWM let me map NAME_LEVEL_ID and CODE_LEVEL_ID at the same time?
I tried running the following DML command to manually map the fields:
call set_measure_key_expression('TEST_CUBE.MAPGROUP1.CUBEMAPGROUP',NA,'TEST_DIM.HIER_NAME.LEVEL\nTEST_DIM.HIER_CODE.LEVEL','VIEW_OWNER.V_TEST_DIM.NAME_LEVEL_ID\nVIEW_OWNER.V_TEST_DIM.CODE_LEVEL_ID',FALSE)I checked the mappings afterwards and the two fields are indeed mapped, but when I try to maintain, I got an error stating that 'VIEW_OWNER.V_TEST_DIM.NAME_LEVEL_ID\nVIEW_OWNER.V_TEST_DIM.CODE_LEVEL_ID' does not exits or something like that.
Does any know a better way to implement this?
Please help.

I understand what you are trying to achieve, and technically it should be possible. In practice, however, Disco caches dimensional information as it is not expecting information such as descriptions to change from one query to the next.
The complication is the description objects do not have any additional dimensionality beyond their base dimension, however, there is a language dimension that might be useful in this case. If you created an additional language with a formula that calls a program to set the underlying AWM language dimension you could assign this measure to the first worksheet in your workbook and allow users to swap between different versions of their long descriptions. However, this would be a session wide setting and not worksheet specific.
In the AWM tree you will need to add additional languages to your AW which can then be used a placeholders for your different descriptions. This will affect all your dimensions so you will need to either use OLAP DML to copy the base language descriptions to all the other languages or using the mapping editor.
In the dimension mapping tool you will now see multiple entry points for descriptions - English, French, German etc depending on which languages you picked. You can assign any column from your source view/table to these columns.
Should work - I did something similar for another customer. It is not ideal, and does require the users to open/create a worksheet to switch the descriptions but it was all I could think of at the time.
Keith Laker
Oracle EMEA Consulting
BI Blog: http://oraclebi.blogspot.com/
DM Blog: http://oracledmt.blogspot.com/
BI on Oracle: http://www.oracle.com/bi/
BI on OTN: http://www.oracle.com/technology/products/bi/
BI Samples: http://www.oracle.com/technology/products/bi/samples/
Does that make sense?

Long Description and Short Description

Similar Messages

Maybe you are looking for