SAP ABAP Message Class NC (IS-HCM Hospital communication)
Basic Data
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ NBAS (Package) Appl. development Hospital System master data, catalogs
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
NBAS (Package) Appl. development Hospital System master data, catalogs 
Attributes
| Message class |  |
NC |
| Short Description |  |
IS-HCM Hospital communication |
| Changed On |  |
20131127 |
| Last Changed At |  |
164916 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
reserved hospital (communications module HCM) | ||
| 2 | 001 |
------------ Standard messages start here ---------------- TW/PS -------- | ||
| 3 | 002 |
No entry in table & for & | ||
| 4 | 003 |
No entry in table & for & & | ||
| 5 | 004 |
No entry in table & for & & & | ||
| 6 | 005 |
Error while reading table & | ||
| 7 | 006 |
Error while updating table & | ||
| 8 | 007 |
& & & & | ||
| 9 | 008 |
Table & is not defined in data dictionary | ||
| 10 | 009 |
Table & has no key field & | ||
| 11 | 010 |
Length of field & is shorter than in data dictionary | ||
| 12 | 011 |
Error while inserting record into database | ||
| 13 | 012 |
Error while making changes in database | ||
| 14 | 013 |
Transaction code & unknown | ||
| 15 | 014 |
Enter data | ||
| 16 | 015 |
Select a row | ||
| 17 | 016 |
Select a valid row | ||
| 18 | 017 |
Select a row | ||
| 19 | 018 |
Select the end of the block | ||
| 20 | 019 |
Data will be irretrievably deleted when you press ENTER | ||
| 21 | 020 |
Cannot assign number from number range & & & | ||
| 22 | 021 |
Numbers of number range & & & in critical area | ||
| 23 | 022 |
Last free number of number range & & & assigned | ||
| 24 | 023 |
Error while inserting records into table &, keys: & & & | ||
| 25 | 024 |
&1 &2 added to table &3 | ||
| 26 | 025 |
Error while deleting records from table & | ||
| 27 | 026 |
Number range error; change current number level from &1 to &2 | ||
| 28 | 027 |
Number range &2 missing in client &1; comparison with table &3 required | ||
| 29 | 028 |
Caution: action is not integrated in the Change + Transport System | ||
| 30 | 029 |
Case &2 does not exist in institution &1 | ||
| 31 | 030 |
Error while updating program & | ||
| 32 | 031 |
Data selection terminated after & hits | ||
| 33 | 032 |
No data exists for the selection given | ||
| 34 | 033 |
Program & is currently locked (already running), user & | Space: object requires documentation | |
| 35 | 034 |
Return code & from receiving system & | ||
| 36 | 035 |
Enter a valid institution. | ||
| 37 | 036 |
Target system/program (&) not identified during allocate | ||
| 38 | 037 |
Error while deleting records: & records instead of & | ||
| 39 | 038 |
& & could not be inserted into table & | ||
| 40 | 039 |
Avoid extensive selections, problems with system performance! | ||
| 41 | 040 |
Program & is currently locked (possibly by & or &), user & | Space: object requires documentation | |
| 42 | 041 |
No entry in table & for selection specified | ||
| 43 | 042 |
Program & is currently locked | ||
| 44 | 043 |
Select a sort order | ||
| 45 | 044 |
Select a processing mode | ||
| 46 | 045 |
Institution & is in production operation: function is not allowed | ||
| 47 | 046 |
Enter more precise selection criteria | ||
| 48 | 047 |
Further information not available on this entry | ||
| 49 | 048 |
Function was canceled | ||
| 50 | 049 |
& records have been modified | Space: object requires documentation | |
| 51 | 050 |
File & already exists | ||
| 52 | 051 |
You have no write authorization for file & | ||
| 53 | 052 |
Cannot open file &1: &2 | Space: object requires documentation | |
| 54 | 053 |
Cannot determine file name | ||
| 55 | 054 |
File creation/transfer failed: & | ||
| 56 | 055 |
Correct contradictory selection specifications | Space: object requires documentation | |
| 57 | 056 |
No information available | Space: object requires documentation | |
| 58 | 057 |
Adjustments not required | Space: object requires documentation | |
| 59 | 058 |
Program ended successfully | Space: object requires documentation | |
| 60 | 059 |
Selection interval exceeds & days; this will yield extensive dataset | Space: object requires documentation | |
| 61 | 060 |
No messages available | ||
| 62 | 061 |
First message reached | ||
| 63 | 062 |
Last message reached | ||
| 64 | 063 |
Segment/message error; code & | ||
| 65 | 064 |
Message & was changed successfully | ||
| 66 | 065 |
Status & prohibits editing of message & | ||
| 67 | 066 |
Function cannot be executed / not permitted here | Space: object requires documentation | |
| 68 | 067 |
Error while executing action | Space: object requires documentation | |
| 69 | 068 |
Error while decoding message | Space: object requires documentation | |
| 70 | 069 |
Enter a valid selection interval | Space: object requires documentation | |
| 71 | 070 |
Selection interval start &, & is in the future | Space: object requires documentation | |
| 72 | 071 |
Incorrect parameter specification when &1 called | Space: object requires documentation | |
| 73 | 072 |
Tolerance range of & days was exceeded | Space: object requires documentation | |
| 74 | 073 |
Error while inserting record in table & | Space: object requires documentation | |
| 75 | 074 |
Specify an event (with application Id) | Space: object requires documentation | |
| 76 | 075 |
Incorrect selection specification; entry not permitted here | Space: object requires documentation | |
| 77 | 076 |
Serious internal error in &1 &2 &3; see long text | Space: object requires documentation | |
| 78 | 077 |
Cannot process file &1 | Space: object requires documentation | |
| 79 | 078 |
File name &1 exceeds maximum permitted length of &2 characters | Space: object requires documentation | |
| 80 | 079 |
Select one option only | Space: object requires documentation | |
| 81 | 080 |
File &1 already exists and will be overwritten | Space: object requires documentation | |
| 82 | 081 |
File &1 has been archived | Space: object requires documentation | |
| 83 | 082 |
Cannot archive file &1 | Space: object requires documentation | |
| 84 | 083 |
Cannot delete file &1 | Space: object requires documentation | |
| 85 | 084 |
Cannot copy file &1 to &2 | Space: object requires documentation | |
| 86 | 085 |
&1 entries successfully processed | Space: object requires documentation | |
| 87 | 086 |
Last changes have been rolled back | Space: object requires documentation | |
| 88 | 087 |
Procedure & is productive: function is not permitted | Space: object requires documentation | |
| 89 | 088 |
File &1 was successfully created or modified | Space: object requires documentation | |
| 90 | 089 |
File &1 successfully created or changed in directory &2 | Space: object requires documentation | |
| 91 | 090 |
Data has been refreshed | Space: object requires documentation | |
| 92 | 091 |
Include &1 does not exist yet. Create it manually, if necessary. | Space: object requires documentation | |
| 93 | 092 |
Content of error message is not correct | The short text describes the object sufficiently | |
| 94 | 100 |
>>>>>>>>>> the communication messages start here <<<<<<<<<<<<<<<<<<< | ||
| 95 | 101 |
No customer message segments available | ||
| 96 | 102 |
Change segment owner ID & (leading letter mandatory) | ||
| 97 | 103 |
Maintain field & (occurs in segment & &) | ||
| 98 | 104 |
Maintain segments with owner ID 'SY' | ||
| 99 | 105 |
All customer structures have been successfully generated | ||
| 100 | 106 |
Customer structures generated: & segment(s) contain(s) errors | ||
| 101 | 107 |
Maintain segment-to-field assignments | ||
| 102 | 108 |
Maintain message fields | ||
| 103 | 109 |
Maintain segment assignment for message type & & | ||
| 104 | 110 |
Inbound pool & does not exist; create it | ||
| 105 | 111 |
Outbound pool & does not exist; create it | ||
| 106 | 112 |
Institution & & does not exist; create it | ||
| 107 | 113 |
Message type & & & & does not exist; check | ||
| 108 | 114 |
Maintain message type(s) for event & & | ||
| 109 | 115 |
Maintain system & for event & & in institution & | ||
| 110 | 116 |
Message type & & & & does not exist; correct your entry | ||
| 111 | 117 |
Message type & & & & contains errors; ENTER -> copy anyway | ||
| 112 | 118 |
Message type & & & & has not been checked; ENTER -> copy anyway | ||
| 113 | 119 |
Message type & & & & already exists; ENTER -> overwrite | ||
| 114 | 120 |
Owner ID of copy must be different than that of original | ||
| 115 | 121 |
Only SAP can maintain SAP message types | ||
| 116 | 122 |
No segments exist for message type & & & & | ||
| 117 | 123 |
Only SAP can maintain SAP message segments | ||
| 118 | 124 |
Segment & & & & does not exist; correct your entry | ||
| 119 | 125 |
Segment & & & & contains errors; ENTER -> copy anyway | ||
| 120 | 126 |
Segment & & & & has not been checked; ENTER -> copy anyway | ||
| 121 | 127 |
Segment & & & & already exists; ENTER -> overwrite | ||
| 122 | 128 |
No fields exist for message segment & & & & | ||
| 123 | 129 |
Message type & & created as copy of & & | ||
| 124 | 130 |
Message segment & & created as copy of & & | ||
| 125 | 131 |
No segments maintained for message type & & & & | ||
| 126 | 132 |
Specifications on message type & & & & successfully deleted | ||
| 127 | 133 |
Specify a message standard | ||
| 128 | 134 |
Specify the version of the message standard | ||
| 129 | 135 |
Message standard & & does not exist. Correct your entry. | ||
| 130 | 136 |
Specify a message type number | ||
| 131 | 137 |
Specify an owner code for the message type | ||
| 132 | 138 |
No fields maintained for message segment & & & & | ||
| 133 | 139 |
Specifications on message segment & & & & successfully deleted | ||
| 134 | 140 |
Specify a message segment number | ||
| 135 | 141 |
Specify an owner code for the segment | ||
| 136 | 142 |
& HCM entries successfully deleted from table TCPIC | ||
| 137 | 143 |
SAP structures were successfully generated | ||
| 138 | 144 |
SAP structures generated: & errored segment(s) exist | ||
| 139 | 145 |
No dispatch orders exist | ||
| 140 | 146 |
Cannot find any message types | ||
| 141 | 147 |
Cannot find any segment assignments | ||
| 142 | 148 |
All & dispatch orders were sucessfully formatted | ||
| 143 | 149 |
Only & old messages ready to send exist | ||
| 144 | 150 |
Messages ready to send do not exist | ||
| 145 | 151 |
Message transmission completed | ||
| 146 | 152 |
Environment variables in receiving system & are not correct | ||
| 147 | 153 |
Cannot create .tmp file in receiving system & | ||
| 148 | 154 |
Cannot lock file in receiving system & | ||
| 149 | 155 |
Cannot rename file(s) in receiving system & | ||
| 150 | 156 |
Invalid number of data records for receiving system & | ||
| 151 | 157 |
Cannot open status file in receiving system & | ||
| 152 | 158 |
Cannot open file in receiving system & | ||
| 153 | 159 |
.tmp files still exist in receiving system & | ||
| 154 | 160 |
Cannot overwrite target file in receiving system & | ||
| 155 | 161 |
Gateway error occurred in receiving system & | ||
| 156 | 162 |
& entries (& messages) successfully deleted from log file | ||
| 157 | 163 |
& dispatch orders successfully deleted from table NC01 | ||
| 158 | 164 |
& entries (& messages) successfully deleted from table NC02 | ||
| 159 | 165 |
For system & return code &: connection failed/severed | ||
| 160 | 166 |
No entry for system & in table TXCOM | ||
| 161 | 167 |
Parameters of system & are incorrect | ||
| 162 | 168 |
Send date specifications are ignored with "Older than ... (in days)" | ||
| 163 | 169 |
Sending for & of & receivers successful (& messages) | ||
| 164 | 170 |
Specify an owner code | ||
| 165 | 171 |
Automatic dispatch inactive in institution & | ||
| 166 | 172 |
& cases processed | ||
| 167 | 173 |
No data at partner & | ||
| 168 | 174 |
No control data available for any of specified systems | ||
| 169 | 175 |
Data successfully transferred from all & systems | ||
| 170 | 176 |
No receipt control for system &, event & & exists | ||
| 171 | 177 |
Data successfully transferred from system & | ||
| 172 | 178 |
Data transfer from system & failed | ||
| 173 | 179 |
Transfer failed for & out of & systems | ||
| 174 | 180 |
Transfer failed for all & systems | ||
| 175 | 181 |
No relevant entry exists in table TXCOM | ||
| 176 | 182 |
& dispatch orders formatted, & errored orders not formatted | ||
| 177 | 183 |
Cannot find any segments | ||
| 178 | 184 |
Customer structures generated: & errored type(s) exist | ||
| 179 | 185 |
Customer structures generated: & type(s), & segment(s) errored | ||
| 180 | 186 |
No data in system & | ||
| 181 | 187 |
& dispatch orders created, & not created, since data is missing | ||
| 182 | 188 |
Format error: & message starts with & instead of & | ||
| 183 | 189 |
&2 messages received from system &1; errors in &3 of them | ||
| 184 | 190 |
Format error: HL7 component separator is missing | ||
| 185 | 191 |
Format error: HL7 repetition separator is missing | ||
| 186 | 192 |
Format error: HL7 subcomponent separator is missing | ||
| 187 | 193 |
Incorrect receiver & (instead of application &) | ||
| 188 | 194 |
Format & & in the standard &, version & not supported | ||
| 189 | 195 |
Customer message end segments are not authorized | ||
| 190 | 196 |
No data exists for client & in system & | ||
| 191 | 197 |
Creation of batch input session(s) & failed: rollback started | ||
| 192 | 198 |
All &2 messages were sent to system &1 | ||
| 193 | 199 |
Data structures of system & are incorrect | ||
| 194 | 200 |
A write error occurred in receiving system & | ||
| 195 | 201 |
& message(s) retrieved for sending | ||
| 196 | 202 |
System & is currently locked | ||
| 197 | 203 |
Maintain segment & & (in group segment & &) | Space: object requires documentation | |
| 198 | 204 |
Choose a partner system | Space: object requires documentation | |
| 199 | 205 |
You are transporting RFC destination & and function modules & and & | Space: object requires documentation | |
| 200 | 206 |
SAP structures generated: & type(s) contain errors | Space: object requires documentation | |
| 201 | 207 |
SAP structures generated: & type(s), & segment(s) contain errors | Space: object requires documentation | |
| 202 | 208 |
& does not support case-related processing; you cannot use this program | Space: object requires documentation | |
| 203 | 209 |
&1 dispatch orders created | Space: object requires documentation | |
| 204 | 210 |
&1 dispatch orders created, &2 orders not created | Space: object requires documentation | |
| 205 | 211 |
Assign a unique name | ||
| 206 | 212 |
TXCOM name must have 7 characters | ||
| 207 | 213 |
Last character of the name will be ignored | ||
| 208 | 214 |
Version of specified communication standard does not exist | ||
| 209 | 215 |
For dispatch, you must enter a name for PUT_TAB | ||
| 210 | 216 |
For receipt, you must enter names for GET_TAB and GET_RESP | ||
| 211 | 217 |
& already used for & on & - use another name! | ||
| 212 | 218 |
Program names do not correspond to SAP recommendation | ||
| 213 | 219 |
Owner codes starting with 'S' are reserved for SAP | ||
| 214 | 220 |
Owner code & for & & does not exist | ||
| 215 | 221 |
Name does not correspond to SAP recommendation | ||
| 216 | 222 |
Partner system will be deleted | ||
| 217 | 223 |
Maintain RFC destination & (SM59) | ||
| 218 | 224 |
When express dispatch is active, an RFC destination must be maintained | Space: object requires documentation | |
| 219 | 225 |
Active express dispatch only useful if function name maintained | Space: object requires documentation | |
| 220 | 226 |
Creating a system is only useful if dispatch or receipt required | ||
| 221 | 227 |
You cannot make a selection via message numbers in packet mode | Space: object requires documentation | |
| 222 | 228 |
Enter at least one communication channel | Space: object requires documentation | |
| 223 | 229 |
Enter a contact person | Space: object requires documentation | |
| 224 | 230 |
Case selection & does not exist in institution & | Space: object requires documentation | |
| 225 | 231 |
Specify case selection(s) or end date | Space: object requires documentation | |
| 226 | 232 |
Can only process older records (limit: &2) | Space: object requires documentation | |
| 227 | 233 |
&1 messages retrieved from temporary storage | Space: object requires documentation | |
| 228 | 234 |
First display messages in temporary storage | Space: object requires documentation | |
| 229 | 235 |
&1 messages from temporary storage included in the display | Space: object requires documentation | |
| 230 | 236 |
No messages in temporary storage for case &1 | Space: object requires documentation | |
| 231 | 237 |
&1 messages from temporary storage removed from display | Space: object requires documentation | |
| 232 | 238 |
All messages are already in temporary storage | Space: object requires documentation | |
| 233 | 239 |
Object &1 &2 &3 &4 already exists | Space: object requires documentation | |
| 234 | 240 |
Message standard && created as copy of & & | Space: object requires documentation | |
| 235 | 241 |
&1 stored without reference; obsolete message records deleted | Space: object requires documentation | |
| 236 | 242 |
You have selected message no. &1 | Space: object requires documentation | |
| 237 | 243 |
Case selection only authorized for single specific institution | Space: object requires documentation | |
| 238 | 244 |
3rd digit of reason for discharge/transfer is incorrect | Space: object requires documentation | |
| 239 | 245 |
Cannot create character set conversion object (&1) | Space: object requires documentation | |
| 240 | 246 |
w/o HC smart card data, transmission only possible after conf.of coverage | Space: object requires documentation | |
| 241 | 247 |
Stored messages already exist for this case | Space: object requires documentation | |
| 242 | 248 |
Final invoice missing: cancel inv. &1 and repeat final billing(see l.txt) | Space: object requires documentation | |
| 243 | 249 |
Total invoice number &1 is not defined | Space: object requires documentation | |
| 244 | 250 |
Company code & does not exist | Space: object requires documentation | |
| 245 | 251 |
Invoice & does not have a valid §302 billing type | Space: object requires documentation | |
| 246 | 252 |
Case & does not have services; check | Space: object requires documentation | |
| 247 | 253 |
Readmission entire case &1 is obsolete. (leading case: &2) | Space: object requires documentation | |
| 248 | 254 |
Test | Space: object requires documentation | |
| 249 | 255 |
Procedure &1 is not supported | Space: object requires documentation | |
| 250 | 256 |
Diagnosis &1 cannot be transferred in an ETL/NDG segment | Space: object requires documentation | |
| 251 | 257 |
The health insurance number is required with admission reason 06 | Space: object requires documentation | |
| 252 | 300 |
------------ EDI (§301) messages start here ---------- TW/PS ----------- | ||
| 253 | 301 |
Control data does not exist for any of specified DCPs | ||
| 254 | 302 |
Key fields required by NC301 were not transferred | ||
| 255 | 303 |
Not all mandatory fields for message are available | ||
| 256 | 304 |
Cannot find message types for the communication standard | ||
| 257 | 305 |
Segment is not assigned to a message type (TNCT2) | ||
| 258 | 306 |
Cannot find segment (TNCS0) for the communication standard | ||
| 259 | 307 |
Patient number & for case & does not exist | ||
| 260 | 308 |
No entry for communication standard found in TNCST | ||
| 261 | 309 |
Function module from communication standard not found (TNCST) | ||
| 262 | 310 |
No invoice items available for invoice & | ||
| 263 | 311 |
No entry defined in table TNCS0 for segment & | ||
| 264 | 312 |
No function module defined in table &2 for segment &1 | Space: object requires documentation | |
| 265 | 313 |
Error while determining fields for segment & | ||
| 266 | 314 |
Missing path within agreements for institution &, data coll. point & | ||
| 267 | 315 |
Customizing incorrect: no entry for institution & and data coll. point & | ||
| 268 | 316 |
Cannot open file & for read operation | ||
| 269 | 317 |
Cannot determine data collection points for this selection | ||
| 270 | 318 |
Syntax error in data record & | ||
| 271 | 319 |
Cannot determine invoice header of billing document number & | ||
| 272 | 320 |
No case found for invoice & (case number &) | ||
| 273 | 321 |
Case-rel. ins. relat. for case & not found (seq.no. IR = &) | ||
| 274 | 322 |
All & events were successfully processed | ||
| 275 | 323 |
& events successfully processed, & problematic | ||
| 276 | 324 |
Communication procedure & not active in institution & | ||
| 277 | 325 |
No & agreements defined for data collection point & | ||
| 278 | 326 |
No file name specified for data collection point & | ||
| 279 | 327 |
No type-to-segment assignments defined for the communication standard | ||
| 280 | 328 |
No messages exist for data collection point & | ||
| 281 | 329 |
Message no. & is too long; cannot process | ||
| 282 | 330 |
Select collective or single processing | ||
| 283 | 331 |
Specify a valid data collection point | ||
| 284 | 332 |
Message no. & does not exist (only status record) | ||
| 285 | 333 |
Cannot change message no. & | ||
| 286 | 334 |
Cannot change all message statuses | ||
| 287 | 335 |
Cannot create file administration record | ||
| 288 | 336 |
File administration record no. & already exists | ||
| 289 | 337 |
Cannot modify file administration record | ||
| 290 | 338 |
&: cannot modify data collection point transaction record | ||
| 291 | 339 |
File status prevents renewed file creation with file no. & | ||
| 292 | 340 |
Select reconstruction or restart | ||
| 293 | 341 |
File administration record does not exist (anymore) | ||
| 294 | 342 |
Previous file creation was incomplete | ||
| 295 | 343 |
Required entry field & is not filled in segment & | ||
| 296 | 344 |
Fields & and & are not filled in segment & | ||
| 297 | 345 |
Fields &, & and & are not filled in segment & | ||
| 298 | 346 |
Required segment & does not exist in & record | ||
| 299 | 347 |
Total charges & different to the invoice amount & | ||
| 300 | 348 |
Maximum size (& KB) of file reached | ||
| 301 | 349 |
Inst. &, sender &: Files not consecutively numbered, & is missing | ||
| 302 | 350 |
Previous file (no. &) has not been completely imported | ||
| 303 | 351 |
Enter a number for the transfer file | ||
| 304 | 352 |
You cannot reset sequence number | ||
| 305 | 353 |
Resetting sequence number may result in data inconsistency | ||
| 306 | 354 |
Last sequence number reached (99000); cannot increment | ||
| 307 | 355 |
Update for table & failed | ||
| 308 | 356 |
Line & in file & is too long to be imported | ||
| 309 | 357 |
Sequence number of file cannot exceed & | ||
| 310 | 358 |
You cannot process file again | ||
| 311 | 359 |
Enter a valid message number | ||
| 312 | 360 |
No entry in & for & & (EDI order no. &) | ||
| 313 | 361 |
Number must be between & and & | ||
| 314 | 362 |
Entered error number & is unknown | ||
| 315 | 363 |
Enter either an error number or an error text | ||
| 316 | 364 |
Entry too long; cannot exceed & characters | ||
| 317 | 365 |
No ext. error message exists; cannot change status to "ext. error" | ||
| 318 | 366 |
No. &: message type & does not match previous message type & | ||
| 319 | 367 |
&: & &, status & | ||
| 320 | 368 |
EDI order & created; error & for file/message &, message type & | Space: object requires documentation | |
| 321 | 369 |
Invalid segment ID code: & | ||
| 322 | 370 |
Invalid message ID code: & | ||
| 323 | 371 |
& file status records transferred into the new table structure | ||
| 324 | 372 |
DataIncsty: Entry in tab. &2 missing for entry in tab. &1. Continue = &3. | ||
| 325 | 373 |
Data inconsistency: File assignment to records from & does not exist | ||
| 326 | 374 |
Cannot transfer & file status records into the new table | ||
| 327 | 375 |
Cannot create partner transfer file | ||
| 328 | 376 |
Invalid data collection point. Enter a decoding data collection point. | ||
| 329 | 377 |
Cannot determine a data collection point for institute indicator & | ||
| 330 | 378 |
Receiver unknown (II no.: &) | ||
| 331 | 379 |
Invoice &: No §301 charge key exists for service & | ||
| 332 | 380 |
Enter either an insurance provider type or a data collection point | ||
| 333 | 381 |
Same data collection point. No need to replace. | ||
| 334 | 382 |
Enter one data collection point only | ||
| 335 | 383 |
Cannot determine external file/directory name | ||
| 336 | 384 |
File for &2 was copied along with files for institution &1 | ||
| 337 | 385 |
Cannot determine admission for case & | ||
| 338 | 386 |
Cannot determine master record for service & in service catalog & | ||
| 339 | 387 |
Cannot determine maximum length of stay for FR & in service catalog & | ||
| 340 | 388 |
More incorrectly transferred files exist than are displayed | ||
| 341 | 389 |
Parameter: external / internal processing | ||
| 342 | 390 |
Data collection point & is not valid for institute indicator & | ||
| 343 | 391 |
& files were transferred from the communication server directory | ||
| 344 | 392 |
Data collection point &: & files processed | ||
| 345 | 393 |
No insurance relationship relevant for §301 (case &) exists | ||
| 346 | 394 |
Directory logic: SAP original control | ||
| 347 | 395 |
Cannot transmit file in communication server directory | ||
| 348 | 396 |
Cannot delete last external error message for external error | ||
| 349 | 397 |
Specify a correct hexadecimal value | ||
| 350 | 398 |
No insurance exists for case & | ||
| 351 | 399 |
No message sent to insurance provider &1 for case &2 | ||
| 352 | 400 |
Data collection point & is not valid on & | ||
| 353 | 401 |
No data collection point maintained for ins. provider & | Space: object requires documentation | |
| 354 | 402 |
Case & is self-payer only | ||
| 355 | 403 |
Case & is excluded from EDI processing | Space: object requires documentation | |
| 356 | 404 |
Message & was excluded by ins. provider & for EDI processing | Space: object requires documentation | |
| 357 | 405 |
Selected processing not authorized for this message | ||
| 358 | 406 |
No active communication procedures exist in institution & | ||
| 359 | 407 |
Communication procedure & is not known or is not active | ||
| 360 | 408 |
&: mapping failed for table &, field & with value & | Space: object requires documentation | |
| 361 | 409 |
Missing data in the interface from & | ||
| 362 | 410 |
Procedure & is not supported (yet) | ||
| 363 | 411 |
No address found for patient & | Space: object requires documentation | |
| 364 | 412 |
No address found for business partner & | Space: object requires documentation | |
| 365 | 413 |
No address found for guarantor & | Space: object requires documentation | |
| 366 | 414 |
& specified as submission status, should be & however | Space: object requires documentation | |
| 367 | 415 |
Code & (&) unknown; occurred for patient &, message & | Space: object requires documentation | |
| 368 | 416 |
External error number &1: &2 &3 | Space: object requires documentation | |
| 369 | 417 |
Specified region code & is not permitted | Space: object requires documentation | |
| 370 | 418 |
Cannot read comparison file & | Space: object requires documentation | |
| 371 | 419 |
RFC communication failed: FM &, destination &, return code & | Space: object requires documentation | |
| 372 | 420 |
Patient & is excluded from EDI processing | Space: object requires documentation | |
| 373 | 421 |
No data collection point found for EDI procedure & | Space: object requires documentation | |
| 374 | 422 |
Transfer system specifications incorrect or not maintained | Space: object requires documentation | |
| 375 | 423 |
Errors detected during data transmission | Space: object requires documentation | |
| 376 | 424 |
Status & is unknown in EDI procedure & | Space: object requires documentation | |
| 377 | 425 |
& messages are no longer on hold | Space: object requires documentation | |
| 378 | 426 |
EDI invoice record missing for creating dunning record (&) | Space: object requires documentation | |
| 379 | 427 |
Invoice record not sent or rejected - dunning record will be created (&) | Space: object requires documentation | |
| 380 | 428 |
No messages found | Space: object requires documentation | |
| 381 | 429 |
Transfer system cannot transmit the message further | Space: object requires documentation | |
| 382 | 430 |
Service quantity zero or does not exist - check | Space: object requires documentation | |
| 383 | 431 |
Service (&) not completely billed for | Space: object requires documentation | |
| 384 | 432 |
Institution &, case &: message transmission not required | Space: object requires documentation | |
| 385 | 433 |
No target payment amount for case &; see long text | Space: object requires documentation | |
| 386 | 434 |
Timeout - transfer system cannot transmit message further | Space: object requires documentation | |
| 387 | 435 |
You cannot use partial cancellation with this procedure | Space: object requires documentation | |
| 388 | 436 |
Response to message & was received, but not processed | Space: object requires documentation | |
| 389 | 437 |
RFC communication failed: FM &1, destination &2, error: &3&4 | Space: object requires documentation | |
| 390 | 438 |
Cannot find reference message & for message & | Space: object requires documentation | |
| 391 | 439 |
Message & is identical to the rejected message & | Space: object requires documentation | |
| 392 | 440 |
Error in previous message & prevents transmission of current message & | Space: object requires documentation | |
| 393 | 441 |
Function illegal with EDI procedure &1 | Space: object requires documentation | |
| 394 | 442 |
Partial cancellation for ins. provider &1 not permitted (EDI proc. &2) | Space: object requires documentation | |
| 395 | 443 |
Repeated transfer of EDI file &1 for data collection point &2 | Space: object requires documentation | |
| 396 | 444 |
Interchange control reference number cannot be determined for file &1 | Space: object requires documentation | |
| 397 | 445 |
Reference message does not exist for message & | Space: object requires documentation | |
| 398 | 446 |
Estimated length of stay must be extended | Space: object requires documentation | |
| 399 | 447 |
Function is only supported for outbound messages | Space: object requires documentation | |
| 400 | 448 |
Inbound message caused message status to be changed to &1 | Space: object requires documentation | |
| 401 | 449 |
Direct update failed: data stored in BI session ISH_MGRR_ERR | Space: object requires documentation | |
| 402 | 450 |
Function only possible or useful for outbound files | Space: object requires documentation | |
| 403 | 451 |
Data file and order file passed to transfer system again | Space: object requires documentation | |
| 404 | 452 |
Maintain institution indicator of external hospital &1 | Space: object requires documentation | |
| 405 | 453 |
Admitting facility is only relevant with corresponding admission reason | Space: object requires documentation | |
| 406 | 454 |
Maintain positions &1-&2 of admission reason | Space: object requires documentation | |
| 407 | 455 |
&1 segment(s) &2 too many and were deleted -> followup error possible | Space: object requires documentation | |
| 408 | 456 |
File &1 does not belong to insurance provider type &2 | Space: object requires documentation | |
| 409 | 457 |
Manually locked &2 msgs still in inst. &1; you cannot clear release flag | Space: object requires documentation | |
| 410 | 458 |
You cannot release message since earlier messages are still locked | Space: object requires documentation | |
| 411 | 459 |
You cannot lock message since later messages are already released | Space: object requires documentation | |
| 412 | 460 |
Manual lock function not activated. Lock cannot be set. | Space: object requires documentation | |
| 413 | 461 |
Unknown type of data collection point &. Processing discontinued. | Space: object requires documentation | |
| 414 | 462 |
You have to create invoice cancellation message for EDI procedure &1 | Space: object requires documentation | |
| 415 | 463 |
Required segment &1 must occur at least &2 times | Space: object requires documentation | |
| 416 | 464 |
Admission reason &1 incorrect for pre-admission treatment | Space: object requires documentation | |
| 417 | 465 |
Segment &1 deleted since it occurs more than permitted &2 times | Space: object requires documentation | |
| 418 | 466 |
Negative number not permitted in field &1 in segment &2 | Space: object requires documentation | |
| 419 | 467 |
First send existing FEHL messages with program RNC30102 | Space: object requires documentation | |
| 420 | 468 |
Estimated length of stay must be extended | Space: object requires documentation | |
| 421 | 469 |
Data exchange reference is not specified in segment &1 | Space: object requires documentation | |
| 422 | 470 |
Discharge reason &1 requires inst. ind. of admitting inst. in segment &2 | Space: object requires documentation | |
| 423 | 471 |
&2 message was not created for cancellation document &1 | Space: object requires documentation | |
| 424 | 472 |
&1 cancellation msg for cancell. doc. &2 requires original message | Space: object requires documentation | |
| 425 | 473 |
Error while creating &1 cancellation message for cancellation doc. &2 | Space: object requires documentation | |
| 426 | 474 |
Insurance provider &1 does not allow down payment deduction (EDI proc.&2) | Space: object requires documentation | |
| 427 | 475 |
Cannot convert patient weight: &1 &2 | Space: object requires documentation | |
| 428 | 476 |
Artifical respiration duration exceeds permitted value: &1 | Space: object requires documentation | |
| 429 | 477 |
Final invoice amount is negative; see long text | Space: object requires documentation | |
| 430 | 478 |
Institute indicator &1 is invalid | Space: object requires documentation | |
| 431 | 479 |
External ID is not maintained for catalog &1 | Space: object requires documentation | |
| 432 | 480 |
Cannot find copayment transfer posting document &1/&2 (&3) | Space: object requires documentation | |
| 433 | 481 |
FAB segment for specialty &1 was not created | Space: object requires documentation | |
| 434 | 482 |
Weight at admission is not maintained | Space: object requires documentation | |
| 435 | 483 |
Specification in field &1 is too short; provide missing data | Space: object requires documentation | |
| 436 | 484 |
Status of insured is not 99999 although health insurance num. not defined | Space: object requires documentation | |
| 437 | 485 |
Cannot determine full amounts for segment GES | Space: object requires documentation | |
| 438 | 486 |
Cannot make selection using organizational units (EDI procedure &1) | Space: object requires documentation | |
| 439 | 487 |
Cannot make selection using patients or cases (EDI procedure &1) | Space: object requires documentation | |
| 440 | 488 |
Cannot make selection using cases (EDI procedure &1) | Space: object requires documentation | |
| 441 | 489 |
Specifing org. units when "None" is selected has no effect | Space: object requires documentation | |
| 442 | 490 |
Only selection &2 possible with EDI procedure &1 | Space: object requires documentation | |
| 443 | 491 |
Restrict admission/visit date (EDI procedure &1) | Space: object requires documentation | |
| 444 | 492 |
A previously transmitted file was rejected | Space: object requires documentation | |
| 445 | 493 |
&1: last rejected file still to be re-transmitted | Space: object requires documentation | |
| 446 | 494 |
Lock reason (see long text) &1: &2 &3 &4 | Space: object requires documentation | |
| 447 | 495 |
File rejected: No more data transferred (see long text) | Space: object requires documentation | |
| 448 | 496 |
Charge factor value is not a whole number; cannot send message | Space: object requires documentation | |
| 449 | 497 |
Quantity is not a whole number; cannot send message | Space: object requires documentation | |
| 450 | 498 |
File status prohibits reconstruction of file &1 | Space: object requires documentation | |
| 451 | 499 |
Text explanation is required data element | Space: object requires documentation | |
| 452 | 500 |
--------- Monitoring messages -------------------- PS ------------------ | ||
| 453 | 501 |
Enter the name of person responsible | ||
| 454 | 502 |
Monitoring program is already running | ||
| 455 | 503 |
Missing selection criteria | ||
| 456 | 504 |
Check completed - no errors found | ||
| 457 | 505 |
NC02 contains & old dispatch messages | ||
| 458 | 506 |
& batch input sessions are flagged as incorrect | ||
| 459 | 507 |
& IS-H batch input session have file suffix & | ||
| 460 | 508 |
Messages for partner system & not transferred since & (& attempt(s)) | ||
| 461 | 509 |
System & does not exist; cannot transmit messages | ||
| 462 | 510 |
System & is locked - message dispatch currently not possible | ||
| 463 | 511 |
Table NC01 contains & old dispatch orders | ||
| 464 | 512 |
&2 contains old/too many entries. Number of entries: &1. | Space: object requires documentation | |
| 465 | 513 |
Enter a recipient for each active check | ||
| 466 | 514 |
Recipient & (type &) does not exist | ||
| 467 | 515 |
Recipient & (type ) exists, but is not valid | ||
| 468 | 516 |
Type & specified for recipient & is not supported | ||
| 469 | 517 |
Error when checking the recipients & & | ||
| 470 | 518 |
Recipient & is not defined in the system | Space: object requires documentation | |
| 471 | 519 |
Problems occurred when monitor executed | ||
| 472 | 520 |
Time stamp wrongly set in NCMON | ||
| 473 | 521 |
Could not save check results | ||
| 474 | 522 |
Confirmation of receipt: bad update in NCMOS | ||
| 475 | 523 |
Recipient not maintained in NCMON | ||
| 476 | 524 |
& & received EDI messages that can be processed are contained in & | ||
| 477 | 525 |
& contains EDI messages that are older than & days | ||
| 478 | 526 |
&V1& external EDI files have not been processed | ||
| 479 | 527 |
No validity date specified for data collection point & | ||
| 480 | 528 |
Overlapping validity specifications for DC point with institute ind. & | ||
| 481 | 529 |
Institute indicator not defined for data collection point & | ||
| 482 | 530 |
& messages are overdue; start message dispatch | ||
| 483 | 531 |
Message type &: & messages are overdue | ||
| 484 | 532 |
Message type &: & messages pending transmission | ||
| 485 | 533 |
Separators & of data collection point & are not unique | ||
| 486 | 534 |
Specify path for data collection point & | ||
| 487 | 535 |
Communication procedure, standard or version not specified for DCP & | ||
| 488 | 536 |
Inst. &1: files of &4 procedure not imported since &3 on &2 | Space: object requires documentation | |
| 489 | 537 |
Reserved character must be blank | Space: object requires documentation | |
| 490 | 538 |
Only special characters permitted in this field/segment | Space: object requires documentation | |
| 491 | 539 |
Number range adjustment for EDI procedure & not active in institution & | Space: object requires documentation | |
| 492 | 540 |
&1: file &2 (no. &3) has duplicate record numbers | Space: object requires documentation | |
| 493 | 541 |
File &1: record &2 occurs more than once (message no. &3 and &4) | Space: object requires documentation | |
| 494 | 542 |
Message &1 is not contained in a file | Space: object requires documentation | |
| 495 | 543 |
II of admitting institution illegal with discharge reason &1 | The short text describes the object sufficiently | |
| 496 | 544 |
§302-relevant invoice &1 with wrong currency &2 | Space: object requires documentation | |
| 497 | 545 |
Total invoice &1 with wrong currency &2 | Space: object requires documentation | |
| 498 | 546 |
Absence segment ETL with absence reason & missing | Space: object requires documentation | |
| 499 | 547 |
Reason for admission does not match key 1 | Space: object requires documentation | |
| 500 | 548 |
Admission reason 0601 is mandatory for healthy newborn | Space: object requires documentation | |
| 501 | 549 |
Admission reason 01 is mandatory for sick newborn | Space: object requires documentation | |
| 502 | 550 |
Institution &1 has no communication procedure with def. residence time | Space: object requires documentation | |
| 503 | 551 |
Case &1 has EDI messages that must not be archived | Space: object requires documentation | |
| 504 | 552 |
File &1 found for DCP &2. Clarify gap in numbering. | Space: object requires documentation | |
| 505 | 553 |
No validity period found for data collection point &1 | The short text describes the object sufficiently | |
| 506 | 554 |
ETL segment will not be created for department &1 (discharge date &2) | The short text describes the object sufficiently | |
| 507 | 555 |
Aborting file creation since file would contain single invoices | Space: object requires documentation | |
| 508 | 556 |
Cancellation doc. (for copayt tranfer post.doc.) &1/&2 not found (&3) | Space: object requires documentation | |
| 509 | 557 |
Back posting document &1/&2 was not found (&3) | Space: object requires documentation | |
| 510 | 558 |
Enter referring physician or plant number | Space: object requires documentation | |
| 511 | 559 |
Complete readmission case: Unable to determine reason for case merging | Space: object requires documentation | |
| 512 | 560 |
Mode is only supported for one data collection point | The short text describes the object sufficiently | |
| 513 | 561 |
Interim billing with copayment, but max.copayment amount/year not reached | Space: object requires documentation | |
| 514 | 562 |
Insurance provider &2: deducting copayment from several invoices | Space: object requires documentation | |
| 515 | 563 |
Insurance provider &1 has incorrect copayment procedure (&2) | Space: object requires documentation | |
| 516 | 564 |
Case &1, insurance provider &2: Copayment not entered in full | Space: object requires documentation | |
| 517 | 565 |
Case &1: Copyt not made for outpt surgery. Copyt reas. cannot be created | Space: object requires documentation | |
| 518 | 566 |
Value &4 in explanation of ind. remuneration not allowed for this AMBO | Space: object requires documentation | |
| 519 | 567 |
Multiple or no P116b service areas found | Space: object requires documentation | |
| 520 | 568 |
Invalid combination of charge keys | Space: object requires documentation | |
| 521 | 569 |
Character set &1 is not supported for procedure &2 | The short text describes the object sufficiently | |
| 522 | 570 |
Service area (code 22) for billing according to P116b SGB V is missing | Space: object requires documentation | |
| 523 | 571 |
Segment &1 of message contains characters that are not supported | Space: object requires documentation | |
| 524 | 572 |
Back posting document &1/&2 does not belong to copayment rec. &3/&4 | Space: object requires documentation | |
| 525 | 573 |
Copayment receivable document &1/&2 not found | Space: object requires documentation | |
| 526 | 574 |
Pack posting document not found for copayment receivable &1/&2 | Space: object requires documentation | |
| 527 | 575 |
PRZ segment not created for procedure &1 | Space: object requires documentation | |
| 528 | 576 |
FAB segment was not created for procedure &2 | Space: object requires documentation | |
| 529 | 577 |
Service &1 is relevant for fee total - not allowed for this AMBO | Space: object requires documentation | |
| 530 | 600 |
>>>>> Start of General BAPI Messages (No Application) | Space: object requires documentation | |
| 531 | 601 |
Mandatory parameter &1 not filled (module &2) | Space: object requires documentation | |
| 532 | 602 |
Field content &1 different from data type &2 of field &3 | Space: object requires documentation | |
| 533 | 603 |
Current client is &1, but data is determined for client &2. | Space: object requires documentation | |
| 534 | 604 |
Unit of measure cannot be changed. Catalog value applies. | Space: object requires documentation | |
| 535 | 605 |
Desired function not possible without value in field &1. | Space: object requires documentation | |
| 536 | 606 |
Referenced address data &2 in &1 does not exist in &3 | Space: object requires documentation | |
| 537 | 607 |
Further telephone data for address &1 does not exist in &2 | Space: object requires documentation | |
| 538 | 608 |
Import file &1 of DCP &2 (explicit file specification) | Space: object requires documentation | |
| 539 | 609 |
You are not authorized to read file &1 | The short text describes the object sufficiently | |
| 540 | 610 |
Function only supported for inbound EDI messages | Space: object requires documentation | |
| 541 | 611 |
S_DATASET authorization (program &1, act. &2, file *) is missing | Space: object requires documentation | |
| 542 | 612 |
Message context does not exist | Space: object requires documentation | |
| 543 | 613 |
Multiple selection not possible for this operation | Space: object requires documentation | |
| 544 | 614 |
Select either inbound messages or outbound messages | Space: object requires documentation | |
| 545 | 615 |
Function is only supported for outbound messages | Space: object requires documentation | |
| 546 | 616 |
All messages must have only one status | Space: object requires documentation | |
| 547 | 617 |
Error situtation: current change undone | Space: object requires documentation | |
| 548 | 620 |
File &1 found for transfer system &2 | Space: object requires documentation | |
| 549 | 625 |
File &1 has already been rejected | Space: object requires documentation | |
| 550 | 700 |
------- DALE-UV Messages Start Here ---------- | The short text describes the object sufficiently | |
| 551 | 701 |
Segment &1: type of treatment - internal billing type &1 unknown | The short text describes the object sufficiently | |
| 552 | 702 |
Segment &1: service item - no services found | The short text describes the object sufficiently | |
| 553 | 703 |
Segment &1: internal billing type cannot be determined | The short text describes the object sufficiently | |
| 554 | 704 |
Space: object requires documentation | ||
| 555 | 705 |
Segment &1: institute indicator cannot be determined | The short text describes the object sufficiently | |
| 556 | 706 |
Check module: technical error | Space: object requires documentation | |
| 557 | 707 |
Error in check module call | Space: object requires documentation | |
| 558 | 708 |
Check module: RFC connection &1 failed | Space: object requires documentation | |
| 559 | 709 |
Check module: &1 could not be written | Space: object requires documentation | |
| 560 | 710 |
Case &1 does not have insurance relationship for insurance provider &2 | The short text describes the object sufficiently | |
| 561 | 711 |
A data collection point is not assigned to accident ins. consultant &1 | The short text describes the object sufficiently | |
| 562 | 712 |
Data collection point &1 does not exist or is not valid at this time | The short text describes the object sufficiently | |
| 563 | 713 |
Check module: &3 (error code: &1, field: &2) | Space: object requires documentation | |
| 564 | 714 |
Insurance provider &1 is not an accident insurance carrier | Space: object requires documentation | |
| 565 | 715 |
Message confirmed: status code &1, date &2, time &3 | Space: object requires documentation | |
| 566 | 716 |
Confirmation: &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 567 | 717 |
Cannot determine responsible accident insurance consultant | Space: object requires documentation | |
| 568 | 718 |
Message &1 was not found | Space: object requires documentation | |
| 569 | 719 |
DCP was not found for accident insurance consultant &1 | Space: object requires documentation | |
| 570 | 720 |
File &1: status of message &2 was set | The short text describes the object sufficiently | |
| 571 | 721 |
XML parser: &1 (row/column: &2/&3) | The short text describes the object sufficiently | |
| 572 | 722 |
An II number is not assigned to accident ins. consultant &1 | The short text describes the object sufficiently | |
| 573 | 723 |
Data collection point for UNIDAV &1 not found | The short text describes the object sufficiently | |
| 574 | 724 |
Accident ins. consultant cannot be found for OU &1 with movement type &2 | The short text describes the object sufficiently | |
| 575 | 725 |
Error occurred generating PDF file | The short text describes the object sufficiently | |
| 576 | 726 |
Command is too long; current length &1; permitted length &2 | The short text describes the object sufficiently | |
| 577 | 727 |
Error writing XML file: &1 | The short text describes the object sufficiently | |
| 578 | 800 |
>>>>>>>>>> Test messages start here <<<<<<<<<<<<<<<<<<<<<< | ||
| 579 | 801 |
Enter a modification ID or a planning object | Space: object requires documentation | |
| 580 | 802 |
Enter an institution | Space: object requires documentation | |
| 581 | 803 |
Enter a planning object | Space: object requires documentation | |
| 582 | 804 |
Enter a date | Space: object requires documentation | |
| 583 | 810 |
Order file & exists, but is empty | Space: object requires documentation |
History
| Last changed on/by | |
20131127 | SAP |
| SAP Release Created in |
