Exception caught by adapter framework: No configuration / default adapter specified for EDISeparator

[saurabhkumbhare]

Hello Experts,

I am configuring the scenario ( AS2 to EDISeparator and EDISeparator to IDOC ).

Can you please help me with the error below which is from the either the EDISeparator Receiver channel or the EDISeparator Sender channle.

09.06.2014 17:52:18.709	Information	Message is encrypted with 1.3.14.3.2.7 algorithm
09.06.2014 17:52:18.778	Information	AS2 Message is signed with SHA1 (1.3.14.3.2.26) algorithm
09.06.2014 17:52:18.779	Information	AS2 Message message signature is validated, signer ID is X509CertSelector: [ Serial Number: 1624063516 Issuer: CN=Mendelson AS2 TEST,OU=Integration,O=Mendelson,L=Berlin,ST=Unknown,C=GE matchAllSubjectAltNames flag: true ]
09.06.2014 17:52:18.784	Information	AS2 document size is 350 Bytes
09.06.2014 17:52:18.784	Information	Payload charset converted from ISO-8859-15 to ISO-8859-15
09.06.2014 17:52:18.785	Information	B2B EdifactConverterModule : EDI format detected as EANCOM
09.06.2014 17:52:18.785	Information	B2B EdifactConverterModule: Message will be read as ISO-8859-1.
09.06.2014 17:52:18.785	Information	MP: processing local module localejbs/EdifactConverterModule
09.06.2014 17:52:18.785	Information	0}: The module-paramteter "eancom.subversion.prefix" is not set. Using default value "false"
09.06.2014 17:52:18.786	Information	0}: The module-paramteter "eancom..audit" is not set. Using default value "false"
09.06.2014 17:52:18.791	Information	MP: processing local module localejbs/CallSapAdapter
09.06.2014 17:52:18.791	Information	Application attempting to send an XI message asynchronously using connection AS2_http://sap.com/xi/XI/AS2
09.06.2014 17:52:18.792	Information	Trying to put the message into the send queue
09.06.2014 17:52:18.831	Information	Message successfully put into the queue
09.06.2014 17:52:18.831	Information	The application sent the message asynchronously using connection AS2_http://sap.com/xi/XI/AS2. Returning to application
09.06.2014 17:52:18.836	Information	MIC (DeJYUIusqQj6aaYRASdHhAo+4J0=) is calculated using SHA1 algorithm.
09.06.2014 17:52:18.838	Information	The message was successfully retrieved from the send queue
09.06.2014 17:52:18.843	Information	Message status set to DLNG
09.06.2014 17:52:18.845	Information	MDN is succcessfully signed with SHA1 (1.3.14.3.2.26) algorithm
09.06.2014 17:52:18.859	Information	Trying to put the message into the send queue

09.06.2014 17:52:18.912	Information	Message successfully put into the queue
09.06.2014 17:52:18.913	Information	The message was successfully retrieved from the send queue
09.06.2014 17:52:18.918	Information	Message status set to DLNG
09.06.2014 17:52:18.961	Information	Trying to put the message into the send queue
09.06.2014 17:52:19.001	Information	Message successfully put into the queue
09.06.2014 17:52:19.001	Information	The message was successfully retrieved from the send queue
09.06.2014 17:52:19.006	Error	MP: exception caught with message No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.006	Information	Delivering to channel: B2BSE00002_O2C_ORDERS_VANS_PO_WRITE_EDISeparator
09.06.2014 17:52:19.006	Information	Message status set to DLNG
09.06.2014 17:52:19.009	Error	Exception caught by adapter framework: No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.010	Error	Transmitting the message to endpoint <local> using connection AS2_http://sap.com/xi/XI/AS2 failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.015	Information	The asynchronous message was successfully scheduled to be delivered at Mon Jun 09 17:57:19 CEST 2014
09.06.2014 17:52:19.015	Information	Message status set to WAIT

