Two infosources for the same datasource.

Hello,
I have a doubt and i need some help with it.
I have a datasource and two infosources conected with that datasource.
I also have two ODS and each one is filled with one infosource and ODS are equal.
I fill ODS A with field type= A and ODS B with field type=B.
Datasource has delta behaviour.
I created two infopackages, with init delta, and i put diferent values for field type in selection fields in both infopackages.
First, it's this possible? I'm having a error, first extraction runs well but when i execute the second infopackage, i 've an error, saying that the the first request must be set first.
Any help?
Thanks
Maria

hi maria ,
U can fill two ODS from the same datasource by using two Infopackages ,
in the scheduler screen u can do the necessary settings and trigger the infopackage.
Regards ... Kumar Sarvepalli .... ///// Honor with points if helpful

Similar Messages

Use two indicators for the same variable in two different VIs

hello, I want to use two indicators for the same variable in two different VIs running at the same time
should I use global variables?? I want to avoid because I have lot of variables and it would takes too much memory,I tried with this code but the value of the second indicator is not updated
I tried to use the queue and it works but the problem is as i said previously that i have many variables shoud I use a queue for each one??
what should I do?
thank you in advance
cordialy
Attachments:
projet.zip ‏13 KB

CrisSTine01 wrote:
hello, I want to use two indicators for the same variable in two different VIs running at the same time
I'm a huge fan of User Events to send updates to GUIs from who knows where.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Can we create two POs for the same 3rd party Sales Order?

Hi MM experts,
Issue: Can we create two POs for the same 3rd party Sales Order
In Third party purchase process, first sales order created with a spl. item category and it creates the PR automatically with the Sales order material and Qty and this PR converted PO.
They got a pur.req. for sale order on same item for same delevery date. They did not get any warning msg. saying that a PO was prviously placed against this sale order.
How it is possible that we were able to place another PO? concern is that second PO was palced against SO which was already used & completed. they were able to place 2 POs for the same customer same delevery date. How it is possible?
If anyone face the same issue, please let me know if you have any answer to this questions.
Thanks in advance.
Suresh.

Suresh,
It is hard for me to give you a definitive answer since you have created a customized solution.
How it is possible that we were able to place another PO? concern is that second PO was palced against SO which was already used & completed. they were able to place 2 POs for the same customer same delevery date. How it is possible?
Normally, the system will not do this. A third party PR or PO will be 'account assigned' to the Sales order. SAP standard 3rd party will not create additional purchase reqs unless there has been manual intervention. Try searching for changes in the Sales order and changes in the original purchase order. They may give you a clue.
I believe the normal Item category for third party SO is TAS (I am working from memory here, I am not in front of a system). I don't know what ZTAG does. I confess I am not an SD expert. You might also want to post your question in an SD forum.
You mention two custom applications, ZMMPLAN and ZSTPMP. These somehow have functionality that is used to help you convert your PRs to POs. If I were in your position, I believe I would also look at these applications for clues to how they might be contributing to your problem. And please don't send me details about these apps. I will not comment on custom code in this forum.
Sorry I can't be of more help.
Rgds,
DB49

Post a witholding tax in two countries for the same vendor

Hi all,
I would like to know if there is any way (standar not development) to post a witholding tax in two countries for the same vendor belonging to a company code. (extended witholding tax scene).
System always display extended witholding indicators belonging to the country of the company code.
Thanks in advance.
Emilio Rozalén
SAP FI Consultant.

Hi B.Rama,
I think so, but Do you know the meaning of country witholding field in vendor master?.
Besides you can find this field in customizing, reports but I dont know its functionality.
Thanks and regards
Emilio Rozalé

I was charged two times for the same game

I was charged two times for the same game...how can I get my money back? I even was emailed a receipt for them both...no one noticed? Please help me.

How to report an issue with Your iTunes Store purchase

Why are there two prices for the same audiobook?

Why are there two prices for the same audiobook in iTunes?

