Hierarchy
SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR⤷
PY-AU-PS (Application Component) Public Sector⤷
P00PSWB (Package) Public Sector : Generic Workbench objects
IMG Activity
| ID | HR_PBS_00_21_1_1 | Specify Status Change Rules between Sub Process Scenarios |
| Transaction Code | S_KJ4_38000023 | IMG activity: HR_PBS_00_21_1_1 |
| Created on | 20030207 | |
| Customizing Attributes | HR_PBS_00_21_1_1 | Specify Status Change Rules between Sub Process Scenarios |
| Customizing Activity | HR_PBS_00_21_1_1 | Process status flow rule definition |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | HR_PBS_00_21_1_1 |
Example
If the relationship between two Sub Process Scenarios is not independent, then you need to define a Process Status Flow rule. Process Status Flow Rule defines the in-depth relationship between the Primary and Secondary Sub Process Scenarios.
For example taking the case of Primary Sub Process Scenario A and Secondary Sub Process Scenario B.
Sub Process Scenario A - Status Group A1, has values :
- New
- In Process
- Completed
Sub Process Scenario B - Status Group B1, has values :
- New
- Report Generated
- Draft Copy
- Approved
Primary Sub Process Scenario A is PRE-REQUISITE FOR Secondary Sub Process Scenario B.
Process Status Flow Rule for the relationship - XAB :
1. Primary Status A: In process & Preceeding DO NOT ALLOW
Secondary Status B: Report Generated & Succeeding
i.e. If Sub Process Scenario A has status = 'In Process'/'New'(that is preceeding) then Do not Allow Sub Process Scenario B Status to be changed to 'Report Generated'/'Draft Copy'/'Approved'.
2. Primary Status A: Completed ALLOW
Secondary Status B: Report Generated & Succeeding
You can also specify what kind of message to be displayed if the Status Change is not permitted. The type of messages may be "Error/ Warning/Information" type.
Requirements
Standard settings
Recommendation
Activities
Further notes
If you have defined a Process Status Flow Rule between Sub Process Scenario A & B. You can reuse the same Process Status Flow Rule between Sub Process Scenario A & C , B & C, etc. provided both the Sub Process Scenarios use the same Status Group and the relationship between the Sub Process Scenarios is also similar to the relationship between A & B.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional 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_21_1_1 | 0 | L6B0000001 | International Functions for the Public Sector |
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 |
| VV_T7PBSWB5B | V - View | SM30 |
History
| Last changed by/on | SAP | 20041126 |
| SAP Release Created in | 10A |
