HRIS AQ ARINSO Query 3.0 Administrator Manual PDF

ARINSO Query
Administrator Manual
ARINSO Query – Administrator Manual 1
Version 3.0
ARINSO Query
Administrator Manual
Version 3.0
November 2001
Version 3.0
Foreword
ARINSO International believes that the information described in this manual is

accurate and reliable, and much care has been taken in its preparation. However, no
responsibility, financial or otherwise, can be accepted for any consequences arising
out of the use of this material, including loss of profit, indirect, special, or
consequential damages.
The Customer should exercise due care to assure that the use of the software and
related documentation will be in full compliance with the laws, rules, and regulations
of the jurisdictions with respect to which it is used.
Copyright
Contents of this publication are copyrighted and cannot be reproduced in any form
without the written permission of ARINSO International. The information contained
herein is subject to change.
ARINSO Query is a trademark of ARINSO International.
All other brand or product names are trademarks or registered trademarks of their
respective companies.
© 2001 ARINSO International
All rights reserved.
Version 3.0
About This Manual
Using this Use this manual for instruction on how to customize and implement the ARINSO
manual Query.
The Implementation Guide (IMG) is intended for both super users and administrators
with given authorization profiles. However, limitations have been set on access to
certain parts of the IMG, depending on experience.
In order to skip, scan, and search for the information you require, use the chapter
overviews to indicate whether the content is relevant to you.
Manual This manual contains the following chapters:

content
Chapter Description
1 Introduction to the ARINSO Query Tool
2 Authorization Management
3 Overview of the Implementation Guide
4 Version and License
5 Global Tools
6 Customizing Tools
7 Business Intelligence
8 Upgrade Tools
Continued on next page
Version 3.0
About This Manual, Continued
Conventions To help the user identify and understand information in this manual, several
used conventions are used:
– this icon identifies examples in the manual
– this icon identifies notes in the manual
All screen shots used in this manual are SAP GUI 4.6
Note
Version 3.0
Table of Contents
Foreword ........................................................................................................................................... 3
About This Manual ........................................................................................................................... 4
Table of Contents .............................................................................................................................. 6
Chapter 1 ................................................................................................................................................. 9
Introduction to the ARINSO Query Tool ................................................................................................. 9
Overview........................................................................................................................................... 9
Installing ARINSO Query............................................................................................................... 10
Installing ARINSO Cloud ............................................................................................................... 11
Installing AccessDown Program..................................................................................................... 12
Chapter 2 ............................................................................................................................................... 13
Authorization Management ..................................................................................................................... 13
Overview......................................................................................................................................... 13
Chapter 3 ............................................................................................................................................... 15
Overview of the Implementation Guide.................................................................................................. 15
Overview......................................................................................................................................... 15
Chapter 4 ............................................................................................................................................... 18
Version and License .................................................................................................................................. 18
Overview......................................................................................................................................... 18
Version Installed ............................................................................................................................. 19
Change the License Key ................................................................................................................. 21
Chapter Summary ........................................................................................................................... 22
Chapter 5 ............................................................................................................................................... 23
Global Tools............................................................................................................................................... 23
Overview......................................................................................................................................... 23
Section A: Query Parameters....................................................................................................... 24
Overview......................................................................................................................................... 24
User Group...................................................................................................................................... 25
System Parameters .......................................................................................................................... 28
Administrator Parameters................................................................................................................ 34
Recommendations on Using Administrator Parameters ................................................................. 39
User Parameters .............................................................................................................................. 40
Path Parameters............................................................................................................................... 50
Section B: Variant Tools............................................................................................................... 52
Overview......................................................................................................................................... 52
Download / Upload Variants........................................................................................................... 53
Correct Variants .............................................................................................................................. 58
Fast Variant Group Management .................................................................................................... 61
Section C: Delete Temporary Objects ......................................................................................... 64
Overview......................................................................................................................................... 64
Section D: Mapping Authorizations to Tables............................................................................ 66
Overview......................................................................................................................................... 66
Section E: Chapter Summary ...................................................................................................... 68
Overview......................................................................................................................................... 68
Query Parameters ............................................................................................................................ 69
Variant Tools................................................................................................................................... 72
Delete Temporary Objects & Mapping Authorizations to Tables .................................................. 74
Version 3.0
Table of Contents, Continued
Chapter 6 ............................................................................................................................................... 75
Customizing Tools..................................................................................................................................... 75
Overview......................................................................................................................................... 75
Section A: Fields and Areas.......................................................................................................... 76
Overview......................................................................................................................................... 76
Field Customizing ........................................................................................................................... 78
Creating Standard Fields ................................................................................................................. 82
Creating Complex Fields ................................................................................................................ 85
Creating Virtual Fields.................................................................................................................... 88
Creating Referenced Date Fields .................................................................................................... 90
Creating HR Plan Fields ................................................................................................................. 92
Text for Field .................................................................................................................................. 96
View, Modify and Delete Fields ..................................................................................................... 98
Area Customizing ......................................................................................................................... 100
Link between Areas and Fields ..................................................................................................... 104
Relationships between Tables ....................................................................................................... 108
Conditions on Tables .................................................................................................................... 111
Section B: Special Graphics ....................................................................................................... 113
Overview....................................................................................................................................... 113
Cloud Scenario.............................................................................................................................. 114
Cloud Ranges ................................................................................................................................ 119
Section C: Layout Wizard .......................................................................................................... 121
Overview....................................................................................................................................... 121
Layout Wizard Functions.............................................................................................................. 122
Layout Wizard Calculations.......................................................................................................... 127
How to Create a Function Module ................................................................................................ 130
Section D: Start-Up Filter........................................................................................................... 132
Overview....................................................................................................................................... 132
Start-Up Filter ............................................................................................................................... 133
Section E: Other Tools................................................................................................................ 136
Overview....................................................................................................................................... 136
Parameters of Programs ................................................................................................................ 137
Customizing the List of Persons ................................................................................................... 139
Customizing Synchronizer ............................................................................................................ 141
Download / Upload Customizing.................................................................................................. 146
Check the Customizing ................................................................................................................. 152
Section F: Chapter Summary .................................................................................................... 155
Overview....................................................................................................................................... 155
Areas and Fields............................................................................................................................ 156
Special Graphics ........................................................................................................................... 160
Layout Wizard............................................................................................................................... 161
Start-up Filter ................................................................................................................................ 162
Other Tools ................................................................................................................................... 163
Version 3.0
Table of Contents, Continued
Chapter 7 ............................................................................................................................................. 167

Business Intelligence ............................................................................................................................... 167
Overview....................................................................................................................................... 167
Section A: PA Infotypes.............................................................................................................. 169
Overview....................................................................................................................................... 169
Updating PA Infotype Programs................................................................................................... 171
Infotypes with Recurring Fields.................................................................................................... 175
Infotypes with Calculated Fields................................................................................................... 177
Infotypes with Multiple Fields ...................................................................................................... 178
A Special Case: Infotype 0008...................................................................................................... 180
Dynamic Actions........................................................................................................................... 183
Section B: Payroll Extraction..................................................................................................... 184
Overview....................................................................................................................................... 184
Payroll Wage Type Customizing .................................................................................................. 186
Configure Clusters to be Extracted ............................................................................................... 191
Payroll Extraction Synchronizer ................................................................................................... 193
Payroll Extraction Execution ........................................................................................................ 195
Section C: Time Extraction ........................................................................................................ 202
Overview....................................................................................................................................... 202
Updating Programs for Time Extraction....................................................................................... 203
Infotype 0005 Extraction .............................................................................................................. 204
Infotypes 2001, 2002, 2003, 2005 Extraction ............................................................................... 206
Time Cluster Extraction ................................................................................................................ 208
Planned Working Time Extraction................................................................................................ 210
Section D: Recommendations on Shadow Tables..................................................................... 212
Overview....................................................................................................................................... 212
Section E: Chapter Summary .................................................................................................... 213
Overview....................................................................................................................................... 213
PA Infotypes ................................................................................................................................. 214
Payroll Extraction ......................................................................................................................... 216
Time Extraction............................................................................................................................. 218
Chapter 8 ............................................................................................................................................. 220
Upgrade Tools ......................................................................................................................................... 220
Overview....................................................................................................................................... 220
Appendix A .......................................................................................................................................... 221
Table Entries to Create Dynamic Actions for PA Infotypes ............................................................... 221
Overview....................................................................................................................................... 221
Appendix B .......................................................................................................................................... 227
List of Customized Tables ...................................................................................................................... 227
Overview....................................................................................................................................... 227
Version 3.0
Chapter 1
Introduction to the ARINSO Query Tool
Overview
Introduction For ad-hoc online reporting and controlling, ARINSO Query allows the user to
generate extremely fast custom queries against the following SAP-HR data:
• Employee master data
• Applicant master data
• Organizational structure data
• Payroll result data
• Travel expense data
• Time result data
• Pensions data
In order to implement and customize the ARINSO HR Query according to the needs
of the user, the administrator must follow procedures in this Implementation Guide.
In this chapter This chapter contains the following topics:
Topic See Page
Installing ARINSO Query 10
Installing ARINSO Cloud 11
Installing AccessDown Program 12
Version 3.0
Installing ARINSO Query
Introduction ARINSO Query is delivered on a CD-Rom along with installation instructions.
It consists of a series of SAP transports, which should be imported on the customer’s

system in the order specified in the “Order of Transports” file. This is delivered with
the CD-Rom. ARINSO Query is then ready for use.
Note See the Installation Manual for a complete overview on how to install the
ARINSO Query.
Pre-requisites ARINSO Query version 3.0 is developed to function on:
• SAP R/3™ versions 4.0 and higher
• Oracle, MS SQL, Adabas and DB2 databases
Oracle There are two special features for clients on an Oracle database which use database
database procedures:
procedure
• Enhanced performance
• Syntax check on the generated native SQL
This functionality is optional, though recommended for Oracle clients.
It is necessary to install three procedures and a function in order to use this

functionality. SYS authorization will be necessary to do these installations. All the
syntax and full instructions are included on the installation CD.
To activate the new functionality made possible by installing these, please see the
section on Administrator Parameters (page 34).
License Key A License Key is required the first time a Query is run. This has to be requested from
ARINSO Products, by filling in a special form (included on the installation CD) and
sending it to LICENSE.PRODUCTS@ARINSO.COM.
When the license expires, the same procedure must be completed. Request a new
license key from LICENSE.PRODUCTS@ARINSO.COM in the same way.
Version 3.0
Installing ARINSO Cloud
Introduction ARINSO Cloud is a PC based program which displays a two dimensional graph,
based on the data extracted by ARINSO Query. Any axes can be customized and set
against the data selected in the Query main screen.
ARINSO Cloud is an optional functionality and should be installed by a technical

administrator if required. It is fully integrated into the ARINSO Query.
Pre-requisites ARINSO Cloud can be installed for clients running on Microsoft Windows. The
following versions are supported:
• Microsoft Windows 95, Windows 98, Windows ME, Windows NT Version 4.0
or Windows 2000
• Pentium 2 processor running at 300 MHz
Note The Cloud will run on a less powerful machine, but the above is
recommended
• 25 MB space on the hard drive
• additional 128 MB of memory
Getting started An installation program for ARINSO Cloud is included in the ARINSO Query
CD-Rom. An uninstall program is also provided.
Version 3.0
Installing AccessDown Program
Introduction In order to download query results to MS Access™, a PC based program called

“AccessDown” must be installed.
This program should be installed by a technical administrator. It is fully integrated

into the ARINSO Query.
Pre-requisites AccessDown can be installed for clients running on Microsoft Windows. The
following versions are supported:
• Microsoft Windows 95, Windows 98, Windows ME, Windows NT Version 4.0
or Windows 2000
• Pentium processor running at 100 MHz
• 10Mb disk space
Getting started The AccessDown program is provided on the ARINSO Query CD-Rom. Full
instructions on installing the procedure are included on the CD-Rom.
Version 3.0
Chapter 2
Authorization Management
Overview
Introduction There are two types of authorizations to consider:
1. Standard SAP HR authorizations
2. Authorizations to use parts of ARINSO Query
SAP HR The following SAP HR authorizations are respected:

authorizations
• P_ORGIN HR: Master data
• P_ORGXX HR: Master data extended check
• PLOG PD: Personnel Planning & Development
• P_APPL HR: Applicants
• P_PCLX HR: Clusters
• P_TCODE HR: Transaction Code
• P_PERNR HR: Master data - Personnel number check
• P_CH_PK HR-CH: Pension fund: Account access
• Structural PD Authorizations
• Customer defined SAP HR authorizations (triggered by setting P_NNNN)
Version 3.0
Overview, Continued
ARINSO The ARINSO Query Implementation Guide (IMG) is intended for both Super Users
Query and Administrators. Limitations have been set on access to certain parts of the IMG,
authorizations depending on experience. Some actions in the Query are restricted to Administrators
only, and some to Super Users.
Below are the actions in the Query that need to have an authority check before them
as well as the user types that are allowed to perform those checks:
Activity Authorization
Save Public Variant Administrator, Super User
Modify Public Variant Administrator, Super User
Create Root Public Group Administrator, Super User
Modify Public Group Administrator, Super User
View Field Customizing Administrator, Super User
Modify Field Customizing Administrator
View Parameters Customizing Administrator, Super User
Modify Parameters Customizing Administrator
Execute Business Intelligence Administrator, Super User
If a user/administrator tries to change part of the IMG to which they do not have
Note
authorization, access will be denied.
If SAP system is put in mode “no changes allowed”, then only Super User activities
(in table above) can be performed.
Authorization For instruction on how to create an authorization object, see section on System
object Parameters in Chapter 5, page 30.
Version 3.0
Chapter 3
Overview of the Implementation Guide
Overview
Introduction The Query Implementation Guide is designed to explain how the ARINSO Query
can be customized according to the needs of the customer.
Customizing in the Query IMG directly affects what the users will see and how they
will be able to use the Query tool.
Getting started To launch the ARINSO Query Implementation Guide:
• Log on to SAP
• Enter transaction code YPAQC in the command field or
• From ARINSO HR Query main screen (transaction YPAQ), go to menu bar and
click Administration → Implementation Guide as shown below:
View of Query The view below shows the initial ARINSO Query Implementation Guide screen:
IMG screen
Note The last three nodes (Customizing Tools, Business Intelligence and
Upgrade Tools) are only displayed in the IMG if they have been installed
previously (see Installation Manual for instruction on how to install
them).
Version 3.0
Overview, Continued
Description of Each Query IMG node drills down to reveal the options that need to be customized.
IMG The table below gives an overview of what each node allows to do:
The node … Allow an appropriately authorized user to administrate …
Version and License installed version and license key
Global Tools query parameters, variant tools and global maintenance tool
Customizing Tools fields and areas, special graphics (cloud), layout wizard, start-up
filter and other tools
Business Intelligence PA infotypes, payroll and time results
Upgrade Tools old Query deletion, Query version upgrade and variants upgrade
For details on Query IMG authorizations, see page 14.

Note
Help Each node in the Query IMG has documentation attached to it. Click next to the
node to access it.
ARINSO also provides online help, i.e. structured, searchable HTML versions of
both the Administrator Manual and the End User Manual.
On any field in the tool, online help can be accessed by clicking F1on the field and
then on .
Note See Installation Manual for instruction on how to install the online help.
Version 3.0
Overview, Continued
Icons A series of features, which are standard in SAP, is frequently used in the Query IMG.
The table below gives a short description of those features:
Icon … Allows the Administrator to …
create a new field
display a field
modify a field
delete a whole selection
copy selection
insert a line
delete a line
test the selections made
save the selections made and automatically call for a transport

request (where appropriate) revealing the screen below:
Enter transport request and validate by clicking .
access dropdown menu
Version 3.0
Chapter 4
Version and License
Overview
Introduction The Version and License node drills down to the following customizing options:
Those two programs allow the administrator to respectively:
• see which ARINSO Query version(s) and patches are installed, and
• change the license key.
Topic See Page
Version Installed 19
Change the License Key 21
Chapter Summary 22
Version 3.0
Version Installed
Introduction In this part of the Implementation Guide the administrator can check which Query
versions are installed on the system as well as the list of patches for each installed
version.
Getting started To access the Version Installed tool click under the
Version and License node of the Query IMG.
Query version To view and choose a Query version follow the procedure described in the table
below:
Step The Administrator …
1 Accesses the Version Installed tool as described above to reveal the

following screen:
Version 3.0
Version Installed, Continued
Query version (continued)
2 Chooses a version by clicking on the icon to reveal a list of possible

entries. Select one entry by double clicking on your choice.
3 Validates the selection by pressing Enter. The detailed Query version

name is now displayed right of the version field and the patches are
listed in the table.
4 Clicks to go back to the IMG main screen.
Version 3.0
Change the License Key
Introduction A license key is required by the Query. This program allows the administrator to
change a license key sent from ARINSO email address:
license.products@arinso.com.
Accessing the To access the Change the License Key program click
program under the Version and License node of the Query IMG.
Change license To change a license key follow the procedure below:

key
1 Accesses the Change License Key screen as described above to reveal

the following screen:
2 Enters the license key number in the yellow part as shown in the screen
view above
3 Clicks to confirm selection and go back to the Query IMG main

screen
Version 3.0
Chapter Summary
At the end of At the end of this chapter the administrator should be able to access and use the
the chapter Version and License node of the ARINSO Query IMG to:
• check which Query version(s) is/are installed on the system as well as the list of
patches for each version installed
• change a Query license key
Version 3.0
Chapter 5
Global Tools
Overview
Introduction The Global Tools section drills down to the following nodes:
Here is an overview of the function of each node:
• Query Parameters – this node allows the administrator to define parameters that
will be used by default every time the Query is launched
• Variants Tools – this node allows the administrator to carry out administrative
tasks on variants (download and upload variants between different SAP clients,
correct variants and manage authorizations on variants)
• Delete Temporary Objects – this node allows the administrator to delete

temporary objects in the Query
• Mapping Authorizations to Tables – this node allows the administrator to link

tables to infotypes
For information on … See section … On page …
Query Parameters A 24
Variant Tools B 52
Delete Temporary Objects C 64
Mapping Authorizations to Tables D 66
Chapter Summary E 68
Version 3.0
Section A: Query Parameters
Overview
Introduction The Query Parameters node drills down to the following customizing options:
• User Group – allows the administrator to group users together
• System Parameters – allows the administrator to define parameters for the whole
system (i.e. client independent parameters)
• Administrator Parameters – allows the administrator to define parameters per

client
• User Parameters – allows the administrator to set parameters for users or user
groups
• Path Parameters – allows the administrator to specify path directories of Query

elements
In this section This section contains the following topics:
Topic See Page
User Group 25
System Parameters 28
Administrator Parameters 34
Recommendations on Using Administrator Parameters 39
User Parameters 40
Path Parameters 50
Version 3.0
User Group
Purpose The aim of this part of the Query IMG is to group users together so they can be
assigned the same Query parameters and options.
Getting started To access the screen to change user groups click on under the Query
Parameters node of the IMG.
Screen view The view below shows the screen where user groups can be created and changed:
Screen The User Group screen is divided into two sections:

description
• Group – lists all the groups created
• User by groups – lists all the users belonging to a group (to view the list of users
in a group, select the group and click )
Version 3.0
User Group, Continued
Creating a The table below describes how to create a user group:

user group
1 In the ‘Group’ section clicks on (insert line) to reveal the screen

below:
2 Enters the new user group name
3 Clicks to go back to main screen. The new user group is now

included in the list of groups.
Version 3.0
User Group, Continued
Adding users In the table below the administrator will find the procedure for adding users to a
to a group group:
1
Selects the group to which users should be added and clicks to view
details of that group. The selected group is now highlighted in blue.
2 Clicks (in the ‘Users by group’ section) to reveal the following

