Query re universe export

Hi All,
I imported a universe <name of the universe is weekenddemo> from the repository and then renamed it and saved it with name demo_MS. After that I made few changes to demo_MS universe and after that when I tried exporting it back to repository but the universe is getting exported with the old name (with which I initially imported it). Attached is the screen shot showing the same.
Please advise on how to import an existing universe, rename it, and then export the new universe with new name.
Thanks

Hi Mohit,
The universe has two names:
1. File name which is for identifying for windows based folder system(This you will find when you click on Save as). This is Long name of universe.
2. There is a short name also present in File--> parameters of the universe, which is used in the repository.
Try to keep both same.
In your case you changed only Long name and your short name was same as the one you gave previously.
Thanks
Gaurav

Similar Messages

SQL Developer 4.0 EA3. query result in export format problem

Query output in export format (insert, csv, xml,...) is not working in 4.0 EA3.
Query executed as script (F5) does not display anything:
select /*insert*/ * from dual;
SQL Developer 3 displays the result correctly:
REM INSERTING into dual
SET DEFINE OFF;
Insert into "dual" (DUMMY) values ('X');
About
Oracle SQL Developer 4.0.0.13
Version 4.0.0.13
Build MAIN-13.30
IDE Version: 12.1.3.0.41.131007.2031
Product ID: oracle.sqldeveloper
Product Version: 12.2.0.13.30
Version
Component    Version
=========    =======
Oracle IDE    4.0.0.13.30
Java(TM) Platform    1.7.0_07
Versioning Support    4.0.0.13.30

That's been fixed for the next release.

Cascading LOV in BEx Query OLAP Universe + BEx variable

Hi gurus,
we have an universe where a Cascading LOV has been defined based on a BO Hierarchy ( based on a BW hierarchy), the OLAP universe is based on a BEx query.
Now, when the users create a WebI report selecting a value from the value list, the Cascading LOV appears and the user selects the value, descending by the nodes.
We are analyzing the universe performance and we are testing to add some time BEx variables in the query ( in the current version no variables are used).
Everything works properly but when we try to select a value from the Cascading LOV and try to select a lower level the webI returns a mdx error indicanting that the time variable is not informed. (WIS 10901: A database error ocurred; MDX query can not be executed: specify a value for the variable Z... )
We thought that the mdx for the LOV get values from the MD table because in the infoobject definition, it has the Business Explorer Settings:
Query Def. Filter Value Selection = Value in Master Data Table
Query Execution Filter Val. Selectn = Value in Master Data Table
The Query Execution Filter Val. Selectn can be defined at the infoprovider also (with the provider specific Properties of the infoobject) and also at the query, whe have not modify none of them.
My first question is which settings has efect at OLAP Universes, the infoobject settings; the infocube settings or the query settings ?
Are the Cascading LOV integrated with BEx Query OLAP Universe?
Is it an application error?
Many Thanks in advanced.
Best Regards,
Nuria

Hi Ingo,
many thanks for your quick answer.
That was one of the possibilities we have analized but the problem is that the user has to inform the hierarchy level for all the reports, that kind of variables is translated in the universe as a prompt
Now we have only one universe and some business analists users create reports themselves for the business area based on that universe.
The users create WebI filters without prompts,just filtering the hierarchy node. If we add the BEx variable then the user sould inform the prompt for all the reports based on that universe.
We want to avoid that prompt, we have several hierarchies in the query for different infoobjects.
Thanks again.
Best Regards,
Nuria

Universal export for iPhoto

Hi all!
Since I am switching to Lightroom I was looking for universal way to export my photos from iPhoto. It turns out something as simple as exporting albums to folders with album names doesn't exist (or I couldn't find it). Then I found GREAT UNIVERSAL exporter!
http://www.n8gray.org/code/scriptexport
You type in your script actions (unix command line knowledge required).
For example to export album to folder with same name as album:
Preflight: mkdir ~/Desktop/NEW/"$iPAlbumName"
Per-Item: cp "$iPImageSourcePath" ~/Desktop/NEW/"$iPAlbumName"
And volia
You can easy script what you wish...FTP, SSH, format conversion.....
Thank you Nathaniel!

