SAP ABAP Data Element NO_TMP_NAM (Indicator: no renaming of temporary file)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CA-DMS (Application Component) Document Management System
⤷
CV (Package) Application Development: R/3 Document Management

⤷

⤷

Basic Data
Data Element | NO_TMP_NAM |
Short Description | Indicator: no renaming of temporary file |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | NOTEMPFILE | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 8 | NoRename |
Medium | 16 | No renaming |
Long | 16 | No renaming |
Heading | 0 |
Documentation
Definition
When you display an original application file that is stored in a secure storage area, this indicator determines whether the file can be renamed.
Use
To display an original application file that is stored in the SAP database, a vault, or an archive, the system creates a copy.
- In the standard SAP System, the copy is assigned a name according to the naming convention defined in the program.
- Some viewing programs can only find an original application file if the copy of the file has the name that the file had when it was saved to a secure storage area. In this case, the naming convention links the redline file to the viewer file.
If you set this indicator, the copy is assigned the name that the original application file had when it was saved to the secure storage area.
Procedure
Only set this indicator if your viewer application does not allow renaming of the file.
Examples
Dependencies
History
Last changed by/on | SAP | 19980423 |
SAP Release Created in |