Results for “setup_code_jsp”

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

Overview

EAM_FAILURECODES_PVT is the private implementation package for the Enterprise Asset Management (EAM) failure code setup API in Oracle E-Business Suite. It underpins the public package EAM_FAILURECODES_PUB and encapsulates the business logic that validates, inserts, updates, copies, and locks the failure, cause, and resolution code hierarchies used by maintenance personnel to record asset failure analysis. The package is owned by APPS and classified as PVT, meaning it is intended for internal use by the EAM setup forms and by other EAM packages rather than for direct invocation by customer extensions.

The body defines constants for the package name and declares a global exception, G_LOCKROW_EXCEPTION, initialized against Oracle error -54 through PRAGMA EXCEPTION_INIT. This construct is central to the package's concurrency strategy: when a setup or lock routine attempts to lock a row already locked by another session, the -54 (resource busy) condition is trapped and translated into a friendly EAM message. A shared Raise_Error helper calls FND_MESSAGE.SET_NAME, optionally sets a token, registers the message via FND_MSG_PUB.ADD, and raises FND_API.G_EXC_ERROR, ensuring consistent error propagation to callers such as the Setup Code form.

Key Procedures and Functions

• SETUP_CODE — Creates or updates a single failure, cause, or resolution code, invoking Validate_Code to enforce mandatory attributes, code type validity within the G_FAILURE_CODE, G_CAUSE_CODE, and G_RESOLUTION_CODE enumerations, and effective date rules before committing the record.
• SETUP_COMBINATION — Maintains the relationship rows that combine failure, cause, and resolution codes into a valid combination, applying the same validation and locking semantics as SETUP_CODE.
• COPY_FAILURESET — Copies an existing failure set, including its associated codes and combinations, to produce a new set, providing a rapid setup mechanism for organizations standardizing failure hierarchies across asset groups.
• SETUP_CODE_JSP — The JSP-facing wrapper invoked by the EAM self-service or HTML setup pages to create or update code information; it delegates to SETUP_CODE and adapts error handling for the web tier.
• SETUP_COMBINATION_JSP — The JSP-facing counterpart of SETUP_COMBINATION, used by browser-based setup screens to persist combination records.
• LOCK_CODE_JSP — Acquires a row-level lock on a code record for the duration of an HTML editing session, preventing concurrent modification by another user; a -54 collision is converted to the package's lock exception.
• LOCK_COMBINATION_JSP — The analogue of LOCK_CODE_JSP for combination records, securing the combination row before changes are applied.

Tables Accessed

• EAM_FAILURE_CODES — Stores failure code definitions, including the effective_end_date column read during validation to detect existing and expired codes.
• EAM_CAUSE_CODES — Stores cause code definitions validated in the same manner as failure codes.
• EAM_RESOLUTION_CODES — Stores resolution code definitions validated against the G_RESOLUTION_CODE type.
• EAM_FAILURE_COMBINATIONS and EAM_FAILURE_COMBINATIONS_S — Hold valid combination rows and the corresponding lock/sequence data that LOCK_COMBINATION_JSP and SETUP_COMBINATION manipulate.
• EAM_FAILURE_SETS — Provides the source and target records for COPY_FAILURESET.
• EAM_ASSET_FAILURE_CODES — Records actual failure events on assets, referenced to determine whether a code is in use before changes are permitted.

All tables are accessed through APPS synonyms under the EAM schema.

Usage Notes

The package is invoked primarily from the EAM failure code setup forms and associated JSP pages within Oracle EBS 12.1.1 and 12.2.2, and it is referenced by one other package, which relies on its validation and locking services. Direct calls from custom code should target EAM_FAILURECODES_PUB instead, since the PVT naming convention signals that signatures may change without notice. Because the package depends on FND_MESSAGE, FND_MSG_PUB, and FND_API, the standard EBS message stack must be initialized by the calling form or concurrent program. The lock exception handling assumes that the -54 error is raised only by the intended FOR UPDATE operations; custom callers trapping G_LOCKROW_EXCEPTION should surface the associated EAM lock message rather than interpreting it as a generic database failure.