[saurabhkumbhare · Accepted solution]

Hello Dimitri,

The scenario is

1. VAN ( AS2 )  -> SAP PO ( EDISeparator )

2.        SAP PO ( EDISeparator ) -> ECC ( IDoc )

Here are the screenshots of the configuration as requested:

Sender Interface :

Receiver Interface :

Sender AS2 config :

Receiver EDISeparator config :

Sender EDISeparator config :

Receiver IDOC config :

IDoc details configured but not added in this document

Please let me know if you want me to check more.

Thanks

Saurabh.

[Dimitri · Accepted solution]

Hi Saurabh,

Just a quick one: I still see EDIFACT configuration within the receiver EDIseparator adapter. Please do use EANCOM settings.

Try to leave out the 111111 and 33333 and try to be as generic as possible until you identified the problem.

Kind regards,

Dimitri

[ruchir_sinha · Accepted solution]

Hi Saurabh,

Sorry for responding late. I was unwell.

Thanks for asking to share the scenario. I wanted to do the same.

@Saurabh: I request you to remove the EDIFACTConverterModule which you have put on the AS2Receiver Adapter.

It is first converting to XML and then trying to split which is wrong. After splitting it should convert to XML which you have already put after the EDI Separator Sender adapter.

Best Regards,

Ruchir

[saurabhkumbhare]

Hello Experts,

The above error was solved. In the receiver EDISeparator adaptor ( under module configuration ), the Type was changed from Java Library to Local Enterprise Bean. ( my mistake ).

Now the scenario is working.

All credits to and .

Thanks a lot experts!! Feel relieved!!!

Thanks

Saurabh

[saurabhkumbhare]

Hello and ,

I think I have progressed a bit. Just unsure of the usage of the Module configuration .I now get a new error (see below) and the updated config details are :

Sender Interface :

Receiver Interface :

Sender AS2 config :

Receiver EDISeparator config :

Sender EDISeparator config :

Receiver IDOC config :

IDoc details configured but not added in this document

