Results for “oks_renew_contract_pub”

22 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.OKS_RENEW_CONTRACT_PUB package is the public renewal API for Oracle Service Contracts (OKS) in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the supported entry point through which a service contract is renewed — that is, extended into a successor contract with a new number, term, and period of performance — while preserving the commercial and entitlement relationships of the source agreement.

The header comment identifies this package as the R12-and-later replacement for legacy renewal logic. The stated redesign objectives are improved performance, reduced dependence on OKC (Contracts Core) code, incorporation of R12 functional design changes, compliance with current Oracle Applications coding and logging standards, and ease of maintenance. The package is declared AUTHID CURRENT_USER and defines packaged constants for validation scope (G_VALIDATE_ALL, G_VALIDATE_ERRORS) and validation status (G_VALID_STS_SUCCESS, G_VALID_STS_WARNING, G_VALID_STS_ERROR), which are mirrored from the private package OKS_RENEW_CONTRACT_PVT via SUBTYPE declarations.

Key Procedures and Functions

  • RENEW_CONTRACT — The primary renewal routine. It accepts the identifier of the source contract (p_chr_id, mandatory) together with optional target attributes: new contract number, modifier, start date, end date, duration, and unit of measure code. It also accepts p_renewal_called_from_ui (Y when invoked from the user interface, N when driven by Events), and returns x_chr_id, the identifier of the newly created renewed contract. Documented defaulting rules state that an omitted contract number inherits the source contract number and that modifier and date attributes follow defined inheritance rules.
  • VALIDATE_RENEWAL — Performs validation of a proposed renewal without committing the renewed contract, returning validation results using the packaged validation record and table types.
  • VALID_FOR_RENEWAL — Determines whether a given contract is eligible for renewal, based on its current status and renewal configuration.
  • FOR — A documented packaged element associated with the renewal API surface, used in conjunction with the procedures above.

Tables Accessed

  • OKC_K_HEADERS_B — The Contracts Core header table. The package reads the source contract header and writes the header row of the renewed contract, including contract number, modifier, and effective dates.
  • MTL_UNITS_OF_MEASURE_TL — The inventory units-of-measure translations table, consulted to resolve and validate the p_new_uom_code period value supplied for the renewed contract's duration.

Usage Notes

Typical invocation occurs through the Service Contracts forms and through Oracle Service Contracts renewal processing, where p_renewal_called_from_ui distinguishes interactive user-driven renewals from event-driven renewals. Concurrent programs and workflow events that automate mass or scheduled renewal also call this package.

For custom integrations, OKS_RENEW_CONTRACT_PUB is the sanctioned API; direct inserts into OKC_K_HEADERS_B are not supported and bypass validation, defaulting, and logging. No other packaged objects in the ETRM metadata reference this package, confirming its position as a top-level public interface rather than an internal dependency. Callers should invoke VALID_FOR_RENEWAL and VALIDATE_RENEWAL before RENEW_CONTRACT to surface eligibility and validation errors prior to contract creation. Error handling should interrogate the G_VALID_STS_* constants to interpret outcomes. Version header OKSPRENKS.pls 120.1 indicates the file has been functionally stable since the R12 release cycle.