Message could not be forwarded to the JCA adapter. Reason: File can not be decoded: Input length = 1

[Former Member]

Hello Experts,

I have configured a ODETTE EDI scenario (IDoc to OFTP), which is working fine unless there are some special characters(e.g. XYZ TECHNÔLÔGIES) in any IDoc field. In the module configuration for EdifactConverterModule I am using the edifact.encoding parameter with value as "ISO-8859-1" in addition to the Encoding parameter (in General tab - File setting) of the OFTP adapter.

Below is the failure log

Information	B2B EdifactConverterModule: writing character content "XYZ TECHNÔLÔGIES"
Information	B2B EdifactConverterModule: Message  will be sent as ISO-8859-1.
Information	B2B EdifactConverterModule: closing edifact segment with ":"
Information	B2B EdifactConverterModule: finished xml document
Information	B2B EdifactConverterModule: finishing xml tag "D_5375"
Information	B2B EdifactConverterModule: starting xml tag "D_5387"
Information	B2B EdifactConverterModule: writing "QT"
Information	B2B EdifactConverterModule: writing character content "1"
Information	MP: processing local module localejbs/ModuleProcessorExitBean
Information	Message entered AF MP exit bean and will now be passed to the JCA adapter
Error	Message could not be forwarded to the JCA adapter. Reason: File can not be decoded: Input length = 1
Information	Initial configuration: OFTP Version 1.4(4) over TCPIP
Error	MP: exception caught with cause javax.resource.ResourceException: File can not be decoded: Input length = 1
Error	Exception caught by adapter framework: File can not be decoded: Input length = 1
Error	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: File can not be decoded: Input length = 1
Error	Message status set to NDLV

Can you please check the details and help me to identify the root cause in this case.

Thanks,

Jitender

[Dimitri · Accepted solution]

Try using UTF-8 for the encoding parameter

[azharshaikh]

Hi Jitender,

Pls ckh the following link if it helps:

Regards,

Azhar