RRI target selections same as source query

Hi BI Experts,
As per my requirement the input of the target query should be same as the first query. i.e..,
if A ,B,C,docnumber are the variables of two queres and if i fill Variable A in query one and in the result of the first query i right click on first docuemnt and goto target query then the slection citeria of the target query is Variable A and the document number as well.But the user doesnt want the docnumber to be carried to target query.
Please let me know your views in achieving the issue
Regards,
Madhu

Hi,
Please check the requirements correctly. Usually users will jump from summary report to detail report.
Confirm with the user if requirement is correct or not.
If you dont want to provide the docnumber in the target query, ask user to click on the filed that is available in the target query, If he click on the document then user will not get any data in the target report.
Thanks
srikanth

Similar Messages

Warning "Source selection for is incompatible for target selection" in RRI

Hi Friends,
I am getting the following warning message while jumping from one query to another(RRI) :
Source selection for is incompatible for target selection
I have also found one SAP Note : Note 1265027 - Incompatible selection for a variable in the target query which states that it is a program error and we have to Import Support Package 04 for SAP NetWeaver BI 7. 01 (SAPKW70104) into your BI system for SAP NW BI 7.0 Enhancement Package 1.
But the problem is we are already in Support Package 04 .After that also we are facing the same problem.
Can anyone please let me know how to fix this issue?Is anyone faced such an issue.
Thanks in advance.
Regards,
Debjani..

check if the correction instruction given in the note is present in your system.

Passing Source Query Variables to Target query in RRI

Hello,
I Creating Jump Queries.
In the source query user is entering some variable(Dates), based on these varaibles I am creating formula variable in the source query.
I wanted pass the same varible values(which are entered by user) to target values(RRI) and use the same formula varaible in the target query.
Please advise me how can I do this.
Thanks
Venkat

Hello Venkat,
Please refer to note 1053310 for complete details about RRI and application rules.
The variables are passed implicity but you can explicity defined the rules for varaibles as well. You can define assignment details as required. I hope this will help.
Thanks and Regards,
Asit G Ramteke

In Procedure command, source query results not passed to target as # variables - why not?

Hi all,
I'm using ODI 11.1.1.6.0.
Has anyone had issues with this version with this feature?
I've just upgraded from 10.1.3.4.5.6_02 and feature doesn't work at all (not even in new procedures!) in my repository.
I've even tried creating a brand new repository then creating a new data server, new physical schema, new logical schema, mapped physical schema to the logical schema, and created a new procedure that does:-
Source tab (Oracle): SELECT scen_name FROM snp_scen
Target tab (ODI Tools): OdiStartScen -SCEN_NAME=DUMMY -SESSION_NAME=#scen_name
The session that's created has the name "#scen_name" and not the name from the result of the source query.
The DUMMY scenario is just generated from another procedure that has a single OdiSleep command.
Any ideas chaps?

Yet another bug...
Fixed in 11.1.1.6.4.

Passing YTD selection from a main query to a detailed query using RRI

Hi,
We have created two queries: one main query on an infocube for aggregated data, one detailed query on the feeding DSO for data at the level of sales document items.
Both queries show monthly and YTD (year-to-date) actual cost figures.
The user enters for instance the month of 05.2005 on the main query in a variable ZP_MONTH.
A user exit variable ZS_YTD is calculated so that the interval 01.2005 - 05.2005 is stored in ZS_YTD.
Revenues in the month are displayed in one column.
Revenues in the YTD period are displayed in another column.
Assume the data is displayed by document types.
Then the user should select the document type and perform a jump target (Goto) to the detailed query to see which sales document items are contributing to the total revenues behind the document type.
We have defined a ZS_YTD_2 variable on the detailed query. It is used in the field assignments in the RSBBS transaction to receive the 0CALMONTH selection (in our case 01.2005 - 05.2005). Then on the detailed query, we defined another userexit variable to capture the selected month based on ZS_YTD_2.
Our issue is that when the user goes from the main query to the detailed query, the variable screen of the detailed query is being displayed with the variable ZS_YTD_2 open and the user can even change the selection there.
Is it possible to remove the display of this intermediate variable screen?
Thanks.

Well. If you unflag the variable for ready for input on the detailed query, then it is not possible for that variable to receive the period selected on the main query. Even worse, the query crashes with the message that the variable is not correctly defined.
Any other suggestion?
Thanks.

Need to genereate Target file name same as Source File Name thru Local J2SE

