Code for select query

Hi please help me to write this select query
report i/ps are :bukrs,anlkl,report date,ktansw,budat and posnr
report o/p:belnr,bukrs
bukrs:value is entered in the selection screen
anlkl:optional field in selection screen
report date:fetched and placed in a table
ktansw:can this be directly fetched from table
budat:fetched and placed in a table
posnr:already fetched and placed in the table

ANLAV is a structure. Structures don't hold data. You need to find the associated database table.
Then, you just select the data you want (and don't already have) from the database tables into internal tables defined in your program ....and there you have it.

Similar Messages

Transaction code for SAP query reports

Hi All,
I am trying to create transaction code for sap query report but couldn't go further.
1) Created User group in SQ03
2) Created infoset in SQ03 and assigned that to the user group
3) Created query in SQ01 using the infoset.
I executed the report in SQ01 and it is working fine.
Now I try to create a transaction code in SE93 using the steps mentioned in the following link:
Assign transaction code to SAP Query (created via SQ01)
But when try to execute the report using the transaction code, it is giving error message 'User group xxxxxx is not yet created'
Could any one advice me if I miss something? Or please help me to create this transaction code and transport to production?
Thanks in advance

HI,
based on the thread you've already mentioned:
In SE93, Create a Paramter Transaction
-> Transaction = Start_report
-> In default values, give the below details:
D_SREPOVARI-REPORTTYPE = AQ
D_SREPOVARI-EXTDREPORT = Name of the Query
D_SREPOVARI-REPORT = User Group
So check if the user group is typed correct in SE93 and check also if the user group exits in the system where you are trying to run the transaction.
best regards, Christian

Code for selection screen, urgent

Hi Everyone,
I need code for selection screen.
I have four radio buttons, p1, p2,p3,p4(assume)
If I select second radiobutton, remaining three radiobuttons should be in disable mode and also the information under them should be in disable mode. Give the coding details. Thanks in advance. U will be rewarded.
Regards,
Nagaraju

Hi,
REPORT ZTEST222 .
PARAMETERS : p_add RADIOBUTTON GROUP radi
                         USER-COMMAND radio MODIF ID MOD,
p_disp RADIOBUTTON GROUP radi DEFAULT 'X' MODIF ID pod,
p_chng RADIOBUTTON GROUP radi MODIF ID rad,
p_er_log RADIOBUTTON GROUP radi MODIF ID cod.
SELECT-OPTIONS : s_idn    FOR vendor   MODIF ID mod,
                               s_pcode FOR ws_c_pcode MODIF ID pod.
PARAMETERS: p_plant    LIKE zaw_pol_plan-plant   MODIF ID rad,
             p_zzvend   LIKE zaw_pol_plan-zzvendor   MODIF ID cod.
AT SELECTION-SCREEN OUTPUT.
LOOP AT SCREEN.
IF p_add EQ 'X'.
      IF screen-group1 EQ 'MOD'.
        screen-active = 1.
        MODIFY SCREEN.
ELSE.
         screen-active = 0.
        MODIFY SCREEN.
ENDIF.
IF p_disp EQ 'X'.
      IF screen-group1 EQ 'POD'.
        screen-active = 1.
        MODIFY SCREEN.
ELSE.
         screen-active = 0.
        MODIFY SCREEN.
ENDIF.
IF p_chng EQ 'X'.
      IF screen-group1 EQ 'RAD'.
        screen-active = 1.
        MODIFY SCREEN.
ELSE.
         screen-active = 0.
        MODIFY SCREEN.
ENDIF.
IF p_er_log EQ 'X'.
      IF screen-group1 EQ 'COD'.
        screen-active = 1.
        MODIFY SCREEN.
ELSE.
         screen-active = 0.
        MODIFY SCREEN.
ENDIF.
Pls. reward if useful
    ENDLOOP.
Pls. reward if useful

Question on creation of t-code for SAP query

Hello,
I posted a thread in here back on 06/20/2007 asking for help on creating a t-code for a SAP query. one of the responses that I recieved was
<i>"Sure, all you need to do is get the report name which is generated by the query. You can find this in SQ01, select the query and from the menu, Query, More Functions, Display Report name. Then go to Se93 and create the tcode with this report name."</i>
the report name was AQFKZFINANCE====GL_FRANCE=====.
I created the t-code using this name. I had it transported to my QAS system an now we are getting a error stating that the the program is not found.
When I check in SE38, I can see this program AQA0ZFINANCE====BP_RECON====== in both my development system and my QAS system.
Should I have created in the t-code using the AQA0ZFINANCE====BP_RECON====== instead of the AQFKZFINANCE====GL_FRANCE===== program?
Is there any reason why the program AQFKZFINANCE====GL_FRANCE===== would not be in QAS?
I do not have access to SQ01 in our QAS system so I cannot perfrom the process stated above.
thanks in advance for the help.

Hi,
Please check this thread perhaps it may help.
Re: How to create TCode for Sapquery
Regards,
Ferry Lianto

OPtimizing Performance for Select query on NAST table

Hi All,
   We are fetching a single record from NAST table. The table has around 10 Million Entries.
   The Select Query takes around 5-6 minutes to return.
   We are not using the Primary key completely. We are using only one field of the primary key.
    The field is also a part of the Index but we are not using all the fields in the index as well.
    We need to bring down the time. What can be the solution? I cant see any changes to the code, since its a single query and we cant use the Entire Primary key.
   Would creating an Index on the fields that we are concerned with help in this regard.
   Open to all solutions.
Thanks in Advance,
Imran

Hi,
Please check this thread
http://sap.ittoolbox.com/documents/popular-q-and-a/specifying-the-index-to-be-used-2462
For creating another secondary index in NAST whether basis will approve for this?
aRs

Steps for creating T.code for SAP Query

Hi Friends,
I have developed and SAP Query through SQ01, i want to assign an T.code for that.
What are the steps we have to do in SE93.
Regards
Kumar M

