Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
JBA (Package) Application developmnet IS-B General Development
Basic Data
| Data Element | JBABMENGV |
| Short Description | Position - No. of Units (by Value Date) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | MENGE | |
| Data Type | QUAN | Quantity field, points to a unit field with format UNIT |
| Length | 13 | |
| Decimal Places | 3 | |
| Output Length | 17 | |
| 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 | Units(V.D) |
| Medium | 15 | No.Units(V.Dte) |
| Long | 20 | No. Units (Val.Date) |
| Heading | 0 |
Documentation
Definition
Depending on the product category and quotation type, positions are updated either using the nominal amount or the number of units.
The position value is the sum of the flows posted up to the key date.
The number of units based on the value date is only updated for unit-quoted securities. A security order contains the 'interest value date' as well as the 'position value date'. The number of units in the position changes on the 'position value date' while the number of units based on value date changes on the 'interest value date'. Since these two dates can differ, the number of units in the position value and the number of units based on value date are not necessarily the same.
Use
The number of units based on value date has no application at present.
History
| Last changed by/on | SAP | 20011002 |
| SAP Release Created in |
