SAP SIMPLE!?  Yes, There Are Simple Solutions to Business Dilemmas<br />Donna L Wendling<br />Sherryanne H Meyer<br />Air ...
Introduction<br />Having trouble meeting your business’s needs with standard SAP ?<br />Do you lose sleep over needing an ...
3<br />
Learning Points <br />Fear no more!  <br />Today we’ll show you how to:<br />Think outside of the box to get the most out ...
5<br />Air Products and Chemicals<br />Presents<br />THE MOST MEMORABLE…<br />THE MOST STARTLING…<br />EXPERIENCES OF <br ...
6<br />Return on Investment<br /><ul><li>  Or Therapists!</li></li></ul><li>7<br />Things we Use…..<br />Caution<br />
8<br />Things we Use…..<br />
9<br />Get the facts…<br />
10<br />Things we Use…..<br />
Get the facts…<br />
12<br />Things we Use…..<br />
13<br />Get the facts…<br />
14<br />Things we Use…..<br />
15<br />Get the facts…<br />
16<br />Things we Use…..<br />
17<br />Get the facts…<br />
18<br />Things we Use…..<br />
19<br />Get the facts…<br />
Business Case #1 – Alternative Cost Center<br />Variable compensation payment needs to be charged to a business area that ...
21<br />Business Case #1 – Alternative Cost Center<br />Maintain cost assignment<br />
22<br />Business Case #1 – Alternative Cost Center Solution<br /><ul><li>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) </li></li></ul><li>23<br />Join Tables in QuickViewer<br />Quickviewer Join Conditi...
24<br />Quickviewer End Result <br />Convert to an SAP Query; Give to End-Users with a Transaction<br />
Business Case #2 – Payroll on Withdrawn Status  <br />Employee set to Status WithdrawnStatus<br />Advantage of Withdrawn S...
26<br />Business Case #2 – Payroll on Withdrawn Status<br />Solution  <br /><ul><li>When Infotype 15 or 221 is created for...
28<br />Dynamic Action<br />Business Case #2 – Payroll on Withdrawn Status  <br />Personnel Admin    Customizing Procedur...
29<br />Business Case #2 – Payroll on Withdrawn Status  <br />Additional Payment for Withdrawn Employee<br />
30<br />Business Case #2 – Payroll on Withdrawn Status  <br />Date Automatically Updated in Background<br />
31<br />The BaDI<br />Business Case #2 – Payroll on Withdrawn Status  <br />Created with transaction SE19 – Business Add-I...
Business Case #2 – Payroll on Withdrawn Status  BAdI - Definition HRPAD00INFTY<br />SAP HELP<br />32<br />
Business Case #2 – Payroll on Withdrawn Status  BAdI - Create using transaction SE19<br />33<br />
Business Case #2 – Payroll on Withdrawn Status  BAdI - Attributes<br />34<br />
Business Case #2 – Payroll on Withdrawn Status  BAdI - Interface/Methods<br />35<br />
36<br />Payroll Results Adjustment is created via an interface program for withdrawn employee<br />Payment made to Termina...
37<br />Business Case #2 – Payroll on Withdrawn Status  <br />Date is automatically updated in the background<br />
Business Case #3 – Comp Planning Grade History<br />Compensation requires most recent Date in Grade (X6) which is maintain...
Business Case #3 – Comp Planning Grade HistorySolution <br />Combined Dynamic Action and ABAP code<br />Anytime Grade chan...
40<br />Business Case #3 – Comp Planning Grade History<br />Basic Pay is created with new grade <br />
41<br />Business Case #3 – Comp Planning Grade History<br />Date Type X6 automatically updated on Infotype 41 <br />
Business Case #4 – Integrate Separate HR and ERP Instances<br />Integration HR with ERP for Travel Management and Time Ent...
Business Case #4 – Integrate Separate HR and ERP InstancesSolution<br />Dynamic Action with ABAP procedure checks for spec...
Is current cost center <br /> True or Dummy?<br />Create IT0027<br /> subtype 1 and 2<br />Does employee<br /> have previo...
Business Case #4 – Integrate Separate HR and ERP InstancesTransaction CMOD – Create Project<br />45<br />
Business Case #4 – Integrate Separate HR and ERP Instances - Enhancement  PBAS0001Components<br />46<br />
Business Case #4 – Integrate Separate HR and ERP InstancesCost center changes on position<br />47<br />
Business Case #4 – Integrate Separate HR and ERP InstancesPower user is prompted  to create Infotype 27 Subtype 1<br />48<...
Business Case #4 – Integrate Separate HR and ERP Instances After  Infotype 27 Subtype 1 is created – Dynamic Action will c...
Business Case #4 – Integrate Separate HR and ERP Instances Dynamic Action will create Infotype 315 and  default cost cente...
Business Case #5 – Handling Unicode Characters<br />Upgraded to ECC 5.0 and Unicode enabled – Now SAP could accept double-...
Business Case #5 – Handling Unicode CharactersSolution<br />User Exit PB<br />AS0001 – Component EXIT_SAPFP50M_002<br />Re...
Business Case #5 – Handling Unicode CharactersPA30 – Entry of Personal Data<br />53<br />Invalid Characters Error<br />
Business Case #5 – Handling Unicode CharactersPA30 – Entry of Family Members <br />54<br />Invalid Characters Error<br />
Business Case #6 – Retirement Plan Changes Requires Separate Date Tracking<br />Retirement Plan changed to stage eligibili...
Business Case #6 –Separate Date TrackingSolution <br />Create Custom Infotype 9041 - Date Specifications 2 to hold additio...
Business Case #6 –Separate Date Tracking Transaction PM01 <br />57<br />
Business Case #6 –Separate Date Tracking Structure<br />58<br />
Business Case #6 –Separate Date Tracking Module Pool<br />59<br />
Business Case #6 –Separate Date Tracking Screen Painter<br />60<br />
Business Case #6 –Separate Date Tracking Infotype Attributes<br />61<br />
Business Case #6 –Separate Date Tracking Original Infotype 41 Date Specifications<br />62<br />
Business Case #6 –Separate Date Tracking Infotype 9041 Date Specifications 2<br />63<br />
Business Case #7 – Control Access to Data Pulled into Reports<br />Manager do not have time or expertise to know what data...
Business Case #7 – Control Access to Data Solution <br />Global Variants – System Variants CUS& transportable<br />Use Tra...
Business Case #7 – Control Access to Data Transaction STVARVC <br />66<br />
Business Case #7 – Control Access to Data Global Variant <br />67<br />
Business Case #7 – Control Access to Data SAP Query run with variant<br />68<br />
Business Case #7 – Control Access to Data Program Variant<br />69<br />
Business Case #7 – Control Access to Data Program run with variant<br />70<br />
Use Simple SAP Tools . . .And Life Returns to Normal<br />Quick Viewer<br />SAP Query<br />Customer-Defined Transactions A...
SAP – Simple.<br />72<br />
73<br />Resources<br /><ul><li>Help.sap.com
Follow SAP QUERY > Tools for Queries > QuickViewer > Creating QuickViews
SAP Developers Network
Upcoming SlideShare
Loading in …5
×