Hi
Create a report pgm with the following code & create a T.Code for this pgm in se93.
data: gv_test type sy-repid.
DATA: GV_USERGROUP TYPE AQADEF-BGNAME VALUE 'FI',
      GV_QUERY TYPE AQADEF-QUNAME VALUE 'ZCON_FI_QUERY',
      GV_RNAME TYPE AQADEF-PGNAME .
CALL FUNCTION 'RSAQ_REPORT_NAME'
EXPORTING
    WORKSPACE        = ''
    USERGROUP        = GV_USERGROUP
    QUERY            = GV_QUERY
IMPORTING
   REPORTNAME       = GV_RNAME
* For the dynamic excution of the called query assisgn GV_RNAME to <gv_test>.
gv_test = GV_RNAME.
submit (gv_test) via selection-screen and return.

Getting deadlock detected while waiting for resource error for select Query.....

Hi all,
i am getting a below error whenever executing the below select query....
some times it will show dead lock detected while waiting for resource and terminated...
some times it executes and gives result..
but all the time it writes an alert to alert log
Plesae suggest how to resolve the issue..........
Thanks in advance
Env: Linux / Oracle 11.2.0.3.3
Error from alert log:
Errors in file /u01/oracle/oracle/diag/rdbms/bdrdb/bdrdb/trace/bdrdb_p017_6076.trc:
ORA-00060: deadlock detected while waiting for resource
ORA-10387: parallel query server interrupt (normal)
Trace file info... bdrdb_p017_6076.trc:
Trace file /u01/oracle/oracle/diag/rdbms/bdrdb/bdrdb/trace/bdrdb_p017_6076.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /u01/oracle/oracle/product/11.2.0/dbhome_1
System name:    Linux
Node name:      bdrdb.cteplindia.com
Release:        2.6.18-308.el5PAE
Version:        #1 SMP Fri Jan 27 17:40:09 EST 2012
Machine:        i686
Instance name: bdrdb
Redo thread mounted by this instance: 1
Oracle process number: 92
Unix process pid: 6076, image: [email protected] (P017)
*** 2013-11-04 23:18:57.915
*** SESSION ID:(423.59970) 2013-11-04 23:18:57.915
*** CLIENT ID:() 2013-11-04 23:18:57.915
*** SERVICE NAME:(bdrdb) 2013-11-04 23:18:57.915
*** MODULE NAME:() 2013-11-04 23:18:57.915
*** ACTION NAME:() 2013-11-04 23:18:57.915
*** 2013-11-04 23:18:57.915
DEADLOCK DETECTED ( ORA-00060 )
[Transaction Deadlock]
Deadlock graph:
                       ---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name          process session holds waits process session holds waits
PS-00000001-00000011        92     423     S             33     128     S     X
BF-2ed08c01-00000000        33     128     S             92     423     S     X
session 423: DID 0001-005C-00081126     session 128: DID 0001-0021-00067D23
session 128: DID 0001-0021-00067D23     session 423: DID 0001-005C-00081126
DEADLOCK DETECTED ( ORA-00060 )
[Transaction Deadlock]
Deadlock graph:
                       ---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name          process session holds waits process session holds waits
PS-00000001-00000011        92     423     S             33     128     S     X
BF-2ed08c01-00000000        33     128     S             92     423     S     X
session 423: DID 0001-005C-00081126     session 128: DID 0001-0021-00067D23
session 128: DID 0001-0021-00067D23     session 423: DID 0001-005C-00081126
Rows waited on:
Session 423: no row
Session 128: obj - rowid = 00021DC1 - AAAh3BAAVAAAQL/AAA
(dictionary objn - 138689, file - 21, block - 66303, slot - 0)
----- Information for the OTHER waiting sessions -----
Session 128:
sid: 128 ser: 46176 audsid: 1836857 user: 102/DBLOCAL
    flags: (0x8000041) USR/- flags_idl: (0x1) BSY/-/-/-/-/-
    flags2: (0x40009) -/-/INC
pid: 33 O/S info: user: oracle, term: UNKNOWN, ospid: 31611
    image: [email protected]
client details:
    O/S info: user: masked, term: masked, ospid: 5924:568
    machine: masked program: Toad.exe
    application name: TOAD background query session, hash value=526966934
current SQL:
    application name: TOAD background query session, hash value=526966934
current SQL:
SELECT DISTINCT B_FP_TEST.TEST_ID
FROM B_FP_TEST,
       B_USER_INFO,
       J_FP_INVESTIGATOR,
       L_TEST_STATUS,
       L_ATMS_TEST_TYPE,
       j_op_test_anml
WHERE     B_FP_TEST.TEST_ID = J_FP_INVESTIGATOR.TEST_ID
       AND B_FP_TEST.TEST_TYPE_ID = L_ATMS_TEST_TYPE.ATMS_TEST_TYPE_ID
       AND B_USER_INFO.B_USER_INFO_ID = J_FP_INVESTIGATOR.INVESTIGATOR_ID
       AND B_FP_TEST.STATUS_ID = L_TEST_STATUS.STATUS_ID
       AND B_FP_TEST.IS_DELETED = :"SYS_B_00"
       AND B_FP_TEST.TEST_NUM NOT IN (:"SYS_B_01", :"SYS_B_02", :"SYS_B_03")
       AND L_ATMS_TEST_TYPE.IS_DELETED = :"SYS_B_04"
       AND J_FP_INVESTIGATOR.is_pi = :"SYS_B_05"
       AND L_TEST_STATUS.STATUS IN (:"SYS_B_06", :"SYS_B_07", :"SYS_B_08")
       AND j_op_test_anml.test_id = B_FP_TEST.TEST_ID
