SUMMARY:

• Currently provide ABAP problem resolution and system enhancements for large companies that use SAP, primarily Smithfield Foods. Support activities are typically in the areas of Human Capital Management (HCM) and often include design, configuration, development, and testing activities.
• Have worked with HCM2.
• In addition to configuration activities, have had the opportunity to learn and spend several years applying SAP’s ABAP programming language.
• Also spent several years learning and applying SAP automation tools like LSMW, SCAT, and SECATT and reporting tools like Infoset Query, Quick Viewer, and EPI - USE Query Manager.
• Over the years, technical skills have been complemented by experience in both technical and management roles on numerous large information technology projects.
• Throughout this time, have taken pride in discovering and using SAP’s capabilities in solutions that go Confidential what another implementation or support person might use.

SKILLS:

SAP: ABAP, Application Link Enabling (ALE), EDI, RFC, SAP Script, Smartforms, and Workflow

HCM: Organizational Management, Personnel Administration, Benefits Administration, Employee and Management Self Service, Compensation Management, and Events, Time Management, Payroll, and Authorizations

SD: Sales and Distribution

Reporting tools: Adobe forms, eCATT, and other SAP tools and SAP modules

EMPLOYMENT EXPERIENCE:

SAP Software Engineer

Confidential

SAP Software Engineer

Confidential

SAP Software Engineer

Confidential

Program Administrator

Confidential

Director, Technical Resources

Confidential

Responsibilities:

• Developed and conducted numerous classes on SAP’s query tools for both end users and developers. for developers included the various ways that authorizations, logical d Confidential bases, and ABAP program code can be added to enhance queries.
• Compiled a programming standards manaual for the Service Center and provided in those standards for other developers. Being able to “debug” production programs has been invaluable in troubleshooting customers’ problems. Being able to develop SAP enhancements and interfaces and then perform all of the functional testing has helped to keep costs to our customers low.
• Trained others how to use SAP’s CATT and eCATT (Extended Computer Aided Testing) tools. Employed them repeatedly on customer projects. For one customer’s acquisition project, created an action and a series of eCATTs that could take a single Excel spreadsheet of employee d Confidential and create all organization units, jobs, and positions as well as their relationships to each other. Another eCATT was then used to “hire” the employees into those new positions, populating all of the standard and “custom” employee infotype tables in the process. The customer has since used this process successfully for multiple acquisitions.
• Became proficient in the use of SAP Workflow and the various forms that it takes. For one customer, made ABAP program changes for the MSS-based PCR (Personnel Change Request) processes so that requests would automatically move to the appropriate approver based on organizational structure, position vacancies, and temporary approver substitutions, and would take into account managers who were out on a leave of absence.
• Going Confidential the activation of change logging for employees’ infotype tables, discovered how to activate similar logging of changes for organization management objects such as positions and jobs. Also extended this logging to “custom” infotypes, not provided by SAP.
• Going Confidential the addition of new fields to the employee infotype tables, learned how to add new fields to organization management objects and, for one customer, provided a way for them to maintain values that would show up in drop-down lists for those fields. Provided for different screen layouts to be used based on the record subtype being viewed. For another customer, added a checkbox to employees’ dependent records to indicate when they had court-ordered health insurance coverage. If anyone tried to change a health plan record in a way that would drop that coverage, the program logic in a user exit would issue an error message and prevent the change.
• SAP’s “dynamic actions” can be used to trigger simple functions such as the display of an infotype record or the triggering of an email notification. With the addition of ABAP code, complex conditions can be included for these actions. Went Confidential that with numerous enhancements to make life easier for the customer. In one instance, the termination of an employee would dynamically trigger the end-dating of the employee’s benefit plans and any recurring deductions, thus eliminating the need for an end user to perform those functions. Another would trigger the automatic creation of any employer-paid benefits, such as life insurance, for a new hire, thus eliminating similar activities previously done by an end user .
• Developers might typically be asked to provide a report program to identify employees with dependents who are about to reach the age where their health insurance coverage cannot continue. Went Confidential that and created a program that would identify those dependents, and then create new health plan records that no longer included those dependents and started on the birth date of the dependent. And, based on the remaining dependents, the program would also change the coverage option appropriately (to employee-plus-spouse or employee-only, for example).
• Developers typically use SAP-provided “user exits” to add ABAP program code to address a customer’s specific needs, but user exits are limited by what d Confidential is available for each. For one customer, encountered a problem with vacation accruals within time evaluation not handling leap years correctly. Solved the problem by having the code in one user exit save d Confidential into memory that a second user exit then retrieved and used as each employee was being processed.