Search Results populate_null_columns

Overview

The APPS.EAM_PERMIT_DEFAULT_PVT package is a private (PVT) PL/SQL package within the Oracle Enterprise Asset Management (EAM) module of Oracle E-Business Suite. It supports the work permit and safety management functionality delivered through the EAM Process Safety public APIs, specifically the work permit header structure defined in EAM_PROCESS_SAFETY_PUB. The package carries the AUTHID CURRENT_USER directive, meaning its runtime privileges are resolved against the invoking schema rather than the package owner, a design choice that allows it to operate consistently within the security context of the calling application code.

Its principal business role is to preserve previously entered work permit data when a user updates an existing permit record. In EAM, work permits capture safety-critical attributes associated with work orders and maintenance activities. When users modify a permit through the maintenance user interface, they frequently leave certain fields untouched. Without a defaulting mechanism, those unfilled columns could be overwritten with nulls, silently discarding valid data. This package exists to prevent that outcome by carrying forward values from the prior database record.

Key Procedures and Functions

The only documented procedure in this package is Populate_Null_Columns. As its name and the embedded source comments indicate, the procedure inspects the columns of an incoming work permit header record that the user has not populated, and assigns each such column the corresponding value from the old (previously stored) record. This behavior applies exclusively to the update scenario; the source header explicitly states that the procedure "is not called for CREATE," since there is no prior record to draw default values from during initial permit creation.

The procedure operates on the record type EAM_PROCESS_SAFETY_PUB.eam_wp_header_rec_type, accepting both the new incoming record and the old stored record, and returning an output record with the null columns reconciled. No public functions are exposed by this package; its interface is intentionally narrow and internal.

Tables Accessed

The ETRM metadata does not list any base tables accessed through APPS synonyms for this package. This is consistent with its design: the procedure performs in-memory record manipulation rather than direct SQL against database tables. All input and output values are passed through PL/SQL record parameters, and the actual persistence of the reconciled record is handled by the calling layer within EAM_PROCESS_SAFETY_PUB and its associated DML routines. Any table interaction ultimately falls to the public API that invokes this private helper, which is where permit header inserts and updates against the underlying EAM safety tables occur.

Usage Notes

This package is classified as a private API, meaning it is not intended for direct invocation by customers or third-party integrations. It is referenced by one other package — logically the EAM Process Safety public API layer — which orchestrates the overall permit create, update, and delete logic. During a permit update, the public API retrieves the existing record, passes it along with the user-modified record to Populate_Null_Columns, and then persists the returned, fully populated record.

Because the procedure is scoped to the update path, developers extending EAM safety functionality should not call it during creation flows. The header comment block references script version 120.1, dated 2011, indicating the package has been stable across EBS 12.1.1 and 12.2.2 releases. Customizations should be avoided; instead, use the supported public APIs in EAM_PROCESS_SAFETY_PUB, letting this private package handle null-column defaulting transparently as part of the standard update transaction.