Search Results c_valueset_valtype_independent




Overview
Explore in AI Chat

Overview

APPS.JTF_JFLEX_PUB is a public PL/SQL package that exposes utility APIs for interrogating Oracle E-Business Suite key flexfield and descriptive flexfield definitions at runtime. Its name derives from the CRM Foundation (JTF) technology stack, and the package provides a programmatic bridge between application code and the flexfield metadata managed by the Oracle Application Object Library (FND). Business functions that need to render, validate, or interpret flexfield structures — particularly in Oracle CRM modules such as TeleSales, Service, or iStore — can call these APIs rather than querying FND metadata tables directly.

The package is owned by APPS and classified as PUB, indicating it is a supported public interface intended for consumption by other Oracle and customer-developed code. The source header (jtfflexs.pls 120.2, last shipped 2005/10/25) indicates the package has remained stable across the 12.1.1 and 12.2.2 releases, with no structural changes introduced by the 12.2 online patching architecture.

Key Procedures and Functions

The package declares two documented procedures and two public constants.

  • GET_FLEXFIELD — Accepts an application short name and a flexfield name and returns the runtime definition of that flexfield. The output set includes the flexfield name, the owning application name, the number of segments, and parallel arrays describing each segment: segment name, database column name, default value, prompt, maximum size, minimum and maximum values, mandatory flag, default type, validation type, LOV identifier, format type, and display size. This single call therefore returns the complete structural and behavioural description of a key or descriptive flexfield in a form suitable for dynamic rendering.
  • GET_VALUESET — Accepts a value set identifier and returns the list of values associated with that set. The output consists of two parallel arrays: the value itself and its user-facing meaning. This is the procedure most commonly associated with the search term "get_valueset," as it provides a lightweight mechanism for populating list-of-values items without issuing direct queries against FND_LOOKUP_VALUES or the underlying value set tables.
  • Constants C_VALUESET_VALTYPE_INDEPENDENT ('I') and C_VALUESET_VALTYPE_NONE ('N') — These constants are returned by GET_FLEXFIELD in the validation type array and allow callers to branch on whether a segment uses an independent value set or no validation at all.

Tables Accessed

The documented table reference for this package is PLITBLM, an APPS synonym. In the Oracle EBS data dictionary, PLITBLM is the standard name for a PL/SQL index-by table type used to pass collections between PL/SQL and Oracle Forms. Its appearance in the metadata reflects that the package's array parameters (jtf_varchar2_table_300, jtf_number_table, and related types) are structurally compatible with this collection type. The actual flexfield definition data is resolved internally through the FND flexfield metadata views; the ETRM excerpt does not enumerate those base tables, and they should not be assumed from the package signature alone.

Usage Notes

JTF_JFLEX_PUB is typically invoked from Oracle Forms-based CRM applications and from custom PL/SQL code that requires dynamic flexfield handling without hard-coding segment structures. A common pattern is to call GET_FLEXFIELD during form initialisation to build the segment prompt and validation metadata, then to call GET_VALUESET when the user opens a list of values for a validated segment. Because both procedures return collections sized to match the underlying definition, callers must size their receiving arrays adequately or use the number of segments returned by GET_FLEXFIELD as a loop bound.

The package is not referenced by any other documented package, so it is a leaf-level utility rather than part of a larger internal dependency chain. When calling it from custom code, developers should honour the NOCOPY OUT parameter convention, which means the output collections are passed by reference for performance and should be treated as owned by the caller after return. As with all APPS-owned public packages, direct modification is unsupported; extensions should wrap rather than alter the shipped specification.