Skip to Content
avatar image
Former Member

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

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

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Apr 05, 2017 at 10:53 AM

    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

    Add comment
    10|10000 characters needed characters exceeded