Search Results okc_k_headers_b_s




Overview
Explore in AI Chat

Overview

OKS_IMPORT_INSERT is a PL/SQL package body owned by the APPS schema that supports the bulk import of service contract data into Oracle E-Business Suite's Service Contracts (OKS) and Contracts Core (OKC) data model. The package serves as the insert stage of the contract import pipeline: after staging tables have been populated and validated, OKS_IMPORT_INSERT performs the physical creation of contract header, line, party-role, governance, contact, process, and usage-counter records. Its central role is bridging the interface staging area (OKS_INT_* tables) with the base contract tables such as OKC_K_HEADERS_B, OKC_K_LINES_B, and OKS_K_HEADERS_B. The package is classified as an internal utility API (classification OTHER) rather than a public user-facing API such as OKS_IMPORT_PUB or the OKC Contract Management APIs, and it is invoked through the Service Contracts import process rather than directly by end users.

Key Procedures and Functions

The documented package exposes a single procedure, INSERT_CONTRACTS. Although the ETRM metadata does not disclose its parameter list, its purpose is to move validated contract data from the temporary/interface staging tables into the permanent OKS and OKC base tables. Invocation is normally performed once per import run after the staging rows have passed validation, typically within the same database transaction as the preceding validation step so that a failure can be rolled back as a unit. Its logic relies on the underlying FND_API, FND_MESSAGE, and FND_MSG_PUB error-handling infrastructure, allowing it to surface errors to the calling concurrent program.

Tables Accessed

INSERT_CONTRACTS reads staged data from OKS_INT_HEADER_STG_TEMP, OKS_INT_LINE_STG_TEMP, OKS_INT_SALES_CREDIT_STG_TEMP, OKS_INT_USAGE_COUNTER_STG_TEMP, OKS_INT_COVERED_LEVEL_STG_TEMP, OKS_COVERED_LEVELS_INTERFACE, OKS_LINES_INTERFACE, and OKS_USAGE_COUNTERS_INTERFACE. It writes contract structures into the base tables OKC_K_HEADERS_B, OKC_K_HEADERS_B_S, OKC_K_HEADERS_TL, OKC_K_LINES_B, OKC_K_LINES_TL, OKC_K_ITEMS, OKC_K_VERS_NUMBERS, OKC_K_GRPINGS, OKC_GOVERNANCES, OKC_CONTACTS, OKC_K_PARTY_ROLES_B, OKC_K_PARTY_ROLES_TL, and OKC_K_PROCESSES. The OKS-specific tables OKS_K_HEADERS_B, OKS_K_LINES_B, OKS_K_LINES_TL, OKS_K_SALES_CREDITS, OKS_SUBSCR_HEADER_B, and OKS_SUBSCR_HEADER_TL capture service-specific attributes. Customer and site references are resolved against HZ_CUST_ACCT_SITES_ALL and HZ_CUST_SITE_USES_ALL, and utility routines in OKC_P_UTIL are used for common contract operations.

Usage Notes

OKS_IMPORT_INSERT is not intended for direct customer invocation; it is called by the broader Service Contracts import flow (OKS_IMPORT_PUB and its associated concurrent program) after validation of staged records. Because its data set includes OKC_K_HEADERS_B, the package is relevant to searches involving the OKC contract header base table and its sequences (OKC_K_HEADERS_B_S). Custom integrators who need to load contracts outside the supported import path should use the documented OKC and OKS public APIs rather than this internal package, since reliance on its underlying tables and OKC_P_UTIL helpers is unsupported. The package is classified with API classification OTHER and is referenced by at least one other package, confirming its role as an internal building block. In EBS 12.1.1 and 12.2.2 the dependency graph, table list, and procedure surface are consistent, with no documented differences between the two releases.