Search Results insert_sif_price_parms

Overview

OKL_SIF_PRICE_PARMS_PUB is a public PL/SQL package body in the Oracle E-Business Suite Applications (APPS) schema, owned by Oracle Lease and Finance Management (OKL). It belongs to the Sales Information File (SIF) price parameter integration layer and provides the programmatic interface through which externally sourced price parameters are inserted, maintained, and validated within the leasing application. The package is the public counterpart to the private implementation package OKL_SPP_PVT, delegating the actual data manipulation to that lower-level package while presenting a stable, versioned API to callers.

Like other public APIs in ETRM, the package follows the Oracle Application Object Library (FND_API) transaction-handling conventions: it accepts an API version, an initialization flag, and standard return status, message count, and message data OUT parameters. Errors are surfaced through the standard FND_API return statuses—G_RET_STS_SUCCESS, G_RET_STS_ERROR, and G_RET_STS_UNEXP_ERROR—and messages are retrieved using FND_MSG_PUB. This design allows callers to participate in a single logical transaction with consistent rollback and message propagation behaviour.

Key Procedures and Functions

The documented API exposes the following procedures and functions (parameters are not enumerated here; only documented purposes are described):

• INSERT_SIF_PRICE_PARMS — Inserts a new SIF price parameter record. It accepts a price parameter record (SPPV_REC_TYPE), calls OKL_SPP_PVT.INSERT_ROW within a savepoint, and raises the standard FND_API exceptions when the return status indicates an error or unexpected error. Rollback to the savepoint is performed on exception, and messages are counted and retrieved via FND_MSG_PUB.
• UPDATE_SIF_PRICE_PARMS — Updates an existing SIF price parameter record through the corresponding private routine.
• DELETE_SIF_PRICE_PARMS — Removes a SIF price parameter record from the underlying table.
• LOCK_SIF_PRICE_PARMS — Acquires a lock on the target price parameter record to serialise concurrent maintenance operations.
• VALIDATE_SIF_PRICE_PARMS — Validates a SIF price parameter record, enforcing the business rules required before the record can be accepted. This is the procedure most commonly searched for by name.
• ADD_LANGUAGE — A translation/MLS maintenance stub retained for consistency with the standard ETRM package template; in the documented source it simply returns NULL.

Tables Accessed

The only table documented as referenced through APPS synonyms is PLITBLM. This is the multi-language (translation) base table used by the Oracle multi-lingual support infrastructure, and its presence here is consistent with the ADD_LANGUAGE routine and the MLS conventions applied to ETRM packages. The primary business data manipulated by INSERT, UPDATE, and DELETE operations resides behind the OKL_SPP_PVT private package, which encapsulates the SIF price parameter storage; direct table references therefore do not appear at the public API layer. Callers should treat OKL_SPP_PVT as the owner of the physical storage and use OKL_SIF_PRICE_PARMS_PUB exclusively for entry.

Usage Notes

OKL_SIF_PRICE_PARMS_PUB is typically invoked from Oracle Forms, concurrent programs, and custom PL/SQL code that needs to create or maintain SIF price parameters as part of lease pricing integration. The metadata records three packages as referencing this object, confirming it is an established dependency for downstream ETRM components. The header comment indicates the source file is shipped as noship, meaning the object is deployed to the database but excluded from shipped patch artifacts in the ordinary sense.

Because the package delegates to OKL_SPP_PVT and uses SAVEPOINT-based rollback, callers may safely embed individual calls inside a larger transaction: on error the API rolls back only to its own savepoint, sets X_RETURN_STATUS to the appropriate FND_API constant, and exposes the accumulated messages through X_MSG_COUNT and X_MSG_DATA. When the searched VALIDATE_SIF_PRICE_PARMS procedure is used, it should be called before INSERT or UPDATE to confirm that supplied parameters satisfy the pricing constraints; the subsequent call is skipped if validation returns an error status. Custom code should always check X_RETURN_STATUS after every invocation rather than relying on exceptions, since the API handles its own exception translation.