Using several global structures in one query?

Hello Together,
I want to use several global structures in a query and group them for instance in the rows. I have tried it out, and it does not seem to be possible.
Any ideas- can I overgo this problem somehow?
Thanks,
Elisabeth

Hi Elisabeth,
This should help:
http://help.sap.com/saphelp_nw04/helpdata/en/f1/0a5632e09411d2acb90000e829fbfe/content.htm

Similar Messages

Change in global structure in one query

Hi,
1. I have some five queries already developed. Here in all the five queries i am using one global structure. I have a requirement tp change the global structure, Now after i change the global structure in one query1 do i need to transport only that query1 or i have to transport all the five queries for the change to get reflected.
2. There are five workbooks also developed for the corresponding queires. After changing the queries do i need to update the output result in all the workbooks as well?
Here in the global structure the keyfigures are replaced with new keyfigures?
Little confused , need help? Please answer my two questions
Thanks,
rani

>
rani wrote:
> Hi,
>
> 1. I have some five queries already developed. Here in all the five queries i am using one global structure. I have a requirement tp change the global structure, Now after i change the global structure in one query1 do i need to transport only that query1 or i have to transport all the five queries for the change to get reflected.
>
>
> Thanks,
> rani
If you changed the global structure then transport the structure not the query.
Go to transport connection in RSA1 choose Query elements -
>Structures.
Select your structure and transport.
That should do.As long as you use "Restore to initial query" in the dataprovider properties of the workbook it should reflect your changes else you need to change at workbook level too.
Hope this helps.

Can anyone help me figure out how to sync my ipod with my purchased music? I have used several computer and at one point synced my ipod with a computer that only had about half of my music. My other computers are no longer working. Not sure how to get

Can anyone help me figure out how to sync my ipod with my purchased music? I have used several computer and at one point synced my ipod with a computer that only had about half of my music. My other computers are no longer working. Not sure how to get my purchased music back onto my ipod?

Hi kimcinma!
Your previous purchases are saved on iCloud even if you bought them on another computer. If you can't find them on your current computer, you might need to unhide them. Go to iTunes preferences, and click on Store Preferences. Then click the box for "show iTunes in the Cloud purchases". Then click on OK, and everything you've ever bought from iTunes on that Apple ID will show up in your library. You will need to download them from iCloud first before you can synch them to your iPod Classic. To do this, click on the little cloud with the arrow in it next to your song, and it will download to your computer. When you have the music that you want downloaded, plug in your iPod and synch away. Hope this helps!
Sandygirl

BRAIN416 InfoObject 1KYFNM is used in both structures of the query

Hi Expert,
I have some problem with MDXTEST on BW 3.5 which i select multiprovider to generate MDX Staement but it goes to ABAP Debugger "CX_RSR_PROG_ERROR" and message BRAIN 416 information said "InfoObject 1KYFNM is used in both structures of the query".
Anyone please explain me what should i do????
Thank you for your help
=SJ=

Dear RajNi,
In This Multiprovider A, i use only 1 infoset which only 1 ODS B.
I'm so confuse because i create new ODS like ODS B and do step like Multiprovider A.
Please help me if you have ever seen like that.
Many thanks
=SJ=

InfoObject 1KYFNM is used in both structures of the query

I am getting the error message - "InfoObject 1KYFNM is used in both structures of the query", while executing the query. Can you please help me remove this error and proceed with the query execution?
Thanks and Regards,
Sachin Kalani.

Hi Sachin,
As the error suggested, make sure that u have used that KF only once in ur Query definition.
Regards,
Rajkandula

Using several data connections in one SSIS data source?

