Hierarchy
⤷ PY-AU-PS (Application Component) Public Sector
⤷ P00PSWB (Package) Public Sector : Generic Workbench objects
Basic Data
Data Element | P00_PBS_BRULE |
Short Description | Rules for business flow |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | P00_PBS_BRULE | |
Data Type | CHAR | Character String |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
Value Table | T7PBSWB2H |
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 | Rules |
Medium | 20 | Rules for bus. flow |
Long | 28 | Rules for business flow |
Heading | 25 | Rules for business flow |
Documentation
Definition
Business rules
Use
In the process workbench engine (PWE), several process are linked together to complete a whole business process. These individual processes which are called sub process scenario, need to be completed in a certain sequence. The business rule defines the sequence in which the sub process scenarios have to be executed in order to complete the business scenario.
Dependencies
See also Process Status Flow Rule, 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..
I.e. There are are certain sub process scenarios which are pre-requisite for other sub process scenarios, where as there may be some which are not dependent on each other.
History
Last changed by/on | SAP | 20040819 |
SAP Release Created in | 470 |