Results for “promotion_type”

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

Overview

AS_PROMOTION_LETTERS_V is a Sales Foundation (AS) view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes promotion records of type "L" (letters). In Oracle EBS, "promotions" are flexible marketing and sales entities that can represent several distinct things depending on their type code. One such type is the letter, used in sales and marketing correspondence workflows. The view filters the underlying promotions data so that only enabled promotion letters are returned, together with their associated word processor definition.

Because the view restricts its result set to rows where PROMOTION_TYPE is 'L' and the enabled flag is 'Y', it is designed as a convenience reporting and integration access point rather than a general promotions query surface. Consumers that require the complete promotions catalog should query AS_PROMOTIONS directly; consumers interested specifically in active letters can use this view to avoid re-implementing the filter logic. The ETRM documentation notes that this view is not implemented in the reference database, meaning it may not exist in every environment or release, and its presence should be verified against the target instance before dependent code is deployed.

Underlying Base Objects

The view is defined as a join over two Sales Foundation tables: AS_PROMOTIONS (aliased PROM) and AS_WORD_PROCESSORS (aliased WP). Although the documented metadata lists "Referenced base objects: none documented," the view text supplied in the ETRM excerpt clearly establishes these two tables as the underlying objects.

• AS_PROMOTIONS (PROM) — the primary table holding promotion definitions, including code, name, type, enabled status, description, ownership, public visibility, and a foreign key to a word processor.
• AS_WORD_PROCESSORS (WP) — the word processor definitions used to drive document generation and merge behavior for letters and other templated output.

The join condition is PROM.WORD_PROCESSOR_ID = WP.WORD_PROCESSOR_ID, an inner join that excludes any promotion letter lacking a valid word processor reference. Filter predicates restrict results to PROM.TYPE = 'L' and PROM.ENABLED_FLAG = 'Y'. The relationship is effectively many-to-one from promotions to word processors at the row level of this view.

Key Columns

The projection includes the following attributes, all inherited from the two base tables:

• PROMOTION_ID — primary key of the promotion record in AS_PROMOTIONS.
• PROMOTION_CODE — the user-facing short code for the promotion letter.
• PROMOTION_NAME — descriptive name of the letter.
• PROMOTION_TYPE — the promotion type; in this view always 'L' by construction.
• PROMOTION_ENABLED_FLAG — enabled status; always 'Y' in this view.
• PROMOTION_DESCRIPTION — free-text description.
• PROMOTION_OWNER_PERSON_ID — the person who owns the letter, typically for security and responsibility scoping.
• PROMOTION_PUBLIC_FLAG — indicates whether the letter is publicly visible.
• PROMOTION_WORD_PROCESSOR_ID — foreign key to the associated word processor.
• WP_WORD_PROCESSOR_ID — the word processor identifier as selected from AS_WORD_PROCESSORS; effectively the same value as the preceding column in each returned row.

Common Use Cases and Queries

The view supports LOV-style lookups, validation routines, and integration extracts that need a list of active promotion letters with their document templates. A typical query selects the identification and descriptive columns:

• SELECT promotion_code, promotion_name, promotion_description FROM as_promotion_letters_v ORDER BY promotion_name;
• SELECT promotion_id, promotion_code, promotion_word_processor_id FROM as_promotion_letters_v WHERE promotion_public_flag = 'Y';
• SELECT p.promotion_code, w.wp_word_processor_id FROM as_promotion_letters_v p WHERE p.promotion_owner_person_id = :person_id;

Because the view already excludes disabled letters and non-letter promotion types, queries remain concise. In environments where the object is not deployed, equivalent output can be produced by joining AS_PROMOTIONS to AS_WORD_PROCESSORS and applying the same TYPE and ENABLED_FLAG predicates.