Message Number list used by SAP ABAP Class CL_FDT_TRANS_DB (FDT: Version Copy between DB Tables)
SAP ABAP Class CL_FDT_TRANS_DB (FDT: Version Copy between DB Tables) is using
# Object Type Object Name Object Description Note
     
1 Message Number  FDT_TRANSPORT - 088 BRF+: &1 object IDs do not exist or are already deleted logically
2 Message Number  FDT_TRANSPORT - 141 BRF+: The processing lock could be obtained for all BRFplus objects (&1)
3 Message Number  FDT_TRANSPORT - 140 BRF+: Foreign lock &2. Could not get the processing lock for &1 objects
4 Message Number  FDT_TRANSPORT - 128 BRF+: &1 unnamed unused objects have been physically deleted
5 Message Number  FDT_TRANSPORT - 112 BRF+: ID &1 does not exist or is not deleted logically in the target
6 Message Number  FDT_TRANSPORT - 110 BRF+: No table entries specified for transport &1
7 Message Number  FDT_TRANSPORT - 105 Lock scope was set to client level
8 Message Number  FDT_TRANSPORT - 099 BRF+: Vers. mode 'transport' - &1 lines of persistence object &2 changed
9 Message Number  FDT_TRANSPORT - 094 BRF+: Host: &1
10 Message Number  FDT_TRANSPORT - 093 BRF+: Logical undelete would be successful for &1 object IDs
11 Message Number  FDT_TRANSPORT - 143 BRF+: The lock scope for the processing lock was set to client level
12 Message Number  FDT_TRANSPORT - 088 BRF+: &1 object IDs do not exist or are already deleted logically
13 Message Number  FDT_TRANSPORT - 086 BRF+: &1 object IDs must be undeleted again in the target system
14 Message Number  FDT_TRANSPORT - 085 BRF+: &1 object IDs do not exist or are not deleted logic. in the target
15 Message Number  FDT_TRANSPORT - 084 BRF+: Logical undelete failed
16 Message Number  FDT_TRANSPORT - 083 BRF+: Logical undelete successful for &1 Object IDs
17 Message Number  FDT_TRANSPORT - 082 BRF+: Logical undelete started for &1 Object IDs
18 Message Number  FDT_TRANSPORT - 078 BRF+: Object &1 is not updated due to customer changes
19 Message Number  FDT_TRANSPORT - 077 BRF+: Object ID is not logically deleted in the target - table &1
20 Message Number  FDT_TRANSPORT - 300 BRF+: &1 started for &2 object IDs
21 Message Number  FDT_TRANSPORT - 735 BRF+: &1 objects are logically deleted
22 Message Number  FDT_TRANSPORT - 734 BRF+: &1 objects are marked for delete
23 Message Number  FDT_TRANSPORT - 733 BRF+: Inactive version deleted for &1 objects, that are marked for delete
24 Message Number  FDT_TRANSPORT - 722 BRF+: The emergency transport attribute was set for the current transport
25 Message Number  FDT_TRANSPORT - 306 BRF+: Hard logical delete failed
26 Message Number  FDT_TRANSPORT - 305 BRF+: Hard logical delete successful for &1 object IDs
27 Message Number  FDT_TRANSPORT - 304 BRF+: Hard logical delete started for &1 object IDs
28 Message Number  FDT_TRANSPORT - 302 BRF+: &1 failed
29 Message Number  FDT_TRANSPORT - 301 BRF+: &1 successful for &2 object IDs
30 Message Number  FDT_TRANSPORT - 076 BRF+: Table &2 - Object ID delete for &1 lines executed
31 Message Number  FDT_TRANSPORT - 182 Piece list errors are output as warnings only (global user setting &1)
32 Message Number  FDT_TRANSPORT - 181 Table '&1' is missing on the transport piecelist
33 Message Number  FDT_TRANSPORT - 180 Table '&1' on the piecelist is not registered for object type &2
34 Message Number  FDT_TRANSPORT - 179 An inconsistent transport piecelist was detected (Table type &1).
35 Message Number  FDT_TRANSPORT - 171 BRF+: &1 IDs couldn't be locked
36 Message Number  FDT_TRANSPORT - 170 BRF+: Physical delete started for &1 packages
37 Message Number  FDT_TRANSPORT - 163 BRF+: Correct the piecelist with report FDT_TRANS_CORRECT_PIECELIST
38 Message Number  FDT_TRANSPORT - 145 BRF+: Wrong version &1 for table &2 on piecelist. Version must be 000000.
39 Message Number  FDT_TRANSPORT - 023 BRF+: Only test mode: No database changes
40 Message Number  FDT_TRANSPORT - 050 BRF+: DB copy is started for &1 object IDs ( &2 -> &3 )
41 Message Number  FDT_TRANSPORT - 049 BRF+: Object list: &1
42 Message Number  FDT_TRANSPORT - 048 BRF+: Time stamp: &1
43 Message Number  FDT_TRANSPORT - 047 BRF+: Physical delete started for &1 object IDs (table type &2)
44 Message Number  FDT_TRANSPORT - 040 BRF+: Data changes committed
45 Message Number  FDT_TRANSPORT - 040 BRF+: Data changes committed
46 Message Number  FDT_TRANSPORT - 040 BRF+: Data changes committed
47 Message Number  FDT_TRANSPORT - 040 BRF+: Data changes committed
48 Message Number  FDT_TRANSPORT - 023 BRF+: Only test mode: No database changes
49 Message Number  FDT_TRANSPORT - 051 BRF+: Persistence object &3 - version copy for &1 ( &2 ) lines executed
50 Message Number  FDT_TRANSPORT - 023 BRF+: Only test mode: No database changes
51 Message Number  FDT_TRANSPORT - 023 BRF+: Only test mode: No database changes
52 Message Number  FDT_TRANSPORT - 019 BRF+: Object &1 (&2) has no source version
53 Message Number  FDT_TRANSPORT - 015 BRF+: Foreign lock &3.&1/&2 FDT source/target objects could not be locked
54 Message Number  FDT_TRANSPORT - 015 BRF+: Foreign lock &3.&1/&2 FDT source/target objects could not be locked
55 Message Number  FDT_TRANSPORT - 014 BRF+: Runtime client: &1 / target client: &2
56 Message Number  FDT_TRANSPORT - 013 BRF+: All BRFplus objects (&1) could be locked successfully
57 Message Number  FDT_TRANSPORT - 013 BRF+: All BRFplus objects (&1) could be locked successfully
58 Message Number  FDT_TRANSPORT - 060 BRF+: Persistence object &2 - delete for &1 lines executed
59 Message Number  FDT_TRANSPORT - 074 BRF+: Phys. deletion aborted: &2 logically undeleted entries in target &1
60 Message Number  FDT_TRANSPORT - 070 BRF+: Executing check before start of physical deletion for &1 object IDs
61 Message Number  FDT_TRANSPORT - 069 BRF+: &1 Object IDs have to be newly deleted log. and phy. in the target
62 Message Number  FDT_TRANSPORT - 067 BRF+: &1 Customer object versions may not be overwritten by SAP versions
63 Message Number  FDT_TRANSPORT - 065 BRF+: &1 Object ID versions will be changed by this transport
64 Message Number  FDT_TRANSPORT - 064 BRF+: &1 Object ID versions are local changes of same origin version
65 Message Number  FDT_TRANSPORT - 063 BRF+: &1 Object ID versions are unchanged to previous transports
66 Message Number  FDT_TRANSPORT - 062 BRF+: &1 Object ID versions have already been activated
67 Message Number  FDT_TRANSPORT - 061 BRF+: &1 Object ID versions are already physically deleted in source
68 Message Number  FDT_TRANSPORT - 010 BRF+: &1 objects with no active version were specified in the object list
69 Message Number  FDT_TRANSPORT - 059 BRF+: No Object IDs specified in object list &1 and persistence object &2
70 Message Number  FDT_TRANSPORT - 058 BRF+: &1 Object IDs skipped: Already deleted logical in target and source
71 Message Number  FDT_TRANSPORT - 057 BRF+: &1 Object IDs will be processed in the target
72 Message Number  FDT_TRANSPORT - 056 BRF+: &1 Object IDs have to be newly deleted logically in the target
73 Message Number  FDT_TRANSPORT - 055 BRF+: &1 Object IDs have to be newly created in the target
74 Message Number  FDT_TRANSPORT - 054 BRF+: &1 lines of persistence object &2 changed
75 Message Number  FDT_TRANSPORT - 053 BRF+: Copy and activation already executed for all object ID versions
76 Message Number  FDT_TRANSPORT - 052 BRF+: Copy for &1 ( &2 ) lines of persistence object &3 executed