16.06.2014 11:52:35.414	Information	The message was successfully retrieved from the send queue
16.06.2014 11:52:35.420	Information	Delivering to channel: B2BSE00002_O2C_ORDERS_VANS_PO_WRITE_EDISeparator
16.06.2014 11:52:35.420	Information	MP: processing local module localejbs/ModuleProcessorExitBean
16.06.2014 11:52:35.420	Information	Message entered AF MP exit bean and will now be passed to the JCA adapter
16.06.2014 11:52:35.420	Information	Message status set to DLNG
16.06.2014 11:52:35.433	Information	UNA segment UNA found
16.06.2014 11:52:35.444	Information	Parsed UNB segment 333333333/014 to 111111111/014
16.06.2014 11:52:35.445	Information	Parsed UNH segment ORDERS D96A
16.06.2014 11:52:35.514	Information	Searching sender channel for Eancom message part message with Message type ORDERS, Message version number D, Message release number 96A, Interchange sender identification 333333333, Interchange sender identification code qualifier 014, Interchange recipient identification 111111111, Interchange recipient identification code qualifier 014, Message Subversion EAN008, Message Agency UN
16.06.2014 11:52:35.579	Information	Sender channel (Channel) keys: ObjectId=7abf551ddbb638268f91af80ec1c04c8 values: ToPartySchema= Attributes=(Attributes:Channel:EDISeparator:INBOUND) values: edisep.advanced=false snd.interchangeSenderId=.* snd.tradacommessagetype=.* snd.xpath= snd.xpath.value= snd.filterCondition=equal snd.edifactMessageReleaseNumTxt= snd.tradacomMessageTypeUsingFreeText=false snd.eancomMessageReleaseUsingFreeText=false snd.eancomMessageVersionFreeText= snd.odetteMessageType=.* snd.edifactMessageVersion=.* snd.xml.splitPath=null snd.eancomMessageVersion=.* snd.odetteMessageVersion=.* snd.edifactMessageRelNumUsingFreeText=false snd.otherVersionReleaseIndustryIdentifierCodeEnabled=false adapterStatus=active snd.vdaMessageType=.* snd.eancomCONTRLMessageRelease=3 snd.odetteMessageTypeTxt= snd.tradacommessageversion=.* snd.edifactMessageVerNumUsingFreeText=false snd.edifactMessageTypeUsingFreeText=false snd.xpathUsingFreeText=false snd.interchangeSenderIdCode=.* snd.otherVersionReleaseIndustryIdentifierCode=.* snd.odetteMessageTypeUsingFreeText=false snd.tradacomreccode=.* snd.edifactMessageVersionFreeText= snd.edifactInterchangeRecipientIdentification=.* eoio.sequenceId= snd.edifactMessageTypeTxt= snd.odetteMessageVerNumUsingFreeText=false snd.eancomMessageVerNumUsingFreeText=false snd.interchangeReceiverId=.* snd.eancomMessageRelease=.* snd.tradacomsendername=.* snd.tradacomMessageTypeTxt= snd.vdaLieferantenNummer=.* snd.interchangeReceiverIdCode=.* snd.edifactInterchangeSenderIdentificationCode=.* snd.odetteMessageVersionFreeText= snd.versionReleaseIndustryIdentifierCode=.* snd.edifactInterchangeSenderIdentification=.* snd.edifactMessageType=.* snd.eancomMessageType=.* snd.xpathTxt= snd.vdaMessageTypeTxt= deliverySemantics=eo snd.eancomMessageReleaseTxt= snd.plainmessagetype=.* snd.xml.split=false snd.edifactMessageRelease=.* snd.vdaMessageTypeUsingFreeText=false snd.tradacomrecname=.* edisep.addParameterParams=TableData: edisep.addParameterParams {} snd.encoding=iso885915 snd.vdaKundenNummer=.* snd.tradacomsendercode=.* snd.edifactCONTRLMessageRelease=3 snd.edifactInterchangeRecipientIdentificationCodeQualifier=.* snd.transactionSetIdentifierCode=.* Service=ASJAVA_DX5 Channel=B2BSE00002_O2C_ORDERS_PO_ECC_READ_EDISeparator EngineType=CA Party= TransProt=XI TransProtVers=1.0.0 FromPartySchema= FromPartyAgency= Direction=I MsgProt=EANCOM MsgProtVers=1.0.0 EngineName= AdapterType=EDISeparator AdapterSWCV=06c536e6fafe11e0bb1cea8f0a4290b1 ToPartyAgency= AdapterNamespace=http://sap.com/xi/XI/EDISeparator found. New message ID is f18894a8-f53b-11e3-a748-00001e96c7e2
16.06.2014 11:52:35.586	Error	MP: exception caught with cause javax.resource.ResourceException: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule
16.06.2014 11:52:35.586	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 during processing local class: localejbs/GenericConverterModule
16.06.2014 11:52:35.590	Error	Exception caught by adapter framework: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule
16.06.2014 11:52:35.591	Error	Transmitting the message to endpoint <local> using connection AS2_http://sap.com/xi/XI/AS2 failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule

[saurabhkumbhare]

Hello Experts,

Any pointers for my problem ?

Many thanks in advance!!

Saurabh

[Dimitri]

Hi Saurabh,

Can you share your configuration? And especially the EDIseparator and Integration Cockpit setup.

Thanks.

Dimitri

[saurabhkumbhare]

Hello Ruchir,

Thanks a lot for your expert guidance.

I have now imported the EANCOM content and below is the Control Key Scenario Association.

However I still get the same error as mentioned before.

Can you please help

Thanks

Saurabh

[saurabhkumbhare]

Thank you .

For the EANCOM, I imported the first 2 files out of the below list.

But the problem is I am not able to add anything under the "Control Key Name" field since the value list is empty.