screen listing all users in alphabetical order:
3 Selects the users to add to the group by:
• ticking the box left of the user name or

• double clicking on a name or
• selecting a name and then clicking to validate the choice or

• clicking to select all users
Note A confirmation pop-up will appear if the user already belongs

to a group.
4 Clicks to validate the selection(s) and go back to user group main

screen.
Deleting users To delete users from a group:
• Select the users to delete, and
• Click to remove them from the group.
Version 3.0
System Parameters
Purpose System Parameters are used to set up the Query to work in a particular way. Here,
the administrator must select:
• the SQL options to use,
• the authorization object name, and
• the wage types to use in the Business Intelligence section.
System parameters are client-independent.
Getting started To access the System Parameters screen click on under the
Query Parameters node of the IMG.
Screen view The screen view below shows the System Parameters screen:
Version 3.0
System Parameters, Continued
Screen The System Parameters screen is made up of three sections:

description
• SQL Options
• Authorizations and
• Business Intelligence
Each section is explained in the following paragraphs.
SQL Options In the ‘SQL Options’ section, the administrator must enter the following:
• a database user – specifies where Oracle procedures have been installed (e.g.
SYS), and
• a view name – specifies the begin view name that will be used to view the data
(e.g. V_ARG_). A number will be added to the name to make it unique.
Note This is only necessary when the ‘Use View’ or ‘Use Table’ options are
being used. See section on Administrator Parameters, page 36, for
information on what ‘Use View’ and ‘Use Table’ are.
Authorizations Some actions in the Query need an authorization to be performed (see Chapter 2,
page 13 for a list of those actions).
The administrator must create two things:
• an authorization object, and
• an authorization field.
An authorization object is an element of the authorization system. It enables complex

checks of an authorization. For the authorization check to be successful, the user
must pass the check for each field contained in the object (it combines up to ten
authorization fields).
The client must create his own authorization object in order to be able to use the
Profile Generator (transaction PFCG) to set up the profiles for the users.
Version 3.0
Creating an Before creating an authorization object, an authorization field must be created. To

authorization create an authorization field follow the steps described in the table below:
field
Note As of SAP release 4.6b go directly to step 3 of the table above (still in
transaction SU20).
1 Enters transaction code SU20 in the command field to reveal the

following screen:
2 Clicks on to access the ‘Authorization Fields’ screen
3 Clicks the icon to reveal the screen below:
4 Chooses a field name according to naming convention used
Note We advise to use YQUERY_ACT as field name
5 Enters data element /ARINSO/QUERY_AUTH_OBJECT
6
Clicks the icon to create and save the authorization field
Version 3.0
Creating an Once the field has been created, the authorization object can be defined. To do this,
authorization follow the steps below:
object
1 Enters transaction code SU21 in the command field to reveal the

following screen:
2 Double clicks on object class HR to access the HR objects list
3 Creates a new object by clicking . The following popup screen will

then appear:
4 Enters the name of the object being created
Note We advise to use Y_QUERY30 as object name
Version 3.0
Creating an authorization object (continued)
5 Gives an object description
Note Object class should already be filled. If this is not the case,
select HR from the dropdown menu.
6 Enters the name of the field created earlier (e.g. YQUERY_ACT) in the
‘Authorization fields’ table.
7 Saves selections by clicking the icon
Inserting Once both authorization field and object have been created, they can be inserted in
authorization the System Parameters screen as shown below:
parameters
Business In the Business Intelligence section of the System Parameters screen, the
Intelligence administrator must specify the following parameters:
• Min Lgart – default wage type for minimum salary
• Max Lgart – default wage type for maximum salary
• Per. Lgart – default wage type for periodic salary
• Ann. Lgart – default wage type for annual salary
As part of the shadow table extraction for infotype 0008, an employee’s minimum or
maximum salary, as well as period salary or annual salary can be extracted. In order
to do this, values have to be entered here for each parameter. The values entered will
act as “dummy” wage types in the shadow table (see Chapter on Business
Intelligence, page 167).
The table overleaf describes each parameter giving possible values:

Version 3.0
Business Intelligence (continued)
Parameter Possible values
MIN LGART E.g. If the value “9MIN” is entered in this field, then to report on
minimum salary a complex field would be set up in the Query to
extract from table /ARINSO/BI_0008 where LGART = 9MIN
MAX LGART E.g. If the value “9MAX” is entered in this field, then to report on
maximum salary a complex field would be set up in the Query to
extract from table /ARINSO/BI_0008 where LGART = 9MAX
PER LGART E.g. If the value “9PER” is entered in this field, then to report on
periodic salary a complex field would be set up in the Query to
extract from table /ARINSO/BI_0008 where LGART = 9PER
ANN LGART E.g. If the value “9ANS” is entered in this field, then to report on
annual salary a complex field would be set up in the Query to extract
from table /ARINSO/BI_0008 where LGART = 9ANS
Saving data Once all selections have been made for System Parameters, click to save data.
This will call for a transport request. Create a transport request as prompted and click
to validate.
Version 3.0
Administrator Parameters
Purpose Like System Parameters Administrator Parameters are used to set up the Query to
work in a particular way but this time they are client dependent.
Accessing the To access the table for customizing Administrator Parameters, click on
program under the Query Parameters node of the IMG.
Screen view The view below shows the table where Administrator Parameters can be customized:
Note If this table only contains entries for one user, the administrator is taken
directly to the next screen (see overleaf for a view of that screen).
Version 3.0
Administrator Parameters, Continued
Entering The table on next page describes the procedure for customizing Query Administrator
parameters Parameters:
1 Clicks to reveal the screen below:
Note To alternate between change and display mode, click icon

2 Enters a user name or user group for which administrator parameters
need to be set. Parameters can be set for individual users. A default
value, which is used if there is no other record for a user, can also be set.
This default value is denoted by &DEFAULT.
3 Specifies the requested SQL Optimization (five) and Authorization
(three) parameters
Note The eight parameters are explained in the table overleaf.

4 Clicks to save new entries. This will call for a transport request.
Create a transport request as prompted and click to validate.
Version 3.0
Parameters The table below gives a description of the eight administrator parameters to define:
Parameter Use Possible values
SQL Optimizer This parameter allows the administrator to • PIN (Pernr In) – Normal process
change the way the native SQL statement is (i.e. population and layout are
generated. processed simultaneously)
The Query generates a native SQL statement • PTAB (Pernr Tab) – Process
to select the data from the database. through multiple queries (i.e.
Normally, population and layout restrictions population first and then layout)
are processed in one select statement.
However, when the SQL length exceeds the • $ (value defined for the default
SAP length (SAP restriction), it is quicker to user &DEFAULT)
first select personnel numbers, and then
generate a second SQL statement to select
layout data. Note If left blank, PIN is taken
by default.
SQL Hint (Oracle Generates an SQL Hint. SQL Hints are used • RULE – a rule-based optimizer
dependent) for optimizations on reports. uses a fixed set of rules when
determining the execution plan
Oracle Hints – also called Optimizers Goal for a statement and does not
Hints – influence the optimizer’s overall attempt to factor in the ultimate
goal when formulating an execution plan cost of executing that plan. This
(the way Oracle proceeds the SQL statement hint can be used when the
to retrieve the results). statistics are not launched or are
It is advised to leave it blank if the DBMS invalid on the system.
(Oracle for instance) is well configured. • ALRW (All Rows) – performs
an execution plan that
minimizes the resource
consumption
• $ (default value)
Version 3.0
Parameters (continued)
Use View (Oracle Aims at improving the performance of the • Enter X to use this option
dependent) native SQL. It stores the program code in a
view and an Oracle procedure performs the • leave blank to not use it
actual selections of data at database level.
• take the value defined for the
In order to benefit from this option you must default user &DEFAULT ($)
have an Oracle database, and have installed
the Oracle procedures.
Use Table (Oracle Aims at improving the performance of the • Enter X to use this option
dependent) native SQL. It uses an Oracle procedure to
select data, which is put into a temporary • leave blank to not use it
table. The entire contents of this table are
then selected by open SQL with one simple • take the value defined for the
select statement. default user &DEFAULT ($)
In order to benefit from this option, you

must have an Oracle database, and have
installed the Oracle procedures.
Check Generated The code that extracts data for a Query is • Enter X to use this option
SQL written in native SQL, therefore standard
SAP syntax checks cannot be carried out on • leave blank to not check the
the generated code. generated SQL
For Oracle databases, there is the option of • take the value defined for the
executing a syntax check on database level. default user &DEFAULT ($)
In order to benefit from this option, you

must have an Oracle database, and have
installed the Oracle procedures.
Number of days To respect structural PD authorizations, the • $ (default value)

between refresh Query fills up a table with all PD
PD authorization authorization details for each user. This • 000 (every day)
option tells the Query how often the table
should be updated. This depends on how • a number between 001 and 999
often PD authorizations change within your (e.g. 005 = every 5 days)
organization.
Version 3.0
Number of days In order to respect authorizations on • $ (default value)

between refresh pensions data, a table is filled with
pension individuals’ authorizations profiles. • 000 (every day)
authorization
Here, the administrator decides how often • a number between 001 and 999
that table should be updated. This depends
on how often pensions security profiles are
changed within your organization.
This option is only relevant if the ARINSO

Query is to be used to query on SAP
pensions data.
Number of This parameter allows the administrator to • $ (default value)

concurrent queries regulate the number of Query sessions a user
can have running at the same time. • 000 (unlimited)
This could be interesting in the case of many • a number between 001 and 999
users, to restrict demand on your systems. (e.g. 004 allows 4 Query
sessions to run simultaneously)
Note Leaving blank means unlimited
Modify To modify Administrator Parameters:

administrator
parameters • double click on a name/group (make sure you are in change mode) or select a
name/group and click (make sure you are in change mode)
• carry out the necessary changes and save
Version 3.0
Recommendations on Using Administrator Parameters
Introduction Administrator Parameters can be managed in such a way that performance of the
ARINSO Query is improved.
Use of Oracle Oracle views can be used for big databases to accelerate reporting or for very
views complicated security profiles. The procedure to install them is available on the
Products CD or can be sent upon request at products@arinso.com
Note This feature is only available with an Oracle Database.
SQL In order to speed up and optimize some queries, the ARINSO Query can use the
optimization following SQL optimizers: HINT, PERNR IN, PERNR TAB, ALL ROWS and
RULES.
There are no rules on which optimizer will be better as it is system dependent.
ARINSO Products support provides tools helping to determine the best combination.
Contact us for further information.
Creation of When a few fields in the database are queried a lot due to their relevance in your
secondary business requirements, creating additional database indexes is an excellent way to
indexes increase performance. A thorough analysis of what indexes to create are needs to be
done beforehand.
This is even truer when reporting on PD fields.
Version 3.0
User Parameters
Purpose This part of the IMG is used for administrators to set default values and modify
existing values for users or user groups. Changes will be reflected in the table shown
below.
Note User Parameters can also be customized via the menu on the Query main
selection screen menu. Go to Administration Æ User Options as shown
in this view:
Getting started Click on under the Query Parameters node to access the
screen below where the list of users for whom parameters have been set is displayed:
Version 3.0
User Parameters, Continued
Entering The table below describes the procedure for customizing Query User Parameters.
parameters Each parameter will be discussed in a separate table (see overleaf).
2 Enters a user name or user group for which user parameters need to be
set. Parameters can be set for individual users. A default value, which is
used if there is no other record for a user, can also be set. This default
value is denoted by &DEFAULT.
3 Specifies the requested parameters
Note Each parameter is explained in the table overleaf
Version 3.0
Entering parameters (continued)
4 Clicks to save new entries. This will call for a transport request.
Create a transport request as prompted and click to validate.
Parameters The table below gives a description of the user parameters to define:
Country grouping Country groupings are used to separate one country

Click or use F4 to
from another. They are primarily used in conjunction
display a list of all
with wage types to specify the country for which
possible values
payroll results will be accessed.
Default currency This option converts all currencies to the currency

Click or use F4 to
chosen here by default in case several currencies are
display a list of all
used (in the Cloud or in the Layout Wizard) so that
possible values
results can be displayed in one single currency.
Example
If in the same Cloud different currencies are used (e.g.

French Francs, US Dollars and Belgian Francs) and
US Dollar is specified as default here, those currencies
will be converted to US Dollar in the results.
Version 3.0
Show technical When the user selects F4 on the Query main screen to • leave blank to not use
name choose a field, he or she is presented with a list of this option or
fields to choose from. By default, only the field • put a cross (X) to use
description is displayed in this list. this option or
• take the value defined
Checking this box allows the user to also see the for the default user ($)
technical name of fields.
Show all fields Allows the user to see all the fields in the list of fields • leave blank to not use
(i.e. even unauthorized ones) when pressing F4 on the this option or
Query main selection screen. • put a cross (X) to use
this option or
for the default user ($)
Query type Used to choose the query type to use by default every • PA (employee data)
time the ARINSO Query is launched or
• PB (applicant data) or
• value defined for the
default user ($)
Popup exit Query Allows the administrator to show a confirmation • leave blank to not use
popup when exiting the query. This is to ensure that this option or
the query is not exited by mistake and settings lost. • put a cross (X) to use
this option or
Version 3.0
Population screen This option determines the Population Selection tab to • 0 (population
use by default on the Query main selection screen. selection table and
start-up filter) or
• 1 (population
Example
selection table only)
or
If the value ‘0’ is entered here, both the Population
Selection table and the Start-up Filter will be displayed • $ (value defined for
on the Query main selection screen as shown in the the default user)
view below:
Version 3.0
Ignore initial count Used to decide whether the Query should count the • leave blank to
population when it is first launched. If the initial count perform initial count
is skipped, the user will get quicker to the selection or
screen.
• put a cross to ignore
If the administrator chooses to ignore the count, the initial count (X) or
following appears on the Query main screen revealing
that the population count is not available: • take the value defined
Default start-up Specifies the default start-up filter to display on the

Click or use F4 to
filter Query main screen. The start-up filter is used to restrict
display the list of all
the population to a particular sub-population that the
customized start-up filters
user will query (see page 130 for instruction on how to
customize start-up filters).
Module ID Defines the module ID (i.e. output mode) to be used by • LAYLIST (Resulting
default on the main screen when launching the Query. List)
This is simply a default value and can be changed from • HRREP (HR Report)
the Query main selection screen. • CLOUD (Cloud)
• PYRAM (Pyramid)
Note See Chapter 4 of the End User Manual for a
description of each output mode • LAYWIZ (Layout
Wizard)
Version 3.0
Layout screen Specifies which layout screen to use in the Layout • 0 (layout selection list
Screen tab in the Query. and layout filter)
• 1 (only layout
selection list)
Example
• 2 (only layout filter)
The screen below shows an example of a Layout List • $ (value defined for
tab displaying both Layout Selection and Layout Filter the default user)
(i.e. using value ‘0’):
Popup exit Allows the administrator to decide whether to show a • leave blank to not use
resulting list confirmation popup when exiting the Query Resulting this option or
List. • put a cross (X) to use
this option or
Note This option is useful if exiting by mistake • take the value defined
to avoid selecting all the data again. for the default user ($)
Version 3.0
Access DB file The user has the possibility to download the Query The Access database
name Resulting List to Microsoft Access™. name has to be entered
manually
This option allows the user to determine the name of
the Access Database File to use when downloading the
list to Access™.
Spreadsheet Used to define the spreadsheet type to use by default • EXCEL (Microsoft
selection for downloading the results from the Query Resulting Excel™)
List. • LOTUS123 (Lotus
123)
• $ (value defined for
the default user)
Show all values Allows the administrator to show all required entries in • leave blank to remove
the Resulting List or remove double entries if he or she double entries or
wishes to. • put a cross (X) to
show all options or
Version 3.0
Description of job The Query can run jobs in background using the • a title of your own
icon on the main selection screen. choice
This option allows the administrator to define the title • ?ASK will display a
that will be displayed in the Query Workflow tab when popup asking for a job
running a background job. All possible values are description every time
listed in the column opposite. the Query is run in
background
Example • #DATUM will show

the datum on which
the background job
was executed
• #UZEIT will show

The title entered by default for this option will appear the time on which the
in the Query Workflow tab as shown in the view background job was
below: executed
• #UNAME will show

the name of the user
who executed the
background job
• leave blank to display

the system default title
Date specification Used to decide if a date should be specified every time • leave blank to not use
in variants a variant is saved. Date specifications allow the this option or
administrator to determine the dates used when • put a cross (X) to use
executing the variant in the future. this option or
If this functionality is not used, then variants will for the default user ($)
always be run with the dates initially saved in them.
Version 3.0
Go to pension In the resulting list the end user has the possibility to • leave blank to not use
transaction do a drill down to personal data by going to transaction this option or
PA30. Whenever relevant he or she can also display • put a cross (X) to use
pension funds data (transaction PACA). this option or
Here, the administrator has to decide whether to for the default user ($)
display pension funds data if relevant.
Version 3.0
Path Parameters
Purpose This part of the Query Implementation Guide is used to show path directories of
different Query elements.
Getting started To access Path Parameters click on under the Query

Parameters node.
Screen view The view below shows the Path Parameters screen:
Path There are six types of Path Parameters:

parameters
• Cloud Program Path – where the Cloud program is installed
• Temporary Path – where temporary files are located
• Capture Path – where capture files are located
• Online Help Path – where online help files are located
• Access Download Program Path – where Access Download program is located
• Access Download Database Path – where Access Download database is located
As for other parameters, Path Parameters can be viewed, modified, created and
deleted.
Version 3.0
Path Parameters, Continued
Creating path To create new path parameters follow this procedure:

parameters
1 Accesses the screen where Path Parameters are customized as explained

above and click .
2 Gives the name of the user for whom the parameter should be set.
Parameters can be set for individual users. A default value, which is used if
there is no other record for a user, can also be set. This default value is
denoted by &DEFAULT.
3 Specifies the parameter to locate. Choose one of the following (the list can
be accessed by pressing F4):
• CLD_PROG (Cloud program)
• GLB_TEMP (temporary files)
• GLB_CAPT (capture files)
• GLB_ONLI (online help files)
• OUT_ACSS (Access Download program)
• OUT_ACSD (Access Download database)
Note The administrator needs read and write access to directories

GLB_TEMP and GLB_CAPT
4 Determines path directory where the file selected should be located
5 Clicks to save new entries. This will call for a transport request. Create
a transport request as prompted and click to validate.
Version 3.0
Section B: Variant Tools
Overview
Introduction This part of the Query IMG allows the administrator to carry out administrative tasks
on variants. The Variant Tools node drills down to the following customizing
options:
Here is an overview of what each node allows the administrator to do:
• Download / Upload Variants – this option allows the administrator to download

and upload variants from different clients
• Correct Variants – this option allows the administrator to correct errors in

variants or delete erroneous variants
• Fast Variant Group Management – this option allows the administrator to

quickly update authorizations on variant groups
Topic See Page
Download / Upload Variants 53
Correct Variants 57
Fast Variant Group Management 59
Version 3.0
Download / Upload Variants
Purpose In this part of the IMG, administrators can download and upload Query variants from
different systems/clients.
Accessing the To access the Download / Upload Variants program click

program under the Variant Tools node of the Query IMG.
Screen view The view below shows the Download / Upload Variants customizing screen:
Version 3.0
Download / Upload Variants, Continued
Screen The Download / Upload Variants screen is made up of two tabs:

description
1. Download Variants
2. Upload Variants
Downloading The Download Variants tab consists of three elements:

variants
• a table with the list of existing variants that can be downloaded
• a search section enabling to search for variants by user, by group ID or by

