Results for “as_mail_blitz_letters_active_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view AS_MAIL_BLITZ_LETTERS_ACTIVE_V is a reporting and integration object within the Oracle EBS AS – Sales Foundation product family. Its documented description identifies it as the "Active mail blitzes view," indicating that it exposes a filtered subset of promotional letter records that are currently enabled and which carry a mail-blitz or generic-token purpose. In Oracle Sales Foundation, a "mail blitz" (or mailblitz) represents a targeted marketing communication — typically a letter or template — that is dispatched to a defined audience. The view therefore serves as the canonical read-only source for applications, concurrent programs, or custom reports that need to enumerate active mail-blitz letters without applying their own filtering logic.

In Oracle EBS 12.1.1 and 12.2.2, this view is part of the foundation layer that integrates sales promotions with letter-generation and correspondence functionality. Rather than storing data in its own right, it projects business-meaningful records out of the promotions table, converting low-level configuration into a consumable list of "active" mail blitzes. The 12.2.2 ETRM metadata notes that the view is "Not implemented in this database," meaning it appears in the documentation set but is not created in every environment; availability depends on whether the corresponding AS patch or configuration has been applied.

Underlying Base Objects

Although the ETRM metadata records no explicitly referenced base objects, the embedded view text identifies its sole underlying base object as AS_PROMOTIONS (aliased as P). The view is a simple projection with a restrictive WHERE clause, applying three predicates simultaneously:

• TYPE = 'L' — restricts rows to letters (as opposed to other promotion types).
• LETTER_PURPOSE_CODE IN ('GENERIC_TOKEN', 'MAILBLITZ_TOKEN') — limits records to those intended as generic tokens or mail-blitz tokens.
• ENABLED_FLAG = 'Y' — returns only currently enabled promotions, which is the basis for the "Active" designation in the view name.

Because it is defined directly over AS_PROMOTIONS, the view inherits that table's indexing, security, and multi-org characteristics. Any change to promotion data is reflected immediately in the view, as no materialization or snapshot layer is involved.

Key Columns

The ETRM metadata documents the following columns, and the view text maps them to underlying promotion attributes:

• LETTER_ID — documented column name; maps to P.PROMOTION_ID, the primary identifier of the promotion record.
• CODE — the promotion code (P.CODE), used as the human-readable short identifier.
• NAME — the promotion name (P.NAME), the descriptive label of the mail blitz letter.
• PUBLIC_FLAG — indicates whether the letter is public (Y) or restricted.
• PUBLIC_LETTER — a derived display column produced by DECODE(P.PUBLIC_FLAG, 'Y', '*', NULL), rendering an asterisk when the letter is public and NULL otherwise.
• DESCRIPTION — free-text description of the promotion.
• OWNER_PERSON_ID — the person identifier of the promotion owner, enabling joins to party or person tables for ownership reporting.

Common Use Cases and Queries

Typical scenarios include populating selection lists for mail-blitz configuration, validating which letters are eligible for dispatch, and feeding correspondence engines that require an enabled token-based letter. A representative query follows:

• SELECT letter_id, code, name, public_letter, owner_person_id FROM as_mail_blitz_letters_active_v ORDER BY name; — enumerates all active mail-blitz letters for a configuration LOV.
• SELECT code, name FROM as_mail_blitz_letters_active_v WHERE public_flag = 'Y'; — lists only public letters suitable for broad distribution.
• SELECT v.name, p.party_name FROM as_mail_blitz_letters_active_v v, hz_parties p WHERE v.owner_person_id = p.party_id; — joins ownership information to party data for stewardship reporting.

Because the view returns only enabled, token-purpose letters, consumers should treat its result set as authoritative for "active" correspondence and avoid duplicating the filtering logic at the application layer.