SAP... Simple!

[
SAP SIMPLE!?
Yes, There Are Simple Solutions to Business Dilemmas
Donna L Wendling
]
Sherryanne H Meyer
Air Products and Chemicals, Inc.

[ CHRISTINA CRONE
ASUG INSTALLATION MEMBER
MEMBER SINCE: 1999

[ MIKE STOKO
ASUG BOARD OF DIRECTORS
MEMBER SINCE: 2003

[ BOB GAUTHIER
ASUG ASSOCIATE MEMBER
MEMBER SINCE:1998

Real Experience. Real Advantage.

[ 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……..

Real Experience. Real Advantage. 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


[


[ 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!

[ Things we Use…..
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


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


[ Get the facts…


Dynamic Actions

• Dynamic actions trigger automatic processing when specific
infotype records are maintained
• More powerful when used with ABAP code


[ 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.


[ 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.


[ 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


[ 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


[ 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?


Maintain cost assignment


Solution

Quickviewer, SAP Query, Infoset, and a
Transaction
 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


[ Convert to an SAP Query; Give to End-Users
Quickviewer End Result
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


Business Case #2 – Payroll on Withdrawn Status
[ Solution

Create Dynamic Action or BaDI

 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

• Works when run in foreground
Dynamic • Extremely easy to set up
Action • Automates efforts for the Power User

• Works in background or foreground
• Can be used with both Power User
BaDI entries and incoming interface entries
• Requires understanding of ABAP Code


Dynamic Action
 Personnel Admin  Customizing Procedures


Business Case #2 – Payroll on Withdrawn Status
[ Additional Payment for Withdrawn Employee


Date Automatically Updated in Background


The BaDI
 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


BAdI - Definition HRPAD00INFTY
 SAP HELP


BAdI - Create using transaction SE19


BAdI - Attributes


BAdI - Interface/Methods


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


Business Case #3 – Comp Planning Grade History
[ Solution
Dynamic Action Using ABAP Code
 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


[ 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
process

Business Case #4 – Integrate Separate HR
[ and ERP Instances
Solution
Combine User Exit with Dynamic Action
 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

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
Dummy True
True or Dummy?
Create IT0027
subtype 1 and 2 Does employee
No have previous
cost center?

Does IT0027
have Internal Cost Center Yes
order or cost center?

Is Previous
No Cost Center
Dummy?
Internal
Create Infotype 0315 –
Cost Center Defaults
from Infotype 0027 Yes
Does employee
Delimit IT0027
have existing IT0315?
End subtype 1 and 2

Create Infotype 0315 –
Yes Cost Center Defaults
from Infotype 0001
Delimit IT0315

End

End

[ and ERP Instances

Transaction CMOD – Create Project


Business Case #4 – Integrate Separate HR and
[ ERP Instances - Enhancement PBAS0001

Components


[ and ERP Instances
Cost center changes on position


[ Business Case #4 – Integrate Separate HR and
ERP Instances

Power user is prompted to create Infotype 27 Subtype 1


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


ERP Instances

Dynamic Action will create Infotype 315 and default cost
center from Infotype 27 with user exit


[ 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


[ Business Case #5 – Handling Unicode Characters
Solution
User Exit
 User Exit PB
 AS0001 – Component EXIT_SAPFP50M_002
 Restrict Asian Characters with quot;Invalid Characterquot; message
 Allow European and US characters
 Not allowed : Asian: ジェームス
 Allowed - European:
 Polish: Ą Ć Ę Ł Ń Ó Ś Ź Ż
 Czech: Á Č Ď É Ě Í Ň Ó Ř Š Ť Ú Ŧ Ý Ţ
 Slovak: á ä č ď dz dţ é ch í ľ ĺ ň ó ô ŕ š ť ú ý ţ
 Other European: à á â ã ä å þ Þ ß Ç ç ţ

Business Case #5 – Handling Unicode
[ CharactersPA30 – Entry of Personal Data

Invalid Characters Error


[ Business Case #5 – Handling Unicode
CharactersPA30 – Entry of Family Members

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!


Business Case #6 –Separate Date Tracking
[ Solution
Customer Infotype
 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


[ Business Case #6 –Separate Date Tracking
Transaction PM01


Structure


Module Pool


Screen Painter


Infotype Attributes


Original Infotype 41 Date Specifications


Infotype 9041 Date Specifications 2


[ 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


Solution
Variants

 Global Variants – System Variants CUS& transportable
 Use Transaction STVARVC to update values for variants


Transaction STVARVC


Global Variant


SAP Query run with variant


Business Case #7 – Control Access to Data
[ Program Variant


Program run with variant


[ 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


[ SAP – Simple.


[ Resources
 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


[ Questions

Donna Wendling
wendlidl@airproducts.com


[ 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!

Recommended

Recommended

More Related Content

Similar to SAP... Simple!

Similar to SAP... Simple! (20)

More from Sherryanne Meyer, SHRM-SCP

More from Sherryanne Meyer, SHRM-SCP (10)

SAP... Simple!