Results for “frm_flex_api”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.FRM_FLEX_API is a PL/SQL package that belongs to the Oracle E-Business Suite (EBS) foundation layer, specifically associated with the Forms runtime and flexfield infrastructure. The $Header$ signature (frmfapis.pls 120.0, dated 2006/12/14) and the internal date history show this package originated in the early Oracle Applications releases and has been maintained only minimally since. Its stated description is deliberately generic: parameters are listed as "None," and the package body is documented as having been progressively stubbed out. In EBS 12.1.1 and 12.2.2, this object persists essentially as a compatibility shell rather than an active code path.

The package was originally created to expose a small set of Application Programming Interface calls relating to flexfield handling within the Forms runtime domain. By the RM8 (Release Management 8) timeframe, the 14-NOV-02 revision explicitly "stubbed out procedures not used by RM8," indicating that the functional logic was retired and only the specification skeleton was retained. No business-critical behavior is expected from this package in current releases.

Key Procedures and Functions

The ETRM metadata for this object documents zero procedures or functions. This is consistent with the source excerpt, which shows the package specification ending with no declared program units before the closing END FRM_FLEX_API; statement. The header comment block itself confirms that procedures were removed ("Stub out procedures not used by RM8"), leaving an empty specification.

Because no callable interfaces are documented, no parameter lists exist and none should be assumed. Any historical procedure names associated with FRM_FLEX_API in earlier releases are not part of the documented 12.2.2 interface and must not be invoked in custom development, as their bodies no longer exist.

Tables Accessed

The ETRM metadata records no tables referenced via APPS synonyms for this package. This aligns with the empty specification: with no executable program units, there is no SQL and therefore no dependency on application tables, views, or sequences.

In practice, flexfield-related data in EBS resides in tables such as FND_FLEX_VALUES, FND_FLEX_VALUE_SETS, and FND_ID_FLEX_STRUCTURES, but the documented metadata confirms that FRM_FLEX_API does not read or write any of these. Reinforcing this, the metadata shows the package is referenced by zero other packages, meaning it sits as an isolated node in the dependency graph.

Usage Notes

FRM_FLEX_API should be treated as a non-functional compatibility object in both EBS 12.1.1 and 12.2.2. It is not intended to be invoked directly by forms, concurrent programs, or custom code. Because the specification is empty, any attempt to call a member of this package will fail at compile time.

Its only practical relevance is historical and diagnostic. The continued presence of the stub preserves the object identifier and avoids breaking legacy references that may still exist in very old compiled forms or libraries, even though none are documented. Development standards for current releases direct implementers toward the supported flexfield APIs in the FND_* family (for example the FND_FLEX_* packages) rather than this retired wrapper.

Finally, regarding the search phrase "when fabrfci app will be live," it is unrelated to this package. FRM_FLEX_API contains no scheduling, deployment, or application-readiness logic, and no metadata here indicates any go-live milestone. Any question about when a specific application becomes live must be answered through Oracle's release documentation rather than through this object.