You type in your script actions (unix command line knowledge required).
Unfortunately that requires more than what most of us are knowledgeable in.
Do you Twango?

Universe export - data changes not reflecting in Report

Hi
The changes and the latest updates in the database are not reflecting in reports,
even if i export the universe again.
and i have refreshed the reports, that even not reflecting.
i did Edit query and Run query this action also not bringing the latest data to reports
why this happens ?
how to solve this issue ?
Regards
Dineshkumar

You can search for KB articles on SAP Service Market Place .
Here is first :
Symptom
You make changes a local Universe in Designer.
When refreshing the report, in Desktop Intelligence, the results do not reflect Universe update.
It used to be enough to simply refresh report's data, for Dataprovider to show object changes from the Semantic layer.
Change of behaviour in SP3 codeline: the DeskI Query Panel does not automatically pick up the latest modifications made to the local Universe.
Reproducing the Issue
Using BusinessObjects Desktop Intelligence XIR2 SP3:
Using your universe (eFashion), create and refresh a simple Desktop Intelligence report (.rep).
Make a simple change to the universe (like renaming a field/ object name) and save these changes.
Go back to the open DeskI report and try to refresh the data provider using: 'Data/Refresh Data'.
This will not show the latest changes.
However, if you follow the same workflow using XIR2 SP2, the universe update will be immediately visible (in the report) simply after refresh.
Cause
This is not a product regression, but intentional change in application's code delivered with FixPack3.1.
Fix Request ADAPT00818520 changed the application's behaviour: << When a restricted user is logged on to view a Desktop Intelligence document, prompt windows may be slow to open. >>
Resolution
In Desktop Intelligence menu, go to: Tools > Universes
Click 'Refresh'
Select and 'Import' your universe
Next, go to toolbar menu: Data > Edit Data Provider
In Query Panel, click 'Run' to regenerate the Query and interrogate the updated universe.
Only after following these actions will the .unv ammendments be visible in the report.
Here is second :
Symptom
Changes to object made for the Universe is not affected when refreshed from InfoView if we check 'Allow selection of multiple Contexts' in Universe Designer
Desktop Intelligence (Deski) Report still prompts for selection of contexts even if 'Allow selection of contexts' is unchecked for Universe
Row level Restriction is not applied correctly in InfoView(View Mode) when 'Allow selection of multiple Contexts' checked in the Universe Designer
Environment
BusinessObjects Enterprise XI 3.1 Service Pack 2 Fix Pack 2.6
Reproducing the Issue
Changes to object made in the Universe is not affected in InfoView(View mode) when 'Allow selection of multiple Contexts' is checked in Universe
1. Log in to Designer
i) Import Island Resort Marketing
ii) Go to Universe Parameter >> SQL
ii)Uncheck Allow Selection of Multiple Context
2. Create a new Desktop Intelligence(Deski) Report based on Island Resort Marketing
i) Drag the object Country in the Result's Pane
ii) Save and Export the report to the repository.
3. In Designer Change the Object Country under Resort from Resort_Country.country to
i) Resort_Country.country+'ddd'
Note: Uncheck Allow Selection of Multiple Context
ii) Save and Export the Universe
4. Log in to InfoView
i) View the report
ii) Refresh the report
iii) Changes to the object taken place i.e Country is concatenated with ddd
5. In the Universe Designer, change the Object Country under Resort from Resort_Country.country to
i) Resort_Country.country+'eee'
Note: Check Allow Selection of Multiple Context
ii) Save and Export the Universe
6. Log out from InfoView and login again
i) View the report
ii) Refresh the report
iii) Changes not taken place. Shows only Country instead of Country concatenated with eee.
Row level Restriction is not applied correctly in InfoView(view Mode) when 'Allow selection of multiple Contexts' checked for the Universe.
Import efashion Universe
Drag the Outlet_Lookup table into the objects pane on the left hand side
Create Row Level Restriction on the state field of Outlet_Lookup table as Outlet_Lookup.State=(u2018Texasu2019)
Apply the restriction to Administrator
Save and Export the Universe. Note: Uncheck Allow Selection of Multiple Context in Universe Parameter>>SQL
Log in to Desktop Intelligence (Deski) as administrator with Enterprise Authentication
Create a new Deski report
Drag the object state from the Outlet_Lookup table to the Results pane
Observed that the administrator is able to see only Texas which is expected behavior
Save and export the report
Log in to Infoview as Administrator
View the report. Refresh the report
Observed that the administrator is able to see only Texas which is expected behavior
Log in to Infoview as any user say Test User
View the report. Refresh the report
Observed that Test User is able to see all the states which is expected behavior
In the Universe Designer, Check Allow Selection of Multiple Context in Universe Parameter>>SQL for efashion Universe
Save and export the Universe
Log in to Infoview as Test user
View the report
Refresh the Report
TestUser is able to see only Texas which mean that the restriction is applied to Test User also
Cause
This is by Design as the 'Allow selection of multiple Contexts' forces selection of the context, which is not possible in Infoview, so that in Infoview it is assumed the Context is already selected and no SQL regeneration is required.
Resolution
Problem Description: Changes to object made in the Universe is not affected when refreshed from InfoView if we check 'Allow selection of multiple Contexts' in Universe Designer
Explanation:
If we modify an object and selects also the option 'Allow selection of multiple Contexts', it means that potentially there is more than one SQL that can be generated with the use of that object. Hence if a report is created in Deski, run and exported to enterprise, that means, one particular context (SQL) has been selected.
If you then update one or more of the objects again, the SQL will have to be regenerated in Deski for the right context to be selected for that particular report.
Therefore, if this option is used, for the objects to be updated, the SQL of the report will have to be regenerated in Deski, run and export it back to repository, then refresh the report in InfoView.
For Deski reports viewed in InfoView, it is not possible to evaluate the context on refresh. The report will always use the context stored with the report and same for the SQL. Therefore the Deski report will need to be imported locally, refresh it and then export it back to repository for the changes to take place.
Problem description: Desktop Intelligence (Deski) still prompts for selection of contexts even if 'Allow selection of contexts' is unchecked for Universe
Explanation:
The option 'Allow selection of Multiple Contexts' in Designer is not to disable the prompt. It will prompt you to select context if the object used is associated with context. The option is just to allow Deski to select multiple contexts at a time if in case the object used is associated with multiple contexts and accordingly generates the SQL.
However if we uncheck the option even if there are multiple contexts associated with the object used, it will allow selection of only one context at a time.
Problem Description: Issue with Row level Restriction when refreshed from InfoView with 'Allow selection of multiple Contexts' checked for the Universe.
Explanation:
We first have to regenerate the SQL in Deski, then export it to repository and refresh from InfoView for the changes to take place correctly. The explanation above applies.

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.

