Collecting Configuration Data Requested by Oracle Support (OTM) (Doc ID 1443933.1)

Last updated on SEPTEMBER 27, 2013

Applies to:

Oracle Transportation Management - Version 6.0 and later
Information in this document applies to any platform.
***Checked for relevance on 27-Sep-2013***

Goal

Why is this Data Being Requested?

As part of troubleshooting a problem, it is often most effective to configure an internal test case to review and research the problem. Having this configured locally within Oracle allows for the ability to step through the code to further diagnose problems.

Therefore the collection of this data allows for this internal test case setup to expedite the research of a problem. This note is designed to make this collection more effective, which results in less preparation of Screenshots which can become cumbersome to collect for larger test cases.

XML vs CSV Collection

Some OTM Data Types allow for the ability to export the entire data structure by preparing an XML file that includes all data related to the object. For these data objects, you only need to prepare the single XML to provide to Oracle Support.

For other Data Types that do not have the ability to generate an XML, the object can be exported via CSV (i.e. direct exports from the database tables). A Data Type might be stored in various database tables and therefore multiple CSV exports can be necessary for a single Data Type.

In the section below, these two methods are explained. Each Data Type that might be requested by Oracle Support is listed under the section for which it applies.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms