Results for “pa_deductions_all”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_DEDUCTIONS_ALL is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores summary information about deduction requests raised against suppliers. In project procurement and supplier management flows, this table captures the amounts an organization intends to withhold, recover, or offset from supplier payments — for example, penalties, back-charges, retainage recovery, or quality-related deductions. Each row represents a single deduction request and ties together the project, the supplier, the related purchasing document, and the related control item. The table is owned by the PA schema and is documented as VALID with 27 columns in the 12.2.2 physical schema.

From a heuristic Data Vault modeling perspective, the relationship metadata classifies PA_DEDUCTIONS_ALL as standalone. This suggests treating it as a candidate satellite or hub-like entity that does not participate in an extensive foreign-key network — it is not a pure transactional link table and is best modeled as a descriptive/aggregate record keyed on its own business identifiers.

Key Information Stored

The primary surrogate key is DEDUCTION_REQ_ID, uniquely enforced by index PA_DEDUCTIONS_ALL_U1. Two documented unique indexes act as business-key candidates: PA_DEDUCTIONS_ALL_U1 on DEDUCTION_REQ_ID and PA_DEDUCTIONS_ALL_U2 on DEDUCTION_REQ_NUM. The most operationally significant columns include:

• DEDUCTION_REQ_NUM — the human-readable deduction request identifier.
• PROJECT_ID — the project against which the deduction is booked.
• VENDOR_ID and VENDOR_SITE_ID — the supplier and site subject to the deduction.
• CI_ID — foreign key to PA_CONTROL_ITEMS, linking the deduction to a control item.
• PO_HEADER_ID and PO_NUMBER — the purchasing document referenced by the deduction.
• CHANGE_DOC_NUM and CHANGE_DOC_TYPE — the change document driving the deduction.
• DEBIT_MEMO_NUM and DEBIT_MEMO_DATE — the associated debit memo details.
• TOTAL_AMOUNT and TOTAL_PFC_AMOUNT — the total deduction value and its project functional currency amount.
• CURRENCY_CODE, CONVERSION_RATE, CONVERSION_RATETYPE, and CONVERSION_RATEDATE — the currency and conversion parameters applied.
• STATUS and DOCUMENT_TYPE — the processing state and classification of the request.
• ORG_ID — the operating unit, supporting multi-org security.
• CREATION_DATE, CREATED_BY, LAST_UPDATION_DATE, LAST_UPDATED_BY — standard audit columns.

Common Use Cases and Queries

Typical reporting includes deduction aging, deduction totals by supplier, and reconciliation of debit memos against purchasing documents. A supplier-level aggregation illustrates standard usage:

SELECT VENDOR_ID, CURRENCY_CODE, SUM(TOTAL_AMOUNT) TOTAL_DEDUCTED
FROM PA_DEDUCTIONS_ALL
WHERE ORG_ID = :p_org_id
AND STATUS = :p_status
GROUP BY VENDOR_ID, CURRENCY_CODE;

Analysts frequently join PA_CONTROL_ITEMS via CI_ID to trace the originating control item, and filter by DEDUCTION_REQ_DATE or DEBIT_MEMO_DATE for period-based reporting. Project managers query by PROJECT_ID, while AP and procurement teams reconcile by PO_NUMBER or DEBIT_MEMO_NUM.

Related Objects

The documented foreign key links PA_DEDUCTIONS_ALL.CI_ID to PA_CONTROL_ITEMS. Beyond that documented relationship, integration assumptions include PA_PURCHASE_ORDERS and PO_HEADERS_ALL via PO_HEADER_ID/PO_NUMBER, PO_VENDORS and PO_VENDOR_SITES_ALL via VENDOR_ID and VENDOR_SITE_ID, PA_PROJECTS_ALL via PROJECT_ID, and GL currency conversion views through CURRENCY_CODE and CONVERSION_RATE. Applications typically surface this data through Projects supplier management and AP debit memo flows rather than a dedicated public API.