Query meaning

Hello all,
Please help me understanding this query:
T_EINA_EINE is internal table, prepare a new internal table with field VAKEY LIKE KONH-VAKEY and populate data from T_EINA_EINE by placing VAKEY0(10) = lifnr, VAKEY10(18) = matnr, VAKEY28(4) = ekorg, VAKEY32(4) = werks, VAKEY+36(1) = ESOKZ.
Thanks,
Shreekant

Hi,
excute this code .hope u understand your query.
DATA: D1 TYPE STRING,
D2 TYPE STRING.
D1 = 'ABCDEFGH'.
D2 = D1+4(2).
WRITE:/ D1,
D2.
result after execution:
D1 -
> ABCDEFGH
D2 -
> EF.
<i><b>Regards
Debjani
Reward point for helpful answer</b></i>

Similar Messages

  • What does Adhoc query means

    Hello friends,
    The Report with tcode S_ahr_61016359 was persent in sap 4.6 c but now this tcode gives the message that this report was deleted use adhoc query instead in version ECC 6.0.
    can you tell what does this means.
    Regards,
    Vidya.

    hi
    good
    SAP HR Ad-Hoc Query
    One of the key requirements of a Human resources management system is the ability to facilitate decision-making use of the information in the system. The reporting functionality within SAP HR is one of the main reasons why clients have chosen SAP rather than another HRIS - one of our former research articles takes a closer look at the different reporting tools available and how to make most use of them.
    Reporting can become very challenging when the differing needs of many decision-makers - human resources, payroll and benefits professionals, line managers, and executives - must be met. SAP HR has responded to this challenge and offers a variety of access methods designed for the needs of different users. This article focuses on the functionality of Ad-hoc Query, a tool that still isn’t used by all companies who have SAP HR. Some of these organizations are still unfamiliar with the full potential of Ad Hoc query and are afraid to use it. This article has a closer look at how easy it is to use ad hoc query and how this simple but powerful tool can make your reporting so much more efficient and less time consuming.
    AD HOC QUERY AS AN IDEAL TOOL FOR DIFFERENT TYPES OF USERS
    The advantage of Ad Hoc Query is that it enables occasional system users or people with little experience to define their own reports according to their personal requirements in an easy and quick fashion. It is an ideal query tool for anyone who needs to obtain human resource information when and as needed.
    An overview of different types of available HR information (for example Personal data, Addresses, Basic pay, Organizational assignment etc.) is displayed in a list, which includes all the infotypes and the relevant fields, users need to pull the information from. This list is obtained by creating a functional area. Users simply select the information they want by marking checkboxes in the list. Report results can then be formatted to users' needs and preferences; for example the presentation style or the sequence of columns in the report can be changed. Users can create and then format the output of the desired report all in one screen and save the query to run it whenever needed.
    http://www.insightcp.com/res_15.htm
    thanks
    mrutyun^

  • "Last_Analyzed" in SQL Query Means ?

    Hi All,
    Can any one please let me know the Meaning or purpose of "LAST_ANALYZED" from the below Query.For what purpose we use that word and how it will work?
    SELECT table_name,num_rows,last_analyzed FROM ALL_TABLES WHERE table_name like 'PYM%'
    Regards

    952934 wrote:
    The documentation is NOT extremely helpful in this case. I would like to know the answer to this same question, and your answer is more smart alecky than useful. Thanks for nothing.
    What I need to know is what does Oracle mean by "analyzed." Does that mean the last time the table was "touched" for instance, like in a transaction? The last time is was updated? Does that mean certain statistics were collected? If yes, what statistics and where is that information located? Well in fact you have a slightly different question. This is why the answer did fit perfectly to your case.
    And you highjacked a thread that is more than 3 years old.
    Kindly also consider this even older but still valid thread: http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:4347359891525
    Edited by: Sven W. on Aug 15, 2012 5:48 PM

  • Drilldown in BeX Query Designer

    Hello,
    I am new in SAP. I am having problem creating Drill down. I have this report where all the data is Transactional data. So I haven't created any Master Data. So I won't be able to use Navigational Attribute for Drill down purpose and I don't want to use Hierarchy. Is there any possibility of getting the Drill down in BeX Query Designer? Any help will be appreciated.
    Warm Regards,
    Debayan

    Hi Debayan,
    first of all, what is your requirement to create a drill down?
    A drill down in BEx query means showing additional information from report output. There are 3 ways to drill down a query in BEx
    1. Master data-Navigational Attributes
    2. Master data- Hierarchies
    3. Free characteristics
    As you dont have any master data in the report (which is very strange) you can use the additional characteristics provided in the 'Free characteristics' to see how the drill down works in BEx.
    Please share your exact requirement.
    Hope this helps.
    -Swati.

  • Operator in Select query (+)=

    Hi All,
    I am trying to understand what this sql query means.
    SELECT person_id, last_update_date FROM per_addresses WHERE per_addresses.primary_flag(+) = 'Y'
    I dont userstand the per_addresses.primary_flag(+) = 'Y' part .. what does this (+) before equals means.
    Thanks for your help

    Yes, and the relevant section of that document is :-
    You cannot use the (+) operator to outer-join a table to itself, although self joins are valid. For example, the following statement is not valid:
    -- The following statement is not valid:
    SELECT employee_id, manager_id
    FROM employees
    WHERE employees.manager_id(+) = employees.employee_id;

  • How to get sql server performance counters using query?

    Hai i want to see my sql server performance counters like, Full Scans/sec,  Buffer
    Cache Hit Ratio,  Database Transactions/sec, User
    Connections, Average Latch Wait Time (ms), Lock
    Waits/sec, Lock Timeouts/sec, Number
    of Deadlocks/sec, Total Server Memory, SQL
    Re-Compilations/sec, User Settable Query. If any one know how to get it by using query means, please help me.
    Thanks in advance

    Hello,
    Below is query created by Jonathan Kehayias for measuring Perfom counters using DMV sys.dm_os_performance_counter.
    You can download book from below link
    https://www.simple-talk.com/books/sql-books/troubleshooting-sql-server-a-guide-for-the-accidental-dba/
    DECLARE @CounterPrefix NVARCHAR(30)
    SET @CounterPrefix = CASE WHEN @@SERVICENAME = 'MSSQLSERVER'
    THEN 'SQLServer:'
    ELSE 'MSSQL$' + @@SERVICENAME + ':'
    END ;
    -- Capture the first counter set
    SELECT CAST(1 AS INT) AS collection_instance ,
    [OBJECT_NAME] ,
    counter_name ,
    instance_name ,
    cntr_value ,
    cntr_type ,
    CURRENT_TIMESTAMP AS collection_time
    INTO #perf_counters_init
    FROM sys.dm_os_performance_counters
    WHERE ( OBJECT_NAME = @CounterPrefix + 'Access Methods'
    AND counter_name = 'Full Scans/sec'
    OR ( OBJECT_NAME = @CounterPrefix + 'Access Methods'
    AND counter_name = 'Index Searches/sec'
    OR ( OBJECT_NAME = @CounterPrefix + 'Buffer Manager'
    AND counter_name = 'Lazy Writes/sec'
    OR ( OBJECT_NAME = @CounterPrefix + 'Buffer Manager'
    AND counter_name = 'Page life expectancy'
    OR ( OBJECT_NAME = @CounterPrefix + 'General Statistics'
    AND counter_name = 'Processes Blocked'
    OR ( OBJECT_NAME = @CounterPrefix + 'General Statistics'
    AND counter_name = 'User Connections'
    OR ( OBJECT_NAME = @CounterPrefix + 'Locks'
    AND counter_name = 'Lock Waits/sec'
    OR ( OBJECT_NAME = @CounterPrefix + 'Locks'
    AND counter_name = 'Lock Wait Time (ms)'
    OR ( OBJECT_NAME = @CounterPrefix + 'SQL Statistics'
    AND counter_name = 'SQL Re-Compilations/sec'
    OR ( OBJECT_NAME = @CounterPrefix + 'Memory Manager'
    AND counter_name = 'Memory Grants Pending'
    OR ( OBJECT_NAME = @CounterPrefix + 'SQL Statistics'
    AND counter_name = 'Batch Requests/sec'
    OR ( OBJECT_NAME = @CounterPrefix + 'SQL Statistics'
    AND counter_name = 'SQL Compilations/sec'
    -- Wait on Second between data collection
    WAITFOR DELAY '00:00:01'
    -- Capture the second counter set
    SELECT CAST(2 AS INT) AS collection_instance ,
    OBJECT_NAME ,
    counter_name ,
    instance_name ,
    cntr_value ,
    cntr_type ,
    CURRENT_TIMESTAMP AS collection_time
    INTO #perf_counters_second
    FROM sys.dm_os_performance_counters
    WHERE ( OBJECT_NAME = @CounterPrefix + 'Access Methods'
    AND counter_name = 'Full Scans/sec'
    OR ( OBJECT_NAME = @CounterPrefix + 'Access Methods'
    AND counter_name = 'Index Searches/sec'
    OR ( OBJECT_NAME = @CounterPrefix + 'Buffer Manager'
    AND counter_name = 'Lazy Writes/sec'
    OR ( OBJECT_NAME = @CounterPrefix + 'Buffer Manager'
    AND counter_name = 'Page life expectancy'
    OR ( OBJECT_NAME = @CounterPrefix + 'General Statistics'
    AND counter_name = 'Processes Blocked'
    OR ( OBJECT_NAME = @CounterPrefix + 'General Statistics'
    AND counter_name = 'User Connections'
    OR ( OBJECT_NAME = @CounterPrefix + 'Locks'
    AND counter_name = 'Lock Waits/sec'
    OR ( OBJECT_NAME = @CounterPrefix + 'Locks'
    AND counter_name = 'Lock Wait Time (ms)'
    OR ( OBJECT_NAME = @CounterPrefix + 'SQL Statistics'
    AND counter_name = 'SQL Re-Compilations/sec'
    OR ( OBJECT_NAME = @CounterPrefix + 'Memory Manager'
    AND counter_name = 'Memory Grants Pending'
    OR ( OBJECT_NAME = @CounterPrefix + 'SQL Statistics'
    AND counter_name = 'Batch Requests/sec'
    OR ( OBJECT_NAME = @CounterPrefix + 'SQL Statistics'
    AND counter_name = 'SQL Compilations/sec'
    -- Calculate the cumulative counter values
    SELECT i.OBJECT_NAME ,
    i.counter_name ,
    i.instance_name ,
    CASE WHEN i.cntr_type = 272696576
    THEN s.cntr_value - i.cntr_value
    WHEN i.cntr_type = 65792 THEN s.cntr_value
    END AS cntr_value
    FROM #perf_counters_init AS i
    JOIN #perf_counters_second AS s
    ON i.collection_instance + 1 = s.collection_instance
    AND i.OBJECT_NAME = s.OBJECT_NAME
    AND i.counter_name = s.counter_name
    AND i.instance_name = s.instance_name
    ORDER BY OBJECT_NAME
    -- Cleanup tables
    DROP TABLE #perf_counters_init
    DROP TABLE #perf_counters_second
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • SQL query perfomance is bad, Need suggestion on creating proper index

    Hello Team,
    I am executing below query on a 8 Million rows table, This query is taking around 2.5 minutes, Could some one suggest me a some index criteria which can improve my query response time to milli seconds.
    SELECT c4_pvcx0.sy_objectid, c4_pvcx0.sy_objectid, c4_pvcx0.sy_objectid FROM c4_pvcx c4_pvcx0 WHERE c4_pvcx0.c4_az_iosqos = 'C4ir00018}' AND c4_pvcx0.sy_objectid != 'C4vd00F}iD' AND c4_pvcx0.sy_pendoperation != 2 AND (c4_pvcx0.sy_changeorderid = 'SYxf0003Ga' AND c4_pvcx0.sy_version = 1 OR c4_pvcx0.sy_version = 0 AND NOT (c4_pvcx0.sy_objectid IN (SELECT c4_pvcx0.sy_objectid FROM c4_pvcx c4_pvcx0 WHERE c4_pvcx0.sy_changeorderid = 'SYxf0003Ga' AND c4_pvcx0.sy_version = 1))) ORDER BY c4_pvcx0.sy_objectid ASC
    Table definition is
      CREATE TABLE "C4_PVCX"
       (     "SY_OBJECTID" CHAR(10 BYTE) NOT NULL ENABLE,
         "SY_CREATEDDATE" VARCHAR2(24 BYTE) NOT NULL ENABLE,
         "SY_MODIFIEDDATE" VARCHAR2(24 BYTE) NOT NULL ENABLE,
         "SY_COMMITTEDDATE" VARCHAR2(24 BYTE) NOT NULL ENABLE,
         "SY_SEQUENCENUMBER" NUMBER(*,0),
         "SY_CHANGEORDERID" CHAR(10 BYTE) NOT NULL ENABLE,
         "SY_VERSION" NUMBER(*,0),
         "SY_PENDOPERATION" NUMBER(*,0),
         "SY_SNOOKERSEQNUM" NUMBER(*,0),
         "VPN" VARCHAR2(16 BYTE) NOT NULL ENABLE,
         "DOMAIN" VARCHAR2(16 BYTE) NOT NULL ENABLE,
         "SRAZ_BANDWIDTH" NUMBER(*,0),
         "SRZA_BANDWIDTH" NUMBER(*,0),
         "SRBACKUPROLE" VARCHAR2(12 BYTE) NOT NULL ENABLE,
         "SRA_CONSUME_BW" VARCHAR2(5 BYTE) NOT NULL ENABLE,
         "SRZ_CONSUME_BW" VARCHAR2(5 BYTE) NOT NULL ENABLE,
         "SRPRIORITY" NUMBER(*,0),
         "SRUNIPRIORITY" NUMBER(*,0),
         "SRA_PRIMTP" VARCHAR2(44 BYTE) NOT NULL ENABLE,
         "SRZ_PRIMTP" VARCHAR2(44 BYTE) NOT NULL ENABLE,
         "SRNAME" VARCHAR2(64 BYTE) NOT NULL ENABLE,
         "SRDESTSERV" VARCHAR2(32 BYTE) NOT NULL ENABLE,
         "SRCOST" NUMBER(*,0),
         "SREMSADMINSTATUS" VARCHAR2(16 BYTE) NOT NULL ENABLE,
         "SRA_CONSUME_CID" VARCHAR2(5 BYTE) NOT NULL ENABLE,
         "SRZ_CONSUME_CID" VARCHAR2(5 BYTE) NOT NULL ENABLE,
         "RATYPE" VARCHAR2(4 BYTE) NOT NULL ENABLE,
         "RAA_VCI" NUMBER(*,0),
         "RAZ_VCI" NUMBER(*,0),
         "RAA_VPI" NUMBER(*,0),
         "RAZ_VPI" NUMBER(*,0),
         "RA_FRTT" NUMBER(*,0),
         "RAQOS" VARCHAR2(8 BYTE) NOT NULL ENABLE,
         "RAA_FRDISC" VARCHAR2(5 BYTE) NOT NULL ENABLE,
         "RAZ_FRDISC" VARCHAR2(5 BYTE) NOT NULL ENABLE,
         "RAAZ_TDTYPE" VARCHAR2(8 BYTE) NOT NULL ENABLE,
         "RAAZ_SCR" NUMBER(*,0),
         "RAAZ_PCR" NUMBER(*,0),
         "RAAZ_MBS" NUMBER(*,0),
         "RAAZ_CDVT" NUMBER(*,0),
         "RAAZ_MCR" NUMBER(*,0),
         "RAAZ_CDV" NUMBER(*,0),
         "RAAZ_MAXCTD" NUMBER(*,0),
         "RAAZ_CLR" NUMBER(*,0),
         "RAZA_TDTYPE" VARCHAR2(8 BYTE) NOT NULL ENABLE,
         "RAZA_SCR" NUMBER(*,0),
         "RAZA_PCR" NUMBER(*,0),
         "RAZA_MBS" NUMBER(*,0),
         "RAZA_CDVT" NUMBER(*,0),
         "RAZA_MCR" NUMBER(*,0),
         "RAZA_CDV" NUMBER(*,0),
         "RAZA_MAXCTD" NUMBER(*,0),
         "RAZA_CLR" NUMBER(*,0),
         "RAAZ_ICR" NUMBER(*,0),
         "RAAZ_RIF" VARCHAR2(8 BYTE) NOT NULL ENABLE,
         "RAAZ_NRM" NUMBER(*,0),
         "RAAZ_RDF" VARCHAR2(8 BYTE) NOT NULL ENABLE,
         "RAAZ_ADTF" NUMBER(*,0),
         "RAAZ_TRM" VARCHAR2(8 BYTE) NOT NULL ENABLE,
         "RAAZ_TBE" NUMBER(*,0),
         "RAAZ_CDF" VARCHAR2(4 BYTE) NOT NULL ENABLE,
         "RAZA_ICR" NUMBER(*,0),
         "RAZA_RIF" VARCHAR2(8 BYTE) NOT NULL ENABLE,
         "RAZA_NRM" NUMBER(*,0),
         "RAZA_RDF" VARCHAR2(8 BYTE) NOT NULL ENABLE,
         "RAZA_ADTF" NUMBER(*,0),
         "RAZA_TRM" VARCHAR2(8 BYTE) NOT NULL ENABLE,
         "RAZA_TBE" NUMBER(*,0),
         "RAZA_CDF" VARCHAR2(4 BYTE) NOT NULL ENABLE,
         "C4PVC_ID" VARCHAR2(40 BYTE) NOT NULL ENABLE,
         "C4AZ_UPC" VARCHAR2(4 BYTE) NOT NULL ENABLE,
         "C4ZA_UPC" VARCHAR2(4 BYTE) NOT NULL ENABLE,
         "C4AZ_CAST" VARCHAR2(12 BYTE) NOT NULL ENABLE,
         "C4ZA_CAST" VARCHAR2(12 BYTE) NOT NULL ENABLE,
         "C4AZ_QOSINDEX" NUMBER(*,0),
         "C4ZA_QOSINDEX" NUMBER(*,0),
         "SRPROFILE" CHAR(10 BYTE) NOT NULL ENABLE,
         "SRNODE" CHAR(10 BYTE) NOT NULL ENABLE,
         "SRNETWORK" CHAR(10 BYTE) NOT NULL ENABLE,
         "SRA_TP" CHAR(10 BYTE) NOT NULL ENABLE,
         "SRZ_TP" CHAR(10 BYTE) NOT NULL ENABLE,
         "SRSOID" CHAR(10 BYTE) NOT NULL ENABLE,
         "C4_AZ_IOSQOS" CHAR(10 BYTE) NOT NULL ENABLE,
         "C4_ZA_IOSQOS" CHAR(10 BYTE) NOT NULL ENABLE
    Currently i have below indexes on this table.
      CREATE UNIQUE INDEX  "C4_PVCX_IDX" ON "PRFT1"."C4_PVCX" ("SY_OBJECTID", "SY_VERSION")
      CREATE UNIQUE INDEX    "C4_PVCX CR" ON "PRFT1"."C4_PVCX" ("SY_CHANGEORDERID", "SY_OBJECTID", "SY_VERSION")
      CREATE INDEX "C4_PVCX_CD" ON "PRFT1"."C4_PVCX" ("SY_COMMITTEDDATE")
    Execution Plan
    Plan hash value: 1884930072
    | Id  | Operation           | Name       | Rows  | Bytes | Cost (%CPU)| Time
    |
    |   0 | SELECT STATEMENT    |            |   795 | 30210 | 73650   (5)| 00:14:44
    |
    |   1 |  SORT ORDER BY      |            |   795 | 30210 | 73650   (5)| 00:14:44
    |
    |*  2 |   FILTER            |            |       |       |            |
    |
    |*  3 |    TABLE ACCESS FULL| C4_PVCX    | 15909 |   590K| 73646   (5)| 00:14:44
    |
    |*  4 |    INDEX UNIQUE SCAN| C4_PVCX_CR |     1 |    24 |     3   (0)| 00:00:01
    |
    Predicate Information (identified by operation id):
       2 - filter("C4_PVCX0"."SY_VERSION"=0 AND  NOT EXISTS (SELECT /*+ */ 0
                  FROM "PRFT1"."C4_PVCX" "C4_PVCX0" WHERE "C4_PVCX0"."SY_VERSION"=1
    AND
                  "C4_PVCX0"."SY_OBJECTID"=:B1 AND "C4_PVCX0"."SY_CHANGEORDERID"='SY
    xf0003Ga
                  ') OR "C4_PVCX0"."SY_VERSION"=1 AND "C4_PVCX0"."SY_CHANGEORDERID"=
    'SYxf000
                  3Ga')
       3 - filter("C4_PVCX0"."C4_AZ_IOSQOS"='C4ir00018}' AND
                  "C4_PVCX0"."SY_PENDOPERATION"<>2 AND
                  "C4_PVCX0"."SY_OBJECTID"<>'C4vd00F}iD')
       4 - access("C4_PVCX0"."SY_CHANGEORDERID"='SYxf0003Ga' AND
                  "C4_PVCX0"."SY_OBJECTID"=:B1 AND "C4_PVCX0"."SY_VERSION"=1)
    Statistics
              0  recursive calls
              0  db block gets
         296336  consistent gets
         294809  physical reads
              0  redo size
            466  bytes sent via SQL*Net to client
            480  bytes received via SQL*Net from client
              1  SQL*Net roundtrips to/from client
              1  sorts (memory)
              0  sorts (disk)
              0  rows processedThanks & Regards
    Satish
    Edited by: Satish Kumar Ballepu on May 16, 2009 2:54 AM

    before index creation. check "OR" condition in your query.
    that query means below code
    AND    ((c4_pvcx0.sy_changeorderid = 'SYxf0003Ga'AND c4_pvcx0.sy_version = 1)
                                                    OR  (c4_pvcx0.sy_version = 0)  --> rerturn rows  "sy_version=0" without sy_changeorderid condition"
            AND NOT ( c4_pvcx0.sy_objectid IN (
                                               SELECT c4_pvcx0.sy_objectid
                                               FROM   c4_pvcx c4_pvcx0
                                               WHERE  c4_pvcx0.sy_changeorderid = 'SYxf0003Ga'
                                               AND    c4_pvcx0.sy_version = 1
    {code}
    is it right?                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Group by result in query

    how can i see the group by result in a query means show result also in groups i hope u guys understand wat i meann

    Mushy wrote:
    how can i see the group by result in a query means show result also in groups i hope u guys understand wat i meannJust select the GROUP BY columns. Not sure what you are exactly looking for. Lets say you have a table of employee and you want count of employee on each department you can do this
    SELECT deptno, count(*) FROM emp GROUP BY deptnoHere i have selected deptno and grouped by deptno.
    Is this what you are looking for?

  • ABAP Query Transport request related

    Hi,
    I have created a Abap query,
    1) User group
    2)Infoset
    3) Query
    But when i transport the request in to Quality, I can see only Infoset, not able to see User group and query which i created in the
    Development
    Please suggest, is this std behaviour or is anything missed
    Rgds,
    Jai

    Thanks to all,
    I just created TR with new package for user group and included ifoset and query in the same TR
    and imported, issue is resolved
    But my question is,where we can utilize below help material, I have spent much time to understand below given explaination and finally left without any conclusion
    Short text
    SAP Query: Transport tool
    Description
    The report RSAQR3TR handles all tasks concerning the transport of queries, InfoSets and user groups.
    General information
    Queries, InfoSets and user groups are stored in the table AQDB. This table is client-specific. For the transport of queries, InfoSets and user groups, there is a special client-independent transport table called TAQTS. You can carry out transports either
    ·     from a client (source client) of an SAP system to another client (target client) in the same SAP system or
    ·     from a client (source client) of an SAP system (source system) to a client (target client) in another SAP system (target system).
    In both cases, you have to perform similar actions.
    The objects to be transported must first be copied from the source client using an export from the table AQDB into the transport table TAQTS. At the same time, a transport request is created for the transport system that includes all entries created by the export from table TATQS (transport dataset). The name of this transport request conforms to the transport system naming conventions (sysKnnnnnn) and is included in the export log. The transport dataset is stored in the table TAQTS under a key which matches the name of the transport request.
    If you are transporting within one SAP system (from one client to another), you can import the transport dataset from the target client. The name of the transport request to use for this purpose is that specified during the export, since it should match the key of the transport dataset in the table TAQTS. With this import, the transport dataset is read from the transport table TAQTS and inserted into the table AQDB, where extensive checks ensure that there are no inconsistent statuses in the table AQDB.
    If you are transporting from one SAP system to another, you must first use the transport system to release and export the transport request generated by the export. This transports the transport dataset from the transport table TAQTS into the target system. Then, you can import from the target client of the target system, as described above.
    The transport datasets generated by exports in the transport table TAQTS are not deleted after successful import unless this is explicitly requested. Therefore, you can import a transport dataset several times (when copying a functional area to several different clients, for example).
    This report handles exports (generation of transport datasets), imports (reading of transport datasets) as well as the management (display and deletion) of transport datasets.
    As transport action, you must specify one of the values EXPO (export), IMPO (import), SHOW (display transport dataset) or DELE (delete transport dataset).
    Transport action EXPO (exports)
    If you select the 'Test only' parameter when exporting (no blank characters), the system determines only those queries, InfoSets and user groups that would be selected according to the selections for transport described below and generates an appropriate log. A transport dataset is not generated in the table TAQTS. This allows you to check whether a selection really includes the queries, InfoSets and user groups to be transported.
    With exports, there are four different options for selecting objects (user groups, InfoSets, queries) to be transported. These are 'Transport of user groups', 'Transport of InfoSets', 'Transport of InfoSets and queries' and 'Transport of queries'. You must choose exactly one of these transport types.
    In each case, you can also define an import option depending on the transport type. This allows you to determine how the transport dataset is inserted in the table AQDB of the target client during a later import.
    The import options, each of which has an abbreviated syntax,
    are as follows:
    REPLACE  or R
    MERGE    or M
    GROUP=ug or G=ug    (ug = name of a user group)
    UNASSIGN or U
    If you use the transport type 'Transport of user groups', all user groups are transported according to the select option 'user groups' and the selected import option. The import options REPLACE and MERGE are allowed.
    If you use the transport type 'Transport of InfoSets', all InfoSets are transported according to the select option 'InfoSet' and the selected import option. The import options REPLACE, MERGE, GROUP=ug and UNASSIGN are allowed.
    If you select the transport type 'Transport of InfoSets and queries', all InfoSets are transported according to the select option 'InfoSets' and the selected import option. The import options REPLACE and MERGE are allowed. Also, all queries are transported for each functional area selected, according to the select option 'queries'. In this case, the user groups of the queries are irrelevant and only the import option REPLACE is allowed.
    This transport type allows you to transport a modified InfoSet and all the associated queries.
    For the transport type 'Transport of queries', all queries are transported according to the select option 'User groups' and the select option 'Queries' as well as the selected import option. The import options REPLACE and GROUP=ug are allowed.
    The export log displays which user groups, which InfoSets and which queries are transported, as well as the import options used.
    Transporting a user group
    Transporting a user group means transporting all members of the group from the source client. However, the InfoSet assignment to the user group in the source client is NOT transported.
    The import option REPLACE first deletes all members of the group in the target client and then enters the members from the source client.
    The import option MERGE leaves all members of the group assigned in the target client and adds the members of the group from the source client.
    Entering a new member in a user group in the target client is possible only if a user master record exists.
    In the target client, the assignment of InfoSets to this user group remains.
    Transporting an InfoSet
    Transporting an InfoSet means transporting the InfoSet and the InfoSet assignment to user groups in the source client.
    Importing an InfoSet is possible only if the same logical database exists in the target client. Extensive checking is also performed to ensure that there are no inconsistencies between the InfoSet and the logical database.
    The import option REPLACE first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries dependent on the InfoSet. The InfoSet is then transported to the target client and the assignment of the InfoSet to user groups is copied from the source client, if user groups also exist in the target client.
    The import option GROUP=ug first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries referring to the InfoSet. The InfoSet is then transported to the target client and assigned to the user group ug of the target client, if such a user group exists.
    The import option MERGE leaves the assignment of the InfoSet to user groups in the target client and transports it to the target client. It then copies the assignment of the InfoSet to user groups from the source client if user groups also exist in the target client.
    The import option UNASSIGN first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries referring to the InfoSet. The InfoSet is then transported to the target client. No assignment of the InfoSet to user groups is performed.
    Transporting a query
    Transporting a query means only the query itself is transported.
    Importing a query is possible only if a corresponding user group (see below) and a corresponding InfoSet exist in the target client and if the InfoSet is assigned to the user group. To demonstrate the effect of the import options, suppose that the query has the name QU and belongs to the user group BQ in the source client.
    The import option REPLACE overwrites the query QU of the user group BQ in the target client if the user group exists.
    The import option GROUP=ug overwrites the query QU of the user group UG in the target client if the user group exists. In this case, the query is explicitly assigned to a user group in the target client. This target user group may be differnet from the user group in the source client.
    Transport action IMPO (imports)
    If you choose the 'Test only' parameter with imports, only a test import is performed. This means that the system performs checks as for a real import and generates an import log. The import log contains information on the locks that have to be set. With a test import, you can check whether a transport dataset can be imported without any problem and which changes it would make in the table AQDB of the target client. A test import itself never makes changes in the table AQDB of the target client.
    All transport datasets are imported according to the select option 'transport request'. In this case, the system outputs a detailed log of all checks carried out and all changes made in the table AQDB.
    If you select the parameter 'Delete after successful import', the transport dataset in the table TAQTS is deleted after the import of each transport dataset if no errors occur during the import.
    Transport action SHOW (display)
    All transport datasets included in the transport table TAQTS are output with name (also the name of the transport request) and contents in the form of an overview.
    Transport action DELE (delete)
    All transport datasets are deleted according to the select option 'transport request'. To avoid unintentional deletion, the select option 'transport request' must contain values, meaning that the transport action DELE is not performed if this select option is empty.
    Transport of ABAP Query
    I am involved in this upgrade project to 4.7 
    The users are not able to find any reports (in QA System) which were there before the upgrade in SQ01. But they can see them in production which is not yet upgraded. They want me to copy all the reports to the QA system now....I dont have any idea how to do that. 
    I remember a similar problem upgrading to 4.6C from 4.5B ...... 
    Take a look at OOS note 672784. 
    You can transport queries between systems in SQ02 (hit the lorry button) or run program RSAQR3TR. 
    You download the infosets, queries etc into a file and load them into whichever system you wish.
    Just wanted to share my experience of transporting queries:
    I needed to move a user group, 2 infosets and 3 queries from a 4.6 system to a 4.7 system. 
    When I tried doing this via the SQ* transactions I did not get the import/export option, so instead ran RSAQR3TR. 
    Step 1. Run RSAQR3TR in 'old' system. Select EXPORT and specify the objects to be transported. 
    (System includes these in an automatically created transport request) 
    Step 2. Release this transport and request it be transported to 'new' system. 
    (This results in the entries being populated in transport table AQTDB in 'new' system). 
    Step 3. Run RSAQR3TR in 'new' system. Select IMPORT and tick the Overwrite checkbox. Specify the transport number in the field labelled 'dataset with imports'. 
    (RSAQR3TR gives the message that stuff has been imported OK). 
    Step 4. In my example I still couldn't find the queries, so ran RSAQR3TR one more time, this time specifying 'Copy Standard Area -> Global Area'. 
    (Now my queries etc were available in new system). 
    Perhaps there are better ways, but after 1.5 days of struggling I was glad to get this far.  
    regards,
    Jai

  • Wat is ad-hoc query designer

    wat is adhoc query and how to make adhoc query.

    Hi Viswanath,
    Ad hoc query means dynamic query ( on demand basis)where your reporting needs are dynamic.
    Check this link:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/08/965b423be8de54e10000000a155106/frameset.htm
    Also check:
    Ad hoc Query Designer
    Ad-Hoc Query Designer
    Ad-hoc Query's
    assign points if useful ***
    Thanks,
    Raj

  • Where is the data coming from in query

    Hi,
    When we run a query are we getting the data from source system?
    Or the cube in Bw?
    CAn somebody clarify this for me?
    And if i have a query which invloves A hierarchy,is the query execution time going to be more?
    Or because the hierarchy is master data it does not effect the query execution time?
    Thanks.
    Haarika.

    The OLAP cache is a performance aid.  A query will look in the OLAP cache to see if the data has already been retrieved from the database already, and if it has been, and all other criteria for using the cache are met, the query will get the data from the cache rather than having to read the database.  Deleting the data in the cube will invalidate the cache for that query, meaning the query must go to the cube, and surprise, surprise, find no data. Any time the cube gets changed, the cache will be invalidated.

  • What is SQL Query

    Dear all,
    what is meant by SQL Query?
    I have a report which is directly in production and not in development.its a user created program.
    some one said that it is SQL query.
    What is meant by it ?
    Is there any name for that SQL query?
    If yes,how can I find it?

    Hi,
      SQL Query means select statement u r getting the data from the database table.
    Standard SQL
    SQL (Structured Query Language) is a largely standardized language for accessing relational databases.  It can be divided into three areas:
    ·         Data Manipulation Language (DML)
    Statements for reading and changing data in database tables.
    ·         Data Definition Language (DDL)
    Statements for creating and administering database tables.
    ·         Data Control Language (DCL)
    Statements for authorization and consistency checks.
    Each database has a programming interface that allows you to access the database tables using SQL statements.  The SQL statements in these programming interfaces are not fully standardized. To access a specific database system, you must refer to the documentation of that system for a list of the SQL statements available and their correct syntax.
    The Database Interface
    To make the R/3 System independent of the database system with which you use it despite the differences in the SQL syntax between various databases, each work process on an application server has a database interface. The R/3 System communicates with the database by means of this interface.  The database interface converts all of the database requests from the R/3 System into the correct Standard SQL statements for the database system. To do this, it uses a database-specific component that shields the differences between database systems from the rest of the database interface.  You choose the appropriate layer when you install the R/3 System.
    There are two ways of accessing the database from a program - with Open SQL or Native SQL.
    Open SQL
    Open SQL statements are a subset of Standard SQL that is fully integrated in ABAP. They allow you to access data irrespective of the database system that the R/3 installation is using. Open SQL consists of the Data Manipulation Language (DML) part of Standard SQL; in other words, it allows you to read (SELECT) and change (INSERT, UPDATE, DELETE) data.
    Open SQL also goes beyond Standard SQL to provide statements that, in conjunction with other ABAP constructions, can simplify or speed up database access. It also allows you to buffer certain tables on the application server, saving excessive database access. In this case, the database interface is responsible for comparing the buffer with the database. Buffers are partly stored in the working memory of the current work process, and partly in the shared memory for all work processes on an application server. Where an R/3 System is distributed across more than one application server, the data in the various buffers is synchronized at set intervals by the buffer management. When buffering the database, you must remember that data in the buffer is not always up to date. For this reason, you should only use the buffer for data which does not often change. You specify whether a table can be buffered in its definition in the ABAP Dictionary. 
    Native SQL
    Native SQL is only loosely integrated into ABAP, and allows access to all of the functions contained in the programming interface of the respective database system. Unlike Open SQL statements, Native SQL statements are not checked and converted, but instead are sent directly to the database system. When you use Native SQL, the function of the database-dependent layer is minimal. Programs that use Native SQL are specific to the database system for which they were written. When writing R/3 applications, you should avoid using Native SQL wherever possible. It is used, however, in some parts of the R/3 Basis System - for example, for creating or changing table definitions in the ABAP Dictionary.
    The ABAP Dictionary
    The ABAP Dictionary, part of the ABAP Workbench, allows you to create and administer database tables.  Open SQL contains no statements from the DDL part of Standard SQL. Normal application programs should not create or change their own database tables. 
    The ABAP Dictionary uses the DDL part of Open SQL to create and change database tables. It also administers the ABAP Dictionary in the database.  The ABAP Dictionary contains metadescriptions of all database tables in the R/3 System. Only database tables that you create using the ABAP Dictionary appear in the Dictionary. Open SQL statements can only access tables that exist in the ABAP Dictionary.
    Authorization and Consistency Checks
    The DCL part of Standard SQL is not used in R/3 programs. The work processes within the R/3 System are logged onto the database system as users with full rights.  The authorizations of programs or users to read or change database tables is administered within the R/3 System using the R/3 authorization concept.  Equally, transactions must ensure their own data consistency using the R/3 locking concept.  For more information, refer to Authorization Concept and Programming Database Updates.
    Plzz reward points if it helps.
    Edited by: manjari kotta on Dec 18, 2007 7:29 AM

  • New Selection Parameter in existing query

    Dear All,
    Can anyone tell how to add additional selection parameters to an existing query ?
    Regards

    Mahesh,
      Query means Is it ABAP Query.
    If it is ABAP query there are 2 ways.
    You can create at infoset level :  In sq02 enter your infoset name press change button.press shift+ F8  there you can find the "Selections"   tab ,press.In that you can find creat button press.
    Enter name of the parameter name .Here you will find 2 radio buttons
    1. Select-options 2. parameters
    select the radio button whichever you want  press enter.
    In net screen give "Description"  "Selection text"   and there you will find 3 formats for parameters.
    1. Type   --if your parameter is your own defined ex : type c  length 12
    2.  like --if it is database field structure Ex: mara-matnr. 
    enter any one.enter & save.
    Pls. reward points for if it is useful.

  • Hierarchical tree query

    dear all,
    plz can you explain to me what is this query mean
    plz i need it piece by piece
    rg_emps := Create_Group_From_Query('rg_emps','select 1, level,last_name, NULL, to_char(employee_id) '||' from employees '   ||'connect by prior employee_id = manager_id ' ||'start with job_id = ''AD_PRES''');i exactly need this part
    select 1, level, last_name, null
    how could you select null (oooooooh )
    plz help & advice

    hi
    here is an example:
    select -1 , level , ename , null , to_char(empno)
    from emp start with mgr is null
    connect by prior empno = mgror
    select 1 , level , ename , null , to_char(empno)
    from emp start with mgr is null
    connect by prior empno = mgrsarah
    Edited by: QGIRCO on Jan 17, 2010 10:27 PM

  • Hi all, I need help please to run few query one after the other...

    I understood I should do it with procedures? is it the simplest way?
    I don't know PLSQL and it was quite difficult for me to try learn it alone.
    there is a simplest way? or a good guide that able to help me?
    thanks a lot,

    Hi,
    Here's an example of a SQL*Plus script.
    Use any text editor to create a file (let's call it aug_6.sql) that contains all the statements you want to execute in order, like this:
    --      *****  Begin aug_6.sql  *****
    CREATE SEQUENCE rownum_incrementing INCREMENT BY 1 START WITH 1;
    CREATE SEQUENCE increment_order_num INCREMENT BY 1 START WITH 1000;
    Insert into orders_main(order_num,order_date,sapak_num,status) values (increment_order_num.nextval, sysdate, '12','new3');
    Insert into orders_details(row_num,order_num,item_num,quantity) values
    (rownum_incrementing.NextVal,
    ( select max(order_num) from orders_main) ,'14','40');
    Insert into delivery_main
    values (increment_del_num.nextval
    ,(select max(order_num) from orders_main)
    , sysdate
    , (select sapak_num from orders_main where order_num = ( select max(order_num) from orders_main)));
    --      *****  End aug_6.sql  *****Note that I made a lot of changes in what you posted, because there seemed to be a lot of mistakes. (See list below.)
    Once you have saved the file, you can run it in SQL*Plus by referring to the full path name of the file:
    SQL> @c:\aaa\bbb\aug_6This is very useful if you have to do the exact same thing more than once (for example, if you are going to create the same sequences and INSERT the same data in your development database, then in your test database, and finally in your production database).
    Here are a few things for you to watch:
    (a) "Query" means "SELECT statement". Use "SQL Statement" if you're talking about any kind of SQL command (including CREATE SEQUENCE and INSERT).
    (b) Every SQL statement must end with a semicolon (;) or slash (/).
    (c) Make sure single-quotes always occur in pairs.
    (d) Make sure parentheses occur in pairs, every "(" followed by a ")".
    (e) Don't use strings to refer to numbers, or vice cersa. For example, if the columns item_num and quantity in the table orders_dtails are NUMBERs, then give them NUMBER values (without quotes) like 14 and 40, not string values like '14' and '40'.
    (f) As part of a larger statement, you can simply use
    SYSDATE
    instead of the scalar sub-query
    (SELECT SYSDATE FROM dual)

Maybe you are looking for