I am loading data from several SQL Server 2012 databases into a datamart. Currently, I am simply using sql sources and destinations for that. However, some of the queries require JOINs between the source databases. Therefore I currently refer to the databases
within the command text of the sql source, e.g.
SELECT t1.Field, t2.Field
FROM [server1].[db1].[dbo].[table1] t1
JOIN [server1].[db2].[dbo].[table1] t2 ON t1.Table1Id = t2.RemoteTable1Id;
This is flawed, since all the sql commands have to be changed if the database or server names change. It would be far better to refer to connections which can be changed on package level and my question is how to get that done.
One way I can think of to get that done is to use several sql source queries and join the data with SSIS join operations. For that all current data flows need to be reworked and I am unsure about the performance when joining large databases compared to the
performance of a single t-sql query.
The other approach would be some dynamic sql stuff which I want to avoid whenever possible. However, if it was possible to use a parameter to insert server/database into the sql command somehow, then that could be an option.

Whatever you're doing now is a bad practice inside SSIS. You should be using data flow tasks for this if data come from different sources and use connection managers pointing to each of them. You add these connection properties as config items which will
enable you to change them from outside package based on your environment
If performance is your concern you can go for staging approach where you bring deltas(changes) alone on daily basis and then use it in the comparisons with destination tables using MERGE or T-SQL for set based processing. You need to have audit columns in
your tables for this though.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Netweaver 04s - Use of two structures in the query craeted dump

I have used two structures in a query, The same query works fine in current BW 3.5 system but in BI 7.O sandbox (copy of prod), it dumps out.
When I check the query, it does give these message (same as in PROD, where it runs without a problem).
- Different hierarchies are used for characteristic Cons Group
- Number variable ZFV_HTES cannot be replaced.
- Fiscal year variant is to be specified for key figure Cumulative (YTD) Value in Group Currency

Hi Rakesh.
Did you get a satisfactory outcome to this problem? Does the current patch of Netweaver 04S cover it?
Would appreciate your reply, please.
Patrick

Use data in structure in SAP Query

I am creating a SAP query using a logical database but will like to include data from a Structure can anyone help me.

Do not worry about this topic, I have obtained the result by myself, it can be done with global variables. The error was in the initialization of some of the variables involved.
Thank you any way and forgive me for the disturbance.
Sinceresly,
Miguel.

Cardinality explosion with several XMLTable calls in one query - how to constrain ?

Hi,
when I engage several (say, four) XMLTable calls using comma (= cartesian join) in a single query, the plan shows me insane cost of 15 digits. Though execution time is reasonable because XML document is very small, I would like the plan appear with more realistic values to correctly predict query time when XML document becomes larger. How can I make CBO be aware of actual size of XML text?
Should I use XML indexing to constrain search space? What are the 'best practices' in indexing XML text for efficient parsing by XMLTable?
SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE    11.2.0.3.0      Production
TNS for Linux: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production
Thanks for your answers!

Hi,
Thanks, odie_63. I used index to give CBA an idea of cardinality.
So, the original plan is (P=Peta, T=Tera, etc...):
Plan hash value: 954188411
| Id | Operation             | Name        | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT      |             | 4451T| 5099P|    14T (1)|999:59:59 |
|   1 | NESTED LOOPS         |             | 4451T| 5099P|    14T (1)|999:59:59 |
|   2 |   NESTED LOOPS        |             |   544G|   638T| 1816M (1)|999:59:59 |
|   3 |    NESTED LOOPS       |             |    66M|    79G|   222K (1)| 00:44:34 |
|   4 |     NESTED LOOPS      |             | 8168 |     9M|    32   (0)| 00:00:01 |
|   5 |      TABLE ACCESS FULL| XML_DROPBOX |     1 | 1252 |     3   (0)| 00:00:01 |
|   6 |      XPATH EVALUATION |             |       |       |            |          |
|   7 |     XPATH EVALUATION |             |       |       |            |          |
|   8 |    XPATH EVALUATION   |             |       |       |            |          |
|   9 |   XPATH EVALUATION    |             |       |       |            |          |
Note
   - Unoptimized XML construct detected (enable XMLOptimizationCheck for more information)