White space in parm files foils query for dp export

Hi,
The data pump QUERY option does very strange things with extra white space in parameter files.
If I have any space or a tab between the table name and the colon e.g.
QUERY=UTL_DATA_SYS.LOG_SYSTEM_ERROR :"WHERE 1=2"
I get the following error:
ORA-39001: invalid argument value
ORA-31658: specifying a schema name requires a table name
If I put the white space after the colon, it applies the filter to EVERY TABLE !!!! e.g.
QUERY=UTL_DATA_SYS.LOG_SYSTEM_ERROR: "WHERE 1=2"
. . exported "UTL_DATA_SYS"."SSO_AUDIT_LOG_ARCHIVE" 8.640 KB 0 rows
. . exported "UTL_DATA_SYS"."LOG_SYSTEM_ERROR" 8.921 KB 0 rows
. . exported "UTL_DATA_SYS"."APEX_META_DATA" 7.492 KB 0 rows
. . exported "UTL_DATA_SYS"."SSO_AUDIT_LOG" 8.632 KB 0 rows
. . exported "UTL_DATA_SYS"."LOG_APEX_ACTIVITY_ARCHIVE" 11.92 KB 0 rows
. . exported "UTL_DATA_SYS"."LOG_APEX_ACTIVITY_PG_DAY_SUM" 18.06 KB 0 rows
. . exported "UTL_DATA_SYS"."LOG_APEX_ACTIVITY_USR_WK_SUM" 9.054 KB 0 rows
. . exported "UTL_DATA_SYS"."APEX_IR_COLUMN" 6.515 KB 0 rows
. . exported "UTL_DATA_SYS"."APEX_ITEM_USE" 7.273 KB 0 rows
. . exported "UTL_DATA_SYS"."ALL_WBT_TABLES" 9.617 KB 0 rows
. . exported "UTL_DATA_SYS"."ALL_WBT_USERS" 5.25 KB 0 rows
. . exported "UTL_DATA_SYS"."APEX_META_DATA_KEYWORD" 5.257 KB 0 rows
. . exported "UTL_DATA_SYS"."APPLICATION_PARAMETER" 6.625 KB 0 rows
. . exported "UTL_DATA_SYS"."A_APPLICATION_PARAMETER" 7.929 KB 0 rows
. . exported "UTL_DATA_SYS"."STANDARD_ABBREVIATION" 5.242 KB 0 rows
. . exported "UTL_DATA_SYS"."SYSTEM_LOG_LEVEL_DEF" 5.914 KB 0 rows
. . exported "UTL_DATA_SYS"."APEX_APPL_DETAIL" 0 KB 0 rows
. . exported "UTL_DATA_SYS"."APEX_OBJECT_REL" 0 KB 0 rows
. . exported "UTL_DATA_SYS"."APEX_WBT_INVALID_REFER" 0 KB 0 rows
Master table "SYSTEM"."SYS_EXPORT_SCHEMA_04" successfully loaded/unloaded
If I get everything JUST RIGHT e.g.
QUERY=UTL_DATA_SYS.LOG_SYSTEM_ERROR:"WHERE 1=2"
I DO get the desired result
Processing object type SCHEMA_EXPORT/POST_SCHEMA/PROCOBJ
. . exported "UTL_DATA_SYS"."SSO_AUDIT_LOG_ARCHIVE" 402.1 MB 5121006 rows
. . exported "UTL_DATA_SYS"."LOG_SYSTEM_ERROR" 8.921 KB 0 rows
. . exported "UTL_DATA_SYS"."APEX_META_DATA" 188.5 MB 1472587 rows
. . exported "UTL_DATA_SYS"."SSO_AUDIT_LOG" 82.19 MB 895951 rows
. . exported "UTL_DATA_SYS"."LOG_APEX_ACTIVITY_ARCHIVE" 28.49 MB 177253 rows
etc
Is it unreasonable to ask Oracle to trim white space before it processes these commands? I really appreciate all the power of the data pump, but this is one area that some added work would be appreciated to reduce fragility and avoid unexpected behavior.
Thanks
Steve

