SAP Query

Step-by-Step Tutorials • • • • • • • • • • •
What is SAP Query? Purpose and Advantages of SAP Query?

Configuration for SAP Query
Create transaction for SAP-Query Creating Ad Hoc query (HCM related infoset query) Developing SAP Query for Task List Data Extraction Transport of SAP Query objects Setting the Expiry date in SAP Query SAP Query for getting hourly background job status Building an SAP Query using ABAP Code

Development of Basic List Query using SAP Query
Working with infosets/User Groups/Query in detail

What is SAP Query? Purpose and Advantages of SAP Query?
SAP Query is SAP’s tool to define and execute once own reports without knowing ABAP programming language. Let us see the key topics to explore SAP Query. Topic # 1 Topic What is Query? Purpose of Query. 2 3 4 Advantages of Query Infosets/UserGroups/Query in Detail Practical session covering important working models - I Practical session covering important models-II Various Lists and Background Scheduling In this document we shall cover Topic#1. What is SAP query and why do we need queries? Many times a need arises for SAP Users and Functional Consultants to generate quick reports without getting any ABAP coding done – time taken to complete the coding in development, transport and test it in QA system and then transport to production – is sometimes too long. In such cases, SAP query is a tool provided by SAP for generating these kinds of reports. Purpose

  

The SAP Query application is used to create reports not already contained in the default. It has been designed for users with little or no knowledge of the SAP programming language ABAP. SAP Query offers users a broad range of ways to define reports and create different types of reports such as basic lists, statistics, and ranked lists. These outputs can include lists on screens in table format, ALV grids, downloadable spreadsheets, and downloadable flat files. The internal report generator creates an ABAP program corresponding to the definition of the list.

Features: The SAP Query comprises five components:  Queries  InfoSet Query  Infosets  User Groups  Translation/Query Classic reporting- the creation of lists, statistics and ranked lists- are covered by the InfoSet Query and Queries components. Other components’ range of functions cover the maintenance of Infosets, the administration of user groups and also the translation of texts created in the SAP Query. All data required by a user for a report can be read from various tables. To define a report, you first have to enter individual texts, such as titles, and select the fields and options, which determine the report layout. In the WYSIWYG (What You See Is What You Get) mode, you can edit the lists using Drag & Drop and various toolbars. Overview: The following sections describes the individual SAP Query components and provides general information about query areas, transport and authorizations Menu Path à SAP Query à Queries à SAP Query à Infosets Used For Maintaining Queries Maintaining Infosets Transaction Code SQ01 SQ02 SQ03 SQ07

à SAP Query à User Groups Maintaining User Groups à Translation à Query Language Comparison

Query Components The Queries component is used by end users to maintain queries. You can carry out the following tasks:  Execute Queries and Generate Lists  Define Queries  Change Queries Infosets Components  InfoSets are special views of data sources.  An InfoSet describes which fields of a data source can be reported on in queries.  InfoSets are assigned to user groups.  End-users are able to work only with those InfoSets that are relevant to their particular area, as designated by the role or user group that they are assigned to.  Eg: Vendor master data can be important in purchasing as well as in accountancy. The relevant InfoSet is assigned to both roles/user groups. This means that queries based on this InfoSet can be copied and executed by both groups. User Groups Components 1.
2. The User Groups component is used to maintain user groups. The system administrator uses it to set up the work environment for end-users. Every user assigned to the user group is able to execute the query. Users are not allowed to modify queries from other user groups, although they may, under certain circumstances, copy and execute


Translation/Query Component  A great deal of text is generated when defining queries, InfoSets, and user groups.  The SAP Query displays these texts in the language that you chose when you logged on to the SAP system.  You can compare the text languages using the component Translation/Query.  A related text in one or more additional languages is made available for each of the texts created when defining the query.

