1. Data Management Guide
  2. DB.XML User Interface

DB.XML User Interface

This chapter explains how to use the DB.XML user interface to export and import.

Exporting DB.XML

This section describes how to export DB.XML using the web-based user interface.

  1. Log into Oracle Transportation Management.
  2. Locate the DB XML Export user interface. By default this will be Business Process Automation > Data Import/Export > DB.XML Export.
  3. Choose an Export Object Type. Fields specific to the selected type will now be displayed.
    1. DB Object: This option is deprecated as it is not fully functional in Cloud environments and should not be used.
    2. DB Object Set: This option is deprecated as it is not fully functional in Cloud environments and should not be used.
    3. Query: The following fields are available:
      1. SQL Query: For example “select * from activity”.
      2. Root Name: the element name to be used for the parent XML element.
    4. Migration Entity: The following fields are available:
      1. Migration Entity Name: For example “Location.”
      2. Object IDs: For example “GUEST.MY_LOC_1, GUEST.MY_LOC_2”.
  4. Optionally, select to export Foot print columns or Large Objects as elements.
  5. Click Run. Oracle Transportation Management displays the results page.

For example, the following shows an export with a SQL Query on the LOCATION table for LOCATION_GID = 'NYC'.

<dbxml:xml2sql xmlns:dbxml="https://xmlns.oracle.com/apps/otm/DBXML" Version="20A">
   <dbxml:TRANSACTION_SET>
      <LOCATION LOCATION_GID="NYC" LOCATION_XID="NYC" LOCATION_NAME="NEW YORK" CITY="NEW YORK" PROVINCE="NY" PROVINCE_CODE="NY" COUNTRY_CODE3_GID="USA" TIME_ZONE_GID="America/New_York" LAT="40.75167" LON="-73.99417" IS_TEMPORARY="N" IS_MAKE_APPT_BEFORE_PLAN="N" DOMAIN_NAME="PUBLIC" IS_SHIPPER_KNOWN="Y" IS_ADDRESS_VALID="Y" IS_LTL_SPLITABLE="Y" BB_IS_NEW_STORE="N" EXCLUDE_FROM_ROUTE_EXECUTION="N" IS_TEMPLATE="N" APPT_OBJECT_TYPE="S" PRIMARY_ADDRESS_LINE_SEQ="1" IS_ACTIVE="Y" ADDRESS_UPDATE_DATE="2013-08-13 14:14:31.0">
         <LOCATION_ADDRESS LOCATION_GID="NYC" LINE_SEQUENCE="1" DOMAIN_NAME="PUBLIC"/>
         <LOCATION_ADDRESS LOCATION_GID="NYC" LINE_SEQUENCE="2" DOMAIN_NAME="PUBLIC"/>
         <LOCATION_CORPORATION LOCATION_GID="NYC" CORPORATION_GID="NYC" DOMAIN_NAME="PUBLIC"/>
         <LOCATION_REFNUM LOCATION_GID="NYC" LOCATION_REFNUM_QUAL_GID="IA" LOCATION_REFNUM_VALUE="NYC" DOMAIN_NAME="PUBLIC"/>
         <LOCATION_ROLE_PROFILE LOCATION_GID="NYC" LOCATION_ROLE_GID="AIRPORT" DOMAIN_NAME="PUBLIC" X_DOCK_IS_INBOUND_BIAS="N" CREATE_XDOCK_HANDLING_SHIPMENT="Y" CREATE_POOL_HANDLING_SHIPMENT="Y" IS_ALLOW_MIXED_FREIGHT="N"/>
         <LOCATION_ACTIVITY_TIME_DEF LOCATION_GID="NYC" LOCATION_ROLE_GID="AIRPORT" ACTIVITY_TIME_DEF_GID="388715" DOMAIN_NAME="PUBLIC">
            <ACTIVITY_TIME_DEF ACTIVITY_TIME_DEF_GID="388715" ACTIVITY_TIME_DEF_XID="388715" FIXED_STOP_TIME="0" FIXED_STOP_TIME_UOM_CODE="NULL" FIXED_STOP_TIME_BASE="0" VARIABLE_STOP_TIME="0" VARIABLE_STOP_TIME_UOM_CODE="NULL" VARIABLE_STOP_TIME_BASE="0" DOMAIN_NAME="PUBLIC"/>
         </LOCATION_ACTIVITY_TIME_DEF>
      </LOCATION>
   </dbxml:TRANSACTION_SET>
</dbxml:xml2sql>
Note: Refer to the Oracle Transportation Management Data Dictionary for more information about what the objects can contain.
Note: Oracle Transportation Management does not display elements that are empty in the database.

Saving DB.XML Output to a File on Your PC

View the source for the frame containing the displayed XML using your browser and save as a file with the “.db.xml” file extension. The steps to view the source vary from browser to browser.

Note: Especially if your data contains non-ASCII characters, just save your file as-is and use an editor that supports UTF-8 when editing the file later on.

Importing DB.XML

This section describes how to import a DB.XML file using the web-based user interface.

  1. Log into Oracle Transportation Management.
  2. Locate the DB XML Import user interface. By default this will be Business Process Automation > Data Import/Export > DB.XML Import.
  3. Select the appropriate Schema. This defaults to GLOGOWNER.
  4. Click Browse to specify the required Input XML File containing the transaction set to be uploaded.
  5. The default Transaction Code is I (insert). You can change the Transaction Code from I to either II, IU, D or RC.
  6. If the Transaction Code is RC, you may need to specify Managed Tables. This will be required when no pre-configured child table properties are setup for the parent table in the input XML file. If no managed tables are found, the RC transaction code is treated like an IU i.e. no child records will be removed.
  7. Click Run.

Oracle Transportation Management displays summary statistics with a Success Count and an Error Count. The count is the number of transactions that were successful or in error.