Search Results refresh_sales_k_hdrs

Overview

The APPS.OKI_REFRESH_PUB package body is a public API in Oracle E-Business Suite that supports the Oracle Knowledge Initialize (OKI) data refresh mechanism used by the Service Contracts (OKS) and related Order Management flows. Its principal business function is to refresh, rebuild, or repopulate the denormalized "K" (Knowledge) staging and interface tables that back service contract sourcing, pricing, and order capture. These tables hold pre-computed snapshots of sales headers, sold item lines, covered product lines, expired lines, sales representatives, conversion rates, pricing rules, and address data, allowing the contract and order entry screens to resolve eligible service offerings quickly rather than recomputing them from base transaction tables at runtime.

In EBS 12.1.1 and 12.2.2 the package is owned by the APPS schema and is reported as VALID. It is registered as a public API (PUB classification), meaning it is intended to be called programmatically by other EBS components or by custom extensions rather than being restricted to internal use. It is not referenced by any other database object, which indicates it sits at the top of the call stack and is driven directly by concurrent programs or user actions.

Key Procedures and Functions

The package exposes twenty-three documented procedures and functions, organized around a set of refresh operations, accelerated "FAST" variants, and job control utilities.

• REFRESH_DAILY_RATES — refreshes the currency conversion rates used when evaluating service pricing and coverage amounts.
• REFRESH_SALES_K_HDRS and FAST_SALES_K_HDRS — rebuild the knowledge-level sales header records, with the FAST variant performing a narrower, incremental refresh for performance.
• REFRESH_SOLD_ITM_LINES and FAST_SOLD_ITM_LINES — repopulate the sold item line snapshot used for service eligibility determination.
• REFRESH_COV_PRD_LINES and FAST_COV_PRD_LINES — refresh covered product lines, which record items that are already covered under an existing service agreement.
• REFRESH_EXPIRED_LINES and FAST_EXPIRED_LINES — rebuild the lines whose service coverage has lapsed.
• REFRESH_K_SALESREPS and FAST_K_SALESREPS — refresh sales representative information associated with the knowledge tables.
• REFRESH_K_CONV_RATES — refresh knowledge conversion rate data.
• REFRESH_K_PRICING_RULES and FAST_K_PRICING_RULES — rebuild the pricing rule snapshot used for service pricing during order capture.
• REFRESH_ADDRS and FAST_ADDRS — refresh address data held in the knowledge tables, supporting ship-to and bill-to logic.
• JOB_START, JOB_END, and INITIAL_JOB_CHECK — control procedures that mark the beginning and end of a refresh run and validate preconditions before a job proceeds.
• UPDATE_SERVICE_LINE — updates an individual service line record, allowing a targeted modification outside a full refresh.

Tables Accessed

The documented dependency list shows that the package body references APPS.OKI_REFRESH_PVT, the private implementation package that performs the bulk of the actual data manipulation, along with FND_CONC_DATE (the concurrent program date table used for date-driven processing) and the STANDARD package from SYS. The specific base tables are not enumerated in the metadata, but based on the procedure names and ETRM context, the package reads from and writes to the OKI knowledge tables (the OKI_... K-tables) for sales headers, sold item lines, covered product lines, expired lines, sales representatives, conversion rates, pricing rules, and addresses. These are populated directly by the refresh procedure, often by first calling into OKI_REFRESH_PVT for the underlying SQL work.

Usage Notes

OKI_REFRESH_PUB is typically invoked as part of the Oracle Service Contracts knowledge refresh concurrent program, which rebuilds the knowledge tables on a scheduled basis so that order and contract entry screens reflect current coverage, pricing, and eligibility. Because it is a public API, custom code may call it directly to perform on-demand refreshes or targeted updates (for example, UPDATE_SERVICE_LINE) following a data correction. It is not referenced by other database objects, so callers must invoke it explicitly from a concurrent program, a form, or a custom PL/SQL block, and the JOB_START/JOB_END pair should bracket refresh activity to ensure job control and validation logic run correctly.

The ETRM metadata supplied is limited; the parameter lists and detailed table mappings above are described at the level supported by the documented procedure names and dependency list.