Query Areas A query area contains a set of query objects (queries, InfoSets, and user groups) that are discrete and consistent. There are the following query areas:  Standard area  Global area Standard Area 1.Client specific 2.Query objects are not attached to the Workbench Organizer Advantage :-End users can develop queries (ad-hoc reports) in their own client that are not meant for use in the rest of the system. Global Area 1. Cross client 2. Query objects are attached to workbench organizer Advantage:-The global query area is well suited for centrally developing queries meant for use and distribution throughout the system. Authorizations End-users, system administrators, and translators must all be assigned the appropriate authorizations allowing them to work with the SAP Query. In order to give individual users targeted, specific rights, the following options are available:  Roles/user groups  Authorizations Steps to create a Query Step Description TCODE

 Infoset Query  Queries  Quick viewer SAP Query Step-by-step procedure in configuring SAP Query SAP R/3 Query tools (SAP Query) are based on the following four main components: • • • • Query Areas Query Groups InfoSets Administrative Decisions (Company-specific) Configuration of the Query tools is done in the following manner: • • • • Create Query Groups Assign Users to Query Groups Create InfoSets Assign each InfoSet to a Query Group. Create Query Groups • Go to Transaction SQ03.1 2 3 Create a infoset or functional area Assignment of user group to infoset Creation of query based on infoset SQ02 SQ03 SQ01 Tools for Queries The following are the tools to manage. create and change queries. .

enter the name of the Query Group in the User Group field and click on CREATE . Now in the main screen.• Ensure that you are in the correct SAP Query area by navigating to Environment à Query Areas • • Select the “Standard Area (Client-specific).

Assign Users to Query Groups • Click on the “Assign Users and InfoSets” button • Enter the SAP User-Ids of all the users you wish to include in the test group. . • User Group ZSAPTECH_GRP is created. Click on SAVE to save your entries.• Enter the description of the User Group in the next popup that appears.

Create InfoSets • • Go to transaction SQ02 Ensure that you are in the correct SAP Query area by navigating to Environment à Query Areas • Enter the name of the InfoSet you wish to create and click on CREATE. .

.• Enter the title and the logical database on the popup screen that appears. We have used the LDB F1S (Flight bookings related) for our demo purpose.

As seen on the screen. • • Expand the tree on the left hand side to view the fields in each table. the left side of the screen shows the tables and the fields. The right side displays the field groups. Now we need to assign fields to the field groups. . These field groups will display in the SAP Query tool during reporting. Please note that only the fields that are included here will be available for field selection in the SAP Query Tool that uses this infoSet as a data source.• Change InfoSet screen appears.

. • Attach each InfoSet to a Query Group • • Go to transaction SQ02 Enter the InfoSet name created above and click on “User Group Assignment” button. • Now generate the InfoSet by clicking on GENERATE.• Select the field group on the right side and then drag and drop the fields from the left side to this field group. When all the required fields are added. click on SAVE.

sort text for your transaction 3) Choose radio button 5.• Select the query group “ZSAPTECH_GRP” from the above list and click on SAVE. . Create transaction for SAP-Query 1) Open transaction SE93 2) Put object name . Transaction with parameter.

4) Default value for transaction ‘START_REPORT’ 5) In bellow default value section insert default value SREPOVARI-REPORTTYPE = AQ "Parameter indicating Abap Query D_SREPOVARI-REPORT = ZY_CS_ALLSLS "Query User group D_SREPOVARI-EXTDREPORT= ZY_SLS_MST_001 "Query name .

6) Save the transaction. .

.8) Execute the transaction.

Go to Tcode SQ03.for analytical reports The first step in the process of creating an Ad-Hoc query is to create a Functional Area.Creating Ad Hoc query (HCM related infoset query) The InfoSet Query is a useful tool for maintaining queries within the SAP Query and is suitable for developing queries and for ad-hoc reporting. Function area provides special views of logical databases. They determine which fields of a logical database can be evaluated in queries. percentages etc Ranked List .reports with statistical functions such as Averages. the name Ad-Hoc Query is used instead of InfoSet Query. A special feature is the Human Resources (HR) component. Ad-Hoc query provides three different kinds of reports: • • Basic List . When InfoSet Query is used in HR for ad-hoc reporting.Simple reports • Statistics . . InfoSet Query is suitable for reporting in all areas of the SAP R/3 system.

