Defines the data that is used in a concrete HR Form.
The single parts of the HR form are generated on the basis of the InfoNet. This includes the following:
· An ABAP Dictionary structure that is used as an interface to the Form Definition.
This structure contains a table for each InfoStar and InfoDimension that exist in the InfoNet.
· A Form Definition that you design at a later date according to your requirements.
· A print program that reads the data described in the InfoNet and calls form printing.
In the overview tree of theMetaNet, select the data you require in the form, in the form of MetaStars with the assigned MetaDimensions and MetaFigures. Transfer the data from the MetaNet to the InfoNet using Drag&Drop.
If you require further information and functions, see the tab pages.
1. The HR Form tab page includes the following:
¡ Name of the HR form
The name cannot be changed here.
Name of the form class used. Changing the name of an existing form class, can lead to significant changes in the printed form.
Name of the MetaNet used. If you change the name of the MetaNet of an existing form, the data that existed in the old MetaNet is not contained in the new MetaNet and is deleted from your form.
¡ Layout Editor
You select the graphics tool for the form layout. We recommend that you use the Form Builder for new forms.
¡ Star structuring
You determine the ABAP Dictionary structures. The following options are available to you:
§ Nested structure
If you choose the nested structure, the InfoStar tables then only contain the key fields of the relevant InfoDimensions and InfoFigures. The attribute fields of the InfoDimensions are available separately in the tables of the InfoDimensions. In the Layout Editor, be that the SAP Smart Forms or Form Builder, you must then collect data that belongs together with special statements, such as: LOOP ... WHERE.
§ Flat structure
If you choose the flat structure, then the InfoStar tables also contain the attribute fields. You should not execute LOOP statements to describe the data that belongs together. The Forms Workplace executes such LOOP statements automatically after reading the data. The tables of the InfoDimensions are available in both layout editors, but are no longer necessary for the form. This procedure makes creating a form considerably easier.
We recommend that you use the flat structure for new forms.
§ Status (active or inactive)
A form has the status active when the ABAP Dictionary structure, the Form Definition, and the print program are active. You can only print active forms.
§ Created by
§ Changed by
¡ Form parts
§ ABAP Dictionary Structure
§ Form Definition
§ Print Program
2. The InfoStars tab page includes an overview of used InfoStars (technical name, description, and MetaStar).
3. The InfoNet is described on the Documentation tab page.
You can edit the documentation on the individual objects in the Forms Workplace. Choose Fullscreen Editor to change the documentation. For detailed information about documentation maintenance, access the SAP Library and choose Human Resources ® HR Tools ® .
4. On the Selection Screen tab page you can change the selection screen of the print program.
You must enter a report class for the print program to constrain the logical database PNPCE. Depending on the report class, you can also make additional fields available that are visible or invisible in the print program. You determine which of these fields should be displayed and which default values the fields should have. The following applies here:
¡ If you have determined a default value for an invisible field, you can then no longer change this value from the print program, even if you use a variant.
¡ If you have determined a default value for a visible field, you can change this value again from the print program.
5. On the Cumulation Wage Types tab page, you assign the cumulation wage types to the form that you want to use in the form.
SAP R/3 creates the cumulation wage types directly after reading the data from the database. They are then, for example, used as normal wage types for a selection. The Forms Workplace uses subapplications to create cumulation wage types. Each subapplication is a defined subarea within SAP R/3 which you can use to store the cumulation wage types.
You can enter two subapplications on the tab page.
¡ The first subapplication is provided by SAP and contains, for example, tax wage types, which are probably identical for all customers.
¡ You create the second subapplication. You define your own cumulation wage types that you need in the form.
This division into subapplications enables you to use your own cumulation wage types in the form without having to modify the subapplications created by SAP.
Double-click on the subapplications to display or change the cumulation wage types that are defined in the subapplication.
The InfoNet is represented in the Forms Workplace in an overview tree. It contains InfoStars that define and group data used in the form. Each InfoStar contains InfoDimensions and possibly InfoFigures.