Sunteți pe pagina 1din 56

HR Business Content - Technical Aspects -

mySAP ERP HR, SAP AG

- customer -

Business Content Basics How to enhance BW HR Content Tips & Tricks

SAP BW Data Warehousing, Reporting & Analysis

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 3

SAP BW - What does Business Content mean ?


Role
w Workbook / e i WebTemplate rv e s U

Query / View
w e i v

InfoProvider Mapping rules

lic p Ap

n io t a

iv d In

liz a du

t io

InfoSource InfoObject DataSource / Extractor


SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 4

Employee Employee Overtime Overtime Hours Hours

St

n o i t za i rd a d an

Extraction, Transformation and Loading


Integration to mySAP on application level
Open for any source Flexible set of ETL capabilities Open to third-party tools Support of open standards

to get a complete view of your business


SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 5

SAP BW Data Flow: Extraction & Data Staging

BW

InfoCube
Update rules Communication Communication Structure Structure Transfer Rules transfer transfer structure structure

Master Data Attributes


Texts

InfoSource

Communication Communication Structure Structure Transfer Rules transfer transfer structure structure

OLTP
transfer transfer structure structure Extraction Extraction Source Source Structure Structure

Tools for generic data extraction Transaction RSO2


transfer transfer structure structure Extraction Extraction Source Source Structure Structure

Infotype

DataSource
Cluster

Transaction Data

Master Data Texts

Empl. Name

DataSource

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 6

What is an InfoObject ?
The various OLTP data models are unified for BW. A unique name containing technical information and business logic Business objects / data elements become InfoObjects (BW term for Business Evaluation Object)
R/3 OLTP

BW Extractor

Table of cost centers

CO
Controlling

KOSTL

...

DataSource for Cost Center

InfoObject 0COSTCENTER

HR
Human Resources

Table of employees
EMPLO COST_CENTER ...

InfoObjects are unique across application components!

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 7

Types of InfoObjects
Characteristics: evaluation groups like Cost Center, Product group, Material
Have discrete values stored in their master data tables (e.g. the characteristic Region has the values North, South, .. ) Special types of characteristics: Time characteristics like Fiscal period, Calendar year Unit characteristics which comprise currencies and units of measure like Local currency or Sales quantity

Key figures: continuously valued numerical fields like amounts and quantities (e.g.: Revenue and Sales quantity)

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 8

Example: InfoObject Employee


Attributes Orgunit CostCenter ..... Text Language Medium

Reporting Properties

Employee
Display Text Selection ....
External

Hierarchies Technical Description Data Type NUMC Size 8

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 9

HR Personnel Administration - Master Data

Employee (0EMPLOYEE) : IT 0, 1, 7, 8, 31
0PERSON 0PERS_AREA 0PERS_SAREA 0CO_MST_AR 0MAST_CCTR 0EMPLGROUP 0EMPLSGROUP 0ORGUNIT 0JOB 0HRPOSITION 0COMP_CODE ...
where can I investigate mapping between fields in HR-Content BW and fields in HR?... Regular Online documentation is really helpful...
SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 10

Person Personnel area Personnel subarea Master cost center controlling area Master cost center Employee group Employee subgroup Organizational unit Job Position Company code

HR Personnel Administration - Master Data

Employee (0EMPLOYEE)
... 0ANSALARY 0CURRENCY 0EMPLSTATUS 0EMPLPCT 0PAYPCT 0PAYRL_AREA 0PAYSCALEAR 0ESGFORCAP 0PAYSCALEGR 0PAYSCALELV 0PAYSCALETY 0COUNTRY_ID Annual salary Currency key Employment status Employment percentage Capacity utilization level Accounting area Pay scale area ES grouping for payscale provision Pay scale group Pay scale level Pay scale type Country grouping

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 11

HR Personnel Administration - Master Data

Employee (0EMPLOYEE)
... 0ENTRYDATE 0SALARYAR 0SALARYGR 0SALARYLV 0SALARYTY Entry date to calculate len.of service Grade Region Pay Grade Grade Level Salary Structure

