SAP ABAP Message Class B1 (ALE group messages)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-MID-ALE (Application Component) ALE Integration Technology
⤷
SALE (Package) Application Link Enabling
⤷
⤷
Attributes
| Message class | B1 | |
| Short Description | ALE group messages | |
| Changed On | 20130531 | |
| Last Changed At | 115938 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | No entry in table & for key & & & | |||
| 2 | ***** Messages for input and outbound processing ***** | |||
| 3 | No IDoc type maintained for base type & and extension type & | |||
| 4 | Transport contains control data to be distributed - please distribute | Space: object requires documentation | ||
| 5 | Could not determine recipients for message type & | |||
| 6 | A separate logical system is not defined for client & | |||
| 7 | & &, &, &. | Space: object requires documentation | ||
| 8 | &, &, &, & | Space: object requires documentation | ||
| 9 | Segment type & does not exist in message type & | |||
| 10 | Mandatory segment & in message type & cannot be filtered | |||
| 11 | Partner profile missing for recipient & & &, message type & | Space: object requires documentation | ||
| 12 | Objects not in T777I do not have an infotype | |||
| 13 | Position the Cursor Correctly | |||
| 14 | Interface changed for message type &1: Settings reset | Space: object requires documentation | ||
| 15 | Message type & does not exist | |||
| 16 | Message type & exists already | Space: object requires documentation | ||
| 17 | Database error when storing in EDMSG | |||
| 18 | Database error when storing in EDIMSG | Space: object requires documentation | ||
| 19 | Database error when storing in EDIMSGT | |||
| 20 | Database error when storing in EDIMAP | |||
| 21 | Port & is not an RFC port, or RFC destination is missing | |||
| 22 | Error when calling asynchronous Remote Function Call | |||
| 23 | Infotype " " is only for objects without infotypes | |||
| 24 | Database error occurred when storing in BDSER | |||
| 25 | No data for entity & | Space: object requires documentation | ||
| 26 | Inconsistent IDocs passed: Data records or control records missing. | |||
| 27 | Class type &, receiving system &: no list maintained | |||
| 28 | Object type & not maintained for message type & | |||
| 29 | Distribution model posted successfully | Space: object requires documentation | ||
| 30 | Object type & cannot be read for message type & from segment type & | |||
| 31 | No classification object maintained for message type & | |||
| 32 | Database error when storing in BDPNT | |||
| 33 | No distribution class type exists for classification object & | |||
| 34 | ***** Messages for application input ***** | |||
| 35 | No (active) partner profile: sender & & &, message type & | Space: object requires documentation | ||
| 36 | No process code exists for sender & and message type & | |||
| 37 | No function module for input process code & | |||
| 38 | No parameters found for function module & | |||
| 39 | Maximum no. of repetitions exceeded | |||
| 40 | IDocs in packet do not match | Space: object requires documentation | ||
| 41 | Packet contains no IDocs | Space: object requires documentation | ||
| 42 | & master IDocs set up for message type & | Space: object requires documentation | ||
| 43 | & communication IDoc(s) generated for message type & | Space: object requires documentation | ||
| 44 | User & has no authorization for message type & in ALE inbound | Space: object requires documentation | ||
| 45 | Table MASTER_IDOC_DATA is empty | |||
| 46 | Direct call started | |||
| 47 | Task & started with workflow ID & | |||
| 48 | Incorrect function module & called up | |||
| 49 | Application function module & terminated with invalid exception. | |||
| 50 | Task & could not be started. | |||
| 51 | Process & could not be started. | |||
| 52 | Process & started with ID &. | |||
| 53 | More than one IDoc transferred | Space: object requires documentation | ||
| 54 | ***** Messages for failed Select Singles ***** | |||
| 55 | IDoc included in IDoc packet containing an error: transfer it separately | Space: object requires documentation | ||
| 56 | Message type included in request | Space: object requires documentation | ||
| 57 | Filter object type & not permitted with message type & | |||
| 58 | Control data object & does not exist | Space: object requires documentation | ||
| 59 | Message type & does not exist | |||
| 60 | Database error when storing in Table TBD10 | |||
| 61 | Database error when storing in Table TBD12 | |||
| 62 | Database error when storing in Table TBD13 | |||
| 63 | Database error when storing in Table TBDME | |||
| 64 | Database error when storing data in Table & | |||
| 65 | The customer model in HR-ORG could not be deleted | Space: object requires documentation | ||
| 66 | Error when assigning numbers to HR-ORG objects | Space: object requires documentation | ||
| 67 | & request IDocs created for message type & | Space: object requires documentation | ||
| 68 | Remote Function Call destination could not be found | |||
| 69 | Connection to other system could not be established | |||
| 70 | Messages have been created during processing (last was displayed) | Space: object requires documentation | ||
| 71 | Number of IDocs: total &, dispatched &, still open (tRFC queue) & | Space: object requires documentation | ||
| 72 | Place the cursor on a subsystem | |||
| 73 | Filter object already assigned | |||
| 74 | Internal error: Program &, command &, argument & | Space: object requires documentation | ||
| 75 | More than one IDoc selected | The short text describes the object sufficiently | ||
| 76 | Place the cursor on a message type | |||
| 77 | Place the cursor on a filter object | |||
| 78 | Distribution model is being processed | |||
| 79 | Function & is not available in this system, termination | Space: object requires documentation | ||
| 80 | No object type for lists maintained for message type & | |||
| 81 | This IDoc was forwarded to receiver & & &. | Space: object requires documentation | ||
| 82 | Check your entry | |||
| 83 | Message type & included in request & | |||
| 84 | ***** Messages for RBDTBDA1 ***** | |||
| 85 | Change pointer generation deactivated | |||
| 86 | Change pointer generation activated | |||
| 87 | No data could be selected. | |||
| 88 | Database error occurred when storing in table TBDMS | Space: object requires documentation | ||
| 89 | Error occurred when assigning a number for a change pointer | |||
| 90 | External partner system &: functionality not available | Space: object requires documentation | ||
| 91 | Partner system & is an R/2 system: functionality not available | Space: object requires documentation | ||
| 92 | RFC destination & does not exist | Space: object requires documentation | ||
| 93 | Partner profile & & & & does not exist | Space: object requires documentation | ||
| 94 | IDoc type could not be determined for the IDoc | Space: object requires documentation | ||
| 95 | Receiver of IDoc is its own logical system | Space: object requires documentation | ||
| 96 | Start Transaction & for the check | Space: object requires documentation | ||
| 97 | Model & cannot be maintained in own system | |||
| 98 | Message type not permitted, because no ownership for model & | Space: object requires documentation | ||
| 99 | Segment & does not exist for message type & | Space: object requires documentation | ||
| 100 | Indicator cannot be selected | Space: object requires documentation | ||
| 101 | Changes cannot be made to the control data distribution in this system | |||
| 102 | Tool could not be started - please enter call parameters | Space: object requires documentation | ||
| 103 | & | |||
| 104 | F key must be specified | |||
| 105 | Linked object: &, && | |||
| 106 | Message type & does not exist | |||
| 107 | Required segment & cannot be deactivated | |||
| 108 | Segment & has already been deactivated completely | |||
| 109 | No IDoc type found for message type & | Space: object requires documentation | ||
| 110 | Message type & exists already | |||
| 111 | Reduction for message type & saved | |||
| 112 | Higher-level segment deactivated | |||
| 113 | Table & for message type & exists already in EDIMAP | |||
| 114 | Please choose an processing type. | |||
| 115 | This combination is not allowed | |||
| 116 | Reference message type may not have reference | |||
| 117 | Generation of change pointers for & activated in client & | |||
| 118 | Reduction for message type & deleted | |||
| 119 | Generation of change pointers for & deactivated in client & | |||
| 120 | Change pointers for message type & active in client & | |||
| 121 | Message type & already being processed | |||
| 122 | An IDoc without a message type was passed to the ALE layer | Space: object requires documentation | ||
| 123 | Place the cursor on a valid line and field | Space: object requires documentation | ||
| 124 | The IDoc type for this message must not be reduced | Space: object requires documentation | ||
| 125 | Message & is not in valid name range | |||
| 126 | Recipient & & & not permissible for this IDoc | |||
| 127 | There is no data maintained in the reduction pool for message type & | |||
| 128 | A server group should be specified with parallel processing | Space: object requires documentation | ||
| 129 | No assignment for & company code & to a & company code. | |||
| 130 | For & business area & no assignment to a & business area. | |||
| 131 | You do not have the authorization for the action | |||
| 132 | Foreground processing and parallel processing are not possible together | Space: object requires documentation | ||
| 133 | No partner profiles (message control) maintained | |||
| 134 | A message type could not be (uniquely) identified | |||
| 135 | No recipient found for message type & in the ALE model | |||
| 136 | Too many recipients found for message type & in the ALE model | |||
| 137 | Wrong partner type & | |||
| 138 | Select packet size larger than 0 | The short text describes the object sufficiently | ||
| 139 | IDoc type has not been entered for message type & | Space: object requires documentation | ||
| 140 | Change pointer creation is currently deactivated | |||
| 141 | Please maintain ALE Customizing via the IMG | |||
| 142 | All event couplings were activated. | |||
| 143 | You have selected all data records. Did you intend to do this? | Space: object requires documentation | ||
| 144 | The tool cannot be executed on your frontend. | |||
| 145 | No data relevant to audit were selected. | Space: object requires documentation | ||
| 146 | Error when locking the audit statistics for & & &. | |||
| 147 | Database error when writing status records for the status &. | |||
| 148 | A change period must be specified. | |||
| 149 | Number range for change pointer has not been maintained. | |||
| 150 | Message type & cannot be reduced | |||
| 151 | Message type & is not relevant to reduction | Space: object requires documentation | ||
| 152 | The change pointer target should not be changed manually | Space: object requires documentation | ||
| 153 | Selection Period for AUDIT IDocs: &1 &2 -> &3 &4 | Space: object requires documentation | ||
| 154 | Customer distribution model & does not exist | |||
| 155 | Customer distribution model & successfully deleted | |||
| 156 | ***** Error messages in area of serialization ***** | |||
| 157 | Object & &: Overtaking process between systems | |||
| 158 | System error occurred when writing to table BDSE | |||
| 159 | Model & is currently being edited by & | |||
| 160 | Warning! You have not done the checkout with the current model | |||
| 161 | Message type & is not within the permitted SAP name range | |||
| 162 | Error locking change pointer for message type &. | |||
| 163 | Message type & cannot be sent with change pointers | |||
| 164 | No parties are interested in the selected data | Space: object requires documentation | ||
| 165 | IDoc must be processed later; expected: &; current: & | Space: object requires documentation | ||
| 166 | System error has occurred writing data to table BDRGIN | Space: object requires documentation | ||
| 167 | Data in table & has been changed and logged in SYSLOG | Space: object requires documentation | ||
| 168 | Changing the registry can interrupt the data transfer | Space: object requires documentation | ||
| 169 | Data could not be entered in table &. (Does entry already exist?) | Space: object requires documentation | ||
| 170 | Data in table & could not be deleted. | Space: object requires documentation | ||
| 171 | System error has occurred writing data to table BDRGOUT. | Space: object requires documentation | ||
| 172 | Please mark at least one option (outbound and/or inbound) | Space: object requires documentation | ||
| 173 | No changes made (don't need to save) | Space: object requires documentation | ||
| 174 | & entries in the registry table & have been deleted/ SYSLOG log | Space: object requires documentation | ||
| 175 | Change pointers for message type &1 are being migrated | Space: object requires documentation | ||
| 176 | ********* Messages for control data ********************************** | Space: object requires documentation | ||
| 177 | Choose 'Utilities -> Comparison' in the following table maintenance view | Space: object requires documentation | ||
| 178 | Report & is not available in this system, you cannot run it. | Space: object requires documentation | ||
| 179 | Data has already been maintained by & and therefore can only be displayed | Space: object requires documentation | ||
| 180 | System error occurred while writing to table BDEOIO_OUT | The short text describes the object sufficiently | ||
| 181 | System error occurred while writing to table BDEOIO_IN | The short text describes the object sufficiently | ||
| 182 | Subsequent IDOC already processed; expected: &; current: & | Space: object requires documentation | ||
| 183 | Invalid ID for sequence processing | Space: object requires documentation | ||
| 184 | ***** Messages for direct model maintenance ***** | Space: object requires documentation | ||
| 185 | Logical system & must not be deleted | Space: object requires documentation | ||
| 186 | Logical system & must not be deleted | Space: object requires documentation | ||
| 187 | Please check entry & & & in table & | |||
| 188 | Model view & already exists | Space: object requires documentation | ||
| 189 | Place the cursor on a model view | Space: object requires documentation | ||
| 190 | Sending system must be different to receiving system | Space: object requires documentation | ||
| 191 | Method & has already been added | Space: object requires documentation | ||
| 192 | Method & has already been defined in the model view & | Space: object requires documentation | ||
| 193 | Place the cursor on a method | Space: object requires documentation | ||
| 194 | Distribution model has been saved | Space: object requires documentation | ||
| 195 | Distribution model is being edited by user & (You can only display it) | Space: object requires documentation | ||
| 196 | This function is not available for this node | Space: object requires documentation | ||
| 197 | Input help is not available for the filter object type & | Space: object requires documentation | ||
| 198 | Method & cannot be filtered | Space: object requires documentation | ||
| 199 | Filter object has already been added | Space: object requires documentation | ||
| 200 | No filter has been defined for method & | Space: object requires documentation | ||
| 201 | Distribution model has not been changed | Space: object requires documentation | ||
| 202 | Message type & has already been added | Space: object requires documentation | ||
| 203 | Message type & has already been defined in the model view & | Space: object requires documentation | ||
| 204 | Place the cursor on a message type | Space: object requires documentation | ||
| 205 | No filter available for message type & | Space: object requires documentation | ||
| 206 | No further filter available for message type & | Space: object requires documentation | ||
| 207 | No filter has been defined for message type & | Space: object requires documentation | ||
| 208 | Reference to message type & has already been defined | Space: object requires documentation | ||
| 209 | End date cannot be earlier than the start date | Space: object requires documentation | ||
| 210 | The valid time period overlaps with that of the model view & | Space: object requires documentation | ||
| 211 | Classes are defined in a separate Customizing transaction | Space: object requires documentation | ||
| 212 | First save the distribution model | Space: object requires documentation | ||
| 213 | Model view & does not exist and has been deleted in target systems | Space: object requires documentation | ||
| 214 | Method & has not been assigned a message type | Space: object requires documentation | ||
| 215 | You are not authorized to carry out this action | Space: object requires documentation | ||
| 216 | Model view has not been specified | Space: object requires documentation | ||
| 217 | Maintenance systems for model view & are not the same | Space: object requires documentation | ||
| 218 | Method & has already been defined in the model view & | Space: object requires documentation | ||
| 219 | Message type & has already been defined in model view & | Space: object requires documentation | ||
| 220 | The distribution model is currently being processed | Space: object requires documentation | ||
| 221 | Model view & has been created | Space: object requires documentation | ||
| 222 | Model view & has been changed | Space: object requires documentation | ||
| 223 | Model view & has been deleted | Space: object requires documentation | ||
| 224 | Model view & must not be maintained in your own system | Space: object requires documentation | ||
| 225 | You are not authorized to create the model view & | Space: object requires documentation | ||
| 226 | You are not authorized to change the model view & | Space: object requires documentation | ||
| 227 | Client and server must be different systems | Space: object requires documentation | ||
| 228 | You are not authorized to delete the model view & | Space: object requires documentation | ||
| 229 | You are not authorized to transport model view & | Space: object requires documentation | ||
| 230 | You are not authorized to distribute the model view & | Space: object requires documentation | ||
| 231 | Distribution model has been edited by user & | Space: object requires documentation | ||
| 232 | Object & is already defined in the model view & | Space: object requires documentation | ||
| 233 | Distribution via classes for object & has already been defined | Space: object requires documentation | ||
| 234 | Reference to method & has already been defined | Space: object requires documentation | ||
| 235 | Model view & already exists and will be completely overwritten | Space: object requires documentation | ||
| 236 | Define the conversion of the logical systems for copying | Space: object requires documentation | ||
| 237 | This message type belongs to object method &.&. | Space: object requires documentation | ||
| 238 | ***** Error messages for "manual input" method ***** | |||
| 239 | IDoc number & does not exist in the database | Space: object requires documentation | ||
| 240 | Function module not allowed: & | Space: object requires documentation | ||
| 241 | IDoc & has not been edited | Space: object requires documentation | ||
| 242 | Error during application input | |||
| 243 | IDoc successfully processed by the application | Space: object requires documentation | ||
| 244 | Previous status & unsuitable | |||
| 245 | IDoc has been flagged for deletion | Space: object requires documentation | ||
| 246 | No event found to trigger | |||
| 247 | No object type found for event | |||
| 248 | Error when opening IDoc: IDoc locked | Space: object requires documentation | ||
| 249 | Error when opening IDoc: IDoc does not exist | Space: object requires documentation | ||
| 250 | Error when opening IDoc: IDoc number is invalid | Space: object requires documentation | ||
| 251 | Error when reading IDoc: IDoc number is invalid | Space: object requires documentation | ||
| 252 | Error when reading IDoc: no data | Space: object requires documentation | ||
| 253 | Error when writing IDoc status: IDoc number is invalid | Space: object requires documentation | ||
| 254 | Error writing IDoc status: Database error | Space: object requires documentation | ||
| 255 | Error when writing IDoc status: Invalid status | Space: object requires documentation | ||
| 256 | Error when writing IDoc status: No status record exists | Space: object requires documentation | ||
| 257 | Error when closing IDoc: IDoc not opened | Space: object requires documentation | ||
| 258 | Error when closing IDoc: Database error | Space: object requires documentation | ||
| 259 | Error when closing IDoc: Incorrect parametrization | Space: object requires documentation | ||
| 260 | Error when closing IDoc: Status not set | Space: object requires documentation | ||
| 261 | Error: Incorrect IDoc status value | Space: object requires documentation | ||
| 262 | Caution: & IDocs have been selected | Space: object requires documentation | ||
| 263 | Error writing IDOC status: IDoc locked | Space: object requires documentation | ||
| 264 | More than one IDoc in packet: Application supports single processing only | Space: object requires documentation | ||
| 265 | Error when opening IDoc: IDoc already opened | Space: object requires documentation | ||
| 266 | IDoc &: status & cannot be processed | Space: object requires documentation | ||
| 267 | The IDocs have no data records | Space: object requires documentation | ||
| 268 | The IDocs do not exist in the database | Space: object requires documentation | ||
| 269 | IDocs not specified | Space: object requires documentation | ||
| 270 | Error: No IDocs to be processed | Space: object requires documentation | ||
| 271 | There is no ALE link object defined. | |||
| 272 | Link object not in IDOC. | |||
| 273 | You are not authorized to display/edit IDoc & | Space: object requires documentation | ||
| 274 | Server group & could not be initialized | Space: object requires documentation | ||
| 275 | Number of maximum attempts to start parallel processes has been exceeded | Space: object requires documentation | ||
| 276 | & of & IDocs could be transferred in parallel for processing | Space: object requires documentation | ||
| 277 | ***** Error messages in area 'ALE error handling' ***** | |||
| 278 | IDoc & does not exist, processing not possible | Space: object requires documentation | ||
| 279 | No details exist for message | |||
| 280 | Error when processing IDoc & | Space: object requires documentation | ||
| 281 | IDoc & flagged for deletion | Space: object requires documentation | ||
| 282 | IDoc & already processed, processing not possible | Space: object requires documentation | ||
| 283 | Status set within ALE/EDI error handling | |||
| 284 | Status reset after editing IDoc | Space: object requires documentation | ||
| 285 | IDoc & can be passed to the port | Space: object requires documentation | ||
| 286 | IDoc & successfully passed to the port | Space: object requires documentation | ||
| 287 | IDoc & can be tranferred to the application | Space: object requires documentation | ||
| 288 | IDoc & successfully passed to the application | Space: object requires documentation | ||
| 289 | More IDocs created from IDoc & | Space: object requires documentation | ||
| 290 | IDoc & successfully processed | Space: object requires documentation | ||
| 291 | IDoc flagged for deletion | Space: object requires documentation | ||
| 292 | More IDocs have been created from the IDoc | Space: object requires documentation | ||
| 293 | No status records exist for IDoc &, processing not possible | Space: object requires documentation | ||
| 294 | Report has reset status | Space: object requires documentation | ||
| 295 | Resetting the status may result in data inconsistency | Space: object requires documentation | ||
| 296 | ***** More messages for input ***** | |||
| 297 | Errors when compiling version: Target structure & & does not match IDoc | Space: object requires documentation | ||
| 298 | IDoc has wrong status | Space: object requires documentation | ||
| 299 | Parameter & missing in container of task & | |||
| 300 | Version & of process code & not allowed for ALE | |||
| 301 | No object for requested IDoc selected for sending | Space: object requires documentation | ||
| 302 | Account group in the IDoc is different | Space: object requires documentation | ||
| 303 | Status records with status 51 after status 53 | |||
| 304 | No status record was passed to ALE by the application | |||
| 305 | No active event coupling for & . & found, no error work items | Space: object requires documentation | ||
| 306 | Status was set automatically | Space: object requires documentation | ||
| 307 | An editing module must be specified | |||
| 308 | Field & does not belong to structure & of infotype & | |||
| 309 | ***** Messages for ALE Customizing ***** | |||
| 310 | Object class & does not exist | |||
| 311 | Table & for object class & does not exist | |||
| 312 | Table & is not an active table | |||
| 313 | Field & does not exist in table & | |||
| 314 | Application object type & is not planned | |||
| 315 | Assignment not allowed | |||
| 316 | Segment type & deactivated for message type & | |||
| 317 | Field & in segment type & deactivated for message type & | |||
| 318 | A check table has not been defined for field & in table & | Space: object requires documentation | ||
| 319 | Structure to infotype & not found | |||
| 320 | Object type & may only be assigned to fields from one segment type | |||
| 321 | Segment type & not defined for message type & | |||
| 322 | Field & in segment type & does not exist | Space: object requires documentation | ||
| 323 | Conversion rule & does not exist | |||
| 324 | Conversion rule & for segment type & does not exist | |||
| 325 | Object type & is assigned to fields from more than one segment type | |||
| 326 | Required segment & may not be filtered | |||
| 327 | Segment type & does not exist | |||
| 328 | Segment type & does not exist in active form | |||
| 329 | Relationship & is unknown | |||
| 330 | Selected function not implemented for message type & | |||
| 331 | Function not possible for the selected line | |||
| 332 | Logical system & does not exist | |||
| 333 | You are logged on to partner system & | Space: object requires documentation | ||
| 334 | Maintenance transaction & not defined in partner system & | |||
| 335 | Purchasing organization & does not exist | |||
| 336 | Vendor & does not exist | |||
| 337 | Material & does not exist | |||
| 338 | RFC destination & does not exist | |||
| 339 | Specify the RFC destination for logical system & | |||
| 340 | Sales organization & does not exist | |||
| 341 | Distribution channel & does not exist | |||
| 342 | Order type & does not exist | |||
| 343 | Partner status & does not exist | |||
| 344 | Language & does not exist | |||
| 345 | Output mode & does not exist | |||
| 346 | Processing & is not defined | |||
| 347 | The maintenance transaction & is not defined in own system & | |||
| 348 | No application object type planned for the function module | |||
| 349 | Cross-system checking is active. | |||
| 350 | Entries for external object types are not allowed (acc. to table T77EO) | |||
| 351 | Cross-system checking is inactive. | |||
| 352 | There are no inspection results available for the selected line. | |||
| 353 | There are no receiver systems defined in the distribution model | Space: object requires documentation | ||
| 354 | Select at least one system. | |||
| 355 | The table for the listing data for message type & is not defined. | Space: object requires documentation | ||
| 356 | Distribution-relevant class type for table & is not defined. | Space: object requires documentation | ||
| 357 | Class & is not defined for class type &. | Space: object requires documentation | ||
| 358 | To display the test results choose 'Edit -> Detail' | Space: object requires documentation | ||
| 359 | ***** Messages for the conversion pre-production => production ***** | Space: object requires documentation | ||
| 360 | Table &: & of & entries in field & converted (client-independent) | Space: object requires documentation | ||
| 361 | Symbols entered are not allowed | |||
| 362 | Table &: & of & entries in field & converted (client-dependent) | Space: object requires documentation | ||
| 363 | The logical system & is already allocated to another system | |||
| 364 | The logical system & is not taken into account in any conversion | |||
| 365 | The logical system name &1 has been converted to name &2 in client &3 | Space: object requires documentation | ||
| 366 | The logical system & has not yet been defined | Space: object requires documentation | ||
| 367 | The logical system name & already exists | Space: object requires documentation | ||
| 368 | The new logical system name & is the same as the old name & | Space: object requires documentation | ||
| 369 | Error creating program & | Space: object requires documentation | ||
| 370 | Syntax error in program & line & | Space: object requires documentation | ||
| 371 | Conversion of logical system name & for name & in client & | Space: object requires documentation | ||
| 372 | Entries in the field Ext are allowed in * lines 01-12 only | |||
| 373 | ***** Messages for ALE Recovery Tool ***** | Space: object requires documentation | ||
| 374 | No system selected | Space: object requires documentation | ||
| 375 | No documentation is available for object & in language &. | Space: object requires documentation | ||
| 376 | Please choose the participating systems first. | Space: object requires documentation | ||
| 377 | Please check system settings before starting the process. | Space: object requires documentation | ||
| 378 | The processing type of some IDocs has not been defined. | Space: object requires documentation | ||
| 379 | IDoc & no longer exists in system &. | Space: object requires documentation | ||
| 380 | The process "Determine recovery objects" has been started in system &. | Space: object requires documentation | ||
| 381 | System & has been reset to the status on & at &. | Space: object requires documentation | ||
| 382 | An error has occurred when checking IDoc dispatch for system &. | Space: object requires documentation | ||
| 383 | Profile ID 'O' (object-oriented) or 'S' (status-oriented) allowed | |||
| 384 | An error has occurred during message transmission. | Space: object requires documentation | ||
| 385 | A tRFC entry with ID && has been deleted in system &. | Space: object requires documentation | ||
| 386 | No data could be selected for partner system &. | Space: object requires documentation | ||
| 387 | ALE recovery tool converts status | Space: object requires documentation | ||
| 388 | No log found | Space: object requires documentation | ||
| 389 | Could not determine any tables | The short text describes the object sufficiently | ||
| 390 | Read the online documentation before carrying out the transaction | Space: object requires documentation | ||
| 391 | No logical system name has been defined for client & | Space: object requires documentation | ||
| 392 | Table &: & of & entries in field & converted (client-dependent) | Space: object requires documentation | ||
| 393 | ***** Messages for BAPIs <-> ALE generating tool ***** | Space: object requires documentation | ||
| 394 | BAPI &.& does not exist in the system | Space: object requires documentation | ||
| 395 | Reference type & is not a structure and therefore it is not allowed | Space: object requires documentation | ||
| 396 | For the message type & there is no IDoc type & | Space: object requires documentation | ||
| 397 | Only some of the objects in the interface have been released | Space: object requires documentation | ||
| 398 | The release of the interface has been partly reset | Space: object requires documentation | ||
| 399 | The objects in the interface have been released | Space: object requires documentation | ||
| 400 | The release of the interface has been reset | Space: object requires documentation | ||
| 401 | Reset of data filtering deactivates all filter functions | Space: object requires documentation | ||
| 402 | Version &2 of segment &3 released for release &1 | Space: object requires documentation | ||
| 403 | Color/shape value must be specified | |||
| 404 | Segment & is not a BAPI segment | Space: object requires documentation | ||
| 405 | The BAPI does not support packet processing in the current release | Space: object requires documentation | ||
| 406 | The ALE outbound interface is incomplete | Space: object requires documentation | ||
| 407 | The inbound ALE interface is incomplete | Space: object requires documentation | ||
| 408 | Parameter & in the function module has no reference field/structure | Space: object requires documentation | ||
| 409 | **** Object & does not belong to the selected category ***** | Space: object requires documentation | ||
| 410 | Method & of object & has not yet been released. | Space: object requires documentation | ||
| 411 | Process has been cancelled by user | Space: object requires documentation | ||
| 412 | You cannot use the tool for dialog method & | Space: object requires documentation | ||
| 413 | Message type & is not available in the system | Space: object requires documentation | ||
| 414 | Line 001 is missing for event & | |||
| 415 | The IDoc interface is not complete for message type & | Space: object requires documentation | ||
| 416 | BAPI & has been called successfully | Space: object requires documentation | ||
| 417 | No existing function module for object & and method & | Space: object requires documentation | ||
| 418 | Message type & already exists in system | Space: object requires documentation | ||
| 419 | Packet & is not available in the System | Space: object requires documentation | ||
| 420 | Function group & does not exist in system | Space: object requires documentation | ||
| 421 | For object & the method & does not exist | Space: object requires documentation | ||
| 422 | There is not an ALE interface for object & and method & | Space: object requires documentation | ||
| 423 | Function module & does not exist | Space: object requires documentation | ||
| 424 | For object & and method & the message type & already exists | Space: object requires documentation | ||
| 425 | Infotype must be specified | |||
| 426 | syntax error in line & of function module & | Space: object requires documentation | ||
| 427 | The BAPI must have a RETURN parameter | Space: object requires documentation | ||
| 428 | & does not exist | Space: object requires documentation | ||
| 429 | & has been released and cannot be deleted | Space: object requires documentation | ||
| 430 | & has been deleted | Space: object requires documentation | ||
| 431 | & has been generated | Space: object requires documentation | ||
| 432 | The field & of structure & has more than 1000 characters | Space: object requires documentation | ||
| 433 | Predecessor & exists | Space: object requires documentation | ||
| 434 | & already exists | Space: object requires documentation | ||
| 435 | & & | Space: object requires documentation | ||
| 436 | Function code must be specified | |||
| 437 | & is the current version and has not been generated | Space: object requires documentation | ||
| 438 | IDoc type & already exists in packet & | Space: object requires documentation | ||
| 439 | Internal syntax error in template &, line & | Space: object requires documentation | ||
| 440 | Function module & already exists in group &. | Space: object requires documentation | ||
| 441 | & does not exist and has not been deleted | Space: object requires documentation | ||
| 442 | Changes in segment & for new definition are not compatible | Space: object requires documentation | ||
| 443 | & already exists and has not been generated | Space: object requires documentation | ||
| 444 | An error has occurred assigning data (&) | Space: object requires documentation | ||
| 445 | & is still being used and has not been deleted | Space: object requires documentation | ||
| 446 | & has not been generated. Further processing is not possible | Space: object requires documentation | ||
| 447 | Infotype & is not allowed for object type & | |||
| 448 | * Messages for the program generating coding for mapping and conversion | Space: object requires documentation | ||
| 449 | The structure & could not be read | Space: object requires documentation | ||
| 450 | Currency amount passed with more than & digits after decimal point | Space: object requires documentation | ||
| 451 | The field & has already been assigned to the SAP code | Space: object requires documentation | ||
| 452 | The input field has an incorrect domain or an incorrect data type | Space: object requires documentation | ||
| 453 | Function module & already exists | Space: object requires documentation | ||
| 454 | Currency amount & & in field & could not be converted | Space: object requires documentation | ||
| 455 | & initial v., currency amount & in & was transferred without a currency | Space: object requires documentation | ||
| 456 | BAPI field contains SAP code. You cannot enter a value. | Space: object requires documentation | ||
| 457 | No ISO code found for the country key & in the field & | Space: object requires documentation | ||
| 458 | Relationship & is not allowed between object types & and & ->F1 | |||
| 459 | No ISO code found for the currency key & in field & | Space: object requires documentation | ||
| 460 | No ISO code found for the quantity unit & in field & | Space: object requires documentation | ||
| 461 | No ISO code found for the language key & in field & | Space: object requires documentation | ||
| 462 | SAP code: Please assign ISO code field on the detail screen | Space: object requires documentation | ||
| 463 | Currency amount: Assign currency fields/parameters on the detail screen | Space: object requires documentation | ||
| 464 | Function module & has been created | Space: object requires documentation | ||
| 465 | No country key found for the ISO code & in field & | Space: object requires documentation | ||
| 466 | No currency key found for ISO code & in field & | Space: object requires documentation | ||
| 467 | No unit of measure found for ISO code & in field & | Space: object requires documentation | ||
| 468 | No language key found for ISO code & in field & | Space: object requires documentation | ||
| 469 | Please enter an external object type | |||
| 470 | An RFC destination could not be specified for the logical system & | Space: object requires documentation | ||
| 471 | No internal key found for the PSP element & in field & | Space: object requires documentation | ||
| 472 | No external key found for the PSP element & in field & | Space: object requires documentation | ||
| 473 | No internal key found for project definition & in field & | Space: object requires documentation | ||
| 474 | No external key found for project definition & in field & | Space: object requires documentation | ||
| 475 | No RFC destination could be determined for the method call. | Space: object requires documentation | ||
| 476 | Queue name for rule & cannot be set up | The short text describes the object sufficiently | ||
| 477 | Message ID could not be created (error during CREATE_UUID) | The short text describes the object sufficiently | ||
| 478 | Please enter a valid type for the related object | |||
| 479 | Get details from previous status records with status & | Space: object requires documentation | ||
| 480 | Cannot process IDocs with syntax errors | Space: object requires documentation | ||
| 481 | Please enter a valid relationship | |||
| 482 | Please specify program and editing routine | |||
| 483 | ***** Messages for CPIC communication to R/2 ***** | |||
| 484 | RFC destination & for port & is not available | |||
| 485 | No STIMEX received, for details refer to R/2 system log or R/2 EDI log | |||
| 486 | No acknowledgement received, details: R/2 system log or R/2 EDI log | |||
| 487 | No connection to SAP gateway (TXCOM dest. &); for details, SAP system log | Space: object requires documentation | ||
| 488 | No connection to R/2 (TXCOM dest. &); for details, see SAP system log | Space: object requires documentation | ||
| 489 | Connection terminated (TXCOM dest. &); details, see R/2 or SAP system log | Space: object requires documentation | ||
| 490 | R/2 reports incorrect transfer, automatic repetition | |||
| 491 | R/2 rejects logon, for details refer to R/2 system log | |||
| 492 | Local error in R/2, error code returned: & | |||
| 493 | RFC destination &: Parameter & is not maintained | |||
| 494 | Segment type &, version &: No segment name found | |||
| 495 | ***** Messages for CCMS Monitoring ***** | Space: object requires documentation | ||
| 496 | There are no suitable transaction IDs | Space: object requires documentation | ||
| 497 | Internal error in & code &, action could not be carried out. | Space: object requires documentation | ||
| 498 | Status & and direction & are not compatible | Space: object requires documentation | ||
| 499 | & TIDs found for this monitoring object but threshold value is & | Space: object requires documentation | ||
| 500 | Select a work area also | Space: object requires documentation | ||
| 501 | & IDocs for this monitoring object found but threshold value is & | Space: object requires documentation | ||
| 502 | Dependent entries in the detail table have also been deleted | Space: object requires documentation | ||
| 503 | Monitoring object & does not yet exist or has not been specified | Space: object requires documentation | ||
| 504 | Monitor object for determining key figure via IDocs of specified criteria | Space: object requires documentation | ||
| 505 | & open change pntrs found for this monitor object - threshold value is & | Space: object requires documentation | ||
| 506 | Number of IDocs for the defined selection criteria | Space: object requires documentation | ||
| 507 | Number of open change pointers using the defined selection criteria | Space: object requires documentation | ||
| 508 | Values <> 0 require a complex selection (see long text) | Space: object requires documentation | ||
| 509 | Collective nodes for ALE monitoring objects of logical system | Space: object requires documentation | ||
| 510 | Number of IDocs change pointers IDocs with the defined selection criteria | Space: object requires documentation | ||
| 511 | Number of tRFC calls to IDocs with the defined selection criteria | Space: object requires documentation | ||
| 512 | ALE CCMS Monitor: & IDocs in tRFC queue but threshold value is & | Space: object requires documentation | ||
| 513 | Problem with CCMS runtime monitoring: function & | Space: object requires documentation | ||
| 514 | ***** _Messages for Modelling ***** | Space: object requires documentation | ||
| 515 | Filter object type & is not valid | Space: object requires documentation | ||
| 516 | Reference to message type & for filter object type & is not valid | Space: object requires documentation | ||
| 517 | Reference to method & for filter object type & is not valid | Space: object requires documentation | ||
| 518 | Reference to message type & is not valid | Space: object requires documentation | ||
| 519 | Distribution using classes is not allowed | Space: object requires documentation | ||
| 520 | System & occurs as the target system several times | Space: object requires documentation | ||
| 521 | Partner systems must not match in BD64 &1 &2 &3 &4 | The short text describes the object sufficiently | ||
| 522 | ***** Messages for the Conversion of Logical System Names ***** | Space: object requires documentation | ||
| 523 | Log for test run: &1 -> &2 in system &3 (initiator &4) | Space: object requires documentation | ||
| 524 | Log for conversion: &1 -> &2 in system &3 (initiator &4) | Space: object requires documentation | ||
| 525 | Maintain another subroutine for program &1 | Space: object requires documentation | ||
| 526 | Table buffer in server synchronized after conversion | Space: object requires documentation | ||
| 527 | Data inconsistency when running program &1, form routine &2 | Space: object requires documentation | ||
| 528 | Converting the logical system name & to the name & | Space: object requires documentation | ||
| 529 | A Process is Running for Test Run &1 -> &2 | Space: object requires documentation | ||
| 530 | Another Process is Running for Conversion &1 -> &2 | Space: object requires documentation | ||
| 531 | No authorization for navigation | Space: object requires documentation | ||
| 532 | RFC destination &1 cannot be accessed under the name &2 | Space: object requires documentation | ||
| 533 | RFC destination &1 currently not accessible | Space: object requires documentation | ||
| 534 | Select a valid node | Space: object requires documentation | ||
| 535 | Conversion can only be started after the test run | Space: object requires documentation | ||
| 536 | The functions are not available in system &1 | Space: object requires documentation | ||
| 537 | The logical system name & has been used by client & | Space: object requires documentation | ||
| 538 | The new logical system name & is assigned to the current client & | Space: object requires documentation | ||
| 539 | Existence check can only be activated for the test run | Space: object requires documentation | ||
| 540 | Synchronize table buffer in server & after the conversion | Space: object requires documentation | ||
| 541 | Table &1 not selected for conversion | Space: object requires documentation | ||
| 542 | Field &1 in table &2 already contains the name &3 | Space: object requires documentation | ||
| 543 | Error in field &1 of table &2. Manual correction required. | Space: object requires documentation | ||
| 544 | An Error has Occurred in Program &1 | Space: object requires documentation | ||
| 545 | Table &1 was not relevant for conversion | Space: object requires documentation | ||
| 546 | &1 Entry/Entries in Field &2 of Table &3 Have Been Converted | Space: object requires documentation | ||
| 547 | &1 entry/ies in field &2 of table &3 are for conversion | Space: object requires documentation | ||
| 548 | New entry &1 has been entered in field &2 of table &3 | Space: object requires documentation | ||
| 549 | New entry &1 has been entered in field &2 of table &3 | Space: object requires documentation | ||
| 550 | Partner profile for &1 &2 &3 has been deactivated | Space: object requires documentation | ||
| 551 | Error when scheduling the batch job for conversion in system &1 | Space: object requires documentation | ||
| 552 | Table &1 was processed by a parallel process | The short text describes the object sufficiently | ||
| 553 | The processs is executed in the background (&1 &2) in system &3 | Space: object requires documentation | ||
| 554 | No processing available for object &1 | Space: object requires documentation | ||
| 555 | Table &1 is excluded from the conversion | Space: object requires documentation | ||
| 556 | ***** Messages for XPRA programs ***** | |||
| 557 | The report & was executed successfully. | Space: object requires documentation | ||
| 558 | Application: & | |||
| 559 | Database error occurred when reading table &. | |||
| 560 | Database error occurred when writing table &. | |||
| 561 | *** Messages for XPRA RBDXBDLT | |||
| 562 | Class type & does not exist in client & | |||
| 563 | Mo message types were found for the classification object & | |||
| 564 | Application ALE (cross-application), client & | |||
| 565 | & & & & | |||
| 566 | Client &: Validity for the ALE distribution model has been initialized | Space: object requires documentation | ||
| 567 | Please specify one object ID only | |||
| 568 | ***Messages for block processing change pointers | Space: object requires documentation | ||
| 569 | Setting the block size of message type & has failed | Space: object requires documentation | ||
| 570 | Incorrect status for block processing with message type & | Space: object requires documentation | ||
| 571 | Resetting block size for message type & has failed | Space: object requires documentation | ||
| 572 | **************** Messages for serialized distribution ********** | Space: object requires documentation | ||
| 573 | Serialization group & does not exist | Space: object requires documentation | ||
| 574 | Error has occurred scheduling check job | Space: object requires documentation | ||
| 575 | Serialization group & is being dispatched | Space: object requires documentation | ||
| 576 | IDocs in serialization group & are still in the tRFC queue | Space: object requires documentation | ||
| 577 | An error has occurred creating/dispatching the control IDoc | Space: object requires documentation | ||
| 578 | & IDoc(s) of message type & have been sent | Space: object requires documentation | ||
| 579 | Message type & has not been specififed for serialization group & | Space: object requires documentation | ||
| 580 | Message types have not been assigned to the serialization group & | Space: object requires documentation | ||
| 581 | Check job has been scheduled for serialization group & for &, & | Space: object requires documentation | ||
| 582 | Error has occurred when determining receiver for SERDAT | Space: object requires documentation | ||
| 583 | No receiver exists for the group & in the distribution model | Space: object requires documentation | ||
| 584 | Inbound processing for serialization group & is not defined | Space: object requires documentation | ||
| 585 | ** Messages for assigning RFC destinations to logical systems | Space: object requires documentation | ||
| 586 | There is already an entry for this key. | Space: object requires documentation | ||
| 587 | Please select a logical system | Space: object requires documentation | ||
| 588 | User is editing the assignments. (You can only display them). | Space: object requires documentation | ||
| 589 | Please select an RFC destination | Space: object requires documentation | ||
| 590 | An RFC destination has already been assigned for method &.& | Space: object requires documentation | ||
| 591 | Entry & does not exist. Check spelling | Space: object requires documentation | ||
| 592 | Error has occurred making remote call to method & in system & | Space: object requires documentation | ||
| 593 | Error &3 for the remote call of method &1 in system &2, message &4 | Space: object requires documentation | ||
| 594 | **************** API message for receiver determination ***************** | Space: object requires documentation | ||
| 595 | There is no filter object type for filter message type & | Space: object requires documentation | ||
| 596 | The business object type for message type & does not exist | Space: object requires documentation | ||
| 597 | No function module has been assigned to the business object type & | Space: object requires documentation | ||
| 598 | Object & with object ID & has not been found | Space: object requires documentation | ||
| 599 | Filter object &1 is missing for determining receiver of message type &2 | Space: object requires documentation | ||
| 600 | Message type & is dependent on itself | Space: object requires documentation | ||
| 601 | Filter object &1 is not valid for the BAPI table parameter &2. | Space: object requires documentation | ||
| 602 | Filter object &1 is not valid for BAPI (&2,&3) | Space: object requires documentation | ||
| 603 | BAPI (&1, &2) is self-dependent | Space: object requires documentation | ||
| 604 | Filter object &1 is missing for determining receiver of BAPI (&1, &2) | Space: object requires documentation | ||
| 605 | More than one receiving system has been specified for the BAPI (&1, &2) | Space: object requires documentation | ||
| 606 | ********** Messages for maintaining hierarchy of BAPI parameters ****** | Space: object requires documentation | ||
| 607 | Tables &1 and &2 have no shared field reference. | Space: object requires documentation | ||
| 608 | Please position the cursor on one table parameter | Space: object requires documentation | ||
| 609 | The hierarchy for the BAPI (&1, &2) already exists. | Space: object requires documentation | ||
| 610 | No hierarchy for BAPI (&1, &2) exists. | Space: object requires documentation | ||
| 611 | Tables &1 and &2 do not have a shared reference field | Space: object requires documentation | ||
| 612 | Table parameter &1 already exists in the hierarchy | Space: object requires documentation | ||
| 613 | Hierarchy has been saved. | Space: object requires documentation | ||
| 614 | Error has occurred when write-accessing database table TBD19. | Space: object requires documentation | ||
| 615 | Hierarchy has been deleted | Space: object requires documentation | ||
| 616 | Note: The ALE interface must be regenerated afterwards | Space: object requires documentation | ||
| 617 | The hierarchy has not been modified | Space: object requires documentation | ||
| 618 | You have not selected field references | Space: object requires documentation | ||
| 619 | Parameter & does not have parent parameters | Space: object requires documentation | ||
| 620 | You cannot modify the hierarchy. Refer to the long text. | Space: object requires documentation | ||
| 621 | Hierarchy has not been created | Space: object requires documentation | ||
| 622 | The table parameter & is not available in the BAPI interface. | Space: object requires documentation | ||
| 623 | Child parameter &1 is not assigned to parent parameter &2. | Space: object requires documentation | ||
| 624 | All the BAPI table parameters in the hierarchy have already been used. | Space: object requires documentation | ||
| 625 | Name of external structure too long for function module generation | Space: object requires documentation | ||
| 626 | ISO code & is not assigned to a country key | |||
| 627 | Country key & has no ISO code | |||
| 628 | ISO code & is not assigned to a currency key in the valid time period | Space: object requires documentation | ||
| 629 | Currency key & does not have an ISO code | Space: object requires documentation | ||
| 630 | Unit of measure & has no ISO code | |||
| 631 | Language key & does not have an ISO code | Space: object requires documentation | ||
| 632 | ISO code & has not been assigned to a language key | Space: object requires documentation | ||
| 633 | For the ISO code &1 there is more than one SAP currency code for ALE | Space: object requires documentation | ||
| 634 | For the ISO code &1 there is no unique SAP currency code for ALE | Space: object requires documentation | ||
| 635 | For the currency code &1 ALE communication is not allowed | Space: object requires documentation | ||
| 636 | You must select a node | Space: object requires documentation | ||
| 637 | The operation cannot be carried out with this node type | Space: object requires documentation | ||
| 638 | Processing not possible - use Transaction SM58 | Space: object requires documentation | ||
| 639 | No IDocs could be selected | Space: object requires documentation | ||
| 640 | The initialization of the logical system has failed | Space: object requires documentation | ||
| 641 | Display of logical system & is not implemented | Space: object requires documentation | ||
| 642 | Error communicating with system & | Space: object requires documentation | ||
| 643 | No IDoc has been selected | Space: object requires documentation | ||
| 644 | Error in namespace prefixes of function; see long text | Space: object requires documentation | ||
| 645 | Name of internal structure too long for function module generation | Space: object requires documentation | ||
| 646 | Please specify a valid value | |||
| 647 | The default position taken from T77S0 already exists in T528B | |||
| 648 | & & & & |
History
| Last changed on/by | 20130531 | SAP | |
| SAP Release Created in |