Hi Everyone,
I want to genereate Target file name exactly same as Source File Name. I know how to handle this in Central Adapter Engine(Sender & Receiver Communication Channel).
But I need to do this in Local J2SE adpater engine.
Please help me in this regard.
Thanks & Regards,
Nagaraju

U can use the parameter to save the filename in the message header
file.messageAttributes=<name,directory>
This is similar "Adapter-Specific Message Attributes" concept.
http://help.sap.com/saphelp_nw04/helpdata/en/6f/246b3de666930fe10000000a114084/frameset.htm
Regards,
Prateek

Keeping table name same in source and target

is it possible to keep the table name the same in source and target (they're on sepearte databases). Seems like OWB wants to rename the output table (usually adds 1 on the end). When I tried to rename I got a message saying that table name exists.

In my mapping.
First I defined a source and a target. The table on the target doesn't exist yet.
I open mapping editor...drag the table from my source. Let's call it TABLE_A. Then I add Table operator to the mapping (choose create unbound operator with no attributes option). For the name I choose TABLE_A...however when I click OK it then changes the name to TABLE_A_1.
So I double click on the table and change the name to TABLE_A and then I get the message that the table already exists.

Selecting same column twice makes query slow

Hello,
Has anybody any idea why following statement is slow when selecting the
DATA_TYPE column twice?
SELECT S.OWNER,
S.SYNONYM_NAME,
UCOL.COLUMN_NAME,
UCOL.DATA_TYPE,
UCOL.DATA_TYPE,
UCOL.DATA_LENGTH,
COLUMN_ID
FROM ALL_SYNONYMS S,
ALL_TAB_COLUMNS UCOL
WHERE S.TABLE_OWNER = UCOL.OWNER
AND S.TABLE_NAME = UCOL.TABLE_NAME
and S.owner = 'REPORTING_TEST'
and S.SYNONYM_NAME = 'OV_COMMERCIAL_ENTITY_JN'
Replace the owner and table name with one of your own.
If you take one of the DATA_TYPE's out the select is much faster.
Why, I hear you ask, do you select the same column twice?
Well, it's not me. It's BusinessObjects when it does a structure refresh it
produces a statement similar to the one above except that one of the
DATA_TYPE's is a SUBSTR + DECODE (however they in themselves
have virtually no impact on the statement). I just find it weird that repeating
a column twice can have such a dramatic impact on performance.
I'm not a tuning expert and have looked at EXPLAIN PLAN outputs but can't
make head nor tail of them.
Thanks,
Ruud

