BoostAero XML and CSV Implementation Guideline ... - SupplyOn

7 Routing/Syntax check & error handlingIn case of routing or syntax errors, a dedicated message, type Status Notification, is used. The messagewill be sent via AS2 to the supplier. The message contains an error code .7.1 Error codes for all message typesError code Error Case Error Type DescriptionR001 Authorization error ROUTING ERRORSender ID and OrgCode within themessage mismatch with the BIS partnername stored in the CPR002 No entity found ROUTING ERRORNo entity was found in BIS TPM matchingwith the data from the messageR003 no buyer CP found ROUTING ERRORNo buyer CP found with the CP namegiven in the messageR004no networklinkNo networklink found with the buyer CPROUTING ERROR and the sellernumber given in thefoundmessageR005 no seller CP found ROUTING ERRORSeller CP given in the selected networklinkdoes not existR006R007R008R009no networkcommunicationrecord foundno supplytriggerfoundUnauthorized sellerControlPointMultiple sellerControlPointsROUTING ERRORROUTING ERRORROUTING ERRORROUTING ERRORS001 Parsing failed SYNTAX ERRORS002S003S004S005S006Mandatory fieldmissingfield content toolongField content tooshortmismatching fieldtypeInvalid QualifierSYNTAX ERRORSYNTAX ERRORSYNTAX ERRORSYNTAXERRORSYNTAXERRORS007 Repetition Error SYNTAX ERRORC001 Missing reference CONTENT ERRORC002 Old message CONTENT ERRORNo network communication record foundat the networklink with matching logicalfilenameNo SupplyTrigger found in selectednetwork communication recordFor messages sent from a sellsidepartner: The seller ControlPoint which wasdetermined is not assigned to thecommunication partner that has sent themessageFor messages sent from a sellsidepartner: There is more than one sellerControlPoint ID determined within onetransmissionSupplyOn is not able to parse the filebecause it’s not well formed or invalidregarding to the respective XSDA field defined mandatory in the interfacedescription is missingThe content of a field exceeds the max.length defined in the format descriptionThe content of a field falls below the min.length defined in the format descriptionThe content of a field doesn’t match thetype specified in the interface descriptionA code or qualifier within a field isunknownToo much repetitions for a field orsegmentA business object referenced in amessage doesn’t existA newer record than the importedmessage already exists *C003 Duplicate message CONTENT ERROR The message was already importedPublic 27/59