SAP ABAP IMG Activity SIMG_OHAF408 (Set Up Line Layout in Window)
Hierarchy
☛ SAP_HRCFR (Software Component) Sub component SAP_HRCFR of SAP_HR
   ⤷ PY-FR (Application Component) France
     ⤷ P06C (Package) HR Customizing: France
IMG Activity
ID SIMG_OHAF408 Set Up Line Layout in Window  
Transaction Code S_AHR_61008859   IMG Activity: SIMG_OHAF408 
Created on 19981221    
Customizing Attributes SIMG_OHAF408   Set Up Line Layout in Window 
Customizing Activity SIMG_OHAF408   Set Up Line Layout in Window 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_OHAF408    

This IMG activity explains how to set up the line layout in the window.

The layout of individual lines in a window can be identical. This means, for example, that a window could contain several lines in which the wage type text and then the wage type amount are displayed as of exactly the same columns. Print specifications such as column length and output length are not made for pieces of data individually, but layouts are defined to determine the structure of the lines within the window. The layouts are assigned to individual wage types using an identifier in the activity "Set up wage types in window".

By setting up line layouts, you can avoid making numerous redundant entries for different infotypes (e.g. wage type amounts, texts, and numbers), columns, the output length, and sometimes for conversions and field offsets as well. Such repetitions can be avoided because layouts can be used over and over, which means that you can assign them to all the wage types that are printed in accordance with one specific schema.

General procedure

A layout is always line-oriented, i.e. it determines the schema according to which a line is printed. One or more entries are required for a layout, depending on whether the layout in question allows only one piece of wage type data (for example, "XRT-BETRG" for the wage type amount, "XRT-BETPE" for the wage type rate, and "T512T-LGTXT" for the wage type text) or more than one to be printed per line. Each entry always refers to a specific piece of wage type data, i.e. the entry determines how the wage type data is printed on each line. This means that it is possible for a layout to consist of one single entry. However, it is more usual that it consists of more than one entry.

The following must be specified for each entry:

  • Line type
  • Column type
  • Offset
  • Output length
  • Field name

You can also specify the following for each entry:

  • Conversion
  • Field offset for printout
  • Rule for form editing

Those specifications which are not self- explanatory are explained below.

Line type and column type

The combination of line type and column type identifies a layout.

The line type is a two-character numeric value which can be chosen freely (01-99). All entries for one layout must ALWAYS have the same line type.

The column type consists of one character and can be made up as follows:

  • "X"

    You must use column type "X" if you want to print data on just one wage type in a line.

  • "1", "2", "3", "4", "5", "6", "7", "8", "9"

    You must ALWAYS use numeric values for superlines, i.e. if you want to print information for different wage types in a line.

    Definition:

    By "different" wage types we refer to the following cases:

a)    Two entirely different wage types are printed.

    Example:

    Wage type /101

    Wage type /106

b)    Information from different internal payroll tables are

    printed for the same wage type.

    Example:

    Wage type /101 from internal payroll table "RT"

    Wage type /101 from internal payroll table "CRT"

Please note the following with regard to superlines:

All data for the first wage type or for the wage type from the first table must be stored under column type "1"; all information for the second wage type or for the wage type from the second table must be stored under column type "2"; and so on.

  • "T"

    You must use column type "T" for control level start and end texts (see "Control level start and end texts" at the end of this activity).

Please note that every line type can be combined with column type "x", column type "T" and numeric column types ("1", "2" and so on). This means, for example, that you can enter the following line and column types for a particular form:

Line type    Column type

01    X

01    1

01    2

01    3

01    T

Examples

Example 1:

You want to print the monthly value of wage type /101 in a line.

To do this, you must enter a numeric value (such as "01") as the line type and the value "X" as the column type.

Example 2:

You want to print the monthly value of wage type /101 first and then the monthly value of wage type /106 in the same line. In this example, both entries must have the same numeric value (such as "01") as the line type. The column type must have the value "1" for the first wage type (/101) and the value "2" for the second wage type (/106).

Field name

The data is stored in the Field field. The entry in this field can be either a constant, a text module identifier or a table field.

  • Constant

    A constant is printed on a remuneration statement in exactly the same way as it is specified in the Field field. Each constant must be preceded by an apostrophe, which identifies it as a constant.

    Example:

    You want to enter "/" in the Field field as a constant (only example in standard form "DF01"). To do this, you must enter the following:

    '/

    NB Every piece of data that can be defined as a constant can also be defined as a text module. You MUST do this if the length of the piece of data exceeds 10 and/or it is required in several languages (see "Set up text modules").

  • Text module identifier

    You can specify a text module identifier which you have already set up in the IMG activity "Set up text modules" as a field name (eg. "TEXT01"). There must always be a hyphen between the character string "TEXT" and the corresponding text module number.

    Example:

    You want to specify a text module with the identifier "TEXT05" in the Field field. To do this, please enter the following:

    TEXT-05

  • Table field

    You can also specify a table field as a field name. You must ALWAYS specify a table field if the data being set up is variable.

    In the "Allowed tables" overview, all the tables flagged in the column "T512D" contain fields which can be specified in the Field field. The specific table fields which can actually be used are listed under the table names in the "Allowed field names" overview.

    Table fields are specified in the Field field by listing the table in which the field is stored, then a hyphen, and finally the field name itself.

    Example:

    You want to enter the total amount of a wage type. This is stored in field "BETRG" in table "XRT". To do this you must make the following entry in the Field field:

    XRT-BETRG

    Fields from table "SCHLW" are an exception. They must always be entered in the Field field without a hyphen and without the name of the table.

    Example:

    You want to enter the payroll period. This is stored in field "PERIODE" in table "SCHLW". To do this you must make the following entry in the Field field:

    PERIODE

    If you do not know which table contains the piece of information required, you can find out by noting the following:

    • Wage type data (including that on cumulation wage types), with the exception of the wage type text, always comes from internal payroll table "XRT".
    • The wage type text comes from table "T512T" unless it was stored as a text module.
    • Initial and final group texts always come from table "T512G" (see "Initial and final group texts" at the end of this IMG activity).
    • Additional data (such as bank code, cost center) may be read from different internal payroll tables (such as "WPBP", "XBT"). The link between a wage type and a table is formed by the split indicator in the payroll results. If a wage type has split indicator "WP" in the payroll results, for example, additional information is read from internal payroll table "WPBP". Please note that additional data from internal payroll tables can only be printed for wage types that have their corresponding split indicator.

      You can determine the required fields of the named tables by following t

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_OHAF408 FR France
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_OHAF408 0 HLA0009681 Remuneration Statement 
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_T512D V - View OH00 02 Set Up Line Layout in Window 
V_T514C V - View OH14 CEDT 0B Permitted Conversions 
V_T514K V - View OH14 CEDT 0B Permitted Tables 
V_T514N V - View OH14 CEDT 0B Permitted Field Names 
History
Last changed by/on SAP  19981221 
SAP Release Created in