.Select Query areas Menu->Environment->Query areas Select the radio button ‘Global area’.

Select User group as ‘zdemo_user’ (Create Z user group) Click on ‘CREATE’ button.Click on ‘Choose’ Create user group Here you specify the users who should be authorized to run the query. .Go to the menu path Environment => User Group or SQ03 à Give a user group name in the screen. Specify the sap logins of the users whom you want to authorize for using the functional area and click on the Create button. A user group is always associated with a Functional Area. .

Pass short description click SAVE Go to Environment menu select INFOSET or go for tcode (SQ02) Create Infoset with Z like ‘zdemo_infoset’ .

. (demo) Select radio button Logical database ‘PNP or PNPC’ .Click on create button Name as ‘Shortdesc’.

Click on Continue button Open ‘Basic personal data’ Select infotype which u need (like above screen short) Click on continue button .

Click on save and Click on generate button (red button) Go back to main screen Click on ‘Role/User group assignment’ tab .

. .. Query ‘zdemo_01’ (Create zname) Click on ‘create’ button Select ‘infoset’ click on continue.(zdem_user) Save it and back.... Go to tcode for SQ01..Select assigned table check box with User group which u already created.

.. Back.Pass title as Shortdesc.(demo for pa infotype) Save..(the fields you required as Selection screen fields and the fields you need as Output fields) ....... Click on ‘Infoset Query’ button Select selection screen field and Output fields...

Select output check box with right click –select output-only value.. Select fields from which u already given info types .

Click on Execute button (F8)..Finally click on save button Click on continue. Back. Click on continue ready for you REPORT ......

Rate Routing (R) Procedure: Follow the procedure step by step: Transaction Code Menu path Create new Quick view Write the appropriate name of query SQVI Tools>Utilities>SQVI . system will populate the following window.Developing SAP Query for Task List Data Extraction Purpose: To create an SAP query to extract task list data from system. Scope: All task lists pertaining to Production and Planning. Master Recipe (2). Routing (N). complete the details with right information .QuickViewer After you click on create button.

Once you have done with above steps you will get “Choose Data Source” screen. Here in the following step you need to connect different tables properly in order to get task list data.

We are starting with MAPL (Assignment of Task Lists to Materials) table. Similarly, we need to take following tables in order to get the appropriate information. PLKO (Task list – header) PLPO (Task list - operation/activity) PLAS (Task list - selection of operations/activities) CRHD (Work Center Header) CRTX (Text for the Work Center or Production Resource/Tool) MARA (General Material Data) MAKT (Material Descriptions)

Between PLPO and CRHD, the default link is with field OBJTY. You need to delete this link and create with PLPO-ARBID and CRHD-OBJID. For this click on ARBID in PLPO table and drag the cursor towards OBJID in CRHD table. Afterwards it should like

After you finish with above activities the screen will look like



.MARA MATNR MAKT MATNR In the following steps. mainly you need to select which fields you want to see in selection screen and which one in output.

you want to see following fields in Selection Screen o o o Material Plant Task List Type And following fields in output o o Material Material Description . For example.Similarly select all those fields from table enlisted which you want to see in Selection and Display screen.

Material. Group Counter. you can select/deselect additional fields in Quick viewer: Initial screen It’s better to arrange Sort Sequence in order to get proper operation number in output for a combination of Group.o o o o o o o o o o o o o o o o o o o o o o o o Plant Group Group Counter Task List Description Usage Status From Lot Size UoM To Lot Size UoM Operation/Activity Work center Work center description Operation short Text Operation Base Quantity UoM Standard value1 UoM for Std value1 Standard value2 UoM for Std value2 Standard value3 UoM for Std value3 Setup Group Key Setup Group Category Note: As per your requirement. and Plant. .

.Check and Save the Query. Now it’s the time to see the result of efforts that you have put in to develop this query. So execute the transaction.

