Hierarchy
⤷ PY-AU-PS (Application Component) Public Sector
⤷ P00PSWB (Package) Public Sector : Generic Workbench objects
Basic Data
Data Element | P00_PBS_SPATH |
Short Description | Status path |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | P00_PBS_SPATH | |
Data Type | CHAR | Character String |
Length | 3 | |
Decimal Places | 0 | |
Output Length | 3 | |
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 | Stat path |
Medium | 15 | Status path |
Long | 20 | Status path |
Heading | 20 | Status path |
Documentation
Definition
Status path
Use
This is used in definition of Business rules and Process status flow rules. The status path defines whether a transition between status of sub process scenarios is 'Allowed'/'Not Allowed' in accordance with the business rules.
Dependencies
See also Business Rules, Process Status Flow Rules, Relationship between sub process scenarios.
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 Stat Path: ALLOW Sec SPS : Len of serv
Pri Status : Completed Sec Stat : In Process
i.e Allow the status of sub process scenario Length of Service to be set to 'In Process' only after Master Data changes is 'Completed'.
History
Last changed by/on | SAP | 20040819 |
SAP Release Created in | 470 |