Results for “get_account_code_name”

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

Overview

FA_CUA_ASSET_WB_APIS_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite (12.1.1 / 12.2.2). It belongs to the Oracle Assets (FA) module and supports the "CUA" (Customer User Asset / consolidated asset workbench) asset Web/Workbench API layer. The package acts as a helper and data-access layer that sits alongside the core asset API package FA_CUA_ASSET_APIS, exposing utility routines used to build, validate, and render asset-related records in the Assets workbench and associated Web-based asset interfaces. Its principal role is to resolve surrogate identifiers (asset, transaction, book, lease, category), retrieve descriptive attributes (names, numbers, key flexfield names), and manage lightweight session/context values used while processing asset transactions. It also participates in asset hierarchy processing through calls to FA_CUA_HIERARCHY_PKG and the hierarchy tables, enabling parent/child node creation and inheritance of distribution data.

Key Procedures and Functions

The package exposes 29 documented procedures and functions. They fall into several functional groups:

• Context setters/getters: PUT_BOOK_TYPE_CODE, PUT_TRANSACTION_ID, PUT_ASSET_ID and their counterparts GET_BOOK_TYPE_CODE, GET_TRANSACTION_ID, GET_ASSET_ID maintain and retrieve the current asset/book/transaction context during a processing session.
• Validation and lookup helpers: CHECK_BATCH_DETAILS_EXISTS, DERIVE_OVERRIDE_FLAG, and IS_CRLFA_ENABLED determine whether a mass-update batch detail exists, whether an override flag should be derived, and whether the CRLFA (Chinese/Capitalized Lease Financing Asset) feature is enabled via profile options.
• Descriptive resolution functions: GET_CATEGORY_NAME, GET_CATEGORY_ID, GET_LEASE_NUMBER, GET_LEASE_ID, GET_ASSET_KEY_NAME, GET_LOCATION_NAME, GET_ACCOUNT_CODE_NAME, GET_EMPLOYEE_NAME, and GET_EMPLOYEE_NUMBER translate internal identifiers into user-facing descriptions, typically for display in the workbench UI.
• Hierarchy handling: CREATE_NODE and GET_ASSET_PARENT build and traverse the asset hierarchy, resolving parent assets for hierarchical distribution processing.

These routines are deliberately thin wrappers, delegating complex logic to FA_CUA_ASSET_APIS and FA_CUA_HIERARCHY_PKG while centralizing common lookups.

Tables Accessed

The package references its data through APPS synonyms, reading and, where required, writing the following Oracle Assets tables:

• Core asset tables: FA_ADDITIONS (asset master rows), FA_ADJUSTMENTS (asset cost adjustments), FA_BOOKS (asset/book balances), and FA_BOOK_CONTROLS (depreciation run controls).
• Categories and defaults: FA_CATEGORIES_B_KFV, FA_CATEGORY_BOOK_DEFAULTS, FA_CONVENTIONS, FA_METHODS, and FA_CALENDAR_TYPES / FA_CALENDAR_PERIODS supply category names and depreciation setup information.
• Hierarchy tables: FA_ASSET_HIERARCHY, FA_ASSET_HIERARCHY_PURPOSE, FA_HIERARCHY_DISTRIBUTIONS, FA_HIERARCHY_RULE_SET, and FA_HIERARCHY_RULE_DETAILS support parent/child node creation and distribution inheritance.
• Supplementary tables: FA_DISTRIBUTION_HISTORY, FA_EMPLOYEES (for employee name/number), FA_LEASES (for lease number/id), FA_ASSET_KEYWORDS_KFV, FA_LOCATIONS_KFV, GL_CODE_COMBINATIONS_KFV, FA_LOOKUPS, and FA_LIFE_DERIVATION_INFO provide descriptive and code-combination data.
• EBS infrastructure: FND_GLOBAL and FND_PROFILE supply session context and profile-option values; DUAL is used for trivial queries.

Usage Notes

Because the package is a helper library rather than a standalone user-facing component, it is invoked internally by higher-level APIs and workbench forms. It is most commonly called from within the Oracle Assets "CUA" asset workbench flows, from mass-update/asset hierarchy processing programs, and from custom extensions that need to resolve asset, lease, category, or hierarchy descriptors using standardized logic rather than direct SQL. The package is referenced by six other database objects and does not itself reference any external application beyond its documented dependencies. Customizations should call the public functions instead of querying the underlying FA tables directly, preserving consistency with standard Assets behavior and ensuring the same validation used by the workbench is applied.