Viewing entries tagged
SAP HCM Tip

SAP HCM Tip: Managing Schema Changes

2 Comments

SAP HCM Tip: Managing Schema Changes

Introduction

If you have been using time evaluation very long, you may have seen an error like this. When this happens, it tends to cause some panic because it stops time evaluation, and subsequently payroll for all employees.

This occurs when multiple changes are being made to the schema but not moved to the production system at the same time, or in the same order.  Read more.

 

2 Comments

SAP HCM Tip: Standard Organization Management Switch for Transferring Text to Personnel Administration

Comment

SAP HCM Tip: Standard Organization Management Switch for Transferring Text to Personnel Administration

Every now and then we come across a scenario where a customer is having to manually align the Personnel Administration Infotype 0001 dates with the dates of name changes on the Organization Management side of the system.  These scenarios typically play out as follows:  the compensation management team updates Job titles to follow a new naming convention.  This occurs as of a particular date, let’s say 5/1/2016 for example.  In order for the corresponding employees’ records to display correctly in the system, the best practice is to create a corresponding Infotype 0001 (Organizational Assignment) record for each of them on the date of the new job name.  This practice can be time-intensive if performed manually.  Users would have to first query all employees who are assigned to the particular jobs as of the date of change and then would have to manually create a new Infotype 0001 with the corresponding date. Read more.

Comment

SAP HCM Tip: Validity of HR Objects

Comment

SAP HCM Tip: Validity of HR Objects

The Enterprise and Personnel Structures of an SAP HCM System are the foundational structures upon which so much of the system’s functionality can be configured.  It has been the case that once the structures are configured, they’re there forever.  This has resulted in a great deal of caution when setting up these foundational structures because of their downstream use and because of their permanence in the system.  Read more.

Comment

SAP HCM Tip: HCM Processes and Forms - Developing Custom Emails for the Workflow

Comment

SAP HCM Tip: HCM Processes and Forms - Developing Custom Emails for the Workflow

Although SAP delivers many workflows with the HCM P&F processes, it is often imperative to not only develop the custom Workflow (WF), but also add custom emails. SAP provides a relatively easy method to develop the custom “simple” emails. More complex emails can be developed and added to the WF. These more ‘complex’ emails might include, as an example, a list of items (i.e. Employee Names), which is normally not possible using the SAP provided ‘simple’ method. 

This article will demonstrate how to develop not only a ‘simple’ email, but also the requirements to develop a more complex email. Read more.

Comment

SAP HCM Tip: Submitting HCM P&F Process(es) in Batch: Why Might One be Needed to Write the Program

Comment

SAP HCM Tip: Submitting HCM P&F Process(es) in Batch: Why Might One be Needed to Write the Program

Introduction
HCM Processes and Forms (HCM P&F) is a component from SAP used to execute HR processes in which changes are to be made to HR master data. It uses Interactive Forms by Adobe to integrate all involved roles directly in the process. 

This article is not going to discuss the design and build of an HCM P&F application. This will explain how to leverage an existing implementation to satisfy a new business requirement.  Read more.

Comment

SAP HCM Tip: Dynamic Actions for Infotype 41

Comment

SAP HCM Tip: Dynamic Actions for Infotype 41

Creating dynamic actions to update infotype 41 is a challenge due to the fact that any given date type can exist in any one of the twelve available positions on the infotype. For example, one personnel number might have date type ‘XY’ in position two while another personnel number has the same date type in position four. There is also the possibility of one personnel number already having the desired date type while another is missing it. Because of this very real possibility of variation, a dynamic action to update infotype 41 cannot be configured using commands regarding explicit positions for the date types.

So now the question becomes how can a dynamic action be written to update infotype 41. The solution requires using ABAP form routines to determine the existing positions of the date types already stored on the current infotype 41 records and additional routines to either update an existing value or create a new date type entirely.  The below dynamic action (Fig 1) is configured to update infotype 41 with the help of the custom ABAP form routines. Read more.

Comment