SAP ABAP Message Class FDT_TRANSPORT (Formula & Derivation Tool: Transport)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-SRV-BR (Application Component) BRFplus - ABAP-Based Business Rules
⤷
SFDT_TRANSPORT (Package) BRFplus: Transport
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-BR (Application Component) BRFplus - ABAP-Based Business Rules⤷
SFDT_TRANSPORT (Package) BRFplus: Transport 
Attributes
| Message class |  |
FDT_TRANSPORT |
| Short Description |  |
Formula & Derivation Tool: Transport |
| Changed On |  |
20141121 |
| Last Changed At |  |
124013 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
BRF+: Program failed with exception &1 | The short text describes the object sufficiently | |
| 2 | 001 |
BRF+: Invalid Table Type &1 | The short text describes the object sufficiently | |
| 3 | 002 |
BRF+: Expression Type ID &1 does not exist | The short text describes the object sufficiently | |
| 4 | 003 |
BRF+: Table Type &1 not supported for Expression Type &2 | The short text describes the object sufficiently | |
| 5 | 004 |
The short text describes the object sufficiently | ||
| 6 | 006 |
BRF+: Request Type &1 is not within the allowed virtual request types &2 | The short text describes the object sufficiently | |
| 7 | 007 |
BRF+: Formal consistency check of transport list was successful | The short text describes the object sufficiently | |
| 8 | 008 |
BRF+: Incomplete transport list. The following objects are missing | The short text describes the object sufficiently | |
| 9 | 009 |
BRF+: Directly or indirectly referenced object &1 was never transported | The short text describes the object sufficiently | |
| 10 | 010 |
BRF+: &1 objects with no active version were specified in the object list | The short text describes the object sufficiently | |
| 11 | 011 |
BRF+: Unable to read full transport request &1. See preceeding message | The short text describes the object sufficiently | |
| 12 | 012 |
BRF+: Object can only be marked for deletion; see following messages | The short text describes the object sufficiently | |
| 13 | 013 |
BRF+: All BRFplus objects (&1) could be locked successfully | The short text describes the object sufficiently | |
| 14 | 014 |
BRF+: Runtime client: &1 / target client: &2 | The short text describes the object sufficiently | |
| 15 | 015 |
BRF+: Foreign lock &3.&1/&2 FDT source/target objects could not be locked | Space: object requires documentation | |
| 16 | 016 |
BRF+: Invalid request type &1 | The short text describes the object sufficiently | |
| 17 | 017 |
&1 is not a valid database table | The short text describes the object sufficiently | |
| 18 | 018 |
Illegal method call; IS_VALUE is not compatible with IV_TABNAME | The short text describes the object sufficiently | |
| 19 | 019 |
BRF+: Object &1 (&2) has no source version | The short text describes the object sufficiently | |
| 20 | 020 |
Discard version timestamp &1 must not be greater than current timestamp | The short text describes the object sufficiently | |
| 21 | 021 |
BRF+: &2 started for &1 object IDs | The short text describes the object sufficiently | |
| 22 | 022 |
BRF+: &2 successful for &1 object IDs | The short text describes the object sufficiently | |
| 23 | 023 |
BRF+: Only test mode: No database changes | The short text describes the object sufficiently | |
| 24 | 024 |
BRF+: &2 failed (step: &1) | The short text describes the object sufficiently | |
| 25 | 025 |
BRF+: <<< BEGIN: Messages for IDs (&2/&3) &1 >>> | The short text describes the object sufficiently | |
| 26 | 026 |
BRF+: <<< END : Messages for IDs (&2/&3) &1 >>> | The short text describes the object sufficiently | |
| 27 | 027 |
BRF+: After Import failed with exception &1 | The short text describes the object sufficiently | |
| 28 | 028 |
BRF+: Before Export failed with exception &1 | The short text describes the object sufficiently | |
| 29 | 029 |
BRF+: After Import failed with uncaught exception &1 | The short text describes the object sufficiently | |
| 30 | 030 |
BRF+: Before Export failed with uncaught exception &1 | The short text describes the object sufficiently | |
| 31 | 031 |
BRF+: Object activation of new version started for &1 object IDs | The short text describes the object sufficiently | |
| 32 | 032 |
BRF+: Object activation of new version successful for &1 object IDs | The short text describes the object sufficiently | |
| 33 | 033 |
BRF+: Exception Text: '&1' | The short text describes the object sufficiently | |
| 34 | 034 |
BRF+: Object activation failed (step: &1 ) | The short text describes the object sufficiently | |
| 35 | 035 |
BRF+: Object check started for &1 (deep: &2) object IDs | The short text describes the object sufficiently | |
| 36 | 036 |
BRF+: Object has inactive version; activate before transport; s. longtext | Space: object requires documentation | |
| 37 | 037 |
BRF+: Object check failed for &1 object IDs | The short text describes the object sufficiently | |
| 38 | 038 |
BRF+: Object check successful for &1 object IDs | The short text describes the object sufficiently | |
| 39 | 039 |
BRF+: Object changed after write to transport; see long text (SE91) | Space: object requires documentation | |
| 40 | 040 |
BRF+: Data changes committed | The short text describes the object sufficiently | |
| 41 | 041 |
BRF+: Data changes rolled back | The short text describes the object sufficiently | |
| 42 | 042 |
Get inactive transports | The short text describes the object sufficiently | |
| 43 | 043 |
Get all inactive transports | The short text describes the object sufficiently | |
| 44 | 044 |
BRF+: Physical delete for &1 object IDs was successful | The short text describes the object sufficiently | |
| 45 | 045 |
BRF+: Physical delete failed with exception | The short text describes the object sufficiently | |
| 46 | 046 |
BRF+: &1 object IDs were already deleted physically | The short text describes the object sufficiently | |
| 47 | 047 |
BRF+: Physical delete started for &1 object IDs (table type &2) | The short text describes the object sufficiently | |
| 48 | 048 |
BRF+: Time stamp: &1 | The short text describes the object sufficiently | |
| 49 | 049 |
BRF+: Object list: &1 | The short text describes the object sufficiently | |
| 50 | 050 |
BRF+: DB copy is started for &1 object IDs ( &2 -> &3 ) | The short text describes the object sufficiently | |
| 51 | 051 |
BRF+: Persistence object &3 - version copy for &1 ( &2 ) lines executed | The short text describes the object sufficiently | |
| 52 | 052 |
BRF+: Copy for &1 ( &2 ) lines of persistence object &3 executed | The short text describes the object sufficiently | |
| 53 | 053 |
BRF+: Copy and activation already executed for all object ID versions | The short text describes the object sufficiently | |
| 54 | 054 |
BRF+: &1 lines of persistence object &2 changed | The short text describes the object sufficiently | |
| 55 | 055 |
BRF+: &1 Object IDs have to be newly created in the target | The short text describes the object sufficiently | |
| 56 | 056 |
BRF+: &1 Object IDs have to be newly deleted logically in the target | The short text describes the object sufficiently | |
| 57 | 057 |
BRF+: &1 Object IDs will be processed in the target | The short text describes the object sufficiently | |
| 58 | 058 |
BRF+: &1 Object IDs skipped: Already deleted logical in target and source | The short text describes the object sufficiently | |
| 59 | 059 |
BRF+: No Object IDs specified in object list &1 and persistence object &2 | The short text describes the object sufficiently | |
| 60 | 060 |
BRF+: Persistence object &2 - delete for &1 lines executed | The short text describes the object sufficiently | |
| 61 | 061 |
BRF+: &1 Object ID versions are already physically deleted in source | The short text describes the object sufficiently | |
| 62 | 062 |
BRF+: &1 Object ID versions have already been activated | The short text describes the object sufficiently | |
| 63 | 063 |
BRF+: &1 Object ID versions are unchanged to previous transports | The short text describes the object sufficiently | |
| 64 | 064 |
BRF+: &1 Object ID versions are local changes of same origin version | The short text describes the object sufficiently | |
| 65 | 065 |
BRF+: &1 Object ID versions will be changed by this transport | The short text describes the object sufficiently | |
| 66 | 066 |
BRF+: No Object IDs to be changed could be determined | The short text describes the object sufficiently | |
| 67 | 067 |
BRF+: &1 Customer object versions may not be overwritten by SAP versions | The short text describes the object sufficiently | |
| 68 | 068 |
BRF+: &1 Object IDs have to be newly deleted physically in the target | The short text describes the object sufficiently | |
| 69 | 069 |
BRF+: &1 Object IDs have to be newly deleted log. and phy. in the target | The short text describes the object sufficiently | |
| 70 | 070 |
BRF+: Executing check before start of physical deletion for &1 object IDs | The short text describes the object sufficiently | |
| 71 | 071 |
BRF+: Physical deletion started for &1 object IDs | The short text describes the object sufficiently | |
| 72 | 072 |
BRF+: Physical deletion successful for &1 object IDs | The short text describes the object sufficiently | |
| 73 | 073 |
BRF+: Activation of &1 object IDs was skipped due to errors (step &2) | The short text describes the object sufficiently | |
| 74 | 074 |
BRF+: Phys. deletion aborted: &2 logically undeleted entries in target &1 | The short text describes the object sufficiently | |
| 75 | 075 |
BRF+: Table &2 - Object ID version delete for &1 lines executed | The short text describes the object sufficiently | |
| 76 | 076 |
BRF+: Table &2 - Object ID delete for &1 lines executed | The short text describes the object sufficiently | |
| 77 | 077 |
BRF+: Object ID is not logically deleted in the target - table &1 | The short text describes the object sufficiently | |
| 78 | 078 |
BRF+: Object &1 is not updated due to customer changes | The short text describes the object sufficiently | |
| 79 | 079 |
BRF+: Application &1 will be deleted with all associated objects | The short text describes the object sufficiently | |
| 80 | 080 |
BRF+: Object is not deleted. See following messages | The short text describes the object sufficiently | |
| 81 | 081 |
Might be an authorization problem; check Hot Package / S_CTS_ADMIN | The short text describes the object sufficiently | |
| 82 | 082 |
BRF+: Logical undelete started for &1 Object IDs | The short text describes the object sufficiently | |
| 83 | 083 |
BRF+: Logical undelete successful for &1 Object IDs | The short text describes the object sufficiently | |
| 84 | 084 |
BRF+: Logical undelete failed | The short text describes the object sufficiently | |
| 85 | 085 |
BRF+: &1 object IDs do not exist or are not deleted logic. in the target | Space: object requires documentation | |
| 86 | 086 |
BRF+: &1 object IDs must be undeleted again in the target system | The short text describes the object sufficiently | |
| 87 | 087 |
BRF+: &1 object IDs do not exist, are deleted logical. or marked for del. | The short text describes the object sufficiently | |
| 88 | 088 |
BRF+: &1 object IDs do not exist or are already deleted logically | The short text describes the object sufficiently | |
| 89 | 089 |
BRF+: Table &1 must not be recorded on a BRFplus transport request | The short text describes the object sufficiently | |
| 90 | 090 |
No transport object defined for expression type &1 (table type &2) | The short text describes the object sufficiently | |
| 91 | 091 |
BRF+: Start of UNIX file transfer simulation to system &1 | The short text describes the object sufficiently | |
| 92 | 092 |
BRF+: End of UNIX file transfer simulation to system &1 | The short text describes the object sufficiently | |
| 93 | 093 |
BRF+: Logical undelete would be successful for &1 object IDs | The short text describes the object sufficiently | |
| 94 | 094 |
BRF+: Host: &1 | The short text describes the object sufficiently | |
| 95 | 095 |
Exception &2 raised - "&1" | The short text describes the object sufficiently | |
| 96 | 096 |
Source Program : &1 | The short text describes the object sufficiently | |
| 97 | 097 |
Source Include : &1 | The short text describes the object sufficiently | |
| 98 | 098 |
Source Line : &1 | The short text describes the object sufficiently | |
| 99 | 099 |
BRF+: Vers. mode 'transport' - &1 lines of persistence object &2 changed | The short text describes the object sufficiently | |
| 100 | 100 |
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> | The short text describes the object sufficiently | |
| 101 | 101 |
------------------------------------------------------------------------- | The short text describes the object sufficiently | |
| 102 | 102 |
ENQUEUE failed due to foreign lock | The short text describes the object sufficiently | |
| 103 | 103 |
ENQUEUE failed with exception | The short text describes the object sufficiently | |
| 104 | 105 |
Lock scope was set to client level | The short text describes the object sufficiently | |
| 105 | 107 |
&1 BRFplus content objects have been written to transport &2. | The short text describes the object sufficiently | |
| 106 | 108 |
BRF+: &1 object IDs have to be created newly as logically deleted | The short text describes the object sufficiently | |
| 107 | 110 |
BRF+: No table entries specified for transport &1 | The short text describes the object sufficiently | |
| 108 | 111 |
BRF+: Asynchronous physical deletion started for &1 object IDs | The short text describes the object sufficiently | |
| 109 | 112 |
BRF+: ID &1 does not exist or is not deleted logically in the target | The short text describes the object sufficiently | |
| 110 | 114 |
BRF+: &1 objects have been deleted logically | The short text describes the object sufficiently | |
| 111 | 115 |
BRF+: &1 objects have been marked for delete | The short text describes the object sufficiently | |
| 112 | 116 |
BRF+: &1 objects remained unchanged | The short text describes the object sufficiently | |
| 113 | 117 |
BRF+: &1 objects were processed with errors | The short text describes the object sufficiently | |
| 114 | 118 |
BRF+: For &1 objects mark for delete has been reversed | The short text describes the object sufficiently | |
| 115 | 119 |
BRF+: &1 is logically deleted | The short text describes the object sufficiently | |
| 116 | 120 |
BRF+: &1 is marked for deletion | The short text describes the object sufficiently | |
| 117 | 121 |
BRF+: &1 is physically deleted | The short text describes the object sufficiently | |
| 118 | 122 |
BRF+: A client copy only makes sense for BRFplus customizing objects | The short text describes the object sufficiently | |
| 119 | 125 |
BRF+: <<< *** BEGIN: Content from Application Component &1 *** >>> | The short text describes the object sufficiently | |
| 120 | 126 |
BRF+: <<< *** END : Content from Application Component &1 *** >>> | The short text describes the object sufficiently | |
| 121 | 128 |
BRF+: &1 unnamed unused objects have been physically deleted | The short text describes the object sufficiently | |
| 122 | 130 |
BRF+: &1 is recorded under transp. obj. &2 but not under &3; see longtext | Space: object requires documentation | |
| 123 | 131 |
BRF+: Messages from transport object FDT0 | The short text describes the object sufficiently | |
| 124 | 134 |
BRF+: Request &1 was skipped during merge determination | The short text describes the object sufficiently | |
| 125 | 135 |
BRF+: Use report FDT_DCONV_0012 to clean up the import queue | The short text describes the object sufficiently | |
| 126 | 136 |
BRF+: Restart of the import queue for table type &1 | The short text describes the object sufficiently | |
| 127 | 140 |
BRF+: Foreign lock &2. Could not get the processing lock for &1 objects | The short text describes the object sufficiently | |
| 128 | 141 |
BRF+: The processing lock could be obtained for all BRFplus objects (&1) | The short text describes the object sufficiently | |
| 129 | 143 |
BRF+: The lock scope for the processing lock was set to client level | The short text describes the object sufficiently | |
| 130 | 145 |
BRF+: Wrong version &1 for table &2 on piecelist. Version must be 000000. | The short text describes the object sufficiently | |
| 131 | 150 |
BRF+: Current transport, &1 , was activated via &2 with RC = &3 | The short text describes the object sufficiently | |
| 132 | 151 |
BRF+: Transport &1/&4 (RC &2) is merged to &3 for after import processing | The short text describes the object sufficiently | |
| 133 | 152 |
BRF+: Current transport, &1, is merged to no other transport | The short text describes the object sufficiently | |
| 134 | 153 |
BRF+: Import queue evaluation for table type &1 | The short text describes the object sufficiently | |
| 135 | 154 |
BRF+: Import queue update with RC &1 | The short text describes the object sufficiently | |
| 136 | 155 |
BRF+: No open requests found during queue restart for table type &1 | The short text describes the object sufficiently | |
| 137 | 156 |
BRF+: Could not access the message log in the memory | The short text describes the object sufficiently | |
| 138 | 157 |
BRF+: Could not delete the message log in the memory | The short text describes the object sufficiently | |
| 139 | 158 |
BRF+: Import queue restart for transport &1 and table type &2 succeeded | The short text describes the object sufficiently | |
| 140 | 159 |
BRF+: Import queue restart for transport &1 and table type &2 failed | The short text describes the object sufficiently | |
| 141 | 160 |
BRF+: Import queue could not be restarted due to foreign lock | The short text describes the object sufficiently | |
| 142 | 163 |
BRF+: Correct the piecelist with report FDT_TRANS_CORRECT_PIECELIST | The short text describes the object sufficiently | |
| 143 | 170 |
BRF+: Physical delete started for &1 packages | The short text describes the object sufficiently | |
| 144 | 171 |
BRF+: &1 IDs couldn't be locked | The short text describes the object sufficiently | |
| 145 | 172 |
BRF+: Physical delete started for &1 packages (versioned IDs) | The short text describes the object sufficiently | |
| 146 | 173 |
BRF+: Physical delete started for &1 versioned object IDs (table type &2) | The short text describes the object sufficiently | |
| 147 | 174 |
BRF+: Table &2 - Versioned Object ID delete for &1 lines executed | The short text describes the object sufficiently | |
| 148 | 178 |
No BRFplus transport object found in the piece list | Space: object requires documentation | |
| 149 | 179 |
An inconsistent transport piecelist was detected (Table type &1). | The short text describes the object sufficiently | |
| 150 | 180 |
Table '&1' on the piecelist is not registered for object type &2 | The short text describes the object sufficiently | |
| 151 | 181 |
Table '&1' is missing on the transport piecelist | The short text describes the object sufficiently | |
| 152 | 182 |
Piece list errors are output as warnings only (global user setting &1) | The short text describes the object sufficiently | |
| 153 | 183 |
Parts of the piecelist are recorded in E071K_STR instead of E071K | The short text describes the object sufficiently | |
| 154 | 200 |
Failed to write transport object entry for &1 (&2). | The short text describes the object sufficiently | |
| 155 | 201 |
Transport object entry with name &1 already exists for ID &2. | The short text describes the object sufficiently | |
| 156 | 202 |
Transport object entry for ID &1 not found. | Space: object requires documentation | |
| 157 | 250 |
BRF+: System ID &1 is already locked for deletion (no SM12, DB lock used) | The short text describes the object sufficiently | |
| 158 | 251 |
BRF+: System ID &1 is already protected by shared lock for import | The short text describes the object sufficiently | |
| 159 | 252 |
BRF+: System ID &1 does not exist | The short text describes the object sufficiently | |
| 160 | 253 |
BRF+: System ID &1 was not locked | Space: object requires documentation | |
| 161 | 255 |
BRF+: Object ID &1 is not mapped in virtual system &2 | The short text describes the object sufficiently | |
| 162 | 256 |
BRF+: Attempt to tear down the real (non-virtual) system &1 failed | The short text describes the object sufficiently | |
| 163 | 300 |
BRF+: &1 started for &2 object IDs | The short text describes the object sufficiently | |
| 164 | 301 |
BRF+: &1 successful for &2 object IDs | The short text describes the object sufficiently | |
| 165 | 302 |
BRF+: &1 failed | The short text describes the object sufficiently | |
| 166 | 304 |
BRF+: Hard logical delete started for &1 object IDs | The short text describes the object sufficiently | |
| 167 | 305 |
BRF+: Hard logical delete successful for &1 object IDs | The short text describes the object sufficiently | |
| 168 | 306 |
BRF+: Hard logical delete failed | The short text describes the object sufficiently | |
| 169 | 310 |
BRF+: Discard versions started for &1 object IDs | The short text describes the object sufficiently | |
| 170 | 311 |
BRF+: Versions discarded successfully for &1 object IDs | The short text describes the object sufficiently | |
| 171 | 312 |
BRF+: Discarding of versions failed | The short text describes the object sufficiently | |
| 172 | 313 |
BRF+: &1 objects were already discarded with a higher timestamp | The short text describes the object sufficiently | |
| 173 | 314 |
BRF+: &1 objects were already deleted logically or physically | The short text describes the object sufficiently | |
| 174 | 315 |
BRF+: &1 objects have no active version for given timestamp &2 | The short text describes the object sufficiently | |
| 175 | 721 |
BRF+: Wrong suffix set &1 for the emergency transport attribute - use &2 | The short text describes the object sufficiently | |
| 176 | 722 |
BRF+: The emergency transport attribute was set for the current transport | The short text describes the object sufficiently | |
| 177 | 723 |
BRF+: &1 object IDs were released despite before export errors | The short text describes the object sufficiently | |
| 178 | 724 |
BRF+: Before export problems for table type &1 | The short text describes the object sufficiently | |
| 179 | 725 |
BRF+: Before export problems for table type &1 could be solved | The short text describes the object sufficiently | |
| 180 | 726 |
BRF+: The emergency transport attribute was set for &1 and table type &2 | The short text describes the object sufficiently | |
| 181 | 727 |
BRF+: Setting the emergency transport attribute was not necessary | The short text describes the object sufficiently | |
| 182 | 728 |
BRF+: Objects on &1 (table type &2) still have before export problems | The short text describes the object sufficiently | |
| 183 | 729 |
BRF+: Objects on &1 (table type &2) have no more before export problems | The short text describes the object sufficiently | |
| 184 | 730 |
BRF+: No still faulty transports with emergency transport attribute found | The short text describes the object sufficiently | |
| 185 | 731 |
BRF+: Recalculation of &1 transports with emergency transport attribute | The short text describes the object sufficiently | |
| 186 | 732 |
&1 is no SAP inhouse merge request | The short text describes the object sufficiently | |
| 187 | 733 |
BRF+: Inactive version deleted for &1 objects, that are marked for delete | The short text describes the object sufficiently | |
| 188 | 734 |
BRF+: &1 objects are marked for delete | The short text describes the object sufficiently | |
| 189 | 735 |
BRF+: &1 objects are logically deleted | The short text describes the object sufficiently | |
| 190 | 800 |
No request supplied | The short text describes the object sufficiently | |
| 191 | 801 |
Request &1 does not exist | The short text describes the object sufficiently | |
| 192 | 802 |
Request &1 is closed | The short text describes the object sufficiently | |
| 193 | 803 |
Request &1 is still open | The short text describes the object sufficiently | |
| 194 | 804 |
Request &1 is persistent | The short text describes the object sufficiently | |
| 195 | 805 |
Request &1 is not persistent | The short text describes the object sufficiently | |
| 196 | 806 |
Request &1 is a workbench request | The short text describes the object sufficiently | |
| 197 | 807 |
Request &1 is a customizing request | The short text describes the object sufficiently | |
| 198 | 850 |
The data count for the previous step of the measurement is missing | The short text describes the object sufficiently | |
| 199 | 851 |
The data count for the last step of the measurement is missing | The short text describes the object sufficiently |
History
| Last changed on/by | |
20141121 | SAP |
| SAP Release Created in | 710 |
