We installed new SAP PI NW 7.50 with Seeburger 2.2.3
In an AS2 sender channel we use BIC module. When sending a test AS2 message via Mendelson test tool we get the error below. Who can help?
Error in BICMODULE:Temporary error: BIC XI Adapter call failed. Reason: InhouseDocReader doSyntaxCheck(): offset[239]: the found segment '------=_PART_25_5659208.1503648549976CONTENT-TYPE: APPLICATION/EDIFACTCONTENT-TRANSFER-ENCODING: BINARYCONTENT-DISPOSITION: ATTACHMENT; FILENAME=WAYFAIR_ORDERS_EXAMPLE.EDIUNB' is not in the message description. DESCRIPTION: The detected segment/record is missing in the message description. Please check the name and the key settings of that segment/record, the file encoding and the delimiters (especially line/segment delimiters). -module:BICMODULE:Temporary error: BIC XI Adapter call failed. Reason: InhouseDocReader doSyntaxCheck(): offset[239]: the found segment '------=_PART_25_5659208.1503648549976CONTENT-TYPE: APPLICATION/EDIFACTCONTENT-TRANSFER-ENCODING: BINARYCONTENT-DISPOSITION: ATTACHMENT; FILENAME=WAYFAIR_ORDERS_EXAMPLE.EDIUNB' is not in the message description. DESCRIPTION: The detected segment/record is missing in the message description. Please check the name and the key settings of that segment/record, the file encoding and the delimiters (especially line/segment delimiters).
1 Answer
-
Best AnswerSep 04, 2017 at 05:41 PM
I was able to find the root cause. The error was not in the Seeburger BIC module but in the Seeburger Classifier module. The classifier did not correctly detect the content type of the incoming file. When I sent an EDIFACT message, via an AS2 sender channel to SAP PO, the module returned content type Inhouse rather then EDIFACT. After I reported this to the Seeburger company, they provided a hotfix which I tested successfully.
Wilbert Karremans
Add comment
Add comment