Search Results validate_decn_timeframe_code

Overview

AML_TIMEFRAME_PVT is a private PL/SQL package in the Oracle E-Business Suite 12.1.1 / 12.2.2 environment that encapsulates the business logic supporting the Oracle Sales Leads / Marketing decision timeframe functionality. The package belongs to the AML (Sales Leads / Marketing) product family and is classified as a private (PVT) API package, meaning it exists to service the public API layer — specifically AML_TIMEFRAME_PUB — and is not intended for direct invocation by external callers. Its principal responsibility is to manage the lifecycle of decision timeframe records, including their creation, maintenance, deletion, and validation. As documented in the ETRM metadata, the package exposes six procedures and functions and is referenced by one other package in the EBS codebase, confirming its role as a subordinate implementation unit rather than a standalone integration point.

Key Procedures and Functions

The package exposes six documented program units, each aligned to a discrete operation on decision timeframe data:

• CREATE_TIMEFRAME — Inserts a new decision timeframe record, performing the standard EBS API housekeeping such as message list initialization, validation level handling, and commit control, and returning the generated primary key identifier.
• UPDATE_TIMEFRAME — Modifies an existing decision timeframe record, applying the same API conventions as the create operation.
• DELETE_TIMEFRAME — Removes or logically terminates a decision timeframe record.
• VALIDATE_TIMEFRAME_ID — Confirms that a supplied timeframe identifier corresponds to a valid, existing record.
• VALIDATE_DECN_TIMEFRAME_CODE — Confirms that a supplied decision timeframe code is valid. This is the routine most closely associated with the user's search term, and it is the natural entry point for callers attempting to verify a timeframe code before persisting dependent data.
• VALIDATE_TIMEFRAME_DAYS — Confirms the validity of the day-based attributes associated with a timeframe definition.

No parameter lists are reproduced here, as the metadata does not fully enumerate them for every routine.

Tables Accessed

The package operates against a single documented base table accessed through its APPS synonym: AML_SALES_LEAD_TIMEFRAMES. This table stores the decision timeframe definitions used in sales lead processing. The package reads this table during the validation routines — for example, the internal cursor embedded in CREATE_TIMEFRAME queries AML_SALES_LEAD_TIMEFRAMES for an existing, enabled decision_timeframe_code — and writes to it during create, update, and delete operations. The enabled_flag column is significant, since validation and uniqueness checks are scoped to enabled records only.

Usage Notes

Because AML_TIMEFRAME_PVT is a private package, it is invoked indirectly. The standard invocation path is through the public wrapper package AML_TIMEFRAME_PUB, which references this private package and handles the outward-facing API contract. In Oracle EBS, such private packages are typically called from:

• Oracle Forms-based setup or maintenance screens where users define and maintain decision timeframes.
• Concurrent programs that create, update, or purge timeframe data in batch.
• Custom or extension code that subscribes to the public API rather than the private package directly.

Developers searching for validate_decn_timeframe_code should note that this routine is a validation-only helper. It raises or reports errors through the standard FND message stack and does not itself commit data. Direct calls to the private package are unsupported; callers should route requests through AML_TIMEFRAME_PUB and respect the API version and validation-level parameters passed down from the public layer.