Results for “content_sequence”

50+ results




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

Overview

OKC_SECTION_CONTENTS is a transactional table in the Contracts Core (OKC) module of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. It stores the individual building blocks that make up a contract section, such as a label or an article reference. Where OKC_SECTIONS_B defines the section header and its placement within a contract template or authored document, OKC_SECTION_CONTENTS records the ordered components inside that section, giving the section its actual content and presentation sequence.

The table is owned by the OKC schema and contains 30 documented columns in the 12.2.2 physical schema. Its primary key is OKC_SECTION_CONTENTS_PK on the surrogate ID column. Under the heuristic Data Vault classification mined from its foreign-key structure, the table is best modelled as a link: it resolves the many-to-many style associations between a section and the articles or contract lines it references, rather than holding descriptive attributes of a single business entity. This classification is a modelling suggestion, not an Oracle-declared property.

Key Information Stored

The most significant columns are:

The presence of both the surrogate ID and the (SCN_ID, CONTENT_SEQUENCE) unique key is significant: integrators should treat SCN_ID and CONTENT_SEQUENCE as the natural identity of a content row, since the surrogate ID is not meaningful outside the database.

Common Use Cases and Queries

Reporting on contract section structure is the most frequent use. A typical query joins the section header to its ordered contents:

  • Retrieve section layout: SELECT sc.CONTENT_SEQUENCE, sc.LABEL, sc.CAT_ID, sc.SAE_ID FROM OKC_SECTION_CONTENTS sc WHERE sc.SCN_ID = :section_id ORDER BY sc.CONTENT_SEQUENCE;
  • Identify article-backed versus label-only rows: SELECT * FROM OKC_SECTION_CONTENTS WHERE SCN_ID = :section_id AND CAT_ID IS NOT NULL;
  • Reconcile sections against contract lines: join CLE_ID to OKC_K_LINES_B to confirm which lines appear inside a section.
  • Template analysis: join SCN_ID through OKC_SECTIONS_B to the contract template to enumerate all articles used by a template and their ordering.

Because the table carries the standard WHO and ATTRIBUTE columns, it also supports audit reporting on who last changed a section's layout and DFF-based extension reporting.

Related Objects

OKC_SECTION_CONTENTS sits at the intersection of several Contracts Core objects:

  • OKC_SECTIONS_B — parent section definition; joined via OKC_SECTION_CONTENTS.SCN_ID.
  • OKC_K_ARTICLES_B — contract article instances; joined via CAT_ID.
  • OKC_K_LINES_B — contract lines referenced by a section component; joined via CLE_ID.
  • OKC_STD_ARTICLES_B — standard article definitions; joined via SAE_ID.
  • FND_SECURITY_GROUPS — security group reference; joined via SECURITY_GROUP_ID.
  • OKC_SECTIONS_B, OKC_K_ARTICLES_B and OKC_K_LINES_B collectively form the reference chain used by the Contracts Authoring and Template APIs that generate printed contract documents.

Direct DML against this table should be avoided; changes are normally driven through the Oracle Contracts authoring and template maintenance APIs, which maintain the sequence, version and WHO columns consistently.