Search Results okc_oc_int_pub




Overview

OKC_OC_INT_PUB is a public PL/SQL package in the APPS schema that provides the integration layer between Oracle Contracts Core (OKC) and Oracle Order Capture / Quoting (OKX, formerly ASO). Its central purpose is to automate the creation and synchronization of contract documents from sales transactions, and conversely to generate quoting and order documents from existing contract headers. This "quote-to-contract" and "contract-to-order" round-tripping is central to order-to-cash flows in Oracle E-Business Suite 12.1.1 and 12.2.2.

The package carries an API classification of PUB, indicating it is a supported public interface that customers and integrators may call directly from custom code. It is registered as VALID in the ETRM repository and exposes 19 documented procedures and functions. It is referenced by five other packages (including OKC_OC_INT_KTO_PVT, OKS_EXTWARPRGM_PVT, OKS_OCINT_PUB, and the workflow approval packages OKC_WF_K_APPROVE and OKS_WF_K_APPROVE), which confirms its role as a shared service used by service contracts and workflow-driven approval processes as well as by quoting.

Key Procedures and Functions

The documented API surface covers several functional groupings:

Tables Accessed

The package reads and writes the core OKC base tables and the OKX quote/order views via APPS synonyms:

  • OKC_K_HEADERS_B — the contract header; read to fetch contract attributes and written when contracts are created from quotes.
  • OKC_K_ARTICLES_TL — contract article translations, read by GET_ARTICLES to return clause text.
  • OKC_K_REL_OBJS — relationship objects linking a contract to its source quote or order; written by CREATE_K_RELATIONSHIPS.
  • OKX_QUOTE_HEADERS_V / OKX_QUOTE_LINES_V and OKX_ORDER_HEADERS_V / OKX_ORDER_LINES_V — the Order Capture quote and order views used to build or read sales documents.
  • FND_NEW_MESSAGES and FND_USER — used for notification delivery and recipient resolution.

Usage Notes

OKC_OC_INT_PUB is normally invoked indirectly from the Contracts and Quoting forms, from workflow activities (such as the contract approval workflows OKC_WF_K_APPROVE and OKS_WF_K_APPROVE), and from concurrent programs that process renewals or order-to-contract conversions. It is also called by OKS_EXTWARPRGM_PVT for service contract warranty integration. Custom code should call the package only through its public procedures, supplying the required contract or quote identifiers, and should expect message and error handling via the FND message stack. Because the package writes contract headers, relationships, and interaction history, calls should be wrapped in an explicit commit or rollback unit and should not be run concurrently against the same contract record.