Results for “n_attribute”

6 results




Overview
Explore in AI Chat

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

Overview

APPS.EAM_ASSET_ATTR_IMPORT_PVT is a private PL/SQL package body within Oracle Enterprise Asset Management (eAM). Its purpose is to import values for extensible asset attributes — the descriptive flexfield-style attributes defined for asset groups — into the eAM attribute value store. The header comment identifies the import routine, import_asset_attr_values, as a private API whose function is to move extensible asset attribute values into the MTL_EAM_ASET_ATTR_VALUES table. This places the package at the centre of the eAM asset attribute interface process, where attribute data staged in the interface tables is validated and materialised into the production attribute tables.

The package is part of the standard Oracle EBS technical stack and, per the ETRM metadata, is classified as a PVT (private) API owned by APPS and available in both 12.1.1 and 12.2.2. The $Header line (EAMVAAIB.pls 120.3, dated 2010/09/15) indicates it is a long-standing component of the eAM module and that the source file name corresponds to the eAM asset attribute import functionality. The metadata records a single documented procedure, confirming that the public surface of this private package is deliberately narrow: callers are expected to use the single import entry point rather than lower-level routines.

Key Procedures and Functions

The ETRM metadata documents one procedure on this package:

  • IMPORT_ASSET_ATTR_VALUES — the sole documented entry point. According to the embedded source comments, it is declared as a private API with an API version parameter, message-list initialisation, commit control, validation level, an interface header identifier, an import mode, and a purge option as inputs, and return status, message count, and message data as outputs. The comments further note that it optionally returns a generated SQL statement. Its documented role is to import extensible asset attribute values into MTL_EAM_ASET_ATTR_VALUES. Parameter lists are not reproduced here because the metadata only describes them at a summary level; the procedure relies on the standard FND_API conventions for its API version, initialisation, commit, and validation parameters.

The package body also declares package-level global variables used for internal bookkeeping — for example a package name constant (used for error message construction) and a debug logging flag — and local variables within the procedure to hold generated statements and concatenated segment strings. These are implementation details rather than callable APIs.

Tables Accessed

The ETRM metadata lists the following tables referenced through APPS synonyms, together with the role each plays in the import:

  • MTL_EAM_ATTR_VAL_INTERFACE — the interface table that holds staged attribute values pending import; the procedure reads from here.
  • MTL_EAM_ASSET_ATTR_VALUES — the destination table for extensible asset attribute values; the procedure writes imported rows here.
  • MTL_EAM_ASSET_ATTR_GROUPS — supplies the attribute group definitions that govern which attributes apply to an asset.
  • MTL_EAM_ASSET_NUM_INTERFACE — the asset number interface table, used to correlate staged asset identifiers with attribute values.
  • CSI_ITEM_INSTANCES — the installed-base asset instance table, used to validate that the target asset exists.
  • FND_DESCR_FLEX_COLUMN_USAGES — provides descriptive flexfield column metadata needed to resolve attribute definitions.
  • DBMS_SQL — the Oracle-supplied dynamic SQL package, used to build and execute generated statements at runtime, consistent with the procedure's documented x_sql_stmt output parameter and the local l_sql_stmt1 variable.

Usage Notes

Because the package is classified as PVT and its own comments label the procedure private, it is not intended as a public integration API. It is typically invoked indirectly — from eAM concurrent programs or forms that process the asset attribute interface, or from the public package layer that the metadata reports as referencing it (one other package depends on it). The presence of an interface header identifier parameter indicates the import is driven by a header record in the interface tables, with the purge option controlling whether staged rows are deleted after a successful import. Custom code should generally call the supported public entry point rather than this private package, since Oracle does not guarantee the private signature across patch levels.