You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

26A Enhanced Exception Logging – Loss of Error Visibility and Troubleshooting Autonomy

in Transportation Management 2 comments

Summary:

26A Enhanced Exception Logging – Loss of Error Visibility and Troubleshooting Autonomy

Content (please ensure you mask any confidential information):

We need clarification regarding the 26A note "Enhanced Exception Logging" (https://docs.oracle.com/en/cloud/saas/readiness/logistics/26a/otm26a/26A-otm-wn-f42778.htm#Steps-to-enable-and-configure).

The note mentions that for certain technical failures, users will need to contact Oracle Support to retrieve internal logs. We have a concern regarding the troubleshooting workflow:

Is it confirmed that there will be no way, not even via DBA.ADMIN or enhanced logging to access these error details directly within the application?

If so, this seems like a step backward in terms of maintenance and self-service. Currently, we are autonomous in analyzing most issues, which significantly reduces resolution times. Relying on a Service Request (SR) just to get error details for a failed dock appointment will inevitably:

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!