Yes it's true that Oracle caches data but I did run both statements several times within the same session. Run statement 1, run statement 2, add 2nd column and run again, take column away and run again, etc. Always the results were the same. The query with duplicate columns ran in seconds, the one without in milliseconds.
If it tells you anything, below both explain plans. The main difference that I noticed is the full table scan on USER$ for the first query. The second one (although a more elaborate execution plan) seems to use indexes more.
Don't spend too much time on this. I've found a workaround where I create temporary tables for ALL_SYNONYMS and ALL_TAB_COLUMNS and re-direct the public synonyms to point at those. After I've done what I wanted to do with BusinessObjects, I restore the original public synonyms. Next thing I'll try is rebuilding my database from scratch and see if the problem is still there.
Apologies if the listings come out in variable font (how do you paste fixed font?).
=== SQL1 ====================================================
EXPLAIN PLAN FOR
SELECT UCOL.COLUMN_NAME,
UCOL.DATA_TYPE,
UCOL.DATA_TYPE
FROM ALL_SYNONYMS S,
ALL_TAB_COLUMNS UCOL
WHERE S.TABLE_OWNER = UCOL.OWNER
AND S.TABLE_NAME = UCOL.TABLE_NAME
AND S.owner = 'REPORTING_TEST'
AND S.SYNONYM_NAME = 'OV_COMMERCIAL_ENTITY_JN'
Explained.
Elapsed: 00:00:00.04
SQL> @E:\Oracle\Product\10.2.0\db_1\RDBMS\ADMIN\utlxpls.sql
Plan hash value: 1692851197
| Id | Operation | Name |
| 0 | SELECT STATEMENT | |
| 1 | NESTED LOOPS | |
| 2 | NESTED LOOPS | |
| 3 | NESTED LOOPS | |
| 4 | TABLE ACCESS BY INDEX ROWID | USER$ |
|* 5 | INDEX UNIQUE SCAN | I_USER1 |
| 6 | VIEW | ALL_TAB_COLUMNS |
|* 7 | FILTER | |
| 8 | NESTED LOOPS OUTER | |
| 9 | NESTED LOOPS OUTER | |
| 10 | NESTED LOOPS OUTER | |
| 11 | NESTED LOOPS OUTER | |
| 12 | NESTED LOOPS | |
| 13 | NESTED LOOPS | |
| 14 | TABLE ACCESS FULL | USER$ |
| 15 | TABLE ACCESS BY INDEX ROWID| OBJ$ |
|* 16 | INDEX RANGE SCAN | I_OBJ2 |
|* 17 | TABLE ACCESS CLUSTER | COL$ |
|* 18 | INDEX UNIQUE SCAN | I_OBJ# |
|* 19 | TABLE ACCESS CLUSTER | COLTYPE$ |
|* 20 | INDEX RANGE SCAN | I_HH_OBJ#_INTCOL# |
|* 21 | TABLE ACCESS BY INDEX ROWID | OBJ$ |
|* 22 | INDEX RANGE SCAN | I_OBJ3 |
| 23 | TABLE ACCESS CLUSTER | USER$ |
|* 24 | INDEX UNIQUE SCAN | I_USER# |
|* 25 | TABLE ACCESS CLUSTER | TAB$ |
|* 26 | INDEX UNIQUE SCAN | I_OBJ# |
| 27 | NESTED LOOPS | |
| 28 | FIXED TABLE FULL | X$KZSRO |
|* 29 | INDEX RANGE SCAN | I_OBJAUTH2 |
|* 30 | FIXED TABLE FULL | X$KZSPR |
|* 31 | TABLE ACCESS BY INDEX ROWID | OBJ$ |
|* 32 | INDEX RANGE SCAN | I_OBJ2 |
|* 33 | TABLE ACCESS BY INDEX ROWID | SYN$ |
|* 34 | INDEX UNIQUE SCAN | I_SYN1 |
Predicate Information (identified by operation id):
5 - access("U"."NAME"='REPORTING_TEST')
7 - filter(("O"."TYPE#"=3 OR "O"."TYPE#"=4 OR "O"."TYPE#"=2 AND NOT
EXISTS (SELECT 0 FROM "SYS"."TAB$" "T" WHERE "T"."OBJ#"=:B1 AND
(BITAND("T"."PROPERTY",512)=512 OR BITAND("T"."PROPERTY",8192)=8192)))
AND ("O"."OWNER#"=USERENV('SCHEMAID') OR EXISTS (SELECT 0 FROM
"SYS"."OBJAUTH$" "OBJAUTH$",SYS."X$KZSRO" "X$KZSRO" WHERE "OBJ#"=:B2
AND "GRANTEE#"="KZSROROL") OR EXISTS (SELECT 0 FROM SYS."X$KZSPR"
"X$KZSPR" WHERE "INST_ID"=USERENV('INSTANCE') AND ((-"KZSPRPRV")=(-45)
OR (-"KZSPRPRV")=(-47) OR (-"KZSPRPRV")=(-48) OR (-"KZSPRPRV")=(-49) OR
(-"KZSPRPRV")=(-50)))))
16 - access("O"."OWNER#"="U"."USER#")
17 - filter(DECODE("C"."PROPERTY",0,'NO',DECODE(BITAND("C"."PROPERTY",
32),32,'YES','NO'))='NO')
18 - access("O"."OBJ#"="C"."OBJ#")
19 - filter("C"."INTCOL#"="AC"."INTCOL#"(+))
20 - access("C"."OBJ#"="H"."OBJ#"(+) AND
"C"."INTCOL#"="H"."INTCOL#"(+))
21 - filter("OT"."TYPE#"(+)=13)
22 - access("AC"."TOID"="OT"."OID$"(+))
24 - access("OT"."OWNER#"="UT"."USER#"(+))
25 - filter(BITAND("T"."PROPERTY",512)=512 OR
BITAND("T"."PROPERTY",8192)=8192)
26 - access("T"."OBJ#"=:B1)
29 - access("GRANTEE#"="KZSROROL" AND "OBJ#"=:B1)
30 - filter("INST_ID"=USERENV('INSTANCE') AND ((-"KZSPRPRV")=(-45) OR
(-"KZSPRPRV")=(-47) OR (-"KZSPRPRV")=(-48) OR (-"KZSPRPRV")=(-49) OR
(-"KZSPRPRV")=(-50)))
31 - filter("O"."TYPE#"=5)
32 - access("O"."OWNER#"="U"."USER#" AND
"O"."NAME"='OV_COMMERCIAL_ENTITY_JN')
33 - filter("S"."NAME"="UCOL"."TABLE_NAME" AND
"S"."OWNER"="UCOL"."OWNER")
34 - access("O"."OBJ#"="S"."OBJ#")
Note
- rule based optimizer used (consider using cbo)
=== SQL2 ====================================================
EXPLAIN PLAN FOR
SELECT UCOL.COLUMN_NAME,
UCOL.DATA_TYPE
FROM ALL_SYNONYMS S,
ALL_TAB_COLUMNS UCOL
WHERE S.TABLE_OWNER = UCOL.OWNER
AND S.TABLE_NAME = UCOL.TABLE_NAME
AND S.owner = 'REPORTING_TEST'
AND S.SYNONYM_NAME = 'OV_COMMERCIAL_ENTITY_JN'
Explained.
SQL>
SQL> @E:\Oracle\Product\10.2.0\db_1\RDBMS\ADMIN\utlxpls.sql
Plan hash value: 3285788911
| Id | Operation | Name |
| 0 | SELECT STATEMENT | |
| 1 | TABLE ACCESS BY INDEX ROWID | OBJ$ |
|* 2 | INDEX UNIQUE SCAN | I_OBJ1 |
| 3 | TABLE ACCESS BY INDEX ROWID | OBJ$ |
|* 4 | INDEX UNIQUE SCAN | I_OBJ1 |
| 5 | TABLE ACCESS BY INDEX ROWID | OBJ$ |
|* 6 | INDEX UNIQUE SCAN | I_OBJ1 |
| 7 | TABLE ACCESS BY INDEX ROWID | OBJ$ |
|* 8 | INDEX UNIQUE SCAN | I_OBJ1 |
| 9 | TABLE ACCESS BY INDEX ROWID | OBJ$ |
|* 10 | INDEX UNIQUE SCAN | I_OBJ1 |
|* 11 | FILTER | |
| 12 | NESTED LOOPS OUTER | |
| 13 | NESTED LOOPS OUTER | |
| 14 | NESTED LOOPS OUTER | |
| 15 | NESTED LOOPS OUTER | |
| 16 | NESTED LOOPS | |
| 17 | NESTED LOOPS | |
| 18 | NESTED LOOPS | |
| 19 | NESTED LOOPS | |
| 20 | NESTED LOOPS | |
| 21 | TABLE ACCESS BY INDEX ROWID| USER$ |
|* 22 | INDEX UNIQUE SCAN | I_USER1 |
|* 23 | TABLE ACCESS BY INDEX ROWID| OBJ$ |
|* 24 | INDEX RANGE SCAN | I_OBJ2 |
| 25 | TABLE ACCESS BY INDEX ROWID | SYN$ |
|* 26 | INDEX UNIQUE SCAN | I_SYN1 |
| 27 | TABLE ACCESS BY INDEX ROWID | USER$ |
|* 28 | INDEX UNIQUE SCAN | I_USER1 |
| 29 | TABLE ACCESS BY INDEX ROWID | OBJ$ |
|* 30 | INDEX RANGE SCAN | I_OBJ2 |
|* 31 | TABLE ACCESS CLUSTER | COL$ |
|* 32 | INDEX UNIQUE SCAN | I_OBJ# |
|* 33 | TABLE ACCESS CLUSTER | COLTYPE$ |
|* 34 | INDEX RANGE SCAN | I_HH_OBJ#_INTCOL# |
|* 35 | TABLE ACCESS BY INDEX ROWID | OBJ$ |
|* 36 | INDEX RANGE SCAN | I_OBJ3 |
| 37 | TABLE ACCESS CLUSTER | USER$ |
|* 38 | INDEX UNIQUE SCAN | I_USER# |
|* 39 | TABLE ACCESS CLUSTER | TAB$ |
|* 40 | INDEX UNIQUE SCAN | I_OBJ# |
| 41 | NESTED LOOPS | |
| 42 | FIXED TABLE FULL | X$KZSRO |
|* 43 | INDEX RANGE SCAN | I_OBJAUTH2 |
|* 44 | FIXED TABLE FULL | X$KZSPR |
Predicate Information (identified by operation id):
2 - access("O"."OBJ#"=:B1)
4 - access("O"."OBJ#"=:B1)
6 - access("O"."OBJ#"=:B1)
8 - access("O"."OBJ#"=:B1)
10 - access("O"."OBJ#"=:B1)
11 - filter(("O"."TYPE#"=3 OR "O"."TYPE#"=4 OR "O"."TYPE#"=2 AND NOT
EXISTS (SELECT 0 FROM "SYS"."TAB$" "T" WHERE "T"."OBJ#"=:B1 AND
(BITAND("T"."PROPERTY",512)=512 OR BITAND("T"."PROPERTY",8192)=8192)))
AND ("O"."OWNER#"=USERENV('SCHEMAID') OR EXISTS (SELECT 0 FROM
"SYS"."OBJAUTH$" "OBJAUTH$",SYS."X$KZSRO" "X$KZSRO" WHERE "OBJ#"=:B2
AND "GRANTEE#"="KZSROROL") OR EXISTS (SELECT 0 FROM SYS."X$KZSPR"
"X$KZSPR" WHERE "INST_ID"=USERENV('INSTANCE') AND ((-"KZSPRPRV")=(-45)
OR (-"KZSPRPRV")=(-47) OR (-"KZSPRPRV")=(-48) OR (-"KZSPRPRV")=(-49) OR
(-"KZSPRPRV")=(-50)))))
22 - access("U"."NAME"='REPORTING_TEST')
23 - filter("O"."TYPE#"=5)
24 - access("O"."OWNER#"="U"."USER#" AND
"O"."NAME"='OV_COMMERCIAL_ENTITY_JN')
26 - access("O"."OBJ#"="S"."OBJ#")
28 - access("S"."OWNER"="U"."NAME")
30 - access("O"."OWNER#"="U"."USER#" AND "S"."NAME"="O"."NAME")
31 - filter(DECODE("C"."PROPERTY",0,'NO',DECODE(BITAND("C"."PROPERTY",
32),32,'YES','NO'))='NO')
32 - access("O"."OBJ#"="C"."OBJ#")
33 - filter("C"."INTCOL#"="AC"."INTCOL#"(+))
34 - access("C"."OBJ#"="H"."OBJ#"(+) AND
"C"."INTCOL#"="H"."INTCOL#"(+))
35 - filter("OT"."TYPE#"(+)=13)
36 - access("AC"."TOID"="OT"."OID$"(+))
38 - access("OT"."OWNER#"="UT"."USER#"(+))
39 - filter(BITAND("T"."PROPERTY",512)=512 OR
BITAND("T"."PROPERTY",8192)=8192)
40 - access("T"."OBJ#"=:B1)
43 - access("GRANTEE#"="KZSROROL" AND "OBJ#"=:B1)
44 - filter("INST_ID"=USERENV('INSTANCE') AND ((-"KZSPRPRV")=(-45) OR
(-"KZSPRPRV")=(-47) OR (-"KZSPRPRV")=(-48) OR (-"KZSPRPRV")=(-49) OR
(-"KZSPRPRV")=(-50)))
Note
- rule based optimizer used (consider using cbo)

