sap... simple!

[

Real Experience. Real Advantage.

MIKE STOKO[ASUG BOARD OF DIRECTORS

MEMBER SINCE: 2003

BOB GAUTHIER[ASUG ASSOCIATE MEMBER

MEMBER SINCE:1998

CHRISTINA CRONE[ASUG INSTALLATION MEMBER

MEMBER SINCE: 1999

]SAP SIMPLE!? Yes, There Are Simple Solutions to Business Dilemmas

Donna L Wendling

Sherryanne H Meyer

Air Products and Chemicals, Inc.

[


Introduction

Having trouble meeting your business’s needs with standard

SAP ?

Do you lose sleep over needing an immediate solution and not

having a straightforward solution from SAP?

Do you ever feel like this……..

2

[


Learning Points

Fear no more!

Today we’ll show you how to: Think outside of the box to get the most out of your SAP

Deployment and to meet your business needs

Take advantage of SAP delivered options for reporting and

consolidating tables

Maximize SAP functionality – without customization

4

[

Real Experience. Real Advantage. 5

[


Return on Investment

Your company has made a significant investment in SAP . . . The best way to maximize that investment is to

• Fully understand it’s vast capabilities and flexibility

• Get the most of your deployment without having to use

• Outside-SAP-Solutions

• Modifications

• Or Therapists!

[


Quickviewer (SQVI)

• A simplified tool for generating basic lists

• User dependent and cannot be exchanged between users or transported

• Can specify data source explicitly. Tables, table joins, logical databases and infosets can all serve as data sources.

• May convert to a SAP Query and infoset and made available to other users in a specific user group.

Use extreme caution if using PA and PD tables.Use Infosets when possible Caution

Things we Use…..

[


SAP Query (SQ01)

• A comprehensive tool for defining reports in different forms such as basic lists, statistics, or ranked lists

• Requires an Infoset

• Available to other users in specific user group

• Can exist in 2 different query areas

• Global – client independent and are transported automatically (Create Global for use in transactions)

• Standard – client dependent and are not automatically transported.

• Global SAP Query can be assigned to a transaction via SE93

• Transaction can be assigned to security roles

Things we Use…..

[


Get the facts…

[


Dynamic Actions

• Dynamic actions trigger automatic processing when specific infotype records are maintained

• More powerful when used with ABAP code

Things we Use…..

[


Get the facts…

[


User Exits

• SAP created customer exits for specific programs, screens, and menus within standard R/3 applications.

• Exits contain no functionality

• Exits act as hooks - add-on functionality

• Do not affect standard SAP source code

• Do not affect your standard maintenance procedures (adding support packs)

• Are not available for all programs and screens

• Can only be used they already exist in the SAP System.

• Locate applications with pre-defined exits in Locating Applications that have Exits.

Things we Use…..

mk:@MSITStore:\\us0130sutp\ecc50help\htmlhelp\helpdata\EN\00000942.chm::/C81975F343B111D1896F0000E8322D00/content.htm

mk:@MSITStore:\\us0130sutp\ecc50help\htmlhelp\helpdata\EN\00000942.chm::/C81975F343B111D1896F0000E8322D00/content.htm

[


Get the facts…

[


BaDI - Business Add-Ins

• Provided with Release 4.6A and forward

• Delivers an Enhancement technique, known as Business Add-Ins.

• Like User Exits, can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery

• Business add-ins allow enhancements to the standard version of the system.

Things we Use…..

mk:@MSITStore:\\us0130sutp\ecc50help\htmlhelp\helpdata\EN\00000942.chm::/EEA1D548892B11D295D60000E82DE14A/content.htm



[


Get the facts…

[


Create Infotypes

• Requires ABAP Skills

• Requires Experience Using Screen Painter and ABAP Dictionary

• Remember: from the user’s perspective, it’s an input screen; technically it’s a data structure

• Data assigned to an infotype is always assigned to one employee

• The number range reserved for customer infotypes is 9000 to 9999

Things we Use…..

[


Get the facts…

[


Variants

• Use to define selection options used frequently

• Helps end-users execute reports with pre-determined values – no thinking required!

• When you call up a variant, system automatically enters selection variants

• Information System Tools Hierarchy Reports Background processing

Things we Use…..

[


Get the facts…

[


Business Case #1 – Alternative Cost Center

Variable compensation payment needs to be charged to a

business area that is not the employee’s current business area

Entry of Payment occurs on Infotype 0015

Payment will automatically go to employees current cost center

on Infotype 0001

The business wants costs allocated elsewhere

Payroll needs alternative cost center on Infotype 15

How to get the data out of Infotype 15?

20

[


Maintain cost assignment


[


Quickviewer, SAP Query, Infoset, and a Transaction

22


Solution

Quickviewer tool (Transaction SQVI)

Join Tables PA0015 and ASSOB_HR

Convert to an SAP Query and Infoset

Use SE93 Maintain Transaction to create a

transaction for users to access the Query

Assign Transaction to Security Role(s)

[


Join Tables in QuickViewer

Quickviewer Join Conditions

[


Quickviewer End Result Convert to an SAP Query; Give to End-Users with a Transaction

[


Business Case #2 – Payroll on Withdrawn Status

Employee set to Status Withdrawn Status

Advantage of Withdrawn Status – No longer processes thru

payroll, saving time and resources

Disadvantage of Withdrawn Status – Future post-employment

payouts cannot be made without a Payroll specialists intervention

Scenario: Terminated Employee is Eligible for future payment

Payment will be processed through Infotype 15

Need employee to process through payroll, although set to

Withdrawn

Desire to maximize Payroll resources and avoid manual intervention

25

[


Create Dynamic Action or BaDI

26


Solution

When Infotype 15 or 221 is created for Withdrawn

Employee, automatically set Payroll Control Record

(Infotype0003) to permit Run payroll up to date to

date of payment

[


Dynamic Action vs BaDI

27

• Works when run in foreground

• Extremely easy to set up

• Automates efforts for the Power User

Dynamic Action

• Works in background or foreground

• Can be used with both Power User entries and incoming interface entries

• Requires understanding of ABAP Code

BaDI

[


Personnel Admin Customizing Procedures

28


Dynamic Action

[



Additional Payment for Withdrawn Employee

[



Date Automatically Updated in Background

[


Created with transaction SE19 – Business Add-Ins: Initial

Implementation Maintenance Screen

ZP_HRPAD00INFTY_0221 for Infotype 221 and

ZP_HRPAD00INFTY_0015 for Infotype 15

For Personnel Administration Infotypes use Definition

HRPAD00INFTY

We used IN_Update Method - write ABAP code

Activate using Ctrl F3 or

31


The BaDI

[



BAdI - Definition HRPAD00INFTY SAP HELP

32

[



BAdI - Create using transaction SE19

33

[



BAdI - Attributes

34

[



BAdI - Interface/Methods

35

[


Payroll Results Adjustment is created via an

interface program for withdrawn employee

Payment

made to

Terminated

Employee

[



Date is automatically updated in the background

[


Business Case #3 – Comp Planning Grade History

Compensation requires most recent Date in Grade (X6) which

is maintained on Infotype 41 – Date Specifications

Power Users forget to update this field

38

[



Solution

Combined Dynamic Action and ABAP code

Anytime Grade changes on Infotype 8 (Basic Pay) - Dynamic

Action checks if previous grade is not equal to current grade

being saved on Basic Pay (Infotype 8)

ABAP code routine locates the Date in Grade (X6) on

Infotype 41 (Date Specifications)

Dynamic Action copies Infotype 41 in background and Updates

start date from Infotype 8 on Infotype 41 in X6 location

39

Dynamic Action Using ABAP Code

[



Basic Pay is created with new grade

[



Date Type X6 automatically updated on Infotype 41

[


Business Case #4 – Integrate Separate HR

and ERP Instances

Integration HR with ERP for Travel Management and Time

Entry

Goal: Fulfill ERP and Travel cost assignment objectives while

maintaining HR structure

HR Position maintains cost center of Org Unit

Infotype 27 Cost Distribution and 315 Time Sheet Defaults may

be required if true charge code is different from that on Org

Unit

Requirement For Specific Personnel Actions

If Cost Center changes on Position – IT 27 and 315 may need

to be updated based on type of cost center and specific

process42

[



and ERP Instances

Solution

Dynamic Action with ABAP procedure checks for specific

action being executed

Dynamic Action with ABAP procedure checks if cost center

has changed and what type of cost center it is (True or

Dummy)

Based on type of cost center Infotype 27 and Infotype 315 can

be created or delimitd

User Exit PBAS0001 (component EXIT_SAPFP50M_001) is

used to default cost center from Infotype 27 onto Infotype 315

if necessary

Activate User Exit using Ctrl F3 or 43

Combine User Exit with Dynamic Action

[


Creation of Infotype 0027 and 0315 Scenarios –Triggered by specific actions and change to cost center

For Example

1) New Employee in SAP – No prior Cost Center

2) Existing Employee Cost Center Change on current

or new position

Is current cost center

True or Dummy?Dummy

Does employee

have previous

cost center?

Is Previous

Cost Center

Dummy?Internal

No

Create Infotype 0315 –

Cost Center Defaults

from Infotype 0001

Yes

Delimit IT0027

subtype 1 and 2

Create IT0027

subtype 1 and 2

Create Infotype 0315 –

Cost Center Defaults

from Infotype 0027

True

Cost CenterDoes IT0027

have Internal

order or cost center?

No

Yes

End

End

Does employee

have existing IT0315?

Yes

Delimit IT0315

End

[



and ERP Instances

Transaction CMOD – Create Project

45

[


Business Case #4 – Integrate Separate HR and

ERP Instances - Enhancement PBAS0001

Components

46

[



and ERP Instances

Cost center changes on position

47

[



ERP Instances

Power user is prompted to create Infotype 27 Subtype 1

48

[



ERP Instances

After Infotype 27 Subtype 1 is created – Dynamic Action

will create Infotype 27 Subtype 2 in background and default

values with user exit

49

[



ERP Instances

Dynamic Action will create Infotype 315 and default cost

center from Infotype 27 with user exit

50

[


Business Case #5 – Handling Unicode Characters

Upgraded to ECC 5.0 and Unicode enabled – Now SAP could

accept double-byte characters

However, downstream suppliers could not accept double-byte

characters

How to allow update of Infotype 2 (Personal Data) and

Infotype 21 (Familiy Related) – possibly entering double-byte

characters – but prevent these from being saved on the

infotype

51

[


Business Case #5 – Handling Unicode Characters

Solution

User Exit PB

AS0001 – Component EXIT_SAPFP50M_002

Restrict Asian Characters with "Invalid Character" message

Allow European and US characters

Not allowed : Asian: ジェームス

Allowed - European:

Polish: Ą Ć Ę Ł Ń Ó Ś Ź Ż

Czech: Á Č Ď É Ě Í Ň Ó Ř Š Ť Ú Ŧ Ý Ţ

Slovak: á ä č ď dz dţ é ch í ľ ĺ ň ó ô ŕ š ť ú ý ţ

Other European: à á â ã ä å þ Þ ß Ç ç ţ52

User Exit

[


Business Case #5 – Handling Unicode

CharactersPA30 – Entry of Personal Data

53

Invalid Characters Error

[


Business Case #5 – Handling Unicode

CharactersPA30 – Entry of Family Members

54

Invalid Characters Error

[


Business Case #6 – Retirement Plan

Changes Requires Separate Date Tracking

Retirement Plan changed to stage eligibility according to

employee’s age and years of service

Employees over set age and years of service remain eligible for

traditional pension benefit

Other employees have new eligibility dates

Infotype 0041 – Date Specifications tracks eligibility dates – but

was full!

55

[


Business Case #6 –Separate Date Tracking

Solution

Create Custom Infotype 9041 - Date Specifications 2 to hold

additional dates

Use this infotype for established Pension Plans where there will

be no new entrants

Use data on this infotype in interfaces / reports

Transaction PM01 – Create Infotype

Updated Infosets to use in SAP Query

56

Customer Infotype

[



Transaction PM01

57

[



Structure

58

[



Module Pool

59

[



Screen Painter

60

[



Infotype Attributes

61

[



Original Infotype 41 Date Specifications

62

[



Infotype 9041 Date Specifications 2

63

[


Business Case #7 – Control Access to Data

Pulled into Reports

Manager do not have time or expertise to know what data to

“pull” from SAP HR

Goal: Make it as straightforward as possible for them

Need to default dates, year, currency, etc. in compensation

planning reports and programs to control what the Managers

see

64

[



Solution

Global Variants – System Variants CUS& transportable

Use Transaction STVARVC to update values for variants

65

Variants

[



Transaction STVARVC

66

[



Global Variant

67

[



SAP Query run with variant

68

[



Program Variant

69

[



Program run with variant

70

[


Use Simple SAP Tools . . .

And Life Returns to Normal Quick Viewer

SAP Query

Customer-Defined Transactions Assigned to Security Roles

Dynamic Actions

User Exits or BAdI’s

Custom Infotypes

Variants

71

[


SAP – Simple.

72

[


Help.sap.com

Follow SAP QUERY > Tools for Queries > QuickViewer >

Creating QuickViews

SAP Developers Network

https://www.sdn.sap.com/irj/sdn/thread?threadID=230561

SAP Training Course

BC407 QuickViews,InfoSet Query,SAP Query

Resources

[


Questions

Donna Wendling

[email protected]

mailto:[email protected]

[


Call For Speakers – Annual Conference 2009

The ASUG Annual Conference call for speakers opens October 13

through December 1, 2008.

Submit your abstract and tell your SAP story! In exchange, you’ll

receive complimentary registration for the full event (including

Sapphire).

ASUG and Sapphire will again be co-located in 2009 in Orlando,

May 11-14, 2009.

[


] Thank you for your participation.

Your Feedback is important – please complete this session evaluation form.

Speaker: Donna Wendling

Session:

sap... simple!

Documents