SAP ABAP Data Element OLDNR (Document and item number of the data in the external system)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions
⤷ VA (Package) Application development R/3 Sales
⤷ CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions
⤷ VA (Package) Application development R/3 Sales
Basic Data
Data Element | OLDNR |
Short Description | Document and item number of the data in the external system |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | TEXT30 | |
Data Type | CHAR | Character String |
Length | 30 | |
Decimal Places | 0 | |
Output Length | 30 | |
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 | Old number |
Medium | 15 | Old number |
Long | 20 | Old doc./item number |
Heading | 55 | Document and item number in the external system |
Documentation
Definition
The number that uniquely identifies document data that comes from an external, non-SAP system.
Use
When a sales document is transferred into the SAP R/3 System, the system displays the external number as part of related system messages. You can then see which data was, or was not, transferred from the external system.
Procedure
Header data should be identified by the document number. Item data should be identified by both document number and item number. You can construct the field differently, depending on the kind of data you want to transfer. It should always be constructed as exactly as possible, so that, if errors appear, they can be traced to the problem data.
History
Last changed by/on | SAP | 19921214 |
SAP Release Created in | 470 |