Search Results zpb_fnd_util

Overview

ZPB_FND_UTIL is a utility package owned by the APPS schema in Oracle E-Business Suite. The "ZPB" prefix associates it with the Oracle Advanced Supply Chain Planning and Demand Planning product family — historically the ZPB module relates to the planning and forecasting engines within EBS, including the Demand Planner and related supply chain planning components. The "_FND_UTIL" suffix indicates a foundational utility package whose responsibility is to provide shared helper routines that are consumed by the surrounding ZPB application code rather than exposing business-facing functionality directly.

In ETRM terms, the package is classified as an API of type UTIL. It is documented as VALID, meaning the compiled package body exists and no invalid dependencies were detected at the time of metadata capture. As a utility package, ZPB_FND_UTIL does not own business data. It centralizes common logic — in this case, retrieving the status of a submitted request — so that multiple ZPB programs can determine the outcome of concurrent processing without duplicating that logic.

Key Procedures and Functions

The documented ETRM metadata lists exactly one exposed program unit:

• GET_REQUEST_STATUS — A function or procedure that obtains the current status of a concurrent request. It is intended to give callers a single, reusable point of access to request-state information so the caller does not have to query the Oracle Concurrent Manager tables directly. Consistent with its UTIL classification, the routine returns or reports status rather than modifying any request. The metadata does not publish a formal parameter list, and no signature should be assumed beyond the name and this described purpose.

No additional procedures or functions are enumerated in the documented metadata. The package therefore provides a narrow, single-purpose utility surface.

Tables Accessed

The documented metadata records no tables referenced through APPS synonyms. This is consistent with a utility package that resolves concurrent request status through standard EBS foundation objects. In practice, ZPB_FND_UTIL would be expected to read from the Oracle Concurrent Manager foundation views, chiefly FND_CONCURRENT_REQUESTS, which holds request phase and status codes (for example, PHASE_CODE and STATUS_CODE) along with the request identifier. Because the metadata does not list explicit synonyms, any table access should be confirmed from the package body in the customer's environment rather than assumed. No INSERT, UPDATE, or DELETE activity is documented, which aligns with the read-only nature of a status-retrieval utility.

Usage Notes

ZPB_FND_UTIL is an internal support package. According to the dependency metadata, it references SYS.STANDARD and is itself listed as dependent on ZPB_FND_UTIL, a self-referential entry typical of utility code that calls its own routines. Notably, the metadata records that it is referenced by zero other packages, suggesting that within the scanned ETRM footprint the package is not called by other documented package objects; its callers are more likely forms, concurrent programs, or standalone custom code outside the captured dependency set.

Typical invocation scenarios include:

• ZPB planning concurrent programs polling the status of dependent sub-requests before proceeding.
• Customized Oracle EBS extensions or client extensions in Demand Planning that need to confirm completion of a submitted request.
• Diagnostic scripts that report the state of ZPB-related concurrent jobs.

Because the package is a utility and is not documented as a public interface, direct invocation from custom code should be treated cautiously. Oracle does not guarantee backward compatibility for internal utility routines across releases; the recommended approach is to inspect the package specification in the target environment (12.1.1 or 12.2.2) and, where possible, use supported public APIs such as FND_CONCURRENT or FND_REQUEST itself. Any custom call to GET_REQUEST_STATUS should be validated against the installed package signature, as the ETRM excerpt does not publish one.