Search Results as_collateral_kits_u1

Overview

OSM.AS_COLLATERAL_KITS_ALL is a transactional table within the Oracle E-Business Suite (EBS) Oracle Incentive Compensation (OIC) / Trade Management (formerly OSM, the schema historically associated with Supply Chain modules and promotions). The table stores the definitional relationships for collateral kits, that is, the parent-child composition of promotional collateral items that are grouped and distributed together as a single kit. Each row links a parent collateral (a "kit" promotion record) to a child collateral (an individual component promotion record) and carries a quantity indicating how many units of the child belong to the parent.

The "_ALL" suffix indicates that the table is partitioned by operating unit via the ORG_ID column, and the associated APPS synonym AS_COLLATERAL_KITS_ALL exposes the data through the standard multi-org view. The table resides in the APPS_TS_ARCHIVE tablespace and is maintained through concurrent programs and the Trade Management forms, not through a public API, so its contents are typically managed by the application itself.

In line with Data Vault modeling heuristics derived from the foreign key structure, this object is best classified as a link table. Its columns PARENT_COLLATERAL_ID and CHILD_COLLATERAL_ID each resolve to the AS_PROMOTIONS_ALL table, forming a many-to-many associative bridge between promotion records. The measured attribute QUANTITY acts as a degenerated attribute on the link, while the standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the descriptive ATTRIBUTE1…ATTRIBUTE15 flex columns serve as satellite context.

Key Information Stored

The most significant columns are:

• PARENT_COLLATERAL_ID — Surrogate identifier of the parent (kit) promotion record; foreign key to AS_PROMOTIONS_ALL.
• CHILD_COLLATERAL_ID — Surrogate identifier of the child (component) promotion record; foreign key to AS_PROMOTIONS_ALL.
• ORG_ID — Operating unit identifier enabling multi-org partitioning.
• QUANTITY — Number of child collateral units contained within the parent kit.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — Audit trail of the last modification.
• CREATION_DATE / CREATED_BY — Audit trail of the initial insertion.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1…ATTRIBUTE15 — Descriptive flexfield columns reserved for customer-specific extensions.

The composite primary key AS_COLLATERAL_KITS_PK is defined on (PARENT_COLLATERAL_ID, CHILD_COLLATERAL_ID), which represents the surrogate/business identity at the row level. A separate unique index, AS_COLLATERAL_KITS_U1, is defined on (PARENT_COLLATERAL_ID, CHILD_COLLATERAL_ID, ORG_ID). The user query "as_collateral_kits_u1" corresponds precisely to this unique index, which enforces that a given parent-child collateral pairing is unique within an operating unit; this is the natural business-key candidate for the table and is the index most likely referenced in dependency and tuning analyses.

Common Use Cases and Queries

The primary reporting scenarios involve exploding a promotional kit into its component collateral items and aggregating the quantities required for distribution or inventory planning. A typical join pattern retrieves the parent and child promotion descriptions alongside the kit quantity:

• Identifying all child collateral items belonging to a given kit by filtering on PARENT_COLLATERAL_ID.
• Reverse lookup: determining which kits contain a particular child collateral by filtering on CHILD_COLLATERAL_ID.
• Auditing duplicate or conflicting kit definitions using the AS_COLLATERAL_KITS_U1 column set.
• Multi-org reporting restricted by ORG_ID to isolate a single operating unit's kit definitions.
• Extracting flexfield-based classifications through ATTRIBUTE_CATEGORY and the numbered ATTRIBUTE columns.

A representative query joins the table twice to AS_PROMOTIONS_ALL to resolve parent and child names, returning PARENT_COLLATERAL_ID, CHILD_COLLATERAL_ID, QUANTITY, and ORG_ID, ordered by the parent. Analysts frequently pair this table with the standard audit columns to detect recent changes introduced by concurrent kit maintenance programs.

Related Objects

The following objects are most significant to the use and integrity of AS_COLLATERAL_KITS_ALL:

• AS_PROMOTIONS_ALL — Referenced twice, via PARENT_COLLATERAL_ID and CHILD_COLLATERAL_ID; supplies the promotion header records for both kit and component collateral items.
• APPS.AS_COLLATERAL_KITS_ALL — The APPS synonym/view that exposes the OSM table through the multi-org security framework.
• AS_COLLATERAL_KITS_PK — The primary key constraint on (PARENT_COLLATERAL_ID, CHILD_COLLATERAL_ID).
• AS_COLLATERAL_KITS_U1 — The unique index on (PARENT_COLLATERAL_ID, CHILD_COLLATERAL_ID, ORG_ID) that defines the business key.
• OSM.AS_COLLATERAL_KITS_ALL itself does not reference any other database objects besides the two foreign keys to AS_PROMOTIONS_ALL, and is referenced only by its APPS synonym, indicating a tightly scoped dependency footprint.

Because the table participates solely in the promotions relationship model, any change to AS_PROMOTIONS_ALL structure or operating-unit configuration should be reviewed alongside this object to preserve referential integrity.