Data elements & code sets directory - GS1

More documents

Recommendations

Info

EANCOM® 2002 Part III Data Element & Code Sets Directory 0083 Action, coded A code indicating acknowledgement, or rejection (the action taken) of a subject interchange, or part of the subject interchange. 8 = Interchange received Indication of interchange receipt implies that the recipient of the subject interchange: has received the interchange; and acknowledges the parts of the interchange that have been checked in order to assure that the data elements copied into the reporting UCI segment are syntactically correct; and has accepted liability for notifying the sender of acknowledgement or rejection of the other parts of the interchange; and has taken reasonable precautions in order to ensure that the sender is so notified. S Old Code 0085 Syntax error, coded A code indicating the syntax error detected. 1 = UNA not supported (GS1 Code) Notification that the UNA character string cannot be understood or complied with. 2 = Syntax level or version not supported Notification that the syntax version and/or level is not supported by the recipient. 3 = Message version/release not supported (GS1 Code) Notification that the message type, version number and/or release number in the UNG and/or UNH segments are not supported by the recipient. 6 = Data segment missing/invalid (GS1 Code) Notification that a data segment is missing, contains invalid data or cannot be processed for any reason. 7 = Interchange recipient not actual recipient Notification that the Interchange recipient (S003) is different from the actual recipient. 9 = Mandatory data element missing (GS1 Code) Indication that a mandatory data element is missing in a service or data segment. 11 = Password invalid (GS1 Code) @ 12 = Invalid value @ 13 = Missing Indication that the password in segment UNB is invalid. Notification that the value of a simple data element, composite data element or component data element does not conform to the relevant specifications for the value. Notification that a mandatory (or otherwise required) service or user segment, data element, composite data element or component data element is missing S Old Code 10 4, 6 © Copyright GS1 - 40 - Edition 2012
EANCOM® 2002 Part III Data Element & Code Sets Directory 0085 Syntax error, coded A code indicating the syntax error detected. 14 = Value not supported in this position Notification that the recipient does not support use of the specific value of an identified simple data element, composite data element or component data element in the position where it is used. The value may be valid according to the relevant specifications and may be supported if it is used in another position. 15 = Not supported in this position Notification that the recipient does not support use of the segment type, simple data element type, composite data element type or component data element type in the specific in the identified position. @ 16 = Too many constituents Notification that the identified segment contained to many data elements or that the identified composite data element contained too many component data elements. 17 = No agreement No agreement exist that allows receipt of an interchange, functional group or message with the value of the identified simple data element, composite data element or component data element. 18 = Unspecified error Notification that an error has been identified, but the nature of the error is not reported. 19 = Invalid decimal notation Notification that the character indicated as decimal notation in UNA is invalid, or the decimal notation used in a data element is not consistent with the one indicated in UNA. 20 = Character invalid as service character Notification that a character advised in UNA is invalid as service character. 21 = Invalid character(s) Notification that one or more character(s) used in the interchange is not a valid character as defined by the syntax level indicated in UNB. The invalid character is part of the referenced-level, or followed immediately after the identified part of the interchange. 22 = Invalid service character(s) Notification that the service character(s) used in the interchange is not a valid service character as advised in UNA or not one of the service characters in the syntax level indicated in UNB or defined in an interchange agreement. If the code is used in UCS or UCD, the invalid character followed immediately after the identified part of the interchange. 23 = Unknown interchange sender 24 = Too old Notification that the Interchange sender (S002) is unknown. Notification that the received interchange or functional group is older than a limit specified in an IA or determined by the recipient. S Old Code 8 © Copyright GS1 - 41 - Edition 2012
Page 1 and 2: EANCOM 2002 PART III Edition 2012
Page 3 and 4: EANCOM® 2002 Part III Data Element
Page 39: EANCOM® 2002 Part III Data Element
Page 91 and 92:
EANCOM® 2002 Part III Data Element
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367:
show all

Data elements & code sets directory - GS1

Create successful ePaper yourself

Delete template?

Save as template?