Search Results client_column_values




Overview
Explore in AI Chat

Overview

PA_CLIENT_EXTN_BURDEN_RESOURCE is a client extension package body in Oracle EBS Projects (PA) that provides a supported customization hook for burden and resource grouping logic in expenditure and commitment processing. The package is owned by APPS and is classified as an "OTHER" API, meaning it is not a released public interface but rather a stub designed for customer extension. In releases 12.1.1 and 12.2.2, this package allows implementers to inject site-specific grouping criteria into the cost burdening and expenditure distribution flow without modifying Oracle seeded code.

The body contains two documented program units, CLIENT_GROUPING and CLIENT_COLUMN_VALUES. Both follow the standard Oracle client-extension pattern: Oracle ships an empty or pass-through implementation, and customers modify the body (typically through a copy in a custom schema or an applied patch) to apply business-specific rules. The package therefore occupies a controlled customization boundary, protecting core PA logic across upgrades.

Key Procedures and Functions

  • CLIENT_GROUPING — A function that returns a VARCHAR2 value used as the grouping method or grouping key for burden and resource processing. It accepts a set of optional identifier parameters drawn from expenditure items and commitment transactions, covering job, non-labor resource, resource organization, WIP resource, incurred-by person, inventory item, vendor, and BOM equipment/labor resources. Oracle's base implementation returns a NULL grouping method and simply checks the PA_RPT_BTC_SRC_RESRC profile option; if that profile is set to 'Y', it routes through a placeholder block where clients insert additional grouping criteria. The function supports the burden transaction cost source resource (BTC) logic used in burdening calculations.
  • CLIENT_COLUMN_VALUES — A procedure that receives the same family of identifier parameters as IN OUT NOCOPY arguments, allowing the extension to read and, where appropriate, override the incoming column values used for burden and resource derivation. The NOCOPY hint reflects performance intent by passing large values by reference. Like CLIENT_GROUPING, the base body is a client-customization stub; the actual derivation logic is expected to be supplied by the implementer. The searched term "client_column_values" refers directly to this procedure, which is the documented entry point for adjusting resource and expenditure column values.

Tables Accessed

  • PA_EXPENDITURE_ITEMS_ALL — The primary source of expenditure item attributes such as job_id, non_labor_resource, organization_id, wip_resource_id, and inventory_item_id, which feed the grouping and column value logic.
  • PA_EXPENDITURES_ALL — Provides expenditure header attributes, notably incurred_by_person_id, used for personnel-based grouping or validation.
  • PA_COMMITMENT_TXNS — Supplies commitment transaction data including vendor_id and BOM equipment/labor resource identifiers, enabling consistent treatment of committed costs alongside actual expenditures.

All are referenced through APPS synonyms, indicating the package executes in the APPS schema against the standard PA data model.

Usage Notes

PA_CLIENT_EXTN_BURDEN_RESOURCE is invoked internally by Oracle's burden and resource processing modules when the PA_RPT_BTC_SRC_RESRC or related profile options are enabled. It is not called directly from Oracle Forms or concurrent programs; rather, it is called from seeded PA code that expects a grouping method or adjusted column values during cost distribution, burdening, and reporting extract generation. Referenced by four other packages, it acts as an extensibility point within the burden computation chain.

Implementers typically customize the package body after cloning, applying changes through a custom patch or by copying the body into a supported customization schema. Because the base body is intentionally minimal, any custom logic must be reapplied after upgrades or patches that refresh the package. Validation of changes should be performed in a non-production environment, since incorrect grouping values can distort burdened cost calculations and expenditure reporting.