NO Ruleset for GENRAL\96A available (EDI to XML Conversion Error)

[Former Member]

Hi,

My Scenario is Inbound EDI Scenario. I am facing problem during conversion of EANCOM to XML .

Control Key Scenario Association part with the EDI Content Manager is filled in properly. we are not doing anything in the above Control Key
Scenario Association part .Because whatever we are saving we are not able to see in the screen. Please find the below screen shot attached.

XSD produced from B2B Integration Cockpit was being used in the ESR.

No Acknowledgement Enabled.

We have checked with the possible option in the below blog.But not working

http://scn.sap.com/thread/3309007

Regards,

Prem

[Dimitri · Accepted solution]

Hi Prem,

Strange to see the GENERAL part in the error. I expected to see the ORDERS.

Did you configure EANCOM everywhere because it seems that you get EANCOM messages?.

On what SP level your B2B add-on is on?

Kind regards,

Dimitri

[Former Member · Accepted solution]

Hi Dimitri,

Did you configure EANCOM everywhere because it seems that you get EANCOM messages?.

- Yes

On what SP level your B2B add-on is on?

- SP3

Regards,

Prem

[Dimitri · Accepted solution]

Hi Prem,

Take a look at

: any ideas? Can you verify the outcome of incident 0000689142 @ SAP?

Kind regards,

Dimitri

[ruchir_sinha · Accepted solution]

Hi Dimitri,

This incident is in customer action for more than a month. This incident is being processed by primary support colleagues and I just checked the payload attached is that of an ORDERS and INSDES. It is not possible that a EDI Sender channel picks up ORDERS message and gives a GENRAL error. If you see the screenshot closely then in the configuration string it clearly says that it is GENRAL configuration.

As far as fallback to EDIFACT is concerned then last week there was a patch released by one of my colleagues. I don't remember the note number but you can upgrade to the latest patch of your current SP pack.

[Former Member · Accepted solution]

Hi Dmitri/Ruchir,

By mistake I have uploaded  Message Type ORDERS screen shot with Message Protocol EANCOM,but my actual one is Message Type GENRAL with Message Protocol EANCOM only

The combination of message type and version specified in the UNH segment is not maintained in the tables?

the above mentined EDIFACT\EANCOM seems different issue.

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 Occured :
Error in conversion of GENRAL/96A-Edifact-Document at character 1489 to XML:
java.lang.UnsupportedOperationException: No ruleset for GENRAL/96A
available.

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 Occured : Error in
conversion of GENRAL/96A-Edifact-Document at character 1489 to XML:
java.lang.UnsupportedOperationException: No ruleset for GENRAL/96A
available.

Exception caught by adapter framework:
com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message
cannot be dispatched: Message cannot be dispatched: Error Occured : Error in
conversion of GENRAL/96A-Edifact-Document at character 1489 to XML:
java.lang.UnsupportedOperationException: No ruleset for GENRAL/96A
available.

Transmitting the message to endpoint <local>
using connection File_http://sap.com/xi/XI/System 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 Occured : Error in
conversion of GENRAL/96A-Edifact-Document at character 1489 to XML:
java.lang.UnsupportedOperationException: No ruleset for GENRAL/96A
available.

if you need mu input payload please let me know

Please suggest me.

Thanks

Prem

[ruchir_sinha · Accepted solution]

Hi,

Recently we have made changes in EANCOM handling of cases where in the the subversions of EANCOM (like EAN003, EAN004) are not officially provided by SAP standard shipped content then the conversion to XML will be done via EDIFACT. So fallback mechanism is added to support these subversions.

Please apply Note 2064459.

Best Regards,

Ruchir