Hierarchy

⤷

⤷

IMG Activity
ID | /ORM/ORMT_PER_SET | Perform Segment Settings |
Transaction Code | /ORM/31000022 | (empty) |
Created on | 20070523 | |
Customizing Attributes | /ORM/ORMT_PER_SET | Perform Segment Settings |
Customizing Activity | /ORM/ORMT_PER_SET | Perform Segment Settings |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /ORM/PERFORMSEGMENTSETTINGS |
Use
In this IMG activity you configure and maintain the segment settings for incidents.
Incidents are assigned to segments. When an incident is posted, the segment is determined automatically. The desired segments must be configured in this IMG activity.
Note: For ESS scenarios, the segment table ID is a mandatory URL parameter, which defines the available context of the particular ESS Incident posting page.
The segment configuration consists of three elements, each with various functions:
- Dimension maintenance
- Segment tables
- Segment table maintenance
Dimension Maintenance
Segments are de-facto sets of dimensions. Therefore, the first step in configuring segment settings is dimension maintenance.
- Click Create Default Dimensions to create three standard dimensions linked to Risk Management data, Organizational Units, Activity Catalog, and Risk Catalog.
- Click Dimension Maintenance to maintain the dimensions in the standard maintenance view. Each dimension has an ID, a language-dependent name, an implementation class, and parameters. The implementation class is any class that implements the interface /ORM/IF_ORM_ILD_SGMT_DIM. Currently RM provides two classes /ORM/CL_ORM_ILD_SGMT_DIM_HRORG and /ORM/CL_ORM_ILD_SGMT_DIM_TAB. Details, such as parameters formatting, are found in the class documentation. You can also develop your own classes if necessary.
Segment Tables
Each segment table has an ID, a language-dependent name, a flag to activate and deactivate the segment (i.e. allow the allocation of events into the segment table), and the validation flag. If the validation flag is on, the events posted to the segment table require the validation workflow and the Org. Unit must be maintained within the segment table.
Segment Table Maintenance
Once you provide the name of the segment table you can perform several activities:
- Check - Check the consistency of the generated dictionary structures.
- Create - Generate the dictionary structure and database table for the segment table. You must generate the dictionary structure and database table before you can use the segment.
- Number Range - Maintain the number range for the segment table; you must maintain the number range 01. For more information see the IMG activity Maintain Number Range for Incidents.
- Display - Here you can see the generated database table in the raw view and perform further inspection and maintenance activities such as index creation.
- Last Log - This is where you can view the log produced by the last activity.
- Add Dimension - Add a new dimension to the segment table. This requires broad database authorizations.
- Delete Dimension - Never do this if you are not sure!! Removing a dimension from the segment table recalculates all the segment references of the involved incidents. This can take a lot of time.
Standard settings
Activities
Example
Business Attributes
ASAP Roadmap ID | 201 | Make global settings |
Mandatory / Optional | 1 | Mandatory 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 |
/ORM/ORM_ILD_SGMTAB | T - Individual transaction object | /ORM/ORM_ILD_SGMTAB |
History
Last changed by/on | SAP | 20070718 |
SAP Release Created in | 200 |