Kontakt

Ansicht
Dokumentation

OHADBECB0 - Maintain Data Positioning

OHADBECB0 - Maintain Data Positioning

rdisp/max_wprun_time - Maximum work process run time   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

In this step, you set up data that is to be printed in fixed positions on the statement. Such data is usually about specific persons, or is organizational data. For example:

  • Name of employee
  • Personnel number of employee
  • Address of employee
  • SI and tax features of employee
  • Absences of employee
  • Monthly and annual value of paid remuneration
  • Fictitious remuneration
  • Name of administrator
  • Date on which statement was created

An entry is required for each piece of data to be printed in a fixed position.

The following fields must be maintained in Customizing:

  • Page type
  • Line number in form
  • Offset
  • Output length
  • Wage type
  • Field name
  • Conversion
  • Rule for form editing
  • Field offset

Description of fields

Page type

The page type is set to "EP" for statements. Since all data is printed at an exact position, there is no need to distinguish between the first page "FP", every page "EP", and last page "LP". This type of coding is used for remuneration statements, for example.

Line number

The line number specifies the line within the statement on which the item of information is printed.

Offset

This field enables you to specify the column as of which data is printed.

Output length

This determines the length of the entry.

Wage type

The name of a statement wage type is specified in this field, if necessary.

Example

If the amount of statement wage type NET2 (fictitious net) must be printed from table BRT, please enter the following:

WType: NET2
Field name: BRT-BETRG

Field name

The item of information to be printed in a fixed position is stored in the field "Field name". The entry is a table field. Table fields are specified in the field "Field name" by entering the table that contains the field, then a hyphen, and then the name of the field itself.

Example

You want to print an employee's date of birth. It is stored in field "GBDAT" in table "NAME". In this instance, the entry you must make in the field "Field name" is as follows:

NAME-GBDAT

The tables that can be printed are listed under Allowed tables. Tables marked with a cross in the column for table T512Q (maintain data positioning) may be used.

The field names pertaining to the tables are listed under Allowed field names.

Conversion

In the case of field names, it is possible to specify a conversion for printing out the information.

The following conversion indicators are currently supported by the standard system.

  • 01 Key is replaced with text
  • 10 Suppression of zeros
  • 13 Six-character date (DD.MM.YY)
  • 14 Amount followed by 'DM'
  • 15 Workdays followed by 'Wrk.Dy.'.
  • 16 Working hours followed by 'Wrk.Hrs'
  • 17 Date followed by ' -'
  • 18 Four-character date (MM.YY)
  • 19 Value w/ 3 characters before and 2 after the decimal point
  • 20 Date editing DD.MM.YYYY
  • 21 Integer
  • 22 Date editing YYYY
  • 99 Default values can be overwritten

You can also call up the allowed conversions by using Allowed conversions. Those that are allowed are marked with a cross in the column for table T512Q (maintaining data positioning).

Rule for form editing

If the information must only be printed on a statement if certain conditions are met, this field enables you to enter the identifier for a rule that you must have determined during the step Maintaining output rules. The rule determines whether information is printed.

Field offset

This field is not used for statements.

Particular features for statements

  1. Manual entry options
  2. Printing a supplement
  3. User exits
  4. Other payments: tax-exempt and taxable
  5. Leave data:

1. Manual entry options

There are two ways of determining that manual entries can be made in certain parts of the statement

  • Manual fields

If you want the statement to include fields whose content is not determined by the system, enter 'MAN-' in the field 'Field name'. This creates a field which must be maintained manually.

If a fixed text has been defined for this area in the step "Maintaining the form background", it can be overwritten. This entry enables you to determine that text which has already been entered can still be overwritten.

Fields that can be overwritten

If the information in the system is not necessarily correct so that you want to keep the option to overwrite it when printing, enter conversion '99' in the field 'Conversion'. The value stored in the system is then printed but can still be corrected manually.

2. Printing a supplement

If there is not enough room on the statement for all data records for a table, for example, Other Payments, the spare data records are printed in a supplement.

A note is printed on the statement indicating that a supplement exists for this statement. The SPEZ-ANHNG is used, together with a rule, to print this note. You cannot change the printing of the supplement itself.

The supplement data is printed on a separate page. In addition to the header data (including the statement name, personnel number), any data records that cannot be printed on the actual statement due to the restricted number of lines are also printed in the supplement.

For reasons of clarity, only the following tables can be printed in the supplement:
SOL, SOLC, STF, STFC, SOB, LSOB (other payments)
AP (work center data), and FEHL (unpaid absence records).

3. User exit

Two includes are available to enable you to carry out your own modifications.
RPBIDK00: Customer-specific data declarations
RPBIKU00: Customer-specific processing
Include RPBIKU00 contains the routine CUSTOM_MOD. This routine is called immediately before the fields are printed on the statement by conversion 98, which can be entered for a field in the step "Setting up data in fixed positions". The "C_FNAME" field is available as a parameter and contains the field to be printed on the statement.

Example

You want to create statement 20 ("Sickness Pay for Children"), however the content of the AP-WNAME should be changed before the statement is printed in the routine CUSTOM_MOD.
Make the following entry in the above-mentioned step:
Forml SType No Offset Length WType Field Conv
BE25 EP 01 003 25 AP-WNAME 98

4. Other payments: Tax-exempt and taxable

Taxable and tax-exempt payments must be printed on several statements, for example, on a housing subsidy statement. Since a payment may not be just tax-exempt or taxable and may contain a taxable and tax-exempt part, this data must be calculated in a special way.

Special output tables are used to print the tax-exempt and taxable payments on the statement

  • SOL Taxable other payments, specific dates
  • STF Tax-exempt other payments, specific dates
  • SOLC Taxable other payments, cumulated acc. to wage type
  • STFC Tax-exempt other payments, cumulated acc. to wage type
  • SOB Taxable other payments, cumulated acc. to wage type
  • - current year
  • LSOB Taxable other payments, cumulated acc. to wage type
  • - previous year (in statement period)

Data is entered into these tables in accordance with coding for statement wage types SOLE and SBSF.

Data is entered into tables SOL and STF first. The other four tables are then created from these tables.
SOL --> SOLC, SOB and LSOB
STF --> STFC

Statement wage types

SOLE:

  1. Wage types coded in SOLE are placed directly in table SOL. You can use cumulation wage types as well as payroll wage types. (To do this the wage type text for the cumulation wage type must be set up in the step Maintaining Output Wage Types).

SBSF

  1. Wage types set up in the step Tax -> Processing -> Allocate Wage Types into Tax-Exempt/Tax-Liable Shares are broken down accordingly.
    The tax-exempt part is placed in table STF and the taxable part is
    placed in SOL.
    Caution: Only breakdown types 1 and 2 are supported. A wage type coded
    with breakdown type 3 is NOT processed further. To include these
    wage types, you must store the tax-exempt and taxable amount of the
    wage type in additional wage types and code these in SOLE and SBSF
    accordingly.
  2. Wage types are completely tax-exempt
    These are stored directly in STF.
  3. It is also possible to code a cumulation wage type in SBSF.

Differences with the old solution (FYC97/98)

  1. The new output tables SOLC and STFC contain the wage types for other payments used to cumulate the statement period according to wage types.
  2. On the reporting side, wage types are no longer placed in table STF, neither wage types coded in the wage type table in cumulation 07, nor the wage types /126, 127, /256, /257, /465, /688, and /692.
    All wage types (and the resulting tables) to be printed using SOL and STF must be coded accordingly in SOLE or SBSF.
  3. You can code as many wage types as required in SBSF. Previously, the only wage types processed were those set up in the step Tax -> Processing -> Allocate Wage Types into Tax-Exempt/Tax Liable Shares.
  4. Cumulation wage types can also be coded in SBSF and SOLE.

5. Leave data

The leave data is printed from internal table UR1. This table is filled with data indirectly from the Leave infotype.

Leave is stored in different leave types, for example, Standard annual leave, Challenged employee leave, Relocation leave. Which leave types are relevant for the leave printout ?

You can define the selection of relevant leave types using a rule. The field UR1-UJAHR is used as a key word. You can query the following entries:

  • XXXX: Sum of all leave types
  • XXnn where nn = leave type: Sum of leave type nn
  • mmmm where mmmm = leave year: Total in leave year mmmm

1.) The leave entitlement is to be printed (field: UTAGE). All leave types are relevant.

Step: Maintaining data positioning

Field name Rule
-------------------------
UR1-UTAGE 07

Step: Maintaining output rules

Rule No Field V V0 Value1 Value2 Off Length DrValue Conv R
------------------------------------------------------------------------
07 01 UR1-UJAHR C EQ 'XXXX '1 UR1-UJAHR

2.) This time, only leave type 01 (Standard annual leave) is relevant.

Step: Maintaining data positioning

Field name Rule
--------------------------
UR1-UTAGE 07

Step: Maintaining output rules

Rule No Field V V0 Value1 Value2 Off Length DrValue Conv R
----------------------------------------------------------------------
07 01 UR1-UJAHR C EQ 'XX01 '1 UR1-UTAGE

The statement period is decisive.

Exception: Statement of Employment § 312 SGB III (indentified by statement type A, modify in control parameter):

In this statement, the current and last year are decisive. Leave compensation must be printed. This means the date to which the employee would have worked if the remaining leave had not been paid.

Allowed tables

Master data

  • ADR Data from infotype P0006 (permanent residence)
  • ADR2 Data from infotype P0006 (temporary residence)
  • AP Data from infotype P0001 (work center data)
  • APK Data from infotype P0000 re the date of termination
  • AZ Data from infotype P0007 (working time)
  • BBX Data from infotype P0008 (basic pay)
  • BBXM Composite table for maternity protection
  • KG Data from infotype P0232 (child allowance)
  • NAME Personal data from infotype P0002
  • ST Data from infotype P0012 (fiscal data)
  • SV Data from infotype P0013 (social insurance)
  • UR1 Data from infotype P0005 (leave)
    Field UJAHR (leave year) serves as a key word:
    XXXX: total of all leave types in the last 2 years
    XXnn where nn = leave type; total for leave type
    mmmm where mmmm = leave year; total in leave year

Information from other infotypes can be printed by specifying

S NN Field
! ! !
Select Infotype Field name

Example: S29-BRFGN means the field 'mutual indemnity society key' from infotype P0029 (mutual indemnity society). The standard system then offers the following infotypes as a default:

  • S00 Data from infotype P0000 (Period of employment)
  • S02 Data from infotype P0016 (Company control)
  • S03 Data from infotype P2001 (Maternity protection only)
  • S073 Data from infotype P0001 (Training work centers only)
  • S09 Data from infotype P0009 (Bank details)
  • S10 Data from infotype P0010 (Capital formation)
  • S14 Data from infotype P0014 (Recurring payments/deductions)
  • S15 Data from infotype P0015 (Additional payments)
  • S16 Data from infotype P0016 (Contract elements)
  • S19 Data from infotype P0019 (Monitoring of dates)
  • S26 Data from infotype P0026 (Company insurance)
  • S29 Data from infotype P0029 (Mutual indemnity society)
  • S41 Data from infotype P0041 (Date specifications)
  • S49 Data from infotype P0049 (Reduced hours/bad weather)
  • S79 Data from infotype P0079 (SI additional insurance)
  • S80 Data from infotype P0080 (Maternity protection)
  • S111 Data from infotype P0111 (Garnishments)

Time data

  • Z01 Data from infotype 2001 (absences)
  • FEHL Unpaid absences

Payroll results

  • BRT Results table for statements (statement RT)
  • LRT Results table for last period (LAST RT)
  • BCRT Total of all results (cumulated RT)
  • LCRT Total of all results from last year (cum. RT)
  • SCRT Cumulated ST for tax
  • STF Tax-free payments
  • SOL Taxable payments - specific dates
  • SOLC Taxable payments - cumulated acc. to wage types
  • SOB Taxable payments - current year
  • LSOB Taxable payments - last year






RFUMSV00 - Advance Return for Tax on Sales/Purchases   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 20049 Date: 20240524 Time: 012842     sap01-206 ( 183 ms )