and the Result of your efforts is Transport of SAP Query objects By Shiva Kumar Tirumalasetty. Deloitte Consulting India Pvt Ltd .

2. all the options come up for transporting the queries. The transport action is performed based on the radio button selected on the screen. From Transaction SQ02/SQ03->Environment->Transports: On the next screen. . By using the standard program ‘RSAQR3TR’ By using the transport option available on the application bar in Transactions SQ02 or SQ03.ABAP Queries can be transported to different clients by the following two ways: 1.

The transports are to be made in the following order: 1. 3. all the options come up for transporting the queries. followed by the Infoset and then the Queries. . By using the standard program ‘RSAQR3TR’: Execute the standard program RSAQR3TR On the next screen. 4. The transport action is performed based on the radio button selected on the screen. 2. The User Group is to be transported first. User Group transport Infoset transport Infoset and Query transport Queries transport The transports are to be made in the specified order.

check the expiry date of that query from the custom table and generate an error message if the query is expired or work as per the code in the infoset if it’s not expired.Once the query is transported or uploaded in the destination system in the method specified above. Design Logic: 1. the same can be used there for displaying the data fetched from the database.e. 2. . Maintain a custom table with two fields – query name and query expiry date. Setting the Expiry date in SAP Query Business Requirement: The client wants to maintain expiry dates to each and every SAP queries that are running in production. The expired query will not be allowed to run in production. Design a custom function module which will collect the current SAP query name at run time (i. during query execution).

3. For more details on user group. Put that custom function module in the infosets of all the queries. . infoset and query name. Explanations: Step 1: Create a Z-table ZQUERY_EXPIRE along with a table maintenance generator. Step 2: Maintain query names along with their expiry dates in the Z-table ZQUERY_EXPIRE via SM30. Keep all the executable codes of the infosets in the ‘ELSE’ part of the sy-subrc check. refer to table AQLQCAT.

* If the query expires. SPLIT v_user_grp2 AT c_fill INTO v_query_name1 v_rest. qnum TYPE aqs_quname. v_user_grp2 = v_user_grp1+12(14).Step 3: Design a custom function module ZQUERY_EXP_CHECK with an exception QUERY_EXPIRED (Query has expired). SELECT qnum exp_date FROM zquery_expire INTO TABLE i_query WHERE qnum EQ v_query_name. v_query_name1(14) TYPE c. v_rest(14) TYPE c. exp_date TYPE datum. ENDIF. generate the error message IF wa_query-exp_date LT sy-datum. v_sycprog = sy-cprog. v_user_grp2(14) TYPE c. ENDLOOP. ENDFUNCTION. i_query TYPE STANDARD TABLE OF ty_query INITIAL SIZE 0. MESSAGE e000(zbasis_msg) RAISING query_expired. v_user_grp1(30) TYPE c. MESSAGE i002(zbasis_msg). v_query_name TYPE aqs_quname. FUNCTION zquery_exp_check. CONSTANTS: c_fill TYPE c VALUE '='. . v_query_name = v_query_name1. DATA: v_sycprog LIKE sy-cprog. don't do anything ELSE. *"--------------------------------------------------------------*"*"Local Interface: *" EXCEPTIONS *" QUERY_EXPIRED *"--------------------------------------------------------------TABLES: zquery_expire. END OF ty_query. TYPES: BEGIN OF ty_query. v_user_grp1 = v_sycprog+4(26). * If the expiary date is today or yet to come. LOOP AT i_query INTO wa_query. DATA: wa_query TYPE ty_query.

