Search Results eam_maint_attributes_pub




Overview
Explore in AI Chat

Overview

The APPS.EAM_MAINT_ATTRIBUTES_PUB package body is a public Enterprise Asset Management (EAM) API within Oracle E-Business Suite, delivered as part of the Discrete Manufacturing/EAM product family. Its header reflects a build of version 120.4 dated April 2006, and the package remains present and functional across both 12.1.1 and 12.2.2 application releases. The package provides the standard, supported interface through which callers create, maintain, and validate maintenance attribute records associated with asset instances. Maintenance attributes capture the organizational, departmental, accounting, and locational context under which an asset instance is operated and maintained — for example, the owning department, the accounting class, and the EAM area to which the asset is assigned. By exposing this logic as a PL/SQL API rather than requiring direct table manipulation, Oracle ensures that the same validation, referential, and audit rules applied by the EAM application forms also govern any external or customer-written integration.

The package adheres to the Oracle Application Object Library (AOL) API programming standard. It declares g_pkg_name as a constant and follows the documented API signature conventions: an IN parameter p_api_version, initialization and commit flags (p_init_msg_list, p_commit), a validation level control (p_validation_level defaulting to FND_API.G_VALID_LEVEL_FULL), and the standard output trio x_return_status, x_msg_count, and x_msg_data. This conformity allows the API to participate in the standard error-stack and savepoint handling used throughout EBS.

Key Procedures and Functions

The ETRM metadata documents three public procedures within this package:

  • CREATE_MAINT_ATTRIBUTES — The primary creation routine. It accepts instance-level context (notably p_instance_id, p_owning_department_id, p_accounting_class_code, p_area_id, and p_parent_instance_id) and persists the corresponding maintenance attribute rows for the asset instance. It opens a savepoint (SAVEPOINT eam_maint_attribute) before performing DML and resolves defaulting/validation values such as organization and inventory identifiers internally.
  • UPDATE_MAINT_ATTRIBUTES — The public maintenance routine that modifies existing maintenance attribute records for a given asset instance, applying the same validation levels and error-stack conventions as the create routine.
  • VALIDATE_MAINT_DEFAULTS — A validation-only routine that checks the completeness and correctness of maintenance defaults prior to or independent of persistence, returning messages through the standard API output parameters.

Tables Accessed

The package references the following tables through APPS synonyms:

  • CSI_ITEM_INSTANCES — the core source of asset instance identity; the API resolves and updates instance context here.
  • BOM_DEPARTMENTS — validates the owning department referenced by p_owning_department_id.
  • WIP_ACCOUNTING_CLASSES — validates the accounting class code supplied by the caller.
  • MTL_EAM_LOCATIONS — resolves the EAM area/location associated with the attribute record.
  • MTL_SYSTEM_ITEMS — used to obtain item definition context for the asset instance.
  • MTL_PARAMETERS — supplies organization-level defaults and validation parameters, including l_org_id.

Usage Notes

EAM_MAINT_ATTRIBUTES_PUB is typically invoked from EAM asset definition and maintenance setup flows, and may be called by concurrent programs, business events, or custom PL/SQL integrations that must register or update maintenance attributes outside the standard forms. Callers should always supply a valid API version, respect the p_commit flag to control transactional boundaries, and inspect x_return_status plus the message stack before proceeding. Because the ETRM metadata records this package as being referenced by three other packages, it forms part of a larger internal dependency chain; custom code should treat it as a stable but subordinate API and avoid table-level writes to the underlying EAM tables.