Search Results cs_cf_source_cxt_targets_u1




Overview

CS.CS_CF_SOURCE_CXT_TARGETS is a configuration repository table in the Oracle E-Business Suite Customer Care (CS) schema. It stores the code or identifier that references the location containing configuration information for a particular source code and context type combination. The physical location referenced by each row varies by source type: when the source type pertains to an individual page, the target references AK_REGIONS; when the source type pertains to a flow, the target references CS_CF_FLOW_PAGES_B. This table therefore acts as the routing map that binds a source-and-context pair to the page or flow that services it.

The table carries 49 documented columns and resides in the APPS_TS_TX_DATA tablespace with PCT Free of 10. Its primary key constraint is CS_CF_SOURCE_CXT_TARGETS_PK, defined on SOURCE_CONTEXT_TARGET_ID. A heuristic Data Vault classification suggests this object is satellite-leaning, meaning it is best modeled as a descriptive satellite attached to the CS_CF_SOURCE_CXT_TYPES hub rather than as an independent hub or link. The presence of the ZD_EDITION_NAME column confirms the object participates in the Oracle EBS 12.2.2 online patching (editioning) architecture, and the unique index CS_CF_SOURCE_CXT_TARGETS_U1 is defined across SOURCE_CONTEXT_TARGET_ID and ZD_EDITION_NAME to guarantee uniqueness within each edition.

Key Information Stored

SOURCE_CONTEXT_TARGET_ID is the surrogate primary key and the single-column basis of the primary key constraint. SOURCE_CONTEXT_TYPE_ID is a foreign key to CS_CF_SOURCE_CXT_TYPES and reuses that table's primary key to map a source code and context type combination. This column, together with the context value columns, forms the business-key candidate represented by the nonunique index CS_CF_SOURCE_CXT_TARGETS_N1 (SOURCE_CONTEXT_TYPE_ID, CONTEXT_VALUE1, CONTEXT_VALUE2, CONTEXT_VALUE3).

Common Use Cases and Queries

The most common query pattern resolves the target location for a given source, context type, and context value combination. Because the customer target overrides the seeded target, reporting should coalesce the two sets of columns.

  • Resolving an effective target: SELECT NVL(CUST_TARGET_VALUE1, SEED_TARGET_VALUE1) FROM CS_CF_SOURCE_CXT_TARGETS WHERE SOURCE_CONTEXT_TYPE_ID = :type_id AND CONTEXT_VALUE1 = :val1;
  • Auditing customized versus seeded configuration by comparing SEED_TARGET_VALUE1/2 against CUST_TARGET_VALUE1/2 to identify rows where a customer override exists.
  • Joining to CS_CF_SOURCE_CXT_TYPES to report the source code and context type labels alongside each configured target.
  • Edition-aware extraction during 12.2.2 patching, filtering on ZD_EDITION_NAME to isolate run-edition versus patch-edition rows.
  • Impact analysis before changing AK_REGIONS or CS_CF_FLOW_PAGES_B content, because those objects are referenced indirectly through the target value columns.

Related Objects

The following objects are the most significant dependencies, derived from the documented foreign keys and reference paths.

  • CS_CF_SOURCE_CXT_TYPES — referenced by SOURCE_CONTEXT_TYPE_ID; the parent that defines the source code and context mapping.
  • FND_APPLICATION — referenced through CONTEXT_VALUE3; supplies application context values.
  • AK_REGIONS — the referenced location when the source type is page-based.
  • CS_CF_FLOW_PAGES_B — the referenced location when the source type is flow-based.
  • CS_CF_SOURCE_CXT_TARGETS_PK — the primary key constraint on SOURCE_CONTEXT_TARGET_ID.
  • CS_CF_SOURCE_CXT_TARGETS_U1 — the unique index on SOURCE_CONTEXT_TARGET_ID and ZD_EDITION_NAME.
  • CS_CF_SOURCE_CXT_TARGETS_N1 — the nonunique index supporting lookup by SOURCE_CONTEXT_TYPE_ID and context values.