Error eDocument Cockpit

[JordanoJ]

Hello experts,

I hope you are doing very well. Today I have a question regarding an Electronic Invoicing integration that I am developing. I have S4HANA CLOUD PUBLIC EDITION, Integration Suite as middleware, and EFACT as the electronic invoicing provider. What happens is that from S4 an XML is generated that will be sent to EFACT, but before sending it I need to transform the XML into the structure they expect and then send it to them in a file. This part is not the issue, I just mention it to give context.

The problem is that when I trigger the process from the eDocument Cockpit, I get these errors. However, if I check in Integration Suite, it shows as completed and I can see the response returned by the electronic provider. Has any of you experts experienced a similar situation?

Regards.

[nobleaura]

We had a very similar scenario with S/4HANA Cloud and an external e-invoicing provider. What you’re describing usually happens when the iFlow finishes successfully in Integration Suite but the response does not return in the format expected by the eDocument Cockpit. As a result the cockpit shows an error even though the middleware completed.

A few things to double-check:

Make sure the outbound service destination from S/4 to Integration Suite is correctly maintained. The communication system assigned to `SAP_COM_0521` should have the right host, authentication and user.

• In your iFlow, ensure that the response from EFACT is mapped back into the structure S/4 expects. If not, the cockpit flags it as an error even though the call was successful.
• SAP has detailed guidance on both Submitting Electronic Documents and the eDocument Cockpit. They describe exactly how the response and status updates are expected.
• After correcting any configuration, clear and retry the document in the cockpit.

This approach solved the issue for us.

Best regards,

[Chris1973]

Hello @JordanoJ 

Thank you for your question.

Have a looked at Submitting Electronic Documents, eDocument Cockpit for more details.

To summarise, the situation you described is common when you integrate eDocument cockpit with external e-invoicing provider through the integration suite. From your description the iFlow is executed successfully. The error you are experiencing indicates a destination configuration issue on the cloud side.

• First thing to check is to ensue the outbound service is assigned and points correctly to your integration suite endpoint.
• Your communication system linked to SAP_COM_0521 has the correct host, authentication method and user.
• If your iFlow process and finishes but does not map back the response to S4, the cockpit will flag it as an error. You may need to adapt iFlow to send back a proper status in the expected format.

If everything is configured, then make sure you clear and retry the document in eDocument cockpit.

I hope this provides the desired insight.

Best regards

Chris

[JordanoJ]

Hello @Chris

Thank you for your reply. For this case, my communication arrangement is SAP_COM_0873, and it does have the host, path, and authentication method properly configured. I am also attaching evidence of this. As I mentioned before, and as you also pointed out, when I send the document through the eDocument Cockpit the error appears, while in Integration Suite the response is displayed correctly. Do you think I should adapt the response to the metadata defined in that communication arrangement? I recall reading that it might also be due to a missing configuration in the CBC. Could that be possible?

Best regards,
Jordano