Sqvi Manual Detal EN

SAP Query: How to Use,
Use and Expand use

]
Tammy Powlas
Fairfax Water
ASUG Volunteer
SAP Mentor
[ GRAZIELLA SBALCHIERO
ASUG INSTALLATION MEMBER
MEMBER SINCE: 2009
[ APRIL ZANELLI
ASUG INSTALLATION MEMBER
MEMBER SINCE: 2005
[ ARVIND SINGH
[ Fairfax Water
Largest Water Utility in Virginia
1 7 million customers
1.7
AAA bond rating
400 employees
p y
Fairfax Water produces, on average, 160 million gallons of
water per day.
One
O out off ffive Virginians
V gets their
h water from
f FFairfax
f W Water
Real Experience. Real Advantage. 2

[ Learning Points
What is SAP Query
How to set up SAP Query
Creating Reports with SAP Query
Keyy Questions before usingg SAP Queryy
Discuss how to use with BusinessObjects (BW not required)

[ Learning Points
What is SAP Query

[ What is SAP Query?
SAP Query is a powerful, easy-to-use, reporting tool used to
create reports
p from anyy ECC module or Solution Manager g (any
( y
ABAP back end) with limited or no development
Can query from one or more tables
Used to be known as ABAP Query
Provides users a wide range of output such as lists, statistics,
ranked lists and easy downloads to Excel
Before using, check if SAP standard reports might already meet
your requirements

[ Basic Principle
p of Reporting
p g
Tools
Define Generate List
Source: SAP
6
Real Experience. Real Advantage.

[ Reporting Options
SAP provided reports
Custom coded reports (ABAP)
SAP Query
QuickViewer – Transaction SQVI – single
g use query
q y
Module specific Information Systems – LIS, Report Painter,
Report Writer, PMIS, SIS
Third
Th d Party
P
Business Warehouse/BusinessObjects

[ Why Use SAP Query?
Allows end users to develop, change, and execute their own
q
queries
“User-Friendly” end-user tool that requires no ABAP skills
No custom code to write and support
Users can start using fast
More flexible than custom code – users can easily change queries
Queries are easy to administer and support
All SAP Query functionality is supported in release upgrades
Queries can be written against
g anyy ECC application
pp module
Can be used for Operational BI Reporting (Crystal,
Enhancement Pack 5)

[ Learning Points
What is SAP Query

[ Use Cases
A use case captures the “contract” between stakeholders of a
system
y about its behavior under various system
y conditions
The primary actor initiates an interaction with the system to
accomplish some goal
Casual User
Power User
Report
epo t Developer
eve ope

[ Configuration Use Case
Actor: Report Developer
Description: Configuration of SAP Query
Successful criteria: InfoSets and User Groups created
Two Components:
User (query) groups
InfoSets

[ Configuration/How to set up SAP Query
Configuration steps:
Create User Groups
Assign Users to User Groups
Create InfoSet
Assign InfoSet to User Group

[ Create User Group
User groups are a collection of SAP users grouped together
Does not have anything to do with security
Access to data is still controlled by authorizations
How it works:
Assign each user to one or more user groups
The queries assigned to one of the user groups when created
All users in that group can see the queries when running SQ01
You assign the users of SAP Query by entering the user in user
group (Transaction SQ03)
A collection of
SAP users ggrouped
p
together
13

[ Creating User Groups, aka Query Groups
Global area or standard area
User Create/Change/Delete
Groups
Assign InfoSets
Source: SAP
14

[ SAP Query: Assigning User Groups
All users in a user group
Access the same InfoSets
See all queries for the user group
Can have different authorization for creating and changing
queries
i
For example, we created user groups for:
Accounts Payable
Customer Care Center
HR/Payroll
General Ledger
Consider creating along departmental lines
15

[ Step 1 – Create User Groups – SQ03
Queries from assigned user

group show up here to
access
16

[ Step 1 – Create User Groups – SQ03
•Enter transaction SQ03

•Enter a User Group Name
•Click Create
•Enter a group description
•Click Save
•Select Assign Users and
InfoSets
17

[ Step 2 – Assign Users to User Groups
• Enter the
user IDs for
all the users
you want in
the group
•Click Save
18

[
DEMO – CREATING AND

ASSIGNING A USER GROUP

[ Create InfoSets
InfoSets is a source of data
InfoSets can also be used in QuickViewer (SQVI), Crystal and a
variety of BusinessObjects products
Define data and field in the InfoSet
InfoSets
I f S can be
b defined
d f d as:
An ECC table
An ABAP program
A Logical Database (LDB) – most common and a best practice
20

[ Possible Data Sources
Table join (inner, outer)
Inner joins – only data records that have join conditions are
displayed in tables
Outer joins – data records that do not have any join conditions
are also included in the left-hand
left hand table
Table (direct read) – for a single table
Logical
g database
Database tables that are determined in the structure of the
logical database
Best
B practice i is
i to create an InfoSet
I f S from
f a Logical
L i l Database
D b
21

[ What are Logical Databases?
y Logical databases are a pre-arranged hierarchical subset of data
y 250 are in NetWeaver 7.0, 7 0, pre
pre-delivered
delivered by SAP
y Explore using transaction SE36
y Securityy is alreadyy built in
y Common Logical Databases:
y PnP – HR Personnel Administration
y BRM – Accounting Documents
y MSM – Material master
y FMB - Funds Management (based on BCS)
22

[ Step 3 - Create InfoSets
• Enter transaction
SQ02
•Enter a name for
InfoSet
•Click Create
First you decide whether the InfoSet belongs to the
standard or global area
All SAP objects begin with prefix /SAPQUERY/
Consider using naming conventions to

ensure standards are followed for namingg
consistency
23

• Enter a
Name for
InfoSet (title)
• Select a
data source
•Click Enter
24

The Change
InfoSet screen is
divided into 3
areas:
Section A A – list of tables
Section B
in logical
database
B – list of field
Section C groups
C – Field Details
25

•Only the items in the

B section will be seen
B by users when creating
Datasets are divided into logical
g reports
p
units. These are called field groups.
You have to assign a field to a field •You create “Field
group so that the user can output Groups” using the
Groups
the field is in the list. Create button to make
logical groupings of
Field groups are classified to your fields
provide a logical division of data
26

[ Step 3 – Create InfoSets
Add fields to
each field
group by
right clicking
Section B on them in
Section A Section A and
selecting add
field to field
group or drag
d
them over
27

[ Step 3 – Create InfoSets
Generate
When you are finished
adding fields:
1. Click Save
2 Click Generate to
2.
The system manages
build InfoSet; checks
every InfoSet in two
for errors
versions: A generated
version and a revised 3. Click Back to return
version. to main screen of
Infoset 28

[ Questions to ask about adding fields to InfoSets
Which fields contain data for your company?
Ask your users
How will you organize data in field group? Think of your
power users
Like a good reporting – who, what, where, when, how

[ Field Groups Allow for Organization within InfoSets
Organizes data by logical groupings
Pull only the fields needed
Helps with security as users only see what they need to see

[
DEMO – CREATING
INFOSETS

[ Step 4 - Assign Each InfoSet to a User Group
• Select InfoSet
• Cli
Clickk
Role/User
Group
Assignment
• SSelect
l tU User
Group
created in
Step 2
• Click Save
32

[
DEMO – ASSIGNING USER

GROUPS TO INFOSETS

[ SAP Query Configuration Summary
Configuring is easy, but need to plan
Can use the InfoSets in QuickViewer and Crystal and other
BusinessObjects products (enhancement package 5)
You should plan
What fields will be in InfoSets
How to manage into Field Groups
How to manage your users
Standardize naming conventions
Be sure to add your own user ID to your newly created group
34

[ Learning Points
What is SAP Query
Keyy Decisions before usingg SAP Queryy

[ Query Use Case
Actor: Power User
Description: Creates Query
Successful criteria: Query successfully created and executed
A Query can be:

Basic list - a single line data report
Statistical list – a report that calculates averages / percentages
Ranked list – a specially sorted report
Basic lists are most common

[ Steps to Create Reports with SAP Query
1. Enter the report a name
2
2. Enter a title/format
3. Select field groups
4. Select fields
5. Add fields to the selection screen
6. Maintain order and output of fields
7. Enter Selection Screen
8. View report
37

[ Creating SAP Query Report
• EEnter SAP
Query with
transaction
SQ01
• Enter a name for
your report
• Click Create
• Select InfoSet
from the list
Use a naming convention for your reports

so you can locate your queries quickly 38

[ Navigating Between Screens
Navigation Level
Title
Format Field
Groups Field
Selection Selection
Fields
Source: SAP
39

[ Title Format Screen
Enter a title for your report
(required input field)
The “change lock” box check
box will prevent other
users from changing
your report
40

[ Select Field Groups
Select the field groups

that contain the
fields you want to
output or include
on the selection
screen
InfoSets are divided into field
groups, forming logical groups
of data
41

[ Select Fields
Select fields from fields

groups to be output
in your report
42

[ Add Fields to Selection Screen
You select fields to
appear on the
selection screen as
criteria
T create a basic
To b i list
li
report, click the
Basic List button
43

[ Basic List Line Structure
• Set up what you

want your report to
look like
• Indicate the order
and output of your
fields and indicate
any counts or totals
• Click Save
• Press F8 to execute
yyour report
p or click
the Test toolbar icon
44

[ Your Finished Report
• Complete
selection
criteria
• Click Execute
45

[ Your Finished Report
46

[
DEMO – CREATING A QUERY

[ Executing Query Use Case
Actor: Casual User
Description: Executes Query
Successful criteria: Query successfully executed

[ Learning Points
What is SAP Query

[ Key Questions before using SAP Query
What is the client/transport strategy?
Will you use the standard or global application area?
Who will own the InfoSets?
Who will create the reports?
p
What can you base your queries on?
Security..
50

[ Transport Strategy
A popular best practice is to design InfoSets in development,
transport
p them to pproduction,, and create/maintain qqueries and
user groups in live production environment
This is what we do at Fairfax Water
Also worked where nothing was transported and SAP Query
developed occurred in production
51

[ Will you use the Standard or Global Application Area?
Determining which application area you use will impact where
reports
p will be stored and which clients theyy will be available
A popular practice is to create objects in the standard area and
keep them client-specific
Move items to the global area when transporting to production
We use both
52

[ Who “Owns” the InfoSets?
It is important to ensure that your InfoSets are designed,
configured,
g , and tested
A well trained team member should “own” them, work them
in the development client, and transport them to QA, and then
production
d ti
You need to ensure that you have the right data
53

[ What Can you Base Queries on?
SAP Query allows you to create queries based on:
Logical databases (LDBs)
Programs
Tables
Table join combinations
The source of the data is key to ensure that queries run
efficient and provide accurate output
An InfoSet can be created on any of these. Best practice is to
use the Logical database
54

[ How to Manage End Users
Users are assigned via a special role in production to user
g p
groups
Key users can use SQ01 to create queries
Since most queries are based on logical databases, security to
tables is addressed – even though a user may “see” a query for
finance, if they don’t have underlying access to the tables then
theyy cannot execute it

[ Security
Options
Set security so that some users can create reports, while others
only execute them
Use LDB as source, user security is already built in so users see
only what allowed to use
56

[ Comparison
Readily Available in ECC Requires Purchase /

Implementation
SAP Standard Reports Business Warehouse /
SAP Provided tools: BusinessObjects
j
Report Writer Third Party add-ons
Report Painter
SAP Query
Q
QuickViewer
Custom Coded Reports
p

[ Learning Points
What is SAP Query
Keyy Decisions before usingg SAP Queryy

[ Using InfoSets to Connect to BusinessObjects w/o BW
Crystal Reports (CR) is able to connect to SAP ECC
CR has direct connectivitiy to the ABAP dictionary
CR can connect to the InfoSet and InfoSet/SAP Queries in SAP
http://www.sap-press.com/products/Reporting-
and-Analytics-with-SAP-BusinessObjects.html
dA l i i h SAP B i Obj h l

[
DEMO – CREATING
CRYSTAL REPORT AGAINST
ECC SAP QUERY
[
DEMO – CREATING
CRYSTAL REPORT AGAINST
ECC INFOSET
[
DEMO – SETTING UP ALV

USING CRYSTAL

[TransientProvider, Enhancement Package 5
Self Service Search &
Enterprise Reporting Data Visualization Analysis
Reporting Exploration
Crystal Reports Crystal Reports Dashboards BusinessObjects

Web Intelligence Analysis Office Analysis OLAP
2011 for Enterprise (Xcelsius) Explorer
Semantic Layer
Direct Access Universe Based Access Direct Access
Transient Provider
SAP HCM SAP SD SAP FIN 3rd Party Data
Source: www.sdn.sap.com/irj/boc/bi-solution-architecture - Ingo Hilgefort

[ ECC InfoSets, Enhancement Package 05
Transient Provider allows you
…to connect via a BEx Query in the local BI client of your SAP ERP system to
a classic InfoSet and in that way provide real-time ERP data to your end-users
… in that way expose operational data to SAP BusinessObjects tools
Works like an operational infoprovider or remote cube

[ Steps to Create Analysis Workbook Against ECC
InfoSet
Create InfoSet
Set Property
p y to Release -
SQBWPROP
Create BEx Query against InfoSet
Select BEx Query as a data source

in Analysis

[
DEMO – USING ANALYSIS

OFFICE TO QUERY AGAINST
ECC DATA
[ Pros / Cons of Transient Provider
Pros:
Operational BI Real
Real-time
time reporting, no modeling, no loading
Cons:
No hierarchies, no display attributes, no currency translation
Not all InfoSets are available for use

[ Tips
InfoSets can be used with SQVI but the Infoset needs to be in
the standard,, not gglobal area,, otherwise you
y will receive error
message AQ100 InfoSet not found
InfoSets using logical database read the data hierarchically
If you have created a QuickView and you want to convert it to
a SAP Query report, follow these three steps:
Navigate to the main screen of SAP Query (SQ01)
Following menu path Queries > Convert QuickViews
Select the QuickView from the dropdown box, and click the
green check
h k mark,
k andd name the
h SAP query, and
d click
l k the
h green
check mark again

[ Tips
Avoid creating query user groups with the same list of users.
It is confusingg and can become difficult to maintain.
When learning SAP Query, practice in the test/quality
environment and graduate to live client only after thorough
understanding
d t di
Don’t rename field names within the InfoSet

[ Return on Investment
No ABAP Development Required
Fast option for ad hoc reporting out of ECC
You own it! It is part of your toolset – no additional
development required
InfoSets can be a source of data for Crystal Reports and with
ECC Enhancement Package 5 you can use InfoSets with other
BusinessObjects tools

[ Best Practices
InfoSets are to be created in a development client and tested in
a test client before movingg to production
p
Use Logical Databases as security within those logical
databases will be handled for you.
Develop naming conventions

[ Key Learnings
SAP Query is a quick way to report out of ECC with no
development
p required
q
InfoSets can be used as a data source to BusinessObjects
Crystal and other BusinessObjects tools with ECC
E h
Enhancement t Package
P k 5
As an SAP ECC customer, you own this tool! Start using it
today.
y

[ Check it out!
Join the ASUG BI Community
http://tinyurl.com/2df4mr5
Follow us on Twitter:
http://twitter.com/asug_bi
http://twitter.com/@asug_bi

[ On-Line ASUG Business Intelligence Community
“Opt-In”
Opt-In from your ASUG Profile to get updates.
updates
Visit us at www.asug.com

[ ASUG 2011 UPCOMING CONFERENCE

[ ASUG BI/EIM Influence Sessions at TechED
Session Code Description Date / Time
BI150 The BusinessObjects Universe: An Update From the SAP 9/14 9:15 am
B i
BusinessObjects
Obj S
Semantic
i LLayer IInfluence
fl C
Councilil
BI151 ASUG Influence Council: SAP BusinessObjects Analysis 9/14 10: 30 am
BI152 SAP BusinessObjects Enterprise Influence Council 9/15 4:30 pm
BI250 SAP BusinessObjects Explorer Casual User Influence 9/14 4:30 pm

Council
BI251 Best Practices for SAP NetWeaver BW and SAP 9/13 2:00 pm
BusinessObjects BI
BI252 SAP BusinessObjects Mobile BI Influence Council 9/14 2:00 pm
EIM250 Enterprise Data Warehouse Customer Influence Council 9/15 2:00 pm

Update
EIM350 SAP BusinessObjects Information Management Influence 9/13 3:15 pm
C
Council
il
76

[
@tpowlas

Sqvi Manual Detal EN

Cargado por

Información del documento

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

Sqvi Manual Detal EN

Cargado por

Copyright:

Formatos disponibles

SAP Query: How to Use,

Use and Expand use

Real Experience. Real Advantage. 2

Real Experience. Real Advantage. 3

Real Experience. Real Advantage. 4

Real Experience. Real Advantage. 5

Define Generate List

Real Experience. Real Advantage.

Real Experience. Real Advantage. 7

Real Experience. Real Advantage.

Real Experience. Real Advantage. 9

Real Experience. Real Advantage. 10

Real Experience. Real Advantage. 11

Real Experience. Real Advantage. 12

Real Experience. Real Advantage.

Global area or standard area

Real Experience. Real Advantage.

Real Experience. Real Advantage.

Queries from assigned user

Real Experience. Real Advantage.

•Enter transaction SQ03

Real Experience. Real Advantage.

Real Experience. Real Advantage.

DEMO – CREATING AND

Real Experience. Real Advantage. 19

Real Experience. Real Advantage.

Real Experience. Real Advantage.

Real Experience. Real Advantage.

All SAP objects begin with prefix /SAPQUERY/

Consider using naming conventions to

Real Experience. Real Advantage.

Real Experience. Real Advantage.

Real Experience. Real Advantage.

•Only the items in the

Real Experience. Real Advantage.

Real Experience. Real Advantage.

Real Experience. Real Advantage.

Real Experience. Real Advantage. 29

Real Experience. Real Advantage. 30

Real Experience. Real Advantage. 31

Real Experience. Real Advantage.

DEMO – ASSIGNING USER

Real Experience. Real Advantage. 33

Real Experience. Real Advantage.

Real Experience. Real Advantage. 35

 A Query can be:

Real Experience. Real Advantage. 36

Real Experience. Real Advantage.

Use a naming convention for your reports

Real Experience. Real Advantage.

Real Experience. Real Advantage.

Real Experience. Real Advantage.

Select the field groups

Real Experience. Real Advantage.

Select fields from fields

Real Experience. Real Advantage.

Real Experience. Real Advantage.

• Set up what you

Real Experience. Real Advantage.

Real Experience. Real Advantage.

Real Experience. Real Advantage.

DEMO – CREATING A QUERY

Real Experience. Real Advantage. 47

A Query can be:

Works like an operational infoprovider or remote cube