Search Results update_dept_appr

Overview

APPS.EAM_DEPT_APPROVERS_PUB is a public PL/SQL API package body belonging to the Oracle Enterprise Asset Management (EAM) module. Its business purpose is to maintain the association between departments (as defined in BOM_DEPARTMENTS) and the approvers who are authorized to act on behalf of those departments. Because EAM maintenance work orders and related approval workflows must be routed to valid, department-scoped approvers, this package provides the canonical maintenance interface for creating and updating those approver assignments. The package follows the standard Oracle EBS API framework conventions, exposing the customary IN parameters (p_api_version, p_init_msg_list, p_commit, p_validation_level) and OUT parameters (x_return_status, x_msg_count, x_msg_data) that allow callers to participate in the shared FND_API error-handling and message-stack model. It is classified as a PUB package in ETRM metadata, meaning it is intended for direct invocation by external programs rather than being restricted to internal module use.

Key Procedures and Functions

ETRM documentation identifies two documented public procedures in this package:

• INSERT_DEPT_APPR — Creates a new department-approver association. The procedure validates its inputs and writes the corresponding row to the department approvers table, returning the standard API status and message outputs to the caller.
• UPDATE_DEPT_APPR — Modifies an existing department-approver association, typically to change the approver, effective dates, or status attributes of a previously created record.

In addition to the documented public procedures, the package body contains private validation helpers that enforce referential integrity before insert or update operations proceed. Notably, validate_application_id accepts an application identifier and confirms it exists in FND_APPLICATION; if no matching row is found, it raises the EAM message EAM_INVALID_APPLICATION_ID onto the message stack and propagates the standard FND_API.G_EXC_ERROR exception. A parallel helper, validate_responsibility_id, checks that a responsibility exists in FND_RESPONSIBILITY and that it belongs to the supplied application, raising EAM_DA_INVALID_RESP otherwise. These private routines support the documented public procedures and are the reason the package is commonly searched in connection with "validate_application_id."

Tables Accessed

• BOM_DEPARTMENTS — Read to confirm that the department referenced by the approver record is a valid, existing department.
• BOM_EAM_DEPT_APPROVERS — The primary transactional table; rows are inserted and updated here by INSERT_DEPT_APPR and UPDATE_DEPT_APPR.
• FND_APPLICATION — Queried by validate_application_id to confirm the application identifier is registered in the EBS application dictionary.
• FND_RESPONSIBILITY — Queried by validate_responsibility_id to confirm that the responsibility exists and is owned by the expected application.

Usage Notes

This package is typically invoked from EAM setup and maintenance forms where an administrator establishes or amends department approver records, and it may also be called from custom concurrent programs, scripts, or integration routines that batch-load approver data. ETRM metadata records no other packages referencing this API, so callers are generally external — forms, concurrent processing, or bespoke code. When invoking the package, callers should supply a valid p_api_version, honor the p_init_msg_list, p_commit, and p_validation_level conventions of FND_API, and inspect x_return_status plus the message stack (x_msg_count, x_msg_data) to surface validation failures such as an unknown application or responsibility. Because validation errors are raised through FND_MSG_PUB and FND_API.G_EXC_ERROR, callers should wrap invocations in standard exception handling. In 12.1.1 and 12.2.2 the behavior is consistent, as the package relies on core FND and BOM dictionary tables rather than release-specific structures.