Query for Unit Commision

I am trying to write a query show the per unit commission for an item on a Sales Order and put that value into a UDF.
I have got as far as getting a result on the document for a specific row, but I cannot get it to select for all rows on the document.
What I have is as follows:
SELECT (T0.Price* T0.Commission/100)
FROM RDR1 T0 INNER JOIN ORDR T1 ON T0.DocEntry = T1.DocEntry
WHERE T1.DocNum = $[$8.0] AND T0.ItemCode = $[$38.0]
It is the last part where I am trying to specify by itemcode that is proving troublesome. I have used a specific line number instead of ItemCode and that works.
Can someone help me on this?
Rick Winn

The syntax for ItemCode on the marketing document is $\[$38.1.0]
You simply need
SELECT ($\[$38.17.Number]*$\[$38.28.Number]/100)
38.17 refers to Price After Discount column and 38.28 refers to the commission column

Similar Messages

Hierarchical + Analytical query for organizational unit parameters

Hello gurus,
I try for a couples of hour ago to make a query work as I would like.
Our application need to store some parameters for our organization units. These organization units are typically organized in in an hierarchy manner: one top unit with many level of child units. The parameters are stored into another table with 1:1 relationship.
For sake of visualisation, here is the data for the organization unit and parameter table in a more visual format:
SQL> select * from organization_unit;
UNIT_CODE UNIT_NAME            PARENT_UNIT_CODE
00000      Top level
10         L2 unit #10          00000
10-01      L3 unit #10-01       10
10-02      L3 unit #10-02       10
20         L2 unit #20          00000
20-01      L3 unit #20-01       20
20-02      L3 unit #20-02       20
SQL> select * from org_unit_parameters;
UNIT_CODE PARAM1               PARAM2               PARAM3               PARAM4
00000      Default value        Default value        Default value        {null}
10         {null}               Value from 10        Value from 10        {null}
10-01      {null}               {null}               Value from 10-01     {null}
10-02      {null}               {null}               {null}               Value from 10-02
20         Value from 20        Value from 20        Value from 20        {null}
20-01      {null}               Value from 20-01     {null}               {null}
20-02      {null}               Value from 20-02     {null}               {null}The application will query the parameter table to get a parameter value for a given unit.
The parameter resolution algorithm is rather simple: when querying a unit, the applicable parameter is the one defined at the requested level. If the parameter is not defined (null) at the requested level, the parameter value that must be returned is the next defined one in the parent hierarchy. In some rare cases, it can be null if a parameter is not defined anywhere from the requested level to top.
I've made a query that seems to work when querying for one unit at a time. It use hierarchical operators (start with + connect by) with a bit of analytical functions. Here is a test & raw output example:
SQL> WITH hierarchy
2 AS
3 (
4    SELECT ou.unit_code,
5         LEVEL            AS lvl
6    FROM   organization_unit ou
7    START WITH
8      ou.unit_code = '20-01'
9    CONNECT BY
10      ou.unit_code = PRIOR ou.parent_unit_code
11 )
12 SELECT h.*,
13       p.param1                                                        AS param1_raw,
14       LAST_VALUE (p.param1 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param1_with_last,
15       FIRST_VALUE(p.param1 IGNORE NULLS) OVER (ORDER BY h.lvl ASC)    AS param1_with_first,
16       p.param2                                                        AS param2_raw,
17       LAST_VALUE (p.param2 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param2_with_last,
18       FIRST_VALUE(p.param2 IGNORE NULLS) OVER (ORDER BY h.lvl ASC)    AS param2_with_first,
19       p.param3                                                        AS param3_raw,
20       LAST_VALUE (p.param3 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param3_with_last,
21       FIRST_VALUE(p.param3 IGNORE NULLS) OVER (ORDER BY h.lvl ASC)    AS param3_with_first,
22       p.param4                                                        AS param4_raw,
23       LAST_VALUE (p.param4 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param4_with_last,
24       FIRST_VALUE(p.param4 IGNORE NULLS) OVER (ORDER BY h.lvl ASC)    AS param4_with_first
25 FROM   hierarchy                                h
26         LEFT JOIN org_unit_parameters         p
27         ON h.unit_code = p.unit_code
28 ORDER BY h.lvl DESC;
UNIT_CODE   LVL PARAM1_RAW           PARAM1_WITH_LAST     PARAM1_WITH_FIRST    PARAM2_RAW           PARAM2_WITH_LAST     PARAM2_WITH_FIRST    PARAM3_RAW           PARAM3_WITH_LAST     PARAM3_WITH_FIRST    PARAM4_RAW           PARAM4_WITH_LAST     PARAM4_WITH_FIRST
00000         3 Default value        Default value        Value from 20        Default value        Default value        Value from 20-01     Default value        Default value        Value from 20        {null}               {null}               {null}
20            2 Value from 20        Value from 20        Value from 20        Value from 20        Value from 20        Value from 20-01     Value from 20        Value from 20        Value from 20        {null}               {null}               {null}
20-01         1 {null}               Value from 20        {null}               Value from 20-01     Value from 20-01     Value from 20-01     {null}               Value from 20        {null}               {null}               {null}               {null}Seems pretty good, the upper parameters are well «propagated» down with LAST_VALUE function. But, I don't understand why the use of FIRST_VALUE and oppposite ordering doesn't give the same result. A little more playing with the last query for getting the final result for a given unit code:
SQL> SELECT *
2 FROM
3 (
4     WITH hierarchy
5     AS
6     (
7        SELECT ou.unit_code,
8               LEVEL            AS lvl
9        FROM   organization_unit ou
10        START WITH
11           ou.unit_code = '20-01'
12        CONNECT BY
13           ou.unit_code = PRIOR ou.parent_unit_code
14     )
15     SELECT h.*,
16            LAST_VALUE (p.param1 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param1,
17            LAST_VALUE (p.param2 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param2,
18            LAST_VALUE (p.param3 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param3,
19            LAST_VALUE (p.param4 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param4
20     FROM   hierarchy                                h
21               LEFT JOIN org_unit_parameters         p
22               ON h.unit_code = p.unit_code
23     ORDER BY h.lvl
24 )
25 WHERE ROWNUM = 1;
UNIT_CODE   LVL PARAM1               PARAM2               PARAM3               PARAM4
20-01         1 Value from 20        Value from 20-01     Value from 20        {null}Works well!
But, my ultimate goal is to create a view that resolve correctly all these parameters for each level of the organization with proper propagation rather then querying for each unit at a time. I played a bit, but without success. :( My current raw query is this one:
SQL> WITH hierarchy
2 AS
3 (
4     SELECT ou.unit_code,
5            LPAD(' ',2*(LEVEL-1)) || ou.unit_code    AS tree,
6            LEVEL                                    AS lvl
7     FROM   organization_unit ou
8     START WITH
9        parent_unit_code IS NULL
10     CONNECT BY
11        PRIOR unit_code = parent_unit_code
12 )
13 SELECT h.*,
14         p.param1                                                        AS param1_raw,
15         LAST_VALUE (p.param1 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param1_with_last,
16         FIRST_VALUE(p.param1 IGNORE NULLS) OVER (ORDER BY h.lvl ASC)    AS param1_with_first,
17         p.param2                                                        AS param2_raw,
18         LAST_VALUE (p.param2 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param2_with_last,
19         FIRST_VALUE(p.param2 IGNORE NULLS) OVER (ORDER BY h.lvl ASC)    AS param2_with_first,
20         p.param3                                                        AS param3_raw,
21         LAST_VALUE (p.param3 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param3_with_last,
22         FIRST_VALUE(p.param3 IGNORE NULLS) OVER (ORDER BY h.lvl ASC)    AS param3_with_first,
23         p.param4                                                        AS param4_raw,
24         LAST_VALUE (p.param4 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param4_with_last,
25         FIRST_VALUE(p.param4 IGNORE NULLS) OVER (ORDER BY h.lvl ASC)    AS param4_with_first
26 FROM   hierarchy                          h
27            LEFT JOIN org_unit_parameters   p
28            ON h.unit_code = p.unit_code
29 ORDER BY h.unit_code;
UNIT_CODE TREE        LVL PARAM1_RAW                PARAM1_WITH_LAST          PARAM1_WITH_FIRST      PARAM2_RAW                   PARAM2_WITH_LAST          PARAM2_WITH_FIRST         PARAM3_RAW                PARAM3_WITH_LAST          PARAM3_WITH_FIRST         PARAM4_RAW                PARAM4_WITH_LAST       PARAM4_WITH_FIRST
00000      00000         1 Default value             Default value             Default value          Default value                Default value             Default value             Default value             Default value             Default value             {null}                    Value from 10-02       {null}
10           10          2 {null}                    Value from 20             Default value          Value from 10                Value from 10             Default value             Value from 10             Value from 10             Default value             {null}                    Value from 10-02       {null}
10-01          10-01     3 {null}                    {null}                    Default value          {null}                       Value from 20-02          Default value             Value from 10-01          Value from 10-01          Default value             {null}                    Value from 10-02       Value from 10-02
10-02          10-02     3 {null}                    {null}                    Default value          {null}                       Value from 20-02          Default value             {null}                    Value from 10-01          Default value             Value from 10-02          Value from 10-02       Value from 10-02
20           20          2 Value from 20             Value from 20             Default value          Value from 20                Value from 10             Default value             Value from 20             Value from 10             Default value             {null}                    Value from 10-02       {null}
20-01          20-01     3 {null}                    {null}                    Default value          Value from 20-01             Value from 20-02          Default value             {null}                    Value from 10-01          Default value             {null}                    Value from 10-02       Value from 10-02
20-02          20-02     3 {null}                    {null}                    Default value          Value from 20-02             Value from 20-02          Default value             {null}                    Value from 10-01          Default value             {null}                    Value from 10-02       Value from 10-02As you can see, it's not as I expected. I know there's something to do with a PARTITION BY clause, but don't know how.
Is anyone knows how to solve my problem?
Thanks
Bruno
For reproductibility purposes, here is the code to create sturcture and data:
Here is the format of my tables and some samble data:
CREATE TABLE organization_unit (
   unit_code         VARCHAR2(5 CHAR)   NOT NULL PRIMARY KEY,
   unit_name         VARCHAR2(100 CHAR) NOT NULL,
   parent_unit_code VARCHAR2(5 CHAR)
CREATE TABLE org_unit_parameters (
   unit_code         VARCHAR2(5 CHAR)   NOT NULL PRIMARY KEY,
   param1            VARCHAR2(100 CHAR),
   param2            VARCHAR2(100 CHAR),
   param3            VARCHAR2(100 CHAR),
   param4            VARCHAR2(100 CHAR)
-- Inserting data
INSERT INTO organization_unit (unit_code, unit_name, parent_unit_code)
VALUES ('00000', 'Top level', NULL);
INSERT INTO organization_unit (unit_code, unit_name, parent_unit_code)
VALUES ('10', 'L2 unit #10', '00000');
INSERT INTO organization_unit (unit_code, unit_name, parent_unit_code)
VALUES ('10-01', 'L3 unit #10-01', '10');
INSERT INTO organization_unit (unit_code, unit_name, parent_unit_code)
VALUES ('10-02', 'L3 unit #10-02', '10');
INSERT INTO organization_unit (unit_code, unit_name, parent_unit_code)
VALUES ('20', 'L2 unit #20', '00000');
INSERT INTO organization_unit (unit_code, unit_name, parent_unit_code)
VALUES ('20-01', 'L3 unit #20-01', '20');
INSERT INTO organization_unit (unit_code, unit_name, parent_unit_code)
VALUES ('20-02', 'L3 unit #20-02', '20');
INSERT INTO ORG_UNIT_PARAMETERS (unit_code, param1, param2, param3)
VALUES ('00000', 'Default value', 'Default value', 'Default value');
INSERT INTO ORG_UNIT_PARAMETERS (unit_code, param2, param3)
VALUES ('10', 'Value from 10', 'Value from 10');
INSERT INTO ORG_UNIT_PARAMETERS (unit_code, param3)
VALUES ('10-01', 'Value from 10-01');
INSERT INTO ORG_UNIT_PARAMETERS (unit_code, param4)
VALUES ('10-02', 'Value from 10-02');
INSERT INTO ORG_UNIT_PARAMETERS (unit_code, param1, param2, param3)
VALUES ('20', 'Value from 20', 'Value from 20', 'Value from 20');
INSERT INTO ORG_UNIT_PARAMETERS (unit_code, param2)
VALUES ('20-01', 'Value from 20-01');
INSERT INTO ORG_UNIT_PARAMETERS (unit_code, param2)
VALUES ('20-02', 'Value from 20-02');
COMMIT;

Now, I hoppe I got your reqs:
WITH hierarchy AS (
                   SELECT ou.unit_code,
                           LPAD(' ',2*(LEVEL-1)) || ou.unit_code    AS tree,
                           LEVEL                                    AS lvl,
                           param1                                   AS param1_raw,
                           param2                                   AS param2_raw,
                           param3                                   AS param3_raw,
                           param4                                   AS param4_raw,
                           SYS_CONNECT_BY_PATH(p.param1,'#') || '#' AS param1_path,
                           SYS_CONNECT_BY_PATH(p.param2,'#') || '#' AS param2_path,
                           SYS_CONNECT_BY_PATH(p.param3,'#') || '#' AS param3_path,
                           SYS_CONNECT_BY_PATH(p.param4,'#') || '#' AS param4_path
                     FROM organization_unit ou LEFT JOIN org_unit_parameters p
                             ON ou.unit_code = p.unit_code
                     START WITH parent_unit_code IS NULL
                     CONNECT BY PRIOR ou.unit_code = parent_unit_code
SELECT unit_code,
        tree,
        lvl,
        param1_raw,
        REGEXP_SUBSTR(param1_path,'[^#]+',1,GREATEST(1,REGEXP_COUNT(param1_path,'[^#]+'))) AS param1_with_last,
        REGEXP_SUBSTR(param1_path,'[^#]+')                                                 AS param1_with_first,
        param2_raw,
        REGEXP_SUBSTR(param2_path,'[^#]+',1,GREATEST(1,REGEXP_COUNT(param2_path,'[^#]+'))) AS param2_with_last,
        REGEXP_SUBSTR(param2_path,'[^#]+')                                                 AS param2_with_first,
        param3_raw,
        REGEXP_SUBSTR(param3_path,'[^#]+',1,GREATEST(1,REGEXP_COUNT(param3_path,'[^#]+'))) AS param3_with_last,
        REGEXP_SUBSTR(param3_path,'[^#]+')                                                 AS param3_with_first,
        param4_raw,
        REGEXP_SUBSTR(param4_path,'[^#]+',1,GREATEST(1,REGEXP_COUNT(param4_path,'[^#]+'))) AS param4_with_last,
        REGEXP_SUBSTR(param4_path,'[^#]+')                                                 AS param4_with_first
FROM hierarchy
ORDER BY unit_code
UNIT_ TREE              LVL PARAM1_RAW       PARAM1_WITH_LAST PARAM1_WITH_FIRS PARAM2_RAW       PARAM2_WITH_LAST PARAM2_WITH_FIRS PARAM3_RAW       PARAM3_WITH_LAST PARAM3_WITH_FIRS PARAM4_RAW       PARAM4_WITH_LAST PARAM4_WITH_FIRS
00000 00000               1 Default value    Default value    Default value    Default value    Default value    Default value    Default value    Default value    Default value
10      10                2                  Default value    Default value    Value from 10    Value from 10    Default value    Value from 10    Value from 10    Default value
10-01     10-01           3                  Default value    Default value                     Value from 10    Default value    Value from 10-01 Value from 10-01 Default value
10-02     10-02           3                  Default value    Default value                     Value from 10    Default value                     Value from 10    Default value    Value from 10-02 Value from 10-02 Value from 10-02
20      20                2 Value from 20    Value from 20    Default value    Value from 20    Value from 20    Default value    Value from 20    Value from 20    Default value
20-01     20-01           3                  Value from 20    Default value    Value from 20-01 Value from 20-01 Default value                     Value from 20    Default value
20-02     20-02           3                  Value from 20    Default value    Value from 20-02 Value from 20-02 Default value                     Value from 20    Default value
7 rows selected.
SQL> SY.
Edited by: Solomon Yakobson on Nov 12, 2010 10:09 AM

Adhoc query for IT0041

I was told that it is possible to create a separate 'Date for Date Type' for each 'Date Type' in the selection criteria of an adhoc query for IT0041. Can somebody help me with this please?

Hi Sven
Thanks.
I created it with PCH , but very few fields are visible for IT1001
Hence if I want to find chief of Org unit A, then I cannot find it as 'Relationship type/relationship' field of IT1001 is missing here.
Basically I need all the fields which are displayed in IT1001 as shown below:
Need your help to find the way out. Thanks
KP

Can any one send select query for this?

Hi,
can any one plese send select query for the following query.please send as early as possible.
Loop through the I_BSID internal table to fill records in I_OUTPUT.Combine data from I_BSID, I_KNKK, I_KNKK_KNKLI, I_KNA1 and I_KNVV into I_OUTPUT based on the linking conditions .Field Description Source are
I_OUTPUT-BUKRS     Company code     I_BSID-BUKRS
I_OUTPUT-KUNNR     Customer number     I_BSID-KUNNR
I_OUTPUT-NAME1     Customer Name     I_KNA1-NAME1
I_OUTPUT-KNKLI     Credit account     I_KNKK-KNKLI
I_OUTPUT-KDGRP     Customer Group     I_KNKK-KDGRP
I_OUTPUT-KLIMK     Credit Limit     I_KNKK_KNKLI-KLIMK
I_OUTPUT-KVGR1     Business Unit     I_KNVV-KVGR1
I_OUTPUT-REBZG     Invoice Number     I_BSID-REBZG
I_OUTPUT-BLDAT     Invoice Date     I_BSID-BLDAT
I_OUTPUT-WAERS     Document Currency     I_BSID-WAERS
I_OUTPUT-DUE_DATE     Due Date     Based on below
Calculation
Get the Payment terms days combining I_BSID and I_T052 based on the linking conditions mentioned above.    Note : a) Baseline Date : If baseline date I_BSID-ZFBDT is blank , use the Document Date.b) Payment Term Days :If I_BSID-ZBD3T is not blank, take this as Payment Term Days for Due date calculation.
                   If I_BSID-ZBD3T is Blank, then get payment term days from I_T052 based on I_BSID-ZTERM. If there are more than one record in I_T052 for the given Payment term, get the day part from baseline date and select the first record where the day limit I_T052-ZTAGG is greater than the day part.If I_BSID-ZBD3T is blank and I_BSID-ZTERM is also blank, then take Y000 (Due Immediately) as Payment term and proceed with the above logic. Set the payment term field blank while printing.
Calculate Due date : For Debits, Determine Due Date = Baseline Date + Payment term Days(not discount days)                                                          For Credits Due date = Baseline date.Then, move the amount I_BSID-DMBTR to respective buckets (Not yet Due, Current Due, Past due 1-30, Past Due 31-60 etc.) Based on the due date.
Thanks&Regards,
praveen kumar.A

HI,
To get Open Items you can use Function module:
data:i_items TYPE STANDARD TABLE OF rfpos.
CALL FUNCTION 'CUSTOMER_OPEN_ITEMS'
EXPORTING
bukrs = p_bukrs
kunnr = wa_customer-kunnr
TABLES
t_postab = i_items
EXCEPTIONS
no_open_items = 1
OTHERS = 2.
Table I_items will have all the open items for that Customer in the given company code.
Well for Clear Items: Try
GET_CLEARED_ITEMS or FMITPOFM_CLEARED_ITEMS_GET.
Hope it helps.
Manish

Create dynamic report or query for piece count

Hi abaper's
This is a very straight forward requirement. so please give me code
First you have to get the corresponding plant from table T320 for the given warehouse numbers in the selection screen.
1. Get the sum of order qty of sales orders from the sales order tables for the given warehouse(Plant), distribution channel and the give date range.
2. Get the confirmed transfer orders qty from the TO master table where TO confirmation date is in the given date range and WH number.
3. Get the total PGIed qty from the delivery master table where PGI'ed date in the given date range, shipping point is in the corresponding plant of the WH and for the given distribution channel.
As you are going to use the major tables please try to write the select commands effectively to avoid further performance issues.

How to improve the performance fo this code.....this very urgent.
& Issue Number : 22199 &
& Programmer : Anjaneyulu.Pabba &
& Transport Number : D01K962471 &
& Date of Creation : 19/03/2008 &
& Description : Dynamic report or query for piece count &
& Requested By : Parvati.Polisetty &
REPORT ZR_SD_PIECE_COUNT_ALV no standard page heading
 line-size 255
 line-count 65.
 TABLES DECLARATION
*TABLES: T320, "Assignment IM Storage Location to WM Warehouse Number
 VBAK, "Sales Document: Header Data
 VBAP, "Sales Document: Item Data
 TVKOV, "Org. Unit: Distribution Channels per Sales Organization
 LTAK, "WM transfer order header
 LTAP, "Transfer order item
 LIKP, "SD Document: Delivery Header Data
 LIPS. "SD document: Delivery: Item data
 TYPE-POOLS DECLARATION
TYPE-POOLS: SLIS .
 Internal Table Declaration
DATA : BEGIN OF TY_T320,
 WERKS TYPE WERKS_D,
 LGNUM TYPE LGNUM,
 END OF TY_T320.
DATA : BEGIN OF TY_VBAK,
 VBELN TYPE VBELN_VA,
 VTWEG TYPE VTWEG,
 WERKS TYPE WERKS_D,
 KWMENG TYPE KWMENG,
 VSTEL TYPE VSTEL,
 END OF TY_VBAK.
DATA : BEGIN OF TY_LTAK,
 LGNUM TYPE LGNUM,
 TANUM TYPE TANUM,
 VISTA TYPE LTAP_VISTA,
 END OF TY_LTAK.
DATA : BEGIN OF TY_LIKP,
 VBELN TYPE VBELN_VL,
 WERKS TYPE WERKS_D,
 LFIMG TYPE LFIMG,
 END OF TY_LIKP.
DATA : BEGIN OF TY_ITAB ,
LGNUM TYPE LGNUM, "Warehouse Number / Warehouse Complex
WERKS TYPE WERKS_D, "Plant
VBELN TYPE VBELN_VA, "Sales Document
VTWEG TYPE VTWEG, "Distribution Channel
KWMENG TYPE KWMENG, "Cumulative order quantity in sales units
TANUM TYPE TANUM , "Transfer Order Number
VISTA TYPE LTAP_VISTA, "Source actual quantity in alternative
 unit of measure
LFIMG TYPE LFIMG, "Actual quantity delivered (in sales units)
END OF TY_ITAB .
DATA: T_T320 LIKE STANDARD TABLE OF TY_T320 INITIAL SIZE 0 WITH HEADER
 LINE,
 T_VBAK LIKE STANDARD TABLE OF TY_VBAK INITIAL SIZE 0 .
DATA: T_LTAK LIKE STANDARD TABLE OF TY_LTAK INITIAL SIZE 0 WITH HEADER
 LINE.
DATA :T_LIKP LIKE STANDARD TABLE OF TY_LIKP INITIAL SIZE 0 WITH HEADER
 LINE.
DATA:T_ITAB LIKE STANDARD TABLE OF TY_ITAB INITIAL SIZE 0 WITH HEADER
 LINE .
*& Fieldcatalog Declaration
DATA : T_FCAT TYPE SLIS_T_FIELDCAT_ALV,
 W_FCAT TYPE SLIS_FIELDCAT_ALV.
DATA : W_LAYOUT TYPE SLIS_LAYOUT_ALV.
********Global Data Declaration***
DATA :G_REPID LIKE SY-REPID,
 G_EXIT(1) TYPE C,
 GX_VARIANT LIKE DISVARIANT,
 X_SAVE, "for Parameter I_SAVE
 GS_VARIANT TYPE DISVARIANT. "for parameter IS_VARIANT
data: g_lgnum type t320-lgnum,
 g_vtweg type vbak-vtweg,
 g_erdat type vbak-erdat.
*& Selection-Screen
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
SELECT-OPTIONS : S_LGNUM FOR g_lgnum, "Warehouse Number
 S_VTWEG FOR g_vtweg, "Distribution Channel
 S_ERDAT FOR g_erdat ."Date on which the record was
**********"created
SELECTION-SCREEN END OF BLOCK B1 .
SELECTION-SCREEN BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-002.
PARAMETER: P_VARI LIKE DISVARIANT-VARIANT. "Layout
SELECTION-SCREEN END OF BLOCK B2.
*& INITIALIZATION EVENT
INITIALIZATION.
CLEAR GS_VARIANT.
'gs_variant' must at least contain the report-id to allow
saving a variant.
G_REPID = SY-REPID.
§ 2.At least field REPORT of this structure has to be filled!
GS_VARIANT-REPORT = G_REPID.
§ 3.Determine saving options.
X_SAVE = 'A'. "The user may save all types of variants
*******Validating selection-screen values**********************
getting F4 value for display variant field
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_VARI.
PERFORM F4_FOR_VARIANT.
****validation of F4 value of display variant
AT SELECTION-SCREEN.
PERFORM PAI_OF_SELECTION_SCREEN.
*& Start-Of-Selection
START-OF-SELECTION.
*****Subroutine to select Plant from T320
PERFORM FIND_PLANT .
*****Subroutine to select Order Quantity from VBAP
PERFORM ORDER_QUANTITY .
*****Subroutine to select Transfer Order Quantity from LTAK and LTAP
PERFORM TRANSFER_ORDER_QUANTITY.
*****Subroutine to select TDelivery Quantity from LIKP and LIPS
PERFORM DELIVERY_QUANTITY.
*& End-Of-Selection
END-OF-SELECTION.
*****Subroutine for Fieldcatalog
PERFORM FIELDCATALOG .
*****Subroutine for Final Output
PERFORM DISPLAY_OUTPUT .
*& Subroutine Implementaion
*& Form FIND_PLANT
 text
--> p1 text
<-- p2 text
FORM FIND_PLANT .
SELECT WERKS
 LGNUM
 FROM T320
 INTO TABLE T_T320
 WHERE LGNUM IN S_LGNUM.
ENDFORM. " FIND_PLANT
*& Form order_quantity
 text
--> p1 text
<-- p2 text
FORM ORDER_QUANTITY .
SELECT VK~VBELN
 VK~VTWEG
 VP~WERKS
 VP~KWMENG
 VP~VSTEL
 INTO TABLE T_VBAK FROM VBAK AS VK
 INNER JOIN VBAP AS VP
 ON VKVBELN = VPVBELN
 FOR ALL ENTRIES IN T_T320
 WHERE VK~VTWEG IN S_VTWEG
 AND VK~ERDAT IN S_ERDAT
 AND VP~WERKS = T_T320-WERKS.
ENDFORM. " order_quantity
*& Form Transfer_order_quantity
 text
--> p1 text
<-- p2 text
FORM TRANSFER_ORDER_QUANTITY .
SELECT LK~LGNUM
 LK~TANUM
 LP~VISTA
 INTO TABLE T_LTAK FROM LTAK AS LK
 INNER JOIN LTAP AS LP
 ON LKLGNUM = LPLGNUM
 WHERE LK~KQUIT = 'X'
 AND LK~BDATU IN S_ERDAT
 AND LK~LGNUM IN S_LGNUM.
ENDFORM. " Transfer_order_quantity
*& Form Delivery_QUANTITY
 text
--> p1 text
<-- p2 text
FORM DELIVERY_QUANTITY .
SELECT VBELN WERKS LFIMG FROM LIPS
 INTO TABLE T_LIKP
 FOR ALL ENTRIES IN T_T320
 WHERE WERKS = T_T320-WERKS
 AND ERDAT IN S_ERDAT
 AND VTWEG IN S_VTWEG.
ENDFORM. " Delivery_QUANTITY
*& Form fieldcatalog
 text
--> p1 text
<-- p2 text
FORM FIELDCATALOG .
W_FCAT-COL_POS = '1' .
W_FCAT-FIELDNAME = 'LGNUM' .
W_FCAT-REF_TABNAME = 'T320'.
W_FCAT-REF_FIELDNAME = 'LGNUM' .
APPEND W_FCAT TO T_FCAT.
CLEAR W_FCAT.
W_FCAT-COL_POS = '2' .
W_FCAT-FIELDNAME = 'VTWEG' .
W_FCAT-REF_TABNAME = 'VBAK'.
W_FCAT-REF_FIELDNAME = 'VTWEG' .
APPEND W_FCAT TO T_FCAT.
CLEAR W_FCAT.
W_FCAT-COL_POS = '3' .
W_FCAT-FIELDNAME = 'KWMENG' .
W_FCAT-REF_TABNAME = 'VBAP'.
W_FCAT-REF_FIELDNAME = 'KWMENG' .
*w_fcat-seltext_m = '# of Orders'.
APPEND W_FCAT TO T_FCAT.
CLEAR W_FCAT.
W_FCAT-COL_POS = '4' .
W_FCAT-FIELDNAME = 'VISTA' .
W_FCAT-REF_TABNAME = 'LTAP'.
W_FCAT-REF_FIELDNAME = 'VISTA' .
*w_fcat-seltext_m = '# of Pcs Picked'.
APPEND W_FCAT TO T_FCAT.
CLEAR W_FCAT.
W_FCAT-COL_POS = '5' .
W_FCAT-FIELDNAME = 'LFIMG' .
W_FCAT-REF_TABNAME = 'LIPS'.
W_FCAT-REF_FIELDNAME = 'LFIMG' .
*w_fcat-seltext_m = '# of Pcs Shipped'.
APPEND W_FCAT TO T_FCAT.
CLEAR W_FCAT.
W_FCAT-COL_POS = '6' .
W_FCAT-FIELDNAME = 'TANUM' .
W_FCAT-REF_TABNAME = 'LTAK'.
W_FCAT-REF_FIELDNAME = 'TANUM' .
**w_fcat-seltext_m = '# of Pcs Shipped'.
APPEND W_FCAT TO T_FCAT.
CLEAR W_FCAT.
W_FCAT-COL_POS = '7' .
W_FCAT-FIELDNAME = 'WERKS' .
W_FCAT-REF_TABNAME = 'T320'.
W_FCAT-REF_FIELDNAME = 'WERKS' .
**w_fcat-seltext_m = '# of Pcs Shipped'.
APPEND W_FCAT TO T_FCAT.
CLEAR W_FCAT.
ENDFORM. " fieldcatalog
*& Form display_output
 text
--> p1 text
<-- p2 text
FORM DISPLAY_OUTPUT .
LOOP AT T_T320 INTO TY_T320.
 TY_ITAB-WERKS = TY_T320-WERKS.
 TY_ITAB-LGNUM = TY_T320-LGNUM.
 READ TABLE T_VBAK INTO TY_VBAK WITH KEY WERKS = TY_T320-WERKS.
 IF SY-SUBRC = 0.
 TY_ITAB-VBELN = TY_VBAK-VBELN.
 TY_ITAB-VTWEG = TY_VBAK-VTWEG.
 TY_ITAB-KWMENG = TY_VBAK-KWMENG + ty_itab-kwmeng.
 ENDIF.
 READ TABLE T_LTAK INTO TY_LTAK WITH KEY LGNUM = TY_T320-LGNUM.
 IF SY-SUBRC = 0.
 TY_ITAB-TANUM = TY_LTAK-TANUM.
 TY_ITAB-VISTA = TY_LTAK-VISTA + ty_itab-vista.
 ENDIF.
 READ TABLE T_LIKP INTO TY_LIKP WITH KEY WERKS = TY_T320-WERKS.
 IF SY-SUBRC = 0.
 TY_ITAB-LFIMG = TY_LIKP-LFIMG + ty_itab-lfimg.
 ENDIF.
 APPEND TY_ITAB TO T_ITAB.
ENDLOOP.
Function Module for Displaying Final Output ********
W_LAYOUT-COLWIDTH_OPTIMIZE = 'X'.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
 EXPORTING
 I_CALLBACK_PROGRAM = SY-CPROG
 IS_LAYOUT = W_LAYOUT
 IT_FIELDCAT = T_FCAT[]
 TABLES
 T_OUTTAB = T_ITAB.
ENDFORM. " display_output
*& Form f4_for_variant
 text
--> p1 text
<-- p2 text
FORM F4_FOR_VARIANT .
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
 EXPORTING
 IS_VARIANT = GS_VARIANT
 I_SAVE = X_SAVE
 IMPORTING
 E_EXIT = G_EXIT
 ES_VARIANT = GX_VARIANT
 EXCEPTIONS
 NOT_FOUND = 2.
IF SY-SUBRC = 2.
 MESSAGE ID SY-MSGID TYPE 'S' NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
 IF G_EXIT = SPACE.
 P_VARI = GX_VARIANT-VARIANT.
 ENDIF.
ENDIF.
ENDFORM. " f4_for_variant
*& Form pai_of_selection_screen
 text
--> p1 text
<-- p2 text
FORM PAI_OF_SELECTION_SCREEN .
IF NOT P_VARI IS INITIAL.
 MOVE GS_VARIANT TO GX_VARIANT.
 MOVE P_VARI TO GX_VARIANT-VARIANT.
 CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
 EXPORTING
 I_SAVE = X_SAVE
 CHANGING
 CS_VARIANT = GX_VARIANT.
 GS_VARIANT = GX_VARIANT.
ELSE.
 PERFORM VARIANT_INIT.
ENDIF.
ENDFORM. " pai_of_selection_screen
*& Form variant_init
 text
--> p1 text
<-- p2 text
FORM VARIANT_INIT .
CLEAR GS_VARIANT.
GS_VARIANT-REPORT = G_REPID.
ENDFORM. " variant_init

Query For Purchase A/P Cycle Details

Hi
All export pls. provide me Query for Purchase A/P Cycle Details i.e Vendor Code Vendor Description doc. date posting date po date amount quantity unit price same as Grpo returns and invoice in singal screen
Thanks & Regards

Hi,
What do you mean by Query for Purchase A/P Cycle . All Query for A/P Cycle , you can search in SDN.Any specific unsolved query for you can be posted here.Ok.
Check the details:
1.PO creation
http://e-mory.blogspot.com/2008/01/sap-me21n-create-purchase-order_30.html
2.Goods Receipt
http://e-mory.blogspot.com/2008/02/sap-migo-goods-receipt.html
3.Invoice Verification
http://e-mory.blogspot.com/2007/11/sap-miro-enter-invoice-verification.html
Regards,
Biju K

ABAP query for PI

Hi all,
I created a ABAP query for physical inventory report.
I used the table ISEG and i got the relevant output like material, diff value, batch,PI doc number.
But i cant able to get the difference quantity posted.
How to proceed
Regards
KK

Kishore,
Isn't the quantity found in MENGE (quantity in base unit) or ERFMG (quantity in issue unit)?

Query for following report

Dear All,
 My A/P Invoice entry is as Follows.
 A/P Invoice
 1) Item code (Multiple Items Possible)
 2) Quantity per item
 3) Unit Price per item
 4) Under frieght I entry 3 freight value
 5) Tax Code is selected
 The report required is
 1) A/P Invoice No
 2) A/P Post Date
 3) A/P Documnet date
 4) A/P Vendor Code
 5) A/P Vendor Name
 6) Vendor state ( From Vendor Master date Address)
 7) Vendor Cst no / Vat no / Tin No ( These all are UDF)
 8) A/P Doc total before Discount ( This does not contain frieght value) ( I am able to obtain this from the OPCH-- Max 1099 Amount Field)
 9) A/P Doc total After discount
 10) A/P Feieght Break up.
 11) A/P DOc total + Excise details
 12) A/P Tax Code
 13) A/P Tax Amount
 14) A/P Final Total Value
 The main issue is till point number (8) I can get the query after that the query goes wrong.
 I need a similar query for A/R Invoice also.
 Please advice.