variant ID
• a ‘Save to file’ section
Note In order to use this tool, the user must be logged on to the client from
which the download takes place
To download variants, follow the procedure described in the table below:
1 Selects the Download Variants tab
2 Defines which variant(s) to download by selecting variants in the table
Note You can also search for variants by user, group ID and
variant ID. To do so, click and enter selection criteria.
Version 3.0
Downloading variants (continued)
3 Specifies a file name and path in the ‘Save to file’ field. To do so:
1. Click on to reveal the following screen:
2. Specify the file name and the directory path
Note The file type used is not important
3. Click the button
4 Clicks to execute download
Version 3.0
Uploading Variants can be uploaded via the following interface:

variants
The Upload Variants tab consists of three elements:

• a table with the list of existing variants that can be uploaded
• an ‘Upload to’ section to decide to which user and in which group the variant
will be available
• a ‘File’ section to specify the file from which variants are uploaded
Note To do the upload the administrator must first log on to the “target” client
To upload variants follow the steps in the table below:
1 Selects the Upload Variants tab
2 Specifies a file name and path from which variants have to uploaded and
click to import the variants. The variants selected are now displayed
in the Upload Variants table
Version 3.0
Uploading variants (continued)

3 Decides to which user the variant should be uploaded. This can be
carried out:
• via the table for each variant in the table

individually, or
• via the ‘Upload to’ section for all variants

selected in the table
4 Enters the group to which the variant will be attributed.
• via the table for each variant in the table individually
• via the ‘Upload to’ section for all variants selected in the table
By clicking on the possible entries dropdown in the Group ID field

the variant tree for a given user will be displayed:
Select the required group from the tree and the program will return to the
Upload screen with a code number in the Group ID field:
To create a new variant group, click the icon next to the Group ID
field.
Note If this field is left blank, the variant will be uploaded to the
selected user’s private variants
5 Select the variant(s) to upload in the table and click to execute
upload.
Once the variants have been uploaded the following message will appear
at the bottom of the screen .
Version 3.0
Correct Variants
Purpose If changes are made to customizing, existing Query variants may be affected. This
tool allows the administrator to check all variants and correct/delete them if
necessary.
Accessing the To access the Correct Variants program click under the
program Variant Tools node of the Query IMG.
Screen view The view below shows the Correct Variants tool screen. The screen is divided into
two sections:
• a list of variants containing fields that do not exist in the customizing, and
• a list of variants referring to a non-existing user or public group.
Version 3.0
Correct Variants, Continued
Checking If a variant contains fields that do not exist in the customizing or refers to a non-
variants existing user or public group, the administrator has two options:
1. Correct the field
2. Delete the field
Deleting The table below describes how to delete a variant:

variants
Step Action
1 Select variant(s) to delete and click
2 Click ‘Yes’ in the appearing pop-up to confirm the deletion:
Version 3.0
Correct Variants, Continued
Correcting To correct variants containing fields that do not exist in the IMG follow the
fields procedure described in the table below:
Note Correcting errors in variants can also be done via the Query variant tree
screen as described per End User Manual.
Step Action
1 Select the variant(s) in the table that need to be corrected
2 Click to reveal the popup below:
3 Enter the name of the correct field and click
Correcting users To correct variants referring to a non-existing user or public group follow the
or groups procedure described below:
Step Action
1 Select the variant(s) in the table that need to be corrected
2 Click to reveal the popup below:
3 Enter the name of the correct group and click
Version 3.0
Fast Variant Group Management
Purpose The node Fast Variant Group Management allows the administrator to quickly
update all authorizations on variant groups.
Note Authorizations on variant groups can also be managed manually via the
Query itself in the variant tree menu as described per End User Manual
(Chapter 6).
Getting started To access the Fast Variant Group Management program click
under the Variant Tools node of the IMG.
Screen view The view below shows the Fast Variant Group Management interface:
Version 3.0
Fast Variant Group Management, Continued
Screen The Fast Variant Group Management screen consists of four parts:
description
• Group selection – allows to select variant groups of which the administrator
wishes to manage authorizations
• Remove authorizations – allows to delete authorizations on variant groups
• Add authorizations – allows to add authorizations on variant groups
• Modification mode – allows the users to carry out modifications on variants
Group In the section ‘Group Selection’ the administrator chooses variant group(s) of which
selection he or she wishes to manage authorizations as shown in the view below:
The administrator can choose between:
• variant groups by inserting a from/to range in the appropriate fields, or
• only public groups by validating the box
Note If this box is left blank, the user &DEFAULT will be taken by default.
Remove This section allows the administrator to delete variant authorizations as shown in the
authorizations view below:
Choose between deleting:
• all authorizations by validating the ‘Remove authorizations’ box, or
• authorizations of one or several users by inserting a from/to range in the

appropriate fields
Version 3.0
Fast Variant Group Management, Continued
Add This section allows the administrator to insert variant authorizations as shown below:
authorizations
Choose between inserting:

• authorizations for all users by validating the ‘Add authorizations’ box, or
• authorizations for a range of users by inserting a from/to range in the appropriate
fields
Modification In the this part of the screen the administrator can manage the following:
mode
• To manage modification mode of variant groups, enter a figure between 0 and 2

0 – the variant group will not be displayed to the selected user group
1 – the variant group will be displayed to the selected user group
2 – modification is allowed to users in the selected user group
• To manage modification mode of variants, enter a figure between 0 and 2
0 – the user can execute variants of the group
1 – the user can create variants in the group
2 – the user can modify variants in the group
• To manage variant subgroup authorizations, put a cross or leave blank
x – a user can add subgroup(s) to variant group
blank – the user cannot add subgroup(s) to variant group
Execute Click to execute changes to variant groups.
Version 3.0
Section C: Delete Temporary Objects
Overview
Purpose The Delete Temporary Objects section allows the administrator to check that all
Query temporary objects that need deletion have actually been deleted.
When running normally, the Query deletes all temporary objects automatically. But
if it gets interrupted for any reason, those objects may not be deleted.
It is up to the administrator to decide how often this tool should be used.
Getting started To access the Delete Temporary Objects tool click

under the Global Tools node of the Query IMG.
Screen view The view below displays the Delete Temporary Objects tool interface:
Version 3.0
Overview, Continued
Screen The table is divided into five sections:

description
• Object name – name of the object that needs to be deleted
• Object type – kind of object that needs deletion. There are five object types:
screens (S), reports (R), table contents (C), Oracle views (V) and database tables
(T).
• Mandant – where (i.e. in which client) the object was generated
• User name – name of the user who created the object
• Date – date on which the object was generated
Deleting The Delete Temporary Objects tool allows the administrator to delete any temporary
temporary objects created by the Query. It is especially useful for deleting temporary objects of
objects users who have not used the Query for a long time, or who no longer use that system.
To delete temporary objects follow the steps below:
1 Selects the objects to delete by:
• clicking on one or more objects displayed in the table, or
• entering a user name and/or an object type (report, screen, table

content, table and view) and clicking to filter selected entries, or
• selecting all entries by clicking the icon
Note This last method is strongly advised as it allows the

administrator to delete all temporary objects at the same time.
2 Deletes selected entries by clicking the icon
Version 3.0
Section D: Mapping Authorizations to Tables
Overview
Purpose This functionality is necessary to ensure that all authorizations are respected for the
shadow tables.
Example
If a user has a profile that does not allow data to be viewed in infotype 0008, then the
entry 0008 – YPSQL0008 must be made in the table so that this user cannot report
on infotype 0008 in the shadow table.
Getting started To access the Mapping Authorizations to Tables program click

under the Global Tools node of the Query
IMG.
This will reveal the following information popup window:
Simply click on or press <Enter> to access the screen where links between
tables and infotypes are customized.
Screen view The view below shows the screen where links between shadow tables and infotypes
are customized:
Version 3.0
Overview, Continued
4 types Four types of links can be created:
• between infotypes (infotype number)and shadow tables
• between pension data (PENS) and pension tables
• between payroll data (PAYR) and payroll tables
• between time data (TIME) and time tables
Creating The table below describes how to create shadow table authorizations:
authorizations
Step Action
1 Click to access the screen

where authorizations can be mapped from SAP to ARINSO shadow
tables
2 Enter infotypes and tables from which the authorizations should be

mapped.
3 Click to save authorization links.
Version 3.0
Section E: Chapter Summary
Overview
Introduction At the end of this chapter on Global Tools the administrator should be able to:
• define Query Parameters
• carry out administrative tasks on variants via the Variant Tools node
• delete temporary objects in the Query via the Delete Temporary Objects node
• link shadow tables to infotypes via the Mapping Authorizations to Tables node
Topic See Page
Query Parameters 69
Variant Tools 72
Delete Temporary Objects & Mapping Authorizations to Tables 74
Version 3.0
Query Parameters
Introduction At the end of the section on Query Parameters the administrator should be able to
define parameters that will be used by default every time the Query is launched.
More particularly, the administrator should be able to define:
• User Groups
• System Parameters
• Administrator Parameters
• User Parameters
• Path Parameters
User group The Query administrator should now be able to access the User Groups node in order
to group users together so they can be assigned the same Query parameters.
In this node the administrator learnt how to:
• create user groups
• add users to a group
• delete users from a group
System The Query administrator should now be able to access the System Parameters node
parameters to define parameters for the whole system.
More particularly, the administrator should be able to define the following three
categories:
• SQL options, i.e.:
o database user in order to specify where Oracle procedures have been
installed
o begin view name in order to be able to view the data
• authorization object and field in order to be able to use the Profile Generator to
set up the profiles for the users.
• wage types to use in the shadow table extraction for infotype 0008:
o Min Lgart (default wage type for minimum salary)
o Max Lgart (default wage type for maximum salary)
o Per. Lgart (default wage type for periodic salary)
o Ann. Lgart (default wage type for annual salary)
Version 3.0
Query Parameters, Continued
Administrator The Query administrator should now be able to access the Administrator Parameters
parameters node to define parameters per client.
In this section the administrator learnt how to define the SQL Optimization and
Authorization parameters, which are:
• SQL Optimizer for changing the way the native SQL statement is generated.
Use “Pernr In” for a normal process and “Pernr Tab” for a process through
multiple queries
• SQL Hint for optimizing reports. Choose between: Rule, All Rows and index
• Use View for storing the program code in a view.
• Use Table for using an Oracle procedure to select data, which is then put into a
temporary table.
• Check Generated SQL for executing a syntax check on database level.
• Number of days between refresh PD authorization
• Number of days between refresh pension authorization
• Number of concurrent queries to be run at the same time
User The Query administrator should now be able to access the User Parameters node to
parameters set parameters for users or user groups.
In this tool the administrator has to decide:
• Which country grouping and currency should be used by default in the Query
• Whether to show the technical name of fields when selecting fields in the list of
fields on the main interface
• Whether to show all fields – even unauthorized ones – when selecting fields in
the list of fields on the main interface
• Which Query type to use by default: PA (employees) or PB (applicants)
Version 3.0
Query Parameters, Continued
User • Whether to show a confirmation popup when exiting the query

parameters
(continued) • What the Population Selection tab on the Query main interface should look like
• Whether the Query should count the population when it is first launched
• What the default start-up filter should be
• Which default output mode to use (resulting list, layout wizard, HR report,
Cloud or pyramid)
• What the Layout List tab on the Query main interface should look like
• Whether to show a confirmation popup when exiting the resulting list
• Which spreadsheet to use by default
• Which description to use for background jobs
• Whether to specify dates when creating variants
Path The Query administrator should now be able to access the Path Parameters node in
parameters order to specify path directories of Query elements.
The administrator learnt to locate six types of parameters:
• CLD_PROG (Cloud program)
• GLB_TEMP (temporary files)
• GLB_CAPT (capture files)
• GLB_ONLI (online help files)
• OUT_ACSS (Access Download program)
• OUT_ACSD (Access Download database)
Version 3.0
Variant Tools
Introduction At the end of the section on Variant Tools the administrator should be able to carry
out the following administrative tasks on variants:
• download and upload variants
• delete variants
• manage authorizations on variants
Download/up- The administrator should now be able to access the Download / Upload Variants
load variants node to download and upload variants from different clients.
More particularly, the administrator learnt how to:
• do a download by:
o logging on to the source client
o selecting the variants to download
o defining where they should be located
• do an upload by:
o logging on to the target client
o selecting the variants to upload
o specifying to which user and variant group they should be uploaded
Correct The administrator should now be able to access the Correct Variants node in order to
variants correct or delete:
• variants containing fields that do not exist in the IMG
• variants referring to a non-existing user or public group
Version 3.0
Variant Tools, Continued
Fast variant The administrator should now be able to access the Fast Variant Group Management
group node to quickly update authorizations on variant groups by defining the following:
management
• Group selection, which allows to select variant groups of which the
administrator wishes to manage authorizations
• Remove authorizations, which allows to delete authorizations on variant groups
• Add authorizations, which allows to add authorizations on variant groups
• Modification mode, which allows the users to carry out modifications on

variants
Version 3.0
Delete Temporary Objects & Mapping Authorizations to
Tables
Temporary At the end of the section on Delete Temporary Objects the administrator should be
objects able to delete temporary objects in the Query. He or she simply has to select the
objects to delete and click the “delete” icon.
It is advised to delete all temporary objects in the Query.
Mapping At the end of the section on Mapping Authorizations to Tables the administrator
authorizations should be able to ensure that all authorizations are respected for the shadow tables.
to tables
Four types of links can be created:
• between infotypes and shadow tables
• between pension data and pension tables
• between payroll data and payroll tables
• between time data and time tables
Version 3.0
Chapter 6
Customizing Tools
Overview
Introduction The Customizing Tools node allows the administrator to manage:
• Areas and Fields

• Special Graphics (Cloud)
• Layout Wizard
• Start-up Filter and
• Other Tools
as shown in the view below:
For information … See section … On page …
Fields and Areas A 76
Special Graphics B 113
Layout Wizard C 121
Start-up Filter D 130
Other Tools E 136
Chapter Summary F 155
Version 3.0
Section A: Fields and Areas
Overview
Introduction The administrator can add areas and fields customized in the HR system into
ARINSO HR Query. Whatever is customized in this section forms the list of possible
fields for the end user to choose from.
Here, the administrator can define what data can be retrieved by the Query, how it is
retrieved and how the end user chooses to retrieve it.
The Fields and Areas node allows the administrator to:
• create, modify and delete areas and fields
• link areas and fields
• manage relations between tables
• manage conditions on tables
Here is a view of the Fields and Areas node with its customizing options:
Topic See Page
Field Customizing 78
Creating Standard Fields 82
Creating Complex Fields 85
Creating Virtual Fields 88
Creating Referenced Date Fields 90
Version 3.0
Overview, Continued
In this section (continued)
Topic See Page
Creating HR Plan Fields 92
Text for Field 96
View, Modify and Delete Fields 96
Area Customizing 100
Link between Areas and Fields 77
Relationship between Tables 104
Conditions on Tables 111
Version 3.0
Field Customizing
Purpose In this part of the Query Implementation Guide, the administrator has the possibility
to customize (i.e. create, modify and delete) fields. See below for a list of possible
field types to customize.
Getting started To access the Field Customizing screen click under the
Fields and Areas node of the Query IMG.
Main screen The view below displays the Field Customizing main screen giving a list of existing
view fields:
Description The main interface consists of two sections:
• An icon bar, and
• A table of existing fields.
Version 3.0
Field Customizing, Continued
Icons A series of icons, which are standard in SAP, is available on the Field Customizing
main interface.
The table below gives a brief description of each of them:
Icon … Allows the administrator to …
create new fields
find where a field is used (in variants, start-up filters or clouds).

This function is useful for making a distinction between fields that
can be deleted and those that cannot (fields that are being used
cannot be deleted).
display details on fields
modify fields
delete fields
show all fields
sort fields ascending
sort fields descending
do a fast creation of standard fields
Field types There are five types of fields for the administrator to customize:
• Standard fields
• Complex fields
• Referenced date fields
• Virtual fields and
• HR Plan fields
Version 3.0
Field The table below explains the different data fields that can be selected:
definitions
Field type Explanation
Standard fields Standard fields are descriptive data fields retrieved directly from SAP.
Example
Company code is a field used to separate one country from another.
Complex fields A complex field is an SAP data field for which certain conditions apply in the
selection.
Example
If a user wants to retrieve an amount for ‘Car Allowance,’ but is only

interested in a bonus amount for that particular wage type, a complex field
would have to be set up to say, “Retrieve additional payments amount
(PA0015-BETRG) only when additional payments wage type (PA0015-
LGART) = Car allowance”.
Virtual fields Virtual fields do not actually exist in the SAP database, but are interpretations
of fields stored in the database.
Example
In SAP, sex is stored as a 1-digit integer (either 1or 2). Since this is not very
meaningful for end users a ‘virtual field’ is created in order to output “Male”
or “Female” rather than 1 or 2.
Referenced date The referenced date field is used to define fields that are not available in the
fields database, but can be calculated by getting the difference between a reference
date and an existing database date field.
Example
• Age is derived from the date of birth and the reference date.
• Seniority is derived from the seniority date and the reference date.
Version 3.0
Field definitions (continued)
Field type Explanation
HRP fields An HRP field is used only in the population settings to tell the query how to
navigate through the PD structure to retrieve employees.
Example
If the user wants to report on all the personnel belonging to positions in a

particular organizational unit, then an HRP field with evaluation path O-S-P
should be set up.
Accessing To access the field types list click to reveal the following screen:
fields
Click on radio button to access one of the five field types and validate the selection
by clicking .
Next Next comes a description of each field type (standard, complex, referenced date,
virtual and HR Plan) as well as a description of the procedure to follow to create new
fields.
Note When creating new fields, the administrator can copy previous entries.
Version 3.0
Creating Standard Fields
Standard fields Standard fields are extracted directly from the SAP HR database.
This section describes how to create a standard SAP HR field. It is possible to

change the field description according to the needs of the client.
Interface for The view below shows the screen where standard fields are customized:
creating
standard fields
The interface used for creating new standard fields consists of two tabs:
• Definition – defines and locates the field on which to query
• Text for field – allows the administrator to set up a link between the field being
created and its corresponding text field (see page 96 for a description of this tab)
Version 3.0
Creating Standard Fields, Continued
Definition tab The Definition tab consists of three sections as shown in the view below:
• Field Definition – allows the administrator to enter which database table and
field it should retrieve from and define query type to use
• Field Description – column 1 defines the language, column 2 gives a short text
description and column 3 a long text description of the field
• Field Location – locates the field in an area
Example See previous page for an example of a Definition tab.
Creating a In the table below the administrator will find the procedure for creating a standard
standard field field:
1 Accesses standard fields screen as described on page 81
2 Defines the field to be queried on by entering which database table and

database field it should retrieve from and select query type: PA
(employee data) or PB (applicant data).
Note Field ID does not have to be entered by the administrator. It

is filled in automatically by the Query.
3 Describes the field in the Field Description table by entering:

• the required language in column 1
• a short field description in column 2
• a long field description in column 3
Note The same field can have descriptions in several languages.

Descriptions are defaulted from standard SAP. To retrieve
descriptions from SAP click .
Version 3.0
Creating Standard Fields, Continued
Creating a standard field (continued)
4 Assigns the new field to an area in the Field Location table
Note If the area to which the field has to be assigned does not
exist, it can be created by clicking on in Field Location
(see page 102 for instruction on how to create an area).
5
Clicks to test if the field has been created correctly (e.g. description
in a field has to be unique so that a user can select fields). According to
the results obtained do one of the following:
If the result is … Then …
correct
• click
• create a transport request as

prompted and click
incorrect • make the appropriate

