Search Results invoice_dm_map

Overview

APPS.PA_DEDUCTIONS is a server-side PL/SQL package in Oracle Projects that manages the deduction workflow used to recover amounts from suppliers through debit memos. A deduction represents an adjustment against a supplier, typically raised when project expenditures must be recovered because of over-billing, supplier errors, or contractual offsets. The package exposes the full lifecycle of a deduction request: header and transaction creation, maintenance, validation, submission to Oracle Payables for debit memo generation, and the import of vendor debit memos back into Projects. The package is defined with AUTHID CURRENT_USER and is classified as OTHER in the ETRM metadata.

The source declares strongly typed cursor and collection structures (including g_dctn_hdr_rec and g_dctn_txn_rec) that mirror the columns of the deduction header and transaction tables, and a private cursor over PA_DEDUCTIONS_ALL that restricts processing to records with a status of WORKING, REJECTED, or FAILED. This reflects the package's role as a validation and staging engine rather than a purely transactional API.

Key Procedures and Functions

• CREATE_DEDUCTION_HDR / CREATE_DEDUCTION_TXN — Establish a new deduction request header and its associated transaction lines, capturing project, supplier, purchase order, currency, amount, and dating attributes.
• UPDATE_DEDUCTION_HDR / UPDATE_DEDUCTION_TXN — Modify existing header and transaction records, typically while the deduction is still in a WORKING or REJECTED state.
• DELETE_DEDUCTION_HDR / DELETE_DEDUCTION_TXN — Remove deduction headers and their transaction lines prior to submission.
• VALIDATE_DEDUCTION_HDR / VALIDATE_DEDUCTION_TXN — Perform the business-rule checks required before a deduction may be submitted, verifying required attributes and consistency between header and lines.
• SUBMIT_FOR_DEBITMEMO — Transition a validated deduction into the submission process that produces debit memo data for Oracle Payables.
• INVOICE_DM_MAP — Builds the association between an AP invoice (debit memo) and the Projects deduction records, mapping the resulting invoice and invoice lines back to the originating deduction request and transaction identifiers.
• IMPORT_DEBITMEMO — Import debit memo information from Oracle Payables into Projects, creating or reconciling the corresponding deduction records.
• VALIDATE_UNPROCESSED_DED — Identify and validate deduction records that remain unprocessed or rejected, supporting cleanup and re-submission.

Tables Accessed

The package operates primarily on PA_DEDUCTIONS_ALL and PA_DEDUCTION_TRANSACTIONS_ALL, the header and line stores for deduction requests. It uses the sequences PA_DEDUCTIONS_DM_S and PA_DEDUCTION_TXNS_S to generate surrogate keys. Integration with Payables involves AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS_ALL, AP_INVOICE_LINES_ALL, the interface tables AP_INVOICES_INTERFACE, AP_INVOICE_LINES_INTERFACE, and their _S counterparts, with AP_INTERFACE_REJECTIONS recording failed import rows. PA_PROJECTS_ALL and PA_EXPEND_TYP_SYS_LINKS supply project and expenditure type validation context, while FND_LOOKUP_VALUES provides reference lookup values used during validation.

Usage Notes

PA_DEDUCTIONS is typically invoked from the Oracle Projects deduction entry forms, from concurrent programs that submit deductions for debit memo creation and import vendor debit memos, and from custom extensions. Because INVOICE_DM_MAP and IMPORT_DEBITMEMO mediate the Payables round-trip, the package is most relevant when diagnosing why a deduction failed to produce a debit memo or why an imported invoice did not reconcile to its deduction. Three other packages reference PA_DEDUCTIONS, confirming its role as a shared dependency within the Projects deductions subsystem.