May be one is abridged and one unabridged ? or they just may want to get the suckers that think the more expensive one is better ... haha.

Urgent: two authors for the same book

I have a database with three tables: books, authors and aux.
The books table stores the names of the books. The authors table stores the name of the authors. Table aux takes the id of the other two. I did this for the case of the same book has two or more authors
The query I did was the following:
SELECT authores.author, books.title
FROM aux, authors, books
WHERE aux.books_id = books.id AND aux.authors_id = authors.id
ORDER BY books.title ASC
How do I show the two authors for the same book?
For now, I'm using a simple table:
<table border="1" cellpadding="1" cellspacing="1">
<tr>
    <td>author</td>
    <td>title</td>
</tr>
<?php do { ?>
    <tr>
      <td><?php echo $row_rsBooks['author']; ?></td>
      <td><?php echo $row_rsBooks['title']; ?></td>
    </tr>
    <?php } while ($row_rsBooks = mysql_fetch_assoc($rsBooks)); ?>
</table>
Thus, the table presents two results for the same book, instead of uniting the two authors of the same book.

Thanks for the reply.
In the meantime, got what I wanted. The expression looks like this:
SELECT livros.titulo, GROUP_CONCAT(autores.autor SEPARATOR ',') AS Autores
FROM livros INNER JOIN aux ON aux.livros_id = livros.id INNER JOIN autores ON aux.autores_id = autores.id
GROUP BY livros.titulo

Two infopackages for the same DS-- IS combination initialised

Hello Friends,
Can we have two infopackages for the same DS-->IS combination initialised with the same selections conditions and init requests. I have seen this in my client system. How can this be achieved.
Thanks for your help.
---Simmi

That is not possible.
Are you sure Inits were done for same selections ???

Release By two Users for the same Value

Friends
I have an existing PO rel. strategy where the range is 1-10000USD . This is currently released by one user. Now due to business requirement client wants to introduce one additional user to release the PO as well for the same value range.
In a nutshell for the value range USD 1-10000 , There will be two approvers with two different rel. codes. How do I achieve this?
Thanks
samuel

Dear,
Check this : Release Procudure for Purchase Order
Hope Helpful to your requirement.
Regards,
Syed Hussain.

Two tabs for the same page

Hello,
I have been spending the whole morning trying to find a solution for this problem but did not find any either by myself or parsing the forum messages.
I am building an application with a two level tab for the navigation.
Everything is fine as long as the pages referenced by the tabs have a different number.
My problem is that i use the same dynamic page (let say 40) to be accessed through two different tabs.
e.g Parent tab is labelled "Parent"
Two other tabs are created linked to parent tab "Parent" and those are labelled "Action1" and Action2"
Selecting "Action1" will result in rendering the page 40 with a parameter (let say page_type) set to the value 1.
Selecting "Action2" will result in rendering the *same* page 40 with a parameter (let say page_type) set to the value 2.
For the parent tab "Parent" let say that the default is to select "Action1"
Is there any solution to implement that kind of behaviour?
I have tried to create redirecting pages (empty page and a single branch) to achieve this but i always get stucked when trying to have page 40 displaying the proper tabs and parent tab.
Thanks in advance for any help.
Daniel

Hi Andy,
Thanks for your answer!
Whilst it is fairly straightforward to create multiple tabs for the same page (this can be done through Shared Components, Tabs and click Add on the standard >>tabs bar, enter in any page number you like), the functionality of tabs does not provide the means to set item values. Additionally, as both tabs would be >>"current" for your page 40, once you've clicked on one, you can not click on the other.Yes this is exactly what i discover once my page 40 has been built.
There may be ways to do what you need, but as tabs are really there for navigation purposes only, this may become rather complicated. What is the difference >>between Action1 and Action2? Can this be achieved in another way? Have you considered switching to lists for navigation (where you can set item values)?In fact, i can still duplicate this page and have a few changes within each new page. But as a matter of code design as both pages have around half in common, i wanted to share most of the items (build a single page) and then play for a few additional items with conditions encompassing the page type i have set before rendering the page.=> Most items in common, a few others whose display is conditionnal. For the end user, it looks like two different pages because in their business process the "Action1" and "Action2" are clearly different.
I use lists in this application on the home page to reach most of the application pages but while some users prefer to use the links on the home page and go back to home page, other would like to use the tabs and a number of them use both navigation mechanisms.
Sorry if it is not quite clear (english is not my mother tongue).
Regards,
Daniel

