FLSA Status Defaulting

I recently came across an SCN chat on a function I previous did not know. On the JOB, I knew there is an infotype 1610 - US Job Attribute that stored EEO and FLSA. It is a US specific infotype and maintain via table T5u13.  -->

What I did not know is by having that value on infotype 1610, it can help drive the defaulting of FLSA status on a person infotype 0001. 

You can read more about it on SCN - https://scn.sap.com/thread/1883092

Essentially all of this is done through a simple function module MP00014U. 

Note: This is only applicable if you use infotype 1610 on the JOB and not position. Also, note that this infotype is US specific. I've seen people override the configuration and use this for other countries. 

*---------------------------------------------------------------------*
*   Subroutines for Infotype 0001. (NA Dynpros 2007, 2010)            *
*---------------------------------------------------------------------*
*   MODULE GET_EXEMPT reads table 5K13 or 5U13 and get the exempt/non-*
*   exempt indicator.                                                 *
*---------------------------------------------------------------------*
FORM GET_EXMPT USING TAB_PAR.
  DATA TEMP_DATE LIKE SY-DATUM.                         "XIYAHRK029358
  TEMP_DATE = SY-DATUM.                                     "
  IF P0001-ENDDA LT SY-DATUM.                               "
    TEMP_DATE = P0001-ENDDA.                                "
  ELSEIF P0001-BEGDA GT SY-DATUM.                           "
    TEMP_DATE = P0001-BEGDA.                                "
  ENDIF.                                                 "XIYAHRK029358
  CASE TAB_PAR.
    WHEN 'T5U13'.
      SELECT * FROM T5U13 WHERE STELL = P0001-STELL
*     AND   endda GE sy-datum ORDER BY PRIMARY KEY.      "XIYAHRK029358
        AND   ENDDA GE TEMP_DATE ORDER BY PRIMARY KEY.   "XIYAHRK029358
      ENDSELECT.
      IF SY-SUBRC EQ 0.
        Q0001-EXMPT = T5U13-EXMPT.
      ELSE.
*     MESSAGE W009(5U) WITH 'T5U13' P0001-STELL.      "VQLK11K025919
      ENDIF.
    WHEN 'T5K13'.
      SELECT * FROM T5K13 WHERE STELL = P0001-STELL
*          AND   ENDDA GE SY-DATUM ORDER BY PRIMARY KEY. "XIYAHRK029358
          AND   ENDDA GE TEMP_DATE ORDER BY PRIMARY KEY. "XIYAHRK029358
      ENDSELECT.
      IF SY-SUBRC EQ 0.
        Q0001-EXMPT = T5K13-EXMPT.
      ELSE.
*     MESSAGE W009(5K) WITH 'T5K13' P0001-STELL.      "VQLK11K025919
      ENDIF.
    WHEN OTHERS.
                                       "Do Nothing.
  ENDCASE.
ENDFORM.

Infotype 0008 Wage Types Default

When you create a new infotype 0008 record, one or more wage type automatically default into the wage type field. How does this occur and how do you controll it? There are many ways to accomplish this. One way is through user exit custom code, but the standard way is via configuration in the Payroll Data configuration node.


In the SAP IMG configuration node "SPRO -> Personnel Management -> Personnel Administration -> Payroll Data -> Basic Pay -> Wage Types" section you have a series of configuration item to setup Wage Types. On how to setup a Wage Type and their attribute, I'll defer that to another Wiki page at a later date. This page is specifically meant to illustrate how to get the wage type once it is setup to default on infotype 0008 when a new record is created.
Assumption:

• Wage Type attribute and characteristics are properly setup.
• Wage Type permissibilities are properly setup

In the node, there is a section called "Enterprise Structure for Wage Type Model" which calls a feature tree (technical name: LGMST). This is a decision tree that return a specific value or set of values. Usually by SAP standard, it utilize key information found on a user infotype 0001 as a decision factor. In this case, we use MOLGA (Country Grouping) and PERSG (Employee Group)


Based upon the tree condition, it will return a set of values to SAP. In the example above it is either "10/HOURLY" or "10/SALARY". The 10 represent the maximum number of wage types it should default into or return back once it find the matches for the value SALARY or HOURLY. The value SALARY or HOURLY are found in the IMG node called "Revised Default Wage Types" also know as table V_T539A.


With the logic above, it will be able to know to default accordingly. So using example record as seen below. The default of the value 1010 - Regulard Salary. You will also notice value 1099 FTE Equivalent also is on this record. This was default using the User Exit Custom Code method for a different purpose.

Management Global Employee (MGE) - Reuse PERNR

In the past few years, SAP had spent many effort refining the Concurrent Employment / Management Global Employees of their. From modification on the portal side to ECC side, a solution are slowly rolling out for a lot major modules to support multiple PERNRs.

Going back to the basic, in the realms of Personnel Management, we know there is the possibility of using multiple PERNRs. With the MGE functionality activated, when a person goes on international assignment, he/she receives a new PERNR associated with that assignment. Each time an assignment occurs, a new PERNR is given for that assignment. To add to the mix, if the person become country re-assignment (permanent transfer) to a country, they also receive a new PERNR.

Over time, the amount of PERNRs being introduced for a person who goes on assignment a lot get a little out of hand. Recently SAP delivered to major OSS note to address this problem. You need to apply OSS 1363600 and configured your system according to OSS 1397959.

With these two OSS notes applied, you will now be able to "re-use" PERNR. The concept of having multiple pernrs is now limited to only one PERNR per country. You will still have multiple PERNR due to crossing MOLGA, but if the person return to the same country for another assignment, you can re-activate that withdrawn status PERNR.

Explore these two OSS notes and see if help improve your business process and share your thought in the process.

ENTERPRISE COMPENSATION MANAGEMENT WITH mySAP™ ERP

ENTERPRISE COMPENSATION MANAGEMENT WITH mySAP™ ERP

View more documents from smilepak.