SAP ABAP Message Class EA (IDoc Basis Messages)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-MID-ALE (Application Component) ALE Integration Technology
⤷
SED (Package) IDoc Interface (Processing, Administration, Definition)
⤷
⤷
Attributes
| Message class | EA | |
| Short Description | IDoc Basis Messages | |
| Changed On | 20140121 | |
| Last Changed At | 103715 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | -->> Display linked objects <<-- | |||
| 2 | Process code & of type & | The short text describes the object sufficiently | ||
| 3 | Old process codes no longer exist in the system | The short text describes the object sufficiently | ||
| 4 | Error when writing statistic record | Space: object requires documentation | ||
| 5 | Report RSEIDOCM is scheduled, but obsolete. | Space: object requires documentation | ||
| 6 | Internal error | Space: object requires documentation | ||
| 7 | Function is only supported for IDoc record types SAP Release 4.x | The short text describes the object sufficiently | ||
| 8 | Queue processing is not supported for version 3.x | The short text describes the object sufficiently | ||
| 9 | Object & not found | Space: object requires documentation | ||
| 10 | No IDocs linked | Space: object requires documentation | ||
| 11 | Object type & object & unknown | Space: object requires documentation | ||
| 12 | --> Messages from function group EDII (IDoc conversion for Office) | |||
| 13 | Object type & is not known | |||
| 14 | IDoc & could not be read | |||
| 15 | Errors occurred during conversion | |||
| 16 | Function module EDI_IDOC_R3I_OUTGOING can only process references | Space: object requires documentation | ||
| 17 | Function module EDI_IDOC_R3I_INCOMING can only process IDoc data | Space: object requires documentation | ||
| 18 | Conversion error: segment too long | |||
| 19 | Length entry & is invalid | Space: object requires documentation | ||
| 20 | '&' File Has Not Been Accepted for Processing | Space: object requires documentation | ||
| 21 | '&' File Has Not Been Accepted for Processing | Space: object requires documentation | ||
| 22 | -> Send messages via Internet | |||
| 23 | Error occurred while sending IDoc via Internet | Space: object requires documentation | ||
| 24 | IDoc could not be sent | Space: object requires documentation | ||
| 25 | IDoc sent via Internet | Space: object requires documentation | ||
| 26 | Office function module showed return code '&'. | |||
| 27 | Created IDoc '&' was sent via the Internet | |||
| 28 | Created IDoc '&' could not be sent via the Internet | |||
| 29 | Receiver port '&' is not an Internet port in the current client | |||
| 30 | -> Outbound procg via background task | Space: object requires documentation | ||
| 31 | IDoc '&' was created and forwarded for transmission | Space: object requires documentation | ||
| 32 | Messages from IDoc processing can be found in application log | Space: object requires documentation | ||
| 33 | Display of all data records not possible | Space: object requires documentation | ||
| 34 | -> Export to R/2 | Space: object requires documentation | ||
| 35 | Error occurred while IDoc '&' was being sent | Space: object requires documentation | ||
| 36 | IDoc '&' was sent to R/2 System | Space: object requires documentation | ||
| 37 | IDoc sent to R/2 System | Space: object requires documentation | ||
| 38 | qRFC used to send IDoc to SAP system | Space: object requires documentation | ||
| 39 | IDoc received via qRFC | Space: object requires documentation | ||
| 40 | Error occurred while IDoc '&' was being sent | Space: object requires documentation | ||
| 41 | IDoc written to file | Space: object requires documentation | ||
| 42 | IDoc '&' written to file | Space: object requires documentation | ||
| 43 | Incorrect parameter combination when calling EDI_OUTPUT_NEW | Space: object requires documentation | ||
| 44 | Internal error: Program &, command & | Space: object requires documentation | ||
| 45 | Error occurred while IDoc '&' was being sent | Space: object requires documentation | ||
| 46 | IDoc '&' sent to SAP system | Space: object requires documentation | ||
| 47 | IDoc sent to SAP system or external program | Space: object requires documentation | ||
| 48 | Error while writing IDoc to file | Space: object requires documentation | ||
| 49 | Error while sending IDoc (conversion error) | Space: object requires documentation | ||
| 50 | Internal error | Space: object requires documentation | ||
| 51 | Internal error - generated file & may not be processed | Space: object requires documentation | ||
| 52 | IDoc sent to Internet address | Space: object requires documentation | ||
| 53 | IDoc '&' sent to Internet address | Space: object requires documentation | ||
| 54 | IDoc '&' transferred to function module '&' | Space: object requires documentation | ||
| 55 | IDoc '&' transferred to ABAP-PSS port | Space: object requires documentation | ||
| 56 | IDoc has been written in XML format in a file | Space: object requires documentation | ||
| 57 | IDoc cannot be sent to an XML port | Space: object requires documentation | ||
| 58 | IDoc cannot be sent in XML format | Space: object requires documentation | ||
| 59 | IDoc sent by HTTP in XML format | Space: object requires documentation | ||
| 60 | Error when sending by HTTP | Space: object requires documentation | ||
| 61 | IDoc '&' has already been received, therefore reception is refused | Space: object requires documentation | ||
| 62 | Communication error when sending with HTTP | Space: object requires documentation | ||
| 63 | The expected 'encoding="UTF-8" has not been sent, therefore refused | Space: object requires documentation | ||
| 64 | -->>Archiving programs<<-- | |||
| 65 | Unknown direction | Space: object requires documentation | ||
| 66 | Enter period with length greater than zero | Space: object requires documentation | ||
| 67 | Time conflict | Space: object requires documentation | ||
| 68 | Only positive entries allowed | Space: object requires documentation | ||
| 69 | No time unit entered | Space: object requires documentation | ||
| 70 | No IDocs found for selection criteria | Space: object requires documentation | ||
| 71 | Settings saved | The short text describes the object sufficiently | ||
| 72 | You can only select relationship types for this function | Space: object requires documentation | ||
| 73 | You can only select message types for this function | Space: object requires documentation | ||
| 74 | All Message Types are Excluded for this Relationship Type | Space: object requires documentation | ||
| 75 | IDoc queue '&1' of sender '&2' not processed completely | The short text describes the object sufficiently | ||
| 76 | IDoc set to queue status again after edit | The short text describes the object sufficiently | ||
| 77 | IDoc archived | |||
| 78 | IDoc reloaded | |||
| 79 | Error while setting status for container '&' with IDoc links | Space: object requires documentation | ||
| 80 | No queue entries selected | The short text describes the object sufficiently | ||
| 81 | Select an IDoc number by clicking a link | Space: object requires documentation | ||
| 82 | Select a queue name by clicking a link | The short text describes the object sufficiently | ||
| 83 | All IDocs in queue '&' sent to receiving port '&' by qRFC | The short text describes the object sufficiently | ||
| 84 | Queue '&' sent to port '&' in separate task | The short text describes the object sufficiently | ||
| 85 | IDoc '&' no longer in IDoc outbound queue. Refresh the queue. | Space: object requires documentation | ||
| 86 | IDoc removed from outbound queue | Space: object requires documentation | ||
| 87 | IDoc &1 removed from outbound queue &2 | The short text describes the object sufficiently | ||
| 88 | IDoc &1 set to status '31' and removed from outbound queue &2 | The short text describes the object sufficiently | ||
| 89 | IDoc '&' no longer in IDoc inbound queue. Refresh the queue. | The short text describes the object sufficiently | ||
| 90 | IDoc removed from inbound queue | Space: object requires documentation | ||
| 91 | IDoc &1 set to status '68' and removed from inbound queue &2 | The short text describes the object sufficiently | ||
| 92 | IDoc &1 removed from inbound queue &2 | The short text describes the object sufficiently | ||
| 93 | Function module for processing queue missing in target system | Space: object requires documentation | ||
| 94 | Rule name '&1' does not exist | Space: object requires documentation | ||
| 95 | Command file not maintained | Space: object requires documentation | ||
| 96 | Also maintain command file for logical file | Space: object requires documentation | ||
| 97 | -> Further messages port maintenance | Space: object requires documentation | ||
| 98 | No folder exists for saved folder ID | Space: object requires documentation | ||
| 99 | Access to a stored directory not possible in this environment | Space: object requires documentation | ||
| 100 | Logical directory '&' has not been defined in the SAP System | Space: object requires documentation | ||
| 101 | Also maintain the function module for the logical directory | Space: object requires documentation | ||
| 102 | The possible entry is only possible for 'logical directory' | Space: object requires documentation | ||
| 103 | Enter a logical directory | Space: object requires documentation | ||
| 104 | Port & already exists and could not be created | Space: object requires documentation | ||
| 105 | Save the port first! | Space: object requires documentation | ||
| 106 | Port '&' was created and not saved! Deletion not possible! | Space: object requires documentation | ||
| 107 | -> continue FuGr EDI1 | Space: object requires documentation | ||
| 108 | IDoc '&' should be opened again in EDIT mode | Space: object requires documentation | ||
| 109 | No data records to be edited could be found for IDoc '&' | Space: object requires documentation | ||
| 110 | IDoc '&' has no data record with number '&' | Space: object requires documentation | ||
| 111 | Error while updating data records for IDoc '&' | Space: object requires documentation | ||
| 112 | Direction cannot be changed when modifying control record | Space: object requires documentation | ||
| 113 | This IDoc cannot be changed | Space: object requires documentation | ||
| 114 | This IDoc has been generated through a test transaction | Space: object requires documentation | ||
| 115 | This IDoc data record cannot be edited - field is too long | Space: object requires documentation | ||
| 116 | You Are Not Authorized to Edit This IDoc | Space: object requires documentation | ||
| 117 | No IDocs Were Transferred for Display | Space: object requires documentation | ||
| 118 | IDoc created without syntax check | The short text describes the object sufficiently | ||
| 119 | It was not possible to send any IDoc | Space: object requires documentation | ||
| 120 | '&' IDocs in queue '&' were sent by qRFC to destination '&' | The short text describes the object sufficiently | ||
| 121 | You will find detailed information in the previous status records | The short text describes the object sufficiently | ||
| 122 | '&' IDoc(s) set to status '31' and removed from outbound queue | The short text describes the object sufficiently | ||
| 123 | '&' IDoc(s) set to status '68' and removed from inbound queue | The short text describes the object sufficiently | ||
| 124 | '&' IDoc(s) removed from outbound queue | The short text describes the object sufficiently | ||
| 125 | '&' IDoc(s) removed from inbound queue | The short text describes the object sufficiently | ||
| 126 | --> Where-used list for segments | Space: object requires documentation | ||
| 127 | Where-used list for IDoc segments | Space: object requires documentation | ||
| 128 | System & Date & Time & | Space: object requires documentation | ||
| 129 | Segment type & (&) | Space: object requires documentation | ||
| 130 | Use in basic types: | Space: object requires documentation | ||
| 131 | & (&) | Space: object requires documentation | ||
| 132 | Use in extensions: | Space: object requires documentation | ||
| 133 | All segments | Space: object requires documentation | ||
| 134 | Unused segments | Space: object requires documentation | ||
| 135 | Used segments | Space: object requires documentation | ||
| 136 | Immediate Processing Not Possible | Space: object requires documentation | ||
| 137 | Immediate Processing Was Not Possible | Space: object requires documentation | ||
| 138 | Immediate Processing was Canceled | Space: object requires documentation | ||
| 139 | Immediate Processing Was Not Possible | Space: object requires documentation | ||
| 140 | Immediate Processing was Canceled | Space: object requires documentation | ||
| 141 | Immediate Processing Was Not Possible | Space: object requires documentation | ||
| 142 | Immediate Processing in Job '&' | Space: object requires documentation | ||
| 143 | Immediate processing through bgRRC was triggered | Space: object requires documentation | ||
| 144 | User &1 is already processing the configuration | The short text describes the object sufficiently | ||
| 145 | --> Messages from AFTER_IMP-Methods for IDoc types | Space: object requires documentation | ||
| 146 | Program ID &, object type & not processed | Space: object requires documentation | ||
| 147 | Object name is blank | Space: object requires documentation | ||
| 148 | Entries for & in table EDISYN were deleted | Space: object requires documentation | ||
| 149 | No entries for & had to be deleted | Space: object requires documentation | ||
| 150 | >>>> Messages from EDIJ/ Automatic creation of IDoc segments | |||
| 151 | Error while creating table '&' entry '&' | Space: object requires documentation | ||
| 152 | Error while changing table '&' entry '&' | Space: object requires documentation | ||
| 153 | Error while deleting table '&' entry '&' | Space: object requires documentation | ||
| 154 | Internal error & | |||
| 155 | Source structure '&' in ABAP/4 Dictionary has status '&' | |||
| 156 | Segment with description '&' already exists in ABAP/4 Dictionary | |||
| 157 | Source structure '&' is unknown in ABAP Repository | Space: object requires documentation | ||
| 158 | Source structure '&' has no fields in ABAP Repository | Space: object requires documentation | ||
| 159 | Target structure '&' exceeds maximum length of 1000 bytes | |||
| 160 | Segment locked in transport '&', order '&' | |||
| 161 | Segment placed in transport '&', order '&' | |||
| 162 | Name of source structure not entered | |||
| 163 | Dictionary structure '&' could not be created | Space: object requires documentation | ||
| 164 | Creation of IDoc segment for source structure '&' canceled | |||
| 165 | Activation of IDoc segment for source structure '&' canceled | |||
| 166 | Creation of IDoc segment for source struct. '&' completed successfully | |||
| 167 | Unknown ABAP data type '&' | |||
| 168 | Deletion of '&' was not completed successfully | |||
| 169 | Name of source structure '&' could not be transferred completely | |||
| 170 | Table entries for segment for structure '&' exist already | |||
| 171 | Maintain the fields of segment & in the segment editor. | Space: object requires documentation | ||
| 172 | Processing canceled by user | Space: object requires documentation | ||
| 173 | Enter an object name | Space: object requires documentation | ||
| 174 | Basic type '&' is unknown | Space: object requires documentation | ||
| 175 | Extension '&' is unknown | Space: object requires documentation | ||
| 176 | Extended basic type '&' is unknown | Space: object requires documentation | ||
| 177 | Development class & has integration system & | Space: object requires documentation | ||
| 178 | Segment & exists already | Space: object requires documentation | ||
| 179 | Error while creating segment & | Space: object requires documentation | ||
| 180 | Development class & is unknown | Space: object requires documentation | ||
| 181 | Length determination for data element & failed | Space: object requires documentation | ||
| 182 | Data element & is unknown | Space: object requires documentation | ||
| 183 | Data element & is not active | Space: object requires documentation | ||
| 184 | Segment '&' : Internal error & | Space: object requires documentation | ||
| 185 | Segment '&' : Dictionary structure unknown | Space: object requires documentation | ||
| 186 | Error while deleting segment & | Space: object requires documentation | ||
| 187 | Segment & does not exist | Space: object requires documentation | ||
| 188 | Error while changing segment & | Space: object requires documentation | ||
| 189 | Activate segment & in dictionary failed | Space: object requires documentation | ||
| 190 | Change segment & in Dictionary failed | Space: object requires documentation | ||
| 191 | Error while changing segment & | Space: object requires documentation | ||
| 192 | Error during existence check for segment & | Space: object requires documentation | ||
| 193 | Error while releasing segment & | Space: object requires documentation | ||
| 194 | Transferred structure has different field names, field & | Space: object requires documentation | ||
| 195 | Segment definition & unknown | Space: object requires documentation | ||
| 196 | Segment definition & has been released and cannot be deleted | Space: object requires documentation | ||
| 197 | Segment type cannot have same name as source structure & | Space: object requires documentation | ||
| 198 | No segment type entered | Space: object requires documentation | ||
| 199 | No segment structure entered | Space: object requires documentation | ||
| 200 | Last segment definition & not released | Space: object requires documentation | ||
| 201 | Segment & defined locally, development class & | Space: object requires documentation | ||
| 202 | First segment definition in segment & cannot be deleted | Space: object requires documentation | ||
| 203 | Segment definition & has been released and cannot be deleted | Space: object requires documentation | ||
| 204 | Last segment definition & has been released and cannot be changed | Space: object requires documentation | ||
| 205 | Name range violation : Name & not permitted in & system | Space: object requires documentation | ||
| 206 | Segment &1 is unknown in Release &2/&3 | Space: object requires documentation | ||
| 207 | External segment name & cannot be interpreted | Space: object requires documentation | ||
| 208 | Error while resetting release of segment & | Space: object requires documentation | ||
| 209 | Object directory entry with development class & could not be generated | Space: object requires documentation | ||
| 210 | Transferred structure longer than existing structure, line & | Space: object requires documentation | ||
| 211 | Transferred structure contains different data element, line & | Space: object requires documentation | ||
| 212 | Maximum length of segment is 1000 characters, current length is & | Space: object requires documentation | ||
| 213 | Error while generating check log for segment & | Space: object requires documentation | ||
| 214 | Segment definition for current release &1/&2 already exists | Space: object requires documentation | ||
| 215 | Change segment table for & failed | Space: object requires documentation | ||
| 216 | Error while changing segment definitions for & | Space: object requires documentation | ||
| 217 | Error while updating segment table for & | Space: object requires documentation | ||
| 218 | Name range violation : Name & not permitted in & system | Space: object requires documentation | ||
| 219 | Name '&' contains no valid prefix | Space: object requires documentation | ||
| 220 | Name '&' does not correspond to naming convention | Space: object requires documentation | ||
| 221 | Error in transport connection | Space: object requires documentation | ||
| 222 | No entry in conversion table for external segment name &1 | Space: object requires documentation | ||
| 223 | No entry in conversion table for external segment name &1 | Space: object requires documentation | ||
| 224 | Unknown IDoc control record type: '&' | Space: object requires documentation | ||
| 225 | Segment definition & already exists for Release & | Space: object requires documentation | ||
| 226 | No object dictionary entry available for & | Space: object requires documentation | ||
| 227 | '&' entries changed in segment table | Space: object requires documentation | ||
| 228 | New segment definition '&' has no additional fields | Space: object requires documentation | ||
| 229 | A released definition already exists for '&3' in Release &1/&2 | Space: object requires documentation | ||
| 230 | Released segment definitions already exist for segment & | Space: object requires documentation | ||
| 231 | Current segment definition is already released for segment & | Space: object requires documentation | ||
| 232 | The DTD cannot be generated | Space: object requires documentation | ||
| 233 | The DTD cannot be generated | Space: object requires documentation | ||
| 234 | --> Messages from forwarding (FuGr EDIFORWARD) | Space: object requires documentation | ||
| 235 | Outbound IDoc & sent to system & | Space: object requires documentation | ||
| 236 | -> Unicode outbound processing | Space: object requires documentation | ||
| 237 | Conversion error occurred for OPEN DATASET | Space: object requires documentation | ||
| 238 | IDoc file with replacement character | Space: object requires documentation | ||
| 239 | Segment & was written in the file with the replacement character | Space: object requires documentation | ||
| 240 | Control record was written in the file with the replacement character | Space: object requires documentation | ||
| 241 | Could not write IDoc to file | Space: object requires documentation | ||
| 242 | Could not write IDoc to file | Space: object requires documentation | ||
| 243 | *** Messages for SAPLEDID | |||
| 244 | No segment definition exists for segment type & | Space: object requires documentation | ||
| 245 | Segment type & does not exist | Space: object requires documentation | ||
| 246 | Structure of IDoc type & could not be found | Space: object requires documentation | ||
| 247 | IDoc type &, object type & is unknown | Space: object requires documentation | ||
| 248 | Error reading fixed values from table & field & | |||
| 249 | Object type & is unknown | |||
| 250 | IDoc type & is unknown in Release & | Space: object requires documentation | ||
| 251 | Description for IDoc basic type & not found | Space: object requires documentation | ||
| 252 | Segment & is unknown | |||
| 253 | Structure of segment & is unknown | |||
| 254 | Segment & is inconsistent | |||
| 255 | Segment &1 is unknown in Release &2/&3 | Space: object requires documentation | ||
| 256 | Data for segments for IDoc type &, object type & is incomplete | Space: object requires documentation | ||
| 257 | Structure of IDoc type &, object type & is unknown | Space: object requires documentation | ||
| 258 | Attributes for segment & is unknown | |||
| 259 | Field in segment & is unknown | |||
| 260 | Domain & for data element & is unknown | |||
| 261 | Error reaading IDoc record structures | |||
| 262 | Internal error in API for IDoc documentation tools | |||
| 263 | Export canceled by user | Space: object requires documentation | ||
| 264 | Error opening file '&' in directory '&' | |||
| 265 | Error while writing to file '&' in directory '&' | |||
| 266 | Error while creating file '&' in directory '&' | |||
| 267 | '&' is not an IDoc segment | |||
| 268 | Inconsistent data for IDoc type '&' | |||
| 269 | Export to directory '&', file(s) '&' completed successfully | |||
| 270 | Export to directory '&', file '&.h' completed successfully | |||
| 271 | Record type & unknown | |||
| 272 | Version & unknown | |||
| 273 | No IDoc types for SAP Release '&' found | |||
| 274 | Texts for IDoc types could not be read in language '&'. | |||
| 275 | Required format '&' is not supported | |||
| 276 | Some data not found | |||
| 277 | Invalid directory '&' | |||
| 278 | Presentation server error | |||
| 279 | Directory '&' could not be checked | |||
| 280 | No valid working directory found | |||
| 281 | No file name entered | |||
| 282 | List of IDoc types in HTML format created in directory '&', file '&' | Space: object requires documentation | ||
| 283 | Foreign key for structure '&1', field '&2' cannot be evaluated | Space: object requires documentation | ||
| 284 | Data element '&1' of field '&2' unknown | Space: object requires documentation | ||
| 285 | Extension &1 is not linked to any basic types | Space: object requires documentation | ||
| 286 | Extension &1 is not assigned to basic type &2 | Space: object requires documentation | ||
| 287 | Description for extension & not found | Space: object requires documentation | ||
| 288 | The format selected is not supported for the objects selected | Space: object requires documentation | ||
| 289 | Make a selection | Space: object requires documentation | ||
| 290 | Errors occurred in the control framework | Space: object requires documentation | ||
| 291 | Object name missing (enter a name) | Space: object requires documentation | ||
| 292 | ----> Segments consistency check | Space: object requires documentation | ||
| 293 | Segment &1 has repository structure in status &2 | Space: object requires documentation | ||
| 294 | Entries missing in table of &2 for segment &1 | Space: object requires documentation | ||
| 295 | Last user to make changes in repository &1, last user to change seg. &2 | Space: object requires documentation | ||
| 296 | Time of last change in repository &1, time of last change to segment &2 | Space: object requires documentation | ||
| 297 | No. of fields in repository structure &1, no. of fields in segment &2 | Space: object requires documentation | ||
| 298 | Field name in repository '&1', field name in segment '&2', position &3 | Space: object requires documentation | ||
| 299 | Field &1: External length &2 smaller than &3 for appl. data element &4 | Space: object requires documentation | ||
| 300 | Field &1: External length &2 larger than &3 for appl. data element &4 | Space: object requires documentation | ||
| 301 | Segment version &1 contains more/less fields (&2) than structure (&3) | Space: object requires documentation | ||
| 302 | Inconsistent overall length in segment version &1 | Space: object requires documentation | ||
| 303 | Segment version & not released | Space: object requires documentation | ||
| 304 | Segment & has no short text | Space: object requires documentation | ||
| 305 | Repository structure missing for segment & | Space: object requires documentation | ||
| 306 | Segment & consistent | Space: object requires documentation | ||
| 307 | Check segment & | Space: object requires documentation | ||
| 308 | Segment & has no object dictionary entry | Space: object requires documentation | ||
| 309 | Object dictionary entry for segment & has no development class | Space: object requires documentation | ||
| 310 | Field &1, data element &2 with length problem | Space: object requires documentation | ||
| 311 | Field &1, data element &2 with length problem | Space: object requires documentation | ||
| 312 | & is an SAP segment | Space: object requires documentation | ||
| 313 | Entries exist in table of &2 for segment &1 | Space: object requires documentation | ||
| 314 | Segment & consistent with warnings | Space: object requires documentation | ||
| 315 | Segment & is inconsistent | Space: object requires documentation | ||
| 316 | Inconsistency in segment structure table, segment '&1', field '&2' | Space: object requires documentation | ||
| 317 | Could not write IDoc inbound queue | The short text describes the object sufficiently | ||
| 318 | Queue &1 started. &2 IDoc(s) posted successfully. | Space: object requires documentation | ||
| 319 | Queue & started | The short text describes the object sufficiently | ||
| 320 | Queue & not started. First IDoc had error status. | The short text describes the object sufficiently | ||
| 321 | Queue &1 started. &2 of &3 IDoc(s) processed. | The short text describes the object sufficiently | ||
| 322 | Incorrect interface of function module | The short text describes the object sufficiently | ||
| 323 | IDocs are stored in the queue | The short text describes the object sufficiently | ||
| 324 | &1 IDoc(s) in queue &2 given error status and deleted from queue | The short text describes the object sufficiently | ||
| 325 | &1 IDoc(s) in queue &2 deleted from queue | The short text describes the object sufficiently | ||
| 326 | Problem with SOAP class | Space: object requires documentation | ||
| 327 | No IDoc saved in target system (SOAP HTTP) | Space: object requires documentation | ||
| 328 | IDoc sent with SOAP HTTP | Space: object requires documentation | ||
| 329 | No XML fragment specified | The short text describes the object sufficiently | ||
| 330 | >>> Messages for IDoc test tool <<< | |||
| 331 | IDoc type & does not exist | |||
| 332 | Internal error while selecting IDoc types | |||
| 333 | No IDoc selection possible (too many IDoc types). Please enter directly. | |||
| 334 | IDoc tree could not be constructed (internal error) | |||
| 335 | No segments in clipboard | |||
| 336 | IDoc & was saved but cannot or should not be processed | Space: object requires documentation | ||
| 337 | Function modules up to Release 2.x are not supported | |||
| 338 | Interface for function & is incorrect | |||
| 339 | & is not a valid function module | |||
| 340 | IDoc & was saved and processed by function & | |||
| 341 | IDoc & contains errors. No hierarchies can be displayed. | |||
| 342 | Segment(s) transferred to clipboard | |||
| 343 | Following IDoc type serves as template: & | |||
| 344 | Pattern IDoc written to database. Not defined for processing. | Space: object requires documentation | ||
| 345 | IDoc saved to file | |||
| 346 | IDoc saved to file and file forwarded for IDoc inbound processing | |||
| 347 | Error trying to write file (OPEN_DATASET) | Space: object requires documentation | ||
| 348 | Error while writing IDoc data to file | |||
| 349 | Entry for no. of IDocs is missing. IDoc written to file. | Space: object requires documentation | ||
| 350 | Entry for no. of IDocs is missing. IDoc written to file. | Space: object requires documentation | ||
| 351 | No authorization for writing to file & | Space: object requires documentation | ||
| 352 | IDoc & was saved but cannot or should not be sent | Space: object requires documentation | ||
| 353 | IDoc created using test tool by user & | Space: object requires documentation | ||
| 354 | IDoc no. & saved in database | Space: object requires documentation | ||
| 355 | No authorization to open file & | Space: object requires documentation | ||
| 356 | & is processed by altogether & IDocs. | Space: object requires documentation | ||
| 357 | Check time format | Space: object requires documentation | ||
| 358 | No IDoc was found in file &. | Space: object requires documentation | ||
| 359 | The IDoc syntax is correct. | Space: object requires documentation | ||
| 360 | Inbound IDoc: CCMS statistic update failed. | Space: object requires documentation | ||
| 361 | No file is generated as the status and IDoc numbers are empty. | Space: object requires documentation | ||
| 362 | Conversion error when reading from the file '&' | Space: object requires documentation | ||
| 363 | Use IDoc Test Tool in a productive client | The short text describes the object sufficiently | ||
| 364 | Characters cannot be displayed in the requested code page. | Space: object requires documentation | ||
| 365 | --> Messages from API for IDoc types | Space: object requires documentation | ||
| 366 | Basic type & is locked by user & | Space: object requires documentation | ||
| 367 | Extension & is locked by user & | Space: object requires documentation | ||
| 368 | Lock failed (system error) | Space: object requires documentation | ||
| 369 | You have no authorization for basic types (activity &) | Space: object requires documentation | ||
| 370 | You have no authorization for extensions (activity &) | Space: object requires documentation | ||
| 371 | Extension & does not exist | Space: object requires documentation | ||
| 372 | Basic type & does not exist | Space: object requires documentation | ||
| 373 | Segments are not numbered sequentially | Space: object requires documentation | ||
| 374 | Basic type & contains no segments | Space: object requires documentation | ||
| 375 | Extension & contains no segments | Space: object requires documentation | ||
| 376 | Extension & is already released | Space: object requires documentation | ||
| 377 | Basic type & is already released | Space: object requires documentation | ||
| 378 | Predecessor & of extension & is not released | Space: object requires documentation | ||
| 379 | Predecessor & of basic type & is not released | Space: object requires documentation | ||
| 380 | Basic type & could not be changed | Space: object requires documentation | ||
| 381 | Basic type & could not be created | Space: object requires documentation | ||
| 382 | Extension & could not be changed | Space: object requires documentation | ||
| 383 | Extension & could not be created | Space: object requires documentation | ||
| 384 | Extension & has been released and cannot be deleted | Space: object requires documentation | ||
| 385 | Basic type & has been released and cannot be deleted | Space: object requires documentation | ||
| 386 | & already has successor & | |||
| 387 | & already has successor & | |||
| 388 | Extension & could not be deleted | Space: object requires documentation | ||
| 389 | Basic type & could not be deleted | Space: object requires documentation | ||
| 390 | Basic type & has successor & | Space: object requires documentation | ||
| 391 | Basic type & is not released | Space: object requires documentation | ||
| 392 | Extension & has successor & | Space: object requires documentation | ||
| 393 | Extension & is not released | Space: object requires documentation | ||
| 394 | Entry in EDBAS for basic type & is inconsistent | Space: object requires documentation | ||
| 395 | Entry in EDCIM for extension & is inconsistent | Space: object requires documentation | ||
| 396 | No basic types exist in system | Space: object requires documentation | ||
| 397 | No suitable basic types found for extension & | Space: object requires documentation | ||
| 398 | Extensions are available for basic type & | Space: object requires documentation | ||
| 399 | Check basic type & | Space: object requires documentation | ||
| 400 | Check extension & | Space: object requires documentation | ||
| 401 | Extension & exists | Space: object requires documentation | ||
| 402 | Basic type & exists | Space: object requires documentation | ||
| 403 | Segment & exists | Space: object requires documentation | ||
| 404 | Several basic types are assigned to extension & (see long text) | Space: object requires documentation | ||
| 405 | Basic type & exists already | Space: object requires documentation | ||
| 406 | Extension & exists already | Space: object requires documentation | ||
| 407 | Segment type & is still used | Space: object requires documentation | ||
| 408 | & is an SAP basic type | Space: object requires documentation | ||
| 409 | Basic type & has been generated and cannot be deleted | Space: object requires documentation | ||
| 410 | Extension & has been generated and cannot be deleted | Space: object requires documentation | ||
| 411 | View & exists already | Space: object requires documentation | ||
| 412 | View & could not be created | Space: object requires documentation | ||
| 413 | View & does not exist | Space: object requires documentation | ||
| 414 | View & is locked by user & | Space: object requires documentation | ||
| 415 | View & could not be modified | Space: object requires documentation | ||
| 416 | View & could not be deleted | Space: object requires documentation | ||
| 417 | View & refers to basic type &, which has not been released | Space: object requires documentation | ||
| 418 | View & refers to extension &, which has not been released | Space: object requires documentation | ||
| 419 | Extension & is not linked to basic type & | Space: object requires documentation | ||
| 420 | Segment & cannot be included in view | Space: object requires documentation | ||
| 421 | View already contains this segment | Space: object requires documentation | ||
| 422 | View does not contain this segment | Space: object requires documentation | ||
| 423 | Segment & cannot be deleted from this view | Space: object requires documentation | ||
| 424 | You do not have authorization for views (activity &) | Space: object requires documentation | ||
| 425 | Consider the consequences of your changes to &, see long text | Space: object requires documentation | ||
| 426 | Enter a valid application | |||
| 427 | Combination of application and output type does not exist | |||
| 428 | Assignments of basic type & to views are available | Space: object requires documentation | ||
| 429 | Assignments of extension & to views are available | Space: object requires documentation | ||
| 430 | Basic type for a released extension is to be changed | Space: object requires documentation | ||
| 431 | The release of the basis types cannot be reset | Space: object requires documentation | ||
| 432 | The release of the extension cannot be reset | Space: object requires documentation | ||
| 433 | --> Additional messages from FuGr EDI8 (E0) | Space: object requires documentation | ||
| 434 | Extension & is already assigned to basic type & | Space: object requires documentation | ||
| 435 | Extension & is not assigned to any basic type | Space: object requires documentation | ||
| 436 | Enter extension | Space: object requires documentation | ||
| 437 | Object & lies in customer name range | Space: object requires documentation | ||
| 438 | Object & lies in SAP name range | Space: object requires documentation | ||
| 439 | --> Messages from conversion of IDoc types and messages | Space: object requires documentation | ||
| 440 | Basic type & exists already | Space: object requires documentation | ||
| 441 | Short extension name & should not exist as extension | Space: object requires documentation | ||
| 442 | Short logical message type & should not exist as message type | Space: object requires documentation | ||
| 443 | & status process code(s) would be changed | The short text describes the object sufficiently | ||
| 444 | & status process code(s) changed | The short text describes the object sufficiently | ||
| 445 | --> Messages from fast entry for partner profiles | Space: object requires documentation | ||
| 446 | Invalid value '&' for execution mode PI_MODE | Space: object requires documentation | ||
| 447 | No templates available for partner type & | Space: object requires documentation | ||
| 448 | Possible entries for partner number & exist already | Space: object requires documentation | ||
| 449 | No entries made | Space: object requires documentation | ||
| 450 | 1 entry made | Space: object requires documentation | ||
| 451 | & entries were made | Space: object requires documentation | ||
| 452 | ALE port '&' is already defined for logical destination '&' | Space: object requires documentation | ||
| 453 | No authorization for deleting file & | The short text describes the object sufficiently | ||
| 454 | Determination of inbound queue name was not successful | The short text describes the object sufficiently | ||
| 455 | One of the passed parameters was empty | The short text describes the object sufficiently | ||
| 456 | Formed queue name is too long: &1 | The short text describes the object sufficiently | ||
| 457 | Inbound destination &1 has too many prefixes | The short text describes the object sufficiently | ||
| 458 | -> Messages from API for ports or from port maintenance | Space: object requires documentation | ||
| 459 | Port '&' of type '&' does not exist | Space: object requires documentation | ||
| 460 | Port '&' to be deleted of type '&' does not exist | Space: object requires documentation | ||
| 461 | Detailed data for port '&' of type '&' is not available | Space: object requires documentation | ||
| 462 | Database error while deleting port '&' | Space: object requires documentation | ||
| 463 | Port '&' to be copied of type '&' does not exist | Space: object requires documentation | ||
| 464 | Port '&' is already available or a system error occurred during insertion | Space: object requires documentation | ||
| 465 | No port name entered for new port | Space: object requires documentation | ||
| 466 | Port '&' to be found does not exist | Space: object requires documentation | ||
| 467 | tRFC ports cannot be copied! | Space: object requires documentation | ||
| 468 | Logical destination '&' is not compatible with port version '&' | Space: object requires documentation | ||
| 469 | Function module '&' does not exist | Space: object requires documentation | ||
| 470 | Position the cursor on the appropriate field to access & | Space: object requires documentation | ||
| 471 | No test, as RFC destination '&' is maintained for start on '&' | Space: object requires documentation | ||
| 472 | Carry out test using 'Connection test' from RFC destination '&' | Space: object requires documentation | ||
| 473 | No test possible as directory '&' is not available or cannot be read | Space: object requires documentation | ||
| 474 | RFC destination is not maintained | Space: object requires documentation | ||
| 475 | Logical directory '&' has not been defined for operating system '&' | Space: object requires documentation | ||
| 476 | Function module '&' has not been defined for '&'. | Space: object requires documentation | ||
| 477 | Access to directory possible from current application server | Space: object requires documentation | ||
| 478 | ---> Additional messages from process code maintenance | Space: object requires documentation | ||
| 479 | Processing via function module -> ID remains blank | Space: object requires documentation | ||
| 480 | Processing type changed! Please enter ID again! | Space: object requires documentation | ||
| 481 | Processing without ALE via function module is not possible | Space: object requires documentation | ||
| 482 | Enter a valid port version | Space: object requires documentation | ||
| 483 | Also maintain process code allocation for the logical message. | Space: object requires documentation | ||
| 484 | Also maintain process code allocation for the logical message. | Space: object requires documentation | ||
| 485 | Please do not use old process technology! | Space: object requires documentation | ||
| 486 | The ALE table is not yet maintained for process code & ! | Space: object requires documentation | ||
| 487 | When saving, process code '&' is also deleted in the ALE table | Space: object requires documentation | ||
| 488 | --> IDoc API | Space: object requires documentation | ||
| 489 | EDI: Receiver port in control record is default | Space: object requires documentation | ||
| 490 | EDI: Receiver port in control record is invalid | Space: object requires documentation | ||
| 491 | EDI: Receiver partner type in control record is default | Space: object requires documentation | ||
| 492 | EDI: Receiver partner number in control record is default | Space: object requires documentation | ||
| 493 | EDI: Sender port in control record is invalid | Space: object requires documentation | ||
| 494 | EDI: Sender port in control record is default | Space: object requires documentation | ||
| 495 | EDI: Sender partner type in control record is default | Space: object requires documentation | ||
| 496 | EDI: Sender partner number in control record is default | Space: object requires documentation | ||
| 497 | EDI: Field MANDT in data record is invalid | Space: object requires documentation | ||
| 498 | EDI: Field DOCNUM in data record is invalid | Space: object requires documentation | ||
| 499 | EDI: Field SEGNAM in data record is default | Space: object requires documentation | ||
| 500 | EDI: Error during database insert in table EDIDC | Space: object requires documentation | ||
| 501 | EDI: Error during database update in table EDIDC | Space: object requires documentation | ||
| 502 | EDI: IDOCTP field in control record is invalid | Space: object requires documentation | ||
| 503 | EDI: CIMTYP field in control record is invalid | Space: object requires documentation | ||
| 504 | EDI: DOCTYP field in control record is invalid | Space: object requires documentation | ||
| 505 | EDI: Interval to be read is not available in data records | Space: object requires documentation | ||
| 506 | EDI: IDoc & contains no segments | Space: object requires documentation | ||
| 507 | EDI: Next data record could not be read | Space: object requires documentation | ||
| 508 | EDI: No data records could be read | Space: object requires documentation | ||
| 509 | EDI: IDoc cannot be unlocked | Space: object requires documentation | ||
| 510 | Combination of DOCTYP and CIMTYP fields is invalid | Space: object requires documentation | ||
| 511 | Combination of IDOCTP and CIMTYP fields is invalid | Space: object requires documentation | ||
| 512 | DOCTYP and IDOCTP fields are empty | Space: object requires documentation | ||
| 513 | Internal error in DOM creation | Space: object requires documentation | ||
| 514 | Data records for this IDoc could not be edited | Space: object requires documentation | ||
| 515 | IDoc &1 Segment &2 | Space: object requires documentation | ||
| 516 | --> Messages from segment editor for 4.0 | Space: object requires documentation | ||
| 517 | Entry of development class is mandatory | Space: object requires documentation | ||
| 518 | Segment & is locked by user & | Space: object requires documentation | ||
| 519 | Segment & exists already | Space: object requires documentation | ||
| 520 | Segment & does not exist yet | Space: object requires documentation | ||
| 521 | Current segment definition & can still be changed | Space: object requires documentation | ||
| 522 | Current segment definition & can no longer be changed | Space: object requires documentation | ||
| 523 | Segment type & cannot be changed | Space: object requires documentation | ||
| 524 | & does not exist as active data element | Space: object requires documentation | ||
| 525 | Field name & appears several times in segment | Space: object requires documentation | ||
| 526 | Segment definition not saved because user data was not maintained | Space: object requires documentation | ||
| 527 | Segment & could not be read completely | Space: object requires documentation | ||
| 528 | Segment definition & was saved with transport request & | Space: object requires documentation | ||
| 529 | Segment definition & was saved as local object | Space: object requires documentation | ||
| 530 | Export length for field & was set to & | Space: object requires documentation | ||
| 531 | Segment type & is not used yet | Space: object requires documentation | ||
| 532 | Segment type & is not yet assigned to a development class | Space: object requires documentation | ||
| 533 | Segment type & is not yet assigned to a development class | Space: object requires documentation | ||
| 534 | Segment definition must contain at least one field. Data was not saved. | Space: object requires documentation | ||
| 535 | There is already a released segment definition of & for Release & | Space: object requires documentation | ||
| 536 | --> Additional messages from EDI8 | Space: object requires documentation | ||
| 537 | Basic type & could not be converted | Space: object requires documentation | ||
| 538 | Extension & could not be converted | Space: object requires documentation | ||
| 539 | Basic type & and extension & cannot be converted to IDoc type | Space: object requires documentation | ||
| 540 | Message type & could not be converted | Space: object requires documentation | ||
| 541 | Structure & already exists | Space: object requires documentation | ||
| 542 | >>> IDoc inbound processing | |||
| 543 | Process & could not be started for IDoc number & | Space: object requires documentation | ||
| 544 | IDoc: Event-event receiver coupling activated successfully | |||
| 545 | Transferred IDoc data records are empty (internal error) | Space: object requires documentation | ||
| 546 | Transferred IDoc control records are empty (internal error) | Space: object requires documentation | ||
| 547 | Status set to '50' during IDoc inbound processing | Space: object requires documentation | ||
| 548 | No authorization to send IDocs with message type & | Space: object requires documentation | ||
| 549 | Party to be notified from partner profile must be a user | Space: object requires documentation | ||
| 550 | IDoc inbound: IDoc number & invalid | Space: object requires documentation | ||
| 551 | IDoc number & transferred to application | Space: object requires documentation | ||
| 552 | IDoc received repeatedly. | Space: object requires documentation | ||
| 553 | IDoc receieved again, no further processing | Space: object requires documentation | ||
| 554 | >>> XML inbound processing | Space: object requires documentation | ||
| 555 | Prolog & does not have the syntax <?xml version="..."?>. | Space: object requires documentation | ||
| 556 | Field & does not appear in segment &. | Space: object requires documentation | ||
| 557 | Instead of end day & the character string & was found. | Space: object requires documentation | ||
| 558 | Character string & cannot be interpreted as XML tag. | Space: object requires documentation | ||
| 559 | The character string & is not a valid XML tag for the IDoc type | Space: object requires documentation | ||
| 560 | The control record must begin with <EDI_DC40 segment="1"> instead of & | Space: object requires documentation | ||
| 561 | The segment & is not defined in the current IDoc type & | Space: object requires documentation | ||
| 562 | The segment & is not defined. | Space: object requires documentation | ||
| 563 | The character string & cannot be interpreted as a tag. | Space: object requires documentation | ||
| 564 | The start tag <IDOC begin="1"> or the end tag </IDOC> is missing. | Space: object requires documentation | ||
| 565 | The character string & is not the start tag of a segment field. | Space: object requires documentation | ||
| 566 | The XML data could not be processed completely | Space: object requires documentation | ||
| 567 | Error occurred when parsing XML document in line & column & | Space: object requires documentation | ||
| 568 | XML parser: Internal error | Space: object requires documentation | ||
| 569 | IDoc SOAP Namespace - Violation (&) | Space: object requires documentation | ||
| 570 | IDoc SOAP Namespace: EOIO-ID invalid | Space: object requires documentation | ||
| 571 | --> Messages from name conversion for IDoc types | Space: object requires documentation | ||
| 572 | Basic type & could not be converted | Space: object requires documentation | ||
| 573 | Extension & could not be converted | Space: object requires documentation | ||
| 574 | Field DOCTYP will not be able to be completed | Space: object requires documentation | ||
| 575 | Message type & could not be converted | Space: object requires documentation | ||
| 576 | Structure of predecessor type different from specified structure | Space: object requires documentation | ||
| 577 | --> Messages from consistency check for IDoc types | Space: object requires documentation | ||
| 578 | Extension type & does not appear in EDCIM | Space: object requires documentation | ||
| 579 | Basic type & does not appear in EDBAS | Space: object requires documentation | ||
| 580 | Basic type & has no syntax entries | Space: object requires documentation | ||
| 581 | Extension & has no syntax entries | Space: object requires documentation | ||
| 582 | Segment type & does not exist | Space: object requires documentation | ||
| 583 | Basic type & is not released | Space: object requires documentation | ||
| 584 | Extension & is not released | Space: object requires documentation | ||
| 585 | Syntax entries are not numbered sequentially | Space: object requires documentation | ||
| 586 | Parent segment & has no children | Space: object requires documentation | ||
| 587 | Segment & has incorrect number for parent segment | Space: object requires documentation | ||
| 588 | Parent segment for segment & could not be found | Space: object requires documentation | ||
| 589 | Segment & has incorrect hierarchy level | Space: object requires documentation | ||
| 590 | Segment & does not exist | Space: object requires documentation | ||
| 591 | Predecessor of basic type & does not exist | Space: object requires documentation | ||
| 592 | Predecessor of basic type & is not released | Space: object requires documentation | ||
| 593 | Predecessor of extension & does not exist | Space: object requires documentation | ||
| 594 | Predecessor of extension & is not released | Space: object requires documentation | ||
| 595 | Basic type & has no short description | Space: object requires documentation | ||
| 596 | Extension & has no short description | Space: object requires documentation | ||
| 597 | Basic type & is linked to logical message & | Space: object requires documentation | ||
| 598 | Basic type & is not linked with any logical message | Space: object requires documentation | ||
| 599 | Extension & is linked with logical message & | Space: object requires documentation | ||
| 600 | Extension & is not linked with any logical message | Space: object requires documentation | ||
| 601 | Basic type & is released | Space: object requires documentation | ||
| 602 | Extension & is released | Space: object requires documentation | ||
| 603 | No predecessors exist | Space: object requires documentation | ||
| 604 | Predecessor & exists | Space: object requires documentation | ||
| 605 | Predecessor & is released | Space: object requires documentation | ||
| 606 | Syntax table for predecessor & is empty | Space: object requires documentation | ||
| 607 | Segment & appears only in predecessor | Space: object requires documentation | ||
| 608 | Segment & has other attributes in predecessor | Space: object requires documentation | ||
| 609 | New segment & does not have to be a mandatory segment | Space: object requires documentation | ||
| 610 | Extension & is not assigned to any basic type | Space: object requires documentation | ||
| 611 | Extension & is assigned to basic type & | Space: object requires documentation | ||
| 612 | Extension & and basic type & are not compatible | Space: object requires documentation | ||
| 613 | Changes to & will have an effect on several extensions | Space: object requires documentation | ||
| 614 | No development class has been specified | Space: object requires documentation | ||
| 615 | Development class & does not exist | Space: object requires documentation | ||
| 616 | Segment & is parent segment but parent flag is missing | Space: object requires documentation | ||
| 617 | Segment & has invalid frequency of use | Space: object requires documentation | ||
| 618 | No new segments have been added | Space: object requires documentation | ||
| 619 | View has no short description | Space: object requires documentation | ||
| 620 | Syntax error: Segment & must appear in view & | Space: object requires documentation | ||
| 621 | Syntax entry numbering contains errors. | Space: object requires documentation | ||
| 622 | Enter copy template | Space: object requires documentation | ||
| 623 | Attributes cannot be modified | Space: object requires documentation | ||
| 624 | Segment & is used multiple times in IDoc types | Space: object requires documentation | ||
| 625 | ---- Archiving of IDocs | |||
| 626 | Invalid access & to archive | Space: object requires documentation | ||
| 627 | Insert in table & with key & & failed | Space: object requires documentation | ||
| 628 | System format cannot be determined | Space: object requires documentation | ||
| 629 | IDoc & not found | Space: object requires documentation | ||
| 630 | IDoc & found | |||
| 631 | Data decompression for archiving class IDoc contains errors | Space: object requires documentation | ||
| 632 | Data compression for archiving class IDoc failed | Space: object requires documentation | ||
| 633 | IDoc data read contains errors | Space: object requires documentation | ||
| 634 | Failed to delete IDoc table & with key & | |||
| 635 | Character conversion from code page & to & for IDoc failed | Space: object requires documentation | ||
| 636 | IDoc has unknown status value & | Space: object requires documentation | ||
| 637 | Table specifying which status values can be archived is empty | Space: object requires documentation | ||
| 638 | Control record of IDoc with number & not found | |||
| 639 | Archiving object IDoc is inknown | Space: object requires documentation | ||
| 640 | Archiving class IDoc (internal error) | Space: object requires documentation | ||
| 641 | Update not possible | |||
| 642 | Archiving not possible due to missing classification | |||
| 643 | Internal error for IDoc & | Space: object requires documentation | ||
| 644 | IDoc '&' : '&' when reloading | Space: object requires documentation | ||
| 645 | IDoc '&': Inconsistent data in archive '&' | Space: object requires documentation | ||
| 646 | IDoc '&': Control record exists already | Space: object requires documentation | ||
| 647 | IDoc '&': Data records exist already | Space: object requires documentation | ||
| 648 | IDoc '&': Status records exist already | Space: object requires documentation | ||
| 649 | IDoc '&' does not exist | Space: object requires documentation | ||
| 650 | IDoc '&' locked | Space: object requires documentation | ||
| 651 | IDoc '&' cannot be deleted | Space: object requires documentation | ||
| 652 | IDoc '&' only partly deleted | Space: object requires documentation | ||
| 653 | IDoc '&': Processing cannot be completed correctly | Space: object requires documentation | ||
| 654 | IDoc '&': Status records could not be read | Space: object requires documentation | ||
| 655 | IDoc '&': Data records could not be read | Space: object requires documentation | ||
| 656 | Archive information for archive & could not be read | Space: object requires documentation | ||
| 657 | IDoc '&' could not be opened for reading | Space: object requires documentation | ||
| 658 | IDoc '&' could not be opened to set status | Space: object requires documentation | ||
| 659 | IDoc '&' could not be closed after status was set | Space: object requires documentation | ||
| 660 | IDoc '&': Status could not be set | Space: object requires documentation | ||
| 661 | Number range & not found | Space: object requires documentation | ||
| 662 | IDoc number '&' is not suitable for current number level | Space: object requires documentation | ||
| 663 | IDoc '&' from system '&' not reloaded | Space: object requires documentation | ||
| 664 | IDoc & from Release & not reloaded | Space: object requires documentation | ||
| 665 | --> Additional messages (inb. status) | Space: object requires documentation | ||
| 666 | Invalid name '&' in status record & for version of port '&' | Space: object requires documentation | ||
| 667 | IDoc: Different table names in inb. status via IDoc | Space: object requires documentation | ||
| 668 | IDoc: Invalid table name '&' in inb. status via IDoc | Space: object requires documentation | ||
| 669 | IDoc: Status message in inb.status via IDoc is not complete | Space: object requires documentation | ||
| 670 | Error in status inbound from IDoc type SYSTAT01 | Space: object requires documentation | ||
| 671 | IDoc number & has been put down for deletion | Space: object requires documentation | ||
| 672 | IDoc number & already has status 31 | Space: object requires documentation | ||
| 673 | In status postprocessing the IDoc has been released for sending | Space: object requires documentation | ||
| 674 | The IDoc is currently now in status '&' | Space: object requires documentation | ||
| 675 | --> Error FuGr EDIPAKET | Space: object requires documentation | ||
| 676 | IDocs to be processed not found in database | Space: object requires documentation | ||
| 677 | Status of IDocs to be processed cannot be reset | Space: object requires documentation | ||
| 678 | IDocs could be processed as block | Space: object requires documentation | ||
| 679 | IDocs could not be processed successfully | Space: object requires documentation | ||
| 680 | IDocs should not be transferred for processing | Space: object requires documentation | ||
| 681 | No more IDocs available for post-processing | Space: object requires documentation | ||
| 682 | Status set by error handling for IDoc packet | Space: object requires documentation | ||
| 683 | IDocs set to status '30' successfully | Space: object requires documentation | ||
| 684 | IDocs could not be set to status '30' | Space: object requires documentation | ||
| 685 | Incorrect selection of MASS_RSEOUT00 | Space: object requires documentation | ||
| 686 | IDocs set to status '03' successfully | Space: object requires documentation | ||
| 687 | IDocs could not be set to status '03' | Space: object requires documentation | ||
| 688 | IDocs marked for deletion | Space: object requires documentation | ||
| 689 | IDocs should not be marked for deletion | Space: object requires documentation | ||
| 690 | IDocs could not be marked for deletion | Space: object requires documentation | ||
| 691 | Command file could be started | Space: object requires documentation | ||
| 692 | Command file could not be started | Space: object requires documentation | ||
| 693 | Command file could be started, but IDocs still have old status | Space: object requires documentation | ||
| 694 | Restart not possible because port definition is missing | Space: object requires documentation | ||
| 695 | The IDoc number & is not available in the database. | Space: object requires documentation | ||
| 696 | The IDoc number & is not an outgoing IDoc | Space: object requires documentation | ||
| 697 | Deletion not possible, a status record must be written in control record. | Space: object requires documentation | ||
| 698 | The IDoc number must not be 0 or initial. | Space: object requires documentation | ||
| 699 | The entered status is not valid for the inbound status | Space: object requires documentation | ||
| 700 | The status record was stored in file &. | Space: object requires documentation | ||
| 701 | The port entered is not a file port. | Space: object requires documentation | ||
| 702 | No port entered. | Space: object requires documentation | ||
| 703 | No file entered. | Space: object requires documentation | ||
| 704 | No outbound IDoc is available in the system. | Space: object requires documentation |
History
| Last changed on/by | 20140121 | SAP | |
| SAP Release Created in |