/SAPDMC/LSMW_OBJ_060 - Dateien spezifizieren und zuordnen
The following messages are stored in message class /SAPDMC/LSMW_OBJ_060: Dateien spezifizieren und zuordnen.
It is part of development package /SAPDMC/LSMW in software component BC-SRV-DX-LSM. This development package consists of objects that can be grouped under "Legacy System Migration Workbench".
It is part of development package /SAPDMC/LSMW in software component BC-SRV-DX-LSM. This development package consists of objects that can be grouped under "Legacy System Migration Workbench".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Specify input files first. |
| 002 | Define source structures first |
| 003 | Define source fields first |
| 004 | Specify an output file first. |
| 005 | This function only exists for text files on Windows with SAP GUI |
| 006 | Value '&' already assigned. |
| 007 | Warning. File '&' created on the application server. |
| 011 | Position the cursor on a node. |
| 012 | File '&' is already specified. |
| 013 | File '&' is already being used in another object. |
| 014 | Position the cursor on a file. |
| 015 | Position the cursor on a source structure. |
| 016 | A file has already been assigned to source structure '&'. |
| 017 | No file has been assigned to source structure '&'. |
| 018 | File '&' can only be assigned to one source structure. |
| 019 | Position the cursor on an input file (application server). |
| 020 | Specify a value for the record length. |
| 021 | You cannot use separators in hexadecimal length fields. |
| 022 | No record end indicators permitted in packed/hexadecimal fields. |
| 023 | No separators permitted in packed/hexadecimal fields. |
| 024 | File name '&' already being used. |
| 025 | Field name only permitted at start of file with separators. |
| 026 | Ensure field order is correct for data from mutiple source structures |
| 027 | If no field names exist, ensure that the field order is correct |
| 028 | File name 'Converted Data': Max. 45 characters (remaining data saved) |
| 031 | Warning: Unable to read file '&'. |
| 032 | Warning: Unable to write to/read file '&'. |
| 033 | Proposed values for file names created. |
| 034 | Operating system message: & |
| 035 | The opening of text files with code page '&' is not supported |
| 040 | Specify a logical path here |
| 041 | A file name has already been specified for system '&'. |
| 042 | Logical path '&1' does not exist for this operating system |
| 043 | Logical path '&1' does not point to physical directory '&2'. |
| 044 | Logical file '&1' does not exist |
| 045 | Logical file '&1' is not assigned to physical file '&2' |
| 046 | No logical path specified for the converted data |
| 047 | No logical file specified for the data to be converted |
| 048 | No file has been specified for the converted data |
| 049 | Length of physical file name '&1' cannot be longer than &2 characters |
| 050 | Shared use of sequential and separate files is not permitted |
| 051 | Loading from front end is not allowed for packed/hexadec. fields |
| 052 | Packed/hexadecimal fields cannot be read in code page & |
| 053 | Code page & does not allow fixed lengths or hexadecimal length fields |
| 054 | Using different sequential files is not allowed |
| 055 | Conversion error during upload (code page &). See long text |
| 056 | Conversion error when opening code page &. See long text |
| 057 | Conversion error while reading (code page &); see long text |
| 058 | Notepad editor opened locally |
| 059 | Cannot access front-end file |
| 060 | '&1' does not exist; edit the logical path using transaction FILE |
| 061 | '&1' does not exist; edit the logical file using transaction FILE |