Sounds reasonable to file a bug.
Dean

BOE XI 3.1 - Universe Export Restriction

Guys,
Our configuration's are
BOE XI 3.1 SP2.
Windows AD authentication
In our organization we have few developers and few Super Users (Power Users).
Both Developer and Super Users have Universe access. So by default both Developers and Super Users can do Import, Export, Edit and Save, etc functionalities in Universe.
Here my question:
Is it possible to deny 'Export Universe' or 'Save Universe' explicitly to particular users who are all having UNIVERSE access?
If yes then i will restrcit 'Super Users' explicitly.
I have tried many options which are given in tutorial and businessobjects sites. but no hope.
Thank you.

Hi
I would suggest that you have to deny the particular users explicitely the right to create and edit objects in the Universe folder.
Go to the CMC->Universes, navigate to Manage->Top Level security->All universes. Add your particular users as principals there. You can even create previously a user group and set the rights for the group itself. Then select to Assign security and go to Add/remove rights under the Advanced tab. Here you can explicitely deny your users to create and edit objects in this area/folder. That would be enough to stop the specific users from exporting the universes they create into the BOBJ repository.
Regards,
Stratos

Universal export to Excel process

Hello,
I must write pl/sql procedure that exports data to Excel file in XML format. This procedure should be available for all pages in quite big application, so I don’t want to write it by scratch for each report separately. I need more object-oriented way.
Do you know any way to read results of any APEX report region and write it/export to Excel using pl/sql process?
I know how to write XML Excel files and I know I can find region definitions with reports’ queries in APEX_APPLICATION_PAGE_REGIONS view, but I have no idea how to deal with it, especially with pl/sql reports returning string query. How to put this data into cursor, how to declare cursor’s type automatically etc. Maybe I can use some APEX function?
Regards,
Przemek Staniszewski

