1. SAP SIMPLE!? Yes, There Are Simple Solutions to Business Dilemmas Donna L Wendling Sherryanne H Meyer Air Products and Chemicals, Inc.
2. 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
4. 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
5. 5 Air Products and Chemicals Presents THE MOST MEMORABLE… THE MOST STARTLING… EXPERIENCES OF OUR SAP LIVES! Only ASUG could save them! From the Blackness of a Hundred Million Nights Comes a tale so terrifying…
19. 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
20. 21 Business Case #1 – Alternative Cost Center Maintain cost assignment
24. Use SE93 Maintain Transaction to create a transaction for users to access the Query
25.
26. 24 Quickviewer End Result Convert to an SAP Query; Give to End-Users with a Transaction
27. Business Case #2 – Payroll on Withdrawn Status Employee set to Status WithdrawnStatus 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
28.
29. 28 Dynamic Action Business Case #2 – Payroll on Withdrawn Status Personnel Admin Customizing Procedures
30. 29 Business Case #2 – Payroll on Withdrawn Status Additional Payment for Withdrawn Employee
31. 30 Business Case #2 – Payroll on Withdrawn Status Date Automatically Updated in Background
32. 31 The BaDI Business Case #2 – Payroll on Withdrawn Status 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
33. Business Case #2 – Payroll on Withdrawn Status BAdI - Definition HRPAD00INFTY SAP HELP 32
34. Business Case #2 – Payroll on Withdrawn Status BAdI - Create using transaction SE19 33
35. Business Case #2 – Payroll on Withdrawn Status BAdI - Attributes 34
36. Business Case #2 – Payroll on Withdrawn Status BAdI - Interface/Methods 35
37. 36 Payroll Results Adjustment is created via an interface program for withdrawn employee Payment made to Terminated Employee
38. 37 Business Case #2 – Payroll on Withdrawn Status Date is automatically updated in the background
39. 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
40. Business Case #3 – Comp Planning Grade HistorySolution 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
41. 40 Business Case #3 – Comp Planning Grade History Basic Pay is created with new grade
42. 41 Business Case #3 – Comp Planning Grade History Date Type X6 automatically updated on Infotype 41
43. 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 42
44. Business Case #4 – Integrate Separate HR and ERP InstancesSolution 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
45.
46. Business Case #4 – Integrate Separate HR and ERP InstancesTransaction CMOD – Create Project 45
47. Business Case #4 – Integrate Separate HR and ERP Instances - Enhancement PBAS0001Components 46
48. Business Case #4 – Integrate Separate HR and ERP InstancesCost center changes on position 47
49. Business Case #4 – Integrate Separate HR and ERP InstancesPower user is prompted to create Infotype 27 Subtype 1 48
50. Business Case #4 – Integrate Separate HR and 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
51. Business Case #4 – Integrate Separate HR and ERP Instances Dynamic Action will create Infotype 315 and default cost center from Infotype 27 with user exit 50
52. 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
53. Business Case #5 – Handling Unicode CharactersSolution 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
54. Business Case #5 – Handling Unicode CharactersPA30 – Entry of Personal Data 53 Invalid Characters Error
55. Business Case #5 – Handling Unicode CharactersPA30 – Entry of Family Members 54 Invalid Characters Error
56. 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
57. Business Case #6 –Separate Date TrackingSolution 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
63. Business Case #6 –Separate Date Tracking Original Infotype 41 Date Specifications 62
64. Business Case #6 –Separate Date Tracking Infotype 9041 Date Specifications 2 63
65. 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
66. Business Case #7 – Control Access to Data Solution Global Variants – System Variants CUS& transportable Use Transaction STVARVC to update values for variants 65 Variants
67. Business Case #7 – Control Access to Data Transaction STVARVC 66
71. Business Case #7 – Control Access to Data Program run with variant 70
72. 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
80. 75 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.
81. 76 ] Thank you for your participation. Your Feedback is important – please complete this session evaluation form. Speaker: Donna Wendling Session:
