Search Results jtf_jflex_pub




Overview
Explore in AI Chat

Overview

The APPS.JTF_JFLEX_PUB package body provides the public runtime entry points for resolving Oracle E-Business Suite descriptive flexfield structures and their associated value sets. Within the CRM Foundation (JTF) schema, the JFLEX layer abstracts the mechanics of the Flexfield Definition tables (FND_DFLEX) and value set definitions (FND_VSET) so that callers can retrieve flexfield metadata and validated value set contents without issuing direct queries against the underlying Application Object Library tables. This wrapper design centralizes flexfield access logic, insulates dependent products from AOL table structure changes, and enforces a consistent API contract across Oracle EBS 12.1.1 and 12.2.2.

The package is classified as a public API (PUB) in the APPS schema and is documented as VALID in the ETRM inventory. It is a leaf dependency: the metadata records no other database object that references JTF_JFLEX_PUB. The specification and body resolve to the same name, with JTF_JFLEX_PUB listed among its own internal dependencies, confirming that the body implements and calls the declared public interface.

Key Procedures and Functions

  • GET_FLEXFIELD — Returns descriptive flexfield definition metadata. It derives its results from FND_DFLEX, the AOL table that stores flexfield, context, and segment definitions. This routine supplies callers with the structural information required to render or interpret a flexfield, such as identifying the flexfield by its application and descriptive name.
  • GET_VALUESET — Returns value set information derived from FND_VSET, the AOL table holding value set definitions. This routine exposes the value set metadata associated with a flexfield or segment so that callers can validate, display, or resolve the permitted values.

The two procedures constitute the complete documented public surface of the package. Both are intended for programmatic invocation from PL/SQL rather than end-user interaction. The interface also declares the collection types JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_100, and JTF_VARCHAR2_TABLE_300, indicating that flexfield and value set results may be returned as PL/SQL associative or nested tables sized to 100- and 300-character elements alongside numeric identifiers.

Tables Accessed

  • PLITBLM — Referenced through an APPS synonym. This is the PL/SQL internal table (index-by table) library object used by the runtime for collection handling. Its presence in the dependency list reflects the package's use of PL/SQL table types when assembling or returning flexfield and value set results.
  • FND_DFLEX — Read to obtain flexfield definition rows for GET_FLEXFIELD.
  • FND_VSET — Read to obtain value set definition rows for GET_VALUESET.

The dependency list also includes STANDARD and PUBLIC from SYS, which are standard PL/SQL package dependencies rather than application data objects. No INSERT, UPDATE, or DELETE activity against application tables is indicated by the metadata; the package behaves as a read-oriented access layer over AOL flexfield metadata.

Usage Notes

JTF_JFLEX_PUB is a public API (PUB classification) and is the supported entry point for applications requiring flexfield and value set information through the JTF flexfield wrapper rather than through direct AOL queries. Typical invocations occur from PL/SQL-based forms logic, Oracle Forms personalizations, concurrent program PL/SQL, and custom extensions that must resolve a descriptive flexfield structure or enumerate its value set contents. Because the package depends on FND_DFLEX and FND_VSET, calls reflect the flexfield and value set definitions cached in AOL and are subject to the same compilation, caching, and security behavior as other AOL flexfield APIs. The absence of reverse dependencies indicates the package is a consumer, not a provider, within the dependency graph; removing or recompiling it does not invalidate dependent database objects, though callers of its public procedures would fail at runtime if the package became invalid. In both 12.1.1 and 12.2.2 the object resolves in the APPS schema with the same public interface, so existing customizations referencing it remain portable across the two releases.