SAP ABAP IMG Activity OHADBEC0Y (Set Up Form with HR Form Editor)

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	OHADBEC0Y	Set Up Form with HR Form Editor
Transaction Code	S_AHR_61004648	IMG Activity: OHADBEC0Y
Created on	19981221
Customizing Attributes	OHADBEC0Y	Set Up Form with HR Form Editor
Customizing Activity	OHADBEC0Y	Set Up Form with HR Form Editor

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	OHADBEC0Y

In this step, you set up a statement form using the HR form editor.

The information provided below supports the general documentation on the form editor.
To access the general documentation on the form editor, in the transaction for the form editor, choose Help -> Extended help.

Additional Information on Statements (Form Class BEXX)

Attributes

No special features.

Form background

No special features.

Individual fields

Page type

In the standard system, the page type is set to EP in the statements component. Since all entries are made in fixed positions, it is not necessary to differentiate between first page (FP), every page (EP), and last page (LP). This type of coding is only used in forms such as the remuneration statement.

Print information

Constant values, text modules and table fields can be printed in fixed positions. You can also set up manual fields that allow the system administrator to enter additional information after the statement has been created.

For further information, refer to the section Special Features of Statements -> Manual Fields below.

Window

You can not print wage types in a window.

Line layout

Since wage types can not be printed in a window, there is no line layout.

Cumulation identifiers

This function allows you to set up special output wage types for statements (= statement wage types).

The following variants exist:

1. Wage types grouped into a statement wage type
2. Wage types set up in the step 'Assign wage types for form printout' are included in a statement wage type
3. The entry triggers internal calculation of a statement wage type
4. Unpaid absences are encoded by the processing class for absences and the absence valuation rule

For further information, refer to the section Special Features of Statements -> Statement Wage Types.

The standard system includes sample statement wage types for each statement. Replace these sample wage types with your own wage types. Ensure that certain statement wage types have a fixed name and that you use this name when running the program. For information on the statement wage types with and without a name, refer to the section Special Features of Statements -> Statement wage types below.

Text modules

No special features.

Rules

This function allows you to print certain items of information on a statement according to certain rules.

In addition, processing rules are used to print tables.

For further information, refer to the section Special Features of Statements -> Printing tables using rules below.

Special Features of Statements

1. Manual fields
2. Printing payroll results
3. Statement wage types
4. Other payments: Tax exempt and taxable
5. Unpaid absences
6. Regular gross tax amount
7. Constants
8. Time data
9. Leave data
10. Fictitious net
1. Fictitious net in master data
2. Fictitious net in payroll results
3. One-time payments under DM 300
4. Flat-rate tax on remuneration
5. Direct net deduction - Company insurance
   - Employee association contributions
11. Printing tables using rules

1) Manual Fields

It is important that you are able to enter certain types of information in your statement forms manually (for example, data that is not stored in the system). Manual entries can be made in two ways.

1. Manual fields

If you want the statement to include fields whose content is not determined by the system, in the subobject 'Individual fields' enter 'MAN' in the field Table and ' ' in the field Table field. This creates a field that must be maintained manually.

If a fixed text has been defined for this area in the subobject 'Background', it can be overwritten. This entry enables you to determine that text which has already been entered can still be overwritten.

1. Fields that can be overwritten

If you are unsure as to whether the information in the system is correct and you want to be able to overwrite the information when printing, enter conversion 99 in the 'Conversion' field (subobjects 'Individual fields' or 'Rules'). The value stored in the system is then printed but can still be corrected manually.

2) Printing Payroll Results

The individual wage types (from payroll results table RT) are cumulated into a statement wage type, and stored in internal tables. The following codes apply:

• BRT - Period values
• BCRT - Total of all results for statement period
• LRT - Values for last statement period
• LCRT - Implemented only if the statement has statement type F:
  Total for the current year is stored in table BCRT
  Total for the previous year is stored in table LCRT

3) Statement Wage Types

There are 4 coding variants for statement wage types.

1. Wage types are grouped together to form a statement wage type.

Each specified wage type is included in the statement wage type as either a positive or negative amount, depending on the mathematical symbol.

Example

You want to encode statement wage type LFL1.

Cumulation identifier: LFL1

The following summands apply:

Table Identifier Long text Mathematical symbol
----- ---------- --------- -------------------
RT /358 ER HI allowance +
RT /359 ER allow.HI private supp. +
RT /368 ER PI allowance +
RT /369 ER allowance, limited PI +
RT /378 ER UI allowance +
RT /3Q8 ER NI allowance +
RT /3Q9 ER NI allow.private supp. +

1. Wage types set up in the step 'Assign wage types for form printout' are included in a cumulation wage type.

Entries are required for this variant in the steps 'Adjust control parameters' and 'Assign wage types for form printout'. The relationship between the entries is as follows:

1. Adjust control parameters:

The statement is assigned an evaluation class in the 'Evaluation class' field.

Classes 06 - 10 are reserved for statements. Evaluation classes 06 to 08 are used by SAP, and classes 09 and 10 can be defined by the user.

1. Assign wage types for form printout:

The required wage types are maintained with a specification in this evaluation class, and are grouped together.

01 means onetime payment, 09 means employment tax, 10 means church tax, and so on.

1. Cumulation identifiers:

By entering **xx in the 'Identifier' field, the wage types are accessed that are encoded with xx in the evaluation class specified in 'Adjust control parameters'.

Example

In the statement for sick pay/industrial injury pay/transition pay, you want to specify gross pay without onetime payments. In statement wage type BRUG (total gross amounts), the technical wage type "Total Gross Amount" (/101) has a positive value, while the one-time payments are deducted.

1. Step 'Adjust control parameters'
   
   Statement number 14
   Evaluation class 08
2. Step 'Assign wage types for form printout'

Wage types M110 (Leave Allowance), M120 (Christmas Bonus) and M150 (13th Salary) are encoded with 01 in evaluation class "08".

1. Cumulation identifier: BRUG
   
   Table Identifier Mathematical symbol
   ----- ---------- -------------------
   RT /101 +
   RT **01 -
   

1. The Customizing entry triggers an internal calculation of the statement wage type.

The same entries in the fields 'Identifier' for cumulation identifiers and 'Summands' trigger an internal calculation of the wage type.<

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
OHADBEC0Y	DE	Germany

Assigned Application Components

Documentation Object Class	Documentation Object Name	Current line number	Application Component	Application Component Name
SIMG	OHADBEC0Y	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
PE51	T - Individual transaction object	PE51	60	☑	☐	HR: Form Editor

History

Last changed by/on	SAP	19981221
SAP Release Created in