Search Results get_fk




Overview
Explore in AI Chat

Overview

APPS.FII_FLEX_MAPPING is a utility package within the Oracle E-Business Suite Financial Intelligence (FII) product family. Its principal business function is to resolve the individual segments of a Key Flexfield combination into their constituent values, either in aggregate or one segment at a time. Within EBS, a code combination identifier (CCID) uniquely identifies a stored combination in GL_CODE_COMBINATIONS, but reporting, extract, and data-warehouse processes frequently require the segments themselves — company, cost center, account, product, and so on — rather than the opaque CCID. This package supplies that translation, removing the need for each consuming program to write its own flexfield denormalization logic.

The package belongs to the analytical reporting layer of EBS, where Accounting Flexfield values must be expanded for extraction into the Enterprise Data Warehouse or similar structures. Version 12.1.1 and 12.2.2 retain this package unchanged in its documented behavior; the header information shows a stable release dating to the 11i/12.0 development stream, indicating it has been carried forward without functional revision.

Key Procedures and Functions

  • GET_VALUE — Returns segment value information for a combination, resolving it through the package's in-memory cache rather than issuing a fresh query for every call. It is declared with a PRAGMA RESTRICT_REFERENCES to WNDS (Write No Database State), meaning it performs no DML and is safe to invoke from SQL statements and read-consistent contexts. A set of books identifier and a structure identifier accompany the CCID so that the correct key flexfield definition is applied when interpreting the combination.
  • GET_FK — Retrieves a particular segment of a combination at a time, based on a supplied segment number. This is the function most commonly searched for by implementers resolving a single flexfield segment without materializing the entire combination. Like GET_VALUE, it is restricted to WNDS and holds no dependency on cached or package-global state, so it can be called repeatedly and in any order. It is the primary entry point for callers that know which segment ordinal they need.
  • INIT_CACHE — An initialization procedure that must be executed before the cached retrieval functions are used. It accepts a fact short name that identifies the business-area context whose combinations are to be pre-loaded into memory. Invoking it is a prerequisite to benefit from the cache-based path; failing to call it means dependent code cannot rely on pre-loaded values.
  • FREE_MEM_ALL — Releases the in-memory cache when it is no longer required. Because the cache consumes a session or package-level memory footprint, this procedure should be called at the natural end of a batch or extract to avoid retaining stale or unnecessary data. It carries no parameters as documented.

Tables Accessed

The package is documented as referencing four objects through APPS synonyms:

  • GL_CODE_COMBINATIONS — The definitive store of Accounting Flexfield combinations; the source of CCIDs and the row from which segment values are ultimately derived.
  • EDW_LOCAL_SET_OF_BOOKS — Provides set of books context, ensuring combinations are interpreted against the correct ledger definition.
  • EDW_LOCAL_EQUI_SET_OF_BOOKS — Supports resolution of equivalent or mapped sets of books, relevant in multi-organization and reporting-currency scenarios.
  • PLITBLM — PL/SQL memory table utilized by the caching mechanism to hold pre-loaded combination data between calls.

Usage Notes

FII_FLEX_MAPPING is an internal, non-form-bound utility rather than a user-facing API. It is most often invoked from concurrent programs, PL/SQL batch extracts, and custom packages that need to flatten flexfield combinations for reporting or warehouse loading. Because the package is referenced by fifteen other packages, it functions as a shared low-level service within the FII dependency chain, and changes to its behavior can ripple widely.

When using the cached path, callers must observe the documented lifecycle: execute INIT_CACHE at the start of processing and FREE_MEM_ALL at the end. For single-segment lookups, GET_FK can be used directly and is the appropriate choice when only one segment column is required, avoiding the overhead of resolving the full combination. Both retrieval functions are WNDS-restricted, so they may appear in SELECT statements and views, subject to the usual EBS constraints on calling packaged functions from SQL.