Search Results okc_kexp_pvt




Overview
Explore in AI Chat

Overview

OKC_KEXP_PVT is a private PL/SQL package body in the APPS schema that supports the Oracle Contracts (OKC) repository's export and reporting infrastructure. Its name derives from the Contracts "K Export" family of objects, and it operates alongside OKC_KEXP_REPORT and the concurrent-program-facing logic that produces contract export output. The package is classified as a PVT (private) API, meaning it is intended for internal use by Oracle E-Business Suite code rather than as a supported public integration interface. In EBS 12.1.1 and 12.2.2 the object is VALID and depends on standard EBS infrastructure packages including FND_API, FND_PROFILE, OKC_API, and OKC_KEXP_PVT's sibling OKC_KEXP_REPORT. It also references the OKX_SALESREPS_V view, DUAL, and the PL/SQL table type PLITBLM. The package is not referenced by any other database object but is documented as being referenced by one other package, confirming it functions as an internal helper layer within the contract export process. Its principal business role is to manage the transient search-result rows that drive contract export/report selection and to resolve sales representative names for display in that output.

Key Procedures and Functions

The documented program units in OKC_KEXP_PVT are three:

  • LOAD_KSRCH_ROWS — Populates the working set of rows used by the contract export search. It is the loading routine that stages the criteria or result rows into the structures later consumed by the export report logic.
  • DELETE_KSRCH_ROWS — Removes the staged search rows, providing the cleanup counterpart to LOAD_KSRCH_ROWS. Together these two routines manage the lifecycle of the temporary search table.
  • GET_SALESREP_NAME — Resolves and returns the name of a sales representative, using the OKX_SALESREPS_V view as its source of salesrep data for display or reporting purposes.

The precise parameter signatures are not enumerated in the available metadata and should be confirmed by inspecting the package specification in the target environment before any custom invocation.

Tables Accessed

The package references OKC_KEXP_REPORT and its sequence OKC_KEXP_REPORT_S1 as the primary persistent objects. OKC_KEXP_REPORT stores the export/report records generated by the contract export process, and the S1 sequence supplies primary key values for new rows. DUAL is used for standard single-row SQL evaluation, and the PLITBLM PL/SQL table type supports in-memory array handling for the search-row loading and deletion operations. OKX_SALESREPS_V is read by GET_SALESREP_NAME to retrieve sales representative details. Because all access is through APPS synonyms, the actual physical tables reside in the OKC/OKX product schemas.

Usage Notes

Because OKC_KEXP_PVT is a PVT-class package, it is not a supported entry point for customer extensions. It is normally invoked indirectly when a user runs the contract export or reporting flow from Oracle Contracts forms or when a related concurrent program executes. In 12.1.1 and 12.2.2 the package is expected to be called by the single dependent package documented in the ETRM metadata rather than directly by forms. Custom code should avoid calling LOAD_KSRCH_ROWS, DELETE_KSRCH_ROWS, or GET_SALESREP_NAME directly, since private APIs may change between releases without notice. Where sales representative names are required in custom reporting, the supported OKX_SALESREPS_V view should be queried instead. Any diagnosis of export behavior should begin with OKC_KEXP_REPORT and its sequence, as those objects hold the persisted results that OKC_KEXP_PVT manipulates.