Search Results fa_asset_keywords_s

Overview

FA_CREATE_GROUP_ASSET_PKG is a PL/SQL package body in the APPS schema that supports the creation of "group assets" within Oracle Assets (Fixed Assets). A group asset in Oracle EBS is a parent asset that consolidates the costs, depreciation, and financial activity of one or more member assets for reporting and accounting purposes, rather than tracking each component independently. The package provides the server-side logic required to instantiate a group asset record and to associate it with the correct asset keywords, asset category, and depreciation books.

The package carries an API classification of OTHER in the ETRM registry and is documented in both Oracle EBS 12.1.1 and 12.2.2. It is not a public, general-purpose API in the sense of the FA_ADDITION_PUB or FA_ADJUSTMENT_PUB family; instead, it is an internal component invoked during the mass additions and group asset setup lifecycle. Its dependency list confirms that it coordinates with the mass additions infrastructure (FA_MASS_ADDITIONS, FA_MASSADD_DISTRIBUTIONS, FA_MASSADD_PREPARE_PKG) as well as the core reference and transaction entities of the Assets module.

Key Procedures and Functions

The ETRM metadata documents a single callable program unit in this package:

• CREATE_GROUP_ASSET — The primary procedure responsible for constructing a group asset. It creates the parent asset definition and establishes the linkage between the group asset and its attributes, including asset keywords, category, and book information. Because the metadata does not publish a parameter list, the procedure's signature should be confirmed against the deployed source in the target environment before direct invocation.

The package body additionally depends on numerous helper programs within the APPS schema, including FA_ADDITION_PUB, FA_ADJUSTMENT_PUB, FA_API_TYPES, FA_DEBUG_PKG, and FA_MASSADD_PREPARE_PKG. These dependencies indicate that CREATE_GROUP_ASSET reuses standard API type structures and debug tracing conventions rather than implementing ad hoc logic. The presence of FND_API and FND_FLEX_APIS in the dependency list suggests that the package follows the standard EBS API error-handling pattern (returning a success flag and message via API type records) and performs key flexfield validation during group asset creation.

Tables Accessed

The package reads and writes the following documented tables:

• FA_ADDITIONS — the master asset table; the group asset row is written here. FA_ASSET_KEYWORDS and FA_ASSET_KEYWORDS_S store the asset keyword flexfield values that identify the group asset, which is the relevance of the user's search term "fa_asset_keywords_s." The _S suffix indicates this is a sequence/identifier table related to keyword assignment, so CREATE_GROUP_ASSET must resolve or generate the keyword structure for the new group asset.
• FA_BOOKS, FA_CATEGORY_BOOKS, FA_CATEGORIES — supply book and category configuration, including the default depreciation rules and accounts that govern the new group asset.
• FA_DEPRN_PERIODS — used to determine the open depreciation period into which the group asset is placed.
• FA_DISTRIBUTION_HISTORY and FA_MASSADD_DISTRIBUTIONS / FA_MASS_ADD_DIST_TBL — capture cost distribution and mass addition distribution data for the group asset and its members.
• FA_MASS_ADDITIONS — the staging table through which assets enter Oracle Assets; group assets are frequently created as part of the mass additions process.
• FA_LOOKUPS — resolves lookup codes used for statuses and type classifications.
• FND_FLEX_VALUE_SETS and FND_FLEX_VALUE_NORM_HIERARCHY — validate key flexfield segments and normal hierarchy values associated with asset keywords.
• DUAL — used for PL/SQL scalar evaluation.

Usage Notes

FA_CREATE_GROUP_ASSET_PKG is not typically invoked directly by end users. It is called programmatically by the mass additions processing flow and by other Oracle Assets packages; the metadata confirms that the package is referenced by two other database objects. In a custom extension scenario, a developer might call CREATE_GROUP_ASSET from a custom concurrent program or PL/SQL script when automating the setup of group assets, but must first confirm the parameter signature against the target release.

Because the package manipulates FA_ADDITIONS, FA_BOOKS, and distribution history, any invocation should be wrapped in a transaction that respects the standard FND_API commit/rollback conventions. Testing should occur in a non-production environment, and the resulting group asset should be validated through the Asset Workbench. Note that no inverse dependency is listed — the package is not referenced by any database object outside the APPS schema — which reinforces its role as an internal implementation component rather than a published integration point.