Hierarchy
⤷ FIN-FSCM-COL (Application Component) Collections Management
⤷ UDM_STRATEGY (Package) Collection Strategy, Rule, Basic Rule
Basic Data
Data Element | UDM_FLAG_CONDITION |
Short Description | Basic Rule is Prerequisite for Rule |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | BOOLE | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
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 | 0 | |
Medium | 15 | Prerequisite |
Long | 30 | Prerequisite for Rule |
Heading | 30 | Prerequisite for Rule |
Documentation
Definition
Basic rules can be used as prerequisites or conditions for collection rules.
Use
You should use prerequisites if you want to use the same rules with different prerequisites and possibly different valuations in one strategy.
Example
For business partners with risk class A, fewer valuation points are to be given for an amount to be collected than for business partners with a different risk class.
To do this, you create a collection rule with basic rule BR00000001 as prerequisite and BR00000008 as condition.
This rule is entered in the strategy twice. Both entries have different selection conditions for the risk class, a different valuation, and a different long text for the prerequisite.
Dependencies
In the valuation of a business partner, the system does not distinguish between prerequisites and conditions: All basic rules of a condition rule must be fulfilled for the business partner to receive valuation points.
History
Last changed by/on | SAP | 20050411 |
SAP Release Created in | 600 |