----- End of information for the OTHER waiting sessions -----
*** 2013-11-04 23:18:57.916
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=3, mask=0x0)
----- Error Stack Dump -----
ORA-00060: deadlock detected while waiting for resource
ORA-10387: parallel query server interrupt (normal)
----- SQL Statement (None) -----
Current SQL information unavailable - no cursor.
----- Call Stack Trace -----
calling              call     entry                argument values in hex
location             type     point                (? means dubious value)
More......
Query:
SELECT DISTINCT B_FP_TEST.TEST_ID
FROM B_FP_TEST,
       B_USER_INFO,
       J_FP_INVESTIGATOR,
       L_TEST_STATUS,
       L_ATMS_TEST_TYPE,
       j_op_test_anml
WHERE     B_FP_TEST.TEST_ID = J_FP_INVESTIGATOR.TEST_ID
       AND B_FP_TEST.TEST_TYPE_ID = L_ATMS_TEST_TYPE.ATMS_TEST_TYPE_ID
       AND B_USER_INFO.B_USER_INFO_ID = J_FP_INVESTIGATOR.INVESTIGATOR_ID
       AND B_FP_TEST.STATUS_ID = L_TEST_STATUS.STATUS_ID
       AND B_FP_TEST.IS_DELETED = 0
       AND B_FP_TEST.TEST_NUM NOT IN (1, 2, 99)
       AND L_ATMS_TEST_TYPE.IS_DELETED = 0
       AND J_FP_INVESTIGATOR.is_pi = 1
       AND L_TEST_STATUS.STATUS IN ('Scheduled', 'In-Progress', 'Completed')
       AND j_op_test_anml.test_id = B_FP_TEST.TEST_ID
       AND (   (j_op_test_anml.end_date BETWEEN TO_DATE ('28-Oct-2013') - 1
                                            AND TO_DATE ('04-Nov-2013') + 1)
            OR (j_op_test_anml.start_date BETWEEN TO_DATE ('28-Oct-2013') - 1
                                              AND TO_DATE ('04-Nov-2013') + 1)
            OR (TO_DATE ('28-Oct-2013') BETWEEN j_op_test_anml.start_date
                                            AND j_op_test_anml.end_date)
            OR (TO_DATE ('04-Nov-2013') BETWEEN j_op_test_anml.start_date
                                            AND j_op_test_anml.end_date))
       AND L_ATMS_TEST_TYPE.IS_DELETED = 0
       AND B_FP_TEST.DATASOURCE_ID = 9
