Search Results burden_sum_rejection_code




Overview
Explore in AI Chat

Overview

PA_CMT_BURDEN_SUM_ERROR_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the Projects (PA) module. Its purpose is to expose all commitment transactions that failed during the burden summarization process. Burden summarization is the batch process that computes and applies burden (indirect cost) amounts to commitment transactions so that the indirect costs are reflected in project cost reporting. When a commitment transaction cannot be burdened successfully, the process assigns it a rejection code and stores it rather than discarding it. This view surfaces those failed transactions together with a decoded explanation of the rejection reason, making the errors available for investigation, reporting, and correction. Because the view stores no data itself and is not a base table, it is read-only and is intended for querying and reporting rather than transactional maintenance.

Underlying Base Objects

The view is defined over the following documented objects:

  • PA_COMMITMENT_TXNS (synonym) — the primary transactional source holding commitment transactions, their burden summary source run information, and the rejection code.
  • PA_LOOKUPS (view) — supplies the decoded meaning and description for the rejection code via lookup type BURDEN_SUM_REJECTION_CODE.
  • PA_PROJECTS_ALL (synonym) — provides project identification and segment values.
  • PA_PROJECT_TYPES_ALL (synonym) — supplies the project type classification.
  • PA_TASKS (synonym) — supplies task identifiers and task numbers.

The joins are driven by project type, organization, project, and task keys, with the lookup join translating the code into readable text. Critically, the query filters on CMT.BURDEN_SUM_REJECTION_CODE IS NOT NULL, CMT.LINE_TYPE = 'R', and CMT.BURDEN_SUM_SOURCE_RUN_ID = -9999, meaning only rejected commitment lines flagged by the summarization process are returned.

Key Columns

  • PROJECT_TYPE, PROJECT_ID, SEGMENT1 — project type and project identification, with SEGMENT1 typically the project number.
  • TASK_ID, TASK_NUMBER — the task against which the commitment was recorded.
  • PA_PERIOD — the accounting period of the transaction.
  • TRANSACTION_SOURCE, EXPENDITURE_TYPE, LINE_TYPE, CMT_NUMBER — the source, expenditure classification, line type, and commitment document number.
  • EXPENDITURE_ITEM_DATE — the expenditure item date of the commitment line.
  • ORIGINAL_TXN_REFERENCE1/2/3 — reference attributes identifying the original transaction.
  • BURDEN_SUM_SOURCE_RUN_ID — the run identifier of the burden summarization process; the sentinel value -9999 identifies failed rows.
  • BURDEN_SUM_REJECTION_CODE — the coded reason the transaction was rejected.
  • MEANING, DESCRIPTION — decoded text for the rejection code from PA_LOOKUPS.

Common Use Cases and Queries

This view is most often used to diagnose why commitment burden summarization did not complete for certain transactions, and to report on outstanding errors by project, task, or period. A typical query lists all rejected commitments with their decoded reasons:

  • SELECT project_id, segment1, task_number, cmt_number, burden_sum_rejection_code, meaning FROM pa_cmt_burden_sum_error_v;
  • Filter by period: SELECT * FROM pa_cmt_burden_sum_error_v WHERE pa_period = 'JAN-24';
  • Group to identify systemic causes: SELECT burden_sum_rejection_code, meaning, COUNT(*) FROM pa_cmt_burden_sum_error_v GROUP BY burden_sum_rejection_code, meaning;
  • Restrict to a project: SELECT * FROM pa_cmt_burden_sum_error_v WHERE segment1 = 'P-1001';

Because the view already decodes MEANING and DESCRIPTION, administrators can rapidly categorize failures and correct the underlying commitment transactions before re-running burden summarization.