Hierarchy
⤷ FIN-FSCM-TRM-TM (Application Component) Transaction Manager
⤷ FTR_DATA_TRANSFER (Package) Legacy Data Transfer
Basic Data
Data Element | TPM_TRDT_POSNR |
Short Description | Item Number Legacy Data Transfer |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | NUMC08 | |
Data Type | NUMC | Character string with only digits |
Length | 8 | |
Decimal Places | 0 | |
Output Length | 8 | |
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 | ItemNo |
Medium | 15 | Item Number |
Long | 20 | Item Number |
Heading | 11 | Item Number |
Documentation
Definition
The position number can be used for the following as part of the legacy data transfer:
- Several data records for the same key date
If you want to enter more than one data record concerning the same position for a single key date, you can do this by assigning different position numbers.
- Identification of single positions (securities)
If single position management is to be used for a product type, you can address the correct single position by using the position number. A position number must first be assigned for the valuation-area-independent data record. This number must then be entered in the corresponding valuation-area-dependent data record which contains the same key date and differentiation values.
Use
Dependencies
If the valuation-area-independent legacy data transfer for securities is carried out by means of transaction management, a correct single position can be addressed. If you are using single position management, you can address the correct single position in the corresponding valuation-area-dependent records by means of the transaction number which was generated by the single position.
This is generally the procedure for futures.
Example
History
Last changed by/on | SAP | 20040819 |
SAP Release Created in | 500 |