Search Results purchase_classification_code
Overview
POA_CUSTOMIZATION_PKG is an APPS-owned PL/SQL package that forms part of the Oracle E-Business Suite Procurement and Oracle Advanced Procurement (POA) product family. Its name and its documented dependency footprint indicate that it serves as a customization and validation layer supporting the Procurement data-warehouse collection and supplier-performance reporting architecture. The package is classified under the ETRM as an "OTHER" API type, meaning it is not a formally published public API but rather an internal utility that other procurement packages invoke to derive or validate classification and pricing attributes.
The package does not own any base tables of its own. Instead, it exposes reusable logic that other procurement views and collection packages call at runtime. This design allows Oracle to centralize custom derivation rules — for example, purchase classification and target-price logic — in a single package, avoiding duplication across the multiple materialized views and fact-collection views that consume it.
Key Procedures and Functions
Two procedures/functions are documented in the ETRM metadata for this package:
- PURCHASE_CLASSIFICATION_CODE — Derives or returns a purchase classification code value. This logic supports the classification of purchasing transactions, which is used downstream by procurement reporting and supplier-performance fact views. The exact input and output parameters are not exposed in the ETRM excerpt and should not be assumed.
- GET_TARGET_PRICE — Returns a target-price value used in procurement analysis. Target price is a standard procurement analytical measure that compares negotiated or expected pricing against actual transaction pricing. As with the preceding function, the parameter list is not documented in the available metadata.
Both routines are internal helpers; consumers should treat them as supporting logic rather than as stable public interfaces.
Tables Accessed
The ETRM dependency information records only SYS and STANDARD as referenced objects, and lists no application tables through APPS synonyms. This indicates that POA_CUSTOMIZATION_PKG performs no direct DML against procurement base tables. Its logic is therefore either purely computational or relies on values passed in by its callers. Any data retrieval is expected to occur in the calling view or collection program, with the package acting on the supplied context.
Usage Notes
POA_CUSTOMIZATION_PKG is referenced by four other APPS packages/views, which define its practical invocation surface:
- POABV_EDW_RECEIVING_TXN_FCV
- POABV_EDW_SUPPLIER_PERFORM_FCV
- POA_EDW_RECEIVING_TXN_FCV
- POA_EDW_SUPPLIER_PERFORM_FCV
These are EDW (Enterprise Data Warehouse) collection views for receiving transactions and supplier performance. The package is therefore exercised chiefly during procurement data-warehouse collection runs, most likely through concurrent programs that refresh or populate the associated fact and collection views. It is not typically invoked from a standard EBS form. Custom code should call it only with caution, since it is not a published API and its behavior is tied to the collection views that Oracle ships. Because the package is VALID in both 12.1.1 and 12.2.2, it remains available across those releases, but its internal procedures should be treated as unsupported for external modification.