After creating an index, like:
CREATE INDEX XML_DROPBOX_IDX ON XML_DROPBOX (SYS_NC_ROWINFO$)
INDEXTYPE IS XDB.XMLINDEX PARAMETERS (
'PATH TABLE XML_DROPBOX_PATH_IDX (NOLOGGING ENABLE ROW MOVEMENT)
   PATH ID INDEX XML_DROPBOX_PATH_ID_IDX (NOLOGGING)'
the plan become more voluminous, but shows realistic cost:
Plan hash value: 1726871192
| Id | Operation                          | Name                    | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                   |                         |     1 | 10666 |     9   (0)| 00:00:01 |
|* 1 | FILTER                            |                         |       |       |            |          |
|* 2 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 3 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 4 | FILTER                            |                         |       |       |            |          |
|* 5 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 6 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 7 | FILTER                            |                         |       |       |            |          |
|* 8 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 9 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 10 | FILTER                            |                         |       |       |            |          |
|* 11 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 12 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 13 | FILTER                            |                         |       |       |            |          |
|* 14 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 15 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 16 | FILTER                            |                         |       |       |            |          |
|* 17 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 18 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 19 | FILTER                            |                         |       |       |            |          |
|* 20 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 21 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 22 | FILTER                            |                         |       |       |            |          |
|* 23 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 24 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 25 | FILTER                            |                         |       |       |            |          |
|* 26 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 27 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 28 | FILTER                            |                         |       |       |            |          |
|* 29 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 30 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 31 | FILTER                            |                         |       |       |            |          |
|* 32 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 33 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 34 | FILTER                            |                         |       |       |            |          |
|* 35 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 36 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 37 | FILTER                            |                         |       |       |            |          |
|* 38 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 39 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 40 | FILTER                            |                         |       |       |            |          |
|* 41 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 42 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 43 | FILTER                            |                         |       |       |            |          |
|* 44 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 45 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 46 | FILTER                            |                         |       |       |            |          |
|* 47 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 48 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 49 | FILTER                            |                         |       |       |            |          |
|* 50 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 51 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
| 52 | NESTED LOOPS                      |                         |     1 | 10666 |     9   (0)| 00:00:01 |
| 53 |   NESTED LOOPS                     |                         |     1 | 10654 |     8   (0)| 00:00:01 |
| 54 |    NESTED LOOPS                    |                         |     1 | 9132 |     7   (0)| 00:00:01 |
| 55 |     NESTED LOOPS                   |                         |     1 | 7610 |     6   (0)| 00:00:01 |
| 56 |      NESTED LOOPS                  |                         |     1 | 6088 |     5   (0)| 00:00:01 |
| 57 |       NESTED LOOPS                 |                         |     1 | 4566 |     4   (0)| 00:00:01 |
| 58 |        NESTED LOOPS                |                         |     1 | 3044 |     3   (0)| 00:00:01 |
|* 59 |         TABLE ACCESS BY INDEX ROWID| XML_DROPBOX_PATH_IDX    |     1 | 1522 |     2   (0)| 00:00:01 |
|* 60 |          INDEX RANGE SCAN          | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 61 |         TABLE ACCESS BY INDEX ROWID| XML_DROPBOX_PATH_IDX    |     1 | 1522 |     1   (0)| 00:00:01 |
|* 62 |          INDEX RANGE SCAN          | XML_DROPBOX_PATH_ID_IDX |     1 |       |     0   (0)| 00:00:01 |
|* 63 |        TABLE ACCESS BY INDEX ROWID | XML_DROPBOX_PATH_IDX    |     1 | 1522 |     1   (0)| 00:00:01 |
|* 64 |         INDEX RANGE SCAN           | XML_DROPBOX_PATH_ID_IDX |     1 |       |     0   (0)| 00:00:01 |
|* 65 |       TABLE ACCESS BY INDEX ROWID | XML_DROPBOX_PATH_IDX    |     1 | 1522 |     1   (0)| 00:00:01 |
|* 66 |        INDEX RANGE SCAN            | XML_DROPBOX_PATH_ID_IDX |     1 |       |     0   (0)| 00:00:01 |
|* 67 |      TABLE ACCESS BY INDEX ROWID   | XML_DROPBOX_PATH_IDX    |     1 | 1522 |     1   (0)| 00:00:01 |
|* 68 |       INDEX RANGE SCAN             | XML_DROPBOX_PATH_ID_IDX |     1 |       |     0   (0)| 00:00:01 |
|* 69 |     TABLE ACCESS BY INDEX ROWID    | XML_DROPBOX_PATH_IDX    |     1 | 1522 |     1   (0)| 00:00:01 |
|* 70 |      INDEX RANGE SCAN              | XML_DROPBOX_PATH_ID_IDX |     1 |       |     0   (0)| 00:00:01 |
|* 71 |    TABLE ACCESS BY INDEX ROWID     | XML_DROPBOX_PATH_IDX    |     1 | 1522 |     1   (0)| 00:00:01 |
|* 72 |     INDEX RANGE SCAN               | XML_DROPBOX_PATH_ID_IDX |     1 |       |     0   (0)| 00:00:01 |
| 73 |   TABLE ACCESS BY USER ROWID       | XML_DROPBOX             |     1 |    12 |     1   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   1 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
   2 - filter("SYS_P6"."ORDER_KEY">:B1 AND "SYS_P6"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P6"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P6"."LOCATOR")=1)
   3 - access("SYS_P6"."PATHID"=HEXTORAW('6043') AND "SYS_P6"."RID"=:B1)
   4 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
   5 - filter("SYS_P9"."ORDER_KEY">:B1 AND "SYS_P9"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P9"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P9"."LOCATOR")=1)
   6 - access("SYS_P9"."PATHID"=HEXTORAW('66A6') AND "SYS_P9"."RID"=:B1)
   7 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
   8 - filter("SYS_P12"."ORDER_KEY">:B1 AND "SYS_P12"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P12"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P12"."LOCATOR")=1)
   9 - access("SYS_P12"."PATHID"=HEXTORAW('4203') AND "SYS_P12"."RID"=:B1)