RRI - How to edit the Receiver query

Hello All,
As per http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/156e3fefa13042e10000000a114084/frameset.htm
I created a Target for my query (sender). The target or receiver query is also a BeX query in the same system.
Now in my sender query, I have Department in my rows and Employees in the columns. When I double click on Department, it takes me to Target but it does not show the report in the format I want. How do I modify the receiver query?
Also if someone has good knowledge in RRI, it would be really helpful if you can help me out with my query?
Thanks in advance
Regards,
Abhishek

Hi Abhishek,
-- Characteristics that are to be filled from the sender query should be defined as free characteristics. A hierarchy node restriction, for example, can also be transferred to free characteristics as a property.
-- Changeable variables for the receiver query are not filled by the RRI.
-- Selections for various InfoObjects are transferred if the InfoObjects have the same reference characteristic.
When the RRI is called, the sender query transfers the following filters to the receiver query:
·        global filters
·        values in the navigation block (dynamic filters including the presentation hierarchy)
·        filters from the restricted key figure selected
·        filters from the drilldown characteristics selected
The system first fills the variables and then fills the navigation block. In order to do this, a unique characteristic assignment must be possible. Selections for various InfoObjects can then be transferred, as long as the InfoObjects reference the same basic characteristic. Hierarchy nodes are triggered in selections and can then be transferred to the respective InfoObjects.
See this link and if any further questions get back to me :
http://help.sap.com/saphelp_nw04/helpdata/en/c9/bc2d38c4b3f205e10000009b38f8cf/frameset.htm
Assign Points if Helps !!
Regards,
Naveen Rao Kattela

