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.
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.
The newest flavor of Employee Self-Service (ESS) built using Web Dynpro ABAP (WDA) delivered in EHP5+ allows for streamlined configuration of UI elements compared to previous enhancement packages. Now your PA20/30/40 and ESS screens share more configuration tables, which makes many types of screen changes less painful.
1) Open view V_T591C in TCODE SM30. Scroll down to Infotype 0105, subtype 0020. With the “Long_ID” unchecked, we will proceed to show the screens in PA30 and ESS.
Recently I got to work on an interesting client requirement and realized this was becoming common practice. The requirement is to pay Holiday Pay only if the employee works both the day before and the day after a holiday. This can be a complicated matter and often implementers will resort to custom code to resolve this requirement.
Holiday pay is to be generated automatically via time evaluation for your employees on company holidays. Your company also has a holiday policy that states that employees will not get holiday pay hours in case of unexcused absence time before or after a company holiday. Read more.
Have you ever wanted to add a custom program to a process model? We will show you how in a few easy steps!
In the process model below, we have added a custom program to email the employee population a notification informing them payroll is complete and that they are now able to view their check stub. Keep reading for all the steps we took to accomplish this task. Read more.
HR Focal Point's Presentations From HR 2015
HR Focal Point had two of our resources make presentations at the HR 2015 conference. We invite you to click on the links below to review the slides from their presentations. They are a great way to stay current on the educational information that was shared at HR 2015. Read more.