Message Number list used by SAP ABAP Program MKCDFF37 (External Data Transfer: General Form Routines for All Types)
SAP ABAP Program
MKCDFF37 (External Data Transfer: General Form Routines for All Types) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | GD - 205 | Delete entry file | ||
| 2 | GD - 163 | No physical table determined from the logical file name &. | ||
| 3 | GD - 171 | The output file is empty and cannot be overwritten. | ||
| 4 | GD - 172 | Transfer started by &1 | ||
| 5 | GD - 173 | Transfer started in the background | ||
| 6 | GD - 180 | Processing = &1, Job number = &2, Job name = &3. | ||
| 7 | GD - 183 | ----------------------------Start of the rework-------------------------- | ||
| 8 | GD - 184 | ----------------------------Start of the restart------------------------- | ||
| 9 | GD - 190 | Check level: &1 | ||
| 10 | GD - 193 | Process information: Number=&1, PID=&2, Index=&3. | ||
| 11 | GD - 196 | File &1 could not be opened: &2 | ||
| 12 | GD - 197 | File &1 could not be described: &2 | ||
| 13 | GD - 203 | Batch input postprocessing switched on | ||
| 14 | GD - 204 | No multiple importing set | ||
| 15 | GD - 159 | Logical input file: &1 | ||
| 16 | GD - 211 | &1 Records have been processed. | ||
| 17 | GD - 212 | Transfer with relevance determination | ||
| 18 | GD - 218 | No file could be determined from &1. Termination of EDT | ||
| 19 | GD - 219 | Restart not allowed. -> long text. | ||
| 20 | GD - 232 | Variant: &1 | ||
| 21 | GD - 250 | Output of sender fields of read record no. &1 | ||
| 22 | GD - 316 | Number of correct receiver records: &1 | ||
| 23 | GD - 317 | Number of incorrect receiver records: &1 | ||
| 24 | GD - 336 | External data transfer &1, time &2. | ||
| 25 | GD - 340 | GRPID &1 | ||
| 26 | GD - 341 | User exits are active | ||
| 27 | GD - 407 | Name of the application computer: &1 | ||
| 28 | GD - 090 | &1 = log level | ||
| 29 | GD - 009 | The external log number of this run is &1. | ||
| 30 | GD - 011 | Generated program: &1 | ||
| 31 | GD - 012 | Sender structure: &1 | ||
| 32 | GD - 043 | The length of the output file may not exceed &1 characters. &2, &3. | ||
| 33 | GD - 062 | External data transfer completed with return code: &1. | ||
| 34 | GD - 063 | Initialization of the transfer incorrect. Transfer terminated. | ||
| 35 | GD - 067 | Transfer was terminated. | ||
| 36 | GD - 070 | Number of receiver records: &1 | ||
| 37 | GD - 071 | Name of the transfer program: &1 | ||
| 38 | GD - 076 | &1 = Type | ||
| 39 | GD - 077 | &1 = Type text | ||
| 40 | GD - 089 | &1 = log counter | ||
| 41 | GD - 006 | ---------------------------Normal start---------------------------------- | ||
| 42 | GD - 091 | &1 = Information, &2 = Warnings, &3 = Formats | ||
| 43 | GD - 092 | &1 = Block size | ||
| 44 | GD - 098 | Detail log number = &1 | ||
| 45 | GD - 099 | Serious error has occurred | ||
| 46 | GD - 108 | External customer log number: &1 | ||
| 47 | GD - 109 | No user log number specified | ||
| 48 | GD - 115 | Empty file &1 was imported; transfer canceled | ||
| 49 | GD - 154 | Physical output file: &1, enhancement &2 | ||
| 50 | GD - 155 | Logical output file: &1 | ||
| 51 | GD - 156 | Transfer in productive run | ||
| 52 | GD - 157 | Transfer in test run. | ||
| 53 | GD - 158 | Physical input file: &1 |