Grade Level (0SALARYLV)


0SALLVMIN 0SALLVMAX Lower limit of pay grade level Upper limit of pay grade level

Pay Scale Level (0PAYSCALELV)


0PAYLVAMT Amount for pay scale level

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 12

HR Personnel Administration - Master Data

Person (0PERSON ) : IT 2, 6
0DATEBIRTH 0GENDER 0NATION 0PERSLANGU 0COUNTRY 0COUNTY_CDE 0POSTAL_CD 0REGION 0CITY ... Date of birth Gender Nationality Language Country key County code Postal code Region (State, Province, County) Location

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 13

InfoCubes as typical InfoProvider


InfoCubes
Data stored in Star Scheme
A combination of a fact table and dimension tables: Join of relational tables Optimized for multidimensional reporting Shared link to Master data tables

Transaction data Supports partitioning MultiCubes Special types


MultiCubes Remote Cubes

InfoCubes

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 14

InfoCube - Characteristics

Central data stores for reports and evaluations Contains two types of data
Key Figures Characteristics

1 Fact Table and 16 Dimension Tables


3 Dimensions are predefined by SAP
Time Unit Info Package

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 15

InfoCube - Data Model

One business process is modeled at a time Data storage optimized for reporting by a Star Schema
Dimension 1 Dimension 2 Dimension 3

Characteristics are structured together in related branches called Dimensions The key figures, KPI's, and other calculations form the Facts This structure is the same for all R/3 application areas
SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 16

Facts

Dimension n

Dimension 4

InfoCube - Dimensions

Dimension tables are groupings of related characteristics. A dimension table contains a generated primary key and characteristics. The keys of the dimension tables are foreign keys in the fact table.
Customer dimension
C Customer # 13970522 Region West ...

Product dimension
P Product # 2101004 Product group Displays ... T

Time dimension
Period 10 Fiscal year 1999 ...

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 17

InfoCube - Data Granularity

Data Granularity is defined as the detail of the database, the characteristics which describe our key figures.
Fundamental atomic level of data to be represented The by words - for example, headcount by cost center, by nationality

It determines how far you can drill down on the data. Example: Time Granularity
Day versus Month A customer buys the same product 2 to 3 times a month With time granularity of Day: 2 or 3 fact table entries With time granularity of Month: 1 record in the fact table but a loss of information (i.e., number of orders on different weekdays).
SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 18

InfoCube - Performance versus Disk Space

The decision on granularity has the biggest impact on space and performance Reducing granularity means losing information With normal star schemas (i.e. big fact table and small dimension tables) the design of dimensions is primarily guided by analytical needs. Large dimension tables have a big impact on performance

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 19

HR Personnel Administration - InfoSources

Employees (0HR_PA_0):
0CALMONTH 0EMPLOYEE Calendar year / month Personnel number

Actions (0HR_PA_1): IT 0
0CALDAY 0EMPLSTATUS 0ACTIONREAS 0ACTIONTYPE 0EMPLOYEE Calendar day Employment status Reason for action Action type Personnel number

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 20

HR Personnel Administration - InfoCube

Headcount and Personnel Actions (0PA_C01)


updated by InfoSources 0HR_PA_0 and 0HR_PA_1
Key

figures:
0HDCNT_LAST 0HDCNT_FTE 0ACTION_CNT 0AGE_KYF 0PAYPCT 0SRVCLENKYF Number of employees Number of FTEs Number of actions Age in years Capacity utilization level Length of Service Calendar day Calendar year / month Calendar year / quarter Calendar year

Time

characteristics:
0CALDAY 0CALMONTH 0CALQUARTER 0CALYEAR

Characteristics:
InfoSources + attributes of 0EMPLOYEE, 0PERSON + 0AGE, 0AGE_RANGE no navigational attributes due to challenges of time dependency !
SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 21

Business Content Basics How to enhance BW HR Content Tips & Tricks

Generic data extraction


