Search Results ams_campaign_type




Overview
Explore in AI Chat

Overview

APPS.AMS_SOURCECODE_PVT is a private PL/SQL package within the Oracle Marketing (AMS) module of Oracle E-Business Suite. Its central responsibility is the generation, validation, and maintenance of source codes that uniquely identify marketing entities such as campaigns, event offers, and offers. Source codes function as the human-readable identifiers that allow marketing organizations to track the origin and attribution of leads, responses, and revenue across channels. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the owner, and its "PVT" classification indicates it is an internal implementation layer not intended for direct customer invocation. It supplies the underlying logic that public marketing APIs and concurrent processes depend upon when creating or modifying marketing objects. The current header references release 11.5.10 lineage (115.17, dated 2002), but the package remains present and documented in the 12.1.1 and 12.2.2 ETRM repository.

Key Procedures and Functions

The documented API surface consists of six callable units, supported by internal helpers referenced in the source listing including IS_SOURCE_CODE_UNIQUE and GET_NEW_SOURCE_CODE.

  • IS_SOURCE_CODE_UNIQUE — Validates whether a supplied source code value is unique across existing records. It returns a Boolean-style indicator using the FND_API constants g_true or g_false, allowing callers to enforce uniqueness before persistence.
  • GET_NEW_SOURCE_CODE — Generates a new unique source code for a given object type and custom setup, with an optional global audience flag. It raises FND_API.g_exc_error when profile option values would produce an invalid configuration.
  • GET_SOURCE_CODE — The primary code-generation function matched to the user search term. It derives a source code prefix from the supplied type code; when no type code is provided, the ARC object identifier itself serves as the prefix. The ARC object must be one of CAMP, EVEH, or OFFR, and the optional type code must be a valid lookup code from AMS_CAMPAIGN_TYPE, AMS_EVENT_TYPE, or AMS_OFFER_TYPE.
  • CREATE_SOURCECODE — Persists a new source code record, populating the seeded and generated-code tables and their intersection and sequence entities.
  • MODIFY_SOURCECODE — Updates attributes of an existing source code record, typically invoked when the descriptive or type information associated with a code changes.
  • REVOKE_SOURCECODE — Withdraws or inactivates a source code so that it can no longer be assigned or used for tracking.

Tables Accessed

The package operates against the AMS source code data model through APPS-owned synonyms.

  • AMS_SOURCE_CODES — The base table storing source code definitions and their attributes; the package inserts, updates, and queries it during creation, modification, and revocation.
  • AMS_SOURCE_CODES_S — The Oracle Applications intersection/seed table capturing source code security or ownership relationships used when applying access rules.
  • AMS_SOURCE_CODES_GEN_S — Records generated source code sequences or generation history, supporting the uniqueness guarantee enforced by IS_SOURCE_CODE_UNIQUE.
  • AMS_GENERATED_CODES — Stores generated code values, read and written during the GET_NEW_SOURCE_CODE and GET_SOURCE_CODE generation cycle.
  • DUAL — Used for scalar evaluation and formatting operations within the generation logic.

Usage Notes

Because AMS_SOURCECODE_PVT is a private package, direct calls from customer extensions are discouraged; the package is referenced by roughly twelve other packages in the marketing schema that expose supported public APIs. In practice it is invoked when marketing users create campaigns, offers, or event offers through the Oracle Marketing forms, when bulk imports or concurrent programs generate marketing objects, or when integration code creates marketing entities via the supported public APIs, which in turn delegate source code generation here. The get_source_code entry point is the routine most commonly reached at runtime. Implementers performing diagnostics on source code generation issues should trace calls into this package while treating the public marketing APIs as the supported integration boundary.