Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
FS-RBD (Application Component) Value Adjustment⤷
/IBS/RB (Package) iBS: Reserve for Bad Debt
Basic Data
| Data Element | /IBS/E_LOSS_CTRL |
| Short Description | RBD: Loss Processing ECF |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | /IBS/O_LOSS_CTRL | |
| 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 | Loss Proc. |
| Medium | 15 | Loss Processing |
| Long | 35 | Loss Processing |
| Heading | 45 | Loss Processing |
Documentation
Definition
You can use this field to specify how delivered or entered write-off amounts or losses on receivables are to be dealt with as part of the ECF procedure. Corresponding postings are generated depending on the type of ECF loss processing defined.
The following fixed values are available:
Fixed Value Short Description Description
A Usage Before Direct Write-Off If a write-off or loss on receivables is to be processed, risk provision generated in previous periods is first used. The part of the write-off amount that is not covered by a usage is depicted by a direct write-off.
B Direct Write-Off Before Usage If a write-off or loss on receivables is to be processed, risk provision generated in the current period is first reset and then posted in the form of a direct write-off. The part of the write-off amount that is not covered by a reset is depicted by a usage, provided that risk provision generated in previous periods is available.
C Usage Only If a write-off or loss on receivables is to be processed, a risk provision usage for the corresponding amount is generated; if the existing risk provision is not sufficient, it is simultaneously increased (by means of an appropriation) to the level of the usage that is to be posted.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20131127 |
| SAP Release Created in |
