FDT_TRANSPORT - Formula & Derivation Tool: Transport
The following messages are stored in message class FDT_TRANSPORT: Formula & Derivation Tool: Transport.
It is part of development package SFDT_TRANSPORT in software component BC-SRV-BR. This development package consists of objects that can be grouped under "BRFplus: Transport".
It is part of development package SFDT_TRANSPORT in software component BC-SRV-BR. This development package consists of objects that can be grouped under "BRFplus: Transport".
Message Nr ▲ | Message Text |
|---|---|
| 000 | BRF+: Program failed with exception &1 |
| 001 | BRF+: Invalid Table Type &1 |
| 002 | BRF+: Expression Type ID &1 does not exist |
| 003 | BRF+: Table Type &1 not supported for Expression Type &2 |
| 004 | |
| 006 | BRF+: Request Type &1 is not within the allowed virtual request types &2 |
| 007 | BRF+: Formal consistency check of transport list was successful |
| 008 | BRF+: Incomplete transport list. The following objects are missing |
| 009 | BRF+: Directly or indirectly referenced object &1 was never transported |
| 010 | BRF+: &1 objects with no active version were specified in the object list |
| 011 | BRF+: Unable to read full transport request &1. See preceeding message |
| 012 | BRF+: Object can only be marked for deletion; see following messages |
| 013 | BRF+: All BRFplus objects (&1) could be locked successfully |
| 014 | BRF+: Runtime client: &1 / target client: &2 |
| 015 | BRF+: Foreign lock &3.&1/&2 FDT source/target objects could not be locked |
| 016 | BRF+: Invalid request type &1 |
| 017 | &1 is not a valid database table |
| 018 | Illegal method call; IS_VALUE is not compatible with IV_TABNAME |
| 019 | BRF+: Object &1 (&2) has no source version |
| 020 | Discard version timestamp &1 must not be greater than current timestamp |
| 021 | BRF+: &2 started for &1 object IDs |
| 022 | BRF+: &2 successful for &1 object IDs |
| 023 | BRF+: Only test mode: No database changes |
| 024 | BRF+: &2 failed (step: &1) |
| 025 | BRF+: <<< BEGIN: Messages for IDs (&2/&3) &1 >>> |
| 026 | BRF+: <<< END : Messages for IDs (&2/&3) &1 >>> |
| 027 | BRF+: After Import failed with exception &1 |
| 028 | BRF+: Before Export failed with exception &1 |
| 029 | BRF+: After Import failed with uncaught exception &1 |
| 030 | BRF+: Before Export failed with uncaught exception &1 |
| 031 | BRF+: Object activation of new version started for &1 object IDs |
| 032 | BRF+: Object activation of new version successful for &1 object IDs |
| 033 | BRF+: Exception Text: '&1' |
| 034 | BRF+: Object activation failed (step: &1 ) |
| 035 | BRF+: Object check started for &1 (deep: &2) object IDs |
| 036 | BRF+: Object has inactive version; activate before transport; s. longtext |
| 037 | BRF+: Object check failed for &1 object IDs |
| 038 | BRF+: Object check successful for &1 object IDs |
| 039 | BRF+: Object changed after write to transport; see long text (SE91) |
| 040 | BRF+: Data changes committed |
| 041 | BRF+: Data changes rolled back |
| 042 | Get inactive transports |
| 043 | Get all inactive transports |
| 044 | BRF+: Physical delete for &1 object IDs was successful |
| 045 | BRF+: Physical delete failed with exception |
| 046 | BRF+: &1 object IDs were already deleted physically |
| 047 | BRF+: Physical delete started for &1 object IDs (table type &2) |
| 048 | BRF+: Time stamp: &1 |
| 049 | BRF+: Object list: &1 |
| 050 | BRF+: DB copy is started for &1 object IDs ( &2 -> &3 ) |
| 051 | BRF+: Persistence object &3 - version copy for &1 ( &2 ) lines executed |
| 052 | BRF+: Copy for &1 ( &2 ) lines of persistence object &3 executed |
| 053 | BRF+: Copy and activation already executed for all object ID versions |
| 054 | BRF+: &1 lines of persistence object &2 changed |
| 055 | BRF+: &1 Object IDs have to be newly created in the target |
| 056 | BRF+: &1 Object IDs have to be newly deleted logically in the target |
| 057 | BRF+: &1 Object IDs will be processed in the target |
| 058 | BRF+: &1 Object IDs skipped: Already deleted logical in target and source |
| 059 | BRF+: No Object IDs specified in object list &1 and persistence object &2 |
| 060 | BRF+: Persistence object &2 - delete for &1 lines executed |
| 061 | BRF+: &1 Object ID versions are already physically deleted in source |
| 062 | BRF+: &1 Object ID versions have already been activated |
| 063 | BRF+: &1 Object ID versions are unchanged to previous transports |
| 064 | BRF+: &1 Object ID versions are local changes of same origin version |
| 065 | BRF+: &1 Object ID versions will be changed by this transport |
| 066 | BRF+: No Object IDs to be changed could be determined |
| 067 | BRF+: &1 Customer object versions may not be overwritten by SAP versions |
| 068 | BRF+: &1 Object IDs have to be newly deleted physically in the target |
| 069 | BRF+: &1 Object IDs have to be newly deleted log. and phy. in the target |
| 070 | BRF+: Executing check before start of physical deletion for &1 object IDs |
| 071 | BRF+: Physical deletion started for &1 object IDs |
| 072 | BRF+: Physical deletion successful for &1 object IDs |
| 073 | BRF+: Activation of &1 object IDs was skipped due to errors (step &2) |
| 074 | BRF+: Phys. deletion aborted: &2 logically undeleted entries in target &1 |
| 075 | BRF+: Table &2 - Object ID version delete for &1 lines executed |
| 076 | BRF+: Table &2 - Object ID delete for &1 lines executed |
| 077 | BRF+: Object ID is not logically deleted in the target - table &1 |
| 078 | BRF+: Object &1 is not updated due to customer changes |
| 079 | BRF+: Application &1 will be deleted with all associated objects |
| 080 | BRF+: Object is not deleted. See following messages |
| 081 | Might be an authorization problem; check Hot Package / S_CTS_ADMIN |
| 082 | BRF+: Logical undelete started for &1 Object IDs |
| 083 | BRF+: Logical undelete successful for &1 Object IDs |
| 084 | BRF+: Logical undelete failed |
| 085 | BRF+: &1 object IDs do not exist or are not deleted logic. in the target |
| 086 | BRF+: &1 object IDs must be undeleted again in the target system |
| 087 | BRF+: &1 object IDs do not exist, are deleted logical. or marked for del. |
| 088 | BRF+: &1 object IDs do not exist or are already deleted logically |
| 089 | BRF+: Table &1 must not be recorded on a BRFplus transport request |
| 090 | No transport object defined for expression type &1 (table type &2) |
| 091 | BRF+: Start of UNIX file transfer simulation to system &1 |
| 092 | BRF+: End of UNIX file transfer simulation to system &1 |
| 093 | BRF+: Logical undelete would be successful for &1 object IDs |
| 094 | BRF+: Host: &1 |
| 095 | Exception &2 raised - "&1" |
| 096 | Source Program : &1 |
| 097 | Source Include : &1 |
| 098 | Source Line : &1 |
| 099 | BRF+: Vers. mode 'transport' - &1 lines of persistence object &2 changed |
| 100 | >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> |
| 101 | ------------------------------------------------------------------------- |
| 102 | ENQUEUE failed due to foreign lock |
| 103 | ENQUEUE failed with exception |
| 105 | Lock scope was set to client level |
| 107 | &1 BRFplus content objects have been written to transport &2. |
| 108 | BRF+: &1 object IDs have to be created newly as logically deleted |
| 110 | BRF+: No table entries specified for transport &1 |
| 111 | BRF+: Asynchronous physical deletion started for &1 object IDs |
| 112 | BRF+: ID &1 does not exist or is not deleted logically in the target |
| 114 | BRF+: &1 objects have been deleted logically |
| 115 | BRF+: &1 objects have been marked for delete |
| 116 | BRF+: &1 objects remained unchanged |
| 117 | BRF+: &1 objects were processed with errors |
| 118 | BRF+: For &1 objects mark for delete has been reversed |
| 119 | BRF+: &1 is logically deleted |
| 120 | BRF+: &1 is marked for deletion |
| 121 | BRF+: &1 is physically deleted |
| 122 | BRF+: A client copy only makes sense for BRFplus customizing objects |
| 125 | BRF+: <<< *** BEGIN: Content from Application Component &1 *** >>> |
| 126 | BRF+: <<< *** END : Content from Application Component &1 *** >>> |
| 128 | BRF+: &1 unnamed unused objects have been physically deleted |
| 130 | BRF+: &1 is recorded under transp. obj. &2 but not under &3; see longtext |
| 131 | BRF+: Messages from transport object FDT0 |
| 134 | BRF+: Request &1 was skipped during merge determination |
| 135 | BRF+: Use report FDT_DCONV_0012 to clean up the import queue |
| 136 | BRF+: Restart of the import queue for table type &1 |
| 140 | BRF+: Foreign lock &2. Could not get the processing lock for &1 objects |
| 141 | BRF+: The processing lock could be obtained for all BRFplus objects (&1) |
| 143 | BRF+: The lock scope for the processing lock was set to client level |
| 145 | BRF+: Wrong version &1 for table &2 on piecelist. Version must be 000000. |
| 150 | BRF+: Current transport, &1 , was activated via &2 with RC = &3 |
| 151 | BRF+: Transport &1/&4 (RC &2) is merged to &3 for after import processing |
| 152 | BRF+: Current transport, &1, is merged to no other transport |
| 153 | BRF+: Import queue evaluation for table type &1 |
| 154 | BRF+: Import queue update with RC &1 |
| 155 | BRF+: No open requests found during queue restart for table type &1 |
| 156 | BRF+: Could not access the message log in the memory |
| 157 | BRF+: Could not delete the message log in the memory |
| 158 | BRF+: Import queue restart for transport &1 and table type &2 succeeded |
| 159 | BRF+: Import queue restart for transport &1 and table type &2 failed |
| 160 | BRF+: Import queue could not be restarted due to foreign lock |
| 163 | BRF+: Correct the piecelist with report FDT_TRANS_CORRECT_PIECELIST |
| 170 | BRF+: Physical delete started for &1 packages |
| 171 | BRF+: &1 IDs couldn't be locked |
| 172 | BRF+: Physical delete started for &1 packages (versioned IDs) |
| 173 | BRF+: Physical delete started for &1 versioned object IDs (table type &2) |
| 174 | BRF+: Table &2 - Versioned Object ID delete for &1 lines executed |
| 178 | No BRFplus transport object found in the piece list |
| 179 | An inconsistent transport piecelist was detected (Table type &1). |
| 180 | Table '&1' on the piecelist is not registered for object type &2 |
| 181 | Table '&1' is missing on the transport piecelist |
| 182 | Piece list errors are output as warnings only (global user setting &1) |
| 183 | Parts of the piecelist are recorded in E071K_STR instead of E071K |
| 200 | Failed to write transport object entry for &1 (&2). |
| 201 | Transport object entry with name &1 already exists for ID &2. |
| 202 | Transport object entry for ID &1 not found. |
| 250 | BRF+: System ID &1 is already locked for deletion (no SM12, DB lock used) |
| 251 | BRF+: System ID &1 is already protected by shared lock for import |
| 252 | BRF+: System ID &1 does not exist |
| 253 | BRF+: System ID &1 was not locked |
| 255 | BRF+: Object ID &1 is not mapped in virtual system &2 |
| 256 | BRF+: Attempt to tear down the real (non-virtual) system &1 failed |
| 300 | BRF+: &1 started for &2 object IDs |
| 301 | BRF+: &1 successful for &2 object IDs |
| 302 | BRF+: &1 failed |
| 304 | BRF+: Hard logical delete started for &1 object IDs |
| 305 | BRF+: Hard logical delete successful for &1 object IDs |
| 306 | BRF+: Hard logical delete failed |
| 307 | Cust. objects can be written to workb. transports in change mode only |
| 310 | BRF+: Discard versions started for &1 object IDs |
| 311 | BRF+: Versions discarded successfully for &1 object IDs |
| 312 | BRF+: Discarding of versions failed |
| 313 | BRF+: &1 objects were already discarded with a higher timestamp |
| 314 | BRF+: &1 objects were already deleted logically or physically |
| 315 | BRF+: &1 objects have no active version for given timestamp &2 |
| 721 | BRF+: Wrong suffix set &1 for the emergency transport attribute - use &2 |
| 722 | BRF+: The emergency transport attribute was set for the current transport |
| 723 | BRF+: &1 object IDs were released despite before export errors |
| 724 | BRF+: Before export problems for table type &1 |
| 725 | BRF+: Before export problems for table type &1 could be solved |
| 726 | BRF+: The emergency transport attribute was set for &1 and table type &2 |
| 727 | BRF+: Setting the emergency transport attribute was not necessary |
| 728 | BRF+: Objects on &1 (table type &2) still have before export problems |
| 729 | BRF+: Objects on &1 (table type &2) have no more before export problems |
| 730 | BRF+: No still faulty transports with emergency transport attribute found |
| 731 | BRF+: Recalculation of &1 transports with emergency transport attribute |
| 732 | &1 is no SAP inhouse merge request |
| 733 | BRF+: Inactive version deleted for &1 objects, that are marked for delete |
| 734 | BRF+: &1 objects are marked for delete |
| 735 | BRF+: &1 objects are logically deleted |
| 800 | No request supplied |
| 801 | Request &1 does not exist |
| 802 | Request &1 is closed |
| 803 | Request &1 is still open |
| 804 | Request &1 is persistent |
| 805 | Request &1 is not persistent |
| 806 | Request &1 is a workbench request |
| 807 | Request &1 is a customizing request |
| 850 | The data count for the previous step of the measurement is missing |
| 851 | The data count for the last step of the measurement is missing |