ORDERS 93A EAN007 - EDIFACT vs EANCOM

[Former Member]

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.

[Dimitri]

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

[Former Member]

Hi Dimitri,

What settings do you need?  TPM Agreements? Or Integration Builder configuration?

[Dimitri]

Hi,

Please have a look at

Kind regards,

Dimitri

[Former Member]

Hi Dimitri,

B2B Toolkit System Information is as below;

SAP PO ESB is as below;

IB Adapter's is as below;

In B2B Toolkit Admin Cockpit EANCOM and EDIFACT SP04 contents are uploaded.

Before uploading EANCOM content everything worked fine.

After uploading EANCOM content all messages started to process as EANCOM.

I have two issues now;

First issue is I want to process ORDERS 93A as EDIFACT message.

The trading agreement is as below;

EDI Receiver Comm Channel is configured as;

Read from Dynamic Headers is checked.

In module tab;

When I try to process an ORDER 93A message I am getting an error as below;

05.04.2016 12:16:17.451	Information	TPM AckHandler Module: Sender party: TIMKEN found for party ID=1775757487TKFR party Qual=ZZ.
05.04.2016 12:16:17.451	Information	TPM AckHandler Module: successfully retrieved sender information from payload: sender ID=1775757487TKFR sender Qual=ZZ
05.04.2016 12:16:17.452	Information	TPM AckHandler Module: Receiver party: ORS found for party ID=TRODRULM.TRODR001 party Qual=ZZ.
05.04.2016 12:16:17.454	Information	MP: processing local module localejbs/GenericConverterModule
05.04.2016 12:16:17.454	Information	TPM AckHandler Module: Processing finished
05.04.2016 12:16:17.455	Information	B2B GenericConverterModule calling EDI Module localejbs/EdifactConverterModule
05.04.2016 12:16:17.455	Information	B2B GenericConverterModule is being executed
05.04.2016 12:16:17.456	Information	B2B EdifactConverterModule : EDI format detected as EANCOM
05.04.2016 12:16:17.456	Information	B2B EdifactConverterModule: Message will be read with encoding:ISO-8859-1.
05.04.2016 12:16:17.456	Information	B2B EdifactConverterModule: The module-paramteter "eancom.subversion.prefix" is not set. Using default value "false"
05.04.2016 12:16:17.464	Error	MP: exception caught with cause com.sap.aii.af.lib.mp.module.ModuleException: Error in conversion of ORDERS/93A-Edifact-Document at character 575 to XML: java.lang.UnsupportedOperationException: No ruleset for Control key/Message Type/Message version/Message sub version: -1/ORDERS/93A/000000 available in table B2B_EDI_CTRL_MSG.
05.04.2016 12:16:17.466	Error	Exception caught by adapter framework: Error in conversion of ORDERS/93A-Edifact-Document at character 575 to XML: java.lang.UnsupportedOperationException: No ruleset for Control key/Message Type/Message version/Message sub version: -1/ORDERS/93A/000000 available in table B2B_EDI_CTRL_MSG.

I dont know why it is not taking (Control Key SAP - 1 ) . But trying with -1. And saying EDI format detected as EANCOM.

Second issue is;

When I try to process ORDCHG 93A EAN007, even though there is no message for EANCOM in B2B Cockpit. Receiver communication channel tries to process message as EANCOM.

But I can not generate any XSD because I dont have it in EANCOM content.

Could you please help?

Thanks,

Faruk.

[Dimitri]

Please check step 5.2 in the link I provided above.

Also, make sure your B2B components are all on the same SP level. That is important and also adviced by SAP.

[Former Member]

Hi Dimitri,

Here is the control key scenario association for EDIFACT and EANCOM.

If i delete the EANCOM Scenario Association I still can see the Information message in Receiver Communication Channel as below. And I cannot set 'SAP' as control key for Message Format EANCOM.

Searching sender channel for Eancom message part message with Message type ORDERS, Message version number D, Message release number 93A, Interchange sender identification 1775757487TKFR, Interchange sender identification code qualifier , Interchange recipient identification TRODRULM.TRODR001, Interchange recipient identification code qualifier ZZ, Message Subversion EAN007, Message Agency UN

What I really want and need  is : Is there anyway for this to search for Edifact sender channel? Why does it search for it? Or how can I force it to search for Edifact ?

Thanks,

Faruk.

[Dimitri]

Hi Faruk,

Please make sure you have all in place. Use my link for that.

I do not see any control key associated with ORDERS/93A. Therefore, you receive the error.

Make sure all is in place and test again.

Kind regards,

Dimitri

[Former Member]

Hi Dimitri,

I will check the system and compare with the link you provided.

Additionally, how can I associate Message with Control Key?

I can not set it in Control Key Scenario Association, because there is no field for message type.

Thanks,

Faruk

[Dimitri]

Follow my link and revert back in case of problems.

Please make sure to provide screenshots in that case

[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