Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
CA-GTF-DRT (Application Component) Data Retention Tool⤷
FTW1 (Package) Data Retention Tool
Basic Data
| Data Element | TXW_LFILE |
| Short Description | Data File Name |
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 | TXW_LFILE | |
| Search Help: Parameters | L_FILE | |
| Parameter ID | XW2 | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Filename |
| Medium | 15 | Filename |
| Long | 20 | Data file name |
| Heading | 30 | Data file name |
Documentation
Definition
Each data extract or view file has a unique name.
From a technical point of view this name is treated as a platform-independent, logical file name. From this logical file name and the directory set, the system creates physical file names that are valid for your application server.
Naming considerations
File names must follow the conventions of the application server operating system. If you plan to store files on CD-ROM disks in ISO 9660 format, additional restrictions apply:
- File names must not exceed eight characters, and extensions three characters ("8.3 format").
- File names and extensions must all be in the upper case.
- Numbers in file names should be separated from the alphabetical characters by an underscore. Example: JAN_97.TXT.
- Only these characters are allowed: A - Z, 0 - 9, _ (underscore)
In the data file configuration, you can specify that file names must conform to ISO 9660 and that utilities reject file names that do not conform.
Technical background
All read and write data retention tool utilities use the standard logic to convert logical file names to physical file names. The required customizing settings are already preconfigured for UNIX and Windows NT file systems. If you have another file system, you need to create a corresponding syntax group for the logical path "TXW_TAXFILE_PATH" with transaction FILE. The physical path in the syntax group must include the variable <PARAM_1> for the file path and the variable <FILENAME> for the file name. In most cases, you combine these two variables.
Example: for Unix and Windows NT the physical path is <PARAM_1><FILENAME>.
During runtime, the system replaces <PARAM_1> with a path from the specified directory set and <FILENAME> with the logical file name.
Depending on the data volume, the extraction utility may create several physical files so that each file is smaller than the globally specified maximum file size.
Each file is identified by a volume ID. Volume IDs for extension files are "01" for the first extension, "02" for the second extension, and so on. File names for extension files are created automatically by appending an underscore "_" character plus the volume ID to the logical file name that was specified on the selection screen.
Example: The logical file name is "taxfile", the directory is "/usr/sap/tmp/" for all volume IDs. If the extraction utility creates 2 extension files, the following files are created in the specified order:
- /usr/sap/tmp/taxfile
- /usr/sap/tmp/taxfile_01
- /usr/sap/tmp/taxfile_02
- /usr/sap/tmp/taxfile_DR
The file with extension _DR is a directory file that contains one entry for each physical file that was created for the extract. This file is used by the reporting utilities and must be stored together with the first file (/usr/sap/tmp/taxfile in the above example).
History
| Last changed by/on | SAP | 20010830 |
| SAP Release Created in |
