Search Results fte_vehicle_features_s

Overview

APPS.FTE_VEHICLE_PKG is a stored PL/SQL package that encapsulates the core business logic for defining, validating, and maintaining vehicle types and their associated feature sets within Oracle E-Business Suite. Its role is situated in the logistics and transportation domain, where vehicle types represent the classifications of physical assets (trucks, trailers, containers, and similar conveyances) used to move goods. The package body delegates much of its interface discipline to the Oracle Applications foundation layer, depending on FND_API for the standard API return-status conventions, FND_GLOBAL for session context (user, responsibility, and organization), and FND_MESSAGE for user-facing error and warning messages. It also leverages WSH_DEBUG_SV for diagnostic logging and WSH_GLOBAL_PARAMETERS for Shipping Execution configuration, which situates the package inside the Oracle Shipping/Transportation Management execution stack rather than in a purely standalone inventory context. The dependency listing confirms that the package body sits on top of the FTE_VEHICLE_TYPES and FTE_VEHICLE_FEATURES base and _S (translation/seed) tables, tying it directly to the objects returned by the user search term fte_vehicle_features_s.

Key Procedures and Functions

The documented public interface exposes five program units, balancing maintenance operations with validation and lookup utilities:

• CREATE_UPDATE_VEHICLE_TYPE — the primary maintenance entry point. It inserts a new vehicle type record or updates an existing one, handling the corresponding _S translation/seed rows and enforcing the package's data-integrity rules before committing through the standard API savepoint/commit pattern.
• VALIDATE_VEHICLE_TYPE — a validation routine that verifies the completeness and correctness of a vehicle type definition (for example, required descriptive columns and uniqueness) prior to persistence, returning FND_API-compliant status and message output.
• UPGRADE_ITEMS — a data-conversion utility that reconciles or migrates item and vehicle-type relationships, typically invoked during patch application or installation upgrades to align existing MTL_SYSTEM_ITEMS records with the vehicle type model.
• GET_VEHICLE_TYPE_ID — a lookup function that resolves the surrogate primary key of a vehicle type from its identifying attributes, allowing callers to use the package's API rather than querying the base tables directly.
• GET_VEHICLE_ORG_ID — a lookup function that returns the inventory organization context associated with vehicle processing, used to derive the correct operating unit or inventory organization for downstream transactions.

Tables Accessed

The package reads and writes the FTE_VEHICLE_TYPES and FTE_VEHICLE_FEATURES tables together with their _S counterparts (FTE_VEHICLE_TYPES_S and FTE_VEHICLE_FEATURES_S), which store the translatable and seeded definitions of vehicle types and features. It validates item data against MTL_SYSTEM_ITEMS and the key-flexfield view MTL_SYSTEM_ITEMS_B_KFV, consults MTL_PARAMETERS to confirm organization-level inventory settings, checks MTL_ITEM_STATUS for item status control, and joins MTL_UNITS_OF_MEASURE_TL for unit-of-measure descriptions. HR_ORGANIZATION_UNITS supplies organization validation, WSH_GLOBAL_PARAMETERS provides Shipping Execution defaults, and the PL/SQL table type PLITBLM plus STRINGARRAY support bulk parameter passing in the API signatures. Internal help from INV_ITEM_GRP and the package's own FTE_VEHICLE_PKG specification round out the dependencies.

Usage Notes

FTE_VEHICLE_PKG is not referenced by any other database object, but it is itself referenced by five other packages, marking it as a building block consumed by higher-level ETRM or Shipping forms, concurrent programs, and integration code. Typical invocation is through Oracle Forms event handlers or concurrent program wrappers that call CREATE_UPDATE_VEHICLE_TYPE and rely on CV_API semantics for x_return_status handling. Upgrade routines should call UPGRADE_ITEMS only in patch or install mode, while GET_VEHICLE_TYPE_ID and GET_VEHICLE_ORG_ID are safe for read-only use in reports, custom validation, and troubleshooting queries involving the FTE_VEHICLE_FEATURES_S table. The package is listed as VALID in ETRM 12.1.1 and 12.2.2 schemas.