10 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
11 - filter("SYS_P15"."ORDER_KEY">:B1 AND "SYS_P15"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P15"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P15"."LOCATOR")=1)
12 - access("SYS_P15"."PATHID"=HEXTORAW('66BA') AND "SYS_P15"."RID"=:B1)
13 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
14 - filter("SYS_P18"."ORDER_KEY">:B1 AND "SYS_P18"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P18"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P18"."LOCATOR")=1)
15 - access("SYS_P18"."PATHID"=HEXTORAW('550B') AND "SYS_P18"."RID"=:B1)
16 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
17 - filter("SYS_P21"."ORDER_KEY">:B1 AND "SYS_P21"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P21"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P21"."LOCATOR")=1)
18 - access("SYS_P21"."PATHID"=HEXTORAW('652E') AND "SYS_P21"."RID"=:B1)
19 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
20 - filter("SYS_P24"."ORDER_KEY">:B1 AND "SYS_P24"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P24"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P24"."LOCATOR")=1)
21 - access("SYS_P24"."PATHID"=HEXTORAW('44EC') AND "SYS_P24"."RID"=:B1)
22 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
23 - filter("SYS_P31"."ORDER_KEY">:B1 AND "SYS_P31"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P31"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P31"."LOCATOR")=1)
24 - access("SYS_P31"."PATHID"=HEXTORAW('2C38') AND "SYS_P31"."RID"=:B1)
25 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
26 - filter("SYS_P34"."ORDER_KEY">:B1 AND "SYS_P34"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P34"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P34"."LOCATOR")=1)
27 - access("SYS_P34"."PATHID"=HEXTORAW('3026') AND "SYS_P34"."RID"=:B1)
28 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
29 - filter("SYS_P37"."ORDER_KEY">:B1 AND "SYS_P37"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P37"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+2 AND
              SYS_XMLI_LOC_ISNODE("SYS_P37"."LOCATOR")=1)
30 - access("SYS_P37"."PATHID"=HEXTORAW('4F1A') AND "SYS_P37"."RID"=:B1)
31 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
32 - filter("SYS_P40"."ORDER_KEY">:B1 AND "SYS_P40"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P40"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+2 AND
              SYS_XMLI_LOC_ISNODE("SYS_P40"."LOCATOR")=1)
