Search Results okc_rules_b_n1

Overview

OKC.OKC_RULES_B is the base table that stores RULES within the Oracle E-Business Suite Contracts (OKC) module. A RULE is a structured, machine-readable representation of free-format text originally contained in an ARTICLE. Where an ARTICLE captures contractual language in prose form, a RULE distills that language into discrete data elements that automated processes can act upon. RULES are used to inform downstream functions — billing, pricing, fulfillment, renewals, and terms enforcement — that execute against contract data.

Rules are deliberately atomic. A single rule does not carry all the information required to bill a contract; instead, related rules are bundled into a RULE GROUP, and each individual rule in the group describes one facet of the requirement, such as the payment term or the bill-to address. Rule attributes are held using developer flexfields, and the definitions governing those categories and attributes reside in the standard flexfield tables, which must not be modified. Notably, a RULE is conceptually derived from an ARTICLE, but the article need not physically exist on the contract — supporting scenarios such as boilerplate contracts where storing the originating article per instance offers little value.

The heuristic Data Vault classification for this object is hub-leaning, mined from its foreign key structure. This suggests modeling OKC_RULES_B as a hub entity keyed on its surrogate identifier, with the surrounding foreign keys and descriptors contributing satellite and link characteristics as the warehouse model is refined.

Key Information Stored

The table is defined in the OKC schema and resides in the APPS_TS_TX_DATA tablespace with 60 documented columns. Its physical anchor is the surrogate primary key ID, which is also carried on the unique index OKC_RULES_B_U1 in the APPS_TS_TX_IDX tablespace; this index represents the primary business-key candidate.

• ID — surrogate primary key and the target of every incoming rule relationship.
• RGP_ID — foreign key to OKC_RULE_GROUPS_B identifying the rule group to which the atomic rule belongs; the primary grouping mechanism.
• DNZ_CHR_ID — the contract identifier that scopes the rule to its governing document; indexed by OKC_RULES_B_N1 for contract-level retrieval.
• OBJECT1_ID1, OBJECT2_ID1, OBJECT3_ID1 — up to three foreign key references to external objects such as payment terms or price lists. Each is individually indexed (N1 through N7 variants) along with their companion JTOT_OBJECTx_CODE columns, which identify the referenced entity type via JTF_OBJECTS_B.
• RULE_INFORMATION_CATEGORY and RULE_INFORMATION1–15 — the developer flexfield context and its fifteen attribute slots holding rule semantics; indexed by OKC_RULES_B_N4 and OKC_RULES_B_N3 for category and attribute-based lookups.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the descriptive flexfield context and slots used for extensibility.
• STD_TEMPLATE_YN and TEMPLATE_YN — flags indicating whether the rule functions as a standard template.
• WARN_YN, PRIORITY, and DISPLAY_SEQUENCE — control flags governing rule evaluation and presentation ordering.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS supporting multi-tenant data isolation.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the concurrent framework.

Common Use Cases and Queries

Typical uses include retrieving all rules for a contract, resolving rules within a rule group, and locating rules that reference a specific external object such as a payment term.

• Contract-scoped rule listing: SELECT ID, RGP_ID, RULE_INFORMATION_CATEGORY FROM OKC.OKC_RULES_B WHERE DNZ_CHR_ID = :p_contract_id leverages OKC_RULES_B_N1.
• Rule group expansion: SELECT ID FROM OKC.OKC_RULES_B WHERE RGP_ID = :p_rgp_id uses OKC_RULES_B_N2.
• External object resolution: SELECT ID, JTOT_OBJECT1_CODE FROM OKC.OKC_RULES_B WHERE OBJECT1_ID1 = :p_object_id uses OKC_RULES_B_N5.
• Flexfield attribute filtering: join to FND flex tables on RULE_INFORMATION_CATEGORY when reporting on category-specific attributes.
• Template identification: filter on STD_TEMPLATE_YN or TEMPLATE_YN when generating contracts from standard boilerplate.

Related Objects

• OKC_RULE_GROUPS_B — parent of the RGP_ID foreign key; groups atomic rules into functional bundles.
• JTF_OBJECTS_B — referenced via JTOT_OBJECT1_CODE, JTOT_OBJECT2_CODE, and JTOT_OBJECT3_CODE, defining the three external object references.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for data security.
• OKC_ARTICLE_TRANS — references RUL_ID back to OKC_RULES_B, linking rules to article translations.
• OKL_ANSWERS — references RUL_ID, connecting lease answer data to rules.
• OKS_LEVEL_ELEMENTS — references RUL_ID for service-level rule elements.
• OKC_COVER_TIMES and OKC_REACT_INTERVALS — reference RUL_ID for coverage and reaction interval rules.
• OKL_OVD_RUL_TMLS — references RUL_ID for overdue rule templates.