Results for “std_template_yn”

50+ results




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

Overview

OKS_RULES_DFF is a table in the OKS schema (Service Contracts module) of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. Its description — "Contracts Rule Definitions table — rules striped" — reflects its purpose: it stores the definition records that determine how Oracle Service Contracts rule groups and rule templates are applied during contract authoring and processing. The table is part of the OKS rule engine, which governs pricing, coverage, entitlement, warning, and validation behavior for service contract lines.

From a Data Vault modeling perspective, the metadata suggests a link classification. The table's foreign keys target multiple independent reference entities — JTF_OBJECTS_B (object context codes) and OKC_RULE_GROUPS_B (rule groups) — and the table carries descriptive and operational attributes alongside those references. This pattern is characteristic of a link table bridging rule groups, object contexts, and contract-specific rule instances, rather than a pure hub or a satellite holding only descriptive changes over time.

Key Information Stored

The table contains 59 columns. The surrogate primary key is ID, which is enforced by the unique index OKS_RULES_DFF_U1 (also documented as OKS_RULES_B_PK). The most significant columns include:

Common Use Cases and Queries

Typical reporting scenarios include identifying all rule definitions attached to a given rule group, tracing which object types a contract rule references, and auditing warning or priority settings. A standard pattern joins OKS_RULES_DFF to OKC_RULE_GROUPS_B and to JTF_OBJECTS_B three times (once per object slot):

  • Join OKS_RULES_DFF.RGP_ID = OKC_RULE_GROUPS_B.ID to resolve rule group names.
  • Join JTOT_OBJECT1_CODE, JTOT_OBJECT2_CODE, and JTOT_OBJECT3_CODE to JTF_OBJECTS_B.JTOT_OBJECT_CODE to resolve object type descriptions.
  • Filter on DNZ_CHR_ID to isolate rules for a specific contract.
  • Filter on SECURITY_GROUP_ID for multi-org security reporting.

Common uses include rule engine troubleshooting, contract template analysis, and migration validation when moving rule definitions between environments via FNDLOAD or similar utilities.

Related Objects

  • JTF_OBJECTS_B — referenced three times via JTOT_OBJECT1_CODE, JTOT_OBJECT2_CODE, and JTOT_OBJECT3_CODE; defines the object type context for each rule slot.
  • OKC_RULE_GROUPS_B — referenced via RGP_ID; the parent rule group owner.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; enforces data security.
  • OKS_RULES_TL — translation table providing rule names and descriptions (related by ID).
  • OKS_RULES_B — base rules table associated with the DFF stripe (via OKS_RULES_B_PK).
  • OKC_CONTRACTS_ALL / OKC_K_HEADERS_B — parent contract headers referenced through DNZ_CHR_ID.

Because the user search term "jtf_objects_b" appears directly among these foreign key relationships, OKS_RULES_DFF is a key consumer of JTF_OBJECTS_B for defining the object context of service contract rules.