Przemek:
If it were possible to identify a report region source as being the type 'function returning query' I think it would be a simple matter to execute the specified pl/sql function ( using execute immediate) and obtain the query for the report.
Given the query I think, Denes' code will do the rest.
Varad

Dynamic filter on time characteristics on OLAP SAP BEX query based universe

Dear all,
I'm currently working on the integration between SAP NetWeaver BI 7.0 and SAP BusinessObjects XI 3.1 FP 1.5 via integration kit.
I've built an OLAP universe on the top of a BW query based on a multiprovider that contains 10 infocubes.
Everything works fine but I need to create a filter in the OLAP universe that allows to restrict data by current date (e.g. using TIME characteristic of Infocube such as 0CALDAY or 0CALMONTH). From that filter we could start creating other conditions to compare data to different time periods.
I've already tried to use a SAP exit variable in a BW query but this kind of object would restrict query data only by current date and for example it would be impossible to browse data by previous years (to bypass this problem we could use restricted key figures with different offsets but we have too many key figures in the query and the number of restrictions
would rise exponentially).
In a relational DataBase we can do that using a "where condition" based on 'CURRENTDATE' (SQL DB2 syntax).
Now, we need to apply the same logic but translated in MDX syntax.
Is it possible to enter a dynamic filter in the OLAP universe or just fixed or promt values ?
Any advise?
Thanks in advance.
Best Regards.
M.

Hi Ingo,
1) My question is: "How can I have to manage variable in BEX queries and in the UNIVERSE in order to obtain the maximum flexibility to create reports with measures on actual day (for example) without asking the user to promt a value ?"
I want to use an unique BEX query to define an unique UNIVERSE. On this UNIVERSE I want to create many reports (actual day, previous day, and so on).
If I restrict 0CALDAY with an EXIT variable then shall I be able to create a different restrictions on the same Universe based on 0CALDAY ?
2) Another question is:
Is it possible to insert an XML / MDX filter on the OLAP Universe with dynamic derivation of the system date ?
For example:
Instead of this:
<FILTER KEY="[0FISCYEAR].[LEVEL01].[NAME]">
    <CONDITION OPERATORCONDITION="Equal">
        <CONSTANT CAPTION="Z12008"></CONSTANT>
    </CONDITION>
</FILTER>
Is it possible to insert a tag with a dynamic function to derive the system date ?
Thanks in advance.
Best Regards.

L00 and L01 in BW Query based Universe for Characteristics

Hi All,
While creating a universe based upon an SAP BW query, the BW characteristics seem to be doubled as dimensions, with one group markeded L00 and the other as L01.
Why are they doubled?
Is one "better" than the other?
For what purpose?
They key value in L00 returns "all" and L01 returms the key, but all attributes seem to be the same.
Thanks for your help,
John Hawk

Hi,
From an OLAP point of view a characteristic is like a dimension, that means that it contains all the members (level L01) and the All member that aggregates the characteristic members (level L00);
These metadata are provied by SAP BW when using OLAP drivers.
For a characteristic, the level L00 is not necessary unless you want to use the All member.
On the other hand, the level L00 is significant for hierarchies, hierarchy varaibles and structures because it contains members.
We provide an option for the universe generation and the universe update that allows to generate or not the level L00.
This option is available since BOE XI3.1 SP2.
In SP3, we improved the L00 generataion to only impacts the characteristics and not hierarchies and structures.
So the recommendation for characteristics is to not use L00.
Regards,
Didier