Query Exp plan:
Plan hash value: 3398228788
| Id | Operation                                          | Name                | Rows | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |    TQ |IN-OUT| PQ Distrib |
|   0 | SELECT STATEMENT                                   |                     | 1501 |   102K| 1929   (1)| 00:00:24 |       |       |        |      |            |
|   1 | HASH UNIQUE                                       |                     | 1501 |   102K| 1929   (1)| 00:00:24 |       |       |        |      |            |
|   2 |   CONCATENATION                                    |                     |       |       |            |          |       |       |        |      |            |
|   3 |    PX COORDINATOR                                  |                     |       |       |            |          |       |       |        |      |            |
|   4 |     PX SEND QC (RANDOM)                            | :TQ30005            |   241 | 16870 |   800   (1)| 00:00:10 |       |       | Q3,05 | P->S | QC (RAND) |
|* 5 |      HASH JOIN                                     |                     |   241 | 16870 |   800   (1)| 00:00:10 |       |       | Q3,05 | PCWP |            |
|   6 |       PX RECEIVE                                   |                     |   246 | 15990 |   797   (1)| 00:00:10 |       |       | Q3,05 | PCWP |            |
|   7 |        PX SEND HASH                                | :TQ30004            |   246 | 15990 |   797   (1)| 00:00:10 |       |       | Q3,04 | P->P | HASH       |
|* 8 |         HASH JOIN                                  |                     |   246 | 15990 |   797   (1)| 00:00:10 |       |       | Q3,04 | PCWP |            |
|   9 |          PX RECEIVE                                |                     |   573 | 29223 |   793   (1)| 00:00:10 |       |       | Q3,04 | PCWP |            |
| 10 |           PX SEND HASH                             | :TQ30003            |   573 | 29223 |   793   (1)| 00:00:10 |       |       | Q3,03 | P->P | HASH       |
|* 11 |            HASH JOIN                               |                     |   573 | 29223 |   793   (1)| 00:00:10 |       |       | Q3,03 | PCWP |            |
| 12 |             BUFFER SORT                            |                     |       |       |            |          |       |       | Q3,03 | PCWC |            |
| 13 |              PX RECEIVE                            |                     |       |       |            |          |       |       | Q3,03 | PCWP |            |
| 14 |               PX SEND BROADCAST                    | :TQ30000            |       |       |            |          |       |       |        | S->P | BROADCAST |
| 15 |                NESTED LOOPS                        |                     |       |       |            |          |       |       |        |      |            |
| 16 |                 NESTED LOOPS                       |                     |   485 | 20855 |   781   (0)| 00:00:10 |       |       |        |      |            |
| 17 |                  TABLE ACCESS BY GLOBAL INDEX ROWID| J_OP_TEST_ANML      |   485 | 10185 |   296   (0)| 00:00:04 | ROWID | ROWID |        |      |            |
|* 18 |                   INDEX RANGE SCAN                 | IDX$$_2D190001      |   485 |       |     4   (0)| 00:00:01 |       |       |        |      |            |
|* 19 |                  INDEX UNIQUE SCAN                 | FT_TEST_ID_PK       |     1 |       |     0   (0)| 00:00:01 |       |       |        |      |            |
|* 20 |                 TABLE ACCESS BY GLOBAL INDEX ROWID | B_FP_TEST           |     1 |    22 |     1   (0)| 00:00:01 | ROWID | ROWID |        |      |            |
| 21 |             PX BLOCK ITERATOR                      |                     | 70382 |   549K|    11   (0)| 00:00:01 |       |       | Q3,03 | PCWC |            |
|* 22 |              TABLE ACCESS FULL                     | J_FP_INVESTIGATOR   | 70382 |   549K|    11   (0)| 00:00:01 |       |       | Q3,03 | PCWP |            |
| 23 |          BUFFER SORT                               |                     |       |       |            |          |       |       | Q3,04 | PCWC |            |
| 24 |           PX RECEIVE                               |                     |     3 |    42 |     3   (0)| 00:00:01 |       |       | Q3,04 | PCWP |            |
| 25 |            PX SEND HASH                            | :TQ30001            |     3 |    42 |     3   (0)| 00:00:01 |       |       |        | S->P | HASH       |
|* 26 |             TABLE ACCESS FULL                      | L_TEST_STATUS       |     3 |    42 |     3   (0)| 00:00:01 |       |       |        |      |            |
| 27 |       BUFFER SORT                                  |                     |       |       |            |          |       |       | Q3,05 | PCWC |            |
| 28 |        PX RECEIVE                                  |                     |    30 |   150 |     3   (0)| 00:00:01 |       |       | Q3,05 | PCWP |            |
| 29 |         PX SEND HASH                               | :TQ30002            |    30 |   150 |     3   (0)| 00:00:01 |       |       |        | S->P | HASH       |
|* 30 |          TABLE ACCESS FULL                         | L_ATMS_TEST_TYPE    |    30 |   150 |     3   (0)| 00:00:01 |       |       |        |      |            |
| 31 |    NESTED LOOPS                                    |                     |       |       |            |          |       |       |        |      |            |
| 32 |     NESTED LOOPS                                   |                     |     3 |   210 |   329   (1)| 00:00:04 |       |       |        |      |            |
| 33 |      NESTED LOOPS                                  |                     |     3 |   195 |   329   (1)| 00:00:04 |       |       |        |      |            |
|* 34 |       HASH JOIN                                    |                     |     2 |   114 |   325   (1)| 00:00:04 |       |       |        |      |            |
| 35 |        NESTED LOOPS                                |                     |       |       |            |          |       |       |        |      |            |
| 36 |         NESTED LOOPS                               |                     |     6 |   258 |   322   (1)| 00:00:04 |       |       |        |      |            |
| 37 |          PARTITION RANGE SINGLE                    |                     |     6 |   126 |   316   (1)| 00:00:04 |     7 |     7 |        |      |            |
|* 38 |           TABLE ACCESS FULL                        | J_OP_TEST_ANML      |     6 |   126 |   316   (1)| 00:00:04 |     7 |     7 |        |      |            |
|* 39 |          INDEX UNIQUE SCAN                         | FT_TEST_ID_PK       |     1 |       |     0   (0)| 00:00:01 |       |       |        |      |            |
|* 40 |         TABLE ACCESS BY GLOBAL INDEX ROWID         | B_FP_TEST           |     1 |    22 |     1   (0)| 00:00:01 | ROWID | ROWID |        |      |            |
|* 41 |        TABLE ACCESS FULL                           | L_TEST_STATUS       |     3 |    42 |     3   (0)| 00:00:01 |       |       |        |      |            |
|* 42 |       TABLE ACCESS BY INDEX ROWID                  | J_FP_INVESTIGATOR   |     1 |     8 |     2   (0)| 00:00:01 |       |       |        |      |            |
|* 43 |        INDEX RANGE SCAN                            | FI_TEST_ID_PK       |     1 |       |     1   (0)| 00:00:01 |       |       |        |      |            |
|* 44 |      INDEX UNIQUE SCAN                             | L_ATMS_TEST_TYPE_PK |     1 |       |     0   (0)| 00:00:01 |       |       |        |      |            |
|* 45 |     TABLE ACCESS BY INDEX ROWID                    | L_ATMS_TEST_TYPE    |     1 |     5 |     1   (0)| 00:00:01 |       |       |        |      |            |
| 46 |    PX COORDINATOR                                  |                     |       |       |            |          |       |       |        |      |            |
| 47 |     PX SEND QC (RANDOM)                            | :TQ20003            |       |       |            |          |       |       | Q2,03 | P->S | QC (RAND) |
| 48 |      NESTED LOOPS                                  |                     |       |       |            |          |       |       | Q2,03 | PCWP |            |
| 49 |       NESTED LOOPS                                 |                     |    33 | 2310 |   399   (2)| 00:00:05 |       |       | Q2,03 | PCWP |            |
|* 50 |        HASH JOIN                                   |                     |    33 | 2145 |   397   (2)| 00:00:05 |       |       | Q2,03 | PCWP |            |
| 51 |         PX RECEIVE                                 |                     |    78 | 3978 |   393   (1)| 00:00:05 |       |       | Q2,03 | PCWP |            |
| 52 |          PX SEND HASH                              | :TQ20002            |    78 | 3978 |   393   (1)| 00:00:05 |       |       | Q2,02 | P->P | HASH       |
|* 53 |           HASH JOIN                                |                     |    78 | 3978 |   393   (1)| 00:00:05 |       |       | Q2,02 | PCWP |            |
| 54 |            BUFFER SORT                             |                     |       |       |            |          |       |       | Q2,02 | PCWC |            |
| 55 |             PX RECEIVE                             |                     |       |       |            |          |       |       | Q2,02 | PCWP |            |
| 56 |              PX SEND BROADCAST                     | :TQ20000            |       |       |            |          |       |       |        | S->P | BROADCAST |
| 57 |               NESTED LOOPS                         |                     |       |       |            |          |       |       |        |      |            |
| 58 |                NESTED LOOPS                        |                     |    66 | 2838 |   382   (1)| 00:00:05 |       |       |        |      |            |
| 59 |                 PARTITION RANGE SINGLE             |                     |    66 | 1386 |   316   (1)| 00:00:04 |     7 |     7 |        |      |            |
|* 60 |                  TABLE ACCESS FULL                 | J_OP_TEST_ANML      |    66 | 1386 |   316   (1)| 00:00:04 |     7 |     7 |        |      |            |
|* 61 |                 INDEX UNIQUE SCAN                  | FT_TEST_ID_PK       |     1 |       |     0   (0)| 00:00:01 |       |       |        |      |            |
|* 62 |                TABLE ACCESS BY GLOBAL INDEX ROWID | B_FP_TEST           |     1 |    22 |     1   (0)| 00:00:01 | ROWID | ROWID |        |      |            |
| 63 |            PX BLOCK ITERATOR                       |                     | 70382 |   549K|    11   (0)| 00:00:01 |       |       | Q2,02 | PCWC |            |
|* 64 |             TABLE ACCESS FULL                      | J_FP_INVESTIGATOR   | 70382 |   549K|    11   (0)| 00:00:01 |       |       | Q2,02 | PCWP |            |
| 65 |         BUFFER SORT                                |                     |       |       |            |          |       |       | Q2,03 | PCWC |            |
| 66 |          PX RECEIVE                                |                     |     3 |    42 |     3   (0)| 00:00:01 |       |       | Q2,03 | PCWP |            |
| 67 |           PX SEND HASH                             | :TQ20001            |     3 |    42 |     3   (0)| 00:00:01 |       |       |        | S->P | HASH       |
|* 68 |            TABLE ACCESS FULL                       | L_TEST_STATUS       |     3 |    42 |     3   (0)| 00:00:01 |       |       |        |      |            |
|* 69 |        INDEX UNIQUE SCAN                           | L_ATMS_TEST_TYPE_PK |     1 |       |     0   (0)| 00:00:01 |       |       | Q2,03 | PCWP |            |
|* 70 |       TABLE ACCESS BY INDEX ROWID                  | L_ATMS_TEST_TYPE    |     1 |     5 |     1   (0)| 00:00:01 |       |       | Q2,03 | PCWP |            |
| 71 |    PX COORDINATOR                                  |                     |       |       |            |          |       |       |        |      |            |
| 72 |     PX SEND QC (RANDOM)                            | :TQ10003            |       |       |            |          |       |       | Q1,03 | P->S | QC (RAND) |
| 73 |      NESTED LOOPS                                  |                     |       |       |            |          |       |       | Q1,03 | PCWP |            |
| 74 |       NESTED LOOPS                                 |                     |    33 | 2310 |   399   (2)| 00:00:05 |       |       | Q1,03 | PCWP |            |
|* 75 |        HASH JOIN                                   |                     |    34 | 2210 |   397   (2)| 00:00:05 |       |       | Q1,03 | PCWP |            |
| 76 |         PX RECEIVE                                 |                     |    78 | 3978 |   393   (1)| 00:00:05 |       |       | Q1,03 | PCWP |            |
| 77 |          PX SEND HASH                              | :TQ10002            |    78 | 3978 |   393   (1)| 00:00:05 |       |       | Q1,02 | P->P | HASH       |
|* 78 |           HASH JOIN                                |                     |    78 | 3978 |   393   (1)| 00:00:05 |       |       | Q1,02 | PCWP |            |
| 79 |            BUFFER SORT                             |                     |       |       |            |          |       |       | Q1,02 | PCWC |            |
| 80 |             PX RECEIVE                             |                     |       |       |            |          |       |       | Q1,02 | PCWP |            |
| 81 |              PX SEND BROADCAST                     | :TQ10000            |       |       |            |          |       |       |        | S->P | BROADCAST |
| 82 |               NESTED LOOPS                         |                     |       |       |            |          |       |       |        |      |            |
| 83 |                NESTED LOOPS                        |                     |    66 | 2838 |   382   (1)| 00:00:05 |       |       |        |      |            |
| 84 |                 PARTITION RANGE SINGLE             |                     |    66 | 1386 |   316   (1)| 00:00:04 |     7 |     7 |        |      |            |
|* 85 |                  TABLE ACCESS FULL                 | J_OP_TEST_ANML      |    66 | 1386 |   316   (1)| 00:00:04 |     7 |     7 |        |      |            |
|* 86 |                 INDEX UNIQUE SCAN                  | FT_TEST_ID_PK       |     1 |       |     0   (0)| 00:00:01 |       |       |        |      |            |
|* 87 |                TABLE ACCESS BY GLOBAL INDEX ROWID | B_FP_TEST           |     1 |    22 |     1   (0)| 00:00:01 | ROWID | ROWID |        |      |            |
| 88 |            PX BLOCK ITERATOR                       |                     | 70382 |   549K|    11   (0)| 00:00:01 |       |       | Q1,02 | PCWC |            |
|* 89 |             TABLE ACCESS FULL                      | J_FP_INVESTIGATOR   | 70382 |   549K|    11   (0)| 00:00:01 |       |       | Q1,02 | PCWP |            |
| 90 |         BUFFER SORT                                |                     |       |       |            |          |       |       | Q1,03 | PCWC |            |
| 91 |          PX RECEIVE                                |                     |     3 |    42 |     3   (0)| 00:00:01 |       |       | Q1,03 | PCWP |            |
| 92 |           PX SEND HASH                             | :TQ10001            |     3 |    42 |     3   (0)| 00:00:01 |       |       |        | S->P | HASH       |
|* 93 |            TABLE ACCESS FULL                       | L_TEST_STATUS       |     3 |    42 |     3   (0)| 00:00:01 |       |       |        |      |            |
|* 94 |        INDEX UNIQUE SCAN                           | L_ATMS_TEST_TYPE_PK |     1 |       |     0   (0)| 00:00:01 |       |       | Q1,03 | PCWP |            |
|* 95 |       TABLE ACCESS BY INDEX ROWID                  | L_ATMS_TEST_TYPE    |     1 |     5 |     1   (0)| 00:00:01 |       |       | Q1,03 | PCWP |            |
Predicate Information (identified by operation id):
   5 - access("B_FP_TEST"."TEST_TYPE_ID"="L_ATMS_TEST_TYPE"."ATMS_TEST_TYPE_ID")
   8 - access("B_FP_TEST"."STATUS_ID"="L_TEST_STATUS"."STATUS_ID")
