Search Results merge_eligible_yn

Overview

OKS_RENCON_PVT is a private PL/SQL package in the APPS schema within Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its name reflects its role in Service Contracts (OKS — Service Contracts/Support) as a "renewal contract" private API supporting contract renewal and merge processing. The package is classified as a PVT (private) API, meaning it is an internal implementation layer rather than a public interface. Oracle's API classification conventions reserve the PVT suffix for packages whose logic is invoked by higher-level public APIs, forms, or concurrent programs, and whose signatures are not guaranteed for third-party calling. In release 12.2.2, ETRM documents sixteen procedures and functions within the package, confirming that OKS_RENCON_PVT handles the substantive processing behind contract renewal and line-merge functionality: validating operation lines, creating operation instances and lines, evaluating merge eligibility, executing merges, submitting concurrent programs, and updating contract amounts. The package is VALID in the documented environment and is not referenced by any other package, indicating it sits at the top of its own private call stack and is consumed directly by forms or concurrent modules rather than being chained into further package logic.

Key Procedures and Functions

The documented procedures and functions divide into several functional groups.

• Line-source validation: GET_VALID_OPER_LINE_SOURCES and GET_VALID_LINE_SOURCES identify which operation and contract line sources are eligible for a given transaction, filtering input candidates before processing begins.
• Instance and line creation: CREATE_OPERATION_INSTANCES and CREATE_OPERATION_LINES instantiate the OKC operation model records required to process a renewal or merge event.
• Status and target checking: FIND_OL_STATUS resolves the status of an operation line, while IS_VALID_TARGET assesses whether a given line or contract qualifies as a valid merge or renewal target.
• Hierarchy and rule resolution: GET_PARENT_LINE_ID and GET_LRT_RULE retrieve parent-line relationships and line-level rule information used to drive validation and processing.
• Detail retrieval and eligibility: GET_LINE_DETAILS returns line attributes, and MERGE_ELIGIBLE_YN answers the binary eligibility question for merge processing.
• Merge execution: MERGE performs the substantive merge, and UPDATE_CONTRACT_AMOUNT adjusts the associated contract amount afterward.
• Concurrent submission: SUBMIT, SUBMIT_CONC, and SUBMIT_FORM_CONC provide the entry points that submit processing to the concurrent manager, with distinct variants for direct submission and form-initiated submission.
• Logging: LOG_MESSAGES records diagnostic and error information for troubleshooting.

Tables Accessed

The package references standard Core Contracts and Service Contracts tables through APPS synonyms. OKC_CLASS_OPERATIONS, OKC_K_HEADERS_ALL_B, OKC_K_ITEMS, OKC_K_LINES_B, and OKC_K_PARTY_ROLES_B supply contract definition, header, line, item, and party-role data. OKC_OPERATION_INSTANCES and OKC_OPERATION_LINES are the operation model tables written by CREATE_OPERATION_INSTANCES and CREATE_OPERATION_LINES and read by the status and eligibility functions. OKC_STATUSES_B provides status lookup values. OKS_K_HEADERS_B and OKS_K_LINES_B are the Service Contracts header and line tables carrying the renewal and merge targets. DBMS_TRANSACTION and PLITBLM support transaction control and PL/SQL table buffering. FND_GLOBAL supplies application session context, and OKC_API is used for contract attribute access.

Usage Notes

As a private API, OKS_RENCON_PVT is invoked indirectly. Typical call paths are Service Contracts forms that trigger renewal or merge processing for a selected contract, and concurrent programs that process eligible lines in batch; the SUBMIT, SUBMIT_CONC, and SUBMIT_FORM_CONC procedures exist precisely to bridge these two modes, with the form variant handling the Forms-initiated submission path. Customizations should not call the package directly. Custom code requiring renewal or merge behavior should use the corresponding public Service Contracts API or the supported concurrent program, and should treat OKS_RENCON_PVT as subject to change across patches and upgrades. Because the package is referenced by no other package, any dependency analysis that shows OKS_RENCON_PVT as the caller's target indicates a direct invocation from a form, concurrent program, or custom object rather than a layered API chain. Environments upgrading from 12.1.1 to 12.2.2 should validate that the package remains VALID after patching, since the 16 procedures and functions enumerated in ETRM documentation constitute the full documented surface for this object.