Results for “aso_line_attribute_status”

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

Overview

CS_CP_PARAMETERS_V is an APPS-owned Oracle E-Business Suite view that exposes customer product parameters recorded in the Customer Product (CS_CP_PARAMETERS) entity while enriching each row with decoded lookup meanings. In EBS 12.1.1 and 12.2.2, the view is defined in the APPS schema and is accessible to any reporting or integration component with appropriate grants. Its principal role is to present parameter records in a business-readable form: rather than returning opaque lookup codes for parameter_type and status, the view joins to ASO_LOOKUPS twice to surface human-readable values (PARAMETER_TYPE_MEANING and STATUS_MEANING). This makes CS_CP_PARAMETERS_V a natural reporting source for customer product configuration and attribute assignment, particularly in Order Management, Advanced Pricing, and Service Contract contexts where line-level attribute types are governed by lookup values.

Underlying Base Objects

The view is defined over two documented referenced objects:

• CS_CP_PARAMETERS (SYNONYM) — The driving table, aliased PARM in the view definition. It supplies every column except the two decoded meanings.
• ASO_LOOKUPS (VIEW) — Referenced twice in an outer-join configuration, as LK1 and LK2. LK1 decodes PARAMETER_TYPE against lookup_type 'ASO_LINE_ATTRIBUTE_TYPE'; LK2 decodes STATUS against lookup_type 'ASO_LINE_ATTRIBUTE_STATUS'.

Because both lookup joins use the Oracle outer-join operator (+), rows from CS_CP_PARAMETERS are preserved even when no matching lookup row exists. In those cases the meaning columns return NULL, while the raw codes remain available in parameter_type and status. This is significant for the search term "aso_line_attribute_type": the string ASO_LINE_ATTRIBUTE_TYPE does not appear as a column or value on the base table — it is the lookup_type filter applied to ASO_LOOKUPS. Consequently, any query or report that resolves aso_line_attribute_type semantics must reference this view or replicate its join logic.

Key Columns

• cp_parameter_id — Primary key of the underlying parameter record; unique identifier for the parameter row.
• customer_product_id — Foreign key linking the parameter to its parent customer product record; the primary join path for product-centric reporting.
• parameter_type — The raw lookup code classified under lookup_type ASO_LINE_ATTRIBUTE_TYPE.
• parameter_type_meaning — The decoded, user-facing name for parameter_type; populated only when a matching ASO_LOOKUPS row exists.
• name / value — The parameter's identifying name and assigned value.
• status / status_meaning — The raw status code (lookup_type ASO_LINE_ATTRIBUTE_STATUS) and its decoded meaning.
• start_date_active / end_date_active — Effective dating range for the parameter.
• attribute1 – attribute15, context — Descriptive flexfield segments carried through from the base table.
• Audit columns — last_updated_by, last_update_date, created_by, creation_date, last_update_login, application_id.

Common Use Cases and Queries

Typical usage is reporting on parameter assignments for a given customer product while displaying business-friendly type and status labels. A representative query filtering by a specific type meaning is:

• SELECT cp_parameter_id, customer_product_id, name, value, parameter_type_meaning, status_meaning FROM cs_cp_parameters_v WHERE parameter_type = 'SOME_CODE';
• SELECT customer_product_id, parameter_type_meaning, COUNT(*) FROM cs_cp_parameters_v GROUP BY customer_product_id, parameter_type_meaning;
• SELECT * FROM cs_cp_parameters_v WHERE status_meaning = 'Active' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE+1);

Analysts building integrations or custom reports referencing aso_line_attribute_type should query this view and join on customer_product_id rather than querying CS_CP_PARAMETERS directly, since the view already encapsulates the required lookup resolution against ASO_LINE_ATTRIBUTE_TYPE.