SAP ABAP Message Class MEREP_00 (Basic Message)
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
⤷
⤷
Attributes
| Message class | MEREP_00 | |
| Short Description | Basic Message | |
| Changed On | 20060912 | |
| Last Changed At | 114213 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | & not found | Space: object requires documentation | ||
| 2 | &1 entries (&2 run numbers) found | Space: object requires documentation | ||
| 3 | &1 entries found | The short text describes the object sufficiently | ||
| 4 | Receiver call successful; see worklist monitor | The short text describes the object sufficiently | ||
| 5 | & is empty | The short text describes the object sufficiently | ||
| 6 | Mobile ID &1 successfully reset | The short text describes the object sufficiently | ||
| 7 | Prio errors exist and conversation control has set stop on error flag on | The short text describes the object sufficiently | ||
| 8 | & database update failed | Space: object requires documentation | ||
| 9 | Handler worklist &1 has no corresponding inbox data | The short text describes the object sufficiently | ||
| 10 | Run number cannot be assigned | The short text describes the object sufficiently | ||
| 11 | Handler call not permitted for batch user status | The short text describes the object sufficiently | ||
| 12 | Unable to enqueue & | The short text describes the object sufficiently | ||
| 13 | Synchronizer function &1 call failed due to &2 | The short text describes the object sufficiently | ||
| 14 | Return code &1 (&2) | The short text describes the object sufficiently | ||
| 15 | Maximum jobs (&) exceeded | The short text describes the object sufficiently | ||
| 16 | Job (number = &1) started | The short text describes the object sufficiently | ||
| 17 | Failed to update object execution info &1 &2 &3 | The short text describes the object sufficiently | ||
| 18 | Error occured while inserting & data to the database | The short text describes the object sufficiently | ||
| 19 | &1 has started for run number &2 and runtime counter &3 | The short text describes the object sufficiently | ||
| 20 | &1 has finished for run number &2 and runtime counter &3 | The short text describes the object sufficiently | ||
| 21 | Over 90% of number range object & has been consumed | Space: object requires documentation | ||
| 22 | Error saving log/run data for run number &1, runtime counter &2, line &3 | The short text describes the object sufficiently | ||
| 23 | No log entry found for &1 worklist item &2 &3 &4 | Space: object requires documentation | ||
| 24 | No subsequent worklist entry found for &1 worklist &2 &3 | Space: object requires documentation | ||
| 25 | No job information is avilable for &1 worklist item &2 &3 &4 | Space: object requires documentation | ||
| 26 | Run number used twice;data inconsistency | The short text describes the object sufficiently | ||
| 27 | Field name &1 not selected as filter criteria | The short text describes the object sufficiently | ||
| 28 | No job information was found for the log message | The short text describes the object sufficiently | ||
| 29 | Start processing conversation worklist &1 | The short text describes the object sufficiently | ||
| 30 | End processing conversation worklist &1 | The short text describes the object sufficiently | ||
| 31 | Downloader completed successfully (mobile ID: &1, SyncBO: &2) | The short text describes the object sufficiently | ||
| 32 | Value too long | The short text describes the object sufficiently | ||
| 33 | Value not numeric | The short text describes the object sufficiently | ||
| 34 | Data type error for date | The short text describes the object sufficiently | ||
| 35 | Data type error for time | The short text describes the object sufficiently | ||
| 36 | Error in the nest of calls to OBJECT_START and OBJECT_END | The short text describes the object sufficiently | ||
| 37 | Characters are not allowed | The short text describes the object sufficiently | ||
| 38 | Decimal points not allowed | The short text describes the object sufficiently | ||
| 39 | Too many decimal places | The short text describes the object sufficiently | ||
| 40 | Data type conflict in data from mobile | Space: object requires documentation | ||
| 41 | Inbox data deleted (mobile ID = &1, sequence number = &2) | The short text describes the object sufficiently | ||
| 42 | Synchronizer &1 completed successfully (mobile ID=&2, SyncBO=&3) | The short text describes the object sufficiently | ||
| 43 | Conversation control record for &1 not found | The short text describes the object sufficiently | ||
| 44 | Receiver control record not found | The short text describes the object sufficiently | ||
| 45 | Handler control record not found | The short text describes the object sufficiently | ||
| 46 | Sender control record not found | The short text describes the object sufficiently | ||
| 47 | Synchronizer control record for &1 not found | The short text describes the object sufficiently | ||
| 48 | Synchronization type control record not found | The short text describes the object sufficiently | ||
| 49 | SyncBO control record for &1 not found | The short text describes the object sufficiently | ||
| 50 | Conversation control record for &1 not enabled | The short text describes the object sufficiently | ||
| 51 | Receiver control record not enabled | The short text describes the object sufficiently | ||
| 52 | Handler control record not enabled | The short text describes the object sufficiently | ||
| 53 | Sender control record not enabled | The short text describes the object sufficiently | ||
| 54 | Synchronizer control record for &1 not enabled | The short text describes the object sufficiently | ||
| 55 | Selected log has no corresponding worklist item | The short text describes the object sufficiently | ||
| 56 | Receiver does not call handler (return code=&1, reason=&2) | The short text describes the object sufficiently | ||
| 57 | Sender worklist &1 &2 has no corresponding outbox data | The short text describes the object sufficiently | ||
| 58 | Action canceled | Space: object requires documentation | ||
| 59 | Internal error | Space: object requires documentation | ||
| 60 | Enqueue failure for mobile ID &1 | The short text describes the object sufficiently | ||
| 61 | Conversation control record for &1 is unregistered | The short text describes the object sufficiently | ||
| 62 | No conversation worklist record found for mobile ID &1 | The short text describes the object sufficiently | ||
| 63 | SyncBO &1 not (re)generated | The short text describes the object sufficiently | ||
| 64 | Generated code & is not configured correctly | The short text describes the object sufficiently | ||
| 65 | User exits in generated code & raised exception w/o creating RTN records | The short text describes the object sufficiently | ||
| 66 | SyncBO &1 has syntax errors in the user exit | The short text describes the object sufficiently | ||
| 67 | &1 worklists found to be processed for mobile ID &2 | The short text describes the object sufficiently | ||
| 68 | Log start: job name &1 is invalid | The short text describes the object sufficiently | ||
| 69 | Log start: Unknown error | The short text describes the object sufficiently | ||
| 70 | Log stop: job name &1 is invalid | Space: object requires documentation | ||
| 71 | Enter numeric value (0-9) for the parameter &1. | The short text describes the object sufficiently | ||
| 72 | Enter a value in 'Option' field | Space: object requires documentation | ||
| 73 | Length of 'Value' column must not exceed 28 characters | Space: object requires documentation | ||
| 74 | Mandatory fields are not mapped in &1 | Space: object requires documentation | ||
| 75 | No error found | Space: object requires documentation | ||
| 76 | You can only choose the "SyncBO Only" option | Space: object requires documentation | ||
| 77 | Enter a value in 'Value' field | Space: object requires documentation | ||
| 78 | User &1 does not exist or is not a mobile user | Space: object requires documentation | ||
| 79 | &1 &2 &3 &4 | Space: object requires documentation | ||
| 80 | SyncBO &1 is a download SyncBO. Upload data not expected | The short text describes the object sufficiently | ||
| 81 | SyncBO &1 is an upload SyncBO; upload data empty | The short text describes the object sufficiently | ||
| 82 | Invalid job type &1 | The short text describes the object sufficiently | ||
| 83 | Unable to retrieve metadata for SyncBO &1 | Space: object requires documentation | ||
| 84 | Invalid send mask: &1 | The short text describes the object sufficiently | ||
| 85 | Invalid metadata for SyncBO &1 | The short text describes the object sufficiently | ||
| 86 | Number of fields from device exceeds SyncBO definition (value=&1) | The short text describes the object sufficiently | ||
| 87 | Data type from device incompatible (value=&1) | The short text describes the object sufficiently | ||
| 88 | Invalid structure ID: &1 | The short text describes the object sufficiently | ||
| 89 | Invalid parameter for &1: name = &2, value = &3 | The short text describes the object sufficiently | ||
| 90 | XML metadata file successfully downloaded to file path &1 &2 | Space: object requires documentation | ||
| 91 | Error during download: &1 | Space: object requires documentation | ||
| 92 | File name exceeds limit | Space: object requires documentation | ||
| 93 | Invalid character(s) | The short text describes the object sufficiently | ||
| 94 | No encoding information found | The short text describes the object sufficiently | ||
| 95 | Error parsing XML at offset &1, entity &2 | The short text describes the object sufficiently | ||
| 96 | MSD &1 is not an MEREP application | The short text describes the object sufficiently | ||
| 97 | Reason for XML parse error: &1&2&3&4 | The short text describes the object sufficiently | ||
| 98 | Message contains deltas for different SyncBO IDs | The short text describes the object sufficiently | ||
| 99 | Multiple &1s found when creating a single SyncBO delta | The short text describes the object sufficiently | ||
| 100 | No SyncBO delta found | The short text describes the object sufficiently | ||
| 101 | Unknown message type &1 | The short text describes the object sufficiently | ||
| 102 | Unknown value &1 for domain &2 | The short text describes the object sufficiently | ||
| 103 | XML document contains an unknown value &1 for attribute &2 of element &3 | The short text describes the object sufficiently | ||
| 104 | Message is invalid; failed to create DOM | The short text describes the object sufficiently | ||
| 105 | Failed to parse XML document | The short text describes the object sufficiently | ||
| 106 | Forced correction of XML document encoding from &1 to &2 | The short text describes the object sufficiently | ||
| 107 | Failed to correct XML document encoding | The short text describes the object sufficiently | ||
| 108 | Codepage &1 is not supported | The short text describes the object sufficiently | ||
| 109 | Data &1 will be lost after conversion | The short text describes the object sufficiently | ||
| 110 | Index &1 is out of bounds | The short text describes the object sufficiently | ||
| 111 | Metadata for structure &1 is invalid | The short text describes the object sufficiently | ||
| 112 | Value "&1" failed to pass the type check for field &2-&3 | The short text describes the object sufficiently | ||
| 113 | <Dump>&1&2&3&4</Dump> | The short text describes the object sufficiently | ||
| 114 | Failed to create message object from inbox/outbox data | The short text describes the object sufficiently | ||
| 115 | * Monitoring | The short text describes the object sufficiently | ||
| 116 | No worklist found | Space: object requires documentation | ||
| 117 | No log found | Space: object requires documentation | ||
| 118 | Function not supported for selected item | Space: object requires documentation | ||
| 119 | No subordinate worklist found | Space: object requires documentation | ||
| 120 | No data found | Space: object requires documentation | ||
| 121 | Error preparing for data display | The short text describes the object sufficiently | ||
| 122 | Only handler worklist can be reprocessed | Space: object requires documentation | ||
| 123 | Only handler worklist can be processed | Space: object requires documentation | ||
| 124 | Cannot process any of the selected worklists | Space: object requires documentation | ||
| 125 | Only Handler and Sender worklist can be marked as complete | Space: object requires documentation | ||
| 126 | None of the selected worklists can be marked as complete | Space: object requires documentation | ||
| 127 | Worklist status updated | Space: object requires documentation | ||
| 128 | Mobile ID & already exists | Space: object requires documentation | ||
| 129 | Mobile ID & does not exist | Space: object requires documentation | ||
| 130 | Mobile ID & successfully deleted | Space: object requires documentation | ||
| 131 | Mobile group & does not exist | The short text describes the object sufficiently | ||
| 132 | Mobile ID &1 has the same conversation information as mobile ID &2 | The short text describes the object sufficiently | ||
| 133 | Enter value | Space: object requires documentation | ||
| 134 | Mobile group & already exists | Space: object requires documentation | ||
| 135 | Saved successfully | Space: object requires documentation | ||
| 136 | Mobile ID &1 has been proposed | Space: object requires documentation | ||
| 137 | Mbile ID &1 has been reset | Space: object requires documentation | ||
| 138 | Deleted successfully | Space: object requires documentation | ||
| 139 | Replicator only handles generated SyncBOs | Space: object requires documentation | ||
| 140 | Reassign mobile IDs to another mobile group | The short text describes the object sufficiently | ||
| 141 | Choose items | Space: object requires documentation | ||
| 142 | Mobile ID &1 is unregistered | The short text describes the object sufficiently | ||
| 143 | Mobile ID & registered | Space: object requires documentation | ||
| 144 | No mobile ID found | Space: object requires documentation | ||
| 145 | Select a line | Space: object requires documentation | ||
| 146 | Exported successfully | Space: object requires documentation | ||
| 147 | Imported successfully | Space: object requires documentation | ||
| 148 | Transport request deleted successfully | Space: object requires documentation | ||
| 149 | Data successfully purged | Space: object requires documentation | ||
| 150 | Data purge failed | Space: object requires documentation | ||
| 151 | Enter the transport request number | Space: object requires documentation | ||
| 152 | Synchronization type does not exist | Space: object requires documentation | ||
| 153 | Transport request does not exist | Space: object requires documentation | ||
| 154 | Only one request can be released at once | Space: object requires documentation | ||
| 155 | Download successful | Space: object requires documentation | ||
| 156 | SyncBO does not exist or was not generated | Space: object requires documentation | ||
| 157 | SyncBO contains syntax errors | Space: object requires documentation | ||
| 158 | No data to be purged | Space: object requires documentation | ||
| 159 | Detailed output can cause memory error if the number of records is high | Space: object requires documentation | ||
| 160 | Unspecified failure | Space: object requires documentation | ||
| 161 | * Messages with numbers up to 699 are mainly used for SyncBO Builder | The short text describes the object sufficiently | ||
| 162 | SyncBO &1 already exists | Space: object requires documentation | ||
| 163 | SyncBO &1 does not exist | Space: object requires documentation | ||
| 164 | Enter at least one function module (BAPI wrapper) | Space: object requires documentation | ||
| 165 | You cannot use the same BAPI Wrapper for different actions | Space: object requires documentation | ||
| 166 | Value ID &1 has already been created | The short text describes the object sufficiently | ||
| 167 | Value ID is not assigned for parameter &1 in &2 | The short text describes the object sufficiently | ||
| 168 | Value ID &1 is still assigned to some fields | The short text describes the object sufficiently | ||
| 169 | No parameter found | Space: object requires documentation | ||
| 170 | & structure has exceeded the limit length of 2048; reduce some fields | Space: object requires documentation | ||
| 171 | You cannot select more than three filtering criteria | Space: object requires documentation | ||
| 172 | Specify a SyncBO name | Space: object requires documentation | ||
| 173 | Inconsistent interfaces found (&1 entries) | Space: object requires documentation | ||
| 174 | No error found | Space: object requires documentation | ||
| 175 | SyncBO &1 has been saved | Space: object requires documentation | ||
| 176 | SyncBO &1 has been generated | Space: object requires documentation | ||
| 177 | Skeleton & not found | The short text describes the object sufficiently | ||
| 178 | Function modules from the function pool & contain syntax errors | The short text describes the object sufficiently | ||
| 179 | Structure IDs are duplicated | Space: object requires documentation | ||
| 180 | No filtering criteria field has been selected for SyncBO &1 | Space: object requires documentation | ||
| 181 | Function group must start with 'Z' or 'Y'; you cannot leave it blank | Space: object requires documentation | ||
| 182 | Function module &1 is not RFC enabled | Space: object requires documentation | ||
| 183 | SyncBO &1 has been successfully copied | Space: object requires documentation | ||
| 184 | Synchronization type &1 is invalid | Space: object requires documentation | ||
| 185 | Key fields of structure exceeded the maximum length &1 | Space: object requires documentation | ||
| 186 | No SyncBO found | Space: object requires documentation | ||
| 187 | Place the cursor on a valid row | Space: object requires documentation | ||
| 188 | Position of field &1 is inconsistent | The short text describes the object sufficiently | ||
| 189 | SyncBO name &1 is reserved by SAP | Space: object requires documentation | ||
| 190 | Select time and date fields | The short text describes the object sufficiently | ||
| 191 | Field group &1 already exists | The short text describes the object sufficiently | ||
| 192 | Field &1 is already assigned to field group &2 | The short text describes the object sufficiently | ||
| 193 | Field name &1 is reserved by the system | The short text describes the object sufficiently | ||
| 194 | Select field used for language conversion | Space: object requires documentation | ||
| 195 | To use a diff. lang. item, delete existing mappings in current structure | Space: object requires documentation | ||
| 196 | There is no default value for SyncBO &1 | Space: object requires documentation | ||
| 197 | Selection conditions have been saved | Space: object requires documentation | ||
| 198 | SyncBO &1 needs to be generated first | Space: object requires documentation | ||
| 199 | No syntax errors found | Space: object requires documentation | ||
| 200 | RFC function module search failed | Space: object requires documentation | ||
| 201 | SyncBO &1 has already been reset to editor lock | The short text describes the object sufficiently | ||
| 202 | SyncBO &1 has already been published | Space: object requires documentation | ||
| 203 | SyncBO &1 has been set to editor lock by &2 | The short text describes the object sufficiently | ||
| 204 | You cannot select this line | Space: object requires documentation | ||
| 205 | RFC destination & is not available; change the destination | Space: object requires documentation | ||
| 206 | RFC destination of SyncBO &1 has been changed | Space: object requires documentation | ||
| 207 | Generated code not found for SyncBO &1 | The short text describes the object sufficiently | ||
| 208 | R/3 key has not been selected in &1 | Space: object requires documentation | ||
| 209 | No data for specified synchronization key | The short text describes the object sufficiently | ||
| 210 | No key field has been selected for export parameter in &1 | Space: object requires documentation | ||
| 211 | RFC communication failure: & & | Space: object requires documentation | ||
| 212 | RFC system failure: & & | Space: object requires documentation | ||
| 213 | Item key has not been selected for parameter &1 in &2 | Space: object requires documentation | ||
| 214 | Mobile group & does not exist | Space: object requires documentation | ||
| 215 | Specify value ID to be deleted | Space: object requires documentation | ||
| 216 | Mapping setting was copied from &1 | Space: object requires documentation | ||
| 217 | Filtering criteria contain syntax error | Space: object requires documentation | ||
| 218 | Filtering is only driven by referencing SyncBO | The short text describes the object sufficiently | ||
| 219 | Filtering is only driven by referencing SyncBO | The short text describes the object sufficiently | ||
| 220 | SyncBO &1 refers to other SyncBO(s); RFC destination cannot be changed | Space: object requires documentation | ||
| 221 | You cannot copy this SyncBO because relevant metadata contains errors | Space: object requires documentation | ||
| 222 | Key setting for field &1 is inconsistent between &2 and &3 | Space: object requires documentation | ||
| 223 | RFC destination of SyncBO &1 has not been changed | Space: object requires documentation | ||
| 224 | RFC destination dependent on SyncBO &1 has been defined | Space: object requires documentation | ||
| 225 | Import parameter referring to &1 required in &2 if Mass Data selected | Space: object requires documentation | ||
| 226 | Map at least one field | Space: object requires documentation | ||
| 227 | &1 does not have RETURN parameter in export or tables parameter | Space: object requires documentation | ||
| 228 | RETURN parameter in &1 should refer to structure &2 | Space: object requires documentation | ||
| 229 | &1 must have field ME_ACTION in header structure | The short text describes the object sufficiently | ||
| 230 | Metadata for SyncBO &1 contain errors | Space: object requires documentation | ||
| 231 | SyncBO &1 is enabled | Space: object requires documentation | ||
| 232 | Field ME_ACTION must refer to a character type of length 1 | Space: object requires documentation | ||
| 233 | Reference type &1 of export parameter is duplicated in &2 | Space: object requires documentation | ||
| 234 | Reference type &1 of import parameter is duplicated in &2 | Space: object requires documentation | ||
| 235 | Default value for parameter &1 has no effect at runtime | Space: object requires documentation | ||
| 236 | SyncBO &1 is still used as related SyncBO | Space: object requires documentation | ||
| 237 | SyncBO &1 has been disabled | Space: object requires documentation | ||
| 238 | Data type '&1' not supported | The short text describes the object sufficiently | ||
| 239 | Data type of field &3 in parameter &1 is unsupported for BAPI wrapper &2 | Space: object requires documentation | ||
| 240 | No &1 parameter referring to header structure exists in &2 | Space: object requires documentation | ||
| 241 | No &1 parameter referring to a field of header structure exists in &2 | Space: object requires documentation | ||
| 242 | No &1 parameter referring to item structure exists in &2 | Space: object requires documentation | ||
| 243 | Parameter &1 ignored at runtime; must be optional | Space: object requires documentation | ||
| 244 | Interface of related SyncBO &1 is inconsistent with field &2 | Space: object requires documentation | ||
| 245 | RFC destination of related SyncBO &1 is inconsistent with SyncBO &2 | Space: object requires documentation | ||
| 246 | Enter the multiple of ten for the item structure ID | Space: object requires documentation | ||
| 247 | BAPI wrappers were successfully generated and activated | The short text describes the object sufficiently | ||
| 248 | Length of parameter name &1 is longer than 21 | Space: object requires documentation | ||
| 249 | Reference structure must be flat in parameter &1 for BAPI wrapper &2 | The short text describes the object sufficiently | ||
| 250 | Only inbox data can be modified | Space: object requires documentation | ||
| 251 | This function allows only "E:Error" data modification | Space: object requires documentation | ||
| 252 | This function does not allow modification for StructID =&1 | Space: object requires documentation | ||
| 253 | Unexpected error in code generator (Reference: &1/&2/&3/&4) | The short text describes the object sufficiently | ||
| 254 | Unknown error | Space: object requires documentation | ||
| 255 | * Upper is used for non-runtime, mainly for workbench | The short text describes the object sufficiently | ||
| 256 | Enter the valid log level | Space: object requires documentation | ||
| 257 | Cannot expand data because of metadata conflict (ex. different version) | Space: object requires documentation | ||
| 258 | Enter the Last Sync Date | The short text describes the object sufficiently | ||
| 259 | No obsolete mobile id found | The short text describes the object sufficiently | ||
| 260 | Select a Mobile id | The short text describes the object sufficiently | ||
| 261 | Mobile Ids are deleted successfully | The short text describes the object sufficiently | ||
| 262 | Last Sync Date should be grater than Current date | The short text describes the object sufficiently | ||
| 263 | Mobile Id created using MEREP_PD transaction will also be selected | The short text describes the object sufficiently | ||
| 264 | Enter the start date | The short text describes the object sufficiently | ||
| 265 | No record found for consistency check | The short text describes the object sufficiently |
History
| Last changed on/by | 20060912 | SAP | |
| SAP Release Created in | 620 |