Search Results insert_contracts

Overview

The OKS_IMPORT_INSERT package (source file OKSPKIMPINSS.pls, created by Mihira Karra) is a component of the Oracle Service Contracts (OKS) module in Oracle E-Business Suite 12.1.1 and 12.2.2. Its stated purpose is to provide the Service Contracts Import Insert Routines — that is, the final write step in the Service Contracts import pipeline.

Service Contracts import is a multi-stage process. Interface records are first loaded from external sources (staging tables or flat files) into OKS interface tables, then validated for referential and business-rule integrity. Records that pass validation are considered ready for migration into the production contract schema. OKS_IMPORT_INSERT performs that final migration: its single documented procedure moves successfully validated contract records out of the interface tables and into the actual base tables. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer, and it is owned by APPS and classified under the generic API category OTHER. It is referenced by one other package, indicating it is invoked as part of a larger import driver rather than run in isolation.

Key Procedures and Functions

The package exposes exactly one documented program unit:

• INSERT_CONTRACTS (PUBLIC) — Inserts the successfully validated and processed contract records from the Service Contracts interface tables into the production base tables. It has no documented parameters; it is a parameterless procedure. Invoking it commits the staged, validated contract data into the live OKC schema.

No other procedures or functions are exposed in the documented metadata. The header comment confirms the package body was authored in 2007 (revision 120.0), which is consistent with the API lineage carried forward into the 12.1.1 and 12.2.2 code lines.

Tables Accessed

The package references the following tables through APPS synonyms. Collectively they constitute the target contract model that INSERT_CONTRACTS populates:

• Contract headers and versions: OKC_K_HEADERS_ALL_B, OKC_K_HEADERS_B_S, OKC_K_HEADERS_TL, OKC_K_VERS_NUMBERS — the contract header, its translation rows, and version numbering.
• Contract lines and items: OKC_K_LINES_B, OKC_K_LINES_TL, OKC_K_ITEMS — line definitions, translated line text, and line-level items.
• Parties and contacts: OKC_K_PARTY_ROLES_B, OKC_K_PARTY_ROLES_TL, OKC_CONTACTS — contract party roles, their translations, and associated contacts.
• Supporting structures: OKC_GOVERNANCES, OKC_K_GRPINGS, OKC_K_PROCESSES — governance rules, groupings, and processes attached to contracts.
• Customer references: HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL — customer account sites and site uses from the Trading Community Architecture (HZ) model.

The presence of HZ tables reflects that import must resolve and persist customer/site references alongside the contract, ensuring the created contracts point to valid customer account sites.

Usage Notes

OKS_IMPORT_INSERT is not intended for direct interactive use by end users. It is typically invoked:

• As a final step in the Service Contracts import flow, after interface records have been loaded and validated; the import concurrent program or its driver package calls INSERT_CONTRACTS to commit validated records to the base tables.
• By the one package documented as referencing it, which acts as the surrounding orchestration layer for the import process.
• In custom or extension code only where a controlled, validated set of interface records exists and the caller has appropriate APPS-level privileges, since AUTHID CURRENT_USER requires the invoker to hold the necessary object privileges.

Because the procedure inserts directly into production contract tables, it should be run only within the sanctioned import process and with suitable error handling and transaction control, so that a partial failure does not leave orphaned or inconsistent contract data across the OKC and HZ tables.