Results for “ecn_code”

4 results




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

Overview

The CZ_CONSTRAINT_ASSIGNMENTS_V view is a reporting and integration object within the Oracle E-Business Suite Bills of Material (BOM) module. It exposes constraint assignment data used by Oracle Configurator (formerly the Configurator/Configurator Object module, denoted by the CZ prefix) to govern how configuration constraints are applied to assemblies, systems, and items during model and option selection. The view flattens the relationship between a constraint definition and the assignment that binds that constraint to a particular item, organization, or system type, while joining descriptive lookup values so that codes are presented alongside their user-facing meanings.

Because the underlying tables store numeric codes for constraint groups, constraint types, and system types, consumers of the view receive human-readable meanings from FND_COMMON_LOOKUPS without needing to resolve those lookups themselves. This makes the view a convenient source for custom reports, extracts, and interfaces that need to describe configuration rules in business terms rather than internal identifiers. The ETRM metadata notes the object as "Not implemented in this database," meaning it is shipped as a database view definition but is created only where the relevant Configurator schema objects exist; its presence is typical of a fully configured 12.1.1 or 12.2.2 instance.

Underlying Base Objects

The view is defined over a small set of core Configurator and shared EBS objects:

All item and most lookup joins are outer joins, so assignments that reference no item or an unresolved code still appear. The documented metadata lists no referenced base objects, so the relationships above are inferred from the view's SQL text.

Key Columns

The REVENUE_FLAG column, the term searched, is exposed directly from CZ_CONSTRAINT_ASSIGNMENTS and indicates whether the assignment influences revenue recognition logic during configuration.

Common Use Cases and Queries

Typical uses include auditing which constraints apply to a given item, reporting configuration rules by group, and filtering assignments that affect revenue or pricing. A representative query follows:

SELECT ASSIGNMENT_ID, CONSTRAINT_NAME, CONSTRAINT_TYPE, ASSEMBLY_ITEM_NAME, ORGANIZATION_ID, REVENUE_FLAG, PRICE_FLAG, EFFECTIVITY_DATE, DISABLE_DATE FROM CZ_CONSTRAINT_ASSIGNMENTS_V WHERE INVENTORY_ITEM_ID = :item_id AND ORGANIZATION_ID = :org_id AND NVL(REVENUE_FLAG,'N') = 'Y';

Analysts also group results to summarize rule counts: SELECT CONSTRAINT_GROUP_NAME, CONSTRAINT_TYPE, COUNT(*) FROM CZ_CONSTRAINT_ASSIGNMENTS_V GROUP BY CONSTRAINT_GROUP_NAME, CONSTRAINT_TYPE. Because the view carries rowid and audit columns, it supports both read-only reporting and lightweight integration extracts.