Results for “g_resolution_code”

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

Overview

APPS.EAM_FAILURECODES_PUB is a public PL/SQL API package in Oracle E-Business Suite Enterprise Asset Management (EAM). It provides a programmatic interface for maintaining the failure, cause, and resolution code structures used by maintenance organizations to classify equipment breakdowns and their corrective actions. In EAM, failure analysis depends on a normalized coding schema in which each failure event is described by a failure code, an associated cause code, and a resolution code. This package manages both the individual code definitions and the valid combinations that bind a failure, cause, and resolution into a reusable diagnostic pattern. The package follows the standard Oracle EBS PL/SQL API conventions, exposing the FND_API message-handling parameters and returning a standard x_return_status value, and it is classified as a PUB (public) API, meaning it is intended for external invocation by forms, concurrent programs, and customer extensions rather than internal-only use.

Key Procedures and Functions

The package exposes six documented procedures, organized into two functional pairs of three.

• CREATE_CODE — Creates an individual failure, cause, or resolution code. The record type eam_failurecode_rec_type carries the code type, code value, description, effective end date, and a stored last-update date. The header comment documents that code_type and code are required, and that code_type must correspond to a lookup value seeded for the EAM_FAILURE_CODE_TYPE lookup.
• UPDATE_CODE — Modifies an existing failure, cause, or resolution code definition.
• DELETE_CODE — Removes an existing code definition.
• CREATE_COMBINATION — Creates a valid combination linking a failure code, cause code, and resolution code, using the eam_combination_rec_type record, which also carries set identifier, descriptions for each of the three components, effective end date, combination identifier, and standard WHO audit columns.
• UPDATE_COMBINATION — Modifies an existing failure/cause/resolution combination.
• DELETE_COMBINATION — Removes an existing combination.

The package also declares three named constants that drive the code_type parameter: G_FAILURE_CODE (10), G_CAUSE_CODE (20), and G_RESOLUTION_CODE (30). These constants are the authoritative mechanism for distinguishing the three code categories, and G_RESOLUTION_CODE is the value passed when defining or filtering resolution codes. The record structures and constants are declared at package level and are therefore visible to any caller that references the package specification.

Tables Accessed

The supplied documentation does not enumerate the underlying tables by name and lists no APPS synonyms for this package. Functionally, the procedures operate against the EAM failure-code reference tables that store code definitions (typed by G_FAILURE_CODE, G_CAUSE_CODE, or G_RESOLUTION_CODE), the combination table that persists the failure/cause/resolution links, and the code set definition tables referenced by the set_id and set_name fields of the combination record. The stored_last_upd_date field in both record types indicates the API performs last-update-date validation against the current database row to detect concurrent modification. Because the metadata is limited, table names should be confirmed against the EAM schema before building direct DML.

Usage Notes

This package is typically invoked from the EAM failure code setup forms, from concurrent programs that load or synchronize failure code data, and from custom PL/SQL that programmatically seeds code structures during implementation or data migration. Callers must supply p_api_version, should set p_init_msg_list to FND_API.G_FALSE unless message stack initialization is required, and should leave p_commit at its default of FND_API.G_FALSE when the API call is part of a larger transaction. Return status must be checked against FND_API.G_RET_STS_SUCCESS, and x_msg_count and x_msg_data should be consumed through the standard FND message retrieval utilities. One other package references this API, so changes to its behavior can affect dependent code. When populating the combination record, resolution values are supplied through the resolution_code and resolution_description fields, corresponding to the G_RESOLUTION_CODE code type.