SAP ABAP Message Class MEREP_01 (Runtime Messages for Synchronizers)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-MOB (Application Component) SAP NetWeaver Mobile - Use subcomponents
⤷ S_ME_DATA (Package) Mobile: data replication
⤷ BC-MOB (Application Component) SAP NetWeaver Mobile - Use subcomponents
⤷ S_ME_DATA (Package) Mobile: data replication
Attributes
Message class | MEREP_01 | |
Short Description | Runtime Messages for Synchronizers | |
Changed On | 20060912 | |
Last Changed At | 114217 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | There are no records to download | The short text describes the object sufficiently | |
2 | 001 | Number range error: Interval not found (object=&1, range=&2) | The short text describes the object sufficiently | |
3 | 002 | Number range error: Number range not intern (object=&1, range=&2) | The short text describes the object sufficiently | |
4 | 003 | Number range error: Object not found (object=&1, range=&2) | The short text describes the object sufficiently | |
5 | 004 | Number range error: Interval overflow (object=&1, range=&2) | The short text describes the object sufficiently | |
6 | 005 | Number range error: Unspecified error (object=&1, range=&2) | The short text describes the object sufficiently | |
7 | 006 | Number range: Next &1 assigned successfully (object=&2, range=&3) | The short text describes the object sufficiently | |
8 | 007 | Replicator ended successfully (SyncBO=&1) | The short text describes the object sufficiently | |
9 | 008 | Error updating replica DB for download (SyncBO=&1, Mobile ID=&2) | The short text describes the object sufficiently | |
10 | 009 | & record not found | The short text describes the object sufficiently | |
11 | 010 | & record not enabled | The short text describes the object sufficiently | |
12 | 011 | Error converting MSG_HDR to HSC (reason=&1) | The short text describes the object sufficiently | |
13 | 012 | MSG_HDR GUID does not match device header GUID | The short text describes the object sufficiently | |
14 | 013 | Device-sequence number missing | The short text describes the object sufficiently | |
15 | 014 | Message data record length exceeds 2048 bytes | The short text describes the object sufficiently | |
16 | 015 | & is empty | The short text describes the object sufficiently | |
17 | 016 | Incoming message data does not begin with an HSC record | The short text describes the object sufficiently | |
18 | 017 | Default value missing (value ID=&1, depends on=&2, exclusive=&3) | The short text describes the object sufficiently | |
19 | 018 | Default values loaded | The short text describes the object sufficiently | |
20 | 019 | Default values loaded successfully (SyncBO=&1, #=&2) | The short text describes the object sufficiently | |
21 | 020 | Error loading default values | The short text describes the object sufficiently | |
22 | 021 | Reading headers and items from replica database | The short text describes the object sufficiently | |
23 | 022 | Metadata reading was successful (SyncBO=&1, #=&2) | The short text describes the object sufficiently | |
24 | 023 | Error reading metadata (SyncBO=&1) | The short text describes the object sufficiently | |
25 | 024 | Header action &1 initialized | The short text describes the object sufficiently | |
26 | 025 | Retrieving internal table of RDB header (header key=&1, #=&2) | The short text describes the object sufficiently | |
27 | 026 | Retrieve item from internal table for RDB item (sync key=&1, #=&2) | The short text describes the object sufficiently | |
28 | 027 | Header exists in RDB already (R/3 header key=&1) | The short text describes the object sufficiently | |
29 | 028 | Inserting header in RDB (R/3 header key=&1) | The short text describes the object sufficiently | |
30 | 029 | Item exists in RDB already (parent synchronization key=&1, R/3 key=&2) | The short text describes the object sufficiently | |
31 | 030 | Inserting item in RDB (parent synchronization key=&1, R/3 key=&2) | The short text describes the object sufficiently | |
32 | 031 | Match found for item: ldata=&1&2&3&4 | The short text describes the object sufficiently | |
33 | 032 | No match found for item: ldata=&1&2&3&4 | The short text describes the object sufficiently | |
34 | 033 | Deleting R/3 item from internal RDB table: ldata=&1&2&3&4 | The short text describes the object sufficiently | |
35 | 034 | Deleting RDB header from internal RDB table: Sync key=&1, ldata=&2&3&4 | The short text describes the object sufficiently | |
36 | 035 | Item deleted from internal RDB table | The short text describes the object sufficiently | |
37 | 036 | Deleting RDB item from internal RDB table: Sync key=&1, R/3 key=&2 | The short text describes the object sufficiently | |
38 | 037 | Setting header action "ADD" | The short text describes the object sufficiently | |
39 | 038 | Setting header action "MOD" | The short text describes the object sufficiently | |
40 | 039 | Obtaining new synchronization key for header | The short text describes the object sufficiently | |
41 | 040 | Obtaining new synchronization key for item | The short text describes the object sufficiently | |
42 | 041 | New sync key for header obtained successufully (object=&1, sync key=&2) | The short text describes the object sufficiently | |
43 | 042 | Error occurred when obtaining new sync key for header (object=&1) | The short text describes the object sufficiently | |
44 | 043 | Error occurred when obtaining new sync key for item (object=&1) | The short text describes the object sufficiently | |
45 | 044 | New sync key for item obtained successfully (object=&1, sync key=&2) | The short text describes the object sufficiently | |
46 | 045 | Setting item time stamp for first creation (date=&1, time=&2 ) | The short text describes the object sufficiently | |
47 | 046 | Setting item time stamp for last update (date=&1, time=&2 ) | The short text describes the object sufficiently | |
48 | 047 | Setting header time stamp for first creation (date=&1, time=&2 ) | The short text describes the object sufficiently | |
49 | 048 | Setting header time stamp for last update (date=&1, time=&2 ) | The short text describes the object sufficiently | |
50 | 049 | Appending a record to internal table: Sync key=&1, R/3 key=&2 | The short text describes the object sufficiently | |
51 | 050 | Creating RDB item record with action "ADD" | The short text describes the object sufficiently | |
52 | 051 | Creating RDB item record with action "DEL" | The short text describes the object sufficiently | |
53 | 052 | Header action = &1 | The short text describes the object sufficiently | |
54 | 053 | Header action = "ADD" | The short text describes the object sufficiently | |
55 | 054 | Header action = "DEL" | The short text describes the object sufficiently | |
56 | 055 | Preparing action "ADD" for RDB header record | The short text describes the object sufficiently | |
57 | 056 | Preparing action "MOD" for RDB header record | The short text describes the object sufficiently | |
58 | 057 | Preparing RDB header (send mask=&1, R/3 key=&2) | The short text describes the object sufficiently | |
59 | 058 | Creating RDB item record with action "MOD" | The short text describes the object sufficiently | |
60 | 059 | Creating RDB item record with action "DEL" | The short text describes the object sufficiently | |
61 | 060 | DB operation "Recover" or "Clear" detected;SyncBO=&1, mobile ID=&2, OP=&3 | The short text describes the object sufficiently | |
62 | 061 | Initializing last download date for this device | The short text describes the object sufficiently | |
63 | 062 | Last download date initialized succesfully (SyncBO=&1, mobile ID=&2) | The short text describes the object sufficiently | |
64 | 063 | First connection for device &1 with SyncBO &2 | The short text describes the object sufficiently | |
65 | 064 | DB operation = "Clear" | The short text describes the object sufficiently | |
66 | 065 | Load filtering conditions (mobile group=&, mobile ID=&, struct ID=&, #=&) | The short text describes the object sufficiently | |
67 | 066 | Sel. criteria loaded (mobile group=&, mobile ID=&, structure ID=&, #=&) | The short text describes the object sufficiently | |
68 | 067 | Error loading selection criteria (mobile grp.=&, mobile ID=&, structID=&) | The short text describes the object sufficiently | |
69 | 068 | Download log found (SyncBO=&1, mobile ID=&2, date=&3, time=&4) | The short text describes the object sufficiently | |
70 | 069 | Download log not found; first connection for device &1 with SyncBO &2 | The short text describes the object sufficiently | |
71 | 070 | Get no. of headers from RDB for & using filter cond. (date=&, time=&) | The short text describes the object sufficiently | |
72 | 071 | No changes made for device &1, SyncBO &2 since date=&3/time=&4 | The short text describes the object sufficiently | |
73 | 072 | Setting download header action "ADD" | The short text describes the object sufficiently | |
74 | 073 | Record not on device | The short text describes the object sufficiently | |
75 | 074 | Last download: Date=&1/time=&2, first create: Date=&3/time=&4 | The short text describes the object sufficiently | |
76 | 075 | Setting action "MOD" for download header | The short text describes the object sufficiently | |
77 | 076 | Setting action "DEL" for download header | The short text describes the object sufficiently | |
78 | 077 | Header record format converted successfully to external format: &1&2&3&4 | The short text describes the object sufficiently | |
79 | 078 | Appending header to outbox no.&1 (sync key=&2, R/3key=&3, update act.=&4) | The short text describes the object sufficiently | |
80 | 079 | Error converting record format to external format: &1&2&3&4 | The short text describes the object sufficiently | |
81 | 080 | Item found | The short text describes the object sufficiently | |
82 | 081 | Header action for download = "ADD" | The short text describes the object sufficiently | |
83 | 082 | Header action for download = "MOD" | The short text describes the object sufficiently | |
84 | 083 | Header action for download = "DEL" | The short text describes the object sufficiently | |
85 | 084 | Download item action has been set to "ADD" | The short text describes the object sufficiently | |
86 | 085 | Download item action has been set to "MOD" | The short text describes the object sufficiently | |
87 | 086 | Download item action has been set to "DEL" | The short text describes the object sufficiently | |
88 | 087 | Item record format converted successfully to external format : &1&2&3&4 | The short text describes the object sufficiently | |
89 | 088 | Item record format convert to external format failed : &1&2&3&4 | The short text describes the object sufficiently | |
90 | 089 | Appending item to outbox no.&1 (sync key=&2, R/3 key=&3, update act.=&4) | The short text describes the object sufficiently | |
91 | 090 | Updating download log (SyncBO=&1, device=&2, date=&3, time=&4) | The short text describes the object sufficiently | |
92 | 091 | Download log for first connection (SyncBO=&1,device=&2,date=&3, time=&4) | The short text describes the object sufficiently | |
93 | 092 | RDB operation "clear" completed successfully | The short text describes the object sufficiently | |
94 | 093 | Header retrieved from replication DB (header action=&1) | The short text describes the object sufficiently | |
95 | 094 | &1 items received from RDB for device &2 (download date=&3, time=&4) | The short text describes the object sufficiently | |
96 | 095 | Item retreived from RDB (update action =&1) | The short text describes the object sufficiently | |
97 | 096 | No changed record found (SyncBO=&1, mobile ID=&2, sync key=&3, #=&4) | The short text describes the object sufficiently | |
98 | 097 | No download data produced (SyncBO=&1, mobile ID=&2) | The short text describes the object sufficiently | |
99 | 098 | Data from RDB read successfully (SyncBO=&1, headers=&2, items=&3) | The short text describes the object sufficiently | |
100 | 099 | Error retrieving headers and items from RDB (SyncBO=&1) | The short text describes the object sufficiently | |
101 | 100 | Conflict: R/3 = modify, device = modify | The short text describes the object sufficiently | |
102 | 101 | Conflict: R/3 = modify, device = delete | The short text describes the object sufficiently | |
103 | 102 | Conflict: R/3 = delete, device = modify | The short text describes the object sufficiently | |
104 | 103 | Conflict: R/3 = delete, device = delete | The short text describes the object sufficiently | |
105 | 104 | Default value missing: Value ID=&1, depends on=&2, exclusive=&3 | The short text describes the object sufficiently | |
106 | 105 | Unknown error occurred when reading RDB: SyncBO=&1, mobile ID=&2 | The short text describes the object sufficiently | |
107 | 106 | Synchronization key &1 already exits in replication DB | The short text describes the object sufficiently | |
108 | 107 | Synchronization key &1 missing in replicaion DB | The short text describes the object sufficiently | |
109 | 108 | Upload data not allowed when the RDB operation = 'Clear' | The short text describes the object sufficiently | |
110 | 109 | Data inconsistency between sync W/L and inbox data (seqno=&1,TOP cntr=&2) | The short text describes the object sufficiently | |
111 | 110 | There is no record to download | The short text describes the object sufficiently | |
112 | 111 | All updates for one TOP block were successful (seq. no.=&1, TOP cntr.=&2) | The short text describes the object sufficiently | |
113 | 112 | Unknown error occurred when reading RDB (mobile ID=&1, SyncBO=&2) | The short text describes the object sufficiently | |
114 | 113 | RDB was empty (SyncBO=&1, mobile ID=&2) | The short text describes the object sufficiently | |
115 | 114 | Deleting &1 entries from RDB (SyncBO=&2, mobile ID= &3) | The short text describes the object sufficiently | |
116 | 115 | Error storing header/item from mbl10100 (sBO &1,Mbl.ID=&2,hdr=&3,itm=&4) | The short text describes the object sufficiently | |
117 | 116 | Header=&1, items=&2 stored from mbl10100 into itab (sBO=&3,Mobile ID=&4) | The short text describes the object sufficiently | |
118 | 117 | Reading inbox record (mobile ID=&1, seq, no.=&2, rcd_cntr=&3, data=&4) | The short text describes the object sufficiently | |
119 | 118 | Field name &1 successfully created using para_name &2 | The short text describes the object sufficiently | |
120 | 119 | Error creating field name &2 using para_name &1 | The short text describes the object sufficiently | |
121 | 120 | External format successfully converted to internal format: ldata=&1&2&3&4 | The short text describes the object sufficiently | |
122 | 121 | Error converting external format to internal format | The short text describes the object sufficiently | |
123 | 122 | Filling common fields; struct ID=&1, send mask=&2, sync key=&3, action=&4 | The short text describes the object sufficiently | |
124 | 123 | Filling parent fields;struct ID=&1, strvers=&2, send mask=&3, sync key=&4 | The short text describes the object sufficiently | |
125 | 124 | Header action field &1 from device | The short text describes the object sufficiently | |
126 | 125 | Sync key &1 already exists in the replication DB for mobile ID &2 | The short text describes the object sufficiently | |
127 | 126 | Unknown synchronization key &1 for mobile ID &2 | The short text describes the object sufficiently | |
128 | 127 | Filling unchanged fields from RDB (full_sndmsk=&1, send mask=&2) | The short text describes the object sufficiently | |
129 | 128 | Updating inbox record with the new format (data=&1&2&3&4) | The short text describes the object sufficiently | |
130 | 129 | Item action field & from the device | The short text describes the object sufficiently | |
131 | 130 | Sync key &1 not found; entry does not exist for mobile ID &2 | The short text describes the object sufficiently | |
132 | 131 | Match found for header key &1 (sync key=&2) | The short text describes the object sufficiently | |
133 | 132 | No match found for header key &1 (action=&2) | The short text describes the object sufficiently | |
134 | 133 | No line item changed (data=&1&2&3&4) | The short text describes the object sufficiently | |
135 | 134 | Line item changed (data=&1&2&3&4) | The short text describes the object sufficiently | |
136 | 135 | RDB line item to be deleted (sync key=&1, #=&2) | The short text describes the object sufficiently | |
137 | 136 | Getting synchornizer worklist records (mobile ID=&1, #=&2) | The short text describes the object sufficiently | |
138 | 137 | TOP record (seq.no.=&1, counter=&2) not found for mobile ID &3 | The short text describes the object sufficiently | |
139 | 138 | TOP record (seq.no.=&1, counter=&2) read for mobile ID &3 | The short text describes the object sufficiently | |
140 | 139 | TOP record read from R/3 itab; conflict detected (sync key=&1) | The short text describes the object sufficiently | |
141 | 140 | TOP record not found from R/3 itab; conflict not detected (sync key=&1) | The short text describes the object sufficiently | |
142 | 141 | Updating RDB header/item (SyncBO=&1, mobile ID=&2, headers=#&3,items=#&4) | The short text describes the object sufficiently | |
143 | 142 | Updating RDB header/item failed (SyncBO=&1,mobile ID=&2,HDR=#&3,ITEM=#&4) | The short text describes the object sufficiently | |
144 | 143 | Getting header from download itab (sync key=&1, #=&2, data=&3&4) | The short text describes the object sufficiently | |
145 | 144 | Conversion from internal to external successful (header) data=&1&2&3&4 | The short text describes the object sufficiently | |
146 | 145 | Error converting from internal to external (header) mblID=&1 data=&2&3&4 | The short text describes the object sufficiently | |
147 | 146 | Getting item from download itab (sync key=&1, #=&2, data=&3&4) | The short text describes the object sufficiently | |
148 | 147 | Conversion from internal to external successful (item) data=&1&2&3&4 | The short text describes the object sufficiently | |
149 | 148 | Error converting from internal to external (item) (mblID=&1 data=&2&3&4) | The short text describes the object sufficiently | |
150 | 149 | Header action from mobile="ADD" | The short text describes the object sufficiently | |
151 | 150 | Header action from mobile="MOD", R/3 action="ADD" | The short text describes the object sufficiently | |
152 | 151 | Header action from mobile="DEL", R/3 action="ADD" | The short text describes the object sufficiently | |
153 | 152 | Header action from mobile="DEL", R/3 action="MOD" | The short text describes the object sufficiently | |
154 | 153 | Header action from mobile="DEL", R/3 action="DEL" | The short text describes the object sufficiently | |
155 | 154 | Header action from mobile="MOD", R/3 action="MOD" | The short text describes the object sufficiently | |
156 | 155 | Header action from mobile="MOD", R/3 action="DEL" | The short text describes the object sufficiently | |
157 | 156 | Deleting &1 items for mobile ID &2 | The short text describes the object sufficiently | |
158 | 157 | Changing R/3 object header and RDB header (sync key=&1, R/3 key=&2) | The short text describes the object sufficiently | |
159 | 158 | Checking for type conflict=& (X=required, space=not required) | The short text describes the object sufficiently | |
160 | 159 | DB operation="Clear"; upload data exists | The short text describes the object sufficiently | |
161 | 160 | RDB cleared stopping the process;SyncBO=&1, mobile ID=&2, DB operation=&3 | The short text describes the object sufficiently | |
162 | 161 | Line items: add=&1, changed=&2, deleted=&3, not changed=&4 | The short text describes the object sufficiently | |
163 | 162 | Line items: R/3 key=&1, synchronization key=&2, action=&3, item number=&4 | The short text describes the object sufficiently | |
164 | 163 | Objects found in R/3=&1, passed filter=&2, loaded filter=&3 | The short text describes the object sufficiently | |
165 | 164 | Objects: Add=&1, changed=&2, deleted=&3, not changed=&4 | The short text describes the object sufficiently | |
166 | 165 | Synchronization key=&1 > maximum synchronization key from device &2 | The short text describes the object sufficiently | |
167 | 166 | Last assigned sync. key &1 from mobile ID &2 updated successfully | The short text describes the object sufficiently | |
168 | 167 | Error updating last assigned synchronization key &1 from mobile ID &2 | The short text describes the object sufficiently | |
169 | 168 | Mobile ID=&1: Total records=&2, total worklists=&3, conflicts detected=&4 | The short text describes the object sufficiently | |
170 | 169 | Mobile ID=&1: Added=&2, changed=&3, deleted=&4 | The short text describes the object sufficiently | |
171 | 170 | Read TOP rcd from upload data(mobile ID=&1,seqno=&2,rcdcntr=&3,action=&4) | The short text describes the object sufficiently | |
172 | 171 | Deleting header(mobile ID=&1, synchronization key=&2) data=&3&4 | The short text describes the object sufficiently | |
173 | 172 | Updating replication DB for mobile ID &1 (headers=&2, items=&3) | The short text describes the object sufficiently | |
174 | 173 | Number=&1 download data for mobile ID=&2, SyncBO=&3 | The short text describes the object sufficiently | |
175 | 174 | Modifing header(mobile ID=&1, synchronization key=&2) data=&3&4 | The short text describes the object sufficiently | |
176 | 175 | Adding header(mobile ID=&1, synchronization key=&2) data=&3&4 | The short text describes the object sufficiently | |
177 | 176 | No download data from R/3 found in downloader | The short text describes the object sufficiently | |
178 | 177 | RFC communication error: &1&2 | The short text describes the object sufficiently | |
179 | 178 | RFC system error: &1&2 | The short text describes the object sufficiently | |
180 | 179 | There is no record to be downloaded | The short text describes the object sufficiently | |
181 | 180 | After BAPI wrapper call: GetList | The short text describes the object sufficiently | |
182 | 181 | After BAPI wrapper call: GetDetail | The short text describes the object sufficiently | |
183 | 182 | After BAPI wrapper call: Create | The short text describes the object sufficiently | |
184 | 183 | After BAPI wrapper call: Modify | The short text describes the object sufficiently | |
185 | 184 | After BAPI wrapper call: Delete | The short text describes the object sufficiently | |
186 | 185 | Return code from RFC BAPI Wrapper call:&1&2&3&4 | The short text describes the object sufficiently | |
187 | 186 | Before BAPI wrapper call: GetList | The short text describes the object sufficiently | |
188 | 187 | Before BAPI wrapper call: GetDetail | The short text describes the object sufficiently | |
189 | 188 | Before BAPI wrapper call: Create | The short text describes the object sufficiently | |
190 | 189 | Before BAPI wrapper call: Modify | The short text describes the object sufficiently | |
191 | 190 | Before BAPI wrapper call: Delete | The short text describes the object sufficiently | |
192 | 191 | BAPI wrapper terminated successfully; return has initial value | The short text describes the object sufficiently | |
193 | 192 | Filtering loaded for business object R/3 key=&1&2&3&4 | The short text describes the object sufficiently | |
194 | 193 | No. of criteria: SyncBO dp.= No.&1, mob. grp dp.=No.&2, device dp.=No.&3 | The short text describes the object sufficiently | |
195 | 194 | SyncBO dependent filtering passed (field1=&1, field2=&2, field3=&3) | The short text describes the object sufficiently | |
196 | 195 | Mobile group dependent filtering passed (field1=&1, field2=&2, field3=&3) | The short text describes the object sufficiently | |
197 | 196 | Mobile device dependent filtering passed(field1=&1, field2=&2, field3=&3) | The short text describes the object sufficiently | |
198 | 197 | Language key &1 not found | The short text describes the object sufficiently | |
199 | 198 | Error setting text environment for language &1 | The short text describes the object sufficiently | |
200 | 199 | Action &1 not allowed (synchronization key=&2, mobile ID=&3) | The short text describes the object sufficiently | |
201 | 200 | Object filtered (R/3 key=&1) | The short text describes the object sufficiently | |
202 | 201 | &1 asynchronous handlers launched | The short text describes the object sufficiently | |
203 | 202 | Duplicated synchronization key &1 sent from mobile device | The short text describes the object sufficiently | |
204 | 203 | Download header action has been set to "REP" | The short text describes the object sufficiently | |
205 | 204 | RDB header record action "REP" prepared | The short text describes the object sufficiently | |
206 | 205 | Environment variable "DIR_HOME" is not assigned | The short text describes the object sufficiently | |
207 | 206 | Cannot manipulate file: &1 | The short text describes the object sufficiently | |
208 | 207 | File idenitified by &1 does not exist in directory &2 | Space: object requires documentation | |
209 | 208 | There is no data from device to upload | The short text describes the object sufficiently | |
210 | 209 | Downloader for specific business object executed by receiver | The short text describes the object sufficiently | |
211 | 210 | Invalid inbox worklist (blank?) received; mobile ID=&1, SyncBO=&2 | Space: object requires documentation | |
212 | 211 | Invalid inbox record (empty inbox) received; mobile ID=&1, SyncBO=&2 | Space: object requires documentation | |
213 | 212 | Synchronization type of SyncBO &1 does not allow func. to be processed | Space: object requires documentation | |
214 | 213 | Sync_Key = <initial> is not allowed | Space: object requires documentation | |
215 | 214 | No data found by specified criteria | The short text describes the object sufficiently | |
216 | 215 | Replicator terminated with enqueue failure (SyncBO=&1, trial number=&2) | The short text describes the object sufficiently | |
217 | 216 | Enqueue failure in replicator (lock owner=&1, trial no.=&2, R/3 key=&3) | The short text describes the object sufficiently | |
218 | 217 | Enqueue successful in replicator (SyncBO=&1, R/3 key=&2) | The short text describes the object sufficiently | |
219 | 218 | Dequeue successful in replicator (SyncBO=&1, R/3 key=&2) | The short text describes the object sufficiently | |
220 | 219 | Enqueue failure in uploader (lock owner=&1,seq.no.=&2,cntr=&3,R/3key=&4) | The short text describes the object sufficiently | |
221 | 220 | Enqueue successful in uploader(seq. no.=&1, TOP cntr=&2, R/3 key=&3) | The short text describes the object sufficiently | |
222 | 221 | Dequeue successful in uploader(SyncBO=&1,seqNo.=&2,TOPcntr=&3, R/3key=&4) | The short text describes the object sufficiently | |
223 | 222 | Time stamp from device is old (mobie ID=&1, replication DB=&2) | The short text describes the object sufficiently | |
224 | 223 | Last device to update RDB record was same dev. (sync. key=&1, mob. ID=&2) | The short text describes the object sufficiently | |
225 | 224 | Enqueue error in downloader(lock owner=&1,seqNo=&2,TOPcntr=&3,R/3 key=&4) | The short text describes the object sufficiently | |
226 | 225 | Enqueue successful at downloader lock | The short text describes the object sufficiently | |
227 | 226 | Dequeue successful at downloader lock | The short text describes the object sufficiently | |
228 | 227 | Unexpected termination of function call (reference: &1/&2/&3/&4) | The short text describes the object sufficiently | |
229 | 228 | Function module completed successfully | The short text describes the object sufficiently | |
230 | 229 | Check log using transaction code MEREP_LOG | The short text describes the object sufficiently | |
231 | 230 | Unexpected termination of replicator (reference: &1/&2/&3/&4) | The short text describes the object sufficiently | |
232 | 231 | Error updating DB (table=&1,SQL statement=&2,return code=&3,key word=&4) | The short text describes the object sufficiently | |
233 | 232 | Related SyncBO &2 with Sync key &1 is not present on the device. | The short text describes the object sufficiently | |
234 | 233 | R/3 key &1 for related SyncBO &2 missing or cascade search failed | The short text describes the object sufficiently | |
235 | 234 | Circulation found (SyncBO=&1, sync. key=&2, circulation counter=&3) | The short text describes the object sufficiently | |
236 | 235 | Starting next partial replication (counter=&1, R/3 key greater than=&2) | The short text describes the object sufficiently | |
237 | 236 | Fixing "less or equal R/3 key" (counter=&1, R/3key less or equal=&2) | The short text describes the object sufficiently | |
238 | 237 | SyncBO &1 does not exit or MSD is not configured for object &2 | The short text describes the object sufficiently | |
239 | 238 | Update failure of delta BO queue | The short text describes the object sufficiently | |
240 | 239 | Replication job schedule exists for SyncBO &1 | The short text describes the object sufficiently | |
241 | 240 | &1 replication triggered successfully(scheduled job nm.:&2, job count:&3) | The short text describes the object sufficiently | |
242 | 241 | Downloader filled outbox | The short text describes the object sufficiently | |
243 | 242 | Cascade search failed; from (SyncBO=&1, SKey=&2) to (SyncBO=&3, R3Key=&4) | The short text describes the object sufficiently | |
244 | 243 | Duplicated R/3 keys found | The short text describes the object sufficiently | |
245 | 244 | Structure ID=&1, parent synchronization key=&2, R/3 key=&3&4 | The short text describes the object sufficiently | |
246 | 245 | Prio error in related SyncBO (sync. key &1 for related SyncBO &2) | The short text describes the object sufficiently | |
247 | 246 | Create BAPI Wrapper returns initial R/3 key | The short text describes the object sufficiently | |
248 | 247 | &1 out of &2 objects were unable to download,please contact administrator | The short text describes the object sufficiently | |
249 | 248 | Conflict detected at Struct_ID = '&1' and Sync Key = '&2'. | The short text describes the object sufficiently | |
250 | 249 | Row Based Conflict Detection is ON | The short text describes the object sufficiently | |
251 | 250 | Row Based Conflict Detection is OFF | The short text describes the object sufficiently | |
252 | 301 | Mobile ID &1 does not exist | The short text describes the object sufficiently | |
253 | 302 | Mobile ID &1 does not have any entry in &2, &3, and &4 | Space: object requires documentation | |
254 | 303 | Mobile ID &1 does not have any entry in &2 | Space: object requires documentation | |
255 | 304 | Error deleting record of mobile ID &1 in &2 | Space: object requires documentation | |
256 | 305 | Record of mobile ID &1 in &2 successfully deleted | Space: object requires documentation | |
257 | 306 | SyncBO &1 does not exist | Space: object requires documentation | |
258 | 307 | (Mobile ID &1, SyncBO &2) error reading &3 | Space: object requires documentation | |
259 | 308 | Mobile ID &1 and SyncBO &2 do not have entry in &3 | Space: object requires documentation | |
260 | 309 | Error deleting record of mobile ID &1 SyncBO &2 in &3 | Space: object requires documentation | |
261 | 310 | Record of mobile ID &1 SyncBO &2 in &3 successfully deleted | Space: object requires documentation | |
262 | 311 | SyncBO type &1 undefined | Space: object requires documentation | |
263 | 312 | &1 is upload type SyncBO; no data to be deleted | Space: object requires documentation |
History
Last changed on/by | 20060912 | SAP | |
SAP Release Created in | 620 |