SAP ABAP IMG Activity SIMG_OHAMX_467 (Define special processing rules)
Hierarchy
☛ SAP_HRCMX (Software Component) Sub component SAP_HRCMX of SAP_HR
   ⤷ PY-MX (Application Component) Mexico
     ⤷ P32C (Package) Customizing HR Mexico
IMG Activity
ID SIMG_OHAMX_467 Define special processing rules  
Transaction Code S_AHR_61001170   IMG-Activity: SIMG_OHAMX_467 
Created on 19981221    
Customizing Attributes SIMG_OHAMX_467   Define special processing rules 
Customizing Activity SIMG_OHAMX_467   Define special processing rules 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_OHAMX_467    

This IMG activity enables you to set up special processing rules.

You only need to carry out this IMG activity if specific information must be printed on a remuneration statement that depends on specific conditions.

Conditions for printing information can be stored in the system as rules. A rule can determine, for example, that information is only printed or selected if the value of the information exceeds a specified value. A rule can also determine that under a specific condition, one piece of information is replaced on the payroll account by another piece of information.

Rules can be defined for all variable information, that is, for information which can be different from employee to employee. Variable information is set up in the following IMG activities:

  • "Set up data in fixed positions"
  • "Set up line layout in window"
  • "Set up wage types in window"

A rule is assigned to a specific piece of information by the rule number. This is stored in the field Rule for form editing in each of the IMG activities named above.

SETTING UP AND PROCESSING A RULE

A rule can include one or more lines. Every rule line consists of the following components:

  • ID component

    This component contains the rule identification. It includes the following fields:

    • Rule
    • Number

  • IF component

    This component contains the logical rule condition. It includes the following fields:

    • Field name
    • Offset for comparison
    • Length for comparison
    • Comparison type
    • Comparison operator
    • First comparison value
    • Second comparison value

  • THEN component

    This component contains the replacement values for a piece of information. The replacement values are taken into account if the condition in the IF component is fulfilled. The THEN component includes the following fields:

    • Offset
    • Output length
    • New value if condition is fulfilled
    • Conversion

  • Subsequent component

    This component controls the processing of further rule lines. The component includes the following field:

    • Subsequent rule indicator

The IF and THEN components form the basis of a rule. They specify how a variable piece of information is printed, and under which conditions.

When a payroll account is created, the system carries out a comparison within the IF component for every piece of variable information to be printed to which a rule has been assigned. This can give rise to the following:

  • The condition stored in the IF component has been fulfilled. In this case, the THEN component is processed first (that is, the replacement values stored there are used. The subsequent component is then interpreted.

  • The condition stored in the IF component has not been fulfilled. In this case, the subsequent component is interpreted directly.

The subsequent component determines whether subsequent rule lines are processed (that is, if subsequent rule lines exist).

If more than one rule line is processed for a rule, the replacement values stored in the same rule line are used for every fulfilled condition. To prevent replacement values from overlapping if more than one condition is fulfilled, the replacement values stored in the individual rule lines must be chosen accordingly.

If the specified condition has not been fulfilled in any rule line, the information to which the rule is assigned is not printed on the payroll account.

The individual components and their fields are explained in more detail below.

ID COMPONENT

A rule is identified using the fields Rule and Number.

Rule

The field Rule contains a two-digit number (01-99) for every rule. Using this number, the rule can be assigned to one or more variable pieces of information which you set up in previous IMG activities.

Number

The field Number is used to number the rule lines. Rule line numbering starts with "01" and is sequential. This means that number "01" must always be assigned to the first rule line, number "02" to the second rule line, and so on.

The rule identification could, for example, be as follows:

    Rule        Number

    01        01

    01        02

In this example, the rule and number fields define rule "01" which consists of two lines.

IF Component (logical condition)

The logical condition of a rule determines the IF conditions under which replacement values stored in the THEN component are used instead of the information that would normally be printed. The logical condition could, for example, look as follows:

"If information xy equals z, ... "

The logical condition of a rule is stored in the following fields:

  • Field name
  • Offset for comparison
  • Length for comparison
  • Comparison type
  • Comparison operator
  • First comparison value
  • Second comparison value

The above condition can be assigned to these fields as follows:

Information xy        -> stored in the field Field name

"equal to"         -> stored in the field Comparison operator

"z"         -> stored in the field First comparison value

Field name

The field name of the information to which the condition refers is stored in the field Field name. The following relationships may exist between the field name and the variable information to which the rule is assigned:

  • The specified field name is identical to the field name of the information to which the rule is assigned. Using "employee's personnel number" as an example, this means that a rule is assigned to the variable information "employee's personnel number" which starts as follows: "If the employee's personnel number..."

  • The specified field name is not identical to the field name of the information to which the rule is assigned. Using "employee's personnel number" as an example, this means that a rule is assigned to the variable information "employee's personnel number" which starts, for example, as follows: "If the employee's religious denomination..."

Field names are specified in the field Field name firstly by the table which contains the field followed by a hyphen followed by the field name itself. In the overview "allowed field names", you will find all of the field restrictions listed below.

Example:

You want to specify the field "PERNR" from table "PERNR" in the field Field name. To do this, enter the following:

PERNR-PERNR

For further information on entering field names, refer to the IMG activities "Set up data in fixed positions" and "Set up line layout in window".

Field name restrictions

The field Field name is subject to certain restrictions regarding what can and cannot be entered. Constants and text modules CANNOT be entered in the field Field name. Only the fields of certain tables are allowed.

The following principle applies to whether or not a field is allowed:

The field specified in the field Field name must come from the same table such as the field which contains the variable information to which the rule is assigned.

Example:

You want to assign a rule to the variable information "employee's personnel number" which is stored in the field "PERNR" in table "PERNR". In this example, you can only specify fields in the field Field name which are stored in table "PERNR".

The following exceptions apply to the above principle:

  • If a rule is assigned to variable information stored in table "SCHLW", the field specified in the Field name field must be identical to the field from which the variable information originates.

    Example:

    You want to assign a rule to the variable information "Hiring date of employee" which is stored in the field "PHIRE" in table "SCHLW". In this example, only PHIRE can be specified in the field Field name.

  • The fields form the following tables can be specified as field names in every rule in the field Field name:

        PN

        PERM (table applies to Germany only)

        SY

        VERSC

Offset and length for comparison

You need to make an entry in this field if only certain parts of the information specified in the field Field name must be used in the logical condition. It is conceivable, for

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency I   Valid for countries specified 
Customizing Attributes Country Key Country Name
SIMG_OHAMX_467 MX Mexico
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_OHAMX_467 0 AHR0000149 Payroll Account 
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_T512N V - View OH00 5 Define special processing rules 
V_T514K V - View OH14 CKTO H Admitted tables 
V_T514N V - View OH14 CKTO B Permitted field names 
V_T514C V - View OH14 CKTO 8 Admitted conversions 
History
Last changed by/on SAP  19981221 
SAP Release Created in 470