Search Results vea_layer_licenses_sv




Overview
Explore in AI Chat

Overview

The package APPS.VEA_LAYER_LICENSES_SV is a server-side PL/SQL licensing utility that belongs to the Oracle E-Business Suite supply chain execution layer — specifically the Value Chain Execution / Transportation (VEA) module family associated with Oracle Transportation Management and the EBS logistics integration stack. Its header indicates it is compiled with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the owner, which is typical for API-facing service packages in the APPS schema.

The package was originally authored in 1999 (created by N. Parikh, header revision 115.7 dated 2003) and is classified in the ETRM metadata with an API classification of OTHER, indicating it is not a standard public Open Interface or PL/SQL API but rather an internal service/validation package. Its business purpose is to determine whether a given logistics or transportation layer has been licensed for a particular layer provider, and to maintain the license records that back that determination. In essence, it acts as the license gatekeeper for trading-partner or carrier layer functionality.

Key Procedures and Functions

  • isLicensed — A Boolean function that accepts a layer provider code and a transportation planning layer identifier and returns whether that combination is licensed. It is the primary query entry point used by other packages or forms to validate licensing before allowing layer-related processing.
  • delete_rows — A procedure that removes license records matching a supplied layer provider code and transportation planning layer identifier. It supports license maintenance and housekeeping operations.
  • process — The main transactional procedure, following the standard EBS PL/SQL API convention (API version, init message list, commit flag, validation level, and standard return status/message count/message data out parameters). It accepts layer provider code, customer name, description, and transportation planning layer identifier, and performs the insert or update of a license record with full validation and error-message reporting.

Tables Accessed

Per the documented metadata, the package references three tables via APPS synonyms:

  • VEA_LAYER_LICENSES — The primary license table. It stores the licensed layer provider code, customer name, description, and transportation planning layer identifier, and is the direct target of the process and delete_rows operations and the source data for isLicensed.
  • VEA_LAYERS — The layer definition table, consulted to validate and resolve the layer being licensed.
  • VEA_TP_LAYERS — The transportation planning layer table, used to confirm the layer identifier passed to the procedures is valid and current.

Usage Notes

VEA_LAYER_LICENSES_SV is an internal package and is referenced by five other packages within the APPS schema, which confirms it is called programmatically rather than through a dedicated concurrent program or form. Typical invocation scenarios include:

  • Other VEA / transportation packages calling isLicensed to gate layer-dependent logic at runtime.
  • License administration flows invoking process to register or update a license, and delete_rows to remove one.
  • Custom extension code in EBS 12.1.1 or 12.2.2 that needs to determine layer licensing status before enabling functionality.

Because it uses AUTHID CURRENT_USER, callers must have appropriate grants on the underlying tables. The 2003-era header and the absence of a formal published API classification suggest it should be treated as an internal implementation dependency; direct customization against it should be avoided in favor of supported public APIs where available.