Hierarchy
⤷ PY-AU-PS (Application Component) Public Sector
⤷ P00PSWB (Package) Public Sector : Generic Workbench objects
IMG Activity
ID | HR_PBS_00_99_1_1 | General Information |
Transaction Code | S_KJ4_38000030 | IMG activity: HR_PBS_00_99_1_1 |
Created on | 20030225 | |
Customizing Attributes | HR_PBS_00_99_1_1 | General information |
Customizing Activity | HR_PBS_00_98_1_1 |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | HR_PBS_00_99_1_1 |
The Process Workbench Engine(PWE) can be used for different kinds of HR processes in an organization. You can use it for processes such as Termination, Increment Administration, Pension Administration, Payroll related actvities, etc. It gives a holistic view of the entire process and the associated child-processes and tracks the status at each stage of the process.
PWE can be configured so that the sequence or rules are adhered to complete the whole process. It is integrated with the object manager which provides search mechansim based on employee, process to be performed, etc.
The following steps would show how to configure your process in PWE.
1. At the first level you need to configure your business scenario. i.e. the HR process you want to put into PWE. Some examples could be as described above Pension Administartion process, Termination process, Increment process, etc.
2. At the second level you must specify what are the process scenarios in your business scenario. An example could be : Under Pension Administration business scenario, you may have process scenarios like - Basic Pension Assessment, Additional Assessment due to change in allowances, etc.
3. At the third level you would need to specify what are the sub process scenarios which need to be done in a process scenario. For example in the Basic Pension Assessment process scenario mentioned above, you may need some changes to be performed on Master Data, Calculate length of Service of Employee, Simulate Payroll and Generate certain Notification Reports.
4. There may be an additional level you have below the sub process scenarios, where in the need may be to categorise the activity based on the kind of activity. For example in the Master Data Changes Sub Process Scenario described above, you may have further classifications like - Master Data changes Payroll related, Master data changes Time related, etc. This level is called Process Tasks.
To make the entire business scenario function in a way that the legal rules, business rules, jurisdictions, etc are followed you may configure certain business rules for it.
The business scenario can be configured to make it dependent on user roles.
Example
Requirements
Standard settings
Recommendation
Activities
Further notes
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 3 | Nonrequired 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 | HR_PBS_00_99_1_1 | 0 | HLA0100675 |
Maintenance Objects
Maintenance object type |
History
Last changed by/on | SAP | 20030225 |
SAP Release Created in | 10A |