corrections (i.e. correct
what is highlighted in red)
• click to re-test field
• click to save field
6 Accesses the Text for field tab if required to define a text for the field
created and click to save.
Note This step is optional (see page 96 for more information on

this tab)
Version 3.0
Creating Complex Fields
Complex fields Complex fields are stored in the database but their output is the result of a more
complex operation. They allow the administrator to add conditions on the selection
(hence there is an additional tab compared to standard fields: Conditions).
Interface for The view below shows the interface for creating complex fields:
creating
complex fields
The interface used for creating new standard consists of two tabs:
• Definition – defines and locates the field on which to query (this tab is the same
as for standard fields, see page 83 for a description)
• Conditions – allows to put conditions on a selected field
• Text for field – allows to set up a link between the field being created and its
corresponding text field (see page 96 for a description of this tab)
Version 3.0
Creating Complex Fields, Continued
Creating a The table below describes the procedure for creating a complex field:
complex field
1 Accesses complex fields screen as described on page 81
2 Defines field in Definition tab as described for standard fields on page

83 (steps 2 to 4).
Note For an example of a Definition screen see view on previous

page
3 Selects the Conditions tab and specifies the restrictions that apply when
the user queries on the field defined earlier as shown in the following
screen:
The table below gives an overview of available operators used for

defining conditions:
Operator Function
AND Matches the previous and the next criteria.
OR Matches either the previous or the next criteria.
NOT Does not include the next criteria.
(( )) Brackets logically group expressions.
Field ID Defines the name of the field chosen.
Operators Specify what conditions should be applied to the fields
Value Narrows down selection criteria.
Version 3.0
Creating Complex Fields, Continued
Creating a complex field (continued)
4 Repeats step 5 as per standard fields (page 83) to test and save created
field
5 Defines text for field if required (see page 96 for more information on
this tab)
Version 3.0
Creating Virtual Fields
Virtual fields Virtual fields do not actually exist in the SAP database, but are interpretations of
fields stored in the database.
Example
In SAP, sex is stored as a 1-digit integer (either 1or 2). Since this is not very
meaningful for end users a virtual field is created in order to output “Male or
Female” rather than 1 or 2.
Interface for The view below shows the interface for creating virtual fields:
creating
virtual fields
The screen for creating new virtual fields consists of two tabs:
Version 3.0
Creating Virtual Fields, Continued
Creating a The table below describes the procedure used to create a virtual field:
virtual field
1 Accesses virtual fields screen as described on page 81

83 (steps 2 to 4).

page
the user queries on the field defined earlier as shown in the following
screen. Enter conditions, i.e. field and conversion value.
Example
Note In the example above, one field value corresponds to one

conversion value. But a conversion value can have several
field values as shown in the example below:
field
Version 3.0
Creating Referenced Date Fields
Referenced Referenced date fields allow users to report on ‘lengths of time’ that are not stored in
date fields SAP.
Example
Age is calculated by the difference between the reference date on the Query main
screen and date of birth stored in SAP.
Interface for The view below shows the interface for creating referenced date fields:
creating
referenced
date fields
The screen for creating new referenced date fields consists of two tabs:
Version 3.0
Creating Referenced Date Fields, Continued
Creating a In the table below the administrator can find the procedure for creating a referenced
date field date field:
1 Accesses referenced fields screen as described on page 81

83 (steps 2 to 4). The field name must be of type DATE. This definition
gives the database field that will act as a ‘start date’ for calculating the
length of time.

page
the user queries on the field defined. Enter date mode of referenced date
field. All possibilities are listed below:
Example
In the example below the date mode “Number of years” is chosen for
referring to the field ‘Age’.
field
Version 3.0
Creating HR Plan Fields
HR Plan fields HR Plan fields can only be used for population selection. It enables the selection of
population through an evaluation path in PD.
Example
If the user wants to report on all the personnel belonging to positions in a particular
organizational unit, then an HRP field with evaluation path O-S-P could be set up.
Interface for The view below shows the interface for creating HR Plan fields:
creating HR
Plan fields
The screen for creating new referenced date fields consists of two tabs:
Version 3.0
Creating HR Plan Fields, Continued
Creating an The table below describes the procedure for creating an HR Plan field:
HR Plan field
1 Accesses HR Plan fields screen as described on page 81

83 (steps 2 to 4).
Note For an example of a Definition screen see previous page
the user queries on the field defined:
See overleaf for a description of conditions.
field
Version 3.0
Conditions The table below describes the options available in the Conditions tab:
Part Description
Plan version A 2-digit number. Version numbers are used to differentiate between
different organizational plans. If this field is left blank the system will
pull from all plan versions.
Object type Use this field to confine an inquiry to a particular object type. For
example, S represents a position, Q represents a qualification, E
represents a business event, etc.
Search string A search or lookup field. It allows you to find the object you want to
work with (e.g. organizational unit, business event) when you do not
know its object ID.
Object status A 1-digit code that represents a status (1 – active, 2 – planned, 3 –

submitted, 4 – approved, or 5 – rejected).
Note Leave this field blank to include objects of ANY status in an

inquiry/report.
Evaluation path An evaluation path allows you to focus inquiries/reports on objects that
are linked by certain relationships. For example, you may want to focus
on objects involved in the relationship: organizational unit > position >
employee or applicant.
Note If you do not wish to use evaluation paths, leave this field
blank.
Planning status A 1-digit code that represents a status. Statuses allow you to move
objects and infotypes through a planning cycle. The cycle is as follows:
Planned/2 Æ submitted/3 Æ approved/4 or rejected/5 Æ active (if

approved)/1 or planned/2 (if rejected)
Note It is not mandatory to use planning cycles. You can create

objects with active status immediately.
Version 3.0
Conditions (continued)
Part Description
Status vector This field contains a list of statuses (1 – active, 2 – planned, 3 –

submitted, 4 – approved, or 5 – rejected) for Relationship infotypes. The
list allows you to determine which objects are documented in
inquiries/reports, by selecting objects according to the status of their
Relationship infotypes.
You may request more than one status. For example, to include statuses
1, 2 and 3, enter 123 with no spaces or commas.
Note If you do not wish to use Relationship infotype status as

reporting criteria, leave the Status vector field blank.
Status overlap This check box is used in conjunction with the Status vector field. The
check box allows you to run a simulation showing the results of
activating Relationship infotypes. The simulation activates all
Relationship infotypes with the statuses listed in the Status vector field.
Version 3.0
Text for Field
Purpose The Text for Field tab allows the administrator to set up a link between the field
being created and its corresponding text field (in SAP, corresponding texts for fields
are often stored in separate tables).
Text for field The view below shows an example of how the main screen for creating text for a
tab view field is filled:
Example
In the example above:
• Company code is stored in field PA0001-BUKRS
• Company code text is stored in field T001-BUTXT
• Link between PA0001 and T001 is BUKRS
Version 3.0
Text for Field, Continued
Description Field and table data – defines which field the text for a field is stored in.
Conditions parameter – sets the conditions to obtain the current text fields to be used
in the layout and possible entry dropdown.
Defining text Texts for fields can be defined for standard and complex fields only. The table below
for field describes how to specify the text for a field.
Step Action
1 Enter text table with text to define.
Note The field ID is entered automatically by the Query
2 Enter field of this table to define which field text is retrieved from
table.
3 Enter field conditions. These conditions give values to the key fields
of the text table to form conditions on how to retrieve the text field.
The value can be one of the following:
• A value determined by the administrator
• A field name
• One of the following (using upper cases):
o #LANGU (login language)
o #MOLGA (country grouping as defined by default in user

parameters)
o #BEGDA (begin date on the Query main selection screen)
o #ENDDA (end date on the Query main selection screen)
4
Click on
Version 3.0
View, Modify and Delete Fields
Introduction Any field created by the administrator can be viewed, modified or deleted using the
following icons:
• used to display fields
• used to modify fields
• used to delete fields
View a field To view a field, the administrator can choose one of either possibilities below (back
on the Field Customizing main screen):
Possibility The Administrator …
1 Click to reveal the following screen:
Enter a field to display and click to reveal the correct field screen
in display mode.
2 Select an existing field on the Field Customizing main screen and

click to reveal the correct field screen in display mode.
Version 3.0
View, Modify and Delete Fields, Continued
Modify / delete The table below describes how to modify or delete fields:
1 • from the main screen clicks (modify) or (delete), or
• from the display screen clicks (modify) or (delete)
2 Modifies/deletes field contents as appropriate.
3
Clicks to test if the new values are correct.
4 If the test was carried out successfully, clicks to reveal a transport

request pop-up.
5 Creates a transport request as prompted
Version 3.0
Area Customizing
Purpose In this part of the IMG, the administrator can customize areas, i.e. display, create,
modify and delete areas.
Areas are a way of grouping together fields for ease of use. It is often useful to group
according to SAP infotypes, but not essential. Areas are fully customizable to suit the
needs of the client and contain any fields the administrator assigns to them.
Any areas set up here will be available to the end user as possible field entries on the
Query main screen.
Accessing the To access the Area Customizing tool click under the Fields
program and Areas node of the Query IMG.
Screen view The view below shows the Area Customizing main interface from where areas are
managed:
The main screen is made up of two parts:

• An icon bar, and
• A table of existing areas
Version 3.0
Area Customizing, Continued
Icon toolbars A series of icons, which are standard in SAP, is available on the main screen. All
icons are described in the Field Customizing section, page 79.
Display an To view an area select the required area and click the icon to reveal the screen
area below in display mode:
Modify an To modify an area select the required area and click the icon to reveal a screen
area similar to the one above but this time in change mode, where query type, language
and area text can be modified.
Note Remember to click to save modifications
Version 3.0
Create an area To create an area, follow the procedure described in the table below:
Stage The Administrator …
1
Clicks icon to reveal the following screen:
2 Enters an area identifier, query type, language and area description (e.g.
if you have created an area called PA0006, you may wish to give it the
text “Addresses”)
3 Click to save new entries
Version 3.0
Areas can also be created in:

Note
1. The ‘Field Customizing’ node via the Field Location section on the interface for
creating fields as shown in the view below:
To create a new area click and entered required entries as explained above
2. The ‘Link between Areas and Fields’ node (see page 104)
Version 3.0
Link between Areas and Fields
Introduction When created, fields must be assigned to areas to be available for the user. Areas are
a way of grouping together fields for ease of use. It is often useful to group according
to SAP infotypes, but not essential.
Getting started To access the Link between Areas and Fields screen click
under the Fields and Areas node of the Query
IMG.
Screen view The view below shows the interface for managing links between fields and areas:
The main interface is divided into two tables:
• one with the list of areas, and
• another one with the list of fields per area.
Version 3.0
Link between Areas and Fields, Continued
In this node This node allows the administrator to:
• add or remove fields from an area, and
• create, change or delete areas.
Adding fields To add fields to an area, the administrator should follow the procedure described
to an area below:
1 Selects an existing area by:

• double clicking on it, or
• placing the cursor on it and then clicking .

This entry will reveal all the fields belonging to the selected area, which
is now highlighted in blue.
2 Inserts a new field in the area by clicking on to reveal the screen
below:
Version 3.0
Adding fields to an area (continued)
3 Selects the fields to insert by validating the Select column as shown in

the view above.
Note The icon allows the administrator to see all fields that are
not assigned to any area
4
Clicks to validate selections and go back to the main screen
5 Saves by clicking . This will call for a transport request. Create a

transport request as prompted and click to validate.
Deleting fields To delete fields from an area, follow the procedure below:
from an area
1 Selects an existing area by:

• double clicking on it
• positioning the cursor on it and then clicking

This entry will reveal all the fields that exist in this area. The selected
area is now highlighted in blue.
2 Selects the fields(s) to delete in the ‘Fields in the area’ table
3 Clicks to delete selected entries
4 Saves by clicking . This will call for a transport request. Create a
transport request as prompted and click to validate.
Version 3.0
Creating areas See Area Customizing section (page 102) for instruction on how to create areas
The same field can belong to more than one area.

Note
Version 3.0
Relationships between Tables
Introduction Sometimes, for data consistency, it does not make sense to report from one table
without another. Indeed, some SAP infotypes use data coming from other infotypes.
This feature of the Query IMG allows the administrator to specify if a certain table
must also be reported from each time another table is reported from.
Getting started To access the Relationship between Tables program click

under the Fields and Areas node.
Screen view The view below shows the Relationships between Tables screen from where
relations can be displayed, created, modified and deleted:
Some infotypes are dynamically filled by other infotypes. Infotype 0021 (family)
fills in infotype 0106 (related persons) automatically.
Infotype 0106 can contain more than one value for infotype 0021.
Infotype 0021 contains information about family and one record for each family
member.
Therefore, a link is required between infotype 0021 and each attached record in
infotype 0106
Version 3.0
Relationships between Tables, Continued
Example Using infotype 0021 and 0106, the administrator could create a link to:
• See all children of an employee
• Select a population restriction on infotype 0021 of ‘2’ (child)
• Take children’s names from infotype 0106
Note A link between tables 0021 and 0106 would be necessary; otherwise all
family members for all employees would be selected.
Creating table To create relations between tables, the administrator should follow the steps in the
relations table below:
Step The administrator …
1
Clicks to access the following screen:
Version 3.0
Relationships between Tables, Continued
Creating table relations (continued)
Step The administrator …
2 Specifies the two tables for which a relationship should be established
3 Specifies the conditions: fields and field operators
4
Clicks to check if the relationship has been created correctly
5 Clicks on if the test was carried out successfully. This will call for a
transport request. Create a transport request as prompted and click to
validate.
The administrator can also modify, delete or view more relationships using the icons
Note
at the top of the screen.
Version 3.0
Conditions on Tables
Introduction This functionality is used when users wish to report on fields belonging to tables for
which no BEGDA and ENDDA fields are specified. In this case, it is necessary to
put conditions on the BEGDA and ENDDA fields so that the Query knows how to
report on it.
Screen view The view below shows an example of a filled ‘Conditions on tables’ screen:
Example If client does not use SAP payroll, there could be a custom table used to store payroll
results.
This table has a PERNR field and a field called PAYDATE (a date field). The
condition is that PAYDATE must fall within the date range entered on the Query
main screen.
Version 3.0
Conditions on Tables, Continued
Creating To create conditions on tables, the Query administrator should follow the procedure
conditions on below:
tables
1 Clicks to access the ‘Conditions on Tables’ screen as shown on the

previous page
2 Enters the table name on which conditions need to be set either:
3 Defines the fields, field operators and selection dates. For selection dates
the administrator has the choice between (the list can be accessed by
clicking F4):
• BEGDA_LA (layout begin date, i.e. the begin date defined for
layout restrictions in the Query)
• ENDDA_LA (layout end date, i.e. the end date defined for layout
restrictions in the Query)
• BEGDA_SEL (selection begin date, i.e. the begin date defined for
population restrictions in the Query)
• ENDDA_SEL (selection end date, i.e. the begin date defined for
population restrictions in the Query)
• REF_DATE (reference date, i.e. the reference date defined on the

Query main screen)
4
Clicks to test if the selection is correct
5 Clicks on . This will call for a transport request. Create a transport

request as prompted and click to validate.
The administrator can also modify, delete or display more conditions using the icons
Note
at the top of the screen.
Version 3.0
Section B: Special Graphics
Overview
Introduction This section deals with the ARINSO Cloud program. The ARINSO Cloud acts as a
graphical tool, providing an easy way to display a three dimensional graph based on
data extracted by the ARINSO Query from information stored in an SAP-HR
database. It sets customized axes against the query data and generates graphs
according to the needs of the user.
The Special Graphics node contains the following customizing options:
Cloud Two aspects of ARINSO Cloud need to be customized. Whatever the administrator
customizing configures here will appear in the user’s possible entries on Cloud interface.
1. Scenarios – the graph axes
2. Ranges
Topic See Page
Cloud Scenario 114
Cloud Ranges 119
Version 3.0
Cloud Scenario
Introduction The administrator must customize the scenarios available for the user. A scenario
allows the user to display data extracted from the Query in a graphical way. For
example, a scenario could be created to contrast salary with seniority within your
organization.
The administrator can view, create, modify and delete scenarios using icons at the
top of the screen.
Access to cloud To access the Cloud Scenario configuration program click on

scenario under the Special Graphics node of the Query IMG.
Main screen The view below shows the initial Cloud Scenario configuration screen:
view
The Cloud Scenario screen is divided into the following areas:
• Icons – the administrator can create, view, modify or delete scenarios.
• Definition of scenarios – displays ID and description of scenarios used.
Version 3.0
Cloud Scenario, Continued
Creating Cloud scenarios are created via the following interface:

scenarios
This Cloud Scenario screen consists of three tabs:
• Cloud Definition (as shown in the view above),
• Axis Definition (see below for a screen view), and
• Other Fields (see below for a screen view).
The table below describes how to create a Cloud scenario:
1
Clicks on to access the screen displayed above
2 Defines the scenario by entering a scenario ID and query type (employee

data PA / applicant data PB) as well as a language and a description of
the scenario being created
Version 3.0
Creating scenarios (continued)
3 Accesses the Axis Definition tab and enters axis details to be displayed
concerning the selected employees or applicants. The field should
indicate where axis data will be retrieved from. This can be done via the
following interface:
The following information needs to be entered:
• Axis X:
o Fill in field ID
o According to the type of field selected choose one of the two

possibilities (see overleaf):
Version 3.0
3
If you selected … Then …
(cont.)
a continuous field, i.e. a field • validate the ‘Continu’ box

consisting of non-distinct units
(e.g. annual salary) • enter a minimum and
maximum value
• select an interval
a discrete field, i.e. a field • enter a range. A range is

consisting of distinct units (e.g. used to display the data in
company code) one axis on intervals (see
page 119 for more
information on ranges) or
• nothing
• Axis Y. To be filled in the same way as axis X
• Distinction, i.e. determine the criterion according to which the

separation in the cloud graphs will be done (e.g. via sex). Specify:
o a field ID and
o a range
Version 3.0
4 Accesses the Other Fields tab and specifies other fields to be displayed if
required. For each employee or applicant reported on in cloud graph,
additional data can be displayed in an information box, as shown below:
To display those fields in a cloud, the administrator would have to enter

the following fields in the Other Fields tab:
5 Clicks to confirm selections.
Modify or
Click on and icons to modify and delete scenarios respectively.
delete
Version 3.0
Cloud Ranges
Introduction The administrator must customize the ranges available for the user. A Cloud scenario
uses a Cloud range to display the data from one axis in intervals. An example of a
range could be “age” consisting of three intervals, with definitions for each interval:
• 1 – 30 years (Young)
• 31 – 40 years (Middle aged)
• 41 – 65 years (Mature)
The administrator can create, modify or delete ranges.
Access to cloud To access the Cloud Ranges configuration program click under the
range Special Graphics node of the Query IMG.
Screen view The view below shows the initial Cloud Ranges configuration screen:
Version 3.0
Cloud Ranges, Continued
Creating In the table below the Query administrator will find the procedure for creating a new
ranges cloud range:
1 Clicks on icon to reveal the following screen:
2 Enters range type
3 Enters an interval (with a minimum and a maximum value) and a

description of the interval.
4 Clicks on to reveal a transport request screen. Create transport

request as prompted.
View, delete Click , and icons to display, delete and change Cloud ranges respectively.
and modify
ranges
Note Before deleting a range the administrator must check if it is not used in a
scenario with the (where used) icon.
Version 3.0
Section C: Layout Wizard
Overview
Introduction The Layout Wizard enhances the reporting layout and final presentation of an
ARINSO Query. It also allows the user to further process the data by doing
calculations and performing functions on fields.
This part of the Query IMG allows the administrator to customize:
• Layout Wizard Functions and
• Layout Wizard Calculations
Here is a view of the Layout Wizard node with its customizing options:
Topic See Page
Layout Wizard Functions 122
Layout Wizard Calculations 125
How to Create a Function Module 130
Version 3.0
Layout Wizard Functions
Purpose This part of the IMG allows the administrator to customize Layout Wizard
Functions. These allow the user to perform functions on a whole population
selection.
Example
A function AVERAGE can be used to get the average age of the population selected.
Functions are specified via the Layout Wizard tab of the Query tool as shown in the
view below:
A few functions are already customized in the ARINSO Query (e.g. average, count)
but the administrator can create new functions.
Accessing the To access the Layout Wizard Functions screen click

