Search Results cs_tp_freetexts_u1

Overview

CS.CS_TP_FREETEXTS is a configuration seed table in the Oracle E-Business Suite Customer Support (CS) schema. It supports the Template Driven Service Request (SR) framework, specifically the "freetext" answer type. When a template-driven SR answer is defined to accept free-form text rather than a coded lookup value, an entry in this table governs how much text the answer field permits. The row associates a freetext definition with a lookup value and records the permitted text size, effectively acting as a metadata table that drives field length behavior at runtime in the SR capture and answer-rendering UI.

Because the table holds declarative configuration rather than transactional history, it is typically small and seeded or maintained by administrators rather than by end users. In ETRM 12.2.2 the object is documented as VALID with 25 columns, owned by the CS schema, and stored in the APPS_TS_SEED tablespace — a tablespace convention that confirms its role as seed/reference data shipped with the application. Under a heuristic Data Vault classification, this object is best modeled as a satellite (a descriptive attribute set) rather than a hub or link: it carries no natural business identifier beyond its surrogate key and its business meaning is conveyed through descriptive attributes such as FREETEXT_SIZE and the lookup association. Consult the FK structure if stricter classification is required; the documented dependency set is effectively standalone.

Key Information Stored

The most significant columns and their roles are:

• FREETEXT_ID — the surrogate primary key for the freetext configuration record. It is enforced by the primary key constraint CS_TP_FREE_PK and by the unique index CS_TP_FREETEXTS_U1. This is the object's deterministic identifier.
• LOOKUP_ID — associates the freetext record with a lookup value; indexed non-uniquely by CS_TP_FREETEXTS_N1, so multiple freetext rows may share a lookup.
• FREETEXT_SIZE — the permitted size of the free-text answer. This is the operational payload of the row and the value consumed by the template-driven answer logic.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Who columns that audit row creation and modification.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield (DFF) container. ATTRIBUTE_CATEGORY defines the flexfield structure, and the numbered segments hold customer-specific or functional extensions without schema change.
• SECURITY_GROUP_ID — included for hosted (multi-tenant) environments and documented as referencing FND_SECURITY_GROUPS.

Note that FREETEXT_ID is the unique business-key candidate; LOOKUP_ID is deliberately non-unique, indicating a one-to-many relationship between lookup values and freetext definitions.

Common Use Cases and Queries

Typical uses center on configuration review and reporting. Administrators verify the configured freetext size for a given lookup, and developers join to lookup tables to render descriptive answers. Sample patterns:

• Resolve a freetext definition to its lookup meaning: join CS_TP_FREETEXTS to FND_LOOKUP_VALUES on LOOKUP_ID (or the appropriate lookup foreign key) to display the lookup meaning alongside FREETEXT_SIZE.
• Audit configuration changes: query CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE and LAST_UPDATED_BY to identify when a freetext size was altered and by whom.
• Extract DFF usage: report ATTRIBUTE_CATEGORY and populated ATTRIBUTE1–ATTRIBUTE15 segments for configuration analysis.
• Multi-tenant filtering: include SECURITY_GROUP_ID predicates when querying in a hosted environment to isolate tenant-specific configuration.
• Referential integrity checks: use the new primary key and unique index to detect orphan or duplicate freetext definitions and to confirm one-to-many linkage across LOOKUP_ID values.

Related Objects

The documented dependencies and closely associated objects are:

• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; join on SECURITY_GROUP_ID/SECURITY_GROUP_ID for hosted-environment tenancy.
• CS_TP_FREETEXTS_U1 — the unique index on FREETEXT_ID (the searched artifact) supporting the primary key.
• CS_TP_FREE_PK — the primary key constraint on FREETEXT_ID.
• CS_TP_FREETEXTS_N1 — the non-unique index on LOOKUP_ID used for lookup-driven access paths.
• Template Driven SR answer/lookup tables in the CS schema — the template answer configuration tables that consume LOOKUP_ID and FREETEXT_SIZE to render freetext answer types.
• FND_LOOKUPS / FND_LOOKUP_VALUES — the standard lookup framework objects used to resolve LOOKUP_ID into a shareable business meaning for reporting.