Search Results as_api_records_pkg




Overview
Explore in AI Chat

Overview

APPS.AS_INTEREST_PUB is the public API package for the Oracle E-Business Suite iStore/TeleSales "Interests" functionality within the Advanced Sales (AS) product family. In EBS 12.1.1 and 12.2.2, the AS schema maintains a catalog of interest categories and values that describe customer or lead preferences (for example, product affinities, hobbies, or buying interests). These interests are captured on leads, opportunities, and customer records and are used by iStore personalization, TeleSales scripts, and marketing segmentation.

The _PUB suffix designates this as the published, externally callable API. It provides the sanctioned entry points for creating, maintaining, and deleting interest data, while delegating the actual business logic to the private package AS_INTEREST_PVT. Because it is the public wrapper, it is the interface that other modules and customer extensions should call rather than touching the private package or base tables directly.

Key Procedures and Functions

The ETRM metadata documents five procedures/functions. Parameter lists are not published here and must be obtained from the package specification.

  • CREATE_INTEREST — Creates a new interest record (interest category or value) in the AS interest repository.
  • UPDATE_INTEREST — Modifies the attributes of an existing interest record.
  • DELETE_INTEREST — Removes an interest record, subject to the API's validation and referential-integrity rules.
  • CONVERT_VALUES_TO_IDS — Translates interest value names/descriptions into their internal numeric identifiers, facilitating lookups where a caller supplies human-readable values.
  • CONVERT_INTEREST_VALUES_TO_IDS — A companion conversion routine that maps interest value strings to their surrogate IDs, typically used when importing or loading interest data in bulk.

Tables Accessed

The package reads and writes AS_INTEREST_STATUSES, which stores the status definitions (for example, active/inactive) governing interest records, and it leverages PLITBLM, the standard PL/SQL table/index-by-table support object used for bulk operations and array processing. Access to these base tables is performed through APPS synonyms, consistent with EBS schema conventions. Additional interest-value detail resides in the underlying AS interest tables manipulated by AS_INTEREST_PVT; the public package exposes them indirectly through the procedures above.

Usage Notes

AS_INTEREST_PUB is invoked in several standard integration paths. It is referenced by AS_API_RECORDS_PKG and AST_API_RECORDS_PKG, the record-handling packages used in iStore and TeleSales contexts, and by AS_IMPORT_SL_PVT, which drives sales-lead import processing. The views and wrappers AS_INTEREST_PUB_W and AS_INTEREST_PUB_W also call it, and IES_TELESALES_BP_PKG and AML_SALES_LEADS_V2_PUB reference it from the TeleSales and Marketing lead-management areas respectively. This dependency chain confirms that the package is a foundational service for interest maintenance across sales and marketing flows.

Because AS_INTEREST_PUB is classified as a PUB (public) API and follows the standard FND_API error-handling model (it depends on FND_API), callers should invoke it from custom PL/SQL, concurrent programs, or form-based controllers rather than issuing direct DML against the interest tables. Doing so ensures that validation, status checks, and conversion logic remain centralized.

Note on the search term: the user queried "as_api_records_pkg." The metadata shows AS_API_RECORDS_PKG is a dependent of AS_INTEREST_PUB rather than the object itself; the corresponding TeleSales/Interface reference is AST_API_RECORDS_PKG. Both are documented as referencing this package, so AS_API_RECORDS_PKG should be investigated separately if the caller's intent was that object.