Hierarchy
EA-HRGXX (Software Component) Sub component EA-HRGXX of EA-HR⤷
PA-AS (Application Component) HR Administrative Services⤷
PAOC_ASR_PROCESS_MODELLING (Package) Modeling Processes
IMG Activity
| ID | HRAS_PROCESS_OBJECT | Required Settings for Process Object in Case Management |
| Transaction Code | S_PEN_05000314 | (empty) |
| Created on | 20050607 | |
| Customizing Attributes | HRAS_PROCESS_OBJECT | Required Settings for Process Object in Case Management |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | HRAS_PROCESS_OBJECT |
Use
Runtime data that is saved during the execution of form-based workflow steps is saved using the Case Management component.
In Case Management, the data is stored hierarchically in three levels, whereby each level is defined in Case Management as a so-called case type.
- The data and attributes of the processes are saved in the top level, such as the process initiator, for example.
The associated case type in Case Management is the process (H_PO).
- The data and attributes for a form scenario are saved in the middle level, such as the form scenario used in the process and the form scenario version.
The associated case type in Case Management is the scenario (H_FO). If several form scenarios are used in a process, then the process (case type H_PO) contains several scenario objects.
- The data and attributes for a scenario step are saved in the bottom level, such as which user performed the scenario step and what is the current status of the scenario step.
The associated case type in Case Management is the step (H_SO). If there are several scenario steps in a process that use the same form scenario and form scenario version, then the relevant scenario (case type H_FO) contains several step objects.
In the following text, the term process object is used to describe a summary of all data of a process for the three levels described above.
You can display the data of a process object in the backend system with the transaction SCASE (Case Management). This should only be necessary for analysis purposes. Within the transaction, you must specify a suitable Records Management System ID (RMS ID). The case types described above are assigned to the RMS ID ASR_POBJ.
Requirements
Standard settings
SAP delivers the following default case types that are assigned to the Records Management System ID ASR_POBJ:
- Process (H_PO)
- Scenario (H_FO)
- Step (H_SO)
SAP delivers the following profiles for the so-called case search for the default case types H_PO, H_FO, and H_SO.
- Process Search (ASR_POBJ)
- Scenario Search (ASR_FOBJ)
- Step Search (ASR_SOBJ)
This enables you to find instances of the relevant case type quickly.
Activities
In the subsequent IMG activities, you define the necessary settings for setting up the process object framework for the applications of HR Administrative Services (User).
Copy the delivered case types (IMG activity Copy Case Types) from the delivery clients. It is important that you transfer the case types unchanged.
You then copy the profiles (IMG activity Create Profile for Case Search) from the delivery clients. You can adjust the profiles as required.
Example
Business Attributes
| ASAP Roadmap ID | 105 | Define functions and processes |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | 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 | HRAS_PROCESS_OBJECT | 0 | AEN0000011 | HR Administrative Services |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20050713 |
| SAP Release Created in | 600 |
