Search Results debug_output

Overview

MST_AUDIT_REP_EXCP is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM (E-Business Suite Technical Reference Manual) as an "OTHER" API type. It supports the Oracle Transportation Management / Logistics execution functionality associated with the MST (Motor Ship Transport / delivery) schema family. Its principal business function is to generate and evaluate a transportation audit report by detecting exceptions and threshold violations across delivery, shipment, and vehicle-related data. The package compares actual transactional values — weights, volumes, dimensions, distances, coordinates, and in-transit times — against configured thresholds and preferences, and surfaces records that violate business rules for pickup and delivery activities.

This package body is reported as VALID in the 12.1.1 ETRM metadata and is referenced by no other database objects, indicating it is a top-level reporting package rather than a shared library dependency.

Key Procedures and Functions

The ETRM documentation records nineteen procedures and functions. Their documented purposes are summarized below without asserting parameter signatures.

• RUNAUDITREPORT — Principal entry point that drives execution of the full audit report and orchestrates the individual exception checks.
• INITIALIZEGLOBALVARIABLES — Prepares package-level state and global variables prior to report processing.
• GETEXCEPTIONTHRESHOLD — Retrieves configured exception thresholds, typically sourced from MST preferences and parameters.
• MISSINGLATLONGCOORDEXCPTN — Flags deliveries or locations lacking latitude/longitude coordinates, supported by MST_GEOCODING.
• MISSINGDISTANCEDATAEXCPTN — Identifies records with absent distance information.
• DL_WITH_ZERO_VALUES — Detects delivery records carrying zero values where non-zero data is expected.
• DIMENSIONVIOLFORPIECEEXCPTN — Reports dimensional violations on a per-piece basis.
• WGTVOLVIOLFORPIECEEXCPTN — Reports weight/volume violations on a per-piece basis.
• WGTVOLVIOLFORDLEXCPTN — Reports weight/volume violations at the delivery level.
• WGTVOLVIOLFORFIRMDELIVEXCPTN — Reports weight/volume violations for firm deliveries.
• INSUFFICIENTINTRANSITTIMEEXPTN — Detects trips where the calculated in-transit time falls below the required minimum.
• PASTDUEORDERSEXPTN — Flags orders that have exceeded their expected delivery windows.
• FACCALVIOLFORPICKUPEXPTN — Reports facility calendar violations occurring at pickup.
• FACCALVIOLFORDELIVERYEXPTN — Reports facility calendar violations occurring at delivery.
• GET_UOM_CONVERSION_RATES and CONV_TO_UOM — Support unit-of-measure conversion so weights and volumes are compared in consistent units.
• TESTCONV — Diagnostic utility for validating conversion behaviour.
• GET_MINIMUM_TRANSIT_TIME — Derives the minimum allowable transit time, drawing on calendars and shift data.
• DEBUG_OUTPUT — Emits diagnostic messages for troubleshooting.

Tables Accessed

The package accesses its data through APPS synonyms. Delivery and shipment data are read from MST_DELIVERIES, MST_DELIVERY_ASSIGNMENTS, and MST_DELIVERY_DETAILS. Exception output is persisted to MST_EXCEPTIONS and MST_EXCEPTION_DETAILS (and their _S sequence-backed counterparts), with configuration drawn from MST_EXCEP_PREFERENCES, MST_PARAMETERS, and MST_PLANS. Calendar and shift references — BOM_CALENDAR_DATES, BOM_SHIFT_DATES, and BOM_SHIFT_TIMES — support facility calendar and minimum transit-time checks. Mileage, vehicle, and location data come from FTE_LOCATION_MILEAGES, FTE_LOCATION_PARAMETERS, FTE_VEHICLE_TYPES, WSH_LOCATIONS, and WSH_REGION_LOCATIONS. Item, UOM, and carrier data are sourced from MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_B, MTL_UNITS_OF_MEASURE, MTL_UOM_CONVERSIONS, MTL_INTERORG_SHIP_METHODS, WSH_CARRIERS, WSH_CARRIER_SERVICES, and WSH_CARRIER_VEHICLE_TYPES. FND_PROFILE supplies profile option values, and DUAL is used for scalar evaluations.

Usage Notes

MST_AUDIT_REP_EXCP is typically invoked from a concurrent program registered against RUNAUDITREPORT, or from custom code that requires transportation audit exception reporting. Because its procedures call internal helpers such as MST_GEOCODING and MST_SNAPSHOT_TASK_UTIL, it should be executed within a fully configured transportation environment. No other database object references it, so changes are contained but callers must be identified through concurrent program and form registrations. The presence of DEBUG_OUTPUT and TESTCONV indicates the package is intended to be run with diagnostic output available during report troubleshooting.