Results for “oks_k_headers_b”

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

Overview

OKS_K_HEADERS_B is the Service Contracts header attributes table in the Oracle E-Business Suite (EBS) OKS module, which manages service contracts, warranties, and subscription agreements. In Release 12.1.1 and 12.2.2, this table stores the extended, service-specific attribute set for a contract header — the record that carries billing, renewal, tax, credit card, electronic renewal, and accounts receivable interface settings for a service contract. The table resides in the OKS schema and holds 88 documented columns.

Structurally, OKS_K_HEADERS_B is a satellite of the core contracts header table OKC_K_HEADERS_B, joined through the CHR_ID column (contract header identifier). The core OKC_K_HEADERS_B stores the general contract identity — number, dates, status, parties — while OKS_K_HEADERS_B stores the supplemental service-contract-specific attributes that only apply when the contract is processed by the OKS module. This one-to-one relationship is enforced by the unique index OKS_K_HEADERS_B_U2 on CHR_ID. From a Data Vault modeling perspective, this table is heuristically classified as satellite-leaning: it hangs directly off a single parent key (CHR_ID) and carries descriptive, time-stamped attributes rather than representing an independent business entity or many-to-many association.

Key Information Stored

The table carries one surrogate primary key, ID, enforced by the OKS_K_HEADERS_B_PK constraint. Two unique indexes exist: OKS_K_HEADERS_B_U1 on ID and OKS_K_HEADERS_B_U2 on CHR_ID, making CHR_ID the principal business-key candidate — it is the foreign key to OKC_K_HEADERS_B and defines the one-to-one nature of the relationship.

• CHR_ID — contract header identifier; links to OKC_K_HEADERS_B. The dominant business key.
• ACCT_RULE_ID — accounting rule applied to the service contract.
• PAYMENT_TYPE, CC_NO, CC_EXPIRY_DATE, CC_BANK_ACCT_ID, CC_AUTH_CODE, CC_EMAIL_ADDRESS — credit card and payment handling attributes.
• TAX_AMOUNT, TAX_STATUS, TAX_CODE, TAX_EXEMPTION_ID, TAX_CLASSIFICATION_CODE, EXEMPT_CERTIFICATE_NUMBER, EXEMPT_REASON_CODE — tax determination and exemption data.
• BILLING_PROFILE_ID, BILLING_SCHEDULE_TYPE, INV_TRX_TYPE, INV_PRINT_PROFILE, AR_INTERFACE_YN, HOLD_BILLING, SUMMARY_TRX_YN — billing and invoicing configuration for the contract.
• RENEWAL_STATUS, ELECTRONIC_RENEWAL_FLAG, RENEWAL_PO_REQUIRED, RENEWAL_PO_NUMBER, RENEWAL_PRICE_LIST, RENEWAL_PRICING_TYPE, RENEWAL_MARKUP_PERCENT, RENEWAL_GRACE_DURATION, RENEWAL_GRACE_PERIOD, RENEWAL_COMMENT — renewal control parameters.
• COMMITMENT_ID — link to PON_OFFER_COMMITMENTS for procurement commitment integration.
• TRXN_EXTENSION_ID — reference to IBY_FNDCPT_TX_EXTENSIONS for payment transaction extensions.
• SECURITY_GROUP_ID — multi-org / security grouping reference to FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OA Framework/ADF layer.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROCESS_REQUEST_ID, WF_ITEM_KEY.

The _USED columns (for example RENEWAL_PRICE_LIST_USED, BILLING_PROFILE_USED, ERN_FLAG_USED_YN) act as snapshots recording which configuration was actually applied when the contract was finalized, complementing the _ID or configurable columns that hold current values.

Common Use Cases and Queries

Because OKS_K_HEADERS_B is a satellite of OKC_K_HEADERS_B, most reporting joins the two on CHR_ID to present a complete contract profile. A typical pattern retrieves contract number and status from the core table alongside billing and renewal settings:

• Fetching a contract’s billing profile and AR interface flag for receivable reconciliation.
• Reporting renewal exposure: contracts nearing expiration with ELECTRONIC_RENEWAL_FLAG = 'Y' and a configured RENEWAL_PRICE_LIST.
• Tax exemption audits using TAX_EXEMPTION_ID, EXEMPT_CERTIFICATE_NUMBER, and EXEMPT_REASON_CODE.
• Locating contracts tied to a procurement commitment via COMMITMENT_ID.
• Credit card processing checks for service contracts that capture payment details.

A representative query joins OKS_K_HEADERS_B to OKC_K_HEADERS_B on CHR_ID and filters by RENEWAL_STATUS or billing attributes. For API-driven work, service contract creation and update flows populate this row automatically; direct DML is discouraged in favor of the OKS public APIs.

Related Objects

The following objects reference or are referenced by OKS_K_HEADERS_B through documented foreign keys and primary/unique index relationships:

• OKC_K_HEADERS_B — core contract header; joined via OKS_K_HEADERS_B.CHR_ID = OKC_K_HEADERS_B.ID.
• PON_OFFER_COMMITMENTS — referenced by COMMITMENT_ID for procurement commitments.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for security grouping.
• IBY_FNDCPT_TX_EXTENSIONS — referenced by TRXN_EXTENSION_ID for payment transaction extensions.
• OKS_K_HEADERS_B_PK / U1 / U2 — primary and unique constraints on ID and CHR_ID that enforce row identity and the one-to-one link to the core header.

Downstream, this table feeds the OKS service contracts UI and the billing/invoice generation process, meaning changes to billing, renewal, or tax attributes here propagate directly into downstream invoicing, renewal, and AR interface transactions.