SAP ABAP IMG Activity OHTX0559 (Balance Limits)
Hierarchy
☛ SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR
   ⤷ PT (Application Component) Personnel Time Management
     ⤷ PTIC (Package) HR Time Data: Customizing
IMG Activity
ID OHTX0559 Balance Limits  
Transaction Code S_AHR_61009647   IMG Activity: OHTX0559 
Created on 19981221    
Customizing Attributes OHTX0559   Balance limits 
Customizing Activity OHTX0559   Balance Limits 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OHTX0559    

In this step, you set rules for checking the balances determined in time evaluation. The rules allow you to check the time balances to see if they exceed or fall short of individually defined value limits or specifications in working time regulations, and to determine appropriate system reactions. There is a flexible Customizing table that you can use to fulfil the following requirements.

Examples of use

  • Setting value limits based on fixed values or the employee's master data and transaction data (for example, number of planned hours, maximum working time)
  • Checking value limits within periods you can define yourself (for example, 50 days, 13 weeks, and so on)
  • Issuing messages, also as an advance warning, when the value is approaching the value limit (that is, the value limit has not yet been exceeded)
  • Transferring the surplus to another time balance or wage type
  • Limiting the validity of the rule according to the employee's age
  • Transferring time balances to another time type for periods you can define yourself, for example, week balances

Procedure for checking the time balances

You can set balance rules for checking day balances and period balances. Function LIMIT, which checks the time balances during time evaluation, can process the balances in the following ways:

  • Cumulation: Function LIMIT cumulates the day or period balances over a certain processing period and compares the cumulated value with the value limit.
    Example: Productive hours cumulated over a week.
  • Find maximum: Function LIMIT views the day or period balances, finds the maximum value within the processing period, and compares this value with the value limit. In this case there is no cumulation. If you want to use cumulated balances for the comparison, you have to formulate them in a personnel calculation rule.
    Example: You want to find out whether an employee had 60 hours off at once in one week.
  • Find minimum: Function LIMIT views the day or period balances, finds the lowest value within the processing period, and compares this value with the value limit.

Processing periods and check points

You can use different processing periods and check points depending on whether you are processing day or period balances. The check point is the time at which the system uses the rule, for example, at the end of the payroll period.

  1. Processing day balances

    The balances for the day being evaluated from table TES (individual day balances, day processing in time evaluation) are processed together with the balances from table ZES (individual day balances, cluster B2) As before when using personnel calculation rules, they are processed during day processing in time evaluation.
    Note the effect on system performance of using long cumulation periods and regular check points (for example, daily).

  2. Processing period balances
    Here, you specify rules that always refer to a time evaluation period.
    The processing period always amounts to one or more time evaluation periods. The check point must be at the end of a time evaluation period - or at the end of two time evaluation periods, or three, and so on.
    The balances from table SALDO are taken into account. They are processed during final processing in the schema.
    All checks related to time evaluation periods and period balances should also be made using period balances. Check all the data you have entered in the step Define time types again, and make changes if required.

Function LIMIT is accessed both in the day processing block and in the final processing block in the schema.

Processing Customizing entries

Please note that all changes to balances are made in time evaluation. The system runs through the rules in consecutive order according to the specified key. If you want to set several value limits for a balance, you should number the rules so that the ones with the highest value limits are referenced first (for example, a rule with the value limit 30 for flextime balance 0005 is assigned the number 020, a rule with the value limit 20 the number 021, and so on). You should avoid circular relationships (that is, posting in one rule from balance 0005 to balance 0006, and in another from balance 0006 to balance 0005).

Example

  1. You want the flextime balance to have a maximum of +/-10 hours at the end of the quarter, and a maximum of +/- 20 hours in other months. If the value limits are exceeded, you want the balance to be capped and the surplus moved to a wage type or time type.
  2. You want to check legal working time regulations or regulations stipulated by the collective agreement on a daily basis. These working time regulations may depend on the employee's age. If you detect working time violations of any kind, you want to output messages.
  3. You want to check for core time violations and report any you find.
  4. Once an employee has built up 20 compensation hours, you want to output a message to check the deduction of the employee's time in lieu (time off) credit.
  5. You want to make sure that your employees do not work more than 520 planned hours (incl. substitutions) and 585 productive hours (planned and overtime hours) within a 13-week period.
    For each balance, create a rule for checking the relevant value limits. Then select the Duration field under Day balance processed over, and enter 13 weeks as the period. Enter Weekly (end of period) as the check point so that the system always calculates back 13 x 7 days from the day of the evaluation and cumulates the relevant balances.
    Have the system issue messages if the value limits are reached or exceeded.

Requirements

You have already set up the time types for which you want to set value limits or use to calculate value limits in the step Define time types.

Standard settings

The standard system provides sample solutions.

Recommendation

Activities

  1. Decide which value limits you want to check, and how you want to check them.
  2. Choose Define limits for time balances.
  3. Specify the personnel subarea grouping for time recording, the time balance group, and the balance rule.
  4. Set the value limit:
    1. You can either set it as a fixed value, or using the parameters for operation 'HRS=yzzzzz', where 'y' is the origin indicator and 'zzzzz' is the parameter. Using this method, you can access employee-specific value limits from the infotypes (for example, Time Recording Information (0050)).
    2. Indicate whether the value limit represents an upper or lower limit.
  5. Specify which time balance should be used in the comparison:
    1. Specify the time type for which you want the balance to be checked.
    2. Specify the processing period. You can use either day balances or period balances as a basis.
      In day processing for time evaluation, you can process the current day's balance or the total or maximum or minimum of the day balances for a defined period (time evaluation period, payroll period, working week, or other period) can be used, including the values for previous periods if required. You can also determine a certain length of period up to the evaluation date for balance formation, for example, the last 2 weeks.
      In final processing, the time balance is taken from the (time evaluation) period balances; previous periods can also be included.
      Depending on your choice, you can only choose the check points (see below) from day or final processing.
  6. Specify which processing steps should be carried out if the balance exceeds or falls short of the value limit.
    1. Decide if you want a message to be issued and specify the type of message.
    2. Decide whether the time type on which the balance is based should be capped to observe the value limit.
    3. Decide if you want the surplus to be placed in a time balance or time wage type.
  7. If the value limit is reached but not exceeded, a message can be issued. Depending on the tolerance, a note can also be output when the value is approaching the value limit.
  8. If required, determine the time type in which you want the system to save the value it used to check the value limit.
  9. Decide when you want the value limit to be checked. Depending on whether you are processing a day balance or a period balance, the check point must be in day processing or end processing. Note that the system can only process the rules if function LIMIT is also inserted in the day processing or end processing areas of the schema.
  10. Determine the age restriction for employees to whom you want the value limit to apply. You can also leave the interval limits open.
    11. Business Attributes
    ASAP Roadmap ID 204   Establish Functions and Processes 
    Mandatory / Optional 2   Optional activity 
    Critical / Non-Critical 1   Critical 
    Country-Dependency A   Valid for all countries 
    Assigned Application Components
    Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
    SIMG OHTX0559 0 HLA0003735 Time Evaluation with Clock Times 
    Maintenance Objects
    Maintenance object type C   Customizing Object 
    Assigned objects
    Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
    V_T559P V - View SM30 Define Limits for Time Balances 
    V_T555E V - View SM30 03 Define Messages for Exceeded Value Limit 
    PCYC L - Logical transport object PE00 MODT 04 Modify Personnel Calculation Rule MODT 
    PSCC L - Logical transport object PE00 TM00 07 Modify Schema 
    History
    Last changed by/on SAP  19990616 
    SAP Release Created in