Troubleshooting in TM

This section describes the tools you can use to assist you in troubleshooting issues about shipment and carrier route processing using TM, as well as optimization:

• Extension Alerts: To access the extension alerts. select Enterprise > Administration > Extension Alerts. The extension alerts are used when Infor ION is not in available to log errors reported using the Confirm BOD sent from one application to another.

  For example, TM receives a syncShipment BOD that does not contain one of the required data fields such as weight, payment type, ship to party. A row is displayed in the extension alerts table that indicates the XML is not valid.

• TM Application Server log: This log provides details of all errors that have occurred within the TM module. The logging level can be adjusted to provide more details as necessary. See the below section on changing the log level for more information. See Viewing information about the processing of a specific shipment or route and Failing to route and rate example.
• TM ESB log: This log includes all of the messages sent to TM (syncShipment) and those TM has published out (processShipment and syncCarrierRoute BODs). Reviewing these messages allows you to view the data that was transmitted within the messaging files. See Viewing TM-generated BODS.
• Optimization Log: to access the optimization log select Enterprise > Rating and Routing > Optimization Runs > View Log. The View Log page displays this diagnostic information:
  • Pre Processing: Shipments are evaluated against the optimization profile parameters for inclusion in the optimization run. The shipments are then pre-priced to calculate the cost to move the shipment if it is not optimized with other shipments as a result of optimization.
  • Pre Data Extraction: Shipment and rate data is sent to the optimization engine.
  • Core Optimization: Optimization engine imports both shipments and rate contract data and performs the optimization process as specified in the optimization parameters.
  • Post Data Extraction: Carrier routes are created.
  • Post Processing: Resulting carrier routes are routed and rated; any that are more expensive in post optimization, due to routing guide configurations, are broken apart and final results are tallied.