Search Results email_flag

Overview

AS_COLLATERAL_KITS_V is a reporting and integration view within the Oracle E-Business Suite Sales Foundation (AS) module. It exposes the relationship between parent and child collateral items — commonly referred to as "collateral kits" — by joining the kit definition table (AS_COLLATERAL_KITS) to the collateral master view (AS_COLLATERAL_V) and, through an outer join, the word processor setup table (AS_WORD_PROCESSORS). The view presents each parent-to-child collateral association alongside descriptive attributes of the child collateral and its associated delivery/processing flags, including print, fax, and email indicators.

The view serves as a convenient denormalized source for reports and interfaces that need to resolve the composition of a collateral kit and the distribution behavior of its components without writing the three-way join manually. Because it includes an outer join to AS_WORD_PROCESSORS, kits and collateral that have no word processor configuration are still returned, with the delivery flags defaulted to 'N'. This makes the view safe for use in queries where word processor setup may be incomplete.

Underlying Base Objects

The view text defines the join across three objects:

• AS_COLLATERAL_KITS — the driving table (aliased K), which stores the parent/child collateral relationships and the quantity of the child item within the kit. It also carries the standard EBS WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and fifteen descriptive flexfield attribute columns.
• AS_COLLATERAL_V — the collateral master view (aliased C), providing child collateral descriptive data such as code, name, status, description, chargeback amount, quantity on hand, pick flag, online flag, language, country, inventory item, and organization.
• AS_WORD_PROCESSORS — the word processor setup table (aliased WP), joined with an outer join (+) on WORD_PROCESSOR_ID, supplying print, fax, and email flag configuration.

Note that the ETRM metadata records no documented base tables and states the view is "not implemented in this database," meaning it is delivered by the AS product but may not be deployed in every environment.

Key Columns

• ROW_ID — the ROWID of the underlying AS_COLLATERAL_KITS row.
• PARENT_COLLATERAL_ID / CHILD_COLLATERAL_ID — identifiers establishing the kit's parent-child composition.
• QUANTITY — the number of child collateral units contained in the kit.
• CODE, NAME, STATUS, DESCRIPTION — child collateral identification and descriptive fields.
• CHARGEBACK_AMT, QTY_ON_HAND — cost and inventory-related attributes of the child collateral.
• MANUAL_PRINT_FLAG — derived via DECODE: 'N' when no word processor exists, otherwise 'Y'.
• AUTO_PRINT_FLAG, FAX_FLAG, EMAIL_FLAG — sourced from AS_WORD_PROCESSORS and defaulted to 'N' via NVL when no word processor row exists. EMAIL_FLAG specifically indicates whether the collateral is configured for email delivery.
• PICK_FLAG, ONLINE_FLAG — fulfillment and online-availability indicators.
• LANGUAGE, COUNTRY, INVENTORY_ITEM_ID, ORGANIZATION_ID — localization and inventory linkage.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — descriptive flexfield columns.

Common Use Cases and Queries

A frequent requirement is to identify collateral kits whose components are flagged for email delivery, which is the context in which the EMAIL_FLAG column is queried:

SELECT k.ROW_ID,
       k.PARENT_COLLATERAL_ID,
       k.CHILD_COLLATERAL_ID,
       k.CODE,
       k.NAME,
       k.EMAIL_FLAG
FROM   AS_COLLATERAL_KITS_V k
WHERE  k.EMAIL_FLAG = 'Y';

Another common scenario lists all children belonging to a given kit with their distribution flags:

SELECT k.CHILD_COLLATERAL_ID,
       k.NAME,
       k.QUANTITY,
       k.MANUAL_PRINT_FLAG,
       k.AUTO_PRINT_FLAG,
       k.FAX_FLAG,
       k.EMAIL_FLAG
FROM   AS_COLLATERAL_KITS_V k
WHERE  k.PARENT_COLLATERAL_ID = :parent_id;

The view is also useful for reconciling collateral configuration against inventory, for example joining INVENTORY_ITEM_ID and ORGANIZATION_ID to item master tables, or for auditing kits where no word processor has been configured (EMEAIL_FLAG = 'N' across all children). Because it hides the underlying join complexity and defaults absent delivery flags, it is well suited to ad hoc reporting, personalizations, and outbound integration extracts in both 12.1.1 and 12.2.2 environments where it is deployed.