Message Number list used by SAP ABAP Class CL_FDT_DB_LOOKUP (FDT: DB Lookup)
SAP ABAP Class
CL_FDT_DB_LOOKUP (FDT: DB Lookup) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | FDT_CHANGE_INFO - 090 | Database table for fetch was removed | ||
| 2 | FDT_CHANGE_INFO - 091 | Database table for fetch was changed from &1 to &2 | ||
| 3 | FDT_CHANGE_INFO - 092 | &1 conditions were inserted for database fetch | ||
| 4 | FDT_CHANGE_INFO - 093 | &1 conditions were deleted for database fetch | ||
| 5 | FDT_CHANGE_INFO - 094 | Conditions were changed for database fetch | ||
| 6 | FDT_CHANGE_INFO - 095 | Database fetch was changed to return single row | ||
| 7 | FDT_CHANGE_INFO - 096 | Database fetch was changed to return all rows | ||
| 8 | FDT_CHANGE_INFO - 099 | Database table &1 for fetch was added | ||
| 9 | FDT_CHANGE_INFO - 123 | Dynamic database view &1 was added | ||
| 10 | FDT_CHANGE_INFO - 124 | Dynamic database view was removed | ||
| 11 | FDT_CHANGE_INFO - 125 | Dynamic database view was changed from &1 to &2 | ||
| 12 | FDT_CHANGE_INFO - 160 | Database lookup expression was created for DDBV &1 with &2 conditions | ||
| 13 | FDT_CHANGE_INFO - 353 | Database lookup expression was created for table &1 with &2 conditions | ||
| 14 | FDT_CHANGE_INFO - 474 | Aggregate function was introduced | ||
| 15 | FDT_CHANGE_INFO - 475 | Aggregate function was removed | ||
| 16 | FDT_CHANGE_INFO - 476 | Aggregate function was changed | ||
| 17 | FDT_CHANGE_INFO - 477 | Aggregate field was introduced | ||
| 18 | FDT_CHANGE_INFO - 478 | Aggregate field was removed | ||
| 19 | FDT_CHANGE_INFO - 479 | Aggregate field was changed | ||
| 20 | FDT_CHANGE_INFO - 480 | Select mode was introduced | ||
| 21 | FDT_CHANGE_INFO - 481 | Select mode was removed | ||
| 22 | FDT_CHANGE_INFO - 482 | Select mode was changed | ||
| 23 | FDT_CHANGE_INFO - 483 | &1 fields were inserted | ||
| 24 | FDT_CHANGE_INFO - 484 | &1 fields were removed | ||
| 25 | FDT_CHANGE_INFO - 485 | Fields were changed | ||
| 26 | FDT_CHANGE_INFO - 487 | &1 input parameters were inserted | ||
| 27 | FDT_CHANGE_INFO - 488 | &1 input parameters were removed | ||
| 28 | FDT_CHANGE_INFO - 489 | Input parameters were changed | ||
| 29 | FDT_CORE - 002 | Version &1 does not exist | ||
| 30 | FDT_CORE - 006 | No active version found for &1 with timestamp &2 | ||
| 31 | FDT_CORE - 060 | Invalid method call, invalid combination of input parameters | ||
| 32 | FDT_CORE - 060 | Invalid method call, invalid combination of input parameters | ||
| 33 | FDT_CORE - 302 | No &1 supplied for &2 | ||
| 34 | FDT_DSM - 000 | Error calling function module &1 | ||
| 35 | FDT_DSM - 001 | Communication failure using RFC connection &1 | ||
| 36 | FDT_DSM - 004 | System failure using RFC connection &1 | ||
| 37 | FDT_DSM - 025 | Add-on SAP NetWeaver Decision Service Management is not installed | ||
| 38 | FDT_EXPRESSIONS - 217 | Database table &1 does not exist | ||
| 39 | FDT_EXPRESSIONS - 228 | Invalid binding for the dynamic database view parameter in line &1 | ||
| 40 | FDT_EXPRESSIONS - 229 | Line &1: Provide a parameter, context element, expression or direct value | ||
| 41 | FDT_EXPRESSIONS - 230 | Parameter binding is only necessary for dynamic database views | ||
| 42 | FDT_EXPRESSIONS - 231 | Line &2: Parameter &1 is unknown or deleted | ||
| 43 | FDT_EXPRESSIONS - 232 | Line &2: Object &1 is no data element | ||
| 44 | FDT_EXPRESSIONS - 233 | Line &2: &1 is no parameter of the dynamic database view | ||
| 45 | FDT_EXPRESSIONS - 234 | Line &2: Object &1 is unknown or deleted | ||
| 46 | FDT_EXPRESSIONS - 235 | Line &2: Object &1 is no data object and no expression | ||
| 47 | FDT_EXPRESSIONS - 236 | Line &1: &2 can not be converted to parameter &3 | ||
| 48 | FDT_EXPRESSIONS - 237 | The dynamic database view parameter &1 at position &2 is not bound | ||
| 49 | FDT_EXPRESSIONS - 238 | Line &2: Parameters must not be of type amount or quantity | ||
| 50 | FDT_EXPRESSIONS - 239 | Line &1: Provide either an expression or data object or a direct value | ||
| 51 | FDT_EXPRESSIONS - 241 | Line &1: Bind parameter &2 to a context element, expr. or direct value | ||
| 52 | FDT_EXPRESSIONS - 597 | Low value &1 is greater than high value &2 | ||
| 53 | FDT_EXPRESSIONS - 598 | The aggregation function &1 is not supported for this database field | ||
| 54 | FDT_EXPRESSIONS - 598 | The aggregation function &1 is not supported for this database field | ||
| 55 | FDT_EXPRESSIONS - 599 | The result data type for aggregate function &1 should be number. | ||
| 56 | FDT_EXPRESSIONS - 599 | The result data type for aggregate function &1 should be number. | ||
| 57 | FDT_EXPRESSIONS - 600 | No table specified for DB Lookup | ||
| 58 | FDT_EXPRESSIONS - 602 | No low parameter specified for field condition &1 | ||
| 59 | FDT_EXPRESSIONS - 603 | No high parameter specified for field condition &1 | ||
| 60 | FDT_EXPRESSIONS - 604 | Invalid low parameter specified for field condition &1 | ||
| 61 | FDT_EXPRESSIONS - 605 | Invalid high parameter specified for field condition &1 | ||
| 62 | FDT_EXPRESSIONS - 606 | Invalid sign &1 for field condition &2 | ||
| 63 | FDT_EXPRESSIONS - 607 | Invalid option &1 for field condition &2 | ||
| 64 | FDT_EXPRESSIONS - 608 | Result is not of type table: only single select allowed | ||
| 65 | FDT_EXPRESSIONS - 609 | For existence check mode, the result should always be boolean | ||
| 66 | FDT_EXPRESSIONS - 610 | Type of database field &1 does not match the type of return field &3 | ||
| 67 | FDT_EXPRESSIONS - 610 | Type of database field &1 does not match the type of return field &3 | ||
| 68 | FDT_EXPRESSIONS - 610 | Type of database field &1 does not match the type of return field &3 | ||
| 69 | FDT_EXPRESSIONS - 610 | Type of database field &1 does not match the type of return field &3 | ||
| 70 | FDT_EXPRESSIONS - 611 | No field of return structure matches any field of DB table &1 | ||
| 71 | FDT_EXPRESSIONS - 612 | Table &1 has no field called &2: field condition mismatch | ||
| 72 | FDT_EXPRESSIONS - 612 | Table &1 has no field called &2: field condition mismatch | ||
| 73 | FDT_EXPRESSIONS - 613 | Invalid value &1 for the Single flag; choose either true or false | ||
| 74 | FDT_EXPRESSIONS - 614 | Field name must not be initial | ||
| 75 | FDT_EXPRESSIONS - 614 | Field name must not be initial | ||
| 76 | FDT_EXPRESSIONS - 616 | SQL error during processing of DB Lookup expression | ||
| 77 | FDT_EXPRESSIONS - 617 | No authorization to use DB table &1 (S_TABU_DIS with ACTIVITY 03) | ||
| 78 | FDT_EXPRESSIONS - 618 | Fill either low or low_value, but not both | ||
| 79 | FDT_EXPRESSIONS - 619 | Fill either high or high_value, but not both | ||
| 80 | FDT_EXPRESSIONS - 620 | No aggregation should be set for this mode | ||
| 81 | FDT_EXPRESSIONS - 621 | No authorization for displaying data from table &1 | ||
| 82 | FDT_EXPRESSIONS - 622 | Element &1 not available in result data object | ||
| 83 | FDT_EXPRESSIONS - 623 | Aggregation function must not be initial | ||
| 84 | FDT_EXPRESSIONS - 624 | Aggregation function and DB fieldname is initial | ||
| 85 | FDT_EXPRESSIONS - 637 | Result data object in aggregation mode should be an element | ||
| 86 | FDT_EXPRESSIONS - 637 | Result data object in aggregation mode should be an element | ||
| 87 | FDT_EXPRESSIONS - 638 | Invalid selection mode | ||
| 88 | FDT_EXPRESSIONS - 639 | Deep structure is not supported as result of DB Lookup expression | ||
| 89 | FDT_EXPRESSIONS - 640 | Invalid value &1 for Distinct flag: needs to be true or false | ||
| 90 | FDT_EXPRESSIONS - 641 | String fields are not supported for where conditions | ||
| 91 | FDT_EXPRESSIONS - 642 | Aggregation selection is allowed only with transparent tables | ||
| 92 | FDT_EXPRESSIONS - 642 | Aggregation selection is allowed only with transparent tables | ||
| 93 | FDT_EXPRESSIONS - 643 | No field in the table with name &1 | ||
| 94 | FDT_EXPRESSIONS - 644 | Amount and quantity types are not supported with field mapping | ||
| 95 | FDT_EXPRESSIONS - 646 | Selection based on amount and quantity types are not supported | ||
| 96 | FDT_EXPRESSIONS - 647 | Reference field referring to a different table for field &1 | ||
| 97 | FDT_EXPRESSIONS - 647 | Reference field referring to a different table for field &1 | ||
| 98 | FDT_EXPRESSIONS - 647 | Reference field referring to a different table for field &1 | ||
| 99 | FDT_EXPRESSIONS - 656 | Result can not have more than 255 fields | ||
| 100 | FDT_EXPRESSIONS - 671 | Not more than 255 selection conditions are allowed | ||
| 101 | FDT_EXPRESSIONS - 672 | Field mapping required if aggregation is used in a condition | ||
| 102 | FDT_EXPRESSIONS - 673 | The aggregation function &1 is not supported | ||
| 103 | FDT_EXPRESSIONS - 674 | Reference field &1 is assigned to the wrong data base field &2 | ||
| 104 | FDT_EXPRESSIONS - 675 | Table &1 has no field called &2: field mapping mismatch | ||
| 105 | FDT_EXPRESSIONS - 675 | Table &1 has no field called &2: field mapping mismatch | ||
| 106 | FDT_EXPRESSIONS - 676 | Aggregation in condition or mapping is not supported in this mode | ||
| 107 | FDT_EXPRESSIONS - 679 | Provide either a database table or a dynamic database view | ||
| 108 | FDT_EXPRESSIONS - 679 | Provide either a database table or a dynamic database view | ||
| 109 | FDT_EXPRESSIONS - 782 | DB lookup must not use dynamic database view based on a table type | ||
| 110 | FDT_EXPRESSIONS - 783 | Used timepoint type for parameter &1 is not supported | ||
| 111 | FDT_EXPRESSIONS - 784 | Errors in the assigned &1 need to be corrected first: | ||
| 112 | FDT_TRACE_INFO - 169 | DB Lookup is processed in &1 mode | ||
| 113 | FDT_TRACE_INFO - 174 | Performing SELECT SINGLE on table &1 with the given conditions | ||
| 114 | FDT_TRACE_INFO - 175 | Performing SELECT on table &1 with the given conditions | ||
| 115 | FDT_WD_EXPRESSION - 054 | No authorization to use DDBV &1 (authorization object FDT_DDBV) | ||
| 116 | FDT_WD_EXPRESSION - 055 | No authorization for displaying data from DDBV &1 (FDT_DDBV) |