Problems selecting paper bin/source with some printers drivers

Hi,
I'm using CR2008 SP2 .NET SDK.
With some printers drivers i'm unable to set the correct paper source in the print options.
For example, if I use Toshiba e-series PLC driver (you can find it here:drivers and select, for example, the e-STUDIO281C printer).
Even if i set the correct paper source on the report designer when i print it through code (without applying any changes to the report) the report is always printed by the default paper source defined at the printer preferences.
The same thing happens when you do it through the designer.
I already tried the following workaround but without any success: at the CR Designer, go to the File Menu, and choose Page Setup. Under Page Options, check the Dissociate Formatting Page Size and Printer Paper Size. This often helps with these issues. Resave the report, and see if that works any better.
Is there any known issues with printer drivers and CR2008?
(This thread was originally posted in [.NET Development forum|Re: Problems selecting paper bin/source with some printers drivers])

Oops, sorry my mistake. I'll leave it here for now.
How CR works is to get the Printer info from the DEVMODE structure, which is where the printer driver settings and configurations are saved for each printer installed.
What I've seen plenty of times before is within the DEVMODE structure there is one area called DMExtra and in that structure it holds various custom options. Quite often the issue is we query that structure to get info but the problem lies in the driver returning an invalid structure size and therefore CR can't use any custom settings.
Same type of issue if they use an uncommon (ENUM) value for the paper size. In code you can see this in debug mode. But if you simply pass the values as pointers and not attempt to alter them at all CR should not alter what the designer used and saved in the RPT file when the reprot was designed.
What can happen when CR loads the printer info it fails due to problems with the printer itself. There are missing files from the install of the printer which cause Crystal to stop getting the info.
Try this on a clean PC with no other printers installed, Install just that printer driver and then install Crystal Reports. If it still fails then we know it could be Crystal having problems with that driver. You may want to post your issue with the printer manufacturer also. They may be able to test also and determine if it is a CR or their driver issue. They can download a trial version of CR for testing.
Trial lin is: Direct link to the Trial version: http://www.sap.com/solutions/sapbusinessobjects/sme/freetrials/index.epx
If that's not an option you could purchase a support case here for one of our Engineers to escalate to R&D. If it turns out to be a CR problem then you'll get a credit for the case, if it is a printer driver problem then no credit.
Single Case Purcahse is: http://store.businessobjects.com/store/bobjamer/DisplayProductByTypePage&parentCategoryID=&categoryID=11522300?resid=-Z5tUwoHAiwAAA8@NLgAAAAS&rests=1254701640551
Be sure to tell them it needs to go to the Report Designer team first.
There is also a possibilty their driver has issue with Windows OS and the .NET framework. Crystal reports is also UNICODE compliant so the printer driver would have a better success rate if their driver was also unicode compliant.
Bottom line is if it doesn't work in Crystal Designer it won't work in code either.
Thanks again
Don

