Results for “cs_cp_parameters”

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

Overview

CS_CP_PARAMETERS is a Service (CS) module table owned by the CS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to extend the CS_CUSTOMER_PRODUCTS_ALL table, meaning it stores supplementary or configurable attributes associated with a customer product instance without modifying the base customer product record itself. This extension pattern allows Oracle Service to capture parameter name/value pairs, type classifications, activation ranges, and descriptive flexfield context for each customer product.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification identifies this table as satellite-leaning. In practical terms, CS_CP_PARAMETERS behaves as a dependent child of CS_CUSTOMER_PRODUCTS_ALL: its rows describe attributes that qualify a parent customer product, and it should not be treated as an independent hub of business identity. The table carries a single-column surrogate primary key, CP_PARAMETER_ID, enforced by the CS_CP_PARAMETERS_PK constraint and mirrored by the unique index CS_CP_PARAMETERS_U1.

Key Information Stored

The following columns from the documented 33-column schema are the most significant for understanding and querying this table:

• CP_PARAMETER_ID — Surrogate primary key uniquely identifying each parameter row.
• CUSTOMER_PRODUCT_ID — Foreign key to CS_CUSTOMER_PRODUCTS_ALL; ties each parameter to its parent customer product.
• PARAMETER_TYPE — Classification of the parameter, allowing multiple parameter categories per product.
• NAME — The parameter's identifying name.
• VALUE — The parameter's stored value.
• STATUS — Lifecycle state of the parameter record.
• APPLICATION_ID — Identifies the owning application context.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective date range controlling when the parameter is valid.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-org/security-group data isolation.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework during concurrent updates.
• CONTEXT — Descriptive flexfield context segment.
• ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield segment columns for extensible, customer-defined attributes.
• MIGRATED_STATUS_FLAG — Indicator of migration state for the record.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard WHO-column auditing.

The only documented unique index is CS_CP_PARAMETERS_U1 on CP_PARAMETER_ID, which mirrors the primary key rather than constituting an independent business key. No natural business-key unique constraint is documented.

Common Use Cases and Queries

Because CS_CP_PARAMETERS extends customer product data, it is most often queried in the context of a specific customer_product_id to retrieve all configured parameters. A typical retrieval pattern is:

• SELECT cp_parameter_id, parameter_type, name, value, status, start_date_active, end_date_active FROM cs_cp_parameters WHERE customer_product_id = :p_id AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE));
• Reporting by parameter type: group and count records by PARAMETER_TYPE where STATUS is active to inventory configured parameters across products.
• Security-scoped extracts: filter on SECURITY_GROUP_ID for multi-org reporting and data-isolation compliance.
• Flexfield reporting: query CONTEXT and ATTRIBUTE1–15 for customer-specific extension data.
• Change auditing: order by LAST_UPDATE_DATE to identify recently modified parameter configurations.

Related Objects

The documented relationships anchor this table to the following objects:

• CS_CUSTOMER_PRODUCTS_ALL — Parent table; joined on CS_CP_PARAMETERS.CUSTOMER_PRODUCT_ID = CS_CUSTOMER_PRODUCTS_ALL.CUSTOMER_PRODUCT_ID.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for security-group scoping.
• CS_CP_PARAMETERS_PK — Primary key constraint on CP_PARAMETER_ID.
• CS_CP_PARAMETERS_U1 — Unique index on CP_PARAMETER_ID.
• Service (CS) application APIs — Customer product creation and update APIs in the CS module typically insert and maintain parameter rows alongside the parent product record, making CS_CP_PARAMETERS a secondary target of those transactions.

Together these objects position CS_CP_PARAMETERS as a dependent extension of customer product data, best joined through CUSTOMER_PRODUCT_ID and scoped by SECURITY_GROUP_ID.