Search Results crt_wip_by_cust




Overview
Explore in AI Chat

Overview

The APPS.OKI_LOAD_WBC_PUB package body is a public Oracle EBS API responsible for creating and loading Work In Process (WIP) by Customer records. It belongs to the OKI (Oracle Contracts/Order Management WIP-related) module family and is classified as a public (PUB) API, meaning it is intended to be callable from external processes such as concurrent programs, forms, and custom code. The package operates as a thin public wrapper around its private implementation package, OKI_LOAD_WBC_PVT, delegating the substantive business logic to that private layer while exposing a controlled, supported entry point.

The core business purpose of this package is to generate summarized WIP-by-customer data for a given accounting period. This information supports downstream reporting and analysis, including aging calculations where the summary build date is treated as the "current date" for bin and aging computations.

Key Procedures and Functions

  • CRT_WIP_BY_CUST — The single documented procedure in this package. Its purpose is to create all WIP by Customer records for the specified accounting period. The procedure accepts a period set name, period type, and a summary build date supplied as a character string (VARCHAR2). Before processing, it converts the incoming summary build date from its string representation into a true DATE datatype using the standard FND concurrent date conversion utility (fnd_conc_date.string_to_date). Once normalized, it invokes the private procedure oki_load_wbc_pvt.crt_wip_by_cust, forwarding the period set name, period type, the converted build date, and the standard concurrent program output parameters (error buffer and return code). The procedure returns values through the standard concurrent manager x_errbuf and x_retcode OUT parameters.

Tables Accessed

Based on the documented package metadata, no explicit base tables are directly referenced within the public package body itself. All data access is delegated to the private implementation package OKI_LOAD_WBC_PVT, which performs the actual inserts, updates, and queries against the underlying WIP-by-customer staging and summary tables. The public package acts purely as an interface and date-conversion layer, so any table-level dependencies (via APPS synonyms) reside in the private package rather than in OKI_LOAD_WBC_PUB.

Usage Notes

  • Concurrent Program invocation: The signature of CRT_WIP_BY_CUST — with x_errbuf, x_retcode, and a VARCHAR2 summary build date — is characteristic of an Oracle EBS concurrent program. This package is most typically registered and executed as a concurrent program, where the concurrent manager passes the standard output parameters and the date string is entered or defaulted by the user.
  • Date handling: Because the summary build date is received as a string, callers must supply a value in a format acceptable to fnd_conc_date.string_to_date. The converted date is also used as the effective "current date" for bin and aging calculations, so accuracy of this value directly affects aging report results.
  • Wrapper pattern: The public/private split (OKI_LOAD_WBC_PUB calling OKI_LOAD_WBC_PVT) means custom code should invoke only the PUB package to remain on a supported interface path. Direct calls to the private package are not recommended.
  • Version context: The header indicates version 115.8 (dated 2002), incorporating a NOCOPY change. The package remains compatible with Oracle EBS 12.1.1 and 12.2.2 environments.
  • Search relevance: For users searching "crt_wip_by_cust," this procedure is the documented entry point for generating WIP-by-customer summary records, and the reference above confirms it is the sole documented routine in this public package.