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
Basic Data
| Data Element | P00_PBS_PSREL |
| Short Description | Relationship between sub process scenarios |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | P00_PBS_PSREL | |
| Data Type | CHAR | Character String |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Relation |
| Medium | 20 | Relation btw process |
| Long | 30 | Relation btw process scenario |
| Heading | 30 | Relation btw process scenario |
Documentation
Definition
Relationship between sub process scenarios.
Use
For a process scenario, a business rule needs to be defined that determines the sequence in which the sub process scenarios need to be processed.
At the first level, the business rule is defined by specifiying relationships between the respective sub process scenarios. i.e. the sub process scenarios are independent of each other or not. This field is used to define this relationship.
At the second level, the detailed sequence is defined. i.e. the transition of a sub process scebario status is allowed/ not allowed based on the status of certain pre-requisite sub process scenarios.
Dependencies
See also Business rules and Process status flow rule.
Example
In a business scenario like "Pension Administration for Employees", the sub process scenarios could be -
- Master Data changes
- Calculate length of Service
- Generate Notification reports
- Approve reports, etc..
The sequence of steps to complete the business scenario may be : first complete Master Data Changes, then calculate length of service and then proceed to generate notification reports,etc..
So process status flow rule between the sub process scenarios could be defined as -
Prim SPS : MData Changes PRE-REQUISITE Second SPS : Len of service
i.e. the relationship between these 2 sub process scenarios is that Master Data Changes must be first processed before processing Length of Service.
History
| Last changed by/on | SAP | 20040819 |
| SAP Release Created in | 470 |
