Search Results get_final_end_date

Overview

OKS_CON_COVERAGE_PVT is a private PL/SQL package in the APPS schema that underpins the contract coverage functionality delivered through Oracle Service Contracts and Oracle Contracts. As indicated by the PVT suffix, it is an internal implementation package: its procedures and functions are not intended to be called directly by external code, but are invoked by the corresponding public package, OKS_CON_COVERAGE_PUB, which acts as the supported entry point. The package status is VALID and it is classified as a private API within the ETRM (Enterprise Technical Reference Manual) documentation set for Oracle EBS 12.1.1 and 12.2.2.

The business purpose of this package is to perform the server-side processing required to apply contract coverage to service contract lines, to determine billing rates and billing schedules, and to calculate date-related attributes such as final end dates, grace period end dates, and working-day offsets. These operations support the generation of coverage records that link a service contract line to the entitlement being provided, and they make use of Bill Rate Schedules that drive recurring and non-recurring billing.

Key Procedures and Functions

The ETRM metadata documents nine procedures and functions within this package. Descriptions follow; no parameter lists are reproduced because they are not part of the documented metadata.

• APPLY_CONTRACT_COVERAGE — the principal processing routine, responsible for applying coverage to a contract line and creating or updating the associated coverage records.
• GET_BP_PRICELIST — retrieves the price list associated with the business partner, used as the basis for rate determination.
• GET_BILL_RATES — returns the billing rates applicable to the coverage, derived from the Bill Rate Schedules and the pricing context.
• GET_NEXT_WKDAY — a date utility that returns the next working (business) day, supporting schedule calculations that must avoid non-working days.
• REMOVE_ZERO_DURATION_BILLRATES — filters out bill rate entries having zero duration, preventing invalid or meaningless schedule lines from being processed.
• SORT_BILLRATES_DATETIME — orders bill rate entries by date and time so that subsequent processing proceeds chronologically.
• GET_FINAL_END_DATE — computes the final end date of the coverage, accounting for the contract term and related rules.
• GET_BP_LINE_START_OFFSET — determines the start-date offset for the business partner line, used to align coverage start dates.
• GET_GRACE_END_DATE — calculates the end date of the grace period applicable to the coverage.

Tables Accessed

The package operates primarily against the core Contracts and Service Contracts tables, referenced through APPS synonyms. OKC_K_HEADERS_ALL_B, OKC_K_ITEMS, and OKC_K_LINES_B are the Contracts header, item, and line tables that define the contract structure to which coverage is applied. OKS_K_HEADERS_B and OKS_K_LINES_B hold the Service Contracts header and line records, which the coverage processing extends or reads for the service entitlement. OKS_BILLRATE_SCHEDULES stores the bill rate schedule rows from which billing rates are obtained, sorted, and cleaned of zero-duration entries. PLITBLM is an Oracle Applications standard utility table (primarily associated with multi-organization and date-related helper operations) used by internal logic within the package.

Usage Notes

OKS_CON_COVERAGE_PVT is not called directly from Oracle Forms, concurrent programs, or customer extensions. It is referenced by OKS_CON_COVERAGE_PUB, which is the documented public interface, and it also references internal subprograms within itself. Its dependencies include the FND_API framework, FND_PROFILE for profile option lookups, OKC_API for Contracts API services, and the standard SYS.STANDARD package. Custom development should invoke OKS_CON_COVERAGE_PUB rather than this private package, since Oracle does not guarantee the signature or behavior of PVT packages across releases or patches. The utility functions such as GET_NEXT_WKDAY and GET_GRACE_END_DATE are executed within the coverage application flow rather than as standalone calls.