Search Results cost_distribution_override_id

Overview

The PA_COST_DIST_OVERRIDES table is a configuration table within the Oracle E-Business Suite Projects (PA) module. Its primary role is to provide a mechanism for overriding the standard expenditure organization derived by AutoAccounting during the costing and accounting processes. In standard project financial flows, AutoAccounting rules determine the organization used for cost distribution based on attributes of the expenditure item. This table allows for specific, project-level exceptions to those rules, enabling organizations to direct costs to an accounting organization different from the one that would be automatically assigned. This functionality is critical for complex enterprise structures where cost management and reporting may require charges to be booked to an organization other than the one incurring the expenditure.

Key Information Stored

The table stores the relationships that define an override configuration. Its structure centers on mapping a source context to a target organization. The primary identifier is the COST_DISTRIBUTION_OVERRIDE_ID. The core configuration is defined by the PROJECT_ID, which ties the rule to a specific project. The OVERRIDE_FROM_ORGANIZATION_ID specifies the source expenditure organization to be overridden. The OVERRIDE_TO_ORGANIZATION_ID defines the target organization to which costs should be redirected. For more granular control, the EXPENDITURE_CATEGORY column can be used to apply the override only to specific types of expenditures. Additional standard columns, such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY, track the audit history of each record.

Common Use Cases and Queries

A primary use case is managing inter-organizational or corporate chargebacks, where costs incurred by one department must be allocated to a different consuming or funding department. Another scenario involves standardizing accounting for a program managed by a central team, where all costs across multiple executing organizations are consolidated into a single reporting entity. Administrators or implementers often query this table to audit existing overrides or troubleshoot accounting issues. A typical diagnostic query would join to project and organization tables for readability:

• SELECT p.segment1 project_number, hou_from.name from_org, hou_to.name to_org, ec.expenditure_category
  FROM pa_cost_dist_overrides cdo,
  pa_projects_all p,
  hr_all_organization_units hou_from,
  hr_all_organization_units hou_to,
  pa_expenditure_categories ec
  WHERE cdo.project_id = p.project_id
  AND cdo.override_from_organization_id = hou_from.organization_id
  AND cdo.override_to_organization_id = hou_to.organization_id
  AND cdo.expenditure_category = ec.expenditure_category(+);

Related Objects

The PA_COST_DIST_OVERRIDES table maintains defined foreign key relationships with several core tables, as documented in the ETRM. These relationships are fundamental to its integrity and function:

• PA_PROJECTS_ALL: Joined via PA_COST_DIST_OVERRIDES.PROJECT_ID. This links each override rule to a specific project.
• HR_ALL_ORGANIZATION_UNITS (From Organization): Joined via PA_COST_DIST_OVERRIDES.OVERRIDE_FROM_ORGANIZATION_ID. This validates the source expenditure organization being overridden.
• HR_ALL_ORGANIZATION_UNITS (To Organization): Joined via PA_COST_DIST_OVERRIDES.OVERRIDE_TO_ORGANIZATION_ID. This validates the target accounting organization.
• PA_EXPENDITURE_CATEGORIES: Joined via PA_COST_DIST_OVERRIDES.EXPENDITURE_CATEGORY. This allows the override to be scoped to a particular category of cost.

This table is referenced by the costing engine within the Projects module, particularly during the cost distribution and transfer to General Ledger processes, where it is read to apply the configured organizational overrides before posting.