hi aslam,
Try this query,
SELECT T0.DocNum as 'AP Invoice No.',
T0.DocDate as 'Posting Date',
T0.TaxDate as 'Doc. Date',
T0.CardCode as 'Vendor Code',
T0.CardName as 'Vendor Name',
T1.State1,
T2.TaxId1 as 'CST No.',
T2.TaxId11 as 'TIN No.',
T0.Max1099, T0.DocTotal,
T0.TotalExpns,
T0.VatSum
FROM [dbo].[OPCH] T0 INNER JOIN [dbo].[OCRD] T1 ON T0.CardCode = T1.CardCode
INNER JOIN [dbo].[PCH12] T2 ON T0.DocEntry = T2.DocEntry
WHERE T0.DocDate >= '[%0]' and T0.DocDate <= '[%1]'
Whether it solves ur requirement ?
Jeyakanthan

Query for quotes not converted to Sales Orders

Hello,
I am relatively new to SAP B1 (little over a year now) and I am trying to build a query but I have no idea how to approach this one.
I am trying to find Sales Quotes not converted to a Sales Order. Sounds simple but here is where they start getting complicated. I need to specify a date range (normally a year but could be quarterly). Need to specify one or more items, groups, or vendors. Need to display our cost for each item on the quote(s).
Any help on this would be great. I have used the query wizard in the past with some success but this one is getting way out of my comfort zone.
Many thanks to all who have contributed to these discussions. It is nice knowing that I am not the only newbie around.
Keith H