Test: Suppose today’s date is 20/03/2009. Here we’ve added the following code in all the infosets of the 3 queries maintained in the custom table. Scenario 2: Execute the query QRY_TEST3 (expiry date is equal to the current date) from SQ01. IF sy-subrc <> 0. MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4. CALL FUNCTION 'ZQUERY_EXP_CHECK' EXCEPTIONS query_expired = 1 OTHERS = 2. Scenario 1: Execute the query BEJ_QRY_TEST1 (expiry date is less than the current date) from SQ01.03. The expiry date of the query QRY_TEST3 is today (20/03/2009). The expiry date of the query BEJ_QRY_TEST1 was 18. Execute. WRITE: /5 'Hello1'.2009 (as maintained in the Z-table). . ELSE. the following error message will be generated. ENDIF.Step 4: Call this custom function module from the START-OF-SELECTION code sections of all the infosets of the queries that are maintained in the custom table ZQUERY_EXPIRE.

SAP Query for getting hourly background job status This SAP query is designed to get the hourly background job status updates. Assign user ids to this user group.Execute. which are running in production. . create one user group ZPROD_BEJ (Jayanta Bej's User Group). b. a. Using t-code SQ03. Step 1: Create user group. the actual code of the infoset will be executed.

a. Using t-code SQ02. b. Add two selection criterion S_JOBNAM (Job Name) & S_STRTDT (Start Date) and one parameter P_ENDTIM (Time) in the Selections tab. create one infoset BATCH_JOBLIST_REPORT with the direct read from the table TBTCO and including key field only. .Step 2: Create infoset.

.Details: S_JOBNAM. Details: P_ENDTIM. Details: S_STRTDT.

SDLSTRTTM type TBTCO-SDLSTRTTM. JOBNAME type TBTCO-JOBNAME. DATA: begin of gt_TBTCO2 occurs 0. In the DATA section.c. SDLSTRTDT type TBTCO-SDLSTRTDT. DATA: end of gt_TBTCO. ENDTIME type TBTCO-ENDTIME. SDLSTRTTM type TBTCO-SDLSTRTTM. Go to Code tab. DATA: end of gt_TBTCO1. DATA: begin of gt_TBTCO occurs 0. DATA: begin of gt_TBTCO1 occurs 0. write the following code: select JOBNAME SDLSTRTDT SDLSTRTTM ENDTIME STATUS from TBTCO into corresponding fields of table gt_tbtco3 where jobname in s_jobnam and status = 'P'. DATA: end of gt_TBTCO2. JOBNAME type TBTCO-JOBNAME. In the START-OF-SELECTION section. . ENDTIME type TBTCO-ENDTIME. SDLSTRTDT type TBTCO-SDLSTRTDT. ENDTIME type TBTCO-ENDTIME. STATUS type TBTCO-STATUS. d. FLAG1(1). DATA : gt_tbtco3 like gt_tbtco occurs 0 with header line. stat(15). JOBNAME type TBTCO-JOBNAME. SDLSTRTDT type TBTCO-SDLSTRTDT. DATA : gt_tbtco4 like gt_tbtco occurs 0 with header line. FLAG2(1). stat(15). refresh gt_tbtco[]. status(15). SDLSTRTTM type TBTCO-SDLSTRTTM. write the following code: DATA : FLAG(1).

endif. else. gt_tbtco4[] = gt_tbtco[]. sort gt_tbtco by JOBNAME SDLSTRTTM. status = gt_tbtco-status. gt_tbtco1-stat = 'Scheduled'. when 'S'. endat. append gt_tbtco1. case status. gt_tbtco1-stat = 'Suspended'. append gt_tbtco1. gt_tbtco1-stat = 'Released'. when 'P'. append gt_tbtco1. MOVE-CORRESPONDING gt_tbtco to gt_tbtco1. flag = 'X'. else. if ( gt_tbtco-SDLSTRTTM le P_ENDTIM ) .clear gt_tbtco[]. clear gt_tbtco1. gt_tbtco1-stat = 'Cancelled'. when 'R'. when 'Y'. Loop at gt_tbtco. sort gt_tbtco by JOBNAME SDLSTRTTM. append gt_tbtco1. gt_tbtco1-stat = 'Released'. when 'A'. if gt_tbtco-status = 'F' . gt_tbtco1-stat = 'Cancelled'. when 'Z'. gt_tbtco1-stat = 'Active'. if flag = 'X'. check sy-subrc = 0. select JOBNAME SDLSTRTDT SDLSTRTTM ENDTIME STATUS from TBTCO into corresponding fields of table gt_tbtco where jobname in s_jobnam and SDLSTRTDT in s_strtdt. . gt_tbtco1-stat = 'Released'. else. clear gt_tbtco1. elseif gt_tbtco-status = 'F' and gt_tbtco-SDLSTRTTM ge P_ENDTIM. endif. gt_tbtco1-stat = 'Active'. clear gt_tbtco1. at new jobname. gt_tbtco1-stat = 'Released'. delete gt_tbtco where ENDTIME < P_ENDTIM and ( status = 'F' or status = 'A' ). endcase. if ( gt_tbtco-SDLSTRTTM le P_ENDTIM ) .

flag2 = 'X'. append gt_tbtco2. if flag1 <> 'X' and flag2 <> 'X'. else. clear gt_tbtco2. if sy-subrc = 0. append gt_tbtco2. read table gt_tbtco3 with key jobname = s_jobnam-low. clear gt_tbtco2. clear status. clear gt_tbtco2. else. move-corresponding gt_tbtco4 to gt_tbtco2. append gt_tbtco2. gt_tbtco2-jobname = s_jobnam-low. endif. read table gt_tbtco4 with key jobname = s_jobnam-low. if gt_tbtco4-status = 'F'. endif. move-corresponding gt_tbtco3 to gt_tbtco2. CLEAR FLAG.clear gt_tbtco1. gt_tbtco2-stat = 'Canceled'. sort gt_tbtco1 by jobname. flag2 = 'X'. clear gt_tbtco2. endif. endloop. endif. gt_tbtco2-stat = 'Not Scheduled'. if sy-subrc = 0.flag2. read table gt_tbtco1 with key jobname = s_jobnam-low. append gt_tbtco2. if sy-subrc = 0. endif. * Display List of Cases to be Cancelled CALL FUNCTION 'RS_COMPLEX_OBJECT_EDIT' EXPORTING object_name = 'RESULTS' changing object = GT_TBTCO2[] EXCEPTIONS OBJECT_NOT_SUPPORTED = 1 OTHERS = 2. Loop at s_jobnam. gt_tbtco2-stat = 'Finished'. if not gt_tbtco2[] is Initial. endif. . gt_tbtco2-stat = 'Scheduled'. clear : flag1. else. move-corresponding gt_tbtco1 to gt_tbtco2. endif. endloop. sort gt_tbtco3 by jobname. flag1 = 'X'. endif.


. The following report will be displayed. Now we execute the query. the date should be equal to current date and time should be current time and should be done as follows: Now selecting the variant JOBLIST (JOB LIST STATUS).ZUUBI_REPLACEMENT_BILLING_01 ZUBC_DELETE_APP_LOGS SAP_ARCH_RETHIST SAP_ARCH_PAYLOTS SAP_ARCH_RETLOTS SAP_APURG_MDR1 Put all these job names in the select option for job name. In the variant. execute the query.

e. 4. 3. PNP Using some programs . Using table join Directly reading from tables Using logical databases (LDB) e. 2 PM. Building an SAP Query using ABAP Code There are 4 different ways to write SAP queries – depending on the approach of data retrieval strategy: 1. 2.g.This is the status update of all the listed background jobs for the hour 14 i.

Create InfoSet by using t-code SQ02: 2. we’ll demonstrate building SAP query using 2nd method (Direct read of table). 1.Here in this document. Press ‘Create’ button. .

.Press enter. Press ‘Code’. 3. Press enter.

connid TYPE s_conn_id. Write the following code in this section. END OF ty_flight. Select the ‘DATA’ coding section. carrname TYPE s_carrname. * Type for taking data from tables SFLIGHT and SCARR TYPES: BEGIN OF ty_flight. currcode TYPE s_currcode.3. seatsocc TYPE s_seatsocc. i_fldcat TYPE slis_t_fieldcat_alv. fldate TYPE s_date. TYPE-POOLS: slis. . carrid TYPE s_carr_id. i_flight TYPE STANDARD TABLE OF ty_flight INITIAL SIZE 0. 4. seatsmax TYPE s_seatsmax. wa_fldcat TYPE slis_fieldcat_alv. * Internal table and work area declaration DATA: wa_flight TYPE ty_flight. TABLES: scarr.

* Populate the field catalogs wa_fldcat-col_pos = 1. * Retrieve data from tables SFLIGHT and SCARR SELECT m1~carrid m1~connid m1~fldate m1~seatsmax m1~seatsocc m2~carrname m2~currcode INTO TABLE i_flight FROM sflight AS m1 INNER JOIN scarr AS m2 ON m1~carrid = m2~carrid. Now go to START-OF-SELECTION section And write the following code in START-OF-SELECTION section to display a few field data in ALV grid display report format. CLEAR: wa_flight. .5.

CLEAR: wa_fldcat. wa_fldcat-col_pos = 5. MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4. wa_fldcat-col_pos = 4. APPEND wa_fldcat TO i_fldcat. APPEND wa_fldcat TO i_fldcat. wa_fldcat-fieldname = 'SEATSOCC'. ENDIF. wa_fldcat-col_pos = 2. 7. Generate the InfoSet. wa_fldcat-col_pos = 7.wa_fldcat-fieldname = 'CARRID'. wa_fldcat-seltext_l = 'Local currency of airline'. CLEAR: wa_fldcat. * ALV grid display report CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY' EXPORTING it_fieldcat = i_fldcat TABLES t_outtab = i_flight EXCEPTIONS program_error = 1 OTHERS = 2. wa_fldcat-fieldname = 'CARRNAME'. wa_fldcat-fieldname = 'CONNID'. wa_fldcat-seltext_l = 'Airline carrier ID'. wa_fldcat-fieldname = 'CURRCODE'. CLEAR: wa_fldcat. 6. wa_fldcat-seltext_l = 'Airline name'. CLEAR: wa_fldcat. . wa_fldcat-fieldname = 'SEATSMAX'. wa_fldcat-col_pos = 6. APPEND wa_fldcat TO i_fldcat. APPEND wa_fldcat TO i_fldcat. wa_fldcat-seltext_l = 'Maximum capacity'. wa_fldcat-fieldname = 'FLDATE'. Now create a user group. wa_fldcat-seltext_l = 'Flight date'. wa_fldcat-col_pos = 3. CLEAR: wa_fldcat. CLEAR: wa_fldcat. EXIT. wa_fldcat-seltext_l = 'Occupied seats'. APPEND wa_fldcat TO i_fldcat. IF sy-subrc <> 0. APPEND wa_fldcat TO i_fldcat. CLEAR: wa_fldcat. wa_fldcat-seltext_l = 'Flight connection Id'. APPEND wa_fldcat TO i_fldcat.

I’ve assigned two users in my user group.8. . Now assign the user group ZUGRP_BEJ to the InfoSet ZINFOSET_BEJ.

9.Save it. Now create the query. .

Now execute the query from SQ01. . The following selection screen will appear where we need to put the flight date.10.

2.Enter the flight date as 11. we’ll get the following ALV grid display report.2008 and execute the query. Go to Transaction SQ01. The title bar shows you the query group you are currently in. SAP Query Step-by-step procedure in creating a simple list using SAP Query 1.06. .

enter the name of the query you want to create and press CREATE. The InfoSets of the user group ZSAPTECH_GRP is displayed. 5. .3. Ensure that you are in the correct SAP Query area by navigating to Environment à Query Areas 4. In the field “Query”.

Select the InfoSet ZSAPTECH_IS and click ENTER. Enter the title and any other notes that are required. 7. . Click on “Next screen” button as shown in the above screenshot.6.

All the fields in the selected Field groups appear in this screen. 12. Click on Next screen. All the field groups available with the InfoSet are listed above. We can select any particular fields we would like to have in our report. . Click on Next screen.8. In this screen. 10. We can select the field groups that need to be listed in the report. we can select the fields to appear on the selection screen during execution of the report. 9. 11.

. Click on the “Basic List” button to create a SAP Basic list query.13.

specify the line number and sequence number as you would like to appear on the report. the line structure would display the appearance of fields on the selection-screen. totals and counts (as necessary). For each field.14. You can also use this screen to indicate sort order. here also the selection-screen appears. 16. 15. Click on EXECUTE button to execute the report. As shown above. Click on SAVE. . As it is seen on normal reports.


com/Tutorials/SAPQuery/Part2/Page1. click here. For topic#1.Working with Infosets. User Groups. INCLUDEPICTURE "http://www.gif" MERGEFORMATINET \* .saptechnical.15. Query in detail In this document we shall cover Topic#2.

.com/Tutorials/SAPQuery/Part2/Page1.INCLUDEPICTURE "http://www.saptechnical.gif" MERGEFORMATINET \* Infosets Components  InfoSets are special views of data sources.16.

This means that queries based on this InfoSet can be copied and executed by both groups. Creating and changing Infosets Creating Infosets – Prerequisites Assign Data sources Infoset Display/Change Definition of field groups Obtaining additional information Creating Selections Further Codes Application Specific Enhancements Creating Infosets – Prerequisites The following questions help in meeting the prerequisites of creating an infoset.  Eg: Vendor master data can be important in purchasing as well as in accountancy.  Do you need to include any particular measures such as access protection? . An InfoSet describes which fields of a data source can be reported on in queries. as designated by the role or user group that they are assigned to.  Which data source corresponds to the requirements? For example: Material reports in Materials Management Document reports in Financial Accounting  Which fields do you need to include in the InfoSet?  Do you need additional information which is not available in the data source? (This means you are going to have to connect additional tables and the definitions of additional fields.  End-users are able to work only with those InfoSets that are relevant to their particular area.  InfoSets are assigned to user groups.)  Do you need parameters and selection criteria? (Parameters and selection criteria appear on the selection screens of queries that are created using the InfoSet). The relevant InfoSet is assigned to both roles/user groups.

Name Authorization group: This means that only users authorized to execute programs from this authorization group are able to execute these queries.  Reading tables directly: Is used when Query is prepared for retrieving data from one table. Use Tcode: AUTH_DISPLAY_OBJECTS Choose Data Source:  Table join using a table: Is used when Query is prepared for retrieving data from more than one database tables having relationships. Declaration in data section of the program will help the query to select the elements of data to be retrieved from database. 3. Do you need to be able to change the long texts and headers for the selected fields? Assign Data sources 1.  Sequential datasets 4.  Assigning additional tables  Creating additional fields  Creating additional Structures  Extras  Selections  Further Code  Application Specific Enhancements . 2. The selection screen can be prepared in Query and data is retrieved for output. processed. Options  No Automatic Text Recognition  Fixed Point Arithmetic Display/Change Infoset  The InfoSet display allows you to examine or change the structure of the InfoSet. data is validated. Logical databases: Is used when Query is prepared for retrieving data based on a Logical database (LDB) Using programs to retrieve data: Here a program can be written with own logic. As per the logic.  4.

The system administrator uses it to set up the work environment for end-users.  Fields must be assigned to a field group before they can be used in queries.  Every user assigned to the user group is able to execute the query. copy and execute . although they may. under certain circumstances.Definition of field groups  A field group combines related fields together into a meaningful unit.  Users are not allowed to modify queries from other user groups.  Include all table fields  Include key fields  Create empty field groups Note: Logical Database having more than 4 structures has different way of creating field groups.Eg: PNP User Groups Components  The User Groups component is used to maintain user groups.

Creating infosets or functional areas  Tcode-SQ02 .1.




2. To create user groups and assign to infosets  Tcode-SQ03 .


To create a query  Tcode-SQ01 .3.


Steps to create selection criteria to the query  Tcode-SQ01 .