Search Results max_valid_from_date

Overview

OKL_LEASEAPP_TEMPLATE_PVT is a private PL/SQL package in the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, declared with AUTHID CURRENT_USER. It encapsulates the internal business logic for managing lease application templates — reusable definitions that pre-populate the data required when a lease application is created. Templates standardize lease origination by carrying default header, checklist, and version attributes that downstream application records inherit.

The package maintains a lifecycle for each template through a set of status constants. Templates are created with an initial status of NEW (G_INIT_TMPLT_STATUS), then transition through ACTIVE, UNDEREVISION, SUBFORAPPROVED, REJECTED, or INVALID. The constant matching the search term, G_STATUS_INVALID, represents a template state in which the definition is no longer considered usable for generating lease applications. Because this is a _PVT package, it is not intended for direct invocation by external consumers; it is called by the public OKL_LEASEAPP_TEMPLATE API layer and by other internal OKL packages (two documented dependents).

Key Procedures and Functions

• CREATE_LEASEAPP_TEMPLATE — Creates a new lease application template record, establishing the initial version and assigning the starting status of NEW.
• UPDATE_LEASEAPP_TEMPLATE — Modifies an existing template definition, including attributes that govern how lease applications are defaulted from the template.
• VERSION_DUPLICATE_LSEAPP_TMPL — Produces a new version of an existing template, using the default duplicate mode (G_DEFAULT_MODE = 'DUPLICATE') to copy the source definition into a new template version record.
• VALIDATE_LEASE_APP_TEMPLATE — Validates template data prior to persistence or activation, returning error messages through the error_msg_rec/error_msgs_tbl_type structures and raising G_EXCEPTION_HALT_VALIDATION to stop processing on failure.
• MAX_VALID_FROM_DATE — Determines the effective end of the current validity window for a template version, supporting date-effective versioning so that a new version begins after the prior version's valid-from range.
• ACTIVATE_LAT — Transitions a lease application template to the ACTIVE status, making it eligible for use in lease application origination.

Tables Accessed

The package operates against the following APPS synonyms:

• OKL_LEASEAPP_TEMPLATES and OKL_LEASEAPP_TEMPL_VERSIONS_B — the core template header and its versioned definition rows.
• OKL_LEASE_APPLICATIONS_B — lease application headers created from or associated with templates.
• OKL_K_HEADERS and OKC_K_HEADERS_B — contract/lease header data linked to templates.
• OKL_CHECKLISTS — checklist definitions attached to templates.
• OKL_VP_ASSOCIATIONS — associations between templates and related entities.
• WF_EVENTS and WF_PARAMETER_LIST_T — Oracle Workflow event and parameter structures used to raise business events on create, update, or activate.
• FND_LOG_MESSAGES — diagnostic logging via the FND logging framework.
• PLITBLM — the PL/SQL table-to-index-by conversion utility used for bulk operations.

Usage Notes

OKL_LEASEAPP_TEMPLATE_PVT is invoked indirectly. In the standard EBS Lease Management forms, template maintenance screens call the public OKL_LEASEAPP_TEMPLATE API, which delegates to this private package. Concurrent programs that version, validate, or activate templates likewise reach it through the public layer, and the two documented dependent packages call it directly from within the server-side stack. Custom code should never call OKL_LEASEAPP_TEMPLATE_PVT directly; the correct integration point is the public API. Because activation and validation raise workflow events and write to FND_LOG_MESSAGES, invocations should be committed by the caller after successful completion. The G_STATUS_INVALID constant is relevant when diagnosing why a template cannot be used for lease application generation: a template in INVALID status fails validation and is excluded from activation processing.