Hi Keith.
Following a little query for your request.
Take note that query return only the ROWS of sales quote which are never converted in a sales order.
It means that if you have a sales quote whit 1 rows and 1000 unit, and you convert the quote in a order for 500 unit, the quote is considered converted in a order and not displayed
The cost is the price set in PRICE LIST 23 as you say in a your previous post.
SELECT
a.DocDate ,
a.DocNum,
a.CardCode,
b.ItemCode,
b.Quantity,
d.ItmsGrpNam,
b.Price as 'QUOTE_PRICE',
e.Price as 'COST'
FROM
inner join QUT1 b on a.DocEntry = b.DocEntry
inner join OITM c on b.ItemCode = c.ItemCode
inner join OITB d on c.ItmsGrpCod = d.ItmsGrpCod
inner join ITM1 e on b.itemcode = e.ItemCode
where
a.DocDate between [%0] and[%1]
and b.TargetType <> '17'
and b.ItemCode Like '%[%2]%'
and e.PriceList = '23'
EDIT:
In your first post you say
Need to specify one or more items, groups, or vendors.
Please explain what you means for
=> one or more items
in this point you can have some problem with the query manager...
Hope that help
--LUCA

Average for Unit Price within a date range????

Howdy BI Gurus,
We're on BI 7.0.
The client has the following report that I neeed to create in BI:
It's Determines the Average Costs for Raw Material Every Quarter:
Item # | Receipt Date| Qty | Unit Cost | Extended Cost | Vendor
200TU | 01/23/07 | 47,349 | .9950 | 47,112.26 | XYZ
200TU | 02/19/07 | 48,796 | .9870 | 48,552.02 | XYZ
200TU | 04/16/07 | 43,978 | .9340 | 43,758.11 | XYZ
Total Sum For Qty = 140,123
Total Sum For Extended Cost = 139,422.39
Average For Unit Cost = .9720
1. How do you calculate the Average for the Unit Cost?
2. How do display the Total Sum ONLY for the Qty && Extended Cost?
I tried the following document:
"How to...Count the Occurances of a Characteristic"
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7e58e690-0201-0010-fd85-a2f29a41c7af
...that was posted on another forum that shows step by step how to create a Counter infoobject and update the transfer rules with a Constant "1" and after creating a CKF in Query Designer and setting up the Exception Aggregation for "Average of All Values" for Ref. Characteristic "Material" to get the average...Unfortunately, it didn't work for me as I just get $0.0.
I'm thinking maybe the directions were for the old BW version.
Any help would be greatly appreciated.
Best Regards,
Osman

