Product Information
Improved Error Handling in the eDocument Cockpit
As part of the ongoing improvements, the Document Compliance Framework team has developed a feature that allows you to display different sources of errors directly from the result list in the eDocument Cockpit (EDOC_COCKPIT).
What is the main improvement?
With this new feature, all the relevant information related to an error is now displayed at a glance, in a separate but integrated view: the system opens a details pane on the right side with the application log, the interface log, and the last file. You can easily navigate to the next error by double-clicking on the corresponding entry in the Logs/File column.
How do you enable this feature?
This feature is available with Document Compliance Framework 27. For more details, see SAP Note 3005076 – Document Compliance Framework (27).
In the Customizing activity Maintain General Parameters for eDocument (EDOGENCUST), in Customizing for Cross-Application Components, under General Application Functions → eDocument → General Settings, you maintain the following settings:
| Customizing Parameter Name | Customizing Parameter Value |
|
NEW_SCREEN (Allow Screen with Details Pane in eDocument Cockpit) |
X |
Give us your feedback
To ensure that we’re covering what you need, please leave your feedback at the bottom of this blog post!
#SAPGoGlobal #SAPLocalization
Hi Elisabeth,
this looks really useful.
On the same note, can you tell me if it is possible for the application log to retain multiple messages per eDocument? The National Informatics Centre in India can (and does) return multiple messages for a single API call.
Kind regards,
John Moulding
Hi John,
yes, the application log can retain multiple messages for one eDocument.
Best regards,
Elisabeth
Hi Elisabeth,
thank you for confirming that, but (so far as I can see) it isn't possible to add multiple messages to the application log from any bespoke objects that are called by the eDocument Interface Connector: and in a manual system, that's a lot of code, with many possibilities for errors. Raising an exception with a table of messages appears to retain a single message in the log.
Yes, I could add my bespoke classes as friends to class cl_edocument, but that is far from ideal. Maybe I'm missing something, but it seems that it would be really helpful if instance method "add_message_application_log" had a public attribute, rather than protected.
KR,
John
Hi John,
many thanks for your reply.
In this case, I would suggest that you submit an improvement request under Influence Opportunity Homepage - Customer Influence (sap.com).
Best regards,
Elisabeth
Hi Elisabeth,
I followed all the steps for Mexico payment complements config and AIF setup but when I submit an eDocument, it fails with the message text 'Error triggering message, check interface log for details'. When I do that via the 'Goto' button, I get the error 'No interface Log found for selected eDocument'.
Can you give me a hint why the log is not written or not accessible? Any help is much appreciated.
Best Regards,
Achim Tuschewski
Hi Achim,
Thank you for reaching out.
We would need the system access to analyse your query.
Request you to raise a Ticket in component CA-GTF-CSC-EDO-MX.
Thanks & Regards,
Debrath.