11 - access("B_FP_TEST"."TEST_ID"="J_FP_INVESTIGATOR"."TEST_ID")
18 - access("J_OP_TEST_ANML"."START_DATE">=TO_DATE(' 2013-10-27 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND "J_OP_TEST_ANML"."START_DATE"<=TO_DATE(' 2013-11-05
              00:00:00', 'syyyy-mm-dd hh24:mi:ss'))
19 - access("J_OP_TEST_ANML"."TEST_ID"="B_FP_TEST"."TEST_ID")
20 - filter("B_FP_TEST"."DATASOURCE_ID"=9 AND "B_FP_TEST"."IS_DELETED"=0 AND "B_FP_TEST"."TEST_NUM"<>1 AND "B_FP_TEST"."TEST_NUM"<>2 AND
              "B_FP_TEST"."TEST_NUM"<>99)
22 - filter("J_FP_INVESTIGATOR"."IS_PI"=1)
26 - filter("L_TEST_STATUS"."STATUS"='Completed' OR "L_TEST_STATUS"."STATUS"='In-Progress' OR "L_TEST_STATUS"."STATUS"='Scheduled')
30 - filter("L_ATMS_TEST_TYPE"."IS_DELETED"=0)
34 - access("B_FP_TEST"."STATUS_ID"="L_TEST_STATUS"."STATUS_ID")
38 - filter("J_OP_TEST_ANML"."END_DATE">=TO_DATE(' 2013-10-27 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND "J_OP_TEST_ANML"."END_DATE"<=TO_DATE(' 2013-11-05
              00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND (LNNVL("J_OP_TEST_ANML"."START_DATE">=TO_DATE(' 2013-10-27 00:00:00', 'syyyy-mm-dd hh24:mi:ss')) OR
              LNNVL("J_OP_TEST_ANML"."START_DATE"<=TO_DATE(' 2013-11-05 00:00:00', 'syyyy-mm-dd hh24:mi:ss'))))
39 - access("J_OP_TEST_ANML"."TEST_ID"="B_FP_TEST"."TEST_ID")
40 - filter("B_FP_TEST"."DATASOURCE_ID"=9 AND "B_FP_TEST"."IS_DELETED"=0 AND "B_FP_TEST"."TEST_NUM"<>1 AND "B_FP_TEST"."TEST_NUM"<>2 AND
              "B_FP_TEST"."TEST_NUM"<>99)
41 - filter("L_TEST_STATUS"."STATUS"='Completed' OR "L_TEST_STATUS"."STATUS"='In-Progress' OR "L_TEST_STATUS"."STATUS"='Scheduled')
42 - filter("J_FP_INVESTIGATOR"."IS_PI"=1)
43 - access("B_FP_TEST"."TEST_ID"="J_FP_INVESTIGATOR"."TEST_ID")
44 - access("B_FP_TEST"."TEST_TYPE_ID"="L_ATMS_TEST_TYPE"."ATMS_TEST_TYPE_ID")
45 - filter("L_ATMS_TEST_TYPE"."IS_DELETED"=0)
50 - access("B_FP_TEST"."STATUS_ID"="L_TEST_STATUS"."STATUS_ID")
53 - access("B_FP_TEST"."TEST_ID"="J_FP_INVESTIGATOR"."TEST_ID")
60 - filter("J_OP_TEST_ANML"."END_DATE">=TO_DATE(' 2013-11-04 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND "J_OP_TEST_ANML"."START_DATE"<=TO_DATE(' 2013-11-04
              00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND (LNNVL("J_OP_TEST_ANML"."END_DATE">=TO_DATE(' 2013-10-27 00:00:00', 'syyyy-mm-dd hh24:mi:ss')) OR
              LNNVL("J_OP_TEST_ANML"."END_DATE"<=TO_DATE(' 2013-11-05 00:00:00', 'syyyy-mm-dd hh24:mi:ss'))) AND (LNNVL("J_OP_TEST_ANML"."START_DATE">=TO_DATE(' 2013-10-27
              00:00:00', 'syyyy-mm-dd hh24:mi:ss')) OR LNNVL("J_OP_TEST_ANML"."START_DATE"<=TO_DATE(' 2013-11-05 00:00:00', 'syyyy-mm-dd hh24:mi:ss'))))
61 - access("J_OP_TEST_ANML"."TEST_ID"="B_FP_TEST"."TEST_ID")
62 - filter("B_FP_TEST"."DATASOURCE_ID"=9 AND "B_FP_TEST"."IS_DELETED"=0 AND "B_FP_TEST"."TEST_NUM"<>1 AND "B_FP_TEST"."TEST_NUM"<>2 AND
              "B_FP_TEST"."TEST_NUM"<>99)
64 - filter("J_FP_INVESTIGATOR"."IS_PI"=1)
68 - filter("L_TEST_STATUS"."STATUS"='Completed' OR "L_TEST_STATUS"."STATUS"='In-Progress' OR "L_TEST_STATUS"."STATUS"='Scheduled')
69 - access("B_FP_TEST"."TEST_TYPE_ID"="L_ATMS_TEST_TYPE"."ATMS_TEST_TYPE_ID")
70 - filter("L_ATMS_TEST_TYPE"."IS_DELETED"=0)
75 - access("B_FP_TEST"."STATUS_ID"="L_TEST_STATUS"."STATUS_ID")
78 - access("B_FP_TEST"."TEST_ID"="J_FP_INVESTIGATOR"."TEST_ID")
85 - filter("J_OP_TEST_ANML"."END_DATE">=TO_DATE(' 2013-10-28 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND "J_OP_TEST_ANML"."START_DATE"<=TO_DATE(' 2013-10-28
              00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND (LNNVL("J_OP_TEST_ANML"."END_DATE">=TO_DATE(' 2013-11-04 00:00:00', 'syyyy-mm-dd hh24:mi:ss')) OR
              LNNVL("J_OP_TEST_ANML"."START_DATE"<=TO_DATE(' 2013-11-04 00:00:00', 'syyyy-mm-dd hh24:mi:ss'))) AND (LNNVL("J_OP_TEST_ANML"."END_DATE">=TO_DATE(' 2013-10-27
              00:00:00', 'syyyy-mm-dd hh24:mi:ss')) OR LNNVL("J_OP_TEST_ANML"."END_DATE"<=TO_DATE(' 2013-11-05 00:00:00', 'syyyy-mm-dd hh24:mi:ss'))) AND
              (LNNVL("J_OP_TEST_ANML"."START_DATE">=TO_DATE(' 2013-10-27 00:00:00', 'syyyy-mm-dd hh24:mi:ss')) OR LNNVL("J_OP_TEST_ANML"."START_DATE"<=TO_DATE(' 2013-11-05
              00:00:00', 'syyyy-mm-dd hh24:mi:ss'))))
86 - access("J_OP_TEST_ANML"."TEST_ID"="B_FP_TEST"."TEST_ID")
87 - filter("B_FP_TEST"."DATASOURCE_ID"=9 AND "B_FP_TEST"."IS_DELETED"=0 AND "B_FP_TEST"."TEST_NUM"<>1 AND "B_FP_TEST"."TEST_NUM"<>2 AND
              "B_FP_TEST"."TEST_NUM"<>99)
89 - filter("J_FP_INVESTIGATOR"."IS_PI"=1)
93 - filter("L_TEST_STATUS"."STATUS"='Completed' OR "L_TEST_STATUS"."STATUS"='In-Progress' OR "L_TEST_STATUS"."STATUS"='Scheduled')
94 - access("B_FP_TEST"."TEST_TYPE_ID"="L_ATMS_TEST_TYPE"."ATMS_TEST_TYPE_ID")
95 - filter("L_ATMS_TEST_TYPE"."IS_DELETED"=0)

Excellent piece of follow-up on my first suggestion.
I nearly made a comment about how the plan doesn't show Bloom filter pruning either - and then I realised why not. The plan you've shown us comes from Explain Plan with literal values present; the trace file shows bind variables with names that are generated when cursor_sharing is set to force or similar - so the run-time plan and the plan from explain plan are almost guaranteed to be different.
Oracle support will need you to supply the plan you get from trying to run the query and then making a call to dbms_xplan.display_cursor() - dbms_xplan in 10g | Oracle Scratchpad If you do this I think you'll find that the pstart/pstop columns contain entries like :BF0000, and you may even find operations link PX JOIN FILTER CREATE / PX JOIN FILTER USE
A couple of generic notes:
if a query does sufficient work to merit parallel execution, then it's usually better to supply the best possible information to the optimizer, which means using literals rather than bind variables - you could try executing the query with the hint /*+ cursor_sharing_exact */ to stop Oracle from turning your literals into binds; it might be the presence of bind variables that's making the optimizer choose a path that has to include bloom filter pruning in your case.
Where you have the to_date() call you've used a four-digit year - which is a very good thing and helps the optimizer - but it's also a good idea to include an explicit format string as well: with a four-digit year this probably won't make any difference, but it avoids any risk of ambiguity for the optimizer.
I made a comment about the P->S stage and bottlenecks - I spent a couple more minutes looking at the plan, and I see the optimizer has used concatentation: in effect it has run three query blocks one after the other and fed the results to the query co-ordinator - in this case the P->S would make no difference to the end-user response time there's always a final P->S to the coordinator, you just happen to have three of them.
Regards
Jonathan Lewis

Time out problem for select query

I am fetching data from BKPF for my report.
I have written following query.But this query always time out.
SELECT
    BUKRS
    BELNR
    GJAHR
    BLART
    BLDAT
    BUDAT
    MONAT
    XBLNR
    BKTXT
    WAERS
    KURSF
    HWAER
    FROM BKPF
    INTO TABLE I_BKPF
    WHERE BUKRS IN S_BUKRS
     AND BELNR IN S_BELNR
     AND GJAHR IN S_GJAHR
     AND BLART IN S_BLART
     AND BLDAT IN S_BLDAT
     AND BUDAT IN S_BUDAT
     AND MONAT IN S_MONAT
     AND CPUDT IN S_CPUDT
     AND BSTAT = SPACE.
So please suggest me solution.

Hi..
1) Try to make Some of the Fields such as BUKRS , GJAHR as PARAMETERS so that ROWS are restrited mostly.
2) Make fields like BLDAT and BUDAT as OBLIGATORY if possible.
3) And in the SELECT query add the PACKAGE SIZE addition.
<b>Reward if Helpful.</b>

OPtimizing Performance for Select query on huge table

Hi All,
   We are fetching a single record from NAST table. The table has around 10 Million Entries.
   The Select Query takes around 5-6 minutes to return.
   We are not using the Primary key completely. We are using only one field of the primary key.
    The field is also a part of the Index but we are not using all the fields in the index as well.
    We need to bring down the time. What can be the solution? I cant see any changes to the code, since its a single query and we cant use the Entire Primary key.
   Would creating an Index on the fields that we are concerned with help in this regard.
   Open to all solutions.
Thanks in Advance,
Imran

There are sometimes tricks you can use to get it to use the index more efficiently. If you let us know which fields you are using in the SELECT (all of them actually), we might be able to help.
Or are you saying you can't change the code at all?
Please don't create duplicate posts though.
Rob
Message was edited by:
        Rob Burbank

Performance improvement for select query

Hi all,
need to improve performace for the below select query as it is taking long time
SELECT vbeln pdstk
         FROM vbuk INTO TABLE it_vbuk1 FOR ALL ENTRIES IN it_likp
      WHERE vbeln = it_likp-vbeln       AND
            wbstk = 'C' AND "pdstk = ' ' AND
            vbtyp IN gr_delivery AND
            ( fkstk = 'A' OR fkstk = 'B' ) OR
            ( fkivk = 'A' OR fkivk = 'B' ).
Regards,
Kumar

Hi,
    Check if it_likp is sorted on vbeln.
SELECT vbeln pdstk
FROM vbuk INTO TABLE it_vbuk1 FOR ALL ENTRIES IN it_likp
WHERE vbeln = it_likp-vbeln AND
wbstk = 'C' AND
vbtyp IN gr_delivery AND
( ( fkstk = 'A' OR fkstk = 'B' ) OR      <-- check this condition , if ( ) is needed ...
( fkivk = 'A' OR fkivk = 'B' ) ) .
Regards,
Srini.

Alternative for "check select-options" for select query.

hi all,
my report is using a "GET" syntax, followed by "check select-options".
My senior told me to replace the Get syntax with select query.
Now, my program also has dynamic selection screen.
the dynamic selection screen almost has all the fields of database table.
so, what is the way to replace this check select-options while applying select query?
can you tell me how dynamic selection screen fields are populated? are they stored in some internal table?
thanks for help.

HI
Here is some points about LDB.
Logical databases are special ABAP programs that retrieve data and make it available to application programs. The most common use of logical databases is still to read data from database tables by linking them to executable ABAP programs.
However, from Release 4.5A, it has also been possible to call logical databases using the function module LDB_PROCESS. This allows you to call several logical databases from any ABAP program, nested in any way. It is also possible to call a logical database more than once in a program, if it has been programmed to allow this. This is particularly useful for programs with type 1.
Logical databases contain Open SQL statements that read data from the database. You do not therefore need to use SQL in your own programs. The logical database reads the program, stores them in the program if necessary, and then passes them line by line to the application program or the function module LDB_PROCESS using an interface work area
For further on LDB's refer to this link.
[http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9b5e35c111d1829f0000e829fbfe/content.htm]
Hope this will help.
Reward if helpful.
Sumit Agarwal

Standard Match Code for Selection Options with Example

Hi Guys,
             Can anybody tell me Standard Match Code or Search help for Selection Options.
         ex: MBEW-MATNR , MBEW-BWKEY and MBEW-BWTAR. can anybody tell how to keep Search Help or Match Code for the Above Fields in ECC 6.0 with Example
          Very Urgent.
Thanks,
Gopi.

Well Gopi.. as per your requirement no need to use collective search help.
I guess you have three fields in selection-screen,out 3 fields you have two fields contains search help.
Create your user defined search help BWTAR ..
Check the below links for creation search help :
http://help.sap.com/saphelp_46c/helpdata/EN/cf/21ee2b446011d189700000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/41/f6b237fec48c67e10000009b38f8cf/content.htm
Hope you got it.
Thanks
Seshu

Code for selection screen

hi all,
in selectin screen i have to populate two fields VIQMEL-KDAUF(sales order) & VIQMEL-QMNUM( shop visit notification),
here i have to give any of the inputs.like, if i give the SALES ORDER as input, SVN should be retrived& if SVN is given as input SO should be retrived.
depending on the given input the second input also should be retrived and passed to others as input.
can any one send me the code for this..i need it immediately.

Hi,
Tables: viqmel.
Data: begin of it_itab occurs 0,
           ls_qmnum like viqmel-qmnum,
           ls_kdauf like viqmel-kdauf,
        end of it_itab.
select-options: s_qmnum for viqmel-qmnum,
                       s_kdauf for viqmel-kdauf.
select QMNUM KDAUF
           from VIQMEL
           into table it_itab
           where qmnum in s_qmnum
           OR kdauf in s_kdauf.
loop at itab.
write: /it_itab-ls_kdauf, it_itab-ls_qmnum.
endloop.
Reward pts if helpfull

Creating t.code for ABAP query and Transport it TO Production and run it .

Hi Friends
Thanks for ur reply ,
The requirement is that i want to create tcode for abap query and that query can be regenearted ,
in case of regeneration programe name i got answer programame name will be change, i created and modified query but i saw the same programe name ,,, may be it changed when it is trasnported if so then what ??
and also pls give me solution for asiging tcode for query which is going to be regenerated.
thanks and regards
farukh

Dear Farukh,
As we know,
Query is created in Production server and a corresponding program is generated by System.
What we have to do is just to assign the program to the desired transaction code in Development server and transport it.
If you have any doubts please let me know.
Kindly assign points if you find this info usefull.
Regards,
Lijo Joseph

Informatica updates not coming through to DAC for Select Query Ora-01007

I updatee a BI App Workstream to include a few fields, Request Dimension mapplet to be specific.
Informatica changes go just fine and I updated the query used as the select to do my inserts. When I run the task through DAC, I see all my changes except for the user query and it is causing me an 'ORA-01007: variable not in select list' Error because my Select does not match the Bulk insert number of items.
Can anyone suggest where I can look to force my modified query to run as part of the task and not the Original Old User Select query?
Thanks for the help.
Rich

I updatee a BI App Workstream to include a few fields, Request Dimension mapplet to be specific.
Informatica changes go just fine and I updated the query used as the select to do my inserts. When I run the task through DAC, I see all my changes except for the user query and it is causing me an 'ORA-01007: variable not in select list' Error because my Select does not match the Bulk insert number of items.
Can anyone suggest where I can look to force my modified query to run as part of the task and not the Original Old User Select query?
Thanks for the help.
Rich

Code for select query

Similar Messages

Maybe you are looking for