program under the Layout Wizard node of the Query IMG.
Version 3.0
Layout Wizard Functions, Continued
Screen view The view below shows the Layout Wizard Functions screen:
The Layout Wizard Functions screen consists of two sections:
• Definition – where the Layout Wizard function is defined
• Description – where the Layout Wizard function is described
Layout Wizard functions can be viewed, created, modified or deleted.
Version 3.0
Creating a A series of functions are already customized in the ARINSO Query (for an overview
layout wizard see list of functions below). But this list is not exhaustive and the administrator can
function easily create new functions by following the procedure below:
1 Accesses the screen for creating functions by clicking
2 Chooses the name of the new Layout Wizard function to be created
3 Enters function module, i.e. technical name of the function (for

instruction on how to create function modules see page 130)
4 Selects field type(s) by clicking . This will reveal a popup where the
administrator can determine for which type of fields the function will be
valid:
The eight field types are:

• Numeric (N)
• Integer (I)
• Float (F)
• Packed (P)
• Currency (X)
• Time (T)
• Date (D)
• Character (C)
Example
The function SUM cannot apply to a character field.
5 Gives a language and description for the function chosen.
Version 3.0
Creating a layout wizard function (continued)
6 Clicks to test if function has been defined correctly. According to the

results obtained do one of the following:
If the result is … Then …
correct
click
incorrect • make the appropriate

corrections (i.e. correct
what is highlighted in red)
• click to re-test function
• click to save function
Functions The table below describes the functions that are already customized in the ARINSO
Query:
Function Description
Average Calculates and displays an average for each grouping
Count Counts and displays the number of persons included in the

grouping
Decile Calculates and displays deciles for each grouping (see below)
Maximum Selects and displays the maximum figure for each grouping
Median Calculates and displays a median average for each grouping

(see below)
Version 3.0
Functions (continued)
Function Description
Minimum Selects and displays the minimum figure for each grouping
Quartile Calculates and displays quartiles for each grouping (see

below)
Addition Calculates and displays a sum total for each grouping
Note The median, quartile and decile functions are described as follows:
• The function MEDIAN returns the median of the given numbers. The median
is the number in the middle of a set of numbers; that is, half the numbers have
values that are greater than the median, and half have values that are less.
• The function QUARTILE returns the quartile of a data set. Quartiles are often
used to divide populations into groups. For example, you can use quartile to
find the top 25 percent of incomes in a population.
• The function DECILE returns the decile of a data set.
Version 3.0
Layout Wizard Calculations
Purpose In this part of the IMG, the administrator can customize Layout Wizard calculations.
Layout Wizard calculations allow the administrator to do calculations on the basic
data extracted from the database.
Example
Calculated fields are useful for calculating the yearly salary of an employee on the
basis of the monthly salary. To do so, take the employee’s monthly salary and
multiply it by the number of times the employee in question receives his or her salary
in a year (13.90 in the case of Belgium).
Getting started To access the Layout Wizard Calculations screen click

under the Layout Wizard node of the Query IMG.
Screen view The view below displays the Layout Wizard Calculations screen with the list of
existing Layout Wizard calculations:
The icons at the top of the screen allow the administrator to respectively create, view,
modify and delete scenarios.
Version 3.0
Layout Wizard Calculations, Continued
Customizing A series of calculations are already customized in the ARINSO Query. But the
calculations administrator can easily create new Layout Wizard calculations by following the
procedure below:
2 Chooses the name of the new Layout Wizard calculation to be created

(Function ID)
3 Enters function module, i.e. technical name of the function (for

instruction on how to create function modules see page 130)
Version 3.0
Layout Wizard Calculations, Continued
Customizing calculations (continued)
4 Selects a return type by pressing F4, i.e. determine how the function will
be returned or expressed. Possible values are:
• N (numeric)
• I (integer)
• F (float)
• P (packed)
• X (currency)
• T (time)
• D (date)
• C (character)
5 Enters the function to show, i.e. give a succinct description of the Layout
Wizard function that will be seen by the user.
Example
If a calculation is created which takes two values and multiplies them

together, then it would be useful for the user to see (&1 * &2) in this
field.
6 Defines output length, i.e. length of the result of the calculation (in
characters).
7 Specifies the function by entering language(s) and description(s)
Note Parameter names come automatically from the function to

show. For example, if the function (&1 * &2) was defined,
two parameters will be filled here: PARAM01 and
PARAM02.
8 Specifies the field types to be used for each parameter defined. See step
4 for an overview of all field types.
9
Tests the function by clicking and saves if it is correct.
Version 3.0
How to Create a Function Module
Introduction Two kinds of function modules can be used in the Query:
• Layout Wizard Calculations
• Layout Wizard Functions
Function modules have to follow a set of restrictions.
Layout Wizard This kind of function module is used when users want to do a calculation on a record
calculation in the Layout Wizard.
To create a function module go to transaction SE37 and press the

button. The following parameters must be entered in order for the function module to
be used in the Query:
1. Import
• An infinite number of import parameters can be entered
• There are no restrictions on parameter names
• Each parameter can be filled in with a value of the record (e.g. SUM will
have two import parameters, allowing the user to add two fields or
constants).
• Parameters can have a default value or be optional
2. Export
• The name of the export parameter should be: RETVA
• This parameter contains the result of the function module after processing
3. Table
Table parameters are not used. Any parameter entered here will not be taken into
account. However, the field “Optional” has to be flagged.
Version 3.0
How to Create a Function Module, Continued
Layout Wizard This kind of function module is used when users want to perform a function on a set
function of results in the Layout Wizard.
To create a function module go to transaction SE37 and press the

button. The following parameters must be entered in order for the function module to
be used in the Query:
1. Import. Three parameters have to be specified here:
• V_TEXTVAL: this parameter contains the text to be outputted before the

function result.
• V_DEFCURRENCY: this parameter gives the default currency to use

when outputting amount fields. It must be optional.
• V_TYPEFLD: this parameter gives the field types that are given as
parameter. It can be optional.
2. Export
• The name of the export parameter must be: V_VALUE.
• This parameter contains the result of the function module after processing.
Version 3.0
Section D: Start-Up Filter
Overview
Introduction The Start-up Filter limits the population to a particular sub-population. It is re-used
each time the user starts the Query until the user decides to remove or change it.
Example
If you frequently query on active employees who are part of the French section of
your company, a start-up filter can be established to extract only the employees
meeting these criteria.
The Start-up Filter node drills down to the following customizing option:
Topic See Page
Start-up Filter 133
Version 3.0
Start-Up Filter
Accessing the To access the Start-up Filter customizing program click under
program the Start-up Filter node of the Query IMG.
Screen view The view below shows the table where population filters are customized:
The first start-up filter restricts the population on which to query to male employees,
the second one to those employees belonging to company code BE01.
Version 3.0
Start-Up Filter, Continued
Create a filter The table below describes the procedure for creating a new population filter:
1
Clicks to reveal the screen below:
2 Enters the query type to use (employees PA / applicants PB)
Note The start-up filter ID is filled automatically by the system

(therefore this field is shaded).
3 Gives a language and a description for the filter being created
4 Defines population filter conditions. Enter a field, an operator and a

value for that field. For an overview of condition parameters see table
page
Version 3.0
Start-Up Filter, Continued
Create a filter (continued)
5 Clicks to test if the start-up filter has been created successfully
6 If the data are correct, clicks to save new filter. This will call for a
transport request. Create a transport request as prompted and click to
validate.
Version 3.0
Section E: Other Tools
Overview
Introduction The Other Tools node drills down to reveal the following customizing options:
Here is an overview of each option:
• Parameters of Programs – allows the administrator to link fields to PERNRS so

they can be used in HR reports
• Customizing the List of Persons – allows the administrator to customize the list
of persons
• Customizing Synchronizer – allows the administrator to transfer ARINSO

customizing
• Download/Upload Customizing – allows the administrator to download and

upload customizing
• Check the Customizing – allows the administrator to test fields and clouds
checking for errors
Topic See Page
Parameters of Programs 137
Customizing the List of Persons 139
Customizing Synchronizer 141
Download / Upload Customizing 146
Check the Customizing 152
Version 3.0
Parameters of Programs
Purpose One of the output options of the ARINSO Query is to run an SAP ABAP program –
called HR report – using the personnel selected by the Query.
If the program is a PNP program, or if the program has a parameter linked to a

PERNR, then the download will happen automatically.
If the program does not fulfill those criteria, then the Query administrator must
specify which field on the selection screen is to be filled by the personnel numbers
selected by the Query.
The Parameters of Programs node allows the administrator to link fields to personnel
numbers when executing an HR report.
Accessing the To access the Parameters of Programs tool click

tool under the Other Tools node of the Query IMG.
Screen view The view below shows the Parameters of Programs screen:
Program parameters can be viewed, created, modified or deleted.
Version 3.0
Parameters of Programs, Continued
Creating new To create new parameters of programs the administrator should follow the procedure
parameters below:
1 Clicks to reveal a screen similar to the one on the previous

page but this time in create mode.
2 Selects the program for which parameters need to be changed
3 Specifies the PERNR field to be attached to the program. This can be

selected by clicking or pressing F4.
Example
4 Clicks to save
View, modify To view, modify and delete parameters of program use (alternate between
and delete
parameters display and change mode) and .
Version 3.0
Customizing the List of Persons
Introduction This functionality allows the administrator to determine which fields will be
displayed when end users click the icon on the Query main selection screen to
view the list of persons meeting the selection criteria entered.
Accessing the To access the screen for Customizing the List of Persons click
program under the Other Tools node of the Query IMG.
Main screen The view below shows the main screen for customizing the fields for the list of
view persons:
Choosing fields The table below describes how to customize the fields to be displayed in the list of
persons:
Column Column Header Function
1 Query Type Customize the list for either employee (PA) or applicant
(PB) data by indicating the query type.
Note The Query type has to be entered before defining

the field.
Version 3.0
Customizing the List of Persons, Continued
Choosing fields (continued)
Column Column Header Function
2 Row Number The sequential number is used to differentiate between

records.
Note This number does not need to be entered by the

administrator. It is assigned automatically.
3 Technical Field Enter field(s) to be displayed in the list of persons.

ID
4 Technical Value Enter an ‘X’ to view the actual value in the SAP database for
the selected field.
5 Description Click this checkbox to see the description for fields in the
list. In order for this to function, there must be a “text for
field” created.
6 Sort Level Use this to indicate what order the fields in the list should be
sorted in.
7 Ascending / Indicate if the field should be sorted ascending (A) or

Descending descending (D).
8 Today Flag If the ‘Today Flag’ is selected for a field, then only data
relevant on the day of execution will be displayed for that
field, regardless of the dates used in the Query selection
criteria.
9 All Check this checkbox if you wish records to be output in the

result even if some of the fields are empty. The default is to
have this unchecked, which means that only records where
there are values in the field will be output.
Version 3.0
Customizing Synchronizer
Purpose ARINSO Query is transported with standard customizing in a set of tables. If the
client wishes to use ARINSO customizing as a base for its own, it is necessary to
transfer this customizing to the client’s tables.
This gives the client a basic set of customizing which can be used immediately by
end users, or as a base for more specific customizing.
The Customizing Synchronizer tool allows the manipulation of the following:
• Areas and fields

• Clouds
• Start-up filters
• Layout Wizard and
• Others (table relations, conditions on tables and reports)
Note Client customizing cannot be deleted with this tool. Only client
customizing which exists in the ARINSO customizing can be deleted.
Accessing the To access the Customizing Synchronizer screen click

Version 3.0
Customizing Synchronizer, Continued
Screen view The screen view below shows the Customizing Synchronizer interface:
Screen This screen consists of two sections:

description
• a series of icons and
• five tabs
Icons The following icons on top of the screen allow standard actions in SAP:
select all data in a table
deselect all data in a table
Version 3.0
Icons (continued)
activate all changes, i.e. permanently save changes in client

tables
delete data
copy data
undo previous actions since last activate
compare data between ARINSO and client tables
list data that are identical in ARINSO and client tables
list data that are different in ARINSO and client tables
Tabs The Customizing Synchronizer tool screen is made up of five tabs allowing you to
copy customizing from:
• Fields and Areas
• Cloud (scenarios and ranges)
• Start-up Filter
• Layout Wizard (functions and formulas)
• Others (table relations, conditions on tables and reports)
The customizing screens for field and area, cloud, start-up filter, layout wizard and
others have the same format (see next page for screen view):
Version 3.0
Tabs
(continued)
This table consists of three parts:
• the first two columns = ARINSO customizing
• the last two columns = client customizing
• the third column (the middle one) indicates whether data in ARINSO and client
customizing are identical or different using the following legend:
o indicates that data are identical
o indicates that data are different
Version 3.0
Using The table below describes how to use the Customizing Synchronizer tool. The same
ARINSO procedure applies for all tabs: Field_Area, Cloud, Start-up filter, Layout Wizard and
customizing Others.
Note To customize fields select the tab, double click on the area
you want to see the fields from. You are now in the fields customizing
screen, which is the same as for areas and all other tabs.
In order to … Carry out the following actions … To get the following result …
copy customizing 1. select ARINSO customizing Selected customizing is

highlighted red and copied to
2. click customer customizing.
ARINSO customizing has a

icon if field has been copied
delete customizing 1. select ARINSO customizing Selected customizing is deleted

from customer table
2. click on or
ARINSO customizing has a
icon if data has not been copied.
3. click to undo last
changes.
Note
Only ARINSO customizing can be

removed via the customizing tool.
Commit changes Click on . Check Transport request screen is

and create customizing before committing revealed.
transport changes
Important note The administrator must commit changes and create a transport request for changes to
be made.
Version 3.0
Download / Upload Customizing
Purpose The Download / Upload Customizing tool allows the administrator to easily
download client customizing and upload it to another client. This tool can be used for
several purposes:
• to synchronize two systems when they become out of synchronization
• to quickly transfer customizing from one client to another
• to save customizing in a text file
• to send customizing to ARINSO Products Support
Accessing the To access the Download / Upload Customizing program click

Screen view The view below shows the Download / Upload Customizing screen:
Version 3.0
Download / Upload Customizing, Continued
Description The Download / Upload Customizing screen consists of two tabs:
• Download Customizing and
• Upload Customizing
Both tabs have the same format. They allow to download and upload Fields and
Areas, Clouds (scenarios and ranges), Layout Wizard (functions and formulas),
Start-up filters and Others (table relations, conditions on tables, reports).
Downloading To download customizing follow the steps below:

customizing
Note In order to be able to download customizing the administrator must log
on to the source client
1 Selects the Download Customizing tab
2 Chooses to download one or more of the following elements:
• fields and areas
• clouds (scenarios and ranges)
• layout wizard (functions and formulae)
• start-up filter
• others (table relations, conditions on tables, reports)
To carry out selection use one of the following procedures:
• click to select all data contained in the element chosen

(all areas, all clouds, etc). The selection now has a icon or
• click to carry out a multiple selection via the following screen:
Version 3.0
Downloading customizing (continued)
2
(cont.)
Select the data to download. Once required data have been selected, they
are highlighted in yellow. Click to commit selected entries and then
to go back to the main screen.
The selection now has a icon, which means that only a part of the data
has been selected.
3 Back on the main screen selects file location (i.e. where the file should be
downloaded) by clicking to reveal a file location pop up. Enter
directory path and file name and click .
4 Clicks to execute download
Version 3.0
Ranges (Cloud), calculations (Layout Wizard), conditions (Others) and reports

Note
(Others) cannot be downloaded/uploaded directly when clicking .
The table below shows how to access Cloud ranges. The procedure for accessing
calculations, conditions and reports is the same as for ranges.
Step Action
1 Click to access the screen where Cloud scenarios can be

downloaded from:
2 Click at the bottom of that screen to access the screen where

cloud ranges can be downloaded from.
Version 3.0
Downloading The procedure for downloading/uploading fields also differs from the one described
fields above as explained in this table:
Step Action
1 Click on the main interface to access the screen where areas can be
downloaded from:
2 Select the area to which the fields to download belong (the area is now
highlighted in yellow)
3
Click to access the list of fields that belong to the selected area and
select the fields to download
Version 3.0
Upload To upload customizing follow the procedure below:

customizing
Note In order to be able to upload customizing the administrator must log on to
the target client
1 Selects the Upload Customizing tab
2 Chooses the file to import by clicking the icon in the ‘Load file from’
section to reveal the following popup screen:
3
Clicks to import file
4 Among the data just uploaded chooses to upload all or part of it.
To carry out selection use one of the following procedures:
• click to select all data contained in the element chosen

(areas, clouds, etc). The selection now has a icon or
• click to carry out a multiple selection via the following screen

(see step 2 of downloading procedure for a detailed description).
5 Clicks to execute upload
Version 3.0
Check the Customizing
Purpose This program allows the administrator to test the ARINSO Query customizing
checking for errors. It does a check on customized fields and clouds as well as
parameters like intervals, SQL procedures and authorization objects.
Examples of errors that could occur are: fields that do not exist, no description
defined for a field, crossing values in a range, language defined twice, conversion
error in a field, etc.
Warning: Checking the customizing could take a long time to execute.
Accessing the To access the Check Customizing program click

Screen view The view below shows the Check Customizing interface:
Version 3.0
Check the Customizing, Continued
Checking To check customized fields the Query administrator should follow the procedure
fields below:
1 Validates the ‘Check the Fields’ box
2 Enters fields to be checked
Note If nothing is specified here, all fields will be checked.
3 Validates the ‘Also check descriptions’ box to check field descriptions as

well. This is useful for checking that all fields have different names.
Note This could take a long time to execute.
4 Clicks to execute the check. When testing is complete the following

screen will appear indicating whether any errors occurred:
If there are errors, the draw tree will display them with an explanation of
the error incurred. The administrator can correct them by clicking on
and changing the entry.
Version 3.0
Check the Customizing, Continued
Checking To check clouds the Query administrator should follow the procedure described in
clouds the table below:
1 Chooses to check Cloud scenarios and/or Cloud ranges
2 Enters Cloud scenario key (in case checking Cloud scenarios was
selected)
3 Enters Cloud range (in case checking Cloud ranges was selected)
4 Clicks to execute the check. As per field check, a tree will appear
indicating whether any errors occurred. See step 4 of fields check.
Checking The following parameters can be tested via the Check the Customizing tool:
parameters
• Intervals
• Authorization objects
• Default user
• SQL procedures
The table below describes each option:
Checking the checkbox for … Will test whether…
Intervals all intervals are configured correctly as described