Two Tracks for the same Runtime System?

Hello,
can you please tell me if it is allowed to connect two tracks to the same runtime systems?
We have already a track connected to our systems. Now we have created a new track to deliver different content to those systems. We wanted to connect the new track to the same runtime systems. Our basis team told me that a where-used message came up that told them "The following runtime systems are already used elsewhere in the CMS domain".
Can you tell us if we will get problems because of this?
Thanks in advance,
Br,
Michael

Hello again,
ok now, thats something completely different CRM modification is always special.
To be honest i cannot tell for sure what will happen. As far as i know the default deploy strategy of NWDI is "deploy any version" which means NWDI will order SDM to just deploy not regarding any SDM Version (you are on a 7.0x System right?)
So it should be possible if everything else, excelt those 2 DCs is the same things should work. But if not the last deplyoed version of the shared DCS will be active. Which might lead to problems then.
As far as you described, the setup is as the CRM modification guides mentioned.
My first thought is that you are not forced to use CUSTCRMPRJ as SC name for the projects as far as I know. OS maybe the leanest thing would be to just use CUSTCRMPRJ_light (.o)) for the second track.
Hmmm not sure if this is a good idea or thought to the end. I don't have the CRM modifications guide at hand at the moment. But I guess there was a part where something was mentioned similar to this.
After all I have to say:Sorry. I can't give you solid, reliable tip/advice for this case. Maybe my thought will help you.
Or maybe someone else knows better.
Have a good time
Jan

Two deliveries for the same batch item

hi
i have 3 ea with a batch number in my stock. i have created a delivery for 2ea but TO is not yet confirmed. While creating another delivery for 2ea for the same part, it is again picking the same batch in TO. i should have only 1ea, then how it is picking 2ea in TO. is this because I've not confirmed my earlier TO. If I confirm the 2nd TO first, what will happen to the first TO.
Thanks,
Satish

Hi
If 3 is all you have then you should not be able to create a to for two if you already have an open to for two. I suggest you double check all of the data like the batch number that the second to is picking
Do you have this material anywhere else and also you should check wether the material and/or the storage type is allowed to go negative? If this is the case then you can pick as many as you like.
If ypu allow negative stock then you will have this problem.
Negative stock should only be allowed in Interin st types 9xx
I hope that this helps
Frenchy

Two outputs for the same partner functions............

Hello,
I have come across the situation where i need to use two transmission medium for the same partner function, is it possible through the standard settings?
E.x. My client wants to send email and print to the sold to party while confirming order, what are the required settings need to be made?
Thank you.

Similar question was answered in the past, check the link Output transmission medium to print and email and the answer provided by Yadav suits your requirement.
Regards,

Two orders for the same Accordion

Hey!!
I'd like to set two different orders for the same Accordion
varibale heights and duration of time should be change
if I use just one of them like this
var Accordion1 = new Spry.Widget.Accordion("Accordion1", {
useFixedPanelHeights: false })
It works
or
var Accordion1 = new Spry.Widget.Accordion("Accordion1", {
duration: 100, fps: 90 });
it works, too!
But when I want to combine them
var Accordion1 = new Spry.Widget.Accordion("Accordion1", {
useFixedPanelHeights: false })
var Accordion1 = new Spry.Widget.Accordion("Accordion1", {
duration: 100, fps: 90 });
It doesnt work
or like this
var Accordion1 = new Spry.Widget.Accordion("Accordion1", {
useFixedPanelHeights: false, duration: 100, fps: 90 })