This is what I get now when I do an Exception Aggregation on Ref. Char - Material...Look at the last Column titled "Average Unit Price"
Calendar Day Material Individual price in invoice Invoiced quantity Extended Cost Average Unit Price
10/9/2007 17887 $ 14.00 /EA 7,128 EA $ 99,792.00 $ 14.00 /EA
10/22/2007 53093 $ 318.00 /EA 1,920 EA $ 610,560.00 $ 318.00 /EA
10/8/2007 4750MT $ 0.51 /LB 252,000 LB $ 128,088.00 $ 0.51 /LB
10/9/2007 4750MT $ 0.51 /LB 252,000 LB $ 127,638.00 $ 0.51 /LB
10/17/2007 G202 $ 59.40 /EA 6 EA $ 356.40 $ 59.40 /EA
What I want is grup by Material:
Calendar Day Material Individual price in invoice Invoiced quantity Extended Cost
10/9/2007 17887 $ 14.00 /EA 7,128 EA $ 99,792.00
Average Individual price in invoice = $14 (Since there is only 1)
10/22/2007 53093 $ 318.00 /EA 1,920 EA $ 610,560.00
Average Individual price in invoice = $318.00 (Since there is only 1)
1/8/2007 4750MT $ 0.51 /LB 252,000 LB $ 128,520.00
2/9/2007 4750MT $ 0.32 /LB 252,000 LB $ 80,640.00
3/10/2007 4750MT $ 0.24 /LB 252,000 LB $ 60,480.00
4/25/2007 4750MT $ 0.65 /LB 252,000 LB $ 163,800.00
Average Individual price in invoice = (($0.51 + $0.32 + $0.24 + $0.65) / 4) = $0.43
10/17/2007 G202 $ 59.40 /EA 6 EA $ 356.40
Average Individual price in invoice = $59.40 (Since there is only 1)
Hi Kartikey,
I'll try your method tommorrow morning...thank you for your help so far.
I really appreciate it
Best Regards,
Osman
Message was edited by:
 Osman Baig