per Installation Manual
Authorization objects all authorization objects are correct
Default user all parameters for the default user contain at least
one value
SQL procedures Oracle procedures have been installed
Version 3.0
Section F: Chapter Summary
Overview
Introduction At the end of this chapter on Customizing Tools the Query administrator should be
able to:
• manage fields and areas via the Fields and Areas node
• customize ARINSO Cloud scenarios and ranges via the Special Graphics node
• customize Layout Wizard functions and calculations via the Layout Wizard node
• manage start-up filters via the Start-up Filter node
• customize other Query elements via the Other Tools node
Topic See Page
Areas and Fields 156
Special Graphics 160
Layout Wizard 160
Start-up Filter 162
Other Tools 163
Version 3.0
Areas and Fields
Introduction At the end of the section on Areas and Fields the Query administrator should be able
to customize fields and areas in the ARINSO Query so as to form a list of possible
areas and fields for the end user to choose from.
More particularly, the administrator should be able to:
• customize (create, modify and delete) areas and fields
• link areas and fields
• manage relations between tables
• manage conditions on tables
Field The administrator should now be able to access the Field Customizing node in order
customizing to customize (create, modify and delete) fields in the Query.
More particularly, the administrator learnt how to access the interface for
customizing five types of fields:
• Standard
• Complex
• Virtual
• Referenced date
• HR Plan
Version 3.0
Areas and Fields, Continued
Standard fields Standard fields are extracted directly from the SAP-HR database. For standard fields
the administrator should be able to:
• define the field by entering the database table and field it should retrieve from,
the query type to use, the language it should be customized in, a short and a
long text description as well as the area it should be located in
• enter a text for the field created (optional)
Complex fields Complex fields are fields for which certain conditions apply in the selection. For
complex fields the administrator should be able to:
• define the field as per standard field
• put conditions on the selected field using a list of operators
• enter a text for the field created (optional)
Virtual fields Virtual fields are interpretations of fields stored in the database. For virtual fields the
administrator should be able to:
• put conditions on the selected field by entering the field name and its conversion
value
Referenced Referenced date fields are calculated by getting the difference between a reference
date fields date and an existing database date field. For referenced date fields the administrator
should be able to:
• put conditions on the selected field by entering a date mode of referenced field
Version 3.0
HR plan fields HR Plan fields enable the selection of population through an evaluation path in PD.
For HR Plan fields the administrator should be able to:
• put conditions on the selected field by entering the following criteria (not all of
them are mandatory): plan version, object type, search string, object status,
evaluation path, planning status, status vector, status overlap.
Area The Query administrator should now be able to access the Area Customizing node in
customizing order to customize areas grouping fields together.
In this node the administrator learnt to:
• use the toolbar icons in order display, create, modify and delete areas
• customize areas by entering an area identifier, a query type, a language and an

area description
Link between The administrator should now be able to access the Link between Areas and Fields
areas and node in order to assign fields to areas.
fields
• add and remove fields from an area
• create, change and delete areas
Relationships The administrator should now be able to access the Relationships between Tables
between tables node in order to specify if a certain table must be reported from each time another
table is reported from. The administrator learnt to create relations between tables by
specifying the two tables (and more specifically which field in those tables) that must
be related.
Version 3.0
Conditions on The administrator should now be able to access the Conditions on Tables node when
tables no BEGDA and ENDDA fields are specified.
More particularly, the administrator should be able to create conditions on tables by

entering the table name on which conditions need to be set, the conditions being the
field and a corresponding selection date related by an operator.
Version 3.0
Special Graphics
Introduction At the end of the section on Special Graphics the administrator should be able to
customize the ARINSO Cloud.
More particularly, the administrator should be able to customize:
• Cloud scenarios
• Cloud ranges
Cloud The administrator should now be able to access the Cloud Scenario node in order to
scenarios customize scenarios that will be available for the end user. Cloud scenarios display
data extracted from the Query in a graphical way.
More specifically, the administrator should be able to:
• use the toolbar icons to create, display, modify and create Cloud scenarios
• customize Cloud scenarios by entering the following information:
o a scenario definition for which the administrator has to specify the ID,
query type (employee data PA / applicant data PB), language and
description of the scenario being created
o definition of the axes:
♦ For axis X: field ID and according to the type of field selected

(discrete or continuous) an interval or a range
♦ For axis Y: idem as for axis X
♦ For distinction: determine the criterion according to which the
separation in the cloud graphs will be done by specifying a field ID
and a range
o other fields to be displayed in the cloud graph if required
Cloud ranges The administrator should now be able to access the Cloud Ranges node in order to
customize Cloud ranges (used to display the data from one axis in intervals).
More particularly, the administrator learnt how to customize Cloud ranges by

entering a range name, an interval (with a minimum and a maximum value) as well
as a description of the interval selected.
Version 3.0
Layout Wizard
Introduction At the end of the section on the Layout Wizard the administrator should be able to
customize:
• Layout Wizard functions
• Layout Wizard calculations
Layout Wizard The administrator should now be able to access the Layout Wizard Functions node to
functions customize Layout Wizard functions, thereby allowing users to perform functions on
a population selection.
• choose the name of the new Layout Wizard function to be created
• create a function module
• determine for which types of fields the function will be valid
• choose a language and a description for the function being created
Layout Wizard The administrator should now be able to access the Layout Wizard Calculations node
calculations to customize Layout Wizard calculations, thereby allowing users to do calculations
on the basic data extracted from the database.
• choose the name of the new Layout Wizard calculation to be created
• create a function module
• determine for which types of fields the function will be valid
• enter the function to show, i.e. give a succinct description of the Layout Wizard
function that will be seen by the user
• define the output length, i.e. the length of the calculation result
• enter a language and a description for the calculation being created
Version 3.0
Start-up Filter
Purpose At the end of the section on Start-up Filters the administrator should be able to
customize start-up filters to limit the population to a particular sub-population.
More particularly, the administrator should be able to access the screen where start-
up filters are customized in order to enter the following:
• query type to use
• a language and a description for the filter being created
• population filter conditions: a field, an operator and a value for that field
Version 3.0
Other Tools
Introduction At the end of the section on Other Tools the administrator should be able to:
• define parameters of programs
• customize the list of persons
• use the Customizing Synchronizer tool
• download and upload customizing
• check customizing
Parameters of The administrator should now be able to access the Parameters of Program node in
programs order to link fields to PERNRS so they can be used in HR reports.
More particularly, the administrator should be able to customize parameters of

program by:
• selecting the program for which parameters need to be changed
• specifying the PERNR field to be attached to the program
Version 3.0
Other Tools, Continued
List of persons The administrator should now be able to access the List of Persons node in order to
determine which fields will be displayed in the list of persons.
More particularly, the administrator should be able to use the following fields in
order to customize the list of persons:
• Query Type: used to customize the list for either employee (PA) or applicant
(PB) data
• Technical Field ID: used to list the field(s) to be displayed in the list of persons
• Technical Value: used to view the actual value in the SAP database for the
selected field
• Description: used to see the text for field in the list
• Sort Level: used to indicate what order the fields in the list should be sorted in
• Ascending / Descending: used to indicate whether the field should be sorted

ascending (A) or descending (D)
• Today Flag: used to display only data relevant on the day of execution
• All: used to output records in the list even if some of the fields are empty
Customizing The administrator should now be able to access the Customizing Synchronizer node
synchronizer in order to transfer ARINSO customizing tables to his or her customizing tables.
• use the toolbar icons to copy or remove customizing
• transfer areas and fields, clouds, start-up filters, Layout Wizard and others
(relations, conditions and reports)
Version 3.0
Download and The administrator should now be able to access the Download / Upload Customizing
upload node in order to download client customizing and upload it to another client.
customizing
• do a download by:
o logging on to the source client

o selecting the data to download
o defining where they should be located
o committing the download
• do an upload by:
o logging on to the target client

o selecting the data to upload
o committing the upload
Version 3.0
Check The administrator should now be able to access the Check Customizing node in order
customizing to test fields and clouds checking for errors.
More particularly, the administrator learnt to test for:
• fields by:
o validating the ‘Check the Fields’ box on the interface for checking
customizing
o entering fields to be checked or leaving blank to check all fields
o choosing to check field descriptions or not
o correcting errors if need be
• clouds by:
o choosing to check Cloud scenarios and/or Cloud ranges
o entering Cloud scenario key (in case checking Cloud scenarios was
selected)
o entering Cloud range (in case checking Cloud ranges was selected)
• intervals by:
o validating the ‘Check the Intervals’ box on the interface for checking
customizing
• authorizations objects by:
o validating the ‘Check Authorization Object’ box on the interface for
checking customizing
• default user by:
o validating the ‘Check Default User’ box on the interface for checking
customizing
• SQL procedures by:
o validating the ‘SQL Procedures’ box on the interface for checking
customizing
Version 3.0
Chapter 7
Business Intelligence
Overview
Introduction The Business Intelligence node contains the following sub-nodes:
From each of these options, the administrator can drill down to access the programs
for individual infotypes.
Purpose Some data in SAP is difficult to report on in an ad-hoc manner. For instance:
• Payroll result and time result data, which are stored in “inaccessible” cluster
tables.
• Calculated fields (e.g. annual salary), which are not stored anywhere in SAP.
• Recurring fields in an infotype. For example, when there are multiple wage types
or date types on one screen there is no way of knowing which one to report on.
The Business Intelligence section of the IMG allows the administrator to make such
data accessible to end users by storing it in transparent tables, called shadow tables.
Shadow tables are initially filled in the Business Intelligence part of the IMG and are
subsequently updated by dynamic actions.
Version 3.0
Overview, Continued
• Before using a shadow table a proper analysis should be done to investigate the
Notes
ways to get the results.
• Every time a table update is done, make sure that there is sufficiently table space
for PSAPUSER1D and PSAPUSER1I
In this chapter This chapter contains the following sections:
For Information on… See Section … On Page …
PA Infotypes A 169
Payroll Extraction B 184
Time Extraction C 202
Recommendations on Shadow Table Management D 212
Version 3.0
Section A: PA Infotypes
Overview
Introduction This section of Business Intelligence solves the problem regarding the retrieval of
calculated fields and recurring fields in SAP infotypes. There are six nodes for
updating programs for PA infotypes:
1. General PA infotypes
2. US specific PA infotypes
3. Italian specific PA infotypes
4. Spanish specific PA infotypes
5. German specific PA infotypes
6. Japanese specific PA infotypes
The procedure for updating programs for all these infotypes is the same but there are
differences in functionality.
Note The number of updating programs in the IMG tree can vary. According to
the SAP version used, there are shadow tables that exist / do not exist.
Dynamic After performing the initial upload of these shadow tables, the administrator must
actions create a dynamic action in order for subsequent changes made in infotypes to be
maintained in shadow tables.
Dynamic actions should be set up in table T588Z as described in this section.
Version 3.0
Overview, Continued
Topic See Page
Updating PA Infotype Programs 171
Infotypes with Recurring Fields 175
Infotypes with Calculated Fields 177
Infotypes with Multiple Fields 178
A Special Case: Infotype 0008 180
Dynamic actions 183
Version 3.0
Updating PA Infotype Programs
Introduction The administrator can choose to update shadow tables in background directly from
the Query IMG tree or in foreground using the standard SAP transaction SA38.
Updating The table below describes the procedure for updating shadow tables in background.
programs in The same procedure is applicable for all PA infotype programs but there are
background differences in functionalities:
1 Clicks on of the required infotype under the Business Intelligence

node of the ARINSO Query IMG. This sets up a background job. A
message appears saying that the job has been created as revealed in the
screen below:
2 Clicks to execute the creation of a job.
Note The administrator can also check the status of a background job. To do so
go to System → Own job → Job overview. This is standard in SAP.
Version 3.0
Updating PA Infotype Programs, Continued
Updating Programs can also be executed online using the transaction SA38 in standard SAP.
programs Follow the procedure below for updating shadow tables online. The procedure is
online similar for all PA infotype programs.
1 Enters transaction code SA38 in the command field to reveal the

following screen:
2 Types the name of the update program to be executed. The name will be
of the type /ARINSO/QUERY_BI_EXTR_PA_nnnn where ‘nnnn’ is the
infotype number
Note In some cases (i.e. when an infotype needs more than one
update program, see page178) a letter (a, b, c, etc) is added to
the infotype number ‘nnnn’, giving an update program name
of the type /ARINSO/QUERY_BI_EXTR_PA_nnnnl where
‘l’ stands for the letter
Version 3.0
Updating programs online (continued)
3 Clicks to execute the program. This will reveal the following

selection screen:
4 Selects the population for which the update program has to be run using
one or more of the following population selection criteria:
• Personnel number
• Employment status
• Company code
• Payroll area
• Employee group
• Employee subgroup
• Personnel area
• Personnel subarea
• Cost center
Note If nothing is specified in the ‘Selection’ section, the program

will be run for all the population.
Version 3.0
Updating programs online (continued)
5 Chooses to select Control Options or not as shown in the following

screen view:
Control options allow the administrator to optimize the update program

results. Check the table below for information on each option:
Option Function
Insert directly in the Used for inserting data directly in the

database database. If unchecked the program uses
another way to insert data.
Note Selecting this option will make

the update program faster.
Number of employees / Used for determining how many employees

commit should be taken into account each time a
commit is done.
Note This option is set to ‘10’ by

default.
6 Clicks to execute the update program for the selected infotype. Once
the program has been executed the following message
appears at the bottom of the screen.
Version 3.0
Infotypes with Recurring Fields
Introduction Some infotypes contain recurring fields. For example, the same record may contain
multiple wage types or date types, in which case there is no way of knowing which
one to report on.
To solve this problem ARINSO uses shadow tables allowing the administrator to
create one record per recurring field, thereby making data accessible for ad hoc
reporting.
Example The example below shows an infotype with multiple wage types (LGA01, LGA02
and LGA03):
PERNR BEGDA ENDDA LGA01 LGA02 LGA03
15 01.01.2000 01.03.2000 M601 M602 M789
15 02.03.2000 31.12.9999 M601 M605
16 01.05.2001 01.06.2001 K790 K301
For the same personnel number and period, several wage types are displayed in the
table. The Query thus does not know which one to report on. To make reporting
easier one record is created per recurring field, changing the table structure as
outlined below:
PERNR BEGDA ENDDA LGART
15 01.01.2000 01.03.2000 M601
15 01.01.2000 01.03.2000 M602
15 01.01.2000 01.03.2000 M789
15 02.03.2000 31.12.9999 M601
15 02.03.2000 31.12.9999 M605
16 01.05.2001 01.06.2001 K790
16 01.05.2001 01.06.2001 K301
Version 3.0
Infotypes with Recurring Fields, Continued
Infotypes list Below is the list of infotypes that contain recurring fields. See Appendix A, page 221
to know to which section of Business Intelligence each infotype belongs.
• PA0006 • PA0032 • PA0147

• PA0013 • PA0033 • PA0221
• PA0025 • PA0041 • PA0235
• PA0028 • PA0082 • PA0154
• PA0031 • PA0083 • PA0008 (see page

180)
Version 3.0
Infotypes with Calculated Fields
Introduction Some infotypes contain calculated fields (such as annual salary), which are not
stored anywhere in SAP. They are calculated at runtime and displayed on the
infotype screen, but not actually stored in SAP. Reporting on them is thus difficult
and demands processing time.
This section solves the problem regarding the retrieval of calculated fields in SAP
infotypes.
Example An example of an infotype containing calculated fields is infotype 0014 (recurrent

payments). Infotype 0014 contains fields that are calculated indirectly via other fields
and are not stored anywhere in SAP.
The ARINSO Query allows the user to calculate those amounts every time it is
necessary. Running infotype 0014 update program will carry out indirect valuation
using standard functions.
Infotypes list Here is the list of infotypes that contain calculated fields. See Appendix A, page 221
• PA0014
• PA0015
• PA0008 (see page 180)
Version 3.0
Infotypes with Multiple Fields
Introduction Sometimes, the same infotype contains several sets of fields, making it difficult to
know which field to report on.
To solve this reporting problem ARINSO creates a new table for each set of fields,
which is then updated by a different shadow table.
Infotypes list Below is the list of infotypes containing multiple fields. See Appendix A, page 221
• Infotype 0027 – needs entries in tables /ARINSO/BI_027a, /ARINSO/BI_027b,

/ARINSO/BI_027c and /ARINSO/BI_027d
Note Tables /ARINSO/BI_027c and /ARINSO/BI_027d are only used in

SAP release 4.6
• Infotype 0156 – needs entries in tables /ARINSO/BI_156a, /ARINSO/BI_156b
and /ARINSO/BI_156c
• Infotype 0167 – needs entries in tables /ARINSO/BI_167a and

/ARINSO/BI_167b

and /ARINSO/BI_168c

and /ARINSO/BI_169c
Version 3.0
Infotypes with Multiple Fields, Continued
Example Infotype 0027 (cost distribution) contains four sets of fields:

infotype 0027
• Cost Center (CC)
• Funds Center (FC)
• Order Number (ON)
• WBS Element (WBS)
The table below shows an example of a record containing the four sets of fields
mentioned above:
PERNR1 CC1 CC2 FC1 FC2 ON1 ON2 WBS1 WBS2
To solve the reporting difficulty ARINSO creates four different tables rather than
just one:
• Table /ARINSO/BI_0027A has Cost Center in the key
• Table /ARINSO/BI_0027B has Funds Center in the key
• Table /ARINSO/BI_0027C has Order Number in the key
• Table /ARINSO/BI_0027D has WBS Element in the key
To each table corresponds a shadow table so that four update programs have to be
run for infotype 0027:
• In shadow table /ARINSO/QUERY_BI_EXTR_0027A one record is created per

Cost Center
• In shadow table /ARINSO/QUERY_BI_EXTR_0027B one record is created per

Funds Center
• In shadow table /ARINSO/QUERY_BI_EXTR_0027C one record is created per

Order Number
• In shadow table /ARINSO/QUERY_BI_EXTR_0027D one record is created per

WBS Element
Version 3.0
A Special Case: Infotype 0008
Introduction Infotype 0008 (basic pay) differs from other infotypes in the sense that it contains
both calculated fields and recurring fields making reporting even more difficult.
Recurring Infotype 0008 contains recurring fields, i.e. multiple wage types. There is thus no
fields way of knowing which one to report on.
To make reporting easier one record is created in table /ARINSO/BI_0008 for every
different wage type so that when running the update program
/ARINSO/QUERY_BI_EXTR_0008 one separate record is created per wage type.
Note For more information on recurring fields see page 175
Calculated As for infotype 0014, infotype 0008 contains calculated fields, i.e. fields that are
fields calculated indirectly via other fields and are not stored anywhere in SAP.
The ARINSO Query allows the user to calculate those amounts every time it is
necessary using standard functions.
Note For more details on calculated fields see page 177
Annual and The shadow table for infotype 0008 updates the period and annual salary. When
period salary running the update program the values defined in System Parameters (see Chapter 5,
page 28) are put in the shadow tables (e.g. ‘9PER’ for period salary and ‘9ANS’ for
annual salary).
Note If no customizing is specified for those fields (i.e. if the Business

Intelligence parameters “Annual Salary” and “Period Salary” do not have
a value) there will be no record with LGART = 9ANS and LGART =
9PER.
Version 3.0
A Special Case: Infotype 0008, Continued
Minimum and The shadow table for infotype 0008 updates the minimum and maximum salary. This
maximum is done by getting the pay scale details and sending the data to table T510. It then
salary gets the minimum and maximum salary and stores the values in the shadow table
under a dummy wage type (LGART) provided by the client in a customizing table.
Note Minimum and maximum salary calculation is only carried out if the
Query customizing says it should be done. Go to System Parameters and
ensure the Business Intelligence parameters “MIN LGART” and “MAX
LGART” have a value (e.g. 9MIN and 9MAX).
Indirect begin The shadow table for infotype 0008 updates the indirect begin date (IND_BEGDA)
and end dates and indirect end date (IND_ENDDA).
1. When there is a normal update (i.e. not involving indirect valuation or
minimum and maximum salary) the value in field BEGDA is the same as the
value in field IND_BEGDA. The value in field ENDDA is the same as the value
in field IND_ENDDA.
2. When there is indirect valuation the value in field BEGDA is different from
the value in field IND_BEGDA. The value in field ENDDA is different from
the value in field IND_ENDDA.
Example
Take a record in PA0008 with the following begin and end dates:
• BEGDA = 27/02/1996
• ENDDA = 31/12/9999
And knowing that for that record the following amounts are given:
• from 01/01/1992 to 12/10/2000, amount = 2000
• from 13/10/2000 to 31/12/9999, amount = 3000
Expected records created in /ARINSO/BI_0008 are as follows:
Record BEGDA ENDDA IND_BEGDA IND_ENDDA Amount
1 27.02.1996 12.10.2000 27.02.1996 31.12.9999 2000
2 13.10.2000 31.12.9999 27.02.1996 31.12.9999 3000
Version 3.0
A Special Case: Infotype 0008, Continued
Indirect begin 3. When there is a minimum and maximum salary calculation the value in field
and end dates BEGDA is different from the value in field IND_BEGDA. The value in field
(continued) ENDDA is different from the value in field IND_ENDDA.
Example
Take a record in PA008 with the following begin and end dates:
• BEGDA = 27/02/96
• ENDDA = 31/12/9999
And knowing that for that record the following amounts are given:
• from 01/01/1900 to 11/10/2000, amount = 1000
• from 12/10/2000 to 31/12/9999, amount = 1500
Expected records in shadow table are as follows:
Record BEGDA ENDDA IND_BEGDA IND_ENDDA Amount
1 27.02.1996 11.10.2000 01.01.1900 11.10.2000 1000
2 12.10.2000 31.12.9999 12.10.2000 31.12.9999 1500
Version 3.0
Dynamic Actions
Background The administrator must create a dynamic action in order for changes made in
infotypes to be maintained in Business Intelligence shadow tables. This procedure
should be repeated for all, including country specific PA infotypes.
Creating a 1. Access table T588Z in maintain mode.

