• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Dynamic Actions On Steroids

Dynamic Actions On Steroids






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.


11 of 1 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • To validate what is configured for a particular facility BEFORE HR goes into a Facility or Contract negotiation. Allows users to see configured tables instead of just what an employee is eligible for.
  • Work Tax Area is defaulted and dynamic action is more streamlined…
  • IN THE IMG under Personnel Administration – Tools – Revision – Setup up change document List of infotypes to be logged….. You setup Infotype changes or field changes.
  • Transparent table PCL4 stores the key to the cluster PCLF. This cluster stores the changes made to infotype documents for personnel and applicants.
  • Changes are selected from cluster PCL4 using relid = SA for specific pernr and change date from Infotype 0002 V_aedtm. Internal table i_pcl4 is appended with cluster key (pcl4-srtfd) and change date (pcl4-aedtm) for the specific pernr
  • Include a statement for the current infotype structure (for example: TABLES: P0006.) In include MPPDAT00, the fields required for flow control of an infotype dialog are defined in the common part. If you have this include in your program, some fields are available immediately: The field string CSAVE refers in each case to the old record whose values can be compared with the new values in the plausibility checks. To do this, define a second work area for the infotype structure that is used to store the contents of CSAVE. This means that the individual names of the infotypes are given. SAP recommends that you use the *-workarea for the infotype structure in each case (for example: *P0006). Internal table DYNMEAS: contains the infotype accesses (see indicator 'I'). Internal table INITIAL_VALUES: contains the default values for an infotype that is created or copied. (see indicator 'W').

