Search Results update_carrier_vehicle_type




Overview
Explore in AI Chat

Overview

WSH_CARRIER_VEHICLE_TYPES_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It provides a controlled, programmatic interface for maintaining the association between carriers and the vehicle types they operate within Oracle Shipping Execution (WSH). The package is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute with the privileges of the calling session rather than the definer, an important consideration for schema-level grants and security.

Business users configure carrier vehicle types through the Shipping Transaction and carrier setup flows. The underlying records reside in the WSH_CARRIER_VEHICLE_TYPES table, which stores the carrier-to-vehicle-type mapping alongside a set of descriptive flexfield attribute columns and standard WHO audit columns. This package encapsulates the create, update, and locking operations against that table, shielding callers from direct DML and centralizing validation, audit population, and concurrency control. The header comment ($Header: WSHVTTHS.pls 115.0) indicates the file was generated from a database package specification and dates to 2003, consistent with the long-standing stability of the Shipping Execution data model.

Key Procedures and Functions

Three procedures are documented in the package specification, each designed around a shared record type, CVTRecType, which mirrors the columns of the carrier vehicle type entity (carrier ID, vehicle type ID, assigned flag, attribute category, fifteen descriptive flexfield attributes, and the standard creation and update audit columns).

  • CREATE_CARRIER_VEHICLE_TYPE — Inserts a new carrier vehicle type assignment. It accepts a CVTRecType record as input and returns the ROWID of the newly created row along with standard API feedback elements: return status, exception message, position, procedure name, SQL error text, and SQL code. Callers use the returned ROWID for subsequent update or lock operations.
  • UPDATE_CARRIER_VEHICLE_TYPE — The procedure associated with the search term "update_carrier_vehicle_type." It modifies an existing carrier vehicle type assignment identified by a supplied ROWID. Like the create procedure, it takes a CVTRecType record and returns a full set of diagnostic outputs (return status, exception message, procedure name, position, SQL error, and SQL code), enabling callers to detect and handle failures programmatically.
  • LOCK_CARRIER_VEHICLE_TYPE — Acquires a row-level lock on an existing carrier vehicle type record prior to modification. It accepts the CVTRecType record and the target ROWID and returns only a return status. This procedure implements the optimistic locking pattern used throughout Oracle EBS APIs, guarding against concurrent updates by two sessions to the same row.

Tables Accessed

The package performs DML against a single documented table, WSH_CARRIER_VEHICLE_TYPES, accessed through an APPS synonym. This table is the repository of carrier-to-vehicle-type mappings, including the ASSIGNED_FLAG that indicates whether the association is active, the ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 columns used by the descriptive flexfield mechanism, and the audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN). The record type CVTRecType maps directly to these columns, confirming that the procedures read and write the full row image. No other tables, views, or sequences are documented as being referenced by this package.

Usage Notes

This package is the supported API for manipulating carrier vehicle type data; direct inserts or updates against WSH_CARRIER_VEHICLE_TYPES are discouraged because they bypass the validation and audit logic implemented inside the procedures.

  • Oracle Forms and OAF pages — The standard Shipping Execution setup forms and OA Framework pages that maintain carrier vehicle type assignments typically delegate their persistence logic to this package, maintaining the row with the create, update, and lock procedures rather than issuing base-table DML.
  • Concurrent programs and interfaces — Batch loaders and interface programs that populate carrier vehicle type data call CREATE_CARRIER_VEHICLE_TYPE and UPDATE_CARRIER_VEHICLE_TYPE, inspecting X_RETURN_STATUS and X_EXCEPTION_MSG to populate error staging tables.
  • Custom code — Custom PL/SQL should follow the same convention: populate a CVTRecType record, call the appropriate procedure, and test the return status before committing. Because the package is AUTHID CURRENT_USER, the executing schema must possess the necessary privileges on the APPS synonym and the underlying table.
  • Concurrency — Callers should invoke LOCK_CARRIER_VEHICLE_TYPE before UPDATE_CARRIER_VEHICLE_TYPE and pass the same ROWID, ensuring the record has not been changed by another session since it was queried. The documented metadata records no other packages referencing this one, so its use is confined to direct invocation by forms, concurrent programs, and custom code.