Remove prefix L01 from olap universe

HI Experts
I need to remove L01 or prefix from the object name in olap universe ... i found tools- options in that there is replace preifx l00, l01 but i am nable to use it properly can some one help
Example : if object is L01 business partner it should appear Business partner only it should not have L01
regards

You can find some handy tool Based on VBA to mass update the texts of your universe and replace the L00 and L01 prefixes. As far as i could find out in XI 3.1 currently is the only way, unless you want to do it manually one by one. Have a look at the links below. I can confirm that it works.
[http://www.forumtopics.com/busobj/viewtopic.php?t=21029&postdays=0&postorder=asc&start=0]
[Remove L01 prefix from Olap uni;

Similar Messages

Error when passing URL from OLAP Universe to WebI

Hi Experts,
I am getting 'The Supplier XML is not valid' WebI error when passing a URL from OLAP Universe.
URL example:
'<a href="http://www.sap.com">web link</a>'
I follow Universe Designer Guide:
- typing above URL into Dimension Select statement
- selecting Read As Hyperlink in Object Format.
When I drop this dimension into Result Objects panel in WebI Query and run refresh 'The Supplier XML is not valid' pops up.
What i am trying to achive is to create a pre-formatted as Hyperlink object (dimension) in WebI to make it available for a user to design ad-hoc reports.
Please help
Thanks

Hi,
Refer the below forum link for more information:
Universe object format in Web Intelligence
I guess you can do some changes in the format of Universe object and use it in Webi.
-Noor.

Remove prefix numbers from filename

There are like 500 photos which have numbers prefixed before their name. They are all in iphoto 09. The Batch change options doesn't allow text to be replaced. The automator action for renaming finder items does allow replace however one has to specify what to replace, which in my case would be random numbers from 1 to 900. Is there any way I can prefix this images from 1 to 500 by first replacing the first three characters from the images, which in our case are all different numbers?
Neerav

Hi Neerav,
Maybe you can try doing this with an applescript. After you get/select the files somehow in Automator, add the *Run Applescript* action after that. Add this piece of code after the *on run {input, parameters}* line:
repeat with thisFile in input
tell application "Finder"
set fileName to name of (thisFile as alias)
set fileName to (do shell script "echo " & quoted form of fileName & " | sed 's/^[0-9]*//'")
set name of thisFile to fileName
end tell
end repeat
This will delete any numbers that appear in the beginning of the file name. This approach is better than deleting the first three characters in case the numbers aren't padded with leading zeroes.
Anyway, I haven't tested this script myself so back up some files and run it on a such a small sample so that if there are any bugs (I don't expect any) we can remove them.
Message was edited by: hungryjoe

Remove prefix ns from target xml

Hi Guys,
I have a target file that is as follows
<?xml version="1.0" encoding="UTF-8"?>
<ns:MT_Case1 xmlns:ns0="urn:Case:Case1">
<Field1></Field1>
<Field2></Field2>
<Field3></Field3>
< ns /MT_Case1>
How can I remove the pre fix ns from the target xml?
can ne one help pls?
Edited by: Ravindra Teja on Jul 6, 2011 6:58 PM
Edited by: Ravindra Teja on Jul 6, 2011 7:00 PM

You can add or remove the namespace prefix using XMLAnonymizerBean module.
Refer this [link|http://help.sap.com/saphelp_nw04/helpdata/en/45/d169186a29570ae10000000a114a6b/content.htm]
BTW, this namespace prefix might not cause any impact.. What do u test? If the namespace prefix nso is removed using xmlspy editor then you dont get namespace prefix in the element tag.

OLAP Universe Refresh creates error

Hi,
we built an OLAP universe based on BEx Query. SAP Netweaver 7.0 EHP1, BO XI3.1 SP3 FP2, BW Integration Kit XI3.1 SP3 FP2.
BEx query contains 4 Filters that need user input.
When we create the universe for the first time, everything works fine and the Filters with variables are created as Universe Filters with prompts and LoVs.
Everytime when we refresh the universe structure, the MDX syntax of 2 of the Filters in the universe is added again which is causing an error at runtime. So when refreshing the universe 2 times, we see the MDX filter syntax 3 x in the condition field.
The filters have not been changed or moved, so we do not see why 2 filters are refreshed and 2 get addtional code. It also happens with other BEx Queries/Universes.
Thx for ideas

Hi Ingo,
we did not remove the filters from the universe.
"Added again" means, that when I refresh the universe structure, the pane with "added Elements" shows 2 filters that existed already in the universe. Universe designer adds them again.
These are the filters that create the problem.
When I open the filter syntax in the universe, the refresh added the MDX code again, so that it contains the MDX twice.
With every refresh the filter-MDX-code is added again. But only at 2 of 4 filters.
Rgds,
LK

Remove L01 prefix from Olap uni

HI Experts
In my webi doc . i should not have L01 prefix from the olap universe.
For ex: if i have L01Country from olap uni . i should only have country in webi.
My issue is i can edit object properties and do it but how to do it at once when there are around 2000 or more object details i cant edit each and every one .
any procedure to hide it r remove it at universe level
Regards

i think this link may help you
http://www.forumtopics.com/busobj/viewtopic.php?t=21029&postdays=0&postorder=asc&start=0
good luck
Amr

PO Approval Items Workitems are not removed from the Universal Worklist UWL

Hi,
Certain of our purchase orders require approval, they are sent to the relevant approver via workflow to their SAP inbox (SBWP) and universal worklist.
When the user executes the workitem (Approve or Reject) The workitem should be removed from the universal worklist and SBWP when refreshed.
The problem we experiencing is that the Workitems are not removed from the UWL after they have been executed. The SBWP is behaving correctly and the items are removed.
It is not all the workitems that have this problem, only certain ones - but there is no pattern.
Thanks for the help.

Hi,
The user B approved the PR accessing the transaction SBWP or via PR transaction directly?
If via PR transaction directly, then your workflow needs a Wait Event step.
Regards,
Kleber

To remove work item from Universal worklist

Hi,
Can we remove work item from Universal Worklist by deleting. We don't want to approve or reject them but want to remove from inbox.
Is there a way for this?
Regards
PV

Hi Parveen,
check the below note
check below note
Note 49545 - Deleting unnecessary work items
Koti Reddy

Who removed user from AD Universal secuirty group

Hello , i am trying to find who removed user from universal AD group , i checked audit management policy is enabled but some how event is not getting generated or unable to find those events so please help how to find who did that job - removed the user
from universal security group.
And suppose if anybody is deleting and the logs should be generated on one of the local site Domain controller is that correct ? so anywhere or it can be generated on the member server. Any free third party tool who can help here .
Thanks

Here is another informative technet blog resource that helps to track all the changes made in active directory : http://blogs.technet.com/b/askpfeplat/archive/2012/03/05/how-to-track-the-who-what-when-and-where-of-active-directory-attribute-changes-part-i-the-case-of-the-mysteriously-modified-upn.aspx
If you wish to audit such changes automatically, you may also consider on this automated solution (http://www.activedirectoryaudit.com/) that would be a better approach to audit all the critical changes
into real time and get instant notification for through customized email notification.

Error querying OLAP universe based on BEx query

Hi all,
I have a problem extracting larger (more than 80 000 rows) amounts of data through querying an OLAP universe with WebI.
The error is:
Query 1 - NAME_OF_THE_QUERY
A database error occurred. The database error text is: Error in MDDataSetBW.GetCellData. &INCLUDE INCL_INSTALLATION_ERROR. (WIS 10901)
The error occurs when I define larger scope of analysis in the query (four levels). With more modest scope (three levels or less) it's working OK. I need larger data set (more than 200 000 rows) to be populated at night through scheduling the report. We can't afford shrink the scope of analysis because it will hit the BW server during the day when it's needed by other users.
Besides this the speed of the report refresh is very slow - more than 3 minutes per just 400 rows of data. I'm still unable to identify the source of the problem with this slowdown. Executing the same query over the web through the SAP BW BEx Viewer is much much faster - just 3 seconds. Maybe the reason for this is that the BEx viewer aggregates data on the higher level of the hierarchy rather than down to transaction level (like we do by expanding the scope of analysis).
Anyway, if anyone have ideas about the error above I'll be very grateful if you share your thoughts. Thanks!
Our environment:
BO EDGE BI 3.1, standard
SAP BW 3.0
SAP Integration Kit (all transports installed)
BW user with full access

Ingo,
Could you point me to an official SAP document regarding the 1 million cells limitation, which describes the exact version and patch level for SAP BW which removes this limitation? It will be very helpful for me because I have to convince the client to migrate BW from 3.0 to 7.01 if it will solve this limitation.
Thank you in advance!
Ivan
BTW I have installed SP2 + FP2.1 and now the SAP integration is not functional, but I have opened another thread for this problem.

OLAP Universe creation process questions and proposals

We have created an OLAP universe based on a BW-Query. The automatical creation of the OLAP universe does not produce a satisfying result.
We are working with the latest available releases (BOE XI 3.1 SP2 and SAP Integration KIT SP2, SAP BI 7 EHP1).
We have detected that all dimension objects store the name instead of the key field.
Example:
Customer Dimension Object (L01 Customer) = Customer Name
Customer Key Detail Object (L01 Customer Key) = Customer Number
Customer Name Detail Object (L01 Customer Name) = Customer Name
This is not usable for end user because of the following reasons:
1. The detail objects can not be used for merge dimensions, so it is not possible to merge on the supplier number.
2. If you filter on the dimension object you will only see the text in the list of values (LOV) and it is not possible to edit the list of values in the universe to add the supplier number to the LOV as it is possible in relational universes
3. If the user select the detail object always the dimension object in inserted into the report query
4. The "Business Explorer" general setting "Display" of an InfoObject has no effect on the OLAP universe dimension object. If you change it to key always the text is shown. Even if you change the "ValueDisplay as" in the underlying BW Query to "key" is has no effect.
5. The renaming of the L01 object to blank is not possible. You need to rename to " " and then remove on each object the blank.
So we need to modify manually every universe to change the "detail key object" to a "dimension object" and the "detail name object" to reference the new "dimension object" with the key. This manual process has a huge work effort in time. Is there a better solution or enhancements planned in the next releases?
Additionally there should be an option to disable the automatic creation of each characteristic as a subclass in the universe. A wizard should ask if a subclass should be created or not for each characteristic. Currently there are to many subclasses generated which were mostly not needed.

Hi,
First of all I would say u are lucky to start with SP2. Because whatever modifications you do in Universe those are retained.
We had a big trouble in using BOXIR3.1 FP1.7.
Anyways.. Back to your Questions and My asnwers for those:
1. The detail objects can not be used for merge dimensions, so it is not possible to merge on the supplier number.
Ans: True, Dimension object always shows Short text values by default. but if you can create the logic at SAP BI query level to map short text with keys then your problem will be solved.
2. If you filter on the dimension object you will only see the text in the list of values (LOV) and it is not possible to edit the list of values in the universe to add the supplier number to the LOV as it is possible in relational universes.
Ans: True u cannt edit LOV, but alternate solution to it is create the variable in SAP BI Query, that will appear as prompt in universe which will display the List of values with Key as well as Description.
3. If the user select the detail object always the dimension object in inserted into the report query.
Ans: Logically its correct, because Detail object is always associated with Dimension. Buit if you dont want that dimension in query you can remove that dimension by dragging back.
4. The "Business Explorer" general setting "Display" of an InfoObject has no effect on the OLAP universe dimension object. If you change it to key always the text is shown. Even if you change the "ValueDisplay as" in the underlying BW Query to "key" is has no effect.
Ans: In Query designer even if you ValueDisplay as "Key", but at Object level if there is Text and Key associated for perticulat Infoobject, then so by default the dimension will show the Text and there will be seperate Detail object in universe for Key.
5. The renaming of the L01 object to blank is not possible. You need to rename to " " and then remove on each object the blank.
Ans: Yes this is a big trouble.
Regards,
Nisha

OLAP Universe Filter for Constant

Hello
I am trying to create a universe filter. We have a BO OLAP Universe on top of MSAS 2008. We are at BOXI 3.1 SP2/FP2.2
<FILTER KEY="[Date].[Calendar Date].[Date]"><CONDITION
OPERATORCONDITION="InList"><CONSTANT
CAPTION="[Today].item(0).MEMBER_CAPTION"/></CONDITION></FILTER>
Where [Today] is a calculated member.
This one parses fine, however when it comes to MDX which i capture via
profiler
WITH SET NS28B9BE741FD446A5A0414EA718F8FC_0 AS Filter([Date].[Calendar
Date].levels(4).allmembers,((([Date].[Calendar
Date].currentmember.properties("CAPTION")="[Today].item
(0).MEMBER_CAPTION"))))
SELECT { [Measures].DefaultMember } ON COLUMNS ,
NS28B9BE741FD446A5A0414EA718F8FC_0 DIMENSION PROPERTIES
MEMBER_UNIQUE_NAME, MEMBER_CAPTION ON ROWS FROM [My Cube]
This returns empty. However it works fine and returns value if i remove "" wrapping
[Today].item(0).MEMBER_CAPTION and run this query in SQL Server Management Studio ( MDX query)
However i cannot introduce the same in the filter - if i try it gives
me a parse error.
i.e the following doesnt help
<FILTER KEY="[Date].[Calendar Date].[Date]"><CONDITION
OPERATORCONDITION="InList"><CONSTANT
CAPTION=[Today].item(0).MEMBER_CAPTION/></CONDITION></FILTER>
Can you kindly advise if you have seen similar errors and what i can do possibly in this case to workaround this?
Edited by: ramaks on Oct 26, 2010 2:35 AM
Edited by: ramaks on Oct 26, 2010 2:36 AM
Edited by: ramaks on Oct 26, 2010 2:37 AM

Hi Didier,
Thank you for your response. That was exactly my original design - but it has performance implications for us. Please see an earlier thread of mine.
Query Performance in OLAP MSAS Universe using Filter
In this Case the MDX will become as below.
Which means every additional dimension i add creates multiple cross joins, and the filter will go through all possible cross-join combination to filter out that one record for that particular date. My original thread explains this more clearly.
Is there no other way to implement such a filter?
WITH
MEMBER [Measures].[2FF3DF31-5D02-4A9B-A8,BC,E7,25,C2,30,1B,61] AS
    IIF
        [Date].[Calendar Date].CurrentMember.Properties("CAPTION")
      =
        [Today].Item(0).Member_Caption
     ,1
     ,0
SELECT { [Measures].DefaultMember } ON COLUMNS ,
,NON EMPTY
    Filter
              CrossJoin
            AddCalculatedMembers
              [Date].[Calendar Date].[Date].MEMBERS
      [Measures].[2FF3DF31-5D02-4A9B-A8,BC,E7,25,C2,30,1B,61] = 1
DIMENSION PROPERTIES
MEMBER_UNIQUE_NAME, MEMBER_CAPTION ON ROWS FROM [My Cube]
Edited by: ramaks on Oct 26, 2010 4:26 PM

Can we Implement YTD using MDX syntax in olap universe.

Hi,
I am trying to implement YTD prompt from universe level. Can any one suggest how can i implement it using MDX syntax in olap universe.
Regards,
Anil Kumar.

Hi,
In MDX, you need to generate the technical name to have you expression valid.
Moreover the correct syntax is: SUM(MTD(member),measure)
So in your case the prompt must be constrained on the technical name and cannot be free, the correct syntax is:
<EXPRESSION> SUM(MTD(@Prompt('YYYYMM','A','Cal. year / month\L01 Cal. year / month',mono,primary_key)),
@(Select(Key Figures\Total Variance)) </EXPRESSION>
Last, the result will be not really significant because you are asking for a MTD with a Year-Month as time member: the result will be the measure value for the selected month.
In your case you need to have a time series function for an upper level like YTD or QTD. If you want to use MTD, the the time member selected would be at a lowest level, such as week or day.
Regards
Didier

OLAP universe cannot use SSO after Fix Pack 2.3

hi
our dev box can use OLAP universe with SSO authenticantion, after I apply FP2.3 this does not work any more
and I get the following error: DBD UNABLE TO CONNECT SAP BW SERVER INCOMPLETE LOGON DATA,
anyone encounter same issue
thanks

Hi Andreas Madsen
I log a case with SAP, and they point me to the same SAP note.
Basically what they trying to say is, once you install Xcelisius on the server, and applied SP2 and FP2.X you are stuffed.
Since your error is only on your client, then you should consider removing all the BO software on your client and reinstall it agian from scratch.
For me, I need to rebuild the whole server from ground up.
I asked for a special fix, but was rejected
I was advised to install Xcelsius and CR on server for troubleshooting purposes, but seem like this is really a bad idea now.

SAP BW OLAP Universe performance issue

Hi,
Based on BO recommendation, I created a universe on top of a big BEX query which included all characteristics and key figures from a cube. I then created a webi report with 5 characteristics and 1 key figure from this universe. I also create the same report in BEX query designer(same number of objects). I ran both. The Bex query completed under a minute and the webi report took more than 12 minutes to run. I did a bunch of other test with different number of objects combination and saw similar differential in query performance.
I did a trace using 'sm50' and saw the open SQL submitted to BW from BEx was very different from what got submitted from the webi report. Here is what I saw in pseudo code.
Bex:
select dimension1.blah, dimension2.blah, dimension3.blah, dimension..... sum(measure)
from dimension1, dimension2, dimension3, dimension..... factTable
where dimension1.SID = factTable.d1SID
and dimension2.SID = factTable.d2SID
and ......
and (query filters)
OLAP Universe
select dimension1,blah, dimension1.SID
from dimension1, factTable
where dimension1.SID = factTable.d1SID
select dimension2,blah, dimension2.SID
from dimension2, factTable
where dimension2.SID = factTable.d2SID
select dimension3,blah, dimension3.SID
from dimension3, factTable
where dimension3.SID = factTable.d3SID
It seems the OLAP universe was querying the BW cube one dimension at a time and then somehow piece the result sets together to form the final result set. Dimension tables join to the fact table without any filter definitely causes performance issue. Beside, I have no idea why the query requests are submitted to the BW system like that.
I looked in varies forums and found no similar issues posted by others. Has anyone had any performance problem with there OLAP universe? Is this a matter of configurations?
My envrionment:
SAP BW 3.5
BOXI 3.0
ORACLE DB (version ??)

Hi,
You cannot compare a BEx query and a universe query by just comparing the trace.
BEx query makes ABAP calls and universe query makes MDX calls;
Moreover there is only one MDX call sent to SAP, what you have noticed is that there is one MDX call to retrieve member for a given characteristic whereas a prompt has been set on.
Last, Web Intelligence consume only flattened data (row sets) wheras BEx consume data sets.
That means that there is a flattening operation between SAP OLAP engine and the data sent to the Web Intelligence document.
A fix have been developed for a customer to improve performance on Web Intelligence queries, this fix will be available for all customers in SP2 planned in June 09.
Here is a a brief summary of what the fix provide:
- Provide data directly from SAP server to Web Intelligence document. Avoid unnecessary conversion steps: row set --> data set --> row set
- Eliminate redundant sort operations
- Other optimization operations
Didier
Edited by: Didier Mazoue on Nov 20, 2008 8:38 AM

Remove prefix L01 from olap universe

Similar Messages

Maybe you are looking for