Search Results okl_service_integration_pub




Overview
Explore in AI Chat

Overview

OKL_SERVICE_INTEGRATION_PUB is a public PL/SQL package in the Oracle E-Business Suite (EBS) Lease Management (OKL) module, classified as a PUB API and owned by the APPS schema. Its primary purpose is to integrate Oracle Lease Management with Oracle Service (OKS) service contracts. The package enables lease contracts to reference and link service lines defined in service contract headers and lines, thereby synchronizing service coverage with the associated lease assets. This integration is essential when a leased asset requires associated service coverage, such as maintenance or warranty agreements, and the lease contract must reflect that coverage. The package body header indicates a packaging convention consistent with EBS standards: it defines global constants such as G_PKG_NAME, G_APP_NAME, and G_API_TYPE, and uses OKC_API.START_ACTIVITY for savepoint creation, version compatibility checks, and message list initialization.

Key Procedures and Functions

  • CREATE_SERVICE_LINE — Creates a service line within the lease contract context, establishing the service line record that will later be associated with the lease or referenced by an integration call.
  • LINK_SERVICE_LINE — Links an existing service line to a lease contract, ensuring the service coverage is associated with the correct contract header.
  • DELETE_SERVICE_LINE — Removes a previously created or linked service line, supporting maintenance and correction of service coverage records.
  • CHECK_SERVICE_LINK — The procedure targeted by the user's search. It validates whether a service link already exists, serving as a pre-check to prevent duplicate links and to confirm integration state before further processing.
  • GET_SERVICE_LINK_LINE — Retrieves the service link line information, returning the linkage details for a given contract or service line.
  • CREATE_LINK_SERVICE_LINE — A composite procedure that creates a service line and links it under a given lease contract. It accepts input identifying the lease contract header, service contract header, and service contract service top line, and returns the lease contract service top line identifier. Internally it calls OKC_API.START_ACTIVITY to initialize the API context and validate compatibility.
  • UPDATE_SERVICE_LINE — Modifies attributes of an existing service line, keeping the lease-side representation in sync with changes on the service contract side.
  • CREATE_COV_ASSET_LINE — Creates a covered asset line, associating an asset with the service coverage defined on the lease contract.
  • UPDATE_COV_ASSET_LINE — Updates the covered asset line, reflecting changes to the asset or coverage relationship.
  • INITIATE_SERVICE_BOOKING — Initiates the service booking process, finalizing the integration so the service contract is recognized against the lease.

Tables Accessed

The documented table referenced via APPS synonyms is OKC_K_HEADERS_B, the base table for contract headers. The package reads and writes lease and service contract header records through this table, using contract header identifiers (p_okl_chr_id for the lease contract and p_oks_chr_id for the service contract). The create_link_service_line procedure further references OKC_K_HEADERS_V and OKC_K_LINES_V for header and line identifier types, indicating access to contract lines (OKC_K_LINES_B) and their views for service top lines. These accesses support the creation, linkage, validation, and deletion of service lines across the lease and service contract schemas.

Usage Notes

OKL_SERVICE_INTEGRATION_PUB is a server-side integration API invoked by other EBS packages and by custom extensions rather than directly from a form. The metadata indicates it is referenced by seven other packages, reflecting its role as a shared integration point. It is typically called when lease contracts must be synchronized with Oracle Service contract data, for example during contract creation, service booking, or asset coverage updates. Callers should supply a valid API version, set p_init_msg_list appropriately, and inspect x_return_status along with x_msg_count and x_msg_data for error handling. Use CHECK_SERVICE_LINK prior to CREATE_LINK_SERVICE_LINE or LINK_SERVICE_LINE to confirm that a link does not already exist, avoiding duplicate associations.