Ansicht
Dokumentation

/IBS/RB_RS_PROP - Definition Usage Probability Provisions

PERFORM Short Reference   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

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.

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'.

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

30A

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

Addresses (Business Address Services)   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 3462 Date: 20240426 Time: 231059     sap01-206 ( 54 ms )