SAP ABAP IMG Activity SIMG_OHAK514 (Rules)
Hierarchy
☛ SAP_HRCCA (Software Component) Sub component SAP_HRCCA of SAP_HR
   ⤷ PY-CA (Application Component) Canada
     ⤷ P07C (Package) HR customizing: Canada
IMG Activity
ID SIMG_OHAK514 Rules  
Transaction Code S_AHR_61009646   IMG Activity SIMG_OHAK514 
Created on 19981221    
Customizing Attributes SIMG_OHAK514   Rules 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_OHAK514    

This step enables you to set up rules.

For further information, refer to the section "Set up special processing rules", or to the documentation on the form editor in the SAP Library.

You only need to carry out this step 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 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 steps:

  • "Individual fields"
  • "Line layout"
  • "Identifiers 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 steps 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:

    • Table
    • Field
    • Offset for comparison
    • Comparison length
    • 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:

    • Table
    • Field
    • Position (column in form)
    • Output length
    • Conversion

For each piece of variable information to which a rule is assigned, the values in these fields replace the original values specified in the steps "Individual fields", "Line layout", and "Window".

If there are no entries in certain THEN component fields, the original value is taken into account for each of these fields.

  • 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.

The individual components and their fields are explained in 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 work steps.

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:

  • Table
  • Field
  • Offset for comparison
  • Comparison length
  • 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 Table and Field

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

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

Table and Field

The table and field name of the information to which the condition refers is stored in the fields Table and Field. 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..."

    Example:

    You want the rule condition to refer to the information in the field "PERNR" of table "PERNR". To do this, you enter the following:

    Rule    No    C    Table    Field

    01    01        PERNR    PERNR

For detailed information on field names, refer to the sections "Set up data in fixed positions" and "Set up line layout in window".

Field name restrictions

Only the fields of certain tables are allowed. The following principle applies to whether or not a field is allowed:

  • The table name specified in the field Table must be the same as the table of the individual field 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".

  • If a rule is assigned to variable information stored in table "SCHLW", the field specified in the rule 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 the field "PHIRE" can be specified in the table "SCHLW".

  • The fields from the following tables can be specified in the IF component of every rule:

        PN

        PERM (table applies to Germany only)

        SY

        VERSC

First comparison value

This enables you to enter the value against which the information stored in Table and Field is compared.

The entry in this field can be a constant value, a constant or a table field.

  • Constant value

    If you specify a constant value, it must be preceded by an apostrophe which identifies the value as a constant value.

    Example:

    You want to enter "0" as a constant value in the field First comparison value. To do this, enter the following:

    Value 1

    '0

    Decimals as constant values

    If numbers are specified after a decimal point as part of a constant value in the field First comparison value, the decimal point that is chosen depends on the comparison type:

Comparison type    Decimal point

"N"     "." (for example "0.50")

"C"     depending on the user values in the

    program starter, for example:

    in Germany: ","(comma)

    in the USA:"."(period)

If numbers are specified as a constant value which include a decimal point, it is recommended that you use comparison type "N".

  • Constant

    The fields "HDATE" and "LDATE" in table "SCHLW" are both constants. Fields from table "SCHLW" can be specified simply by entering the field name

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_OHAK514 CA Canada
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_OHAK514 0 HLA0003920 Remuneration Statement 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  19981221 
SAP Release Created in