Hierarchy
EA-HRGXX (Software Component) Sub component EA-HRGXX of EA-HR⤷
PE-LSO-TM (Application Component) Training Management⤷
LSO_IMG (Package) SAP Learning Solution - IMG
IMG Activity
| ID | HR_LSO_M1C8D1E21A5 | Register Form Classes |
| Transaction Code | S_AEN_10000568 | (empty) |
| Created on | 20050310 | |
| Customizing Attributes | HR_LSO_M1C8D1E21A5AT | Register Form Classes |
| Customizing Activity | HR_LSO_M1C8D1E21A5PO | Register Form Classes |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | HR_LSO_M1C8D1E21A5 |
Use
A form class contains a data hierarchy which serves as a basis for an application form. All of the SAP Learning Solution data that you want to output in a form must be modelled in the form class as a form level. Every form level has a data dictionary (DDIC) structure or a DDIC table type. These DDIC objects use the text variables of the SAP Learning Solution as fields and also use their typing.
Text variables are required in request-based correspondence to access the business data of the SAP Learning Solution (for example, recipient's address or recipient's e-mail address). The text variables are grouped into form classes in the Print Workbench. A form class contains all of the business data provided in the SAP Learning Solution to enable generation of a given document.
All text variables that you want to use in the form are listed in the DDIC structures of the form levels. You can classify your form levels and corresponding DDIC structures according to various aspects, for example:
- recipient-related data
- course-related data
When form classes are being processed, all of the fields of the DDIC structures are filled with data via the read class of the text variables of the same names.
Requirements
Note that the fields of the DDIC structure of the form level must have the same names as the text variables, otherwise no data will be transported to the form level.
Ensure that the typing of the DDIC structures of the form level is correct. It must be identical to the typing of the text variable, otherwise the document cannot be output.
Standard settings
Defining customer form classes is a task for an experienced ABAP administator. You should only do so if you want to replace the SAP form classes with customer form classes. Changing the form classes delivered in the standard system amounts to a system modification.
If you use the form classes delivered in the standard system, you do not need to carry out this IMG activity.
Activities
To register customer form classes for request-based correspondence :
- On the screen Change View Correspondence - Form Classes for Correspondence Types , choose New Entries.
- Enter the correspondence type and the form class you have already defined.
Example
See also
For more information about defining form classes, see the documentation for the Correspondence Tool and the Print Workbench.
You create text variables in the IMG activity Define Text Variables.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
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_TFK070_FRMCLS | V - View | SM30 |
History
| Last changed by/on | SAP | 20050310 |
| SAP Release Created in | 600 |