Transactional Transactional Data Data // Master Master Data Data Application Application specific specific Standard Standard extractors extractors

Generic Generic extraction extraction

Enhancements Enhancements InfoSet InfoSet of of SAP SAP Query Query Function Function module module
Transparent table / DB-view

Transparent Transparent Table, Table, Database Database View View Domain Domain Values Values

Table joins (ABAP Select)

Logical data base

Extraction of data to complement the standard extractors Extraction without ABAP scripting (Query, views, domains) Modification of existing dataSource (not recommended by SAP)
SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 23

Delta extraction for generic extractors


Support delta extraction for generic extractors on monotonic attributes like Timestamp Calendar day Numeric pointer (e.g. document number) Current status of delta attribute can be monitored in delta queue (RSA7) especially use of time stamp could make sense (date of change) could be meaningful for transactional data in HR area (cause we have mostly time dependent master data)

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 24

Enhancement with Generic Extractor

Creating new DataSources and using generic data extraction


available with BW Extractors since BW 2.0, Plug-in 99 delta extraction available in BW 3.0, plug-in 2001 Function module interface available in BW 3.0

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 25

Generic extractor: database infoset

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 26

Definition of infoset (time dependent master data)

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 27

Definition of DataSource

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 28

Definition of DataSource

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 29

Benefit of use of logicial database PNP /PNPCE

all selection criteria of logicial database can be used as selection criteria without additional coding

"Provide-statment" will be done automatically in BW

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 30

Result in extractor checker (RSA3)

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 31

Enhancement with additional fields

BW

InfoSource Transfer structure

3 2

Load data

Replicate DataSources

OLTP
1
Define Append

Transfer structure
Customer Customer Append Append

Extraction structure
Customer Customer Exit Exit

Fill Extractstructure during Load


SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 32

Three steps to customize from SAP sources

Appending to existing Sources


Customizing for Business Information Warehouse in Source Systems tree (transaction SBIW within the source system)

1. Create append to existing extract structure of the Source 2. Use customer exit within SAP enhancement (RSAP0001):
1. 2. 3. 4.

EXIT_SAPLRSAP_001 for Transaction Data enhancements EXIT_SAPLRSAP_002 for Master data and Text enhancements EXIT_SAPLRSAP_004 for existing Hierarchy enhancements. New Hierarchy can be extracted from Flat file or create new Data Source using hierarchy data structure

3. Use CMOD to implement ABAP code to fill the new fields

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 33

1. BW R/3 Customizing: Create Append Structure

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 34

2. BW R/3 Customizing: Enhancement

Transaction: CMOD

Technical name of Enhancement

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 35

3. BW R/3 Customizing: Implement ABAP Code

Integrated in Customizing
Technical name of enhancement: RSAP0001 transaction data EXIT_SAPLRSAP_001 master data + texts EXIT_SAPLRSAP_002 hierarchies EXIT_SAPLRSAP_004

Use unique naming convention for Prod. vs. Dev. for Includes
SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 36

Business Content Basics How to enhance HR Business Content Tips & Tricks

Top 13 Tips to a Successful BW Implementation


1. Ensure you have a project sponsor 2. Exact reporting requirements before projects start are the key 3. Follow ASAP (with well defined blueprint phase) 4. If you have to work in a fixed price project: distinguish the estimated efforts in analysis phase and realization phase
For analysis phase you are able to estimate before finishing BBP Realization can be serios estimated after BBP

5. Let customer review and sign off every single phase of your project 6. Activate and use Standard Business Contents (especially dataflow often is reusable, rest is a valuable template for your own objects)
Paradigm Shift Gap Analysis

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 38

Top 13 Tips to a Successful BW Implementation


7. Test: let the keyuser test the solution after realisation (complete that phase carefully) 8. Refer Business Content documentation in SAP Help Portal 9. Have a Sound Stress Test Plan For High Volume Customer
8. Query runtime 9. Extraction runtime

