Search Results get_jdbc_conn_lov




Overview
Explore in AI Chat

Overview

CCT_LKUP_PUB is a public PL/SQL package body owned by APPS within the Oracle E-Business Suite, delivered as part of the ETRM (Enterprise Tracing, Routing, and Monitoring or equivalent Change/Configuration Tracking) module. It provides list-of-values (LOV) services used by ETRM setup and administration flows, returning localized meaning/code pairs and identifier sets used to populate selection lists in forms and other UI or integration layers.

The package is classified as a PUB (public) API, meaning its procedures are intended for external invocation — from forms, concurrent programs, or custom extensions — rather than internal-only use. Its primary role is to centralize lookup queries so that configuration screens consistently and correctly honor language, security group, and enabled-flag rules from FND_LOOKUP_VALUES, and so that dependent ETRM entities such as middleware, route points, and trace configurations display validated enumerations.

The header comments ("$Header: cctplovb.pls") confirm it is a long-standing component carried forward across the Oracle EBS 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

  • GET_TRUE_FALSE_LOV — Returns a simple boolean lookup (mapped to the CCT_BOOLEAN lookup type) as a pair of meaning and code value arrays. It resolves the localized meaning from FND_LOOKUP_VALUES, applies the caller's language via environment language, filters on the security group returned by FND_GLOBAL.LOOKUP_SECURITY_GROUP, and returns the collected meanings/codes along with standard API return status, message count, and message data.
  • GET_JDBC_CONN_LOV — Supplies the connection LOV used when a middleware or server definition must reference a JDBC connection, allowing the caller to pick from the connections configured in the ETRM middleware tables.
  • GET_TRACE_LOV — Provides the trace selection list, matching the "get_trace_lov" search term. It populates the LOV of configured traces so that operators can select a trace configuration from the ETRM trace registry.
  • GET_TEST_TYPE_LOV — Returns the enumeration of available test types, used in diagnostic and test-configuration screens where a test category must be chosen.
  • GET_MW_LOV — Populates the middleware LOV, exposing the middleware definitions maintained in CCT_MIDDLEWARES so that dependent setup can reference an existing middleware instance.
  • GET_ROUTE_POINT_LOV — Supplies the route-point LOV, drawing from CCT_MW_ROUTE_POINTS so that routing configuration can select a valid route point for the middleware in context.

Each procedure follows Oracle's API conventions: a standard savepoint-based entry, initialization of x_return_status to FND_API.G_RET_STS_SUCCESS, and OUT NOCOPY return parameters conveying status, message count, message data, and the resulting LOV arrays.

Tables Accessed

  • FND_LOOKUP_VALUES — Read by GET_TRUE_FALSE_LOV to resolve enabled, language-specific lookup meanings and codes; the query also applies lookup security group filtering to respect data security.
  • CCT_MIDDLEWARES — Read to populate the middleware LOV and to source JDBC connection selections.
  • CCT_MW_ROUTE_POINTS — Read to populate the route-point LOV.
  • PLITBLM — The standard Oracle API message-handling table, used by the package's shared error/return handling to store and retrieve API messages.

Usage Notes

CCT_LKUP_PUB is invoked from ETRM setup and administration forms wherever a validation list is needed, and it may be called directly from custom PL/SQL or concurrent programs that must present the same LOV values. Callers should always check x_return_status against FND_API.G_RET_STS_SUCCESS and, when x_msg_count exceeds zero, retrieve messages through the standard FND_MSG_PUB API before proceeding. The package's documented plumbing — SAVEPOINT, IEO_STRING_VARR arrays, and env language parameter — means callers must pass the session language so that returned meanings are correctly localized. Because it is a PUB API, direct modification is discouraged; extensions should call the documented procedures. Referenced by no other packages per the metadata, it functions as an entry-point utility layer rather than a dependent internal library.