Skip to Content
avatar image
Former Member

ORDERS 93A EAN007 - EDIFACT vs EANCOM

Hi Experts,

We were using EDIFACT-to-XML for converting EANCOM files.

But when we uploaded EANCOM content to SAP PO Development server every EANCOM message is processed as EANCOM not EDIFACT.

I dont want to change the Integration Builder configuration for Production System and mappings too.

Is there anyway to process those files as EDIFACT message? Or remove EANCOM content from server?

I tried TPM agreement(Control Key = SAP(EDIFACT)) but it did not seem to work. Messages were processed as EANCOM again.

I would really appreciate your help.

Thanks,

Faruk.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Apr 05, 2016 at 06:16 AM

    Can you share your B2B Integration Cockpit settings and an example file?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Faruk,

      Did you ever find solution to your issue? I seem to be having a similar issue. I cant access the TPM configuration via the converter module.

      First, I get this warning:


      TPM AckHandler Module: Sender party not found for party ID=5790009999999 party Qual=14. Finishing Module Processing


      Then this error:

      Message could not be forwarded to the JCA adapter. Reason: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error in conversion of ORDERS/96A-Edifact-Document at character 515 to XML: java.lang.UnsupportedOperationException: No ruleset for Control key/Message Type/Message version/Message sub version: -1/ORDERS/96A/000000 available in table B2B_EDI_CTRL_MSG.


      I have tested the message with the manual conversion, and here it works fine. I have tried to both setup a custom Control Key and tried using the default SAP control key. Nothing seems to work.

      Any help would be much appreciated.

      Thanks.

      Emil