Need FMS For Unit price

Dear Experts,
Please Find the Attachment and mentioned two fields(Red) and I want Multiply from these Two fields. So please give FMS query for this problem.Kindly give solution ASAP.
Thanks&Regards
Vinoth Raj K

Hi Raj,
Why you need to multiply the Currency Rate to the Unit Price? If you do that option you just multiplying the bp currency and the foreign amount like USDXXX * USDXXX. Does it make sense?
Regards,
Lean

Input Ready Query without unit / currency

HI ,
In my input ready query, it is enabling along with the unit / currency. How to show the input ready query without unit / currency
if I use NODIM() function, it is not possible to creating input ready field.
Please suggest me is there any way to create input ready field without unit / currency.
Thanks and regards
Rajesh

HI Hyma,
1.use the currency / unit field in the filter or drilldown
In this case if the query may have more than 2 fileds which are input ready having differnt unit/ currency, for Ex: Amount = Quantity * Rate
Currency for amount and Rate is INR and for Quantity is Tonnes. if I restrict both INR & TO in filter, in the system it will store both currency and unit for amount, rate and quantity.
HI Andrey,
2. 0CURRENCY or any currency IO that you use in ROWS of query
In this case also, if I use only one type of currency/unit as input ready then it is fine,, but in my query I want to use more then one currency/unit at a time.(As above Example)
Please suggest me how to solve this...
Regards
Rajesh

