Search Results pa_pjc_cwk_utils




Overview
Explore in AI Chat

Overview

PA_PJC_CWK_UTILS is an Oracle EBS Applications (APPS) schema package body that supports the Project Costing and Project Billing functionality surrounding rate-based and cross-charge ("CWK," understood as cross-charge/rate workbench) processing. In Oracle Projects, cross-charge transactions govern the transfer of costs and revenue between a provider organization and a receiver organization, and rate-based processing governs the derivation of burden and revenue amounts from cost bases and rate schedules. This utility package encapsulates the shared decision logic that determines whether a given distribution line qualifies for rate-based handling, whether an existing project cross-charge relationship exists, and whether cross-charge interfacing is permitted at the current point in the process. Because the object is a package body with no documented public specification listed in the metadata, its procedures and functions are consumed internally by the Oracle Projects Costing and cross-charge engine rather than being a formally published public API. The ETRM documentation classifies the package with an API classification of OTHER and records it as VALID in release 12.2.2, consistent with its role as a stable, internally referenced utility component across 12.1.1 and 12.2.2.

Key Procedures and Functions

Three documented program units are exposed by this package body. Parameter lists are not documented in the ETRM metadata and are therefore not reproduced here.

  • IS_RATE_BASED_LINE — Determines whether a given cost distribution line should be treated as rate-based. This drives the downstream decision to apply rate schedules (for burden, revenue, or both) rather than passing the raw cost through unchanged. It centralizes the classification logic so that costing and cross-charge routines reach a consistent determination.
  • EXISTS_PRJ_CWK_RBTC — Tests for the existence of a project cross-charge relationship pertinent to the transaction under evaluation, ensuring that cross-charge processing is only initiated where a valid provider/receiver arrangement is defined.
  • IS_CWK_TC_XFACE_ALLOWED — Returns whether cross-charge interfacing to the relevant transaction currency or threshold-crossing interface is currently permitted. This provides a gate that prevents inappropriate interface activity when the implementation or project setup does not allow it.

Tables Accessed

The package references the following objects through APPS synonyms and dependencies:

  • PA_IMPLEMENTATIONS_ALL — Supplies implementation-level setup and operating unit context, used to confirm that the Projects implementation prerequisites for rate-based or cross-charge processing are satisfied.
  • PA_PROJECTS_ALL — Provides project definition attributes, including the cross-charge and rate configuration that the existence and allowance checks depend upon.
  • PO_DISTRIBUTIONS_ALL — The purchasing distribution source for expenditure items flowing into Oracle Projects, read to evaluate the incoming distribution line before rate-based classification.
  • DUAL — Used for single-row evaluations where no table access is otherwise required.
  • PLITBLM — The standard PL/SQL table (index-by table) dummy referenced by PL/SQL compilation.

Dependencies also include PA_PLSQL_DATATYPES (shared datatype declarations) and PO_PA_INTEGRATION_GRP, indicating integration with the Purchasing-to-Projects expenditure flow.

Usage Notes

PA_PJC_CWK_UTILS is invoked indirectly rather than through a user-facing form. Its documented callers are other PL/SQL packages — the metadata records it as referenced by 19 database objects — which are themselves triggered during Oracle Projects costing, cross-charge, and interface processing. Typical invocation points include the Cost Distribution and cross-charge generation routines that fire when Expenditure Items are processed, and the Purchasing integration flow that inserts distributions from PO_DISTRIBUTIONS_ALL into Projects. Because the package is not catalogued as a formal public API, custom extensions should avoid calling it directly; instead, implementations should rely on the supported Oracle Projects APIs and let the standard engine reach these utility checks. Administrators troubleshooting rate-based or cross-charge exceptions can use the function names as diagnostic markers in trace files and error logs, since a false return from EXISTS_PRJ_CWK_RBTC or IS_CWK_TC_XFACE_ALLOWED typically explains why a distribution was bypassed for cross-charge interfacing.