Search Results aml_timeframe_pub_w




Overview
Explore in AI Chat

Overview

APPS.AML_TIMEFRAME_PUB_W is a public PL/SQL wrapper package belonging to the Oracle E-Business Suite Advanced Marketing (AML) module, which forms part of the Oracle Trade Management and Marketing foundation. The package exposes a programmatic interface for managing "timeframes" — marketing-related date-range definitions used to qualify campaign activities, leads, opportunities, and other time-bound marketing entities. It is a Rosetta-generated wrapper (_W suffix), meaning it is automatically produced by Oracle's Rosetta code-generation framework to bridge the internal (private) implementation package with external callers while enforcing the standard EBS API contract.

The package is declared with AUTHID CURRENT_USER, so it executes with the privileges of the calling schema rather than the owner, which is consistent with Oracle's published API conventions that require the caller to hold the necessary grants on underlying tables and on the private implementation package. The header carries the standard EBS revision stamp ($Header: amlwtfrs.pls 115.1 2003/01/03), indicating this code dates to early releases of the 11i lineage and has been carried forward unchanged into 12.1.1 and 12.2.2. Its API classification is recorded as OTHER, meaning it is not part of the formally certified "PUB" set of business object APIs but is nonetheless shipped and callable.

Key Procedures and Functions

The documented interface comprises five procedures:

  • ROSETTA_TABLE_COPY_IN_P3 — Converts the standard EBS JTF_TABLE collection types (JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_100, JTF_DATE_TABLE) into the internal aml_timeframe_pub.timeframe_tbl_type PL/SQL record collection used by the private implementation. This procedure is invoked internally by the wrapper to marshal bulk array input.
  • ROSETTA_TABLE_COPY_OUT_P3 — Performs the inverse marshalling, copying the internal timeframe_tbl_type collection back into JTF table types for bulk output to the caller.
  • CREATE_TIMEFRAME — Creates a new timeframe record. Its signature follows the canonical EBS API shape: API version, message list initialization, commit control, validation level, access-check and administration flags, admin group and identity/salesforce identifiers, an array-based attribute payload (p8_a0/p8_a1), followed by the standard OUT parameters x_timeframe_id, x_return_status, x_msg_count, and x_msg_data. Optional record-level attributes (p9_a0 through p9_a8) carry defaults of fnd_api.g_miss_num, fnd_api.g_miss_char, and fnd_api.g_miss_date as appropriate. This is the routine reached when a caller searches for "create_timeframe".
  • UPDATE_TIMEFRAME — Modifies an existing timeframe using the same API contract pattern, including validation, access-check, and administrative control parameters.
  • DELETE_TIMEFRAME — Removes a timeframe, applying the same standard EBS error-handling and message-stack conventions.

Tables Accessed

The ETRM metadata records a single referenced object via APPS synonym: PLITBLM. This is the standard EBS multi-purpose PL/SQL table used as an intermediate collection store during Rosetta-style bulk marshalling. No direct DML against the AML timeframe base tables is documented at the wrapper layer; actual persistence occurs inside the private implementation package (aml_timeframe_pub), which this wrapper delegates to after conversion of the JTF arrays.

Usage Notes

This package is typically invoked from AML marketing setup forms, from concurrent programs that bulk-load or refresh timeframe definitions, or from custom PL/SQL that must create timeframes in a controlled, validated manner. Callers should initialize the message list, pass a valid API version, and inspect x_return_status and the message stack (fnd_msg_pub) after every call. Because the package is AUTHID CURRENT_USER, invoking schemas must hold explicit grants on the wrapper, the private package, and PLITBLM. The supplied defaults for p9_a0–p9_a8 allow callers to omit attributes that are not being changed. As the package is classified OTHER rather than a certified public API, Oracle does not guarantee interface stability across patches, and custom code should be regression-tested on upgrade from 12.1.1 to 12.2.2.