Results for “okc_line_style_roles”

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

Overview

OKC_LINE_STYLE_ROLES is a configuration table in the Oracle Contracts Core (OKC) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It defines the set of party roles that may be associated with a contract line of a given line style. In other words, it acts as a validation and control matrix: for each line style defined in OKC_LINE_STYLES_B, the table records which subclass roles (party roles) are permissible on contract lines using that style. This controls which parties — such as customer, supplier, contact, or internal party — can be attached to individual contract lines during authoring, and it underpins the role-selection lists presented in the Contracts authoring UI.

Under the heuristic Data Vault classification derived from its foreign key structure, this object is best modelled as a link table. It resolves a many-to-many relationship between line styles and subclass roles, holding no descriptive attributes of its own beyond administrative and multi-tenant columns. This is consistent with its pure association semantics: it does not describe either parent entity, it merely asserts that a permitted pairing exists.

Key Information Stored

The table is narrow by design, comprising eleven documented columns. The most significant are:

• LSE_ID — Foreign key to OKC_LINE_STYLES_B, identifying the line style for which permitted roles are being defined.
• SRE_ID — Foreign key to OKC_SUBCLASS_ROLES, identifying the party role permitted on lines of that style.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Framework (OAF) to detect concurrent updates.
• SECURITY_GROUP_ID — Supports multi-tenant / operating unit security; foreign key to FND_SECURITY_GROUPS.
• ACCESS_LEVEL — Governs the access privileges applied to the row within the security model.
• ZD_EDITION_NAME — Editioning column supporting Online Patching (EDITION) in 12.2.x; participates in the unique index.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording insert and update provenance and the login session.

The surrogate primary key is OKC_LINE_STYLE_ROLES_PK, defined on the composite (LSE_ID, SRE_ID). A second unique index, OKC_LINE_STYLE_ROLES_U1, adds ZD_EDITION_NAME to that pair — this is the business-key candidate ensuring a role is permitted only once per style per edition. Note that LSE_ID and SRE_ID are foreign keys, not standalone surrogates; the composite forms the natural business key.

Common Use Cases and Queries

Typical usage involves listing roles available for a style, validating a role assignment during contract line creation, and auditing configuration. A representative query retrieves permitted roles for a style:

SELECT lse_id, sre_id
FROM   okc_line_style_roles
WHERE  lse_id = :p_line_style_id;

Joining to parents yields readable output:

SELECT lsb.name line_style, scr.role_name
FROM   okc_line_style_roles lsr,
       okc_line_styles_b lsb,
       okc_subclass_roles scr
WHERE  lsr.lse_id = lsb.lse_id
AND    lsr.sre_id = scr.sre_id;

Reporting scenarios include identifying line styles with no permitted roles (possible configuration gaps), comparing role coverage across styles, and bulk-loading permitted roles when implementing new line styles. In 12.2.x, queries must be edition-aware; unqualified queries resolve against the current edition via the editioning view.

Related Objects

• OKC_LINE_STYLES_B — parent line-style definition; join on LSE_ID.
• OKC_SUBCLASS_ROLES — party role definitions; join on SRE_ID.
• FND_SECURITY_GROUPS — security grouping reference via SECURITY_GROUP_ID.
• OKC_LINE_STYLES_TL — translatable line-style names for reporting.
• OKC_LINE_STYLE_ROLES editioning view (12.2.x) — the edition-aware access path.
• Contracts authoring APIs (OKC authoring/party-role APIs) — consume these permitted-role records when validating line-level party assignments.