Search Results original_start_date

Overview

CS_CP_SERVICES is an Oracle E-Business Suite 12.1.1 / 12.2.2 view owned by the APPS schema and registered under the CS (Service) product family. Its published description is "All services assigned to customer products," meaning it exposes the service lines that are attached to a customer product record — for example, warranty, extended warranty, or support services sold alongside an installed base item. The view is a reportable, security-filtered projection of the underlying service data, and it is the object referenced by ETRM documentation as the source for service coverage, billing, preventive maintenance (PM), and pricing attribute data associated with customer products.

The view carries a large attribute footprint. In addition to core service identifiers it exposes the full pricing attribute set (PRICING_ATTRIBUTE1 through PRICING_ATTRIBUTE15), the fifteen descriptive ATTRIBUTE columns, and the descriptive flexfield CONTEXT column. This is why the object surfaces in searches for "pricing_attribute15": that column is one of the fifteen seeded pricing attributes available for contract and service pricing configuration. Analysts and integrators querying this view typically do so to reconcile service coverage, billing schedules, and pricing context without joining to additional pricing entities.

Underlying Base Objects

The view is defined over a single documented base object, CS_CP_SERVICES_ALL, exposed in the APPS schema as a synonym. CS_CP_SERVICES_ALL is the multi-org (Operating Unit) enabled table holding service records across organizations. The view applies a runtime filter to enforce operating unit security: it evaluates the ORG_ID column against the CLIENT_INFO session context, using NVL and DECODE logic so that records matching the caller's active organization (or records with a NULL ORG_ID) are returned. Records belonging to other operating units are excluded. Effectively, CS_CP_SERVICES is the MOAC-compliant, single-organization-aware layer through which CS Service forms, reports, and integrations read service line information.

Key Columns

• CP_SERVICE_ID — Primary key of the service record.
• CUSTOMER_PRODUCT_ID — The customer product (installed base instance) to which the service is attached.
• SERVICE_INVENTORY_ITEM_ID / SERVICE_MANUFACTURING_ORG_ID — Identifies the service item and manufacturing organization.
• START_DATE_ACTIVE / END_DATE_ACTIVE / ORIGINAL_START_DATE / ORIGINAL_END_DATE — Service coverage window including original terms.
• STATUS_CODE — Current status of the service line.
• INVOICE_FLAG, INVOICE_COUNT, CURRENCY_CODE, CONVERSION_RATE, TAX_CODE, LIST_PRICE, EXTENDED_PRICE, PRICE_PERCENT, DISCOUNT_ID — Billing and pricing controls for the service.
• BILLING_FREQUENCY_PERIOD, FIRST_BILL_DATE, NEXT_BILL_DATE, BILL_ON — Recurring billing schedule attributes.
• PRICING_ATTRIBUTE1 … PRICING_ATTRIBUTE15 — Pricing descriptive flexfield attribute segments; PRICING_ATTRIBUTE15 is the fifteenth of these and is commonly used for customer-specific pricing qualifiers.
• PRICING_CONTEXT — The pricing DFF context that determines which attributes are active.
• ATTRIBUTE1 … ATTRIBUTE15, CONTEXT — The generic descriptive flexfield segments and context for the service line.
• WARRANTY_FLAG, PRORATE_FLAG, PM_SCHEDULE_FLAG — Flags governing warranty treatment, proration, and preventive maintenance.
• NEXT_PM_VISIT_DATE, PM_VISITS_COMPLETED, LAST_PM_VISIT_DATE, CURRENT_MAX_SCHEDULE_DATE — Preventive maintenance scheduling data.
• CONTRACT_ID, CONTRACT_LINE_STATUS_ID, ORIGINAL_SERVICE_LINE_ID, ORIGINAL_SYSTEM_LINE_REFERENCE — Contract linkage and origin tracking.
• ORG_ID — Operating unit, used by the view's security predicate.

Common Use Cases and Queries

Typical uses include reporting active service coverage per installed base item, extracting billing schedules for interfaces, and retrieving pricing attribute values — notably PRICING_ATTRIBUTE15 — for pricing integration or audit. A representative query for services priced by a specific attribute segment is:

• SELECT cp_service_id, customer_product_id, service_inventory_item_id, status_code, pricing_attribute15, pricing_context, extended_price FROM cs_cp_services WHERE org_id = :p_org_id AND status_code = 'ACTIVE' ORDER BY customer_product_id;
• SELECT c.cp_service_id, c.start_date_active, c.end_date_active, c.next_bill_date, c.billing_frequency_period FROM cs_cp_services c WHERE c.customer_product_id = :p_customer_product_id AND SYSDATE BETWEEN c.start_date_active AND c.end_date_active;

Because the view applies the operating unit predicate automatically, callers need not add an explicit ORG_ID filter, though supplying one (as above) keeps queries explicit and index-friendly. Joins to CS_CP_SERVICES_ALL are unnecessary and, given the security filter, undesirable when the caller intends only the current organization's data.