Sap Simple!

3,390 views

Published on

0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,390
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

Sap Simple!

  1. 1. SAP SIMPLE!? Yes, There Are Simple Solutions to Business Dilemmas<br />Donna L Wendling<br />Sherryanne H Meyer<br />Air Products and Chemicals, Inc.<br />
  2. 2. Introduction<br />Having trouble meeting your business’s needs with standard SAP ?<br />Do you lose sleep over needing an immediate solution and not having a straightforward solution from SAP?<br />Do you ever feel like this……..<br />2<br />
  3. 3. 3<br />
  4. 4. Learning Points <br />Fear no more! <br />Today we’ll show you how to:<br />Think outside of the box to get the most out of your SAP Deployment and to meet your business needs<br />Take advantage of SAP delivered options for reporting and consolidating tables<br />Maximize SAP functionality – without customization <br />4<br />
  5. 5. 5<br />Air Products and Chemicals<br />Presents<br />THE MOST MEMORABLE…<br />THE MOST STARTLING…<br />EXPERIENCES OF <br />OUR SAP LIVES!<br />Only ASUG <br />could save them!<br />From the Blackness of a Hundred Million Nights<br />Comes a tale so terrifying…<br />
  6. 6. 6<br />Return on Investment<br /><ul><li> Or Therapists!</li></li></ul><li>7<br />Things we Use…..<br />Caution<br />
  7. 7. 8<br />Things we Use…..<br />
  8. 8. 9<br />Get the facts…<br />
  9. 9. 10<br />Things we Use…..<br />
  10. 10. Get the facts…<br />
  11. 11. 12<br />Things we Use…..<br />
  12. 12. 13<br />Get the facts…<br />
  13. 13. 14<br />Things we Use…..<br />
  14. 14. 15<br />Get the facts…<br />
  15. 15. 16<br />Things we Use…..<br />
  16. 16. 17<br />Get the facts…<br />
  17. 17. 18<br />Things we Use…..<br />
  18. 18. 19<br />Get the facts…<br />
  19. 19. Business Case #1 – Alternative Cost Center<br />Variable compensation payment needs to be charged to a business area that is not the employee’s current business area<br />Entry of Payment occurs on Infotype 0015<br />Payment will automatically go to employees current cost center on Infotype 0001<br />The business wants costs allocated elsewhere <br />Payroll needs alternative cost center on Infotype 15<br />How to get the data out of Infotype 15?<br />20<br />
  20. 20. 21<br />Business Case #1 – Alternative Cost Center<br />Maintain cost assignment<br />
  21. 21. 22<br />Business Case #1 – Alternative Cost Center Solution<br /><ul><li>Quickviewer tool (Transaction SQVI)
  22. 22. Join Tables PA0015 and ASSOB_HR
  23. 23. Convert to an SAP Query and Infoset
  24. 24. Use SE93 Maintain Transaction to create a transaction for users to access the Query
  25. 25. Assign Transaction to Security Role(s) </li></li></ul><li>23<br />Join Tables in QuickViewer<br />Quickviewer Join Conditions <br />
  26. 26. 24<br />Quickviewer End Result <br />Convert to an SAP Query; Give to End-Users with a Transaction<br />
  27. 27. Business Case #2 – Payroll on Withdrawn Status <br />Employee set to Status WithdrawnStatus<br />Advantage of Withdrawn Status – No longer processes thru payroll, saving time and resources<br />Disadvantage of Withdrawn Status – Future post-employment payouts cannot be made without a Payroll specialists intervention<br />Scenario: Terminated Employee is Eligible for future payment <br />Payment will be processed through Infotype 15<br />Need employee to process through payroll, although set to Withdrawn<br />Desire to maximize Payroll resources and avoid manual intervention<br />25<br />
  28. 28. 26<br />Business Case #2 – Payroll on Withdrawn Status<br />Solution <br /><ul><li>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</li></li></ul><li>Dynamic Action vs BaDI<br />27<br />
  29. 29. 28<br />Dynamic Action<br />Business Case #2 – Payroll on Withdrawn Status <br />Personnel Admin  Customizing Procedures<br />
  30. 30. 29<br />Business Case #2 – Payroll on Withdrawn Status <br />Additional Payment for Withdrawn Employee<br />
  31. 31. 30<br />Business Case #2 – Payroll on Withdrawn Status <br />Date Automatically Updated in Background<br />
  32. 32. 31<br />The BaDI<br />Business Case #2 – Payroll on Withdrawn Status <br />Created with transaction SE19 – Business Add-Ins: Initial Implementation Maintenance Screen<br />ZP_HRPAD00INFTY_0221 for Infotype 221 and<br />ZP_HRPAD00INFTY_0015 for Infotype 15<br />For Personnel Administration Infotypes use Definition HRPAD00INFTY<br />We used IN_Update Method - write ABAP code<br />Activate using Ctrl F3 or <br />
  33. 33. Business Case #2 – Payroll on Withdrawn Status BAdI - Definition HRPAD00INFTY<br />SAP HELP<br />32<br />
  34. 34. Business Case #2 – Payroll on Withdrawn Status BAdI - Create using transaction SE19<br />33<br />
  35. 35. Business Case #2 – Payroll on Withdrawn Status BAdI - Attributes<br />34<br />
  36. 36. Business Case #2 – Payroll on Withdrawn Status BAdI - Interface/Methods<br />35<br />
  37. 37. 36<br />Payroll Results Adjustment is created via an interface program for withdrawn employee<br />Payment made to Terminated Employee<br />
  38. 38. 37<br />Business Case #2 – Payroll on Withdrawn Status <br />Date is automatically updated in the background<br />
  39. 39. Business Case #3 – Comp Planning Grade History<br />Compensation requires most recent Date in Grade (X6) which is maintained on Infotype 41 – Date Specifications<br />Power Users forget to update this field <br />38<br />
  40. 40. Business Case #3 – Comp Planning Grade HistorySolution <br />Combined Dynamic Action and ABAP code<br />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)<br />ABAP code routine locates the Date in Grade (X6) on Infotype 41 (Date Specifications)<br />Dynamic Action copies Infotype 41 in background and Updates start date from Infotype 8 on Infotype 41 in X6 location<br />39<br />Dynamic Action Using ABAP Code<br />
  41. 41. 40<br />Business Case #3 – Comp Planning Grade History<br />Basic Pay is created with new grade <br />
  42. 42. 41<br />Business Case #3 – Comp Planning Grade History<br />Date Type X6 automatically updated on Infotype 41 <br />
  43. 43. Business Case #4 – Integrate Separate HR and ERP Instances<br />Integration HR with ERP for Travel Management and Time Entry<br />Goal: Fulfill ERP and Travel cost assignment objectives while maintaining HR structure <br />HR Position maintains cost center of Org Unit<br />Infotype 27 Cost Distribution and 315 Time Sheet Defaults may be required if true charge code is different from that on Org Unit<br />Requirement For Specific Personnel Actions<br />If Cost Center changes on Position – IT 27 and 315 may need to be updated based on type of cost center and specific process<br />42<br />
  44. 44. Business Case #4 – Integrate Separate HR and ERP InstancesSolution<br />Dynamic Action with ABAP procedure checks for specific action being executed<br />Dynamic Action with ABAP procedure checks if cost center has changed and what type of cost center it is (True or Dummy)<br />Based on type of cost center Infotype 27 and Infotype 315 can be created or delimitd<br />User Exit PBAS0001 (component EXIT_SAPFP50M_001) is used to default cost center from Infotype 27 onto Infotype 315 if necessary<br />Activate User Exit using Ctrl F3 or <br />43<br />Combine User Exit with Dynamic Action<br />
  45. 45. Is current cost center <br /> True or Dummy?<br />Create IT0027<br /> subtype 1 and 2<br />Does employee<br /> have previous<br /> cost center?<br />Does IT0027<br />have Internal<br /> order or cost center?<br />Is Previous<br /> Cost Center <br />Dummy?<br />Create Infotype 0315 –<br />Cost Center Defaults<br />from Infotype 0027<br />Does employee<br /> have existing IT0315?<br />Delimit IT0027<br /> subtype 1 and 2 <br />End<br />Create Infotype 0315 –<br />Cost Center Defaults<br />from Infotype 0001<br />Delimit IT0315<br />End<br />End<br />Creation of Infotype 0027 and 0315 Scenarios – Triggered by specific actions and change to cost center<br />For Example <br /><ul><li>) New Employee in SAP – No prior Cost Center</li></ul>2) Existing Employee Cost Center Change on current <br /> or new position<br />Dummy<br />True<br />No<br />Yes<br />Cost Center<br />No<br />Internal<br />Yes<br />Yes<br />
  46. 46. Business Case #4 – Integrate Separate HR and ERP InstancesTransaction CMOD – Create Project<br />45<br />
  47. 47. Business Case #4 – Integrate Separate HR and ERP Instances - Enhancement PBAS0001Components<br />46<br />
  48. 48. Business Case #4 – Integrate Separate HR and ERP InstancesCost center changes on position<br />47<br />
  49. 49. Business Case #4 – Integrate Separate HR and ERP InstancesPower user is prompted to create Infotype 27 Subtype 1<br />48<br />
  50. 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<br />49<br />
  51. 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<br />50<br />
  52. 52. Business Case #5 – Handling Unicode Characters<br />Upgraded to ECC 5.0 and Unicode enabled – Now SAP could accept double-byte characters <br />However, downstream suppliers could not accept double-byte characters<br />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<br />51<br />
  53. 53. Business Case #5 – Handling Unicode CharactersSolution<br />User Exit PB<br />AS0001 – Component EXIT_SAPFP50M_002<br />Restrict Asian Characters with &quot;Invalid Character&quot; message<br />Allow European and US characters<br />Not allowed :  Asian: ジェームス<br />Allowed - European: <br /> Polish: Ą Ć Ę Ł Ń Ó Ś Ź Ż<br /> Czech: Á Č Ď É Ě Í Ň Ó Ř Š Ť Ú Ů Ý Ž <br /> Slovak: á ä č ď dz dž é ch í ľ ĺ ň ó ô ŕ š ť ú ý ž <br /> Other European: à á â ã ä å þ Þ ß Ç ç ž<br />52<br />User Exit<br />
  54. 54. Business Case #5 – Handling Unicode CharactersPA30 – Entry of Personal Data<br />53<br />Invalid Characters Error<br />
  55. 55. Business Case #5 – Handling Unicode CharactersPA30 – Entry of Family Members <br />54<br />Invalid Characters Error<br />
  56. 56. Business Case #6 – Retirement Plan Changes Requires Separate Date Tracking<br />Retirement Plan changed to stage eligibility according to employee’s age and years of service<br />Employees over set age and years of service remain eligible for traditional pension benefit<br />Other employees have new eligibility dates<br />Infotype 0041 – Date Specifications tracks eligibility dates – but was full!<br />55<br />
  57. 57. Business Case #6 –Separate Date TrackingSolution <br />Create Custom Infotype 9041 - Date Specifications 2 to hold additional dates<br />Use this infotype for established Pension Plans where there will be no new entrants<br />Use data on this infotype in interfaces / reports<br />Transaction PM01 – Create Infotype<br />Updated Infosets to use in SAP Query<br />56<br />Customer Infotype<br />
  58. 58. Business Case #6 –Separate Date Tracking Transaction PM01 <br />57<br />
  59. 59. Business Case #6 –Separate Date Tracking Structure<br />58<br />
  60. 60. Business Case #6 –Separate Date Tracking Module Pool<br />59<br />
  61. 61. Business Case #6 –Separate Date Tracking Screen Painter<br />60<br />
  62. 62. Business Case #6 –Separate Date Tracking Infotype Attributes<br />61<br />
  63. 63. Business Case #6 –Separate Date Tracking Original Infotype 41 Date Specifications<br />62<br />
  64. 64. Business Case #6 –Separate Date Tracking Infotype 9041 Date Specifications 2<br />63<br />
  65. 65. Business Case #7 – Control Access to Data Pulled into Reports<br />Manager do not have time or expertise to know what data to “pull” from SAP HR<br />Goal: Make it as straightforward as possible for them<br />Need to default dates, year, currency, etc. in compensation planning reports and programs to control what the Managers see<br />64<br />
  66. 66. Business Case #7 – Control Access to Data Solution <br />Global Variants – System Variants CUS& transportable<br />Use Transaction STVARVC to update values for variants<br />65<br />Variants<br />
  67. 67. Business Case #7 – Control Access to Data Transaction STVARVC <br />66<br />
  68. 68. Business Case #7 – Control Access to Data Global Variant <br />67<br />
  69. 69. Business Case #7 – Control Access to Data SAP Query run with variant<br />68<br />
  70. 70. Business Case #7 – Control Access to Data Program Variant<br />69<br />
  71. 71. Business Case #7 – Control Access to Data Program run with variant<br />70<br />
  72. 72. Use Simple SAP Tools . . .And Life Returns to Normal<br />Quick Viewer<br />SAP Query<br />Customer-Defined Transactions Assigned to Security Roles<br />Dynamic Actions<br />User Exits or BAdI’s<br />Custom Infotypes<br />Variants<br />71<br />
  73. 73. SAP – Simple.<br />72<br />
  74. 74. 73<br />Resources<br /><ul><li>Help.sap.com
  75. 75. Follow SAP QUERY > Tools for Queries > QuickViewer > Creating QuickViews
  76. 76. SAP Developers Network
  77. 77. https://www.sdn.sap.com/irj/sdn/thread?threadID=230561
  78. 78. SAP Training Course
  79. 79. BC407 QuickViews,InfoSetQuery,SAP Query </li></li></ul><li>74<br />Questions<br />Donna Wendling<br />wendlidl@airproducts.com<br />
  80. 80. 75<br />Call For Speakers – Annual Conference 2009<br />The ASUG Annual Conference call for speakers opens October 13 through December 1, 2008. <br />Submit your abstract and tell your SAP story! In exchange, you’ll receive complimentary registration for the full event (including Sapphire).<br />ASUG and Sapphire will again be co-located in 2009 in Orlando,<br /> May 11-14, 2009. <br />
  81. 81. 76<br />]<br />Thank you for your participation.<br /> Your Feedback is important – please complete this session evaluation form. <br />Speaker: Donna Wendling<br />Session: <br />

×