10. Involve customer in every project phase as an active part 11. Be Aware that parallel R/3 and BW Implementation require intense coordination 12. Need Management vision and Commitment -> check the expected added value 13. Project plan should have milestones with clear responsible persons and distance between milestones must be short (maximum 4 weeks --> drill down your milestones
SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 39

Project Resources roles


BW Project Team ( Roles and Responsibilities) Project Sponsor (mandantory) Project Manager (on customer side and own side) Application Architect (can be the project manager from consulting side) BW Data Extraction Developer (ABAP Resource for enhancing extraction, transfer & update rules) Authorization Expert (reporting authorizations are working a little bit different as application authorizations) BW Data Access & Query Developer (Web Reporting Designer) Training Developer & Instructor (mostly on customer side)
Each Project is Different; Adjust Accordingly (one person usually has more than one role) Experiences: in big projects you need approximately 3 -4 consultants and you should demand 4 FTE on customers side
SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 40

BW R/3 Customizing

Transaction: SBIW

Install Business Content

Maintain generic DataSources Maintain DataSources

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 41

HR Structural Authorization in BW
0HR_PA_3

PSA
T77PR R/3 Org. Structure Profile
0HR_PA_2 Info Source

Struc Auth

Security Check

T77UA User Assignment

INDX Cluster

Info Source

Update Rules

T77UU User

Struc Auth ODSs

RSSM Trans
OR
Function Modules RSSB_Generate _Authorizations

PSA PSA 0PA_DS02


0PA_DS03

R/3 OLTP
SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 42

BW

BW/HR Authorization

Bring Structural Authorization into BW Environment


Selectively or bring all R/3 Structural Authorizations Restrictions
Active Plan version only without time-dependency DataSource supports all Object types from R/3, but additional customized update rules required in BW supports not determination of hierarchy node with function module in T77PR (structural profile maintenance)

Accelerator (How to guide) is available to guide implementation Delivery since PI 2001.1 and 2001.2 / BW 3.0a

Authorization for Display Attributes


Available in BW 2.0B since patch 7 Attention: we talk here about structural authorization, that's not the same like authorization in profile generator..........

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 43

Sample Scenario - Steps to Install Structural Authorization (in BW 2.x)


1 2

Create Structural Authorization Profile (IMG or TR-OOSP) Assign User to Profile (IMG or TR-OOSB) 3 4 5 6 7 8 9 Update T77UU table to include User Name Execute program RHBAUS00 to create INDX Activate 0HR_PA_2/3 Datasource in R/3 and BW Activate 0HR_PA_2/3 Infosource & Comm Structure Activate ODS objects and load data from R/3 Activate Target InfoObjects Authorization Relevant Execute RSSB Function Modules to generate BW Authorization (Report
RSSB_GENERATE_AUTHORIZATIONS)

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 44

Personalization based on Structural Authorizations


Data flow for ODS object Personalization Data

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 45

Five Steps to Activate BW/HR Business Content


1. Select and Activate HR DataSource in R/3 system : Install & Transfer BW/HR DataSources (TA:SBIW) 2. Business Content Activation in BW system : 1. MetaData Replications 2. Activate the relevant business content (InfoProviders, InfoSources, Queries, Web Reports, Roles etc.)
Activate in Background Activate in small chunks ( grouping- avoid choosing in data flow before and after) Repeat process for all desired InfoProviders

3. Data Transfer from Source System (setup & schedule Infopackages) 4. Upload Business Packages (content for the portal) from www.iviewstudio.com into Portal. 5. Assign Imported Role to User Ids.
SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 46

Tips & Hints for Installing BW/HR Business Content

Configure Payroll and Time Business Content


Planning Time type and Quote type assignment
Evaluate and grouping for reporting purpose Create External Hierarchy Configure T557 series & T554R Tables Setup in OLTP (OSS note 184266)

Maintain V_T569R for Retroactive category to avoid long running delta extraction (OSS note 353177) Payroll Accounting
Extracted at Monthly Time Dimension PI 2004.1 will contain new payroll extractor (selection logic)

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 47

hint: extention of transactional data


Try so often as possible to extend master DataSources instead of transactional DataSources Update characteristics in update rules from master data attributes -->It will reduce the traffic between OLTP and OLAP -->Master data are reusable for further transactional datasources -->Master data attributes can be used as navigational/display attributes (then they are outside the dataProvider) Select the same time stamp in update rule for every characteristic to avoid diverse time relations

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 48

hint - time dependent master data

Special Considerations for BW/HR:


- Create new (master data) DataSources rather than extending existing DataSources because of extraction performance reasons - If you're extending existing datasource to provide data from additional time dependent tables, you have to take validity of records into account by using the ABAP PROVIDE statement to create new time splits, otherwise validity of data provided in user exit might not be correct - Up to OLTP Release 4.6B, the RFPNR field of datasource 0EMPLOYEE_ATTR is filled with the employee's lowest reference personnel number, which is taken from infotype 0031 Reference Personnel Numbers. As of OLTP Release 4.6C, the RFPNR field is filled with the personnel number which is related via the central person and which has the oldest entry date. The RFPNR field is the link to 0PERSON. This information can be used to count contracts and/or physical persons. If you want to have a different assignment of the person id, please implement that logic in the user exit of master data extraction.

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 49

Tips & Hints for Installing BW/HR Business Content

System Maintenance Perspectives


Keep your system up to date
Apply & Activate latest content/system patches at first possible chance for needed enhancements and Improvements (most actual patch - 1) Review notes periodically; apply as appropriate

Upgrade Consideration
Review changes from both Basis and application perspectives and adopt new improvements wherever is appropriate.

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 50

Tips when Bring in HR Data from non-SAP source


General Considerations
Data Conversion When Integration with SAP data is a requirement, convertnon-SAP to SAP-like, so that you can take advantage of all avaialbe master from R/3 Historical Data consideration:
Since HR Master Data is mostly Time Dependent, historical data must be sorted in a Begda and Endda format without overlapping If non-R/3 system will not be retired, determine where the master data to be maintained preferrable in R/3

Review and incorporate the necessary Master data (ie. Orgunit, Personnel Areas etc.) from non-R3 system Data Cleansing Eliminate dirty data via conversion or build in logic in transfer/update rules (former is preferable) Multiple source systems Clarify before projects start if more then 1 source system will be connected or will be planned for the future -->otherwise other consultants as You will have a migration project in future :-)

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 51

