The document discusses the ABAP Query tool in SAP, including its components (InfoSets, user groups, queries), areas (standard vs global), InfoSet design strategies, and how to create InfoSets, user groups, and queries. Key points include using logical databases or table joins as an InfoSet data source, assigning additional tables/fields, and using queries to build reports with selection criteria and drill-down functionality.

1. The ABAP Query

4. Standard vs. Global Areas

7. InfoSet Design Strategy

12. InfoSet Creation

21. InfoSet - Data Source - External Program * End of data retrieval loop for individual records (ENDSELECT, ENDDO, ENDLOOP) Comment to finish the statement in the loop. The data must be available in the tab structure. * <Query_body> * Code to define the itab table, if such a table is used. * Start of a loop to retrieve, one at a time, each of the records that you want to report on, and place them in the tab structure (SELECT, DO, LOOP) * Code for formatting data Comment to finish off a data statement. * <Query_head> Definition of an internal table itab with structure tab providing the records that you want to report on. DATA: BEGIN OF itab OCCURS xxx. INCLUDE STRUCTURE tab. DATA: END of itab. DATA: Select-Options:… Definition of parameters, selection criteria, and fields. Parameters . Definition of the dictionary structure used to set up the InfoSet. This structure must contain the records that you want to report on. Tables tab . Report xxxxxxxx .

34. User Group Creation and Assignment

38. Query Creation

40. Query - Creation Use Notes to document the Remedy ticket number, date of creation, and brief description. Enter CUS&STANDARD as the standard variant to be used by this query. The naming convention of CUS& allows this to be transported. Enter your Query description, list and output format. Hit to continue.

43. Query – Graphical Query Painter

51. InfoSet Examples

52. InfoSet: ZSD_OPEN_ORDERS User Group: ZSD Query: ZSD_OPEN_ORDER_D Program: AQZZZSD=========ZSD_OPEN_ORD_D Purpose: Make open sales order information available at the order/item/ schedule line level with associated material master information. Separates confirmed and unconfirmed values and quantities and makes totals available at the order, item, and schedule line levels. Values are based on KZWI2 (Sub-total 2) since this represents shipment dollars. Requested date and earliest schedule line date is available at each level. Partial delivery or billing quantities are applied against the schedule lines to determine true open quantities and values at the delivery date level. An open order date allows only orders due to deliver in that time period to be considered. Logical Database Example

60. Purpose: Join material master information from MARA, MARC, MVKE, and MBEW for the purposes of downloading the information to an HWS Data Warehouse. Material data is merged with pricing data for the B0, B1, and B2 price lists for 3 input divisions (3A, 3B, 3C). Characteristic data for the material is also merged as well as Unit of Measure conversions. There are many additional calculated fields for the pricing and classification data. InfoSet: ZMM_DATAMINE User Group: ZMM Query: ZMM_DATAMINE Program: AQZZZMM=========ZMM_DATAMINE== Table Join Example

64. Purpose: Retrieve orders blocked by delivery block at either the schedule line and/or header level. An index was created on VBEP for schedule line delivery block for this report. If a schedule line delivery block is entered as selection criteria, data is retrieved starting with VBEP. If no schedule line delivery block is entered, data is retrieved starting with VBAK. InfoSet: ZSD_SO_BLOCK_E External Program: ZSDQ_SO_BLOCK Data Structure: ZSDQ_SO_BLOCK User Group: ZSD Query: ZSD_SO_BLOCK_E Program: AQZZZSD=========ZSD_SO_BLOCK_E External Program Example