33 - access("SYS_P40"."PATHID"=HEXTORAW('7E65') AND "SYS_P40"."RID"=:B1)
34 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
35 - filter("SYS_P43"."ORDER_KEY">:B1 AND "SYS_P43"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P43"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P43"."LOCATOR")=1)
36 - access("SYS_P43"."PATHID"=HEXTORAW('7497') AND "SYS_P43"."RID"=:B1)
37 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
38 - filter("SYS_P46"."ORDER_KEY">:B1 AND "SYS_P46"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P46"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P46"."LOCATOR")=1)
39 - access("SYS_P46"."PATHID"=HEXTORAW('2D8D') AND "SYS_P46"."RID"=:B1)
40 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
41 - filter("SYS_P49"."ORDER_KEY">:B1 AND "SYS_P49"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P49"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P49"."LOCATOR")=1)
42 - access("SYS_P49"."PATHID"=HEXTORAW('4486') AND "SYS_P49"."RID"=:B1)
43 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
44 - filter("SYS_P66"."ORDER_KEY">:B1 AND "SYS_P66"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P66"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P66"."LOCATOR")=1)
45 - access("SYS_P66"."PATHID"=HEXTORAW('5005') AND "SYS_P66"."RID"=:B1)
46 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
47 - filter("SYS_P69"."ORDER_KEY">:B1 AND "SYS_P69"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P69"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P69"."LOCATOR")=1)
48 - access("SYS_P69"."PATHID"=HEXTORAW('3935') AND "SYS_P69"."RID"=:B1)
49 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
50 - filter("SYS_P59"."ORDER_KEY">:B1 AND "SYS_P59"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P59"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P59"."LOCATOR")=1)
51 - access("SYS_P59"."PATHID"=HEXTORAW('37CE') AND "SYS_P59"."RID"=:B1)
59 - filter(SYS_XMLI_LOC_ISNODE("SYS_P49"."LOCATOR")=1)
60 - access("SYS_P49"."PATHID"=HEXTORAW('4486') )
61 - filter(SYS_XMLI_LOC_ISNODE("SYS_P62"."LOCATOR")=1 AND
              "SYS_P49"."ORDER_KEY"<"SYS_P62"."ORDER_KEY" AND "SYS_P62"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD("SYS_P49".
              "ORDER_KEY") AND SYS_ORDERKEY_DEPTH("SYS_P49"."ORDER_KEY")+1=SYS_ORDERKEY_DEPTH("SYS_P62"."ORDER_KEY")
62 - access("SYS_P62"."PATHID"=HEXTORAW('780B') AND "SYS_P62"."RID"="SYS_P49"."RID")
63 - filter(SYS_XMLI_LOC_ISNODE("SYS_P27"."LOCATOR")=1 AND
              "SYS_P27"."ORDER_KEY"<"SYS_P49"."ORDER_KEY" AND "SYS_P49"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD("SYS_P27".
              "ORDER_KEY") AND SYS_ORDERKEY_DEPTH("SYS_P27"."ORDER_KEY")+1=SYS_ORDERKEY_DEPTH("SYS_P49"."ORDER_KEY")
64 - access("SYS_P27"."PATHID"=HEXTORAW('49C4') AND "SYS_P49"."RID"="SYS_P27"."RID")
65 - filter(SYS_XMLI_LOC_ISNODE("SYS_P46"."LOCATOR")=1 AND
              "SYS_P27"."ORDER_KEY"<"SYS_P46"."ORDER_KEY" AND "SYS_P46"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD("SYS_P27".
              "ORDER_KEY") AND SYS_ORDERKEY_DEPTH("SYS_P27"."ORDER_KEY")+1=SYS_ORDERKEY_DEPTH("SYS_P46"."ORDER_KEY")
66 - access("SYS_P46"."PATHID"=HEXTORAW('2D8D') AND "SYS_P46"."RID"="SYS_P27"."RID")
67 - filter(SYS_XMLI_LOC_ISNODE("SYS_P52"."LOCATOR")=1 AND
              "SYS_P46"."ORDER_KEY"<"SYS_P52"."ORDER_KEY" AND "SYS_P52"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD("SYS_P46".
              "ORDER_KEY") AND SYS_ORDERKEY_DEPTH("SYS_P46"."ORDER_KEY")+1=SYS_ORDERKEY_DEPTH("SYS_P52"."ORDER_KEY")
68 - access("SYS_P52"."PATHID"=HEXTORAW('6AFA') AND "SYS_P52"."RID"="SYS_P46"."RID")
69 - filter(SYS_XMLI_LOC_ISNODE("SYS_P24"."LOCATOR")=1 AND
              "SYS_P24"."ORDER_KEY"<"SYS_P27"."ORDER_KEY" AND "SYS_P27"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD("SYS_P24".
              "ORDER_KEY") AND SYS_ORDERKEY_DEPTH("SYS_P24"."ORDER_KEY")+1=SYS_ORDERKEY_DEPTH("SYS_P27"."ORDER_KEY")
70 - access("SYS_P24"."PATHID"=HEXTORAW('44EC') AND "SYS_P27"."RID"="SYS_P24"."RID")
71 - filter(SYS_XMLI_LOC_ISNODE("SYS_P4"."LOCATOR")=1 AND
              "SYS_P4"."ORDER_KEY"<"SYS_P24"."ORDER_KEY" AND "SYS_P24"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD("SYS_P4"."O
              RDER_KEY") AND SYS_ORDERKEY_DEPTH("SYS_P4"."ORDER_KEY")+1=SYS_ORDERKEY_DEPTH("SYS_P24"."ORDER_KEY"))
72 - access("SYS_P4"."PATHID"=HEXTORAW('5B3D') AND "SYS_P24"."RID"="SYS_P4"."RID")
Note
   - dynamic sampling used for this statement (level=2)

BW 7.0 - display of the global structures in the query designer

Hi colleagues,
When I open the gobal structures of an infoprovider in the query designer, the system shows me all levels of the structures; that is not clearly arranged.
It would be better, the system would show allways only the next level.
Is there any idea ?
regards
Dieter Gerl

Hi,
I can think of three possibilities for a solution.
1. Store the name of the required table in a config table and select at runtime
2. use an 'IF' or 'CASE' statement to deterimine which system you are currently in and then place the required varible within this statement.
3. Preferred solution: use a Field Symbol to assign the table at run-time, this way no errors will occur and your program will compile.
There are many examples of FIELD SYMBOLS on SDN and even the F1 help in SAP.
regards,
CH

How to use IF ELSE statement in one QUERY to MS ACCESS

System.out.println("Enter Final Exam: ");
int f = Integer.parseInt(input.readLine());
command.executeUpdate("UPDATE Students SET Final_Exam='"+f+"',Raw_score=(QT+MT+Final_Exam)/3 WHERE stud_name='"+stdID+"'");
command.executeUpdate("UPDATE Students SET Raw_score=(QT+MT+Final_Exam)/3 WHERE stud_ID='"+stdID+"'");
if (rsf==100)
command.executeUpdate("UPDATE Students SET Final_Grade=1.0 WHERE stud_ID='"+stdID+"'");
else if(rsf < 100 && rsf > 90)
command.executeUpdate("UPDATE Students SET Final_Grade=2.0 WHERE stud_ID='"+stdID+"'");
else
command.executeUpdate("UPDATE Students SET Final_Grade=5.0 WHERE stud_ID='"+stdID+"'");How can I shorten my code using a IF ELSE statement inside a single query or two? Or is it possible?
Edited by: ivatanako on Sep 28, 2007 11:55 PM

Sun has tutorial trail for JDBC, you might want to browse through that; you'll get more details and samples there than here. Here's the link to the section on PreparedStatement: http://java.sun.com/docs/books/tutorial/jdbc/basics/prepared.html
People on the forum help others voluntarily, it's not their job.
Help them help you.
Learn how to ask questions first: http://faq.javaranch.com/java/HowToAskQuestionsOnJavaRanch
(Yes I know it's on JavaRanch but I think it applies everywhere)
----------------------------------------------------------------

Attempting to use several url parameters in one url

Problem: I can either pass along the picture ID parameter or the album ID parameter to the next page, but never both
I have a URL parameter for the picture ID, and I have another for the album ID, which determines also the directory where the pictures are stored on the server.
Only the album ID parameter:
photoalbum.php?mod=album&id_alb=<?php echo $row_rsImages['id_alb']; ?>
which generates this URL: photoalbum.php?mod=album&id_alb=6
Result: loads picture A just fine
Only the picture ID parameter:
photoalbum.php?mod=detail&id_img=<?php echo $row_rsImages['id_img']; ?>
which generates this URL: photoalbum.php?mod=detail&id_img=8
Result: loads picture B just fine
Now I want to pass both parameters:
photoalbum.php?mod=detail&id_img=<?php echo $row_rsImages['id_img']; ?>mod=album&id_alb=<?php echo $row_rsImages['id_alb']; ?>
which generates this URL: photoalbum.php?mod=detail&id_img=8mod=album&id_alb=
Shows only one picture
But when I type a number at the end of the url so that it reads;
photoalbum.php?mod=detail&id_img=8mod=album&id_alb=6
It shows both pictures
MySQL Query:
rsImages
SELECT id_img, Vlg_img, idalb_img, filename_img, filenameA_img, filenameB_img, description_img, date_img
FROM image_img
WHERE idalb_img = colname
Name: colname
Type: Text
Standard Value: -1
Runtime Value: $_GET['id_alb']
MySQL Query:
rsAlbBgr
SELECT id_alb, title_alb, description_alb, backgr_img
FROM album_alb
WHERE album_alb.id_alb= bgrname
Name: bgrname
Type: Text
Standard Value: -1
Runtime Value: $_GET['id_alb']
It's puzzling me for days now, can someone please help me?
MySQL - 5.0.27
MySQL client version: 4.1.20
PHP Version 5.2.3

> which generates this URL: photoalbum.php?mod=detail&id_img=8mod=album&id_alb=
You need an ampersand between each set of information in the url - in this case between img=8 and mod=album. the line above needs to be
photoalbum.php?mod=detail&id_img=8&mod=album&id_alb=

Would the CCA be able to use several CPUs for executing one mapping?

I've data sources in Adabas, and now I want to run a stress test. When I gathered statistics of the processes in all of components:
- In Host (Adabas + Attunity),
- In HP (OWB - oracle 11gR2 + Java process (CCA))
The process in Host and in the database Oracle is very light, but the process Java not, I think that it's the bottleneck
The process Java used only one CPU, although the server had seven CPUs, Is possible use more CPU's?
Cheers
Marisol

Hi Marisol
Which code templates are you using?
Some code templates do very little apart from use the database (which can run parallel DML etc) ... others that are more process intensive such as SQL to SQL (which is more like a generic java loop, not great for large data movement).
How are you using Attunity in this scenario? Are you using the Attunity Adabas ODBC driver? If so, did you try and use the database Gateways?
Regarding performance if additional mappings were invoked at the same time these can leverage other processors in parallel via the CCA.
Cheers
David

Can we use global structure while designing a query on a multiprovider

hai friends,
If i build a multiprovider on cubes for which the query design on those cubes contains global sturctures ,
Can i use those global structures while designing a query on a multiprovider (which contains those cubes)

Hi Vamsi,
The structure from the base cubes will not automatically be available for the queries created on the multiprovider. The only way to get the structure there is to copy a query from the base cube to the multiprovider. You can use transaction RSZC to do this.
Hope this helps...

LOCAL Structure to be copied from one query to another query

Hello all,
In our query we have created a structure locally....
we have to copy the same locally created structure from one query to another query which is on the same multiprovider.
We do not want to make the structure global.
Can anyone suggest some method to achieve this!

For copiying structures fom query to another you have to do it global. After that you can do click on right button on the structure when added to your query and choose "eliminate reference" this does further changes in the structure were local for that query.

Using several global structures in one query?

Similar Messages

Maybe you are looking for