SAP ABAP IMG Activity HR_LSO_M1C1D3E1A1 (Define Object Types)
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_M1C1D3E1A1 Define Object Types  
Transaction Code S_AX8_68000190   IMG Activity: HR_LSO_M1C1D3E1A1 
Created on 20020321    
Customizing Attributes HR_LSO_M1C1D3E1A1AT   Define Object Types 
Customizing Activity HR_LSO_M1C1D3E1A1PO   Define Object Types 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HR_LSO_M1C1D3E1A1    

In this step, you make the settings necessary for changing standard object types and creating new object types.

You can make the following settings:

  • You can define the relationship that should be proposed in the course of the authorization check. For more information on this, please refer to the section "Structural authorization".
  • You can create or change external object types that are not administered in PD (e.g. object type "employee" from HR Master Data Management).

    In this case, you must specify the interface program used to access these object types.

  • You can define an object type hierarchy for evaluations (reporting).
  • You can, if necessary, change the ID of a standard object type ("O" for organizational unit, "T" for task).

Example

If you are reporting on positions, the report will include objects whose object type is the same as the value assigned to the semantic abbreviation "PLSTE" in the parameter group "OTYPE". (In this case 'S').

  • You can maintain the controlling entries for object type-related transactions.

    The information regarding which object type is to be edited in the transaction is stored for each object type-related transaction (PO** = menu-guided infotype maintenance).

Note

You can create two-digit object types in the range "01" to "99".

Activities

  1. Define the mandatory relationship, if required.
  2. Create external object types and specify the program that accesses these object types.
  3. Define an object type hierarchy for the evaluation (reporting).
  4. Change the ID of a standard object type only if it is absolutely necessary, observing the name ranges reserved for customer-specific entries.
  5. If you have created new object types, change the value of the semantic abbreviation of each object type in the parameter group OTYPE, where necessary.

    Similarly, if necessary, change the value of the semantic abbreviation for each object type-related 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 
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 0000000000 Object Types 
History
Last changed by/on SAP  20020430 
SAP Release Created in 2002_1_46C