Is it possible to use same data source for two info cube

Hi,
My Problem is in BW we can not have value of material at storage location level.In R/3 also value is maintained at plant level.
Then we searched and we found out one hot to doc for summarized display of stock values on storage location level.
Problem is that we have gone live in last December and we are using " 0AFMM_C02 " and it contains around 1,81,26,000 records. and according to note we have to use
"0IC_C03".
Both the cube uses same data sources for the data.So, how to get the data for "0IC_C03".
and how to delete the data of existing info cube.And is it possible to delete data selectively from the info cube.
Pls. help.
Regards,
viren.

Hi,
You can't create update rule from PSA.You can create from the infosource or from ODS or from cube to cube or ODS to ODS.
In your scenario, what you can do is create update rules from the ODS to the new cube and then transfer the data from there. Or from the Infosource create rules to the new data target and then upload the full data and then set up the delta.
Third option is to create update rules from the existing cube to the new cube and then load all the data one time. Then you can deactivate the update rules as that was needed only for 1 time data transfer.
Cheers,
Kedar

Attribute as Selection parameter in a Query?

Hi,
Can we add an Attribute of MAT_SALES as a Selection parameter in a Query.
MAT_SALES is already available in Free characteristics in the query along with its attributes, it is not allowing me to make any changes to the existing one.
I assume, we need to change the Attribute as a Navigational one and then add in Selection criteria.
Can someone suggest on the same.
Thanks
Bhanu

You have to make the attribute navigational in 0MAT_SALES and then go into your cube/ods/data target and make it a navigational attribute there as well. If you are using a multiprovider on top of your data target, then you also need to make it navigational there as well.
Brian

How can I use the same data source twice?

in our system there is already a complete transfer of calculations to BI (0CO_PC_PCP_01).
However I want to create a new data flow from ERP starting from the same data source.
Is this possible?
Thanks for help!!

