Search Results as_collateral_kits




Overview
Explore in AI Chat

Overview

AS_COLLATERAL_KITS is a multi-org secured view owned by the APPS schema in Oracle E-Business Suite, belonging to the AS – Sales Foundation product family. It presents the relationship between parent collateral items and their component child collateral items, effectively modelling the bill-of-materials structure for sales collateral kits. A collateral kit groups several individual collateral pieces under a single parent identifier, and this view exposes that parent-child mapping together with quantity and descriptive attributes.

The view is classified as VALID and is a runtime reporting and integration object rather than a base table. Its principal role is to provide an operating-unit filtered window onto the underlying entity, so that queries executed within a given organization context return only rows belonging to that organization. This makes it a standard access point for concurrent programs, forms, OAF pages, and custom interfaces that must respect multi-org security without encoding ORG_ID logic themselves.

Underlying Base Objects

The view is defined over a single base object, AS_COLLATERAL_KITS_ALL, referenced through a synonym. AS_COLLATERAL_KITS_ALL is the multi-org table that physically stores every collateral kit association across all operating units; the _ALL suffix indicates that it is not org-secured at the table level. The view applies the org filter through the standard EBS client-info mechanism.

The filter predicate compares ORG_ID to the value derived from USERENV('CLIENT_INFO'), decoding the first ten characters of the client information string, testing for a leading blank, and substituting -99 when no organization context is set. Because it uses NVL on both sides of the comparison, rows with a null ORG_ID (global or seed data) remain visible to every organization. This is the canonical multi-org view pattern used throughout the APPS schema.

Key Columns

Common Use Cases and Queries

Typical scenarios include expanding a kit into its constituent collateral for pick, ship, or print processing; validating kit composition during collateral setup; and extracting kit structures for data warehousing or migration.

Listing all components of a specific kit:

SELECT child_collateral_id, quantity FROM as_collateral_kits WHERE parent_collateral_id = :p_parent_id;

Identifying which kits contain a given collateral item:

SELECT parent_collateral_id, quantity FROM as_collateral_kits WHERE child_collateral_id = :p_child_id;

Reporting kit membership with audit context:

SELECT parent_collateral_id, child_collateral_id, quantity, org_id, last_update_date, last_updated_by FROM as_collateral_kits ORDER BY parent_collateral_id, child_collateral_id;

Because the view enforces multi-org security automatically, queries return only rows for the session's current operating unit unless the organization context is set appropriately. For cross-organization reporting, the base table AS_COLLATERAL_KITS_ALL should be queried instead, subject to appropriate privileges.