Error |
Possible Causes / Further Steps |
|---|---|
Content import fails without error message in case of large files |
Occurs when the maximum request size for HTTP requests in the ICM is exceeded. Can be avoided by the parameter icm/HTTP/max_request_size_KB in the transaction rz10. |
Segment not found: “Error occurred at X12/TRA document character [...]: Cannot find segment ... for CTRL_KEY 1, VERSION [...] and SET_NAME [...] from segment [...] “ |
ANSI X.12/TRADACOMS: A segment within the message could not be parsed because it is not contained in the tables. |
EDIFACT/ODETTE: Segment not found: Cannot find next state and action for current state "B2B,UNH" and segment "[...]" |
A segment within the message could not be parsed because it is not contained in the tables. |
Error occurred at X12 document character 3: Segment has to start with segment ISA but starts with [...] |
ANSI X.12 documents have to start with an ISA segment. |
Error occurred at X12 document character [...], cause while trying to invoke the method com.sap.aii.converter.x12.x122xml.segments.GSSegment.getVersionReleaseIndustryIdentifierCode() of an object loaded from local variable 'gsSegment' |
ANSI X.12: Version information could not be extracted from the document because no GS segment was found. |
Error in conversion of null/null-Edifact-Document at character [...]to XML: java.lang.UnsupportedOperationException: |
EDIFACT: No UNH segment found in the message. |
Error in conversion of [...]-Edifact-Document at character [...]to XML: java.lang.UnsupportedOperationException: No ruleset for [...] available. |
EDIFACT: The combination of message type and version specified in the UNH segment is not maintained in the tables. |
Error occured at X12 document character [...]: Cannot find conversion rules for [...] |
ANSI X.12: The combination of SET_NAME and VERSION specified in the GS and ST segment is not maintained in the tables. |
Message not processed correctly if several UNA or ISA segments occur. |
The converter does not throw an error but converts only the first message. The EDI separator should be used for a complete processing. |
Error in test tool during reconversion |
This can be due to several reasons: |
(Content Import/Changes) Duplicate Key Exception: “import failed: set failed: Violation of PRIMARY KEY constraint 'PK_B2B_X12_DEF_FIEL_008CAF8B'. Cannot insert duplicate key in object 'dbo.B2B_X12_DEF_FIELD'.” |
If the tables already have contents which have been overwritten during the import, select Overwrite duplicate keys. This is also the case for the CTRL_IF table which is contained in every message-export. |
Error occurred at [...] document character 3: Segment has to start with segment [...] but starts with  |
The document was neither detected as XML nor as EDI document. Maybe there is an encoding problem. |
XML-Parser error occurred while parsing: org.xml.sax.SAXParseException: The element type "[...]" must be terminated by the matching end-tag "</[...]>". |
The XML is not well-formed. |
Error occured at [...] document character [...]: A Component or Data Field Element for the segment [...] at index [...] was not found for CTRL_KEY 1 and VERSION [...] |
A segment in the message contains more fields than specified in the table for the segment. |
Cannot find composite #1 for segment [...] |
Content of the table B2B_[...]_CTRL_SEG does not match the document since no composite is defined for the specified index. |
Found more than one entry in B2B_EDI_CTRL_SEG with [...] |
Content of the table B2B_[...]_CTRL_SEG does not match the document since several composites are defined for the for the specified index |
Cannot find composite field #[...] for composite [...] |
Content of the table B2B_[...]_CTRL_CMP does not match the document since no composite is defined for the specified index |
Found more than one entry in B2B_EDI_CTRL_CMP with [...] |
Content of the table B2B_[...]_CTRL_CMP does not match the document since several composites are defined for the specified index |
End of input stream reached, no Edifact-Segment identifier found |
The document does not end with an segment terminator |
Cannot read next data element, separator * or terminator + was not found, cause: null |
Unexpected end of the ANSI X.12 document |
Error occurred at X12 document character [...]: A Component or Data Field Element for the segment [...] at index [...] was not found for CTRL_KEY 1 and VERSION [...] |
More elements found in the message than specified in the tables |
Cannot find actions for state [...] and set [...] for input [...] |
No entry matching the thecribed state and set can be found in the table B2B_PLA_CTRL_MSG. Check the message's nesting structure and the conversion rules in the table. |
Cannot find control key in table B2B_PLA_CRL_IF [...] |
The table contains an invalid entry. A common error is the specification of an invalid regular expression in the column PATTERN |
Cannot find a matching configuration for [...] |
The table B2B_PLA_CRL_IF does not contain an entry that matches the Sender, Receiver, Interface or content of the processed message |
Cannot find a matching set-pattern for line [...] |
The table B2B_PLA_CRL_SET does not contain a regular expression in the column, PATTERN that matches the parsed line |
The field content [...] has a length of [...] but the maximal allowed length for the field [...] |
When converting an XML document to plain the content of an XML-element is larger than the allowed Field length specified in B2B_PLA_CRL_FIELD. The conversion was stopped to prevent data loss. Correct the XML-document or change the field definition in the table. |
VDA: FieldNotFoundException |
The table B2B_VDA_CTRL_FIELD contains no entry for the specified field. Check the table content for the specified set. |
The content [...] of field [...] in set [...] version [...] is too long; the maximal length is [...] |
The content of an XML-element is too long to fit in the specified field. The conversion was stopped to prevent data loss. |
Cannot find a matching configuration for [...] |
The table B2B_VDA_CTRL_IF does not contain an entry that matches the Sender, Receiver or Interface of the processed message. |
Overview
Content Tools