Question Re: Message cannot be dispatched: Error during processing local bean: localejbs/EDIFACTConverterModule in Technology Q&A

Message cannot be dispatched: Error during processing local bean: localejbs/EDIFACTConverterModule

anupam_ghosh2 — Wed, 15 Nov 2017 15:47:34 GMT

Hi Experts,

There are two scenarios

1. ICO1 --> file to ediseparator

2. ICO2--> Ediseparator to file

ICO1 is reading a edifact file with a file sender channel then trying to forward the same to ediseparator channel. There is no adapter module in any of the channels in ICo1.

In ICO2 EDIseparator channel has module

1 localejbs/EDIFACTConverterModule Local Enterprise Bean 0

2 localejbs/CallSapAdapter Local Enterprise Bean entry

Both the scenarios have no mapping and pass through scenarios. I am getting an error in log of first scenario as shown below

initial log in channel

Searching sender channel for Edifact message part message with Message type INVOIC, Message version number D, Message release number 07A, Interchange sender identification O0013000577MB000000INVOIC, Interchange sender identification code qualifier , Interchange recipient identification 01010000749001, Interchange recipient identification code qualifier

then error log

-------------

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 bean: localejbs/EDIFACTConverterModule.

in b2b cockpit maintained two entries under same control key name. One for ICO 1 and another for ICO2 as shown in attached image.

capture.png

Please let me know if I am missing something here or adapter module name should be different.

Regards

Anupam

Re: Message cannot be dispatched: Error during processing local bean: localejbs/EDIFACTConverterModule

manoj_khavatkopp — Wed, 15 Nov 2017 16:14:26 GMT

Hi Anupam ,

Can you please share the error log screenshot please, below are some inputs.

You mention the control key association only if you using any customize EDI version or else don't touch the key association leave it as default. i.t SAP with all entries *
If you have customized EDI you need to have a custom control key name other then SAP and for that control key you link up your scenario by giving some your unique interface details.

So in short as per your screenshot, you are not using any customized so change the control key association to whatever it was default i.e SAP with all entries * . This should work then.

Br,

Manoj

Re: Message cannot be dispatched: Error during processing local bean: localejbs/EDIFACTConverterModule

anupam_ghosh2 — Thu, 16 Nov 2017 09:38:32 GMT

Hi Manoj,

Here are the screenshots of the scenario

ICO1

-----------

Sender channel

ico1sender.png

receiver channel

ico1receiver.png

ICO2

---------

The sender channel

ico2sender1.png

The sender channel adapter module

ico2sendermoduletab.png

Receiver channel

------------------

ico2receiver.png

error

-----------

error.png

I tried to change the entries in control key to default but error remains same.

Regards

Anupam

Re: Message cannot be dispatched: Error during processing local bean: localejbs/EDIFACTConverterModule

manoj_khavatkopp — Thu, 16 Nov 2017 09:45:45 GMT

Your config looks fine , can you please show the control key association after you made chnages.

Re: Message cannot be dispatched: Error during processing local bean: localejbs/EDIFACTConverterModule

anupam_ghosh2 — Thu, 16 Nov 2017 12:56:21 GMT

Hi Manoj,

Responded to your queries in above response.

Regards

Anupam

Re: Message cannot be dispatched: Error during processing local bean: localejbs/EDIFACTConverterModule

manoj_khavatkopp — Thu, 16 Nov 2017 13:00:13 GMT

Please share the control key association after you made chnages ?

Re: Message cannot be dispatched: Error during processing local bean: localejbs/EDIFACTConverterModule

anupam_ghosh2 — Thu, 16 Nov 2017 15:35:28 GMT

b2bc.png

Thank you for your kind response.

Attached is the screenshot, of b2b cockpit.

in b2b cockpit i was unable to convert edifact to xml.

Regards

Anupam

Re: Message cannot be dispatched: Error during processing local bean: localejbs/EDIFACTConverterModule

manoj_khavatkopp — Thu, 16 Nov 2017 18:34:16 GMT

The control Key association and you config look fine no issues.

Few checks :

In the provided screenshot I can see you are using INVOIC D07A version.I hope you don't have any extra filed or any extra segment to be customized for your requirement. This version is part of standard SAP B2B provided content. So can you please cross check if this version is present in your system under SAP control key. Reference find below.

If you have the version can you check the EDI file which you are trying to convert is a valid file? And when you try to convert this directly in cockpit what error do u see at the bottom? If possible you can attach the EDI file here so that I can try it out in my system.

If you don't see this version in your system then it means the standard content file was not uploaded after B2B Addon installation.

Br,

Manoj

Re: Message cannot be dispatched: Error during processing local bean: localejbs/EDIFACTConverterModule

anupam_ghosh2 — Fri, 17 Nov 2017 06:04:09 GMT

Hi Manoj,

This version is not showing up in the cockpit. In fact no version shows up in b2b cockpit.

Can you please let me know what can be the issue? Here is the screen shot . Do I need to populate the tables or it is provided by SAP?? The names of file are also shown here.

Please let me know if blank table content is expected or not.

tables.png

Thank you so much for your kind help and cooperation.

edifactb2b.png

Re: Message cannot be dispatched: Error during processing local bean: localejbs/EDIFACTConverterModule

manoj_khavatkopp — Fri, 17 Nov 2017 07:28:47 GMT

Hi Anupam,

As I said before your basis team has not imported the B2B content after the addon installation. So would request you to get in touch with them and ask them to import the B2B content into the cockpit, this file is present in the ZIP file which they downloaded from the marketplace. Once you import the standard B2B content the table gets populated automatically.

Br,

Manoj