Search Results get_asset_type_n_dpis

Overview

CSE_ASSET_CLIENT_EXT_STUB is a client extension stub package owned by APPS in the Oracle E-Business Suite. It belongs to the Enterprise Asset Management / Assets (CSE and FA) integration layer and defines the standard extensibility hook points through which customers and partners may override, enrich, or replace the default attribute values that Oracle Assets derives when creating asset records. The package name follows the standard EBS "client extension stub" convention: Oracle ships the stub with empty bodies, and implementers copy it into a custom package that performs the same signature calls. The CSE_ASSET_CLIENT_EXT_STUB documented in ETRM 12.2.2 exposes 25 procedures and functions, and 7 other packages reference it, indicating it sits on a widely consumed call path rather than being terminal utility code.

Key Procedures and Functions

The API classification is OTHER, and the procedures are attribute-oriented getters. They fall into several functional groups:

• Identity and description hooks: GET_ASSET_NAME, GET_ASSET_DESCRIPTION, GET_TAG_NUMBER, GET_MODEL_NUMBER, and GET_MANUFACTURER supply the human-readable attributes of the asset being created.
• Classification hooks: GET_ASSET_CATEGORY, GET_ASSET_TYPE_N_DPIS, GET_BOOK_TYPE, GET_SEARCH_METHOD, and GET_TXN_CLASS_FLAG determine how the asset is classified and which transaction class applies.
• Accounting hooks: GET_ASSET_KEY returns the asset key CCID, while GET_DEPRN_EXPENSE_CCID, GET_PAYABLES_CCID, and GET_INV_DEPR_ACCT resolve the depreciation expense, payables, and inventory depreciation account combinations, respectively.
• Date and status hooks: GET_DATE_PLACE_IN_SERVICE returns the in-service date, and GET_CATCHUP_FLAG governs catch-up depreciation behavior.
• Location and party hooks: GET_ASSET_LOCATION (the searched procedure) resolves asset location data, and GET_EMPLOYEE resolves the employee association.
• Process control hooks: SKIP_ASSET_CREATION and POPULATE_MASS_ADDITION_DFF control whether an asset is created at all and whether descriptive flexfield values are populated on the mass addition.

Each hook reports whether it was actually used through an x_hook_used out parameter and returns diagnostic text through x_error_msg, allowing the caller to distinguish a genuine override from the Oracle default. Parameter-level details beyond these documented occurrences should be confirmed against the live package specification.

Tables Accessed

The single documented table reference is FA_MASS_ADDITIONS, accessed through APPS synonyms. This is the staging table in which mass addition lines are loaded before posting into Oracle Assets. The extension hooks evaluate attribute values for the pending mass addition row, so that the getters can drive defaults and overrides for the eventual asset record.

Usage Notes

These hooks are invoked during the asset creation and mass addition interface flows. Typical callers are the mass additions posting program, the CSE asset integration packages, and custom code performing asset interface loads. Because the stub is shipped with no business logic, implementations customize behavior by creating a client extension package that mirrors the signatures and registers it through the standard profile options used for CSE client extensions. The x_hook_used flag should be tested by callers so that Oracle defaults are applied when no custom hook has been registered.