Hi!
welcome to SDN forums.
anydata source can be mapped only to a single infosource. but it will not ristrict you to have different datatargets from a single infosource. so you have to use filters in infopackages to select the data target and filter the data for this data sources. Only thing you have to do with old dataflow is just ristrict the data relavent for the 1st Datatarget in old Infopackage and re.initialize.
with regards
ashwin

What are differences between the target tablespace and the source tablespac

The IMPDP command create so manay errors. But the EXAMPLE tablespace is transported to the target database successfully. It seems that the transported tablespace is no difference with the source tablespace.
Why create so many errors?
How to avoid these errors?
What are differences between the target tablespace and the source tablespace?
Is this datapump action really successfull?
Thw following is the log output:
[oracle@hostp ~]$ impdp system/oracle dumpfile=user_dir:demo02.dmp tablespaces=example remap_tablespace=example:example
Import: Release 10.2.0.1.0 - Production on Sunday, 28 September, 2008 18:08:31
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Master table "SYSTEM"."SYS_IMPORT_TABLESPACE_01" successfully loaded/unloaded
Starting "SYSTEM"."SYS_IMPORT_TABLESPACE_01": system/******** dumpfile=user_dir:demo02.dmp tablespaces=example remap_tablespace=example:example
Processing object type TABLE_EXPORT/TABLE/TABLE
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
CREATE TABLE "OE"."CUSTOMERS" ("CUSTOMER_ID" NUMBER(6,0), "CUST_FIRST_NAME" VARCHAR2(20) CONSTRAINT "CUST_FNAME_NN" NOT NULL ENABLE, "CUST_LAST_NAME" VARCHAR2(20) CONSTRAINT "CUST_LNAME_NN" NOT NULL ENABLE, "CUST_ADDRESS" "OE"."CUST_ADDRESS_TYP" , "PHONE_NUMBERS" "OE"."PHONE_LIST_TYP" , "NLS_LANGUAGE" VARCHAR2(3), "NLS_TERRITORY" VARCHAR2(30), "CREDIT_LIMIT" NUMBER(9,2), "CUST_EMAIL" VARCHAR2(30), "ACCOUNT_MGR_ID" NU
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
CREATE TABLE "IX"."ORDERS_QUEUETABLE" ("Q_NAME" VARCHAR2(30), "MSGID" RAW(16), "CORRID" VARCHAR2(128), "PRIORITY" NUMBER, "STATE" NUMBER, "DELAY" TIMESTAMP (6), "EXPIRATION" NUMBER, "TIME_MANAGER_INFO" TIMESTAMP (6), "LOCAL_ORDER_NO" NUMBER, "CHAIN_NO" NUMBER, "CSCN" NUMBER, "DSCN" NUMBER, "ENQ_TIME" TIMESTAMP (6), "ENQ_UID" VARCHAR2(30), "ENQ_TID" VARCHAR2(30), "DEQ_TIME" TIMESTAMP (6), "DEQ_UID" VARCHAR2(30), "DEQ_
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
. . imported "SH"."CUSTOMERS" 9.850 MB 55500 rows
. . imported "SH"."SUPPLEMENTARY_DEMOGRAPHICS" 695.9 KB 4500 rows
. . imported "OE"."PRODUCT_DESCRIPTIONS" 2.379 MB 8640 rows
. . imported "SH"."SALES":"SALES_Q4_2001" 2.257 MB 69749 rows
. . imported "SH"."SALES":"SALES_Q1_1999" 2.070 MB 64186 rows
. . imported "SH"."SALES":"SALES_Q3_2001" 2.129 MB 65769 rows
. . imported "SH"."SALES":"SALES_Q1_2000" 2.011 MB 62197 rows
. . imported "SH"."SALES":"SALES_Q1_2001" 1.964 MB 60608 rows
. . imported "SH"."SALES":"SALES_Q2_2001" 2.050 MB 63292 rows
. . imported "SH"."SALES":"SALES_Q3_1999" 2.166 MB 67138 rows
Processing object type TABLE_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."REGIONS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."REGIONS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."COUNTRIES" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."COUNTRIES" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."LOCATIONS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."LOCATIONS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."DEPARTMENTS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."DEPARTMENTS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOBS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOBS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."EMPLOYEES" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."EMPLOYEES" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOB_HISTORY" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOB_HISTORY" TO "EXAM_03"
ORA-39112: Dependent object type OBJECT_GRANT:"OE" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"OE" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/INDEX
ORA-39112: Dependent object type INDEX:"OE"."CUSTOMERS_PK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"OE"."CUST_ACCOUNT_MANAGER_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"OE"."CUST_LNAME_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"OE"."CUST_EMAIL_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"PM"."PRINTMEDIA_PK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMER_CREDIT_LIMIT_MAX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMER_ID_MIN" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMERS_PK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"PM"."PRINTMEDIA__PK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
ORA-39112: Dependent object type CONSTRAINT:"IX"."SYS_C005192" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUSTOMERS_PK" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_ACCOUNT_MANAGER_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_LNAME_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_EMAIL_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"PM"."PRINTMEDIA_PK" creation failed
Processing object type TABLE_EXPORT/TABLE/COMMENT
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
ORA-39112: Dependent object type REF_CONSTRAINT:"OE"."CUSTOMERS_ACCOUNT_MANAGER_FK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39083: Object type REF_CONSTRAINT failed to create with error:
ORA-00942: table or view does not exist
Failing sql is:
ALTER TABLE "OE"."ORDERS" ADD CONSTRAINT "ORDERS_CUSTOMER_ID_FK" FOREIGN KEY ("CUSTOMER_ID") REFERENCES "OE"."CUSTOMERS" ("CUSTOMER_ID") ON DELETE SET NULL ENABLE
ORA-39112: Dependent object type REF_CONSTRAINT:"PM"."PRINTMEDIA_FK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
Processing object type TABLE_EXPORT/TABLE/TRIGGER
ORA-39082: Object type TRIGGER:"HR"."SECURE_EMPLOYEES" created with compilation warnings
ORA-39082: Object type TRIGGER:"HR"."SECURE_EMPLOYEES" created with compilation warnings
ORA-39082: Object type TRIGGER:"HR"."UPDATE_JOB_HISTORY" created with compilation warnings
ORA-39082: Object type TRIGGER:"HR"."UPDATE_JOB_HISTORY" created with compilation warnings
Processing object type TABLE_EXPORT/TABLE/INDEX/FUNCTIONAL_AND_BITMAP/INDEX
ORA-39112: Dependent object type INDEX:"OE"."CUST_UPPER_NAME_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/FUNCTIONAL_AND_BITMAP/INDEX_STATISTICS
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_UPPER_NAME_IX" creation failed
Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/DOMAIN_INDEX/INDEX
Processing object type TABLE_EXPORT/TABLE/POST_INSTANCE/PROCACT_INSTANCE
ORA-39112: Dependent object type PROCACT_INSTANCE skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39083: Object type PROCACT_INSTANCE failed to create with error:
ORA-01403: no data found
ORA-01403: no data found
Failing sql is:
BEGIN
SYS.DBMS_AQ_IMP_INTERNAL.IMPORT_SIGNATURE_TABLE('AQ$_ORDERS_QUEUETABLE_G');COMMIT; END;
Processing object type TABLE_EXPORT/TABLE/POST_INSTANCE/PROCDEPOBJ
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."AQ$_ORDERS_QUEUETABLE_V" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE_N" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE_R" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."AQ$_ORDERS_QUEUETABLE_E" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
Job "SYSTEM"."SYS_IMPORT_TABLESPACE_01" completed with 63 error(s) at 18:09:14

Short of trying to then reverse-engineer the objects that are in the dump file (I believe Data Pump export files contain some XML representations of DDL in addition to various binary bits, making it potentially possible to try to scan the dump file for the object definitions), I would tend to assume that the export didn't include those type definitions.
Since it looks like you're trying to set up the sample schemas, is there a reason that you wouldn't just run the sample schema setup scripts on the destination database? Why are you using Data Pump in the first place?
Justin

In DBI , how to find out the Source Query used for the Report

Hi All,
How to find out the Source Query used to display the data in the DBI Reports or Dashboards. We can get it in Apps Front end by Going to Help and Record Histroty. But DBI Runs in Internet Explorer so i dont know how to get the source query ( SELECT Query ) Used.
In IE we have View --> Source . But that does not help since it gives the HTML Coding and not the SELECT Query used.
If anyone has ever worked on it...Please help me in finding it.
Thanks,
Neeraj Shrivastava

Hi neeraj,
You can see the query used to display reports.Follow these steps to get the query.
1)Login to oracle apps
2)Select "Daily Business Intelligence Administrator" responsiblity.
3)Now click on "Enable/Disable Debugging" (Now u enabled debugging)
4)now open the report which you want to see the query of
5)In view source it displays query along with the bind varilables.
Feel free to ping me if you have any doubts
thanks
kittu

RRI target selections same as source query

Similar Messages

Maybe you are looking for