Search Results validate_currency

Overview

BIM_VALIDITY_CHECK is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema and classified under ETRM as an "OTHER" API. It resides in the source file bimvalcb.pls and carries the internal header identifier $Header: bimvalcb.pls 120.1 2005/06/14 15:44:53 appldev $. The package belongs to the BIM product family, which supports marketing and campaign management functionality within Oracle EBS, and in release 12.1.1 and 12.2.2 it is used to perform date, period, currency, campaign, event, and budget validity verification.

The package is notable for its stub-style implementation. As reflected in the documented excerpt, the bodies of the functions are largely placeholders: validate_periods, call_currency, and validate_currency each contain only a return('SUCCESS') statement. This indicates the package is intended as a validation framework whose actual logic was either deferred to a later patch or overridden by customer or product extensions. In practical terms, the package establishes the API contract and naming conventions used throughout the BIM validity-checking layer.

Key Procedures and Functions

ETRM documentation lists six documented procedures and functions within the package:

• validate_periods — Accepts an input date and returns a status string, determining whether the supplied date falls within a valid period. In the shipped body it returns 'SUCCESS' unconditionally.
• call_currency — Handles currency conversion-related validation. It declares local variables for from/to amounts and currencies along with a return-status flag, and currently returns 'SUCCESS' without performing conversion logic.
• validate_currency — Accepts a start date and end date and returns a status string, verifying currency validity across the specified date range.
• validate_campaigns — The most fully documented entry point. It accepts an input date representing the starting date of validity, returns two OUT NOCOPY error message parameters for period and currency validation respectively, and returns a NUMBER status code: 0 when both validations succeed and 1 when both validations fail.
• validate_events — Validates event-related data within the marketing/campaign domain; no detailed parameter documentation is provided in the metadata.
• validate_budgets — Validates budget records or budget-date relationships; likewise undocumented in parameter detail.

The consistent naming pattern confirms that validate_campaigns acts as the aggregating entry point that internally dispatches to the period and currency checks and consolidates their error messages.

Tables Accessed

The ETRM metadata records no tables referenced via APPS synonyms for this package. Consistent with its stub implementation, the shipped body performs no SQL against base tables — it declares no cursors and executes no SELECT, INSERT, UPDATE, or DELETE statements. Any future or site-specific implementation of the validation logic would presumably query BIM campaign, event, and budget tables along with currency and period setup tables, but no such access is documented in the supplied metadata.

Usage Notes

The package is referenced by zero other packages, meaning it sits at the top of its dependency chain and is invoked directly rather than through another PL/SQL wrapper. In Oracle EBS 12.1.1 and 12.2.2, packages of this type are typically called from Oracle Forms event handlers, from concurrent programs, or from custom client code via the APPS schema. Given the SUCCESS-returning stub bodies, callers should not rely on the stock package for genuine validation; the functions are most useful as extension points. A user searching for validate_periods is likely interested in either wiring an OAF or Forms page to guard date entry against invalid periods, or in overriding the packaged procedure to enforce real date-range or accounting-period logic. Any extension should preserve the documented return conventions, particularly the 0/1 status semantics of validate_campaigns, to avoid breaking downstream callers.