Service Group
To manage service groups, choose . In this window you can define individual services for service groups and create service group hierarchies by assigning groups to each other.
A service group hierarchy is created by subordinating one or more service groups to one service group. The nesting depth is not restricted.
Note
You cannot use dynamic service groups in normal customizing for service groups used in IS-H*MED.
You must enter an assignment type specified in customizing in the function's initial screen. Assignments are configured depending on assignment types. This means that different hierarchies are created.
Groups are formed for the following reasons:
The hierarchies allow a structured organization of services and simplify navigation within service catalogs. (The performable Perf. Svce
and Req. Svce
indicators are not set if the groups are only used for navigation.)
Where a service is composed of several individual services, you can represent the fact by forming groups. When a request is made to a group, all services within this group are regarded as being requested. (The Perf. Svce
indicator may not be set for subordinate services in the service master if a group can only be performed as a whole.)
The sequence number is used to specify the sequence of services within a group. The sequence number is allocated in ascending order, and is currently used for:
Displaying the services of a service group in the service hit list and input help for entering services.
Breaking down a request profile into discrete requests. For further information please refer to the Request Profiles
section.
It is possible to assign a lock time that describes a time interval during which performance of another service element from the same group is excluded once a service element has been performed.