SAP ABAP IMG Activity OHP7_0370 (Maintain Object Types)
Hierarchy
☛
SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR
⤷ PA-PM (Application Component) Budget Management
⤷ PM01 (Package) HR Funds and Position Management
⤷ PA-PM (Application Component) Budget Management
⤷ PM01 (Package) HR Funds and Position Management
IMG Activity
ID | OHP7_0370 | Maintain Object Types |
Transaction Code | S_AHR_61007635 | IMG Activity: OHP7_0370 |
Created on | 19981221 | |
Customizing Attributes | OHP7_0370 | Maintain Object Types |
Customizing Activity | OHP7_0370 | Maintain Object Types |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OHP7_0370 |
In this step, you make the necessary system settings for changing standard object types and for setting up new object types.
Important!
Always consult SAP before you create new object types!!
You can make the following settings:
- You can specify the relationship to be proposed during the authorization check (see the section entitled "Structural Authorization").
- You can create and change external object types that are not managed in Personnel Planning and Development (for example, the object type "Person" from Personnel Administration).
In this case, you must specify the interface program used to access these object types.
- You can define the object type hierarchy for reporting.
- If necessary, you can change the abbreviation used for a standard object type (e.g. "O" for organizational unit, "T" for task).
Example
If positions are required for an evaluation, then the evaluation analyzes all objects whose object type is the same as the value assigned to the semantic abbreviation "PLSTE" in parameter group "OTYPE" (in this case, "S").
- You can define control entries for object type based transactions.
You specify which object type (see above) is processed by each object type based transaction (PO** = menu driven infotype maintenance).
Note
You can create 2-digit, numerical object types (ranging from "01" through "99").
Activities
- If applicable, define the target relationship.
- If applicable, create external object types, and specify the program used to access these object types.
- Define the object type hierarchy for reporting.
- Only ever change the abbreviation of a standard object type if this is absolutely necessary! Always use the name ranges reserved specially for customer specific entries.
- If you have created new object types, you might need to change the value of the semantic abbreviation for this object type in the parameter group OTYPE.
- In the same way, if you need to, change the value of the semantic abbreviation of the corresponding object type based transaction in the parameter group TCODE.
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 | OHP7_0370 | 0 | AHR0000233 | Human Resource Funds and Position 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 |
T7780 | C - View cluster | OOOT | HR-PAPM-HR | Structurally-Dependent Object Types |
History
Last changed by/on | SAP | 19981221 |
SAP Release Created in |