That is not possible.
Are you sure Inits were done for same selections ???

Why is the Star Transformation using two indexes for the same dimension?

Hi,
Recently, I have made an investigation about the Star Transformation feature. I have found a strange test case, which plays an important role in my strategy for our overall DWH architecture. Here it is:
The Strategy:
I would like to have the classical Star Transformation approach (single column Bitmap Indexes for each dimension foreign key column in the fact table), together with additional Bitmap Join Indexes for some of the dimension attributes, which would benefit from the materialization of the join (bitmap merge operation will be skipped/optimized).
The query:
select dp.brand, ds. region_name, dc.region_name
     , count(*), sum(f.extended_price)
from fact_line_item f
     , dim_part       dp
     , dim_supplier   ds
     , dim_customer   dc
where dp.mfgr        = 10                 -- dimension selectivity = 1/10 --> acttual/fact selectivity = 6/10
   and f.part_dk      = dp.dk
   and ds.region_name = 'REGION #1' -- dimension selectivity = 1/9
   and f.supplier_dk = ds.dk
   and dc.region_name = 'REGION #1' -- dimension selectivity = 1/11
   and f.customer_dk = dc.dk
group by dp.brand, ds. region_name, dc.region_name
The actual plan:
| Id | Operation                              | Name                        | Starts | E-Rows | Cost (%CPU)| A-Rows |   A-Time   | Buffers | Reads |
|   0 | SELECT STATEMENT                       |                             |      1 |        | 3247 (100)|      1 |00:01:42.05 |     264K|    220K|
|   1 | HASH GROUP BY                         |                             |      1 |      2 | 3247   (1)|      1 |00:01:42.05 |     264K|    220K|
|* 2 |   HASH JOIN                            |                             |      1 | 33242 | 3037   (1)|    217K|00:01:29.67 |     264K|    220K|
|* 3 |    TABLE ACCESS FULL                   | DIM_SUPPLIER                |      1 |   1112 |   102   (0)|   1112 |00:00:00.01 |     316 |      4 |
|* 4 |    HASH JOIN                           |                             |      1 | 33245 | 2934   (1)|    217K|00:01:29.10 |     264K|    220K|
|* 5 |     TABLE ACCESS FULL                  | DIM_CUSTOMER                |      1 |    910 |   102   (0)|    910 |00:00:00.08 |     316 |      8 |
|* 6 |     HASH JOIN                          |                             |      1 | 33248 | 2831   (1)|    217K|00:01:28.57 |     264K|    220K|
|* 7 |      TABLE ACCESS FULL                 | DIM_PART                    |      1 |     10 |     3   (0)|     10 |00:00:00.01 |       6 |      0 |
|   8 |      PARTITION RANGE ALL               |                             |      1 | 36211 | 2827   (1)|    217K|00:01:28.01 |     264K|    220K|
|   9 |       TABLE ACCESS BY LOCAL INDEX ROWID| FACT_LINE_ITEM              |      6 | 36211 | 2827   (1)|    217K|00:01:33.85 |     264K|    220K|
| 10 |        BITMAP CONVERSION TO ROWIDS     |                             |      6 |        |            |    217K|00:00:07.09 |   46980 |   3292 |
| 11 |         BITMAP AND                     |                             |      6 |        |            |     69 |00:00:08.33 |   46980 |   3292 |
| 12 |          BITMAP MERGE                  |                             |      6 |        |            |    193 |00:00:02.09 |    2408 |   1795 |
| 13 |           BITMAP KEY ITERATION         |                             |      6 |        |            |   4330 |00:00:04.66 |    2408 |   1795 |
| 14 |            BUFFER SORT                 |                             |      6 |        |            |     60 |00:00:00.01 |       6 |      0 |
|* 15 |             TABLE ACCESS FULL          | DIM_PART                    |      1 |     10 |     3   (0)|     10 |00:00:00.01 |       6 |      0 |
|* 16 |            BITMAP INDEX RANGE SCAN     | FACT_LI__P_PART_DIM_KEY_BIX |     60 |        |            |   4330 |00:00:02.11 |    2402 |   1795 |
|* 17 |          BITMAP INDEX SINGLE VALUE     | FACT_LI__P_PART_MFGR_BJX    |      6 |        |            |   1747 |00:00:06.65 |     890 |    888 |
| 18 |          BITMAP MERGE                  |                             |      6 |        |            |    169 |00:00:02.78 |   16695 |    237 |
| 19 |           BITMAP KEY ITERATION         |                             |      6 |        |            |   5460 |00:00:01.56 |   16695 |    237 |
| 20 |            BUFFER SORT                 |                             |      6 |        |            |   5460 |00:00:00.02 |     316 |      0 |
|* 21 |             TABLE ACCESS FULL          | DIM_CUSTOMER                |      1 |    910 |   102   (0)|    910 |00:00:00.01 |     316 |      0 |
|* 22 |            BITMAP INDEX RANGE SCAN     | FACT_LI__P_CUST_DIM_KEY_BIX |   5460 |        |            |   5460 |00:00:02.07 |   16379 |    237 |
| 23 |          BITMAP MERGE                  |                             |      6 |        |            |    170 |00:00:03.65 |   26987 |    372 |
| 24 |           BITMAP KEY ITERATION         |                             |      6 |        |            |   6672 |00:00:02.23 |   26987 |    372 |
| 25 |            BUFFER SORT                 |                             |      6 |        |            |   6672 |00:00:00.01 |     316 |      0 |
|* 26 |             TABLE ACCESS FULL          | DIM_SUPPLIER                |      1 |   1112 |   102   (0)|   1112 |00:00:00.01 |     316 |      0 |
|* 27 |            BITMAP INDEX RANGE SCAN     | FACT_LI__S_SUPP_DIM_KEY_BIX |   6672 |        |            |   6672 |00:00:02.74 |   26671 |    372 |
The Question:
Why is the Star Transformation using both indexes FACT_LI__P_PART_DIM_KEY_BIX and FACT_LI__P_PART_MFGR_BJX for the same dimension criteria (dp.mfgr = 10)?? The introduction of the additional Bitmap Join Index actually make Oracle to do the work twice !!!
Anybody, any idea ?!?

