Search Results oki_load_wbc_pub

Overview

OKI_LOAD_WBC_PUB is a public PL/SQL API package owned by the APPS schema in Oracle E-Business Suite. Its stated purpose, as declared in the package header comments, is to load the OKI_WIP_BY_CUSTOMERS table. This table is part of the OKI (Oracle Contracts) module schema and stores WIP (work in process) by customer information used in contract and order management reporting.

The package is classified as a PUB (Public) API, meaning it is intended for external invocation by other Oracle EBS modules, concurrent programs, or custom code. The package header is identified by the revision string "$Header: OKIPWBCS.pls 115.6 2002/12/01 17:53:53 rpotnuru noship $" and was originally created on 16-July-2001 by the developer Mezra, with a later NOCOPY modification by rpotnuru on 26-NOV-2002. Notably, the package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than as the package owner.

Key Procedures and Functions

The package exposes a single documented public procedure:

• CRT_WIP_BY_CUST — The primary procedure that creates the WIP by customer records. As documented, its out parameters (error buffer and return code) are deliberately listed first due to restrictions imposed by the Oracle Concurrent Manager. Input parameters include a period set name, a period type, and a summary build date. The procedure populates the OKI_WIP_BY_CUSTOMERS table based on the specified accounting period and build date criteria, following the standard concurrent program interface conventions where the error buffer and return code are used to communicate status back to the Concurrent Manager.

Tables Accessed

The documented table load target is OKI_WIP_BY_CUSTOMERS. The package's purpose is to populate this table with WIP and customer-related records generated on a periodic basis. Because ETRM metadata documents the table reference via APPS synonyms, the package reads and writes through the APPS schema synonym namespace. Beyond this primary table, the procedure likely sources its data from period-related and transactional base tables that support the period set name, period type, and summary build date parameters, though only the OKI_WIP_BY_CUSTOMERS load target is explicitly documented.

Usage Notes

OKI_LOAD_WBC_PUB is typically invoked through a concurrent program registration, since its CRT_WIP_BY_CUST procedure is structured to comply with the Concurrent Manager's parameter conventions (out parameters first). The three input parameters — period set name, period type, and summary build date — are supplied by the concurrent program definition at submission time.The package is not referenced by any other documented packages, which confirms it is designed as a top-level entry point rather than a shared utility called by sibling APIs. In custom code, the procedure can be called directly if the caller supplies the period set name, period type, and build date, provided the caller has sufficient privileges to write to the OKI_WIP_BY_CUSTOMERS table. Because the package uses AUTHID CURRENT_USER, callers must hold the necessary object privileges on the target table in their own right. This API is most relevant to implementers extending the OKI contracts module or building custom WIP-by-customer reporting, and it should be scheduled consistently with period close activities so that the summary build date aligns with the accounting period being reported.