Search Results fa_lookup_types

Overview

FA_LOOKUP_TYPES_PKG is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that supports the Oracle Assets (Fixed Assets) module's lookup type setup. Lookup types in Oracle Assets provide the extensible value sets that drive several fixed asset configuration areas, including asset key flexfield segments, asset categories, depreciation conventions, prorate conventions, and other reference data that must be translated and seeded correctly across a multi-language EBS instance. The package encapsulates the database operations necessary to maintain rows in the FA_LOOKUP_TYPES base and translation tables, thereby insulating callers from the underlying multi-table structure required by Oracle's translated (TL) table design pattern.

Because Oracle Assets lookup values are seed data that Oracle delivers and customers may extend, the package performs a dual role: it provides the runtime row-level maintenance operations used by the application forms layer, and it supplies the loader entry points consumed by the FND_LOAD_UTIL seed data framework during patching, upgrades, and language installation. The package body's dependency on AD_ZD_SEED and FND_LOAD_UTIL confirms that it participates in the standard Oracle Applications online patching and seed data load architecture. Its status as a valid, non-referenced object indicates it is a utility package invoked directly rather than called from other database packages.

Key Procedures and Functions

• INSERT_ROW — Creates a new lookup type record, inserting the base row into the FA_LOOKUP_TYPES_B table and the corresponding translatable rows into the FA_LOOKUP_TYPES_TL table for the applicable languages.
• LOCK_ROW — Acquires a row-level lock on an existing lookup type record, used to enforce concurrency control before an update or delete is applied.
• UPDATE_ROW — Modifies the attributes of an existing lookup type, synchronizing changes across the base table and the translation table so that all installed languages remain consistent.
• DELETE_ROW — Removes a lookup type and its associated translation rows.
• ADD_LANGUAGE — Extends existing lookup type records into a newly installed language, populating the FA_LOOKUP_TYPES_TL table with the appropriate rows for that language.
• TRANSLATE_ROW — Updates the translated description or meaning of a lookup type for a specific language in the TL table.
• LOAD_ROW — Loads a single lookup type record as part of a seed data load, typically invoked by the FND_LOAD_UTIL framework.
• LOAD_SEED_ROW — Loads seed data rows for lookup types during patch application or installation, interacting with the AD_ZD_SEED infrastructure.

The documented procedure list totals ten entries, with the remaining procedures serving supporting or internal roles consistent with the above naming conventions.

Tables Accessed

• FA_LOOKUP_TYPES — The view or synonym over the base and translation tables, used for read access to lookup type definitions.
• FA_LOOKUP_TYPES_B — The base (non-translatable) table storing lookup type codes, flags, and attributes that are language-independent.
• FA_LOOKUP_TYPES_TL — The translation table holding language-specific meaning and description columns.
• FND_LANGUAGES — The Oracle Applications language registry, referenced to identify installed and active languages when inserting, translating, or adding language rows.

Usage Notes

FA_LOOKUP_TYPES_PKG is not referenced by any other database package, so it is invoked directly rather than through an API chain. In a typical EBS 12.1.1 or 12.2.2 environment, the row-level procedures are exercised indirectly through the Oracle Assets setup forms that maintain lookup type information, while the LOAD_ROW and LOAD_SEED_ROW entry points are driven by the seed data loading framework during patching, upgrade, and language installation. The ADD_LANGUAGE and TRANSLATE_ROW procedures are particularly relevant after adopting a new language, since Oracle Assets lookup descriptions must be propagated into the TL table for all supported languages. Custom code that needs to maintain Oracle Assets lookup type data should use these procedures rather than issuing direct DML against the underlying tables, to preserve translation integrity and to remain compatible with the AD_ZD_SEED framework used in online patching.