Dom, here it is the plan with the predicates:
| Id | Operation                              | Name                        | Starts | E-Rows | Cost (%CPU)| A-Rows |   A-Time   | Buffers | Reads |
|   0 | SELECT STATEMENT                       |                             |      1 |        | 3638 (100)|      1 |00:06:41.17 |     445K|    236K|
|   1 | HASH GROUP BY                         |                             |      1 |      2 | 3638   (1)|      1 |00:06:41.17 |     445K|    236K|
|* 2 |   HASH JOIN                            |                             |      1 | 33242 | 3429   (1)|    217K|00:08:18.02 |     445K|    236K|
|* 3 |    TABLE ACCESS FULL                   | DIM_SUPPLIER                |      1 |   1112 |   102   (0)|   1112 |00:00:00.03 |     319 |    313 |
|* 4 |    HASH JOIN                           |                             |      1 | 33245 | 3326   (1)|    217K|00:08:17.47 |     445K|    236K|
|* 5 |     TABLE ACCESS FULL                  | DIM_CUSTOMER                |      1 |    910 |   102   (0)|    910 |00:00:00.01 |     319 |    313 |
|* 6 |     HASH JOIN                          |                             |      1 | 33248 | 3223   (1)|    217K|00:08:16.63 |     445K|    236K|
|* 7 |      TABLE ACCESS FULL                 | DIM_PART                    |      1 |     10 |     3   (0)|     10 |00:00:00.01 |       6 |      0 |
|   8 |      PARTITION RANGE ALL               |                             |      1 | 36211 | 3219   (1)|    217K|00:08:16.30 |     445K|    236K|
|   9 |       TABLE ACCESS BY LOCAL INDEX ROWID| FACT_LINE_ITEM              |      6 | 36211 | 3219   (1)|    217K|00:08:40.89 |     445K|    236K|
| 10 |        BITMAP CONVERSION TO ROWIDS     |                             |      6 |        |            |    217K|00:00:32.00 |   46919 | 19331 |
| 11 |         BITMAP AND                     |                             |      6 |        |            |     69 |00:00:34.50 |   46919 | 19331 |
| 12 |          BITMAP MERGE                  |                             |      6 |        |            |    193 |00:00:00.58 |    2353 |      1 |
| 13 |           BITMAP KEY ITERATION         |                             |      6 |        |            |   4330 |00:00:00.10 |    2353 |      1 |
| 14 |            BUFFER SORT                 |                             |      6 |        |            |     60 |00:00:00.01 |       6 |      0 |
|* 15 |             TABLE ACCESS FULL          | DIM_PART                    |      1 |     10 |     3   (0)|     10 |00:00:00.01 |       6 |      0 |
|* 16 |            BITMAP INDEX RANGE SCAN     | FACT_LI__P_PART_DIM_KEY_BIX |     60 |        |            |   4330 |00:00:00.07 |    2347 |      1 |
|* 17 |          BITMAP INDEX SINGLE VALUE     | FACT_LI__P_PART_MFGR_BJX    |      6 |        |            |   1747 |00:01:23.64 |     882 |    565 |
| 18 |          BITMAP MERGE                  |                             |      6 |        |            |    169 |00:00:09.14 |   16697 |   7628 |
| 19 |           BITMAP KEY ITERATION         |                             |      6 |        |            |   5460 |00:00:02.19 |   16697 |   7628 |
| 20 |            BUFFER SORT                 |                             |      6 |        |            |   5460 |00:00:00.01 |     316 |      0 |
|* 21 |             TABLE ACCESS FULL          | DIM_CUSTOMER                |      1 |    910 |   102   (0)|    910 |00:00:00.01 |     316 |      0 |
|* 22 |            BITMAP INDEX RANGE SCAN     | FACT_LI__P_CUST_DIM_KEY_BIX |   5460 |        |            |   5460 |00:00:08.78 |   16381 |   7628 |
| 23 |          BITMAP MERGE                  |                             |      6 |        |            |    170 |00:00:21.46 |   26987 | 11137 |
| 24 |           BITMAP KEY ITERATION         |                             |      6 |        |            |   6672 |00:00:10.29 |   26987 | 11137 |
| 25 |            BUFFER SORT                 |                             |      6 |        |            |   6672 |00:00:00.01 |     316 |      0 |
|* 26 |             TABLE ACCESS FULL          | DIM_SUPPLIER                |      1 |   1112 |   102   (0)|   1112 |00:00:00.01 |     316 |      0 |
|* 27 |            BITMAP INDEX RANGE SCAN     | FACT_LI__S_SUPP_DIM_KEY_BIX |   6672 |        |            |   6672 |00:00:20.94 |   26671 | 11137 |
Predicate Information (identified by operation id):
   2 - access("F"."SUPPLIER_DK"="DS"."DK")
   3 - filter("DS"."REGION_NAME"='REGION #1')
   4 - access("F"."CUSTOMER_DK"="DC"."DK")
   5 - filter("DC"."REGION_NAME"='REGION #1')
   6 - access("F"."PART_DK"="DP"."DK")
   7 - filter("DP"."MFGR"=10)
15 - filter("DP"."MFGR"=10)
16 - access("F"."PART_DK"="DP"."DK")
17 - access("F"."SYS_NC00017$"=10)
21 - filter("DC"."REGION_NAME"='REGION #1')
22 - access("F"."CUSTOMER_DK"="DC"."DK")
26 - filter("DS"."REGION_NAME"='REGION #1')
27 - access("F"."SUPPLIER_DK"="DS"."DK")
Note
   - star transformation used for this statement

Two infosources for the same datasource.

Similar Messages

Maybe you are looking for