Hi delong
This is a Good Question and I think there aren't any further Great Documentation available other than what you may have already gone through: https://help.sap.com/viewer/0f69f8fb28ac4bf48d2b57b9637e81fa/2008.500/en-US/a4f6ccd072f147f299b1d856... This could primarily be because of the fact that this app itseld was luanched in 2008 release. I see some commitment in writing from Product Development on the documentation improvement in the coming releases.
The app primarily helps to trace incoming calls to your S/4HANA system and find issue like SSL-Handshake errors, HTTP protocol errors and Authentication errors.
To start a trace you have to define a trace criteria. Therefore click “Define Trace Criteria”, the most basic way to define the Criterion would be to:
1. Enter something into “Description”-Field (optional)
2. Valid Until: we can leave it as well at its initial value: 10 Minutes
3. Request Method: set to “All” or to the particular calls you want to trace
4. After that click the “Save”-Button.
The trace is activated for the defined criteria, but it is learned there could be a small delay until the trace starts, because all the components needed to be notified.
If the challenge persist, I urge you to raise an incident using the component: BC-SRV-APS-COM.
Hope this helps!
Thank you!
Amith Nair
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.