Hierarchy
⤷ FS-RBD (Application Component) Value Adjustment
⤷ /IBS/RB (Package) iBS: Reserve for Bad Debt
Basic Data
Data Element | /IBS/E_PROCCHECK |
Short Description | RBD: Indicator: No Contracts With Reinstated Original Values |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | /IBS/O_PROCCAT | |
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 | 10 | NoReinsVal |
Medium | 20 | No Cntr. w.Reins.Val |
Long | 30 | No Contracts w. Reinst. Values |
Heading | 30 | No Contracts w. Reinst. Values |
Documentation
Definition
You can use the 'No Contracts With Reinstated Original Values' indicator to control whether such source system contracts with reinstated or recovered original values are to be taken into account when processing previous evaluations.
Use
Characteristic Value Description
X If any contracts were processed during the last evaluation using a processing type that is assigned to the processing category "1" (reinstatement of original value), then the system does not include these contracts in the next RBD account update.
<blank> If any contracts were processed during the last evaluation using a processing type that is assigned to the processing category "1" (reinstatement of original value), then the system does include these contracts in the next RBD account update.
Dependencies
You define and classify the processing type in the Customizing activity Define and Classify Processing Types.
Example
During evaluation of the source system contract "1234" on the last month end date, you processed the contract using a processing type that was assigned to the processing category "1 - reinstatement of original value" in Customizing for RBD. Therefore, the risk provision balance was reset completely to 0 (zero).
During the next month end processing, the system again imports data about this source system contract into the IAS interface. No processing type is supplied in the /IBS/TRB_IASGHD interface table (which means that the processing type field contains no entry).
Processing is executed according to the indicator setting:
Characteristic Value Description
X The contract is not included in the next RBD account update, there is no calculation of the risk provision position and no planned records are set up.
<blank> The system calculates a new risk provision requirement and creates any corresponding planned records - although not for unwinding.
History
Last changed by/on | SAP | 20130529 |
SAP Release Created in |