How to use the same POWL query for multiple users

Hello,
I have defined a POWL query which executes properly. But if I map the same POWL query to 2 portal users and the 2 portal users try to access the same page simultaneously then it gives an error message to one of the users that
"Query 'ABC' is already open in another session."
where 'ABC' is the query name.
Can you please tell me how to use the same POWL query for multiple users ?
A fast reply would be highly appreciated.
Thanks and Regards,
Sandhya

Batch processing usually involves using actions you have recorded. In Action you can insert Path that can be used during processing documents. Path have some size so you may want to only process document that have the same size. Look in the Actions Palette fly-out menu for insert path. It inserts|records the current document work path into the action being worked on and when the action is played it inserts the path into the document as the current work path..

Error while creating a query for my custom infotype

Hi,
I have created a custom infotype with fields currency amount and currency field .
While I am creating a query for it its giving an error
Message no. AQ_AD_HOC221 Error when generating the report(see long text )
I tried to execute the standard program RPUMS40CCI but still I am facing same error .
I have also maintained table T777i for my infotype but still problem exists.
Please help.
P

Hi
Check in PM01

Error while executing a sql query for select

HI All,
ORA-01652: unable to extend temp segment by 128 in tablespace PSTEMP i'm getting this error while i'm executing the sql query for selecting the data.

