Results for “set_order”

2 results




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

Overview

CS_KB_SET_RECS is a Service (CS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores knowledge base set recommendations. It maintains the list of recommended sets or solutions associated with a knowledge base set, allowing support organizations to present ranked, curated solution groupings to agents and end users. The table resides in the CS schema and carries a VALID status in the ETRM repository. Its primary key, CS_KB_SET_RECS_PK, is defined on the SET_REC_ID column, a system-generated surrogate identifier. Because the object captures the associative relationship between a set and the recommendations that belong to it, a Data Vault heuristic classifies it as satellite-leaning: it functions primarily as a descriptive satellite carrying context around a parent set rather than as a standalone hub or a pure many-to-many link.

Key Information Stored

The table exposes 26 documented columns. The most significant include:

  • SET_REC_ID — surrogate primary key (CS_KB_SET_RECS_PK) uniquely identifying each recommendation record.
  • SET_ID — foreign key to CS_KB_SETS_B; identifies the parent knowledge base set that owns the recommendation. This column is also the basis of unique index CS_KB_SET_RECS_U1.
  • SET_ORDER — controls the display or ranking sequence of recommendations within a set; the basis of unique index CS_KB_SET_RECS_U2.
  • SET_NUMBER — the business-facing reference number for the recommendation entry.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing row-level access control across operating units and organizations.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns tracking who created and last modified each row.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS flexfield (descriptive flexfield / DFF) columns available for customer-specific extension without schema changes.

The two unique indexes, CS_KB_SET_RECS_U1 (SET_ID) and CS_KB_SET_RECS_U2 (SET_ORDER), are the documented business-key candidates, meaning a given set and a given order position are each intended to resolve to a single recommendation.

Common Use Cases and Queries

Typical use cases include exposing recommended solutions to agent-facing knowledge tools, ordering recommendations for display, auditing recommendation coverage per set, and reporting on knowledge base content quality. A representative query joining the parent set and security context would read:

  • SELECT r.SET_REC_ID, r.SET_ID, r.SET_NUMBER, r.SET_ORDER FROM CS.CS_KB_SET_RECS r WHERE r.SET_ID = :set_id ORDER BY r.SET_ORDER;
  • SELECT r.SET_REC_ID, s.NAME FROM CS.CS_KB_SET_RECS r, CS.CS_KB_SETS_B s WHERE r.SET_ID = s.SET_ID AND r.SECURITY_GROUP_ID = :group_id;

Because flexfield attributes are available, reporting can also pivot on ATTRIBUTE_CATEGORY and the ATTRIBUTE1–15 columns for site-specific categorization.

Related Objects

  • CS_KB_SETS_B — parent set table; join on CS_KB_SET_RECS.SET_ID = CS_KB_SETS_B.SET_ID.
  • FND_SECURITY_GROUPS — security master; join on CS_KB_SET_RECS.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID.
  • CS_KB_SET_RECS_PK — primary key constraint on SET_REC_ID.
  • CS_KB_SET_RECS_U1 / CS_KB_SET_RECS_U2 — unique indexes on SET_ID and SET_ORDER.
  • Related Knowledge Base objects (such as solution and set-lines tables in the CS_KB family) may reference the same parent set through SET_ID, depending on configuration.