Hierarchy
⤷ IS-B-DP (Application Component) Transaction Data Pool
⤷ JBD (Package) Application development IS-B Data Pool
Basic Data
Data Element | JBSRKUGVB |
Short Description | Realized Price Gains/Losses (Position) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | JBSRKUGVB | |
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 | Real. G/L |
Medium | 15 | Real. Gain/Loss |
Long | 20 | Real. Gains/Losses |
Heading | 0 |
Documentation
Definition
This indicator controls whether realized price gains and losses are to be calculated for single positions in single transaction costing.
Realized price gains occur for security orders, or other position changes that affect revenue (such as transfer postings). The results for security orders can be determined by costing the particular single transactions. Alternatively, these results can be determined in aggregated form by costing the corresponding positions. After doing so, however, you can no longer break it down to the single transaction level.
The income results for other position changes which affect revenue can only be determined by costing the positions.
Use
The user has the following options:
- Realized price gains/losses are not to be calculated.
- Realized price gains/losses are to be calculated only for other position changes.
- Realized price gains/losses should be calculated for orders and other position changes.
- Realized price gains/losses are to be transferred.
If securities orders are included in the realized result, the price gains and losses must not be determined when the single transactions are costed. This would cause the results to be displayed twice.
History
Last changed by/on | SAP | 20011002 |
SAP Release Created in |