Skip to Content
0

no ruleset for Control Key/Message Type/ Message version/ Message sub version:

Feb 28, 2017 at 08:41 AM

134

avatar image

Hello Experts,

I have configured an EDI to IDOC scenario, where we have used EANCOM (ORDERS/D01B) as our source structure, when our customer sends us EANCOM Message, the message failing in Sender Comm. Channel with the following error:

Lib.mp.module.ModuleException: Error in conversion of ORDER/01B-Edifact-Document at character 955 to XML
UnsupportedOperationException no ruleset for Control Key/Message Type/ Message version/ Message sub version: 1/ORDERS/01B/000000 available in table B2B_EDI_CTRL_MSG


The customer sends us the following message header:
UNA:+.? '
UNB+UNOC:3+GEID+TPID+20151130:1025+5'
UNH+1+ORDERS:D:01B:UN'

Our B2B-Table (B2B_EDI_CTRL_MSG) looks as follows.


Has anyone had such a problem?
So, I hope someone can help to solve this issue.

Thanks in advanced.
Kind regards
Ahmed

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Konrad Thalheim Apr 05, 2017 at 10:53 AM
0

Hi Ahmed,

your partner sends a standard edifact message not an eancom.

UNH+1+ORDERS:D:01B:UN'

Kindly try to use the localejbs/EdifactConverterModule insteadaaaa localejbs/EdifactConverterModule instead. EANCOM needs a pattern like this: UNH+1+ORDERS:D:01B:UN:EAN010'

Best regards

Konrad

Share
10 |10000 characters needed characters left characters exceeded