SAP ABAP IMG Activity SIMGH_LMON002 (Define Unique Object Class Identifiers, Permitted Movements and Hierarchy)
Hierarchy
☛
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
⤷
LE-TRM (Application Component) Task & Resource Management
⤷
LTRM (Package) TRM - Core Package

⤷

⤷

IMG Activity
ID | SIMGH_LMON002 | Define Unique Object Class Identifiers, Permitted Movements and Hierarchy |
Transaction Code | S_DTR_07000042 | IMG Activity: SIMGH_LMON002 |
Created on | 20010510 | |
Customizing Attributes | SIMGH_LMON002 | Unique object class identifier |
Customizing Activity | SIMGH_LMON002 | Unique object class identifier |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_LEYMOBJID |
Use
In this IMG activity, you can define the following:
- Object class identifiers for each instance of object class in the monitor and alert monitor
- Permitted movements for the drag&drop operation in the monitor hierarchy tree
- Structure of the monitor hierarchy tree for different variants
Example
Requirements
You have already defined additional object classes in IMG activity Define Object Classes.
Standard settings
Object class identifiers, permitted movements and hierarchy are all provided with the standard system.
Recommendation
Activities
- Choose Object Class Identifier.
- Choose New Entries.
- For each new object class that you have defined:
- Enter a previously defined site number in the Site field (TRM) or choose User defined from the Profile field drop-down list (other applications).
- Enter a unique object class ID.
- Enter the previously defined object class number.
- Go back and choose Object Class Permitted Movements.
- Choose New Entries.
- Enter the site number in the Site field (TRM) or choose User defined from the Profile field drop-down list (other applications).
- Define the permitted movement:
- Select the target object class for the drag&drop operation.
- Select the object class to which the criteria object belongs.
- If desired, enter a service (alternative to the one defined in activity Define Object Classes) that is utilized after the permitted movement is made.
- Go back and choose Object Class Hierarchy for Monitor.
- Enter the relevant root object class (not applicable to TRM).
- Enter the site number in the Site field (TRM) or choose User defined from the Profile field drop-down list (other applications).
- Create your own variant by copying the standard entries (site/profile ****, variant **) and changing the variant to your own two-digit identifier.
- Add the new object classes to your variant. You can position them wherever you want, either as a parent object class or as a child object class.
- If you do not want the branch to be displayed in the monitor or alert monitor, select Hide.
Further notes
You can display the object class hierarchy of your variant via the application. For more information, see the Maintaining Monitor Variants chapter in the SAP Library.
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 |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | SIMG_LEYMOBJID | 0 | ALN0000293 O ALN0000292 O ALN0000291 |
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_LMOBD | V - View | SM30 | Object Class Identifier | |||
V_LMOCM | V - View | SM30 | Object Class Permitted Movements | |||
V_LMOCH | V - View | SM30 | Object Class Hierarchy for Monitor |
History
Last changed by/on | SAP | 20030513 |
SAP Release Created in | 101 |