dynamic action
Note SAP IMG path (in version 4.0b): Personnel management → Personnel
administration → Setting up procedures → Create dynamic actions
2. The table in Appendix A shows which entries should be made in table T588Z for
the PA infotypes. These entries create a dynamic action so that changes made in
the infotype will be maintained in the business intelligence shadow table.
• For all infotypes:

Notes
Dynamic actions are not processed in a batch input session. In batch input, you must
specify the exact sequence of the screens. To ensure this is the case, you must have
already programmed the dynamic action checks before you create the batch input
session. To avoid errors only the static actions are processed when you program and
process a session. Infotypes that usually only appear in the system as a result of a
dynamic action should be updated by calling up the transaction separately.
• For infotype 0008 only:
Dynamic actions are not processed when changes in the customizing for infotype
0008 (indirect valuation) have been done.
Version 3.0
Section B: Payroll Extraction
Overview
Purpose This section of Business Intelligence solves the problem regarding the retrieval of
data from the payroll clusters. The Payroll Extraction program allows the Query to
access and report on otherwise “inaccessible” data.
The Payroll Extraction node drills down to the following options:
Description The Payroll Extraction tool is divided into four options:

• Payroll Wage Type Customizing – execute this program to fill table
/ARINSO/AQ_0LGRT with the names of wage types which the client needs to
extract.
• Configure Clusters to be Extracted – execute this program to configure cluster

parts to be extracted.
• Payroll Extraction Synchronizer – execute this program to copy customizing.
• Payroll Extraction Program – execute this program to run the payroll extraction.
Version 3.0
Overview, Continued
Topic See Page
Payroll Wage Type Customizing 186
Configure Clusters to be Extracted 191
Payroll Extraction Synchronizer 193
Payroll Extraction Execution Program 195
Version 3.0
Payroll Wage Type Customizing
Purpose The ARINSO Query payroll extraction does not necessarily extract all wage types
from every cluster payroll table. Query only extracts those wage types which are
marked for extraction in table /ARINSO/AQ_0LGRT.
Getting started To access the Payroll Wage Type Customizing tool click
under the Payroll Extraction Customizing
node of the Query IMG.
Payroll wage The view below shows the Payroll Wage Type Customizing tool:
type
customizing
interface
Version 3.0
Payroll Wage Type Customizing, Continued
Specify wage In the table below the administrator will find the procedure for specifying wage
types types:
1 Accesses the program as described above
2 Selects a date for checking validity against table T512W. The current
date is select by default.
3 Selects a country grouping. Country groupings are used to separate one

country from another in accordance with HR criteria. They are primarily
used in conjunction with wage types.
4 Checks to
choose how the table /ARINSO/AQ_0LGRT is to be altered.
All entries in table /ARINSO/AQ_0LGRT will be deleted and then

overwritten, based upon the selections made by the administrator.
5 Enters the wage types to be extracted bearing in mind the following:
• RT means Result Table
• CRT means Cumulated Result Table
Note A multiple selection can be carried out at this stage by

clicking .
6 Checks to list the entries which have been inserted.
Version 3.0
Specify wage types (continued)
7 Clicks to execute changes to wage type customization. This will

reveal a transport request screen. Create transport request as prompted.
Once this is done the following screen will be displayed showing the
entries added to /ARINSO/BI_GART (if was
checked):
In table /ARINSO/AQ_0LGRT, wage types are given an extraction specification

Note
value. These values are determined as follows:
• Wage types extracted for RT: 01
• Wage types extracted for CRT: 10
• Wage types extracted for RT & CRT: 11
• Wage types extracted for all tables: 99
The extraction specification priority is 99, 11, 10, 01. This means that if a wage type
is included in the range entered for all wage types and for RT only, then the value 99
will appear in the table /ARINSO/AQ_0LGRT.
Version 3.0
Configuring The table /ARINSO/AQ_0LGRT can be configured manually via transaction code
/ARINSO/AQ_ SM30. The Query administrator should follow the instructions below to configure
0LGRT and view it:
Step Action
1 Enter transaction code SM30 in the command field to access the

following screen where tables can be maintained:
2 Select table name to be viewed or maintained, in this case

/ARINSO/AQ_0LGRT
Version 3.0
Configuring /ARINSO/AQ_0LGRT (continued)
Step Action
3 Click to view the table or

to configure it and reveal the following screen:
Version 3.0
Configure Clusters to be Extracted
Purpose This program allows the administrator to access payroll result data that are stored in
“inaccessible” cluster tables and are therefore “non-queriable”.
It also allows the administrator to extract only certain cluster parts by narrowing
down criteria.
Accessing the To access the Configure Clusters to be Extracted tool click

program under the Payroll Extraction
Customizing node of the Query IMG.
Screen view The view below displays the Configure Clusters to be Extracted tool:
Version 3.0
Configure Clusters to be Extracted, Continued
Extracting To configure cluster parts to be extracted the administrator is requested to follow this
cluster parts procedure:
1 Clicks to access the screen in create mode
2 Gives the country grouping to which the cluster parts to be extracted

belong. Country groupings are used to separate one country from another
in accordance with HR criteria (e.g. country grouping 10 represents the
US).
3 Selects cluster parts that need to be extracted
4 Enters cluster table(s) to which cluster parts to extract belong
5 Once required new entries have been made click
Version 3.0
Payroll Extraction Synchronizer
Purpose ARINSO Query is transported with standard customizing (cluster parts). If the client
wishes to use ARINSO customizing as a base for its own, it is necessary to transfer
this customizing to the client’s tables.
This gives the client a basic set of customizing which can be used immediately by
end users, or as a base for more specific customizing.
Getting started To access the Payroll Extraction Synchronizer tool click

under the Payroll Extraction node of the
Query IMG.
Screen view The view below shows the Payroll Extraction Synchronizer tool:
Version 3.0
Payroll Extraction Synchronizer, Continued
Screen The Payroll Extraction Synchronizer screen consists of three parts:

description
• the first two columns make up ARINSO customizing
• the last two columns make up the client’s customizing
• the third column (the middle one) indicates whether data are identical or
different in ARINSO and client customizing using the following icons:
The table below describes the function of each icon:
Icon … Indicates that …
data are different, i.e. ARINSO customizing has not been copied. Last
two columns are empty.
data are partly identical, i.e. ARINSO customizing has been copied but
not saved. Text in the last two columns is highlighted blue.
data are identical, i.e. ARINSO customizing has been copied and saved.
Text in the last two columns is in black.
Copying data To copy ARINSO cluster customizing follow the procedure below:
1 Selects the data to copy, i.e. those data that have a icon
2 Clicks the icon. The icon has now changed into and text has
been copied to client (highlighted blue)
3 Clicks to save the copied customizing. Upon saving a transport

request screen appears. Enter transport request as prompted and validate
by clicking . The icon has now changed into .
Version 3.0
Payroll Extraction Execution
Purpose This program allows the administrator to run the payroll extraction.
Accessing the To access the Payroll Extraction Program click

program under the Payroll Extraction Execution node of the Query IMG.
Screen The Payroll Extraction Execution selection screen is divided into five sections:
description
1. Population Selection – limits the population for which payroll update occurs.
2. Number of PERNRS and Country Modifier – defines the number of PERNRS

and SAP country code to use in the extraction.
3. Wage Type Selection – defines wage types for payroll extraction.
4. Insert – defines which payroll records will be inserted into the shadow table
5. Delete – defines which payroll records will be deleted from the shadow table
Each section is explained on the following pages.
Version 3.0
Payroll Extraction Execution, Continued
Population The population section is used to limit the population for which payroll update
selection occurs. The administrator can limit the population by filling in one or more of the
following categories:
Nb Pernr
The technical parameter indicates the
number of PERNR that will be proceeded before an update of the database. It is
advised to keep the default value of the parameter ("10").
Only take Checking the checkbox allows the user to restart

PERNR the extraction if the program quits prematurely without having to extract information
for employees whose information was already successfully extracted.
Country The section below is used to define the SAP country code to use in the extraction as
grouping and well as the currency in which the payroll has to be extracted. This means that only
currency records for the selected country will be selected.
Version 3.0
Wage type The view below shows the screen section where wage types for payroll extraction are
selection selected:
The administrator can choose between:
1. Selecting wage types corresponding to extracted records at the time of

extraction.
2. Using wage types in table /ARINSO/AQ_0LGRT. The wage types are already
uploaded in the table /ARINSO/AQ_0LGRT. Therefore keep the radio button
"Use wage type in table /ARINSO/AQ_0LGRT" checked.
Insert The ‘Insert’ section defines which payroll records will be inserted into the shadow
table. The view below shows this section:
All options are explained overleaf.
Version 3.0
Insert options The Insert section allows the administrator to perform one or more of the following:
• To disregard any insertion, click "No update".
• To extract for-periods for employees, click the radio button labeled, "For-
period selection" and enter a period range. The date must be of the type
‘yyyypp’ where ‘y’ stands for the year and ‘p’ for the payroll period.
• To update all records for each in-period as it is run, click "In-period selection"
and enter an in-period for which you want date extracted.
o Check the box "Update voided records" when you want to take the
previous record before the voiding.
o Keep the checkbox "Update Payroll indicator" checked when the

query payroll results tables are not uploaded for the first time.
• To update off-cycle periods, check the checkbox "Off-cycle date selection" and
enter a period.
• To disregard void payroll records, check the checkbox "No void payroll
records".
• Click the appropriate check button according to which records should be

extracted:
o Also take Prior Records
o Also take Old Records
o WPBP dates --> BI_RT dates (Work Place Basic Pay).
This table holds information from infotypes 0000, 0001, 0007 and 0008 associated
with a payroll run. If required, check in order to make entries
made in BI_RT correspond to the begin and end dates of Work Place Basic Pay
records. If this option is not checked, the user has access to the entire payroll period
when querying on any one day within the payroll period.
Version 3.0
Delete The ‘Delete’ section defines which payroll records will be deleted from the shadow
table. The view below shows this section:
Delete options • To disregard any deletion, click "No delete".
• To delete for-periods for employees, click the radio button labeled "FOR-period
selection" and enter a period range.
• To delete all records for each in-period, click "IN-period selection" and enter a
period range.
• To delete off-cycle periods, check the checkbox "Delete Off-cycle date

selection" and enter a period.
• Click the appropriate check button according to which records should be deleted:
o Also take Prior Records
o Also take Old Records
To delete only void payroll records, check "Delete only void".
Executing the Click to execute the program update. It is recommended to run the program as a
update background job as it might take a long time to execute.
Version 3.0
Example 1 Here are some examples of how the Payroll Extraction tool may be used:
• When running the payroll extraction without any prior payroll results having
been extracted into the payroll shadow tables, the administrator might want to fill
the extraction shadow tables with historical data.
• Perhaps the current payroll period is the 6th of the year 2000 and there is a need
to update the shadow tables for all current (payroll status ‘A’) results from the
beginning of the year.
• In this case, the administrator selects the radio buttons “For period selection”. In
the dialog boxes beside the label “For period selection”, the administrator should
enter ‘200001’ on the left side and ‘200006’ on the right side. After running the
extraction, the tables are updated with information for all the most current for-
periods between periods of 1 and 6 of the year 2000.
Example 2 • Now, suppose payroll period 7 has been run and the administrator wishes to
update all information for this period in the payroll shadow tables.
• The administrator selects the radio button option “In period selection” and types
‘200007’ in the dialog box next to it.
• After running the extraction, all information from period 7 is extracted and the
payroll status for records existing in /ARINSO/BI_RT and /ARINSO/BI_RGDIR
is updated to the correct value. In these tables, the value of the field, SRTZA is
converted to ‘P’ where it was ‘A’ and ‘O’ where it was ‘P’.
Version 3.0
Example 3 • Suppose that an off-cycle payment was made and the administrator wants to
have this information immediately available for the Query Tool.
• The administrator runs the extraction program checking the box with the label
“Off-cycle date selection” and types the date of the off-cycle payment in the left
hand dialog box.
• If there were more than one off-cycle payroll to extract, the administrator would
enter a range in the two dialog boxes that would cover all off-cycle payment
dates. The left hand box holds the lesser date of this range.
• In the future, when the extraction is run with the option “In-period selection”,
this off-cycle period will also be included if it has been recalculated for the in-
period. The payroll status of all prior off-cycle payments will also be updated
just like the payroll status for other for-periods.
Version 3.0
Section C: Time Extraction
Overview
Purpose This section of Business Intelligence solves the problem regarding the retrieval of
time result data. The Time Extraction program allows the Query to access and report
on otherwise ‘difficult to access’ data from time infotypes and clusters.
Programs have been created to load ARINSO Query shadow tables with time data
from time infotypes and clusters. These shadow tables are then accessed by the
ARINSO HR Query for reporting.
Dynamic The administrator must create a dynamic action in order for changes made in
actions infotypes to be maintained in shadow tables.
Dynamic actions should be set up in table T588Z as described in section A, page

183.
Topic See Page
Updating Programs for Time Extraction 203
Infotype 0005 Extraction 204
Infotypes 2001, 2002, 2003, 2005 Extraction 206
Time Cluster Extraction 208
Planned Working Time Extraction 210
Version 3.0
Updating Programs for Time Extraction
Introduction As part of the Query Time set up, the administrator must run every program to load
the shadow tables with the information already saved in the different time infotypes
and clusters.
The shadow tables will then be updated by means of a dynamic action every time a
change occurs on an infotype (creation/update/deletion). Dynamic actions only
involve infotypes.
Due to the amount of data involved, all other table and cluster retrievals are done
through manual request, allowing the administrator to manage table sizes easily.
The Time Extraction node drills down to the following options:
Running To run update programs click on the required program under the
update node.
programs
Version 3.0
Infotype 0005 Extraction
Accessing the Click under the Time Extraction node of the

program Query IMG to reveal the screen below:
Screen The screen is divided into three sections:

description
• Population selection
• Period selection
• Continue process after termination of the program
Version 3.0
Infotype 0005 Extraction, Continued
Population The administrator must enter required selections:

selection
• Personnel number
• Company code
• Personnel area
• Personnel sub-area
• Country code
Note Country code is displayed by default but can be modified.
Period The administrator must enter a period selection:

selection
• Selection for a year – check and select a year to load all
the information for the selected year.
• Selection for deletion – check and enter a period range

to delete all the records between year dates.
Track changes When is checked,

the program keeps a record of the latest selections that have been updated. This is
useful if the update program has to be re-started (in the event of a system crash for
example), since those selections already updated will be kept to memory and will not
therefore have to be updated again.
Executing the Once all required entries have been made, click to update changes. Once all
program changes have been updated, the following message will
appear at the bottom of the screen.
Version 3.0
Infotypes 2001, 2002, 2003, 2005 Extraction
Accessing Access program to reveal the screen below. The same selection screen is available
programs for infotypes 2001, 2002, 2003 and 2005.
Description The screen is divided into three sections:
• Continue process after termination of the program
Population As per description for infotype 0005 (see page 205)

selection
Version 3.0
Infotypes 2001, 2002, 2003, 2005 Extraction, Continued
Period As per description for infotype 0005 (see page 205), except:
selection
• For the period – check and enter a period to load all
the information for the selected month and year
• No upload
Track changes As per description for infotype 0005 (see page 205)
Executing the Once all required entries have been made, click to update changes. Once all
program changes have been updated, the following message will
appear at the bottom of the screen.
Version 3.0
Time Cluster Extraction
Screen view Click under the Time Extraction node to access the
Time Cluster Extraction program and reveal the screen below:
Description The screen is divided into three sections:
• Time type selection
Version 3.0
Time Cluster Extraction, Continued

selection
Time type A time type is a grouping of times according to various aspects such as payments
selection regulations, internal company requirements and control tasks. It assigns a meaning to
a time interval. The balances formed in time evaluation are posted to the time types.
The administrator must carry out required selections bearing in mind the following:
• “Individual day balances” is checked for a retrieval from ZES
• “Cumulated balance” is checked for a retrieval from SALDO
A time type selection can be made for each of the two tables.
Note Tables /ARINSO/BI_ZES and /ARINSO/BI_SALDO can be selected by

request only. RPTIME00 does not update this table.
Period As per description for infotype 2001 (see page 207)

selection
Executing the Once all required entries have been made, click to update changes.
program
Version 3.0
Planned Working Time Extraction
Introduction This program allows the Query administrator to extract planned working time data.
Accessing the To access the Planned Working Time Extraction tool click
tool under the Time Extraction node of the
Query IMG.
Screen view Access Planned Working Time Extraction program to reveal the screen below:
Screen The screen is divided into two sections:

description
• Population selection – selects the population on which to run planned extraction
• Period selection – selects the period on which to run planned extraction
Version 3.0
Planned Working Time Extraction, Continued

selection
Period As per description for infotype 2001 (see page 207)

selection
Executing the Once all required entries have been made, click to update changes.
program
Version 3.0
Section D: Recommendations on Shadow Tables
Overview
Introduction Shadow tables in the ARINSO Query can be managed in such a way that
performance is improved.
On the one hand, shadow tables have an excellent impact on performance as they
reduce processing time during extraction. But on the other hand, they use a lot of
disk space. A good management of the shadow tables should make sure that the
database keeps a reasonable size.
Selection of The fact that there is a shadow table in the Query does not necessarily mean that it
shadow tables should be used. If the data modeling in the customer configuration does not meet one
of the three reasons for using shadow tables (see page 167), there is no need for them
to be used.
Example
If a customer does not use the field ‘Communication Type’ in its configuration of
infotype 0006, there is no need to use the relevant shadow table /ARINSO/BI_0006.
Selection of For payroll and time cluster shadow tables, a selection can be made on wage
data in shadow type/time type. By selecting the relevant types for your reporting needs table size and
tables disk space will be drastically reduced.
Payroll cluster As the ARINSO Query Administrator probably knows, a payroll cluster record
tables contains several cluster (internal) tables after extraction – each table containing one
type of information (i.e. RT is the Result Table, CRT is the Cumulated Result Table,
etc). The payroll extraction program allows the administrator to select the tables to
populate with payroll data.
Version 3.0
Section E: Chapter Summary
Overview
Introduction At the end of this chapter on Business Intelligence the Query administrator should be
able to report on:
• PA infotypes
• payroll extraction
• time extraction
Topic See Page
PA Infotypes 214
Payroll extraction 216
Time extraction 218
Version 3.0
PA Infotypes
Introduction At the end of the section on PA infotypes the administrator should be able to retrieve
calculated fields and recurring fields in SAP infotypes and run update programs for
each of them.
Update The administrator should now be able to run update programs for the following PA
programs infotypes:
• General PA infotypes
• US specific PA infotypes
• Italian specific PA infotypes
• Spanish specific PA infotypes
• German specific PA infotypes
• Japanese specific PA infotypes
More particularly, the administrator can:
• Run an update program for a PA infotype in background by clicking on of