Errors when querying against universe with DBlink tables

Running XI 3.1
DB1: MS SQL Server
DB2: Oracle 11g
Universe created on DB2 has linked tables from DB1.
I created a view as Select * from table@DB1
Using Webi Rich Client: successful query results
Using Webi Lite: ORA-12154 error: TNS:could not resolve the connect identifier specified
Using Deski: ORA-01002: fetch out of sequence. ORA-02063: preceding line from DBlink_name
I've tried numerous array fetch size parameters but Deski still has that error message. Is there a different way to fetch data from a DBLink table? Why no errors when using Webi Rich? when creating universe against DBlink tables
Thanks

In our environemnt, we have encountered ORA-4030 and ORA-4031 in the past in one particular windows server. What i remember from that is , a single process in windows will be limited to use 2Gb of memory(irrespective of how much you allocate and how much RAM the server has). All the oracle user and server processes in windows has to get their share from this 2Gb allocated to a single process called oracle.exe. There is some way to extend this 2Gb limit to 3Gb or 4Gb by enabling a switch on some windows config file. You can easily get that by google.
Check the memory used by oracle.exe in 10g server's task manager.
Next, you may need to reduce SGA size... to give more room for user processes. You may investigate on these lines.

Need help to change BO generated query at universe leavel

Hi
Is there any possiblity to change sql at universe leavel.Kindly help me i am new to designer.
The below is the BO generated query.
SELECT specObjID
FROM SpecObj
WHERE SpecClass = dbo.fSpecClass('UNKNOWN')
Users are not intrested to go for coustomised sql in report leavel.
I need to change the above sql accordingly due to some performance issues.
The feilds that specify in the where clause SpecClass = dbo.fSpecClass('UNKNOWN') move to from clause.
Like below
SELECT specObjID
FROM SpecObj ,SpecClass = dbo.fSpecClass('UNKNOWN')
WHERE
Kindly suggest me greatly appriciated.
Thanks.
Raj

HI,
As per your expectation query like below is not possible to give condition in from clause as per my understand,
SELECT specObjID
FROM SpecObj ,SpecClass = dbo.fSpecClass('UNKNOWN')
WHERE
I think your expected result can be achieved by giving condition while creating the object SpecObj.
Steps:
Go to universe, then edit the object SpecObj there you can give the where clause condition
WHERE SpecClass = dbo.fSpecClass('UNKNOWN')
This will increase your performance.
Regrds,
Ragoth.C

Variables from BEx Query through Universe - separated by data provider

Hi,
I have a universe that is being used multiple times within a WEBI report, however, I'd like to select the BEx Queries' variables that come through as prompts separated by query. (multiple queries, multiple prompts; one for each)
For example, I have variables that come through for Exchange Rate type, and I'd like to select query 1 as Exchange Rate Type A, and select query 2 as Exchange Rate type B. At present, the prompting only offers me one input for all data providers that is the same.
A similar functionality exists within BEx Analyzer that is a workbook setting, does something like this exist on WEBI or in the Designer?
Thanks in advance!

I am not sure if anything like what you ask exists.
In such cases I create the prompts in WEBI that gives me control to define the prompts separately for each query.
Edited by: Mathangi Kuppusamy on Sep 1, 2011 2:59 AM

Universe export issues

Hi Guys,
I am on development environment. I am trying to export one universe which has secured connection to the repository but still it is giving error "universe cannot be exported"
As an alternative,
I created a new connection as secured, saved the universe and tried to export, giving the above error. it says the universe is not exported be-cos its connection type is not secured.
Thanks in advance
Speedsin

Hi,
You may not have export access when working from local system. So If you have remote access to client environment then try exporting unv in client environment and if you still face same problem then it would be better to take help of our admin.
Before that delete all the unv's in unv folder then save it and try to export it.
Cheers,
Suresh Aluri.

Query re universe export

Similar Messages

Maybe you are looking for