Hierarchy
SAP_HRGXX (Software Component) Sub component SAP_HRGXX of SAP_HR⤷
PE (Application Component) Training and Event Management⤷
PP9C (Package) Training and Event Management - Customizing
IMG Activity
| ID | SIMG_OHP3OOIT | Maintain Infotypes |
| Transaction Code | S_AHR_61011930 | IMG Activity: SIMG_OHP3OOIT |
| Created on | 19990204 | |
| Customizing Attributes | SIMG_OHP3OOIT | Define Infotypes for Object Types |
| Customizing Activity | SIMG_CFMENUOHP0OOIT | Maintain Infotypes |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_OHP3OOIT |
In this step, you can change the attributes of an infotype.
An infotype is a collection of logical or business-related characteristics of an object.
You can make the following settings:
- You can change the infotype names.
- You can assign infotypes to standard object types or to customer- specific object types.
- You can define another time constraint for an infotype.
In the case of infotypes with underlying subtypes, the time constraint is defined per subtype. If you wish to create your own subtypes, you have to carry out the step "Maintain subtypes" and define a time constraint per subtype.
Example
The address elements (e.g. postal code, city, street, house number etc.) make up the Address infotype, which could be appended to the object Organizational Unit, for example.
Note
You can create four-digit infotypes in the range from "9000" to "9999".
Requirements
You should already have edited the step "Maintain object types" before doing so.
Recommendation
Customer-specific infotypes should be further subdivided for the individual HR modules.
Example of possible sub-divisions:
Infotype area
Customer master data "9000" to "9099"
Customer plan data "9100" to "9199"
Customer time data "9200" to "9299"
Activities
- Change the name of the infotype, if required.
- Check and, if necessary, change the time constraint of the infotypes or subtypes.
- Assign the infotypes to object types.
Note:
The 'cannot be maintained' field in the view "Infotypes per object type" does not affect the Customizing settings. This field (if it is set) merely specifies that you cannot maintain the infotype in question using the standard transactions.
Business Attributes
| ASAP Roadmap ID | 262 | Technical and Graphical Settings |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_OHP3OOIT | 0 | HLA0009703 | Training and Event Management |
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 |
| T778T | C - View cluster | OOIT | 0000000000 | Infotypes |
History
| Last changed by/on | SAP | 20000202 |
| SAP Release Created in |
