Search Results g_dates_mismatch

Overview

OKL_SETUPTQUALITYS_PVT is a private (PVT) PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema, part of the Oracle Lease and Finance Management (OKL) module. It operates within the ETRM (Enterprise Transaction and Reference Model) framework, alongside the associated public package OKL_PTL_QUALITYS_PUB. The package provides the internal implementation layer for maintaining lease quality setup records — the configuration that controls how leased assets and contracts are classified against quality criteria during the lease lifecycle.

The package is declared with AUTHID CURRENT_USER and includes standardized error-handling tokens such as G_UNEXPECTED_ERROR, G_SQLERRM_TOKEN, G_SQLCODE_TOKEN, G_INVALID_DATES, and G_NOT_ALLOWED. Notably, it defines the constant G_DATES_MISMATCH := 'OKL_DATES_MISMATCH'. This constant is the source of the user-searched term okl_dates_mismatch. It represents a message token raised when the date attributes supplied to a quality setup record conflict with one another — for example, an effective start date that falls after an end date, or a date that violates a parent lease or contract date constraint.

Key Procedures and Functions

• GET_REC — Retrieves a single quality setup record (ptqv_rec_type) from the underlying tables. It returns the populated record along with a NO_DATA_FOUND indicator and a return status code, allowing the caller to distinguish between a missing record, a successful fetch, and an error condition.
• INSERT_TQUALITYS — Creates a new lease quality setup record. It accepts the standard API version and initialization-message parameters, the input record to insert, and returns the resulting record and standard output parameters (return status, message count, message data). Date validation errors such as OKL_DATES_MISMATCH are surfaced through this interface.
• UPDATE_TQUALITYS — Modifies an existing quality setup record. It follows the same API versioning and message-handling convention as the insert procedure and applies the same date and validation rules.

The two data-modifying procedures rely on the shared exception G_EXCEPTION_HALT_PROCESSING for fatal errors and on the OKL_API token constants (G_COL_NAME_TOKEN, G_PARENT_TABLE_TOKEN, G_CHILD_TABLE_TOKEN) for consistent message construction.

Tables Accessed

The ETRM metadata does not enumerate the underlying tables referenced by this package through APPS synonyms. Based on the OKL quality setup data model, the package reads and writes the lease quality setup base table and its associated translation or validation tables. The record type ptqv_rec_type is reused from OKL_PTL_QUALITYS_PUB, confirming that the same underlying storage structure serves both the public and private layers. Access is performed through APPS synonyms, so no schema-qualified table names are exposed to callers.

Usage Notes

As a PVT package, OKL_SETUPTQUALITYS_PVT is not intended for direct invocation by end users or external integrations. It is called by two other packages, most likely OKL_PTL_QUALITYS_PUB and a related validation or setup wrapper. The public package exposes the supported API surface for Oracle Forms setup screens, concurrent programs, and custom code, while the PVT layer performs the actual record retrieval and DML.

The presence of the G_INVALID_DATES, G_NOT_ALLOWED, and G_DATES_MISMATCH constants indicates that callers should expect date-related validation failures when setup records overlap, fall outside the lease term, or mix inconsistent start and end dates. When the okl_dates_mismatch error is encountered, it typically originates from the insert or update path of this package and should be remediated by correcting the date attributes on the affected quality setup record rather than by modifying the package itself.