the required infotype under the Business Intelligence node of the ARINSO
Query IMG.
• Run an update program in foreground using transaction SA38
Recurring The Query administrator should now be able to run update programs for PA
fields infotypes containing recurring fields using shadow tables.
Shadow tables allow the administrator to create one record per recurring field,
thereby making data accessible for ad hoc reporting.
Version 3.0
PA Infotypes, Continued
Calculated The Query administrator should now be able to run update programs for PA
fields infotypes containing calculated fields, which are not stored anywhere in SAP.
Multiple fields The Query administrator should now be able to run update programs for PA
infotypes containing several sets of fields, which makes reporting very difficult.
To solve this reporting problem ARINSO creates a new table for each set of fields.
Each set of fields is then updated with a different shadow table.
Version 3.0
Payroll Extraction
Introduction At the end of the section on payroll extraction the administrator should be able to
extract payroll data, solving the problem regarding the retrieval of data from payroll
clusters.
More particularly, the administrator should be able to run the following programs:
• Payroll Wage Type Customizing
• Configure Clusters to be Extracted
• Payroll Extraction Synchronizer
• Payroll Extraction Program
Payroll Wage The Query administrator should now be able to access the Payroll Wage Type
Type Customizing node to fill table /ARINSO/AQ_0LGRT with the wage types which the
Customizing client needs to extract.
More particularly, the administrator learnt how to customize wage types by:
• selecting a date for checking validity against table T512W
• selecting a country grouping
• choosing to delete all entries in table /ARINSO/AQ_0LGRT or not
• entering wage types to be extracted
• choosing to list the entries which have been inserted or not
The administrator also learnt to configure table /ARINSO/AQ_0LGRT manually via

transaction code SM30
Version 3.0
Payroll Extraction, Continued
Configure The Query administrator should now be able to access the Configure Clusters to be
Clusters to be Extracted node to configure cluster parts to be extracted.
Extracted
• give the country grouping to which the cluster parts to be extracted belong
• select cluster parts that need to be extracted
• enter cluster table(s) to which cluster parts to extract belong
Payroll The ARINSO Query administrator should now be able to access the Payroll
Extraction Extraction Synchronizer node to transfer ARINSO customizing tables to the client’s
Synchronizer tables.
Payroll The Query administrator should now be able to access the Payroll Extraction
Extraction Program node to run the payroll extraction.
Program
• select population to limit the population for which the payroll update occurs
• specify the number of PERNRS to use in the extraction
• select the SAP country code to use in the extraction
• define wage types for payroll extraction
• define which payroll records will be inserted into the shadow table
• define which payroll records will be deleted from the shadow table
Version 3.0
Time Extraction
Introduction At the end of this section on time extraction the administrator should be able to
extract payroll data, solving the problem regarding the retrieval of time result data.
More particularly, the Query administrator should be able to:
• run update programs for time infotypes
• extract time cluster data
• run planned working time extraction
Update The Query administrator should now be able to access the nodes for running
programs programs to load the shadow tables with the information already saved in the
different time infotypes and clusters.
More particularly, the Query administrator learnt to run update programs for the
following infotypes:
• infotype 0005
• infotype 2001
• infotype 2002
• infotype 2003
• infotype 2005
For all these infotypes the administrator knows how to:
• select a population for which to load information
• define a period on which to load all information
• track changes in order to keep a record of the latest selections that have been
updated
Version 3.0
Time Extraction, Continued
Time cluster The Query administrator should now be able to access the Time Cluster Extraction
Extraction node in order to extract time cluster data.
• select a population for which to extract data
• define a time type to assign a meaning to time intervals
• define a period on which to extract data
Planned The Query administrator should now be able to access the Planned Working Time
working time Extraction in order to extract planned working time data.
extraction
• select a population for which to extract planned working time data
• define a period on which to extract planned working time data
Version 3.0
Chapter 8
Upgrade Tools
Overview
See upgrade This node of the Query Implementation Guide is discussed in a separate manual, the
installation Upgrade Installation Manual. The administrator is requested to refer to that manual
manual for information on how to use upgrade tools.
Version 3.0
Appendix A
Table Entries to Create Dynamic Actions for PA Infotypes
Overview
Creating a 1. Access table T588Z in maintain mode.

dynamic action
Note SAP IMG path (in version 4.0b): Personnel management → Personnel
administration → Setting up procedures → Create dynamic actions
2. The table in below shows which entries should be made in table T588Z for all
PA infotypes. These entries create a dynamic action so that changes made in the
infotype will be maintained in the business intelligence shadow table.
General PA Infotypes
Mandt Infty Subty Fname Opera Seqno Kennz Vinfo

* KEEP TABLE /ARINSO/BI_0006 UP TO
100 0006 0 90 DATE WITH 0006
MAINTAIN_0006(/ARINSO/QUERY_BI_E
100 0006 0 91 F XTR_PA_0006)
100 0008 0 90 DATE WITH 0008
100 0008 0 91 F XTR_PA_0008)
*KEEP TABLE /ARINSO/BI_0014 UP TO
100 0014 0 DATE WITH 0014
100 0014 0 XTR_PA_0014)
100 0015 0 DATE WITH 0015
100 0015 0 XTR_PA_0015)
* KEEP TABLE /ARINSO/BI_0027A UP
100 0027 0 90 TO DATE WITH 0027
MAINTAIN_0027A(/ARINSO/QUERY_BI_
100 0027 0 91 F EXTR_PA_0027A)
* KEEP TABLE /ARINSO/BI_0027B UP
100 0027 0 92 TO DATE WITH 0027
MAINTAIN_0027B(/ARINSO/QUERY_BI_
100 0027 0 93 F EXTR_PA_0027B)
Version 3.0
Overview, Continued
Creating a dynamic action (continued)
General PA Infotypes

* KEEP TABLE /ARINSO/BI_0027C UP
100 0027 0 94 TO DATE WITH 0027
MAINTAIN_0027C(/ARINSO/QUERY_BI_
100 0027 0 95 F EXTR_PA_0027C)
* KEEP TABLE /ARINSO/BI_0027D UP
100 0027 0 96 TO DATE WITH 0027
MAINTAIN_0027D(/ARINSO/QUERY_BI_
100 0027 0 97 F EXTR_PA_0027D)
100 0028 0 90 DATE WITH 0028
100 0028 0 91 F XTR_PA_0028)
100 0031 0 90 DATE WITH 0031
100 0031 0 91 F XTR_PA_0031)
100 0032 0 90 DATE WITH 0032
100 0032 0 91 F XTR_PA_0032)
100 0033 0 90 DATE WITH 0033
100 0033 0 91 F XTR_PA_0033)
100 0041 0 90 DATE WITH 0041
100 0041 0 91 F XTR_PA_0041)
100 0082 0 90 DATE WITH 0082
100 0082 0 91 F XTR_PA_0082)
100 0083 0 90 DATE WITH 0083
100 0083 0 91 F XTR_PA_0083)
Version 3.0
Overview, Continued
US Specific Infotypes

100 0147 0 90 DATE WITH 0147
100 0147 0 91 F XTR_PA_0147)
100 0167 0 90 TO DATE WITH 0167
100 0167 0 91 F EXTR_PA_0167A)
100 0167 0 92 TO DATE WITH 0167
100 0167 0 93 F EXTR_PA_0167B)
100 0168 0 90 TO DATE WITH 0168
100 0168 0 91 F EXTR_PA_0168A)
100 0168 0 92 TO DATE WITH 0168
100 0168 0 93 F EXTR_PA_0168B)
100 0168 0 94 TO DATE WITH 0168
100 0168 0 95 F EXTR_PA_0168C)
100 0169 0 90 TO DATE WITH 0169
100 0169 0 91 F EXTR_PA_0169A)
100 0169 0 92 TO DATE WITH 0169
100 0169 0 93 F EXTR_PA_0169B)
100 0169 0 94 TO DATE WITH 0169
100 0169 0 95 F EXTR_PA_0169C)
Version 3.0
Overview, Continued

100 0221 0 DATE WITH 0221
100 0221 0 XTR_PA_0221)
100 0235 0 DATE WITH 0235
100 0235 0 XTR_PA_0235)
Spanish Specific PA Infotypes
100 0061 92 DATE WITH 0061
100 0061 93 F XTR_PA_0061)
100 0062 92 DATE WITH 0062
100 0062 93 F XTR_PA_0062)
Italian Specific PA Infotypes
100 0154 0 DATE WITH 0154
100 0154 0 XTR_PA_0154)
*KEEP TABLE /ARINSO/BI_0156A UP TO
100 0156 0 DATE WITH 0156
100 0156 0 EXTR_PA_0156A)
*KEEP TABLE /ARINSO/BI_0156B UP TO
100 0156 0 DATE WITH 0156
100 0156 0 EXTR_PA_0156B)
*KEEP TABLE /ARINSO/BI_0156C UP TO
100 0156 0 DATE WITH 0156
100 0156 0 EXTR_PA_0156C)
Version 3.0
Overview, Continued

100 0157 0 DATE WITH 0157
100 0157 0 XTR_PA_0157)
100 0158 0 DATE WITH 0158
100 0158 0 XTR_PA_0158)
100 0160 0 DATE WITH 0160
100 0160 0 XTR_PA_0160)
100 0305 0 DATE WITH 0305
100 0305 0 XTR_PA_0305)
German Specific PA Infotypes

100 0013 0 DATE WITH 0013
100 0013 0 XTR_PA_0013)
100 0025 0 DATE WITH 0025
100 0025 0 XTR_PA_0025)
100 0079 0 DATE WITH 0079
100 0079 0 XTR_PA_0079)
100 0093 0 DATE WITH 0093
100 0093 0 XTR_PA_0093)
Version 3.0
Overview, Continued
Japanese Specific PA Infotypes

100 0388 0 DATE WITH 0388
100 0388 0 XTR_PA_0388)
100 0559 0 DATE WITH 0559
100 0559 0 XTR_PA_0559)
The sequence number should be adapted to fit in with any existing customer dynamic
Note
actions.
Version 3.0
Appendix B
List of Customized Tables
Overview
Customized The table below contains the list of all tables that are customized in the ARINSO
tables Query:
Table Name Description
/ARINSO/AQ_0ADEF AQ: Customizing - Area - Definition
/ARINSO/AQ_0ATXT AQ: Customizing - Area - Text of Areas in the Query
/ARINSO/AQ_0CDEF AQ: Customizing - Cloud - List of cloud scenario
/ARINSO/AQ_0CFAX AQ: Customizing - Cloud - Definition of Axis
/ARINSO/AQ_0CFOD AQ: Customizing - Cloud - Definition of other fields
/ARINSO/AQ_0CRNG AQ: Customizing - Cloud - Definition of Ranges
/ARINSO/AQ_0CTXT AQ: Customizing - Cloud - Definition of Cloud Text
/ARINSO/AQ_0DFLD AQ: Customizing - Default Fields - (LOP) Fields to show
/ARINSO/AQ_0FDEF AQ: Customizing - Field - Definition of possible fields
/ARINSO/AQ_0FDH AQ: Customizing - Field - Definition of HR Plan fields
/ARINSO/AQ_0FDR AQ: Customizing - Field - Definition of Referenced Fields
/ARINSO/AQ_0FDV AQ: Customizing - Field - Definition of Virtual Fields
/ARINSO/AQ_0FDX AQ: Customizing - Field - Definition of Complex fields
/ARINSO/AQ_0FTFC AQ: Customizing - Field - Text For Field conditions
/ARINSO/AQ_0FTFD AQ: Customizing - Field - Text For Field definitions
/ARINSO/AQ_0FTXT AQ: Customizing - Field - Description of possible fields
Version 3.0
Overview, Continued
Customized tables (continued)
/ARINSO/AQ_0FUSE AQ: Customizing - Field - Favorite fields
/ARINSO/AQ_0LFA AQ: Customizing - Link - Area & Field
/ARINSO/AQ_0LWF1 AQ: Customizing - Layout Wizard - Calc - Functions def.
AQ: Customizing - Layout Wizard - Calc - Functions

/ARINSO/AQ_0LWF2 descript
AQ: Customizing - Layout Wizard - Calc - Functions

/ARINSO/AQ_0LWF3 Types
/ARINSO/AQ_0LWFM AQ: Customizing - Layout Wizard - Function Modules
/ARINSO/AQ_0LWFT AQ: Customizing - Layout Wizard - Functions (Texts)
/ARINSO/AQ_0OCRT AQ: Customizing - Other - Relation between tables
/ARINSO/AQ_0OCTC AQ: Customizing - Other - Conditions on tables
/ARINSO/AQ_0ODCT AQ: Customizing - Other - Options in the tree
/ARINSO/AQ_0OGRP AQ: Customizing - Other - Groups
/ARINSO/AQ_0OGU AQ: Customizing - Other - Groups
/ARINSO/AQ_0OPGM AQ: Customizing - Other - Report with PERNR field
/ARINSO/AQ_0PGL0 AQ: Customizing - Parameters - System Parameters
/ARINSO/AQ_0PGL1 AQ: Customizing - Parameters - Global Parameters
/ARINSO/AQ_0PGL2 AQ: Customizing - Parameters - Path Table
/ARINSO/AQ_0PGL3 AQ: Customizing - Parameters - User Options
Version 3.0
Overview, Continued
/ARINSO/AQ_0SSFC AQ: Customizing - Startup Filter - Conditions
/ARINSO/AQ_0SSFD AQ: Customizing - Startup Filter - Definition
/ARINSO/AQ_0SSFT AQ: Customizing - Startup Filter - Descriptions
/ARINSO/AQ_ACLST AQ: Authorization - Cluster that use
/ARINSO/AQ_APD AQ: Authorization - Table with PD authorizations
/ARINSO/AQ_APDH AQ: Authorization - Hist. of chg on auth. in the Query
/ARINSO/AQ_APENS AQ: Authorization - Table with Pension authorizations
AQ: Authorization - Link between Shadow Tables and

/ARINSO/AQ_ASHTB Infty
/ARINSO/AQ_CLSTD AQ: Cluster - table for documentation
/ARINSO/AQ_CLUST AQ: Cluster - table for WorkFlow
/ARINSO/AQ_GGENO AQ: General - Generated Objects
/ARINSO/AQ_GSESS AQ: General - Sessions by User
/ARINSO/AQ_HELPT AQ: Help - Online Help Link
/ARINSO/AQ_IOUTM AQ: Input - Possible Output Modules
/ARINSO/AQ_OSAVD AQ: Output - Store Key of saved Query
/ARINSO/AQ_SFRMD AQ: Select - Formula pattern for date fields (used for conv)
/ARINSO/AQ_SFRMF AQ: Select - Formula pattern for functions
Version 3.0
Overview, Continued
AQ: Select - SQL Layout generated (for

/ARINSO/AQ_SQLLY USE_VIEW/USE_TABLE)
/ARINSO/AQ_SQLRS AQ: Select - SQL Statement Result (check SQL)
AQ: Select - SQL Statement generated (for

/ARINSO/AQ_SQLST USE_VIEW/USE_TABLE)
/ARINSO/AQ_TCUSD AQ: Tree - Customizing IMG (Definition of nodes)
/ARINSO/AQ_TOPT AQ: Tree - Options for a node
/ARINSO/AQ_VG001 AQ: Variant - Group - Basic Information
/ARINSO/AQ_VG002 AQ: Variant - Group - Group Description
/ARINSO/AQ_VG003 AQ: Variant - Group - Group Authorizations
/ARINSO/AQ_VG004 AQ: Variant - Group - Group Authorizations
/ARINSO/AQ_VL001 AQ: Variant - Layout Wizard - Basic Information
/ARINSO/AQ_VL002 AQ: Variant - Layout Wizard - Variant Description
/ARINSO/AQ_VL003 AQ: Variant - Layout Wizard - Options by fields
/ARINSO/AQ_VL004 AQ: Variant - Layout Wizard - Calculated Fields
/ARINSO/AQ_VL005 AQ: Variant - Layout Wizard - Options
/ARINSO/AQ_VQ001 AQ: Variant - Query - Basic Information
/ARINSO/AQ_VQ002 AQ: Variant - Query - Variant Description
/ARINSO/AQ_VQ003 AQ: Variant - Query - Population Selection
Version 3.0
Overview, Continued
/ARINSO/AQ_VQ004 AQ: Variant - Query - Layout
/ARINSO/AQ_VQ005 AQ: Variant - Query - Layout Filter
/ARINSO/AQ_VQ006 AQ: Variant - Query - Documentation
/ARINSO/AQ_VQ007 AQ: Variant - Query - Date Specification
Version 3.0

HRIS AQ ARINSO Query 3.0 Administrator Manual PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HRIS AQ ARINSO Query 3.0 Administrator Manual PDF

Uploaded by

Copyright:

Available Formats

ARINSO Query

ARINSO Query – Administrator Manual 1

ARINSO Query – Administrator Manual 2

ARINSO International believes that the information described in this manual is

ARINSO Query is a trademark of ARINSO International.

© 2001 ARINSO International

All rights reserved.

ARINSO Query – Administrator Manual 3

Manual This manual contains the following chapters:

1 Introduction to the ARINSO Query Tool

3 Overview of the Implementation Guide

4 Version and License

Continued on next page

ARINSO Query – Administrator Manual 4

– this icon identifies examples in the manual

– this icon identifies notes in the manual

ARINSO Query – Administrator Manual 5

ARINSO Query – Administrator Manual 6

Continued on next page

ARINSO Query – Administrator Manual 7

Chapter 7 ............................................................................................................................................. 167

ARINSO Query – Administrator Manual 8

• Employee master data

• Applicant master data

• Organizational structure data

• Payroll result data

• Travel expense data

• Time result data

In this chapter This chapter contains the following topics:

Topic See Page

Installing ARINSO Query 10

Installing ARINSO Cloud 11

Installing AccessDown Program 12

ARINSO Query – Administrator Manual 9

Introduction ARINSO Query is delivered on a CD-Rom along with installation instructions.

It consists of a series of SAP transports, which should be imported on the customer’s

Pre-requisites ARINSO Query version 3.0 is developed to function on:

• SAP R/3™ versions 4.0 and higher

• Oracle, MS SQL, Adabas and DB2 databases

• Syntax check on the generated native SQL

This functionality is optional, though recommended for Oracle clients.

It is necessary to install three procedures and a function in order to use this

ARINSO Query – Administrator Manual 10

ARINSO Cloud is an optional functionality and should be installed by a technical

• Pentium 2 processor running at 300 MHz

• 25 MB space on the hard drive

• additional 128 MB of memory

ARINSO Query – Administrator Manual 11

Introduction In order to download query results to MS Access™, a PC based program called

This program should be installed by a technical administrator. It is fully integrated

• Pentium processor running at 100 MHz

• 10Mb disk space

ARINSO Query – Administrator Manual 12

Introduction There are two types of authorizations to consider:

1. Standard SAP HR authorizations

2. Authorizations to use parts of ARINSO Query

SAP HR The following SAP HR authorizations are respected:

Continued on next page

ARINSO Query – Administrator Manual 13

Save Public Variant Administrator, Super User

Modify Public Variant Administrator, Super User

Create Root Public Group Administrator, Super User

Modify Public Group Administrator, Super User