Search Results csd_quality_thresholds_b

Overview

CSD_QUALITY_THRESHOLDS_B is a setup table within the CSD (Depot Repair) product schema in Oracle E-Business Suite, documented as VALID in both 12.1.1 and 12.2.2. Its stated purpose is to hold quality threshold setups — the configuration records that determine the maximum acceptable returned quantity for a given item, item category, or organization combination before a quality or return-authorization condition is triggered. Because it is a definitional/setup object rather than a transactional one, rows are typically created and maintained during implementation and revisited only when return policies change.

From a data-modeling perspective, the mined relationship data classifies this object as standalone, meaning it participates in no foreign-key relationships to other tables. Heuristically, therefore, it is best modeled as a hub-like or reference/dimension entity rather than as a link or satellite: it carries its own surrogate identity and its own descriptive attributes, with no documented dependency chain to another entity. When used in a Data Vault pattern, it would most naturally serve as a reference table feeding a dimensions layer.

Key Information Stored

The table contains 30 documented columns. The most significant of these are the following.

• QUALITY_THRESHOLD_ID — the surrogate primary key, enforced by CSD_QUALITY_THRESHOLDS_PK1. Every row is uniquely identified by this system-generated identifier.
• INVENTORY_ORG_ID — the inventory organization to which the threshold applies, allowing thresholds to vary by warehouse or repair organization.
• INVENTORY_ITEM_ID — the specific inventory item governed by the threshold.
• ITEM_CATEGORY_ID — the item category governed by the threshold, providing a broader alternative to item-level setup.
• ITEM_REVISION — the revision of the item for which the threshold is defined, permitting revision-specific quality limits.
• THRESHOLD_QTY — the quantitative threshold value itself; the core business measure of the row.
• UNIT_OF_MEASURE and PRIMARY_UNIT_OF_MEASURE — the UOM in which THRESHOLD_QTY is expressed and the item's primary UOM, used for conversion and validation.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive-flexfield columns, available for customer-specific extensions.
• OBJECT_VERSION_NUMBER — the optimistic-locking column used by the OAF/ADF framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns recording row provenance and change history.

No unique business-key index is documented beyond the surrogate primary key, so QUALITY_THRESHOLD_ID should be treated as the sole guaranteed unique identifier; the combination of organization, item or category, and revision functions as a logical business key but is not enforced as unique in the documented metadata.

Common Use Cases and Queries

Typical usage centers on resolving which threshold applies to an incoming return or repair order. A representative lookup isolates the effective threshold for an item in an organization:

• SELECT quality_threshold_id, threshold_qty, unit_of_measure FROM csd.csd_quality_thresholds_b WHERE inventory_org_id = :org_id AND inventory_item_id = :item_id AND (item_revision = :rev OR item_revision IS NULL);
• Category-level reporting: aggregate THRESHOLD_QTY by ITEM_CATEGORY_ID to review policy coverage across a product line.
• Setup completeness audits: identify inventory items or categories that have no threshold row, or rows where THRESHOLD_QTY or UNIT_OF_MEASURE is null.
• Change auditing: query by LAST_UPDATED_BY and LAST_UPDATE_DATE to determine who last modified a threshold, or join to FND_USER for a readable audit trail.

Because the object is a _B (base) table, any _TL translation table that may accompany it in the CSD schema should be consulted when descriptions or translatable setup text are required, though no such translation table is documented in the supplied metadata.

Related Objects

The documented relationship data records no foreign keys, so CSD_QUALITY_THRESHOLDS_B is standalone and all associations are logical rather than enforced. The most significant related objects are therefore those that supply or consume its key values.

• MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID and organization context; supplies item identity and primary UOM.
• MTL_ITEM_CATEGORIES and MTL_CATEGORIES_B — joined on ITEM_CATEGORY_ID to resolve category names behind category-level thresholds.
• MTL_PARAMETERS / ORG_ORGANIZATION_DEFINITIONS — resolve INVENTORY_ORG_ID to an organization name and code.
• CSD_REPAIRS and CSD_REPAIR_ORDERS — depot repair transactions that logically consume threshold values when evaluating returned quantities.
• CSD_RETURNS or the return-material setup objects in the CSD schema — the operational flow that references threshold policy.
• FND_USER and FND_LOOKUP_VALUES — used respectively for audit resolution and any lookup-backed setup values.
• CSD_QUALITY_THRESHOLDS_PK1 — the primary key constraint itself, relevant when tuning or tracing index usage.

All join columns named above derive from documented column names in CSD_QUALITY_THRESHOLDS_B; the participating tables are identified as the standard EBS owners of those keys and should be validated against the specific instance's data model.