Count deliveries for the same sale sorder

Hello
I would like to use the query to count how many deliveries have been made for the sales order
I have the following but it gives me an error message because I do not know how to use the function count
COUNT T0.BaseEntry FROM ORDR T0, DLN1 T1 WHERE (T0.DocEntry = T1.DocEntry) AND T1.BaseRef = $[$38.44.11.Number]

thanks for your prompt reply
I found the answer and you confirm this
SELECT COUNT (T1.BaseEntry) FROM ORDR T0, DLN1 T1 WHERE (T0.DocEntry = T1.DocEntry) AND T1.BaseRef = $[$38.44.11.Number]
If you remember I need to number the back order when I have the result in that query will be used in the delivery note process table ORDR.
Then when the result is 1 it will be numbered as A
When the result is 2 it will be B and so on

Similar Messages

  • 2 deliveries created for the same sales order

    2 Return Del docs & 2 credit notes were created for one return order no.  
    Posted: Apr 17, 2008 5:33 PM       E-mail this message      Reply 
    Dear SAP Support,
    I would like to know why does the system created 2 return deliveries with the same qty for a single return order document no.? One return delivery doc.no. was created 2 mins earlier than the 2nd return delivery document no. on the same day. After these 2 return deliveries were created, a credit note was also created for each return delivery doc. number. Here is the document flow:
    On Jan. 10, 2008, the Return Order was created
    The Delivery block field is set to 90- (Return block)
    The Billing block field is blank
    On Jan. 14, 2008 @ 12:08:44, the 1st return delivery doc. no. was created. And on the same day also @ 12:10:44, the 2nd delivery doc. was again created.  These 2 deliveries were created by 2 users. 1st delivery is by manual job, the 2nd is by background job processing.  there was a 2 mins. interval for these 2 deliveries.  
    On Jan. 21, 2008 @ 9:47:33, the 1st Credit Return Note was created. And on the same day also @ 9:48:00, the 2nd Credit Return Note was again created.
    In my initial investigation, I found out that there were changes made on the return order document before the 2 return delivery documents were created. Below are the changes that happened:
    On Jan. 14, 2008, @ 9:25:22 hour, the following changes occurred:
    a) Delivery block was changed from 90 - (Return block) to blank
    b) Billing block was changed from blank to 08 - (check credit memo)
    On Jan. 14, 2008, @ 12:08:44, T-Inv Comb field was changed from DC to C
    On Jan. 21, 2008, @ 9:47:20, the Billing Block was changed again from 08 - (check credit memo) to blank
    Will the above changes, contribute to this issue?
    I am also suspecting that the timing on the creation of deliveries via manual job and scheduled background job processig could be the root cause because of the slim time frame between the two job?  
    I hope you can help me get an explanation to this and how this can be avoided.
    Thank you very much in advanced for your help on this matter.
    Hoping to hear from you soon.
    Kind regards,
    Cynthia M. Ondillo
    SAP SD Functional Support

    Hello Jonathan,
    Yes, the  'update document flow' box is ticked and the entry in the 'Pos./negative quantity' field is '+'
      Target delivery type is LR - Returns Delivery    Source sls doc. type is ZRE - Coats Returns Order
      Item category is ZREN - Coats Returns Item
    Since we do not see anything missing in the above setting, can we say that it is a system bug when running manual delivery job close to the time for running the scheduled background job? 
    If it is a system bug, how can this be corrected?
    Regards,
    Cynthia

  • 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

  • 2 pricing procedures for the same sales area

    Hi Gurus.,
                  My client requirement is the client requires 2 pricing procedures for the combination of Same sales areaDEocument Pricing procedurecustomer pricing procedure in OVKK
    He doesnt want to use new sales area or new document pricing procedure or new customer pricing procedure,I know that in standard SAP it is not possible.
    Can any of the gurus throw some light on this.Some work around is required here,So can u please say the required changes in Standard functionality.
    Thanks & Regards
    Narayana
    Message was edited by:
            manam narayana
    Message was edited by:
            manam narayana
    Message was edited by:
            manam narayana

    Hi Gurus.,
                   First of all thank you very much for giving me so tremendous response, But my client requirement is,
                  He has one customer and for that customer when raising an order ,for some orders Tax shouldnot caliculate and for some orders Tax should be caliculated,
            For example :  If he gives price 100,Then the base price should be 100,For some orders he  gives price as 130 rs which is inclusive of tax like 110 should be the base price and 20 rs tax should get caliculated
               So i have tried in the pricing procedures and we have standard pricing procedure RVAA01 & RVAB01 ,In which RVAB01 is the price inclusive of tax procedure,We can assighn different pricing procedures if any of the combination in OVKK is changed,But he dont want to change the combination in OVKK.
            So client asks now when he raise an order he decides how the price should be caliculated, i.e the price may be he give price or price inclusive tax,of which the pricing procedure should automatically split the tax and price accordingly,He is asking in the way like when we raise a sales order we should do like a pop up box should appear asking which pricing procedure should be selected,So on selecting the pricing procedure the order should caliculate based on the selected pricing procedure
    Thanks & Regards
    Narayana

  • While filling up the set uptables ran twice for the same sales order number

    Hi all,
    I ran the set up tables for a sales order number in the morning and then ran again in the evening by mistake so when i see in the rsa3 i can see 2 sales order number.
    If i load the same in the sales order header and item ods, will there be any duplicates from ecc to bi?
    Thanks
    Pooja

    Hello,
    If you load your ODS in overwrite mode, there should not be any problem.
    Regards,
    Fred

  • 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

  • Sales Deal with two different validation dates for the same material

    Hi SAPers,
    I am trying to create a u201CSales Dealu201D VB31, for the same material/condition, but with two different validation dates. After the creation of the first record, I select u201CNew conditionu201D button, but the system give me the message VK104, u201Cthe condition is being processed in the current session.u201D.
    How can I solve this issue?
    Thanks in advance.
    Pedro

    We can't have multiple records for the same condition and key values valid on the same date. The condition end date is part of the primary key in the database table. The date ranges between the records cannot overlap. When you create a new record, usually the end date is set to 12/31/9999 by default. If you need to have this deal to end on a different date and a new deal to start afterwards, then first you need to change 12/31/9999 to a different date.
    Also usually I try to exit the screen between the transactions.

  • How to prevent modifying the same sales order in R/3 & CRM at the same time

    Guys,
    We are using CRM 5.0& R/3 4.6C. We have the middle set up. I have noticed that its possible to open the same sales order in R/3 and CRM in the change mode. I believe this could cause inconsistenices if the users modify the same order in different systems. Is there a standar way to prevent this from happening.
    Is there something like a change lock like we have the distribution lock?
    Anirudh

    Hi,
    As per OSS Note 705200 scenario X, Y and Z are supported with R/3 4.6C. Even if you use Scenario A, SAP wont support that. I would suggest sceario Z to be implemented. This would convert all the CRM order into R/3 order as soon as they are transferred to R/3. As a result the order can now only be modified in R/3 and all the changes would flow back into CRM maintaining the integrity between the systems.
    Refer to OSS Note 541113 for details.
    Regards,
    Gaurav Gera

  • How to avoid that two or more people altering the same Sales Order

    I'm looking for a way to avoid that two or more people altering the same Sales Order at the same time.
    If someone has entered a Sales Order in the system and something needs to be adjust it can be done by two or more people at the same time. The problem is that when someone is saving these changes, the changes of another person, who is still working on the same order, get lost.
    So what we need is an alert that someone is already using this order and that no other person can make any changes at that time. So the order needs to be blocked for altering for any other person at that time.
    To avoid this I think you have to do something with the Stored Procedure. Or has someone a more simple and better solution. So far I didn't find a standard option in Business One neither a solution in this forum.
    Best regards,
    Tim

    Tim,
    There is nothing in the application settings in Business One that could be used to prevent this.  You may post this to the SDK forum as well and perhaps there is a way to achieve this through SDK.

  • How to avoid that two or more people alter the same Sales Order same time

    I'm looking for a way to avoid that two or more people altering the same Sales Order at the same time.
    If someone has entered a Sales Order in the system and something needs to be adjust it can be done by two or more people at the same time. The problem is that when someone is saving these changes, the changes of another person, who is still working on the same order, get lost.
    So what we need is an alert that someone is already using this order and that no other person can make any changes at that time. So the order needs to be blocked for altering for any other person at that time.
    To avoid this I think you have to do something with the Stored Procedure. Or has someone a more simple and better solution.
    I've already put this thread in the Business One forum and someone suggested to put it in the Business One SDK forum, as there isn't a solution in Business One itself.
    So if someone can give me a direction for a solution I would be very pleased.
    Best regards,
    Tim

    Hi Tim,
    The only thing that comes close to what you want in standard SBO is Data Ownership. However, this can't stop someone editing a document that is already being edited.
    You can't use stored procedures to track which document is open because the SBO_SP_TransactionNotification proc (which is the only one that you are able to customise) is triggered when a document is updated or added (or cancelled or closed) and not when the document is actually being edited in the user-interface.
    You could do this by writing an addon that uses the UI API to trap events in the sales order form. In theory, a sales order is being edited if the sales order form is in Update mode (ie in order for the form to be in Update mode, the user must have selected an existing document and changed the value of at least one field). You can trap the event of the user changing a value and then log the user and document in a table. When other users try to edit the same document, you could check the table and then prevent them changing values. When the first user clicks on the update button (or cancels the update or closes the form etc etc) you can remove the lock on the document. However, I have doubts as to how robust it would be. The problem with this kind of locking solution is that you sometimes get 'stranded' locks (eg user was editing a document when their workstation crashed) and the solution can end up being more troublesome than it is worth.
    Kind Regards,
    Owen

  • How to put 2 kinds of material prices on the same sales order

    Hello SD Gurus,
    I have a requirement to put a one-time price (e.g. installation price ) and a recurring monthly price on the same sales order.
    I've tried the following but it is not working.
    1. I have a pricing procedure (PSER01) in which I'm using the following price types:PR00 (Defined as a "Discount or Surcharge") and PRSV.  I'm using PR00 to represent my one-time installation price.  I'm using PRSV to represent my monthly+recurring price.
    2. I used it for a material master in a sales order.  I can add PR00 and see the green traffic light.  But as soon as I add PRSV, the traffic light on PR00 turns yellow (Inactive because of subsequent price).
    I've read several posts on the forum regarding this.  Based on my understanding, I'm using two pricing conditions in one pricing procedure which is not allowed. 
    What can I do differently to enable the one-time price and monthly price to appear for my material master on the sales order?
    Thanks so much for your help!

    Hi,
    As per SAP Logic, if the condition type has condition class "C" then only one value is allowed.
    if you want to add two values ( Fixed + Variable) then you can do the following logic.
    1 ) Have one condition type  say ZFIX ( Use this for Fixed Value ) cond class = C
    2 ) another condition type Say ZVAR(Use this for  variable value ) Cond Class = C
    3 ) another condition type say Zxxx ( use this for your Final Value) cond class = C
    now do not assign any access sequence to the third condition type. write a logic in the "Alt Calculation type " routine to get the value of this condition from the sume of ZFIX + ZVAR
    i.e., ZXXX = ZFIX + ZVAR.
    Make sure that the sequence of the codition types are mentioned exactly like the above.
    this is because if you put ZXXX third then the system automatically ignores the value of ZFIX and ZVAR.
    but the values against those condition types will be stores internally. So in future if we want some information also we can trace back..
    let me know if you need further help..
    thanks..

  • Multiple Executions Plans for the same SQL statement

    Dear experts,
    awrsqrpt.sql is showing multiple executions plans for a single SQL statement. How is it possible that one SQL statement will have multiple Executions Plans within the same AWR report.
    Below is the awrsqrpt's output for your reference.
    WORKLOAD REPOSITORY SQL Report
    Snapshot Period Summary
    DB Name         DB Id    Instance     Inst Num Release     RAC Host
    TESTDB          2157605839 TESTDB1               1 10.2.0.3.0  YES testhost1
                  Snap Id      Snap Time      Sessions Curs/Sess
    Begin Snap:     32541 11-Oct-08 21:00:13       248     141.1
      End Snap:     32542 11-Oct-08 21:15:06       245     143.4
       Elapsed:               14.88 (mins)
       DB Time:               12.18 (mins)
    SQL Summary                            DB/Inst: TESTDB/TESTDB1  Snaps: 32541-32542
                    Elapsed
       SQL Id      Time (ms)
    51szt7b736bmg     25,131
    Module: SQL*Plus
    UPDATE TEST SET TEST_TRN_DAY_CL = (SELECT (NVL(ACCT_CR_BAL,0) + NVL(ACCT_DR_BAL,
    0)) FROM ACCT WHERE ACCT_TRN_DT = (:B1 ) AND TEST_ACC_NB = ACCT_ACC_NB(+)) WHERE
    TEST_BATCH_DT = (:B1 )
    SQL ID: 51szt7b736bmg                  DB/Inst: TESTDB/TESTDB1  Snaps: 32541-32542
    -> 1st Capture and Last Capture Snap IDs
       refer to Snapshot IDs witin the snapshot range
    -> UPDATE TEST SET TEST_TRN_DAY_CL = (SELECT (NVL(ACCT_CR_BAL,0) + NVL(AC...
        Plan Hash           Total Elapsed                 1st Capture   Last Capture
    #   Value                    Time(ms)    Executions       Snap ID        Snap ID
    1   2960830398                 25,131             1         32542          32542
    2   3834848140                      0             0         32542          32542
    Plan 1(PHV: 2960830398)
    Plan Statistics                        DB/Inst: TESTDB/TESTDB1  Snaps: 32541-32542
    -> % Total DB Time is the Elapsed Time of the SQL statement divided
       into the Total Database Time multiplied by 100
    Stat Name                                Statement   Per Execution % Snap
    Elapsed Time (ms)                            25,131       25,130.7     3.4
    CPU Time (ms)                                23,270       23,270.2     3.9
    Executions                                        1            N/A     N/A
    Buffer Gets                               2,626,166    2,626,166.0    14.6
    Disk Reads                                      305          305.0     0.3
    Parse Calls                                       1            1.0     0.0
    Rows                                        371,735      371,735.0     N/A
    User I/O Wait Time (ms)                         564            N/A     N/A
    Cluster Wait Time (ms)                            0            N/A     N/A
    Application Wait Time (ms)                        0            N/A     N/A
    Concurrency Wait Time (ms)                        0            N/A     N/A
    Invalidations                                     0            N/A     N/A
    Version Count                                     2            N/A     N/A
    Sharable Mem(KB)                                 26            N/A     N/A
    Execution Plan
    | Id  | Operation                    | Name            | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | UPDATE STATEMENT             |                 |       |       |  1110 (100)|          |
    |   1 |  UPDATE                      | TEST            |       |       |            |          |
    |   2 |   TABLE ACCESS FULL          | TEST            |   116K|  2740K|  1110   (2)| 00:00:14 |
    |   3 |   TABLE ACCESS BY INDEX ROWID| ACCT            |     1 |    26 |     5   (0)| 00:00:01 |
    |   4 |    INDEX RANGE SCAN          | ACCT_DT_ACC_IDX |     1 |       |     4   (0)| 00:00:01 |
    Plan 2(PHV: 3834848140)
    Plan Statistics                        DB/Inst: TESTDB/TESTDB1  Snaps: 32541-32542
    -> % Total DB Time is the Elapsed Time of the SQL statement divided
       into the Total Database Time multiplied by 100
    Stat Name                                Statement   Per Execution % Snap
    Elapsed Time (ms)                                 0            N/A     0.0
    CPU Time (ms)                                     0            N/A     0.0
    Executions                                        0            N/A     N/A
    Buffer Gets                                       0            N/A     0.0
    Disk Reads                                        0            N/A     0.0
    Parse Calls                                       0            N/A     0.0
    Rows                                              0            N/A     N/A
    User I/O Wait Time (ms)                           0            N/A     N/A
    Cluster Wait Time (ms)                            0            N/A     N/A
    Application Wait Time (ms)                        0            N/A     N/A
    Concurrency Wait Time (ms)                        0            N/A     N/A
    Invalidations                                     0            N/A     N/A
    Version Count                                     2            N/A     N/A
    Sharable Mem(KB)                                 26            N/A     N/A
    Execution Plan
    | Id  | Operation                    | Name         | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | UPDATE STATEMENT             |              |       |       |     2 (100)|          |
    |   1 |  UPDATE                      | TEST         |       |       |            |          |
    |   2 |   TABLE ACCESS BY INDEX ROWID| TEST         |     1 |    28 |     2   (0)| 00:00:01 |
    |   3 |    INDEX RANGE SCAN          | TEST_DT_IND  |     1 |       |     1   (0)| 00:00:01 |
    |   4 |   TABLE ACCESS BY INDEX ROWID| ACCT         |     1 |    26 |     4   (0)| 00:00:01 |
    |   5 |    INDEX RANGE SCAN          | INDX_ACCT_DT |     1 |       |     3   (0)| 00:00:01 |
    Full SQL Text
    SQL ID       SQL Text
    51szt7b736bm UPDATE TEST SET TEST_TRN_DAY_CL = (SELECT (NVL(ACCT_CR_BAL, 0) +
                  NVL(ACCT_DR_BAL, 0)) FROM ACCT WHERE ACCT_TRN_DT = (:B1 ) AND PB
                 RN_ACC_NB = ACCT_ACC_NB(+)) WHERE TEST_BATCH_DT = (:B1 )Your input is highly appreciated.
    Thanks for taking your time in answering my question.
    Regards

    Oracle Lover3 wrote:
    Dear experts,
    awrsqrpt.sql is showing multiple executions plans for a single SQL statement. How is it possible that one SQL statement will have multiple Executions Plans within the same AWR report.If you're using bind variables and you've histograms on your columns which can be created by default in 10g due to the "SIZE AUTO" default "method_opt" parameter of DBMS_STATS.GATHER__STATS it is quite normal that you get different execution plans for the same SQL statement. Depending on the values passed when the statement is hard parsed (this feature is called "bind variable peeking" and enabled by default since 9i) an execution plan is determined and re-used for all further executions of the same "shared" SQL statement.
    If now your statement ages out of the shared pool or is invalidated due to some DDL or statistics gathering activity it will be re-parsed and again the values passed in that particular moment will determine the execution plan. If you have skewed data distribution and a histogram in place that reflects that skewness you might get different execution plans depending on the actual values used.
    Since this "flip-flop" behaviour can sometimes be counter-productive if you're unlucky and the values used to hard parse the statement leading to a plan that is unsuitable for the majority of values used afterwards, 11g introduced the "adaptive" cursor sharing that attempts to detect such a situation and can automatically re-evaluate the execution plan of the statement.
    Regards,
    Randolf
    Oracle related stuff blog:
    http://oracle-randolf.blogspot.com/
    SQLTools++ for Oracle (Open source Oracle GUI for Windows):
    http://www.sqltools-plusplus.org:7676/
    http://sourceforge.net/projects/sqlt-pp/

  • 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                                                                                                     

  • Is it possible to have Different Interval Ranges for the same Doc Type

    Dear All,
    Here is the issue.Is it possible to have different interval ranges for the same document type according to certain condition.Like my client , wants his interval ranges  be divided according to region(which are many)
    Regards,
    Sameer Jalees

    Hello,
    As you know we can only assign one number range for External and one number range group for internal in the sales document type.
    If you want different number ranges based on the regions, then as Jignesh suggested, you need to go for an enhancement.
    Use the exit USEREXIT_NUMBER_RANGE in program MVA45AFZZ, include a Z table with region as a critera and number range group for different numbers based on the regions. Talk to the business and get more details, get the help of ABAP team for technical details.
    Regards,
    SAM

  • Multiple shipping addresses for the same supplier (depending on the symbol)

    Hello ,can we set up multiple shipping addresses for the same supplier (depending on the symbol)?
    .& How..
    Thanks

    a delivery adedress has nothing to do with a certain supplier, except you are talking about subcontracting (do you?)
    a delivery address specifies an address where you want the supplier to send the goods to.
    if it is a third party PO, then the delivery address is derived from ship-to partner of the sales order.
    in case of a standard order to stock, the delivery address is coming from the storage location address (if maintained). if no storage location address is maintained, then SAP takes the address from your plant.
    You can manually add a delivery address in MEAN transaction and then manually assign in POs delivery address tab.
    here you can as well take the address from any address already in your system (e.g. any customer or vendor).

Maybe you are looking for

  • How large of a hard drive can I upgrade to on my late 2009 MacBook?

    I currently have a 250GB 5400 rpm hard drive that cam standard in my MacBook.  I would like to upgrade to a 750 GB.  Can I do this? and can I move to a 7200 rpm drive instead?

  • Support Chinese Character

    Hi, I have some problems on handling Chinese Character. I pass Chinese words to CFC and then do the SELECT search in DB. However, I find it cannot find Chinese words correctly. When I try to prompt (  alert(#trim(URLDecode(search_tenderee_name))#)  )

  • Plant wise profitability

    Dear All, Scenario: There is a single co. code. It has 2 main plants say EX & NEX. Plant EX is excisable and plant NEX is non-excisable. The company has total 14 branches all over india responsible for storage and sales of company's products.There is

  • Oracle 9i + Linux

    Hello all I try to install Oracle9i on my slackware 8.0 box with kernel 2.4.7pre5. I have problem with jre - when I try to run rinInstall I get: Initializing Java Virtual Machine from /tmp/OraInstall/jre/bin/jre. Please wait... SIGSEGV 11* segmentati

  • Been asked I'm sure but I need to know about files on Ipod

    I want to pull all the files off my Ipod and completely redo it. Can anyone please explain how I can do that. I'm not sure which Generation it is but I know it's an older one. 15GB model If anyone understands what I'm trying to ask can you please exp