Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-RM (Application Component) SAP Records Management⤷
SRM_WF_PATH (Package) SRM - Transaction Processing Path
Basic Data
| Data Element | SRMACTINTF |
| Short Description | Name of Interface for Activities |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SEOCLSNAME | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | CLASS | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Interface |
| Medium | 15 | Interface |
| Long | 30 | Interface for Activities |
| Heading | 30 | Interface for Activities |
Documentation
Definition
For each activity area, you can define an Interface ( --> Interfaces) that describes the interface for method calls of an activity in the process route. When Customizing the activities, you can specify a class for each activity that implements this interface.
The functions of an activity area include a function for accessing the methods of a class from the interface, when executing an activity as a step in the workflow that is part of the route.
Example: In the activity area "Disposition" (SRMDP), the interface IF_SRM_DIS_WFPATH_ACTIVITY is defined. The class CL_SRM_DIS_WFPATH_ACTIVITY implements this interface. The activity "Sign approval" is available within a disposition. If a corresponding step is executed in the workflow - BOR object type SDISPOSITN, Method CallDialog - the methods defined in the interface are called at particular points in the program.
The advantage of this method is that customers can develop their own classes in the customer namespace, which implement the interface defined for an activity area. This means it is possible to satisfy customer-specific requirements using the functions available for an activity. SAP already supplies an example implementation for the interface. It is advisable to create other classes as subclasses of this class.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 610 |
