Search Results validate_boolean_flag

Overview

APPS.EAM_PARAMETERS_PUB is a public PL/SQL API package in Oracle Enterprise Asset Management (eAM) that manages the setup parameters controlling eAM behavior at the organization level. Its header comment identifies it as an API of type "Public" exposing the functions insert_parameters and update_parameters, following the standard Oracle E-Business Suite API conventions (p_api_version, p_init_msg_list, p_commit, p_validation_level as inputs, and x_return_status, x_msg_count, x_msg_data as outputs). The package body carries the header identifier EAMPPRMB.pls 120.2, indicating it ships as part of the eAM product family.

The core business constraint enforced by the package is stated directly in the source: "There can be only one set of eam parameters for each unique organization_id." This cardinality rule governs how eAM costing, accounting, and maintenance parameters are stored and maintained, and it is the rationale behind the package's internal validation logic.

Key Procedures and Functions

The documented public procedures are:

• INSERT_PARAMETERS — Creates the single set of eAM parameters for a given organization. Because only one parameter row may exist per organization, this procedure is invoked when no parameter record is present for the organization. It is protected by the private helper validate_unique_org_id, which queries WIP_EAM_PARAMETERS and returns a Boolean indicating whether a row already exists for the supplied organization identifier.
• UPDATE_PARAMETERS — Modifies the existing eAM parameter record for an organization. This procedure is used once the initial parameter set has been created and subsequent changes to costing or accounting behavior are required.

The metadata additionally lists helper routines that support the public entry points, including validate_unique_org_id, a function intended to validate that a supplied lookup code is permissible, and print_log, a debugging utility declared with PRAGMA AUTONOMOUS_TRANSACTION that writes messages to the concurrent manager log via FND_FILE.PUT_LINE.

In the context of the searched term validate_boolean_flag, this package follows the standard EBS API idiom of representing Boolean flags as VARCHAR2 values using the FND_API constants G_TRUE and G_FALSE. The parameter p_init_msg_list and p_commit default to FND_API.G_FALSE, and this convention is the mechanism by which flag-style parameters are validated and interpreted within the API. No separate public procedure named validate_boolean_flag is documented in this package; flag validation is performed inline using these predefined constants.

Tables Accessed

• WIP_EAM_PARAMETERS — The primary table. Holds the single eAM parameter row per organization and is read by validate_unique_org_id and written by INSERT_PARAMETERS and UPDATE_PARAMETERS.
• MTL_PARAMETERS — Organization-level inventory parameters, consulted to validate organization context and defaults.
• HR_ORGANIZATION_INFORMATION — Provides organization classification attributes used to validate that the target organization is a valid eAM-enabled organization.
• WIP_ACCOUNTING_CLASSES — Supplies the accounting class definitions referenced by eAM costing parameters.
• CST_EAM_COST_ELEMENTS — Defines the cost elements available for eAM maintenance costing setup.
• GL_CODE_COMBINATIONS — Validates the general ledger account combinations selected for eAM accounting parameters.

Usage Notes

EAM_PARAMETERS_PUB is a setup-layer API and is not intended for high-volume transactional use. It is typically invoked from the eAM setup user interface in Oracle Forms, where the Parameters window calls INSERT_PARAMETERS when creating the first parameter record for an organization and UPDATE_PARAMETERS for subsequent modifications. The procedures may also be called from concurrent programs, third-party integration code, or custom PL/SQL that programmatically provisions eAM organizations during implementation or cloning activities.

Callers must supply a valid API version, follow the standard FND_API message-handling protocol (checking x_return_status and retrieving messages via FND_MSG_PUB), and honor the commit semantics defined by the p_commit flag. Because the package enforces one parameter set per organization, custom code must not attempt to insert a second row; attempt to insert for an organization already configured should be routed to UPDATE_PARAMETERS. The ETRM metadata records no other packages as depending on this API, so it should be treated as a terminal setup interface rather than a shared utility.