B2B EDI - Outbound scenario issue with EDI separator Receiver channel

[Former Member]

Hi Experts,

Am working on a B2B Outbound scenario: Orders Response IDOC to ORDRSP 96A EDIFACT file. Implementing the scenario on SAP PI 7.4.

I have configured Integrated Configuration from IDOC - ORDRSP.ORDERS05 to ORDRSP 96A using EDI Separator Receiver Channel with below parameters:

Direction: Receiver

Transport Protocol: PI

Message Protocol: Edifact

Formatting: Indent Messages: YES

Also configured another dummy Integrated Configuration with EDI Separator sender channel with below parameters:

Direction: Sender

Transport Protocol: PI

Message Protocol: Edifact

Filter:

Message Type: ORDRSP

Msg Version Number: All Versions

Release Number: 96A

Module: localejbs/EdifactConverterModule.

When i run the scenario by triggering the Orders Response IDOC from ECC, the message is failing in EDI Separator channel with below exception:

Message could not be forwarded to the JCA adapter. Reason: Channel configuration error: Value with name rcv.handleplain not available

MP: exception caught with cause java.lang.IllegalArgumentException: Channel configuration error: Value with name rcv.handleplain not available

Exception caught by adapter framework: Channel configuration error: Value with name rcv.handleplain not available

Please assist with where the issue is?

Thanks a lot for the assistance.

Regards,

Vish

[ruchir_sinha · Accepted solution]

Hi Vish,

What is your B2B release version. Looking at the error i think your AMD for EDI separator adapter is not updated. Please update the same.

Thanks & Regards,

Ruchir

[Former Member · Accepted solution]

Hi Ruchir,

We are using B2B Addon SP1 and PI on 7.4. For Inbound scenarios, the EDI Separator configuration is working fine to convert EDIFACT Orders 96A to XML. But the Outbound Scenario is causing issue.

Can you please elaborate on what you mean by AMD for EDI separator adapter not being updated.

It would be a great help if you can share any sample scenarios on EDI Outbound i.e IDOC -> EDIFACT conversion.

Thanks a lot for the assistance.

Regards,

Vish

[ruchir_sinha · Accepted solution]

Hi Vish,

What I mean by bug on AMD is that your adapter metadata is not updated for the EDI Separator adapter. This is maintained in ESR. The correct AMD can be downloaded from SAP Service Marketplace. It is present along with other components of B2B Addon. This should remove your error.

Also I request you to create an OSS ticket on SAP with component BC-XI-CON-B2B-ESP because you should not get this error even when your AMD is old and other components are modified.

Regards,

Ruchir

[Former Member · Accepted solution]

Hi Ruchir,

Thanks a lot for the quick response. I will do the steps you suggested to first download the latest AMD for EDI separator adapter and see if it solves my issue. Else will raise an OSS with SAP.

Regards,

Vish

[ruchir_sinha · Accepted solution]

Hi Vish,

I request you to create the OSS message even if your issue gets solved. Because the issue needs resolution from the code as well.

Regards,

Ruchir

[Former Member · Accepted solution]

Hi Ruchir,

I have raised the OSS as suggested. Also have requested my Basis team to redeploy the latest AMD i.e B2B Toolkit SP02. Once I receive the confirmation from Basis, I will test and update the thread.

Thanks a lot for all the assistance.

Regards,

Vish

[Former Member · Accepted solution]

Hi Ruchir,

I have deployed the B2B Toolkit SP02 in order to redeploy the AMD. After retriggering the IDOC, I get a new error message - Message Type cannot be determined in the EDI Separator receiver channel.

When I try the EDI XML to convert to EDI format in the EDI Content Manager, It works fine. So wanted to know what is the issue with the EDI separator channel. Below is the error details -

MP: exception caught with cause javax.resource.ResourceException: The message type can not be determined

Message could not be forwarded to the JCA adapter. Reason: The message type can not be determined

Transmitting the message to endpoint <local> using connection IDoc_AAE_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: The message type can not be determined.

I verified the EDI separator sender channel and all parameters are fine. Please let me know where the issue can be?

Regards

Vish

[ruchir_sinha · Accepted solution]

Hi Vish,

For the scenario which you have mentioned above that is outbound scenario you do not require EDI separator adapter (Sender or Receiver). You only need to use the EdifactConverterModule or GenericConverterModule which converts your XML to EDIFACT.

EDI separator adapter is mostly used for the inbound case where in the partner sends an EDIFACT message which is then split and routed as per requirement.

If I have not interpreted correctly then I request you to please explain scenario in detail.

Regards,

Ruchir

[Former Member · Accepted solution]

Hi Ruchir,

Thanks a lot for the assistance. Using the EdifactConverterModule has worked and able to transform the EDI XMl to EDIFACT file.

Great help for me.

Regards,

Vish