Dynamic Actions On Steroids Dynamic Actions On Steroids Presentation Transcript

  • Dynamic Actions on Steroids Session 301 Donna Wendling Sherryanne Meyer
    • Who Is Air Products?
    • Today’s Objectives -- Learning Points
    • Brief Overview – What is a Dynamic Action?
    • The “Basics” - Components of a Dynamic Action
    • Various Scenarios
      • Date Specifications
      • Tax Area
      • Family/Related Persons
    • How To “Kick it up a Notch”
    Today’s Agenda MORE POWER!!!!!
  • Who is Air Products Fast Facts
    • Global gases, chemicals, equipment and services provider
    • Serving technology, energy, healthcare and industrial markets
    • Fortune 500 company
    • Chemical industry safety leader
    • Operations in more than 30 countries
    • ~20,000 employees worldwide
    • Known for our innovative culture and operational excellence
  • SAP HR Countries UK Ireland Belgium Netherlands Germany France United States Canada Spain, Italy, Portugal Indonesia Singapore Malaysia China Hong Kong Japan Korea Taiwan Israel
  • SAP-HR and Air Products
    • 2001 Org Management, HR Admin, Compensation, Benefits, Time Entry, US Payroll, Structural Security, ESS, MDT
    • 2002 Appraisals, C&SP, TEM, Workflow, BW
    • 2002 HR / ERP Integration
    • 2003 HR Phase 3 – Southern Europe
    • 2004 HR Phase 4 – Asia
    • 2004 Recognized SAP Certified Competency Center
    • 2005 MSS-Phase 1
    • 2006 ECC 5.0, Learning Solution, Israel
  • Today’s Objectives: Learning Points
    • What is a Dynamic Action and what can it do for you
      • Automate business processes –
        • Saves time by performing routine tasks
      • Insure data integrity
      • Empower Global Power Users to successfully manage data
    • Create new and improved Dynamic Actions
    • Maximize the power of a Dynamic Actions
    * None of the employees or data represented on the following slides is real.
  • Brief Overview – What is a Dynamic Action?
    • As defined by SAP
    • Dynamic actions trigger automatic processing when specific infotype records are maintained.
    • The advantage of dynamic actions is that the system saves you time by performing routine tasks
  • Brief Overview – Personnel Action vs Dynamic Action
    • Personnel Actions are a series of Infotypes that are added, changed, completely or partially deleted or delimited for the reason specified (i.e. Hiring, Leave, Termination, etc.)
    • Dynamic actions are automated and can use decision logic to enhance a Personnel Action for maintenance of a specific Infotype
  • The Basics - Components of a Dynamic Action IType : Infotype that triggers the dynamic action Sty : Focus on a specific subtype Field n: Start action when maintaining a specific field No : Sequence number Variable Function Part: Specifies the processing details when the dynamic action is triggered FC: Maintenance Operation 02 – Change 04 – Create 06 – Create and change 08 – Delete 10 – Change and Delete 12 – Create and Delete S: Step Indicator P – Check conditions I – Maintain Infotype Record W – Default values for a new record V – Reference to another step F – Call a FORM routine (subroutine in ABAP); M – Send Mail
  • The Basics – Variable Function Part
    • Values of an old data record are in structure PSAVE .
    • Operations on Infotypes can be run in the background by entering /D at the end of the line.
    • Logical OR links must be indicated by /X .
    • When calling a routine you can use internal (module pool) and external routines
      • When calling an external routine, enter name of program in parentheses after the form name
      • It is not possible to transfer parameters to the routine
      • For transferring values from the routine you can use fields in the RP50D structure
  • The Basics – RP50D Structure – Return Values
  • Scenario 1 Date Specifications - Populating Key Dates Dynamically
  • Scenario 1 – Date Specifications Create Key Dates
    • Hire Action (Z1)
    • Dynamic action will create Infotype 0041 (Date Specifications) in background and populate various dates for that employee
            • Original Hire Date (Z1)
            • Employment Date (Z4)
            • Date in Grade (X6)
  • Create IT0041 and populate dates Personnel Action Z1 Create Date Types
  • End Result
  • Scenario 1 – Date Specifications Challenge: Update Key Dates
    • Anytime Pay Scale Group changes on Infotype 0008 (Basic Pay) – Automatically update the Date in Grade (X6) on Infotype 0041 (Date Specifications)
    • BUT ……How do I find the Date in Grade (X6) on Infotype 0041 and update it using a Dynamic Action ????????
  • Answering The Challenge 1. Check Previous Pay Scale Group Not equal to New Pay Scale Group 2. Call procedure to locate X6 Date Type and set RP50D-FIELD1 3. Copy IT 41 in Background 4. Check Value of RP50D-Field1. Update X6 date on IT 41
  • Walk Through: Update Existing Date Type Example: In the Org Reassignment Action, Pay Scale Group is updated on Infotype 0008 (Basic Pay)
  • Procedure to Update Existing Date Type
  • Walk Through: Update Date Type cont’d
  • Scenario 2 Default Tax Area Based on Work Location
  • Scenario 2 – Default U.S. Work Tax Area
    • Hire (Z1), Rehire (Z2) or Org Reassignment (U2) Actions
    • Dynamic Action will Create Infotype 208 (Work Tax Area) and default Tax Area based on employees Personnel Subarea (work location)
  • Scenario 2 – Default Tax Area Based on IT0001-Org Reassignment PSA=157 Work Tax =KY0J
  • End Result
  • Scenario 2 – Default Tax Area The Challenge –Too many Tax Areas!
    • There are so many work Tax Areas to default – we’re running out of room on dynamic action table for Infotype 0001 – maximum 999 lines
    • So how can I manage all the Tax Areas necessary without maxing out the Dynamic actions table entries for 0001??????
  • The Challenge –Too many Tax Areas!
      • 1. Check Action is Hire (Z1), Rehire (Z2) or Org Reassignment (U2) and Country is US
      • 2. Call Procedure to lookup Work Tax Area based on PSA on IT 0001. Set value of RRP50D-FIELD1
    3. Insert Infotype 0208 4. Write RP50D-Field1 to Work Tax area and set percent to 100
  • Walk Thru – New Dynamic Action
  • Procedure for new dynamic action…
  • Walk Thru – New Dynamic Action cont’d
  • Scenario 3 From IT0002-Personal Data Create IT0021-Family Member
  • Scenario 3 – Personal Data Create IT0021 Family Related Persons
    • Hire (Z1) action
    • Dynamic Action will Create Infotype 0021 (Family/Related Person) Subtype 2 (Child) for every dependent
    • Evaluate # of dependents (ANZKD) when Infotype 0002 (Personal Data) is created
  • Create IT0021 Family Related Persons If # Deps = 1, Insert IT0021
  • Create IT0021 Family Related Persons
  • End Result
  • Scenario 3 – Personal Data The Challenge – Adding Dependents
    • Dynamic action for entries into # of dependents works great on the initial Hire action ….
    • BUT……How can create the correct number of Infotype 0021 (Family/Related Person) anytime Infotype 0002 is changed or created and # of dependents (ANZKD) is increased.
  • Answering the Challenge
      • 1. Check previous # is less than new # of Dependents
    2. Call Procedure to get previously saved # of Dependents and calculate the difference. Set RP50D-FIELD1 3. Check value of RP50D-Field1. Insert correct number of IT0021, Sty 2 records.
  • Determining previous entry
  • Walk Through – New dynamic action
  • Procedure for new dynamic action PCL4 cluster stores the changes made to infotype documents.
  • Procedure for new dynamic action
  • Family/Related Persons Infotype dynamically appears first time. Enter first dependent information Save
  • Family/Related Persons Infotype dynamically appears second time. Enter second dependent information Save
  • Or you could………..
  • Much Simpler code……
  • Return on Investment
    • Data Integrity
      • Controls placed in system to ensure accuracy
        • (i.e., of tax authority)
    • Efficiency
      • Time saved in entering infotypes repeatedly
    • Enables downstream processes
      • Compensation Planning process more efficient with Date in Grade
  • Key Learnings
    • Nothing is foolproof - 80/20 Rule
    • Dynamically some business processes can be enabled
    • Dynamically some data entry can be automated
    • Basic Dynamic Actions can provide value added benefits
      • Automating business processes – saves time by performing routine tasks
      • Insuring data integrity
      • Empowering Global Power Users to successfully manage data
    • Dynamic Actions enhanced with some simple ABAP code make the impossible possible
  • Thank you for participating! Please remember to complete and return your session evaluation form following this session. Donna Wendling Sherry Meyer Session Code 301