I am having 44GB of temp space, while executing the below query my temp space is getting full, Expert please let us know how the issue can be resolved..
1. I dont want to increase the temp space
2. I need to tune the query, please provide your recomendations.
insert /*+APPEND*/ into CST_DSA.HIERARCHY_MISMATCHES
(REPORT_NUM,REPORT_TYPE,REPORT_DESC,GAP,CARRIED_ITEMS,CARRIED_ITEM_TYPE,NO_OF_ROUTE_OF_CARRIED_ITEM,CARRIED_ITEM_ROUTE_NO,CARRIER_ITEMS,CARRIER_ITEM_TYPE,CARRIED_ITEM_PROTECTION_TYPE,SOURCE_SYSTEM)
select
REPORTNUMBER,REPORTTYPE,REPORTDESCRIPTION ,NULL,
carried_items,carried_item_type,no_of_route_of_carried_item,carried_item_route_no,carrier_items,
carrier_item_type,carried_item_protection_type,'PACS'
from
(select distinct
c.REPORTNUMBER,c.REPORTTYPE,c.REPORTDESCRIPTION ,NULL,
a.carried_items,a.carried_item_type,a.no_of_route_of_carried_item,a.carried_item_route_no,a.carrier_items,
a.carrier_item_type,a.carried_item_protection_type,'PACS'
from CST_ASIR.HIERARCHY_asir a,CST_DSA.M_PB_CIRCUIT_ROUTING b ,CST_DSA.REPORT_METADATA c
where a.carrier_item_type in('Connection') and a.carried_item_type in('Service')
AND a.carrier_items=b.mux
and c.REPORTNUMBER=(case
when a.carrier_item_type in ('ServicePackage','Service','Connection') then 10
else 20
end)
and a.carrier_items not in (select carried_items from CST_ASIR.HIERARCHY_asir where carried_item_type in('Connection') ))A
where not exists
(select *
from CST_DSA.HIERARCHY_MISMATCHES B where
A.REPORTNUMBER=B.REPORT_NUM and
A.REPORTTYPE=B.REPORT_TYPE and
A.REPORTDESCRIPTION=B.REPORT_DESC and
A.CARRIED_ITEMS=B.CARRIED_ITEMS and
A.CARRIED_ITEM_TYPE=B.CARRIED_ITEM_TYPE and
A.NO_OF_ROUTE_OF_CARRIED_ITEM=B.NO_OF_ROUTE_OF_CARRIED_ITEM and
A.CARRIED_ITEM_ROUTE_NO=B.CARRIED_ITEM_ROUTE_NO and
A.CARRIER_ITEMS=B.CARRIER_ITEMS and
A.CARRIER_ITEM_TYPE=B.CARRIER_ITEM_TYPE and
A.CARRIED_ITEM_PROTECTION_TYPE=B.CARRIED_ITEM_PROTECTION_TYPE
AND B.SOURCE_SYSTEM='PACS'
Explain Plan
==========
Plan
INSERT STATEMENT ALL_ROWSCost: 129 Bytes: 1,103 Cardinality: 1
     20 LOAD AS SELECT CST_DSA.HIERARCHY_MISMATCHES
          19 PX COORDINATOR
               18 PX SEND QC (RANDOM) PARALLEL_TO_SERIAL SYS.:TQ10002 :Q1002Cost: 129 Bytes: 1,103 Cardinality: 1
                    17 NESTED LOOPS PARALLEL_COMBINED_WITH_PARENT :Q1002Cost: 129 Bytes: 1,103 Cardinality: 1
                         15 HASH JOIN RIGHT ANTI NA PARALLEL_COMBINED_WITH_PARENT :Q1002Cost: 129 Bytes: 1,098 Cardinality: 1
                              4 PX RECEIVE PARALLEL_COMBINED_WITH_PARENT :Q1002Cost: 63 Bytes: 359,283 Cardinality: 15,621
                                   3 PX SEND BROADCAST PARALLEL_TO_PARALLEL SYS.:TQ10001 :Q1001Cost: 63 Bytes: 359,283 Cardinality: 15,621
                                        2 PX BLOCK ITERATOR PARALLEL_COMBINED_WITH_CHILD :Q1001Cost: 63 Bytes: 359,283 Cardinality: 15,621
                                             1 MAT_VIEW ACCESS FULL MAT_VIEW PARALLEL_COMBINED_WITH_PARENT CST_ASIR.HIERARCHY :Q1001Cost: 63 Bytes: 359,283 Cardinality: 15,621
                              14 NESTED LOOPS ANTI PARALLEL_COMBINED_WITH_PARENT :Q1002Cost: 65 Bytes: 40,256,600 Cardinality: 37,448
                                   11 HASH JOIN PARALLEL_COMBINED_WITH_PARENT :Q1002Cost: 65 Bytes: 6,366,160 Cardinality: 37,448
                                        8 BUFFER SORT PARALLEL_COMBINED_WITH_CHILD :Q1002
                                             7 PX RECEIVE PARALLEL_COMBINED_WITH_PARENT :Q1002Cost: 1 Bytes: 214 Cardinality: 2
                                                  6 PX SEND BROADCAST PARALLEL_FROM_SERIAL SYS.:TQ10000 Cost: 1 Bytes: 214 Cardinality: 2
                                                       5 INDEX FULL SCAN INDEX CST_DSA.IDX$$_06EF0005 Cost: 1 Bytes: 214 Cardinality: 2
                                        10 PX BLOCK ITERATOR PARALLEL_COMBINED_WITH_CHILD :Q1002Cost: 63 Bytes: 2,359,224 Cardinality: 37,448
                                             9 MAT_VIEW ACCESS FULL MAT_VIEW PARALLEL_COMBINED_WITH_PARENT CST_ASIR.HIERARCHY :Q1002Cost: 63 Bytes: 2,359,224 Cardinality: 37,448
                                   13 TABLE ACCESS BY INDEX ROWID TABLE PARALLEL_COMBINED_WITH_PARENT CST_DSA.HIERARCHY_MISMATCHES :Q1002Cost: 0 Bytes: 905 Cardinality: 1
                                        12 INDEX RANGE SCAN INDEX PARALLEL_COMBINED_WITH_PARENT SYS.HIERARCHY_MISMATCHES_IDX3 :Q1002Cost: 0 Cardinality: 1
                         16 INDEX RANGE SCAN INDEX PARALLEL_COMBINED_WITH_PARENT CST_DSA.IDX$$_06EF0001 :Q1002Cost: 1 Bytes: 5 Cardinality: 1

Query for Unit Commision

Similar Messages

Maybe you are looking for