Hope anyone of you can help me.

Thanks

Saurabh

[ruchir_sinha]

HI Saurabh,

There is one more B2B file which is not present in the list which you have shown. You have to import that file in order to add EANCOM. B2B_EAN_TABLES.b2b. It is part of the same zipped file.

EANCOM is available from SP2 onwards.

Best Regards,

Ruchir

[saurabhkumbhare]

Hi Dimitri,

For spending time on this, really thanks!!

Below is the Control Key Scenario Association :

[saurabhkumbhare]

Hi Dimitri,

The outbound scenario ( ECC to AS2 ) works fine.

Do you still think that there is a problem with the B2B installation.

Thanks

Saurabh

[Dimitri]

Hi Saurabh,

The installation is fine I guess, but check step 5.2.

You are missing some configuration to recognize the incoming message.

Kind regards,

Dimitri

[saurabhkumbhare]

Hi Dimitri,

Thanks for your expert advices. Really appreciate your help.

I get a new error now :

10.06.2014 14:41:44.176	Error	MP: exception caught with cause javax.resource.ResourceException: The message type can not be determined
10.06.2014 14:41:44.176	Error	Message could not be forwarded to the JCA adapter. Reason: The message type can not be determined
10.06.2014 14:41:44.179	Error	Exception caught by adapter framework: The message type can not be determined
10.06.2014 14:41:44.180	Error	Transmitting the message to endpoint <local> using connection AS2_http://sap.com/xi/XI/AS2 failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: The message type can not be determined

Additional info, (just incase), I have not put any values in the "Identifier" tab in the sender EDISeparator adapter.

Thanks

Saurabh

[Dimitri]

Hi Saurabh,

This error means that the system does not recognize the message entering the system.

Have a look at    and more specifically step 5.2

Kind regards,

Dimitri

[Dimitri]

Hi Saurabh,

You need a sender EDIseparator communication channel configured for your incoming message type.

Kind regards,

Dimitri

[saurabhkumbhare]

Hi Dimitri,

I have configured the following scenario :

Interface 1:

Sender AS2 -> Receiver EDISeparator

Interface 2:

Sender EDISeperator -> Receiver IDOC

For the Receiver EDISeperator; I have the following paramters in the adaptor :

Message Protocol : Electronic document interfchange

General tab : Nothing checked

997 acknowledgment / CONTRL : Not required

Module tab:

localejbs/ModuleProcessorExitBean      exit

exit            JNDIName     deployedAdapters/com.sap.aii.adapter.ediseparator.ra/shareable/com.sap.aii.adapter.ediseparator.ra

For the Sender EDISeperator; I have the following paramters in the adaptor :

Message protocol : EANCOM

Message Type : .*

Message version number : All versions

Message release number : All message releases

Interchange sender identification : .*

Interchange sender identification code qualifier :All codes

Interchange receiver identification : .*

Interchange receiver identification code qualifier :All codes

Module tab:

localejbs/CallSapAdapter Local Enterprise Bean entry

localejbs/EdifactConverterModule Local Enterprise Bean 1

EDI Message:

UNA:+.? 'UNB+UNOC:2+333333333:14+111111111:14+140312:1157+

1205972'UNH+120597200001+

ORDERS:D:96A:UN:EAN008+548198'

Sender party is assigned maintained as 333333333 | 014 | 14/EAN International

Can you please help..Many thanks in advance

Thanks

Saurabh

[Dimitri]

Message Protocol should not be EANCOM. You are exchanging EDI messages.

[ruchir_sinha]

Hi Dimitri,

I think he should be using EANCOM in the scenario association because his input file is of type EANCOM (He has EAN008 in UNH segment).

Former Member: . Please import the EANCOM B2B file if you have not done this earlier and define an appropriate Scenario Association for the EANCOM SAP Control key. You have configured the EDI Separator Sender channel for EANCOM and that is correct.

Best Regards,

Ruchir