Search Results cs_cf_source_cxt_targets

Overview

CS_CF_SOURCE_CXT_TARGETS is a configuration table in the Oracle E-Business Suite Service (CS) module, owned by the CS schema. Its documented purpose is to store the target code or identifier that holds configuration for a particular source code and context. In practical terms, the table acts as a mapping layer within the Service configuration framework: it resolves a given source-plus-context combination to the specific target object whose configuration applies to that combination. This indirection allows Oracle to ship seeded configuration while permitting customer-specific overrides, which is why the table carries parallel SEED_TARGET_VALUE1/2 and CUST_TARGET_VALUE1/2 column sets.

The table is present and valid in both Oracle EBS 12.1.1 and 12.2.2. The 12.2.2 physical schema documents 49 columns, with the primary key CS_CF_SOURCE_CXT_TARGETS_PK on SOURCE_CONTEXT_TARGET_ID. A unique index, CS_CF_SOURCE_CXT_TARGETS_U1, spans SOURCE_CONTEXT_TARGET_ID and ZD_EDITION_NAME. The presence of ZD_EDITION_NAME — the Online Patching (adop) editioning column — confirms the object participates in the 12.2 online patching model and may surface editioned rows across patch cycles.

Based on the mined foreign-key structure, the heuristic Data Vault classification for this table is satellite-leaning. As a modeling suggestion, this means the table behaves as a descriptive, context-dependent attribute store attached to a parent business key rather than as an independent hub of business entities or a pure link between hubs. Its principal parent, via SOURCE_CONTEXT_TYPE_ID, is CS_CF_SOURCE_CXT_TYPES.

Key Information Stored

The most consequential columns are:

• SOURCE_CONTEXT_TARGET_ID — the surrogate primary key and the column referenced by CS_CF_SOURCE_CXT_TARGETS_PK. It is also the leading column of the unique index CS_CF_SOURCE_CXT_TARGETS_U1, making it a business-key candidate alongside the editioning column.
• SOURCE_CONTEXT_TYPE_ID — foreign key to CS_CF_SOURCE_CXT_TYPES; ties each target row to its defining source/context type. This is the primary join path to the parent configuration structure.
• CONTEXT_VALUE1 through CONTEXT_VALUE5 — the context discriminator columns. CONTEXT_VALUE3 carries a documented foreign key to FND_APPLICATION, meaning at least one context slot is used to scope configuration by application.
• SEED_TARGET_VALUE1 and SEED_TARGET_VALUE2 — Oracle-delivered target values retained for reference and upgrade integrity.
• CUST_TARGET_VALUE1 and CUST_TARGET_VALUE2 — customer-defined target values that override or supplement the seeded values.
• OBJECT_VERSION_NUMBER — optimistic locking control used by the OAF/ADF framework.
• ZD_EDITION_NAME — editioning column supporting 12.2 online patching; part of the unique index.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) column set, available for client-specific extensions.
• ADDITIONAL_INFO1–ADDITIONAL_INFO15 — a second, non-DFF extensibility block used by Service configuration logic.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

No natural-key uniqueness beyond the documented unique index should be assumed; the five context values plus SOURCE_CONTEXT_TYPE_ID form the de facto lookup tuple in application logic.

Common Use Cases and Queries

The dominant use case is diagnosing why a particular Service configuration is or is not being applied. Because the table resolves context to a target configuration object, support and implementation teams query it to confirm which target value is active for a given source, context, and application.

A typical diagnostic join retrieves all targets for a source context type:

• SELECT t.SOURCE_CONTEXT_TARGET_ID, t.CONTEXT_VALUE1, t.CONTEXT_VALUE3, t.SEED_TARGET_VALUE1, t.CUST_TARGET_VALUE1 FROM CS_CF_SOURCE_CXT_TARGETS t WHERE t.SOURCE_CONTEXT_TYPE_ID = :type_id;

To identify customer overrides versus seeded values, filter on the CUST_TARGET_VALUE columns being non-null. To resolve the application context, join CONTEXT_VALUE3 to FND_APPLICATION. Reporting scenarios include auditing configuration drift between environments (comparing SEED_TARGET_VALUE against CUST_TARGET_VALUE across instances) and validating that every context combination in CS_CF_SOURCE_CXT_TYPES has a corresponding target row.

In 12.2 environments, queries against this table should account for editioned rows; unqualified queries against _ALL or _V views resolve the edition automatically, whereas base-table access may return rows from multiple editions.

Related Objects

The following objects are most significant to this table:

• CS_CF_SOURCE_CXT_TYPES — parent table joined on CS_CF_SOURCE_CXT_TARGETS.SOURCE_CONTEXT_TYPE_ID = CS_CF_SOURCE_CXT_TYPES.SOURCE_CONTEXT_TYPE_ID. Defines the source and context semantics used by each target row.
• FND_APPLICATION — reference table joined on CS_CF_SOURCE_CXT_TARGETS.CONTEXT_VALUE3 = FND_APPLICATION.APPLICATION_ID, scoping configuration by Oracle application.
• CS_CF_SOURCE_CXT_TARGETS_PK — the primary key constraint on SOURCE_CONTEXT_TARGET_ID.
• CS_CF_SOURCE_CXT_TARGETS_U1 — unique index on (SOURCE_CONTEXT_TARGET_ID, ZD_EDITION_NAME), the edition-aware business-key candidate.

Because implementation and extension code frequently reads this table through the Service configuration APIs rather than by direct SQL, developers should confirm the supported interface for their release before building custom queries. The table is tightly coupled to the broader CS_CF_SOURCE_CXT family of configuration objects, and changes to its data should be made through supported configuration flows to preserve upgrade safety.