Search Results burden_sum_rejection_code




Overview
Explore in AI Chat

Overview

APPS.PA_GL_COST_EXCEPT_SUM_V is a reporting view in Oracle E-Business Suite (validated against 12.1.1 and 12.2.2) that consolidates cost distribution exception data generated during the interface of project expenditures from Oracle Projects to Oracle General Ledger. Its purpose is to present, in a single denormalized result set, every cost distribution line that may require attention before it can be successfully transferred to the GL, together with the descriptive exception reason and corrective action recommended by Oracle Projects.

The view is exposed under the APPS schema and is typically consumed by Oracle Projects inquiry screens, by the cost exception reporting functionality, and by custom extracts built for month-end close monitoring. It is especially relevant to implementers who investigate the burden_sum_rejection_code search term: the view translates a null burden summary rejection code into the sentinel value BURDEN_NEW_UNPROC so that unprocessed burden records surface alongside explicit cost exceptions.

Underlying Base Objects

The documented base objects referenced by this view are:

The join between PA_EXPENDITURE_ITEMS_ALL and PA_COST_DISTRIBUTION_LINES_ALL on expenditure item ID forms the spine of the view, with the exception rules applied through a decode across the two exception types.

Key Columns

Common Use Cases and Queries

The view is commonly used to list all distributions blocked from the GL interface and to isolate burden summary rejections. A typical query is:

  • SELECT expenditure_item_id, cost_distribution_line_num, transfer_status_code, exception_reason, corrective_action FROM apps.pa_gl_cost_except_sum_v WHERE transfer_rejection_reason IS NOT NULL;
  • Filtering by burden: add WHERE cdl_exception_type = 'B' to review burden summary rejections such as BURDEN_NEW_UNPROC.
  • Reconciling to Projects: join back to PA_EXPENDITURE_ITEMS_ALL or PA_PROJECTS_ALL using TASK_ID for reporting against a project or task.

Because the exception text is derived dynamically through the package, results reflect the current setup of exception reasons and corrective actions, making the view suitable for operational close monitoring rather than historical archiving.