Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
RE (Application Component) Real Estate Management⤷
FVVICN (Package) R/3 Real Estate Application Development - General Contract
Basic Data
| Data Element | BMWST_DI |
| Short Description | Value-added tax amount included |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR18 | |
| Data Type | CHAR | Character String |
| Length | 18 | |
| Decimal Places | 0 | |
| Output Length | 18 | |
| 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 | VAT |
| Medium | 15 | Value-added tax |
| Long | 20 | Value-added tax |
| Heading | 18 | Value-added tax |
Documentation
Definition
The value-added tax amount underlying the payment transaction in the specified currency.
Dependencies
- See also Condition amount field.
- Exception jurisdiction code:
If the tax calculation with jurisdiction code is activated, the posting or reference date of the transaction is needed to determine the value added tax. These dates may not be available when the value is displayed.
Example: Display of planning records for a rental agreement cash flow or the simulation of a rental agreement debit position.
In order to be able to calculate the value added tax in spite of this, a certain date is chosen for calculation, depending on the activity.
In the case of the display of the rental agreement cash flow, the due date of the item is used.
However, this can result in a different tax amount than the one in the actual subsequent activity.
History
| Last changed by/on | SAP | 19991014 |
| SAP Release Created in |
