Search Results get_asset_key_name

Overview

FA_CUA_ASSET_WB_APIS_PKG is a public PL/SQL package in the APPS schema of Oracle E-Business Suite, belonging to the Oracle Assets (Fixed Assets) application. Its name and structure identify it as a set of APIs supporting a "CUA" (customer/user adoption) Asset Workbench-style function, with particular emphasis on asset hierarchy maintenance and descriptive lookups. The package exposes a mixed set of utility functions and procedures: session-scoped put/get accessors that hold context values during a form or process invocation, boolean predicates that test feature enablement or data existence, hierarchy node creation and parent navigation routines, and a family of name-resolution (lookup) functions that translate internal numeric identifiers into user-meaningful names.

The package is classified under ETRM as an API of classification OTHER, indicating it is a supporting internal API rather than a fully documented public interface with a published parameter contract. In Oracle EBS 12.1.1 and 12.2.2 the package is present under APPS and is referenced by a further six packages, confirming its role as a shared utility layer rather than a standalone entry point.

Key Procedures and Functions

The documented routines fall into several functional groups:

• Context accessors: PUT_BOOK_TYPE_CODE, PUT_TRANSACTION_ID and PUT_ASSET_ID store book type, transaction identifier and asset identifier into package globals, while GET_BOOK_TYPE_CODE, GET_TRANSACTION_ID and GET_ASSET_ID retrieve them. The globals G_LIFE_ASSET_ID, G_TRANSACTION_ID and G_BOOK_TYPE_CODE are annotated as being used to display information in the Life Derivation Form.
• Predicates: IS_CRLFA_ENABLED returns a boolean indicating whether the relevant feature option is active; CHECK_BATCH_DETAILS_EXISTS returns a boolean indicating whether detail rows exist for a supplied batch. GET_TRANSACTION_ID and other getters carry a PRAGMA RESTRICT_REFERENCES (WNPS, WNDS) declaration, marking them as side-effect-free for use in SQL and PL/SQL purity contexts.
• Hierarchy maintenance: CREATE_NODE and GET_ASSET_PARENT operate on the asset hierarchy structures. GET_ASSET_PARENT returns parent hierarchy and asset-purpose information for a given asset. GET_CATEGORY_NAME, GET_LEASE_NUMBER, GET_ASSET_KEY_NAME and GET_LOCATION_NAME resolve identifiers into display names; the user search term get_asset_key_name targets the last of the asset-key resolution family, which converts an internal asset identifier into the asset's key name for display.
• Additional getters: GET_ACCOUNT_CODE_NAME, GET_EMPLOYEE_NAME, GET_EMPLOYEE_NUMBER, GET_LEASE_ID, GET_CATEGORY_ID and DERIVE_OVERRIDE_FLAG complete the 29 documented routines, providing further identifier-to-name translation and override-flag derivation.

Tables Accessed

The package reads and writes through APPS synonyms across the core Oracle Assets data model. Asset master and financial data reside in FA_ADDITIONS, FA_BOOKS, FA_BOOK_CONTROLS, FA_ADJUSTMENTS and FA_DISTRIBUTION_HISTORY. Hierarchy-related logic uses FA_ASSET_HIERARCHY, FA_ASSET_HIERARCHY_PURPOSE, FA_HIERARCHY_DISTRIBUTIONS, FA_HIERARCHY_RULE_DETAILS and FA_HIERARCHY_RULE_SET. Calendar and convention information comes from FA_CALENDAR_PERIODS, FA_CALENDAR_TYPES and FA_CONVENTIONS, while FA_CATEGORY_BOOK_DEFAULTS supplies category-to-book defaulting and FA_LEASES supplies lease information used by the lease-oriented getters. These tables support the lookup functions, the hierarchy node construction, and the batch-existence check.

Usage Notes

Given its accessor design and its reference by six other packages, FA_CUA_ASSET_WB_APIS_PKG is typically invoked indirectly — from Oracle Assets forms (notably the Life Derivation Form, per the source annotations), from concurrent programs, or from other PL/SQL packages that require asset key names, category names, lease numbers, location names or hierarchy context. Custom code should call the GET_* functions for read-only resolution and the PUT_* accessors only when establishing session context before invoking dependent routines; direct calls to hierarchy maintenance routines such as CREATE_NODE should be treated with caution because the package is not documented as a supported open interface. In both 12.1.1 and 12.2.2 the package remains available under APPS with the routines listed above.