useful hint: InfoObject person (0person)


use infoObject Person (0person) in transfer structure of transactional infosource --> it will provide and offer automaticially attributes of person in update rules --> makes the update logic much easier

1. 2. 3. 4.

expand communication structure assign 0EMPLOYEE to 0PERSON in transfer rule use atributes in update rules without programing Attention: only usable when relation 0EMPLOYEE = 0PERSON

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 52

hint: InfoCube - Data Model

modelling under aspect performance vs. thematic order


try to create so much dimensions as possible and try to distribute the charateristics with context among each other --> that will reduce the number of DIM-id's --> performance will be increased optimum will be to have the same number of DIM-id's in every dimension
Dimension 1

Dimension 2 Dimension 3

Facts

Dimension n

Dimension 4

but: often that will be in opposition to order the characteristics under thematic order

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 53

Tips & Hints for Installing BW/HR Business Content 6. Helpful OSS Notes
Org. management
543324 313215 Performance extraction DataSource 0ORGUNIT_ATTR Performance BW master data extraction 0HRPOSITION (performance note for 0HR_PA_OS_1 in process)

Pers. Administration
381239 HR BW: Counting leavings using actions

General HR
397208 BW: Authorizations for HR data extraction

General BW
529789 310304 324684 Different BW extraction / extractor checker + enter date selection as internal format for RSA3, esp. for time dep. master data DATETO/DATEFROM:Extracting time-depdnt master data Selections for language and time-dependence

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 54

Questions?

Q&A

SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 55

Copyright 2004 SAP AG. All Rights Reserved


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 56