Search Results create_link_service_line
Overview
The OKL_SERVICE_INTEGRATION_PUB package is a public PL/SQL API belonging to the Oracle Lease and Finance Management (OKL) application family within Oracle E-Business Suite. It is declared with AUTHID CURRENT_USER and resides in the APPS schema. Its principal business purpose is to integrate lease contract service lines with service contract service lines in the Oracle Service Contracts (OKC) schema. This integration ensures that when a lease incorporates services — such as maintenance, warranties, or support — the corresponding service contract service top lines are created, linked, and kept synchronized with the lease-side representation.
The package header file (OKLPSRIS.pls) dates to the early 12.1.x development cycle, and the API remains documented through 12.2.2. The API follows the standard EBS PL/SQL API conventions, accepting p_api_version, p_init_msg_list, and returning x_return_status, x_msg_count, and x_msg_data so callers can perform structured error handling. It is classified as a PUB API, meaning it is a supported integration surface for external and internal consumers.
Key Procedures and Functions
The package exposes ten documented routines. Their purposes are as follows:
- CREATE_SERVICE_LINE — Creates a lease-side service top line corresponding to a service contract service line. It accepts both the lease contract header ID and the service contract header ID, along with the source service line identifier, and returns the newly created lease service line identifier.
- LINK_SERVICE_LINE — Establishes the association between an existing lease service top line and a service contract service top line.
- DELETE_SERVICE_LINE — Removes a lease service line, taking an existing line record as input.
- CHECK_SERVICE_LINK — Validates whether a service link already exists between the lease and service contract sides, typically used prior to creation to avoid duplicates.
- GET_SERVICE_LINK_LINE — Retrieves the linked service line information for a given lease or service contract context.
- CREATE_LINK_SERVICE_LINE — A combined convenience routine that creates the lease service line and establishes the link to the service contract line in a single call. This is the routine most commonly referenced when searching for "create_link_service_line."
- UPDATE_SERVICE_LINE — Modifies attributes of an existing lease service line.
- CREATE_COV_ASSET_LINE — Creates a coverage asset line, associating an asset with the service coverage on the lease.
- UPDATE_COV_ASSET_LINE — Updates an existing coverage asset line.
- INITIATE_SERVICE_BOOKING — Initiates the service booking process that drives downstream service contract processing.
Tables Accessed
The documented table reference for this package is OKC_K_HEADERS_B, accessed via the APPS synonym. This is the base table for service and lease contract headers, and the package reads it primarily to validate header identifiers and derive contract context. The routines also operate against OKC_K_HEADERS_V and OKC_K_LINES_V, which supply the column definitions for the header ID and service top line ID parameters (p_okl_chr_id, p_oks_chr_id, p_oks_service_line_id, x_okl_service_line_id). It additionally references the private package OKL_SERVICE_INTEGRATION_PVT, which encapsulates the heavier data manipulation logic against the OKC contract line structures.
Usage Notes
OKL_SERVICE_INTEGRATION_PUB is typically invoked from the Oracle Lease Management forms and from concurrent programs that process lease-service integration during contract booking and service coverage setup. It is also a candidate for custom integration code where a lease and a service contract must be programmatically kept in step. Callers should always initialize the message list, pass a valid p_api_version, and check x_return_status for FND_API.G_RET_STS_SUCCESS before proceeding, using the standard FND_MSG_PUB utilities to extract any error messages. Because the package is referenced by seven other packages, changes to its behavior should be evaluated for downstream impact.
-
PACKAGE: APPS.OKL_SERVICE_INTEGRATION_PUB
12.1.1
-
PACKAGE: APPS.OKL_SERVICE_INTEGRATION_PUB
12.2.2
-
PACKAGE BODY: APPS.OKL_SERVICE_INTEGRATION_PUB
12.1.1
-
PACKAGE BODY: APPS.OKL_SERVICE_INTEGRATION_PUB
12.2.2
-
PACKAGE: APPS.OKL_SERVICE_INTEGRATION_PVT
12.1.1
-
PACKAGE: APPS.OKL_SERVICE_INTEGRATION_PVT
12.2.2
-
PACKAGE BODY: APPS.OKL_SERVICE_INTEGRATION_PVT
12.1.1
-
PACKAGE BODY: APPS.OKL_SERVICE_INTEGRATION_PVT
12.2.2
-
APPS.OKL_SERVICE_INTEGRATION_PVT dependencies on FND_LOG
12.2.2
-
APPS.OKL_SERVICE_INTEGRATION_PVT dependencies on FND_LOG
12.1.1
-
APPS.OKL_SERVICE_INTEGRATION_PVT dependencies on OKL_DEBUG_PUB
12.1.1
-
APPS.OKL_SERVICE_INTEGRATION_PVT dependencies on OKL_DEBUG_PUB
12.2.2
-
APPS.OKL_SERVICE_INTEGRATION_PUB dependencies on OKC_K_LINES_V
12.1.1
-
APPS.OKL_SERVICE_INTEGRATION_PUB dependencies on OKC_K_LINES_V
12.2.2
-
APPS.OKL_SERVICE_INTEGRATION_PUB dependencies on OKC_K_HEADERS_V
12.2.2
-
APPS.OKL_SERVICE_INTEGRATION_PUB dependencies on OKC_K_HEADERS_V
12.1.1
-
APPS.OKL_SERVICE_INTEGRATION_PUB dependencies on OKL_API
12.2.2
-
APPS.OKL_SERVICE_INTEGRATION_PUB dependencies on OKL_API
12.1.1
-
APPS.OKL_SERVICE_INTEGRATION_PUB dependencies on OKC_K_HEADERS_V
12.2.2
-
APPS.OKL_SERVICE_INTEGRATION_PUB dependencies on OKC_K_HEADERS_V
12.1.1
-
APPS.OKL_SERVICE_INTEGRATION_PVT dependencies on OKL_API
12.2.2
-
APPS.OKL_SERVICE_INTEGRATION_PVT dependencies on OKL_API
12.1.1
-
APPS.OKL_SERVICE_INTEGRATION_PVT dependencies on OKC_K_LINES_V
12.1.1
-
APPS.OKL_SERVICE_INTEGRATION_PVT dependencies on OKC_K_LINES_V
12.2.2
-
APPS.OKL_SERVICE_INTEGRATION_PVT dependencies on OKC_K_HEADERS_V
12.1.1
-
APPS.OKL_SERVICE_INTEGRATION_PVT dependencies on OKC_K_HEADERS_V
12.2.2
-
APPS.OKL_SERVICE_INTEGRATION_PVT dependencies on OKC_K_HEADERS_V
12.2.2
-
APPS.OKL_SERVICE_INTEGRATION_PVT dependencies on OKC_K_HEADERS_V
12.1.1
-
APPS.OKL_SERVICE_INTEGRATION_PVT dependencies on OKC_API
12.1.1
-
APPS.OKL_SERVICE_INTEGRATION_PVT dependencies on OKC_API
12.2.2