Hierarchy

⤷

⤷

IMG Activity
ID | /IBS/RB_RS_PROP | Definition Usage Probability Provisions |
Transaction Code | /IBS/76000076 | (empty) |
Created on | 20100304 | |
Customizing Attributes | /IBS/RB_RS_PROP | Definition Usage Probability Provisions |
Customizing Activity | /IBS/RB_RS_PROP | Definition Usage Probability Provisions |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /IBS/RB_RS_PROP |
Use
In this Customizing activity, you define settings for the minimum usage probability for provisions. You use the Minimum Usage Probability field to define the smallest permitted percentage that leads to formation of a corresponding risk provision position. This controls the percentage from which the obligation to recognize as liability applies, which causes the system to set up corresponding risk provision positions.
Requirements
Standard settings
Activities
Dependent on the valuation method, RBD area, RBD account type, source system (component ID), source system contract type, and the source system product type, you must define the relevant 'minimum usage probability'.
Example
The following example explains the system settings. After each example, you can see which row of the Customizing settings refers to each requirement:
For contracts of the source system SOURCE-SYS, the following settings are to apply for evaluation method 02 in RBD area 0001 and for RBD accounts of account type '100':
- Source system contracts with contract type 300 and product type 30A should have a minimum usage probability of 55%, so that a provision position can be set up and retained. (see row 2)
- In accordance with the obligation to carry a liability, a minimum usage probability of 50% is sufficient for all other contracts. (see row 1)
This makes the following settings necessary:
Evaluation Method RBD Area Account Type Module ID Contract Type Source System Product Type - Source System Minimum Usage Probability
02 0001 100 SOURCE-SYS 0 * 50,00
02 0001 100 SOURCE-SYS 300 30A 55,00
Further notes
This Customizing activity supports wildcard characters. Wildcard is the name given to a placeholder in the form of an asterisk and allows you to make generalized settings for specific table columns. This minimizes the number of entries that need to be made and provides a better overview. In this table, you can use wildcards for the following fields:
- Product Type - Source System
Note that the "specific entries" are processed first, followed by the general entries.
For amount-dependent or numerical fields, the specified amounts are always interpreted as "valid-from amounts'. This means that at least this value must apply for the corresponding entry to be relevant. The following amount fields are relevant for this Customizing activity:
- Contract Type Source System
Business Attributes
ASAP Roadmap ID | 899 | not to be assigned |
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 | /IBS/RB_RS_PROP | 0 | ALN0000281 | Value Adjustment |
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 |
/IBS/CRB_RS_PROP | S - Table (with text table) | SM30 |
History
Last changed by/on | SAP | 20100304 |
SAP Release Created in |