Results for “cs_customer_product_transfer_v”

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

Overview

CS_CUSTOMER_PRODUCT_TRANSFER_V is a database view owned by the APPS schema in Oracle E-Business Suite, registered under the Service (CS) product family. In the ETRM documentation set for Release 12.1.1 and 12.2.2, the object is catalogued with a status of VALID and is described simply as "Customer Products." The naming convention suggests an intended role in the customer product transfer flow — the process by which an installed base instance, serviceable item, or customer product record is moved between owners, accounts, or organizations within Oracle Service.

Despite the functional intent implied by its name, the documented view text is minimal: the view resolves to a single expression, SELECT SYSDATE LAST_UPDATED_DATE FROM DUAL. It therefore does not project any transactional customer product data. Its practical role is limited to providing a timestamp placeholder rather than functioning as a reporting or integration source for transfer records.

Underlying Base Objects

The only documented base object referenced by the view is the DUAL synonym, the standard Oracle single-row utility table. No ETRM-listed dependency exists on CS_INSTALLED_BASE, CS_CUSTOMER_PRODUCTS, or any of the transactional tables normally associated with customer product transfer processing. This is significant: the view carries no join to the installed base, no reference to transfer history tables, and no filter against active or inactive records.

Because the dependency list contains DUAL alone, the view cannot be used to derive customer product attributes, ownership changes, or transfer audit trails. It should be treated as a stub or placeholder object, likely retained for backward compatibility with forms, concurrent programs, or personalizations that expect the view name to resolve, but which no longer rely on its column content.

Key Columns

The view exposes a single documented column:

• LAST_UPDATED_DATE — Defined as SYSDATE at query execution time. It is not sourced from a base table, is not stored, and does not reflect the last modification date of any customer product or transfer record. Each execution returns the current database server date and time.

Notably, the ETRM column listing shows LAST_UPDATE_DATE as the column name in one section while the view text aliases the expression as LAST_UPDATED_DATE. Implementers should verify the actual column name against ALL_TAB_COLUMNS in their specific environment before writing dependent SQL, as the discrepancy between the documented column list and the view text may indicate version drift between 12.1.1 and 12.2.2.

Common Use Cases and Queries

Given the absence of meaningful data columns, the view is not suitable for operational reporting on customer product transfers. Typical legitimate uses are diagnostic and structural:

• Confirming object existence and validity during an upgrade or patch validation.
• Satisfying referential expectations in custom code that historically referenced the view.
• Obtaining a server-side timestamp for lightweight heartbeat or connectivity checks.

A standard query returns one row:

SELECT last_updated_date FROM apps.cs_customer_product_transfer_v;

To inspect the actual definition in a live instance:

SELECT text FROM all_views WHERE view_name = 'CS_CUSTOMER_PRODUCT_TRANSFER_V';

For genuine customer product transfer reporting, consultants should instead query the installed base and service transaction tables delivered by the CS module. The ETRM metadata confirms that CS_CUSTOMER_PRODUCT_TRANSFER_V provides no transfer data and should not be relied upon as a data source.