SAP ABAP Data Element N2DOC_KEY_STRING (Formatted Doc Key for Messages etc)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷
NMED (Package) R/3MED: Medical documentation GSD

⤷

⤷

⤷

Basic Data
Data Element | N2DOC_KEY_STRING |
Short Description | Formatted Doc Key for Messages etc |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR36 | |
Data Type | CHAR | Character String |
Length | 36 | |
Decimal Places | 0 | |
Output Length | 36 | |
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 | 0 | |
Medium | 0 | |
Long | 0 | |
Heading | 0 |
Documentation
Definition
The key for medical documents consists of 4 parts and has a total length of 33 characters. As standard, the number range of the document number (DOKNR) has 9 leading zeroes. This means that the document key, in particular as a variable in messages, is hard to read.
You should use the Form routine CONCATENATE_DOC_KEY (IN2RETURNF00) to prepare the document key for display:
- Delete leading zeroes from Doc. No.
- Separate key components with '/'
- Semantically correct sequence
The system will deliver a string with a maximum length of 36 characters: dokar/doknr/doktl/dokvr.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20050223 |
SAP Release Created in | 471 |