S4f08.23.en-Us 192

You might also like

Download as pdf or txt
Download as pdf or txt
You are on page 1of 1

Unit 6: SAP Document and Reporting Compliance - Test Strategy, Trouble Shooting, Further Information

For each country electronic document processing covers, there are also country-specific
community groups (see the Jam link). In these, customers can give early feedback on
upcoming requirements, learn about implementation details, and also often answer questions
themselves. JAM page for Italy
Analyzing logs

1. Document and Reporting Compliance cockpit


The first level of logs can be found in the cockpit. You can use it to identify errors and for
the first level of analysis.

2. Interface logs in edoc cockpit


This is the second level of logs you should analyze.

3. Tracing log on SAP Integration Suite


In case of the PaaS solutions, you should activate the tracing on cloud integration. This is
the easiest way to reproduce errors and then analyze these in the logs. For security
reasons, not all messages are fully sent back to the requesting system, so checking in the
middleware is always a good option for root cause analysis. To analyze, you can simply go
to the operations view in the SAP integration Suite, go to the manage integration content
tab where you have listed all the deployed artifacts, and here, you would then simply
search for your respective iflow, and activate the log trace. Please note that this trace is
only active for ten minutes. If the message is not sufficient in the backend, the log tracing
can give you more details to narrow down the error.

Debugging
Debugging is a good way to identify the place in the coding where an error occurs, and get
more context. For example, the respective error message can then be used to find an existing
solution in the knowledge base, or to create an incident.
Finding help in the knowledge base
● Knowledge Base
● Once you have found an entry point to search for, or you narrowed down the error, you can
go to our knowledge base and simply search for a specific error.
● Alternatively, search with the respective component, which you can get from the
compliance tasks overview already mentioned in earlier sections of the training. Supported
Compliance Tasks by Country or Region | SAP Help Portal.

How to get help


● In case the problem is known, you need to implement the solution (note)
● In case the problem is unknown:
- Create an incident if it is a bug
- Create an influence idea if it is a missing feature

LESSON SUMMARY
You should now be able to:
● Troubleshooting for statutory reporting

184 © Copyright. All rights reserved.

You might also like