Hierarchy
SAP_HRCDE (Software Component) Sub component SAP_HRCDE of SAP_HR⤷
PY-DE (Application Component) Germany⤷
P01C (Package) HR Customizing: Germany
IMG Activity
| ID | OHADBECB0 | Maintain Data Positioning |
| Transaction Code | S_AHR_61004513 | IMG Activity: OHADBECB0 |
| Created on | 19981221 | |
| Customizing Attributes | OHADBECB0 | Maintain Data Positioning |
| Customizing Activity | OHADBECB0 | Maintain Data Positioning |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHADBECB0 |
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
- Manual entry options
- Printing a supplement
- User exits
- Other payments: tax-exempt and taxable
- 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:
- 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
- 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&#
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 |
|---|---|---|
| OHADBECB0 | DE | Germany |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHADBECB0 | 0 | HLA0003772 | Statements |
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_T512Q | V - View | OH00 | 60 | Information in Fixed Positions | ||
| V_T514C | V - View | OH14 | BEXX 51 | Permitted Conversions | ||
| V_T514K | V - View | OH14 | BEXX 51 | Permitted Table Names | ||
| V_T514N | V - View | OH14 | BEXX 51 | Permitted Field Names |
History
| Last changed by/on | SAP | 19981221 |
| SAP Release Created in |
