Results for “cs_cp_languages”

43 results




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

Overview

CS_CP_LANGUAGES is a child table in the Oracle E-Business Suite Service (CS) module. It records the languages applicable to a customer product, and it is used specifically when Oracle Installed Base is deployed to store and track software products. Each row associates a language with a given customer product definition, allowing the system to represent the multilingual nature of a software product configuration. In Oracle EBS 12.1.1 and 12.2.2 the table resides in the CS schema and carries a VALID status.

From a Data Vault modeling perspective, the metadata classifies this object as satellite-leaning. This is a heuristic derived from its foreign key structure. The table depends on a parent entity (CS_CUSTOMER_PRODUCTS_ALL) and adds descriptive language attributes rather than acting as a standalone hub or a connecting link. Modelers may therefore treat CS_CP_LANGUAGES as a satellite of the customer product hub, recording language detail keyed to that entity.

Key Information Stored

The most significant columns in CS_CP_LANGUAGES are:

  • CP_LANGUAGE_ID — The surrogate primary key, defined by the CS_CP_LANGUAGES_PK constraint. This is the value most commonly searched as "cp_language_id." It uniquely identifies each language row.
  • LANGUAGE_CODE — The business-key candidate for the language. Together with the parent reference, it identifies which language applies.
  • CUSTOMER_PRODUCT_ID — The foreign key to CS_CUSTOMER_PRODUCTS_ALL, linking the language record to its owning customer product.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — Date-range columns that define when the language association is effective, supporting date-effective or temporal querying.
  • SECURITY_GROUP_ID — The foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant and data-access security.
  • OBJECT_VERSION_NUMBER — Used for optimistic locking under the Oracle EBS framework, incremented on each update.
  • LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard WHO columns capturing audit history of who created or updated each row and when.
  • ATTRIBUTE1 through ATTRIBUTE15 and CONTEXT — The standard Oracle EBS descriptive flexfield columns reserved for customer-defined extensions.

The primary key is a surrogate identifier; LANGUAGE_CODE together with CUSTOMER_PRODUCT_ID serves as the meaningful business-key candidate, since a language should be unique within a given product.

Common Use Cases and Queries

Typical use cases include reporting all languages configured for a software product, auditing effective-dated language associations, and validating multilingual product setups during Installed Base implementations. A frequent query pattern resolves the surrogate key value:

  • Lookup by primary key: SELECT cp_language_id, customer_product_id, language_code FROM cs.cs_cp_languages WHERE cp_language_id = :id;
  • Languages for a product: SELECT language_code FROM cs.cs_cp_languages WHERE customer_product_id = :product_id AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);
  • Joining to the parent for descriptions: SELECT l.language_code, p.* FROM cs.cs_cp_languages l JOIN cs.cs_customer_products_all p ON l.customer_product_id = p.customer_product_id;

Because the table is date-effective, queries often filter on START_DATE_ACTIVE and END_DATE_ACTIVE to retrieve only currently active language associations.

Related Objects

The following objects are most significant in relation to CS_CP_LANGUAGES:

  • CS_CUSTOMER_PRODUCTS_ALL — The parent table. Joined via CS_CP_LANGUAGES.CUSTOMER_PRODUCT_ID = CS_CUSTOMER_PRODUCTS_ALL.CUSTOMER_PRODUCT_ID. This is the primary relationship for this satellite table.
  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for data security and access control.
  • CS_CP_LANGUAGES_PK — The primary key constraint on CP_LANGUAGE_ID.
  • Related Installed Base objects maintained by the CS module that consume customer product language configurations, including those surfaced through the customer products and installed base lookup views.

Because the metadata documents only two foreign key relationships, the objects above represent the complete documented dependency set. Additional reachable objects would be traversed transitively through CS_CUSTOMER_PRODUCTS_ALL.