Search Results pa_deductions_w

Overview

APPS.PA_DEDUCTIONS_W is a public PL/SQL package in Oracle EBS Projects (PA) that exposes the deductions business logic for Oracle Forms and other Java-based or Web ADI clients. It belongs to the Projects Management suite and operates on deduction header and transaction records that represent amounts withheld from supplier invoices, expense reports, or other project-related payments in the context of project accounting and payables integration. The package is declared with AUTHID CURRENT_USER, so all SQL executed inside it runs with the privileges of the calling schema rather than the definer, which is significant for APPS-based invocations where synonyms and grants must be in place. The "_W" suffix is the Oracle Applications convention for a wrapper package generated to support the Rosetta/Forms-over-Java bridge, allowing a Java or middle-tier client to pass and receive PL/SQL table types across the JDBC boundary. The package represents the documented, supported entry point for creating, updating, deleting, and validating deduction headers and lines, and it shields callers from the underlying PA_DEDUCTIONS package internals.

Key Procedures and Functions

The documented API surface consists of sixteen procedures, split into the Rosetta bridge utilities and the business operations. The bridge procedures copy data between the JTF table types used by the Java layer and the PL/SQL collections defined in PA_DEDUCTIONS.

• ROSETTA_TABLE_COPY_IN_P0 / ROSETTA_TABLE_COPY_OUT_P0 — Copy the deduction header ID table (g_dctn_hdrid) in and out of the JTF_NUMBER_TABLE format.
• ROSETTA_TABLE_COPY_IN_P1 / ROSETTA_TABLE_COPY_OUT_P1 — Copy the deduction transaction ID table (g_dctn_txnid) between JTF_NUMBER_TABLE and the PA_DEDUCTIONS collection.
• ROSETTA_TABLE_COPY_IN_P4 / ROSETTA_TABLE_COPY_OUT_P4 — Copy the full deduction header attribute record (g_dctn_hdrtbl) across the bridge, spanning numeric, varchar2, and date columns.
• ROSETTA_TABLE_COPY_IN_P5 / ROSETTA_TABLE_COPY_OUT_P5 — Copy the deduction transaction attribute record set, the counterpart to P5 for line-level data.
• CREATE_DEDUCTION_HDR — Creates a deduction header, establishing the controlling record for one or more deduction lines.
• CREATE_DEDUCTION_TXN — Creates a deduction transaction (line) associated with a header.
• UPDATE_DEDUCTION_HDR — Updates existing header attributes.
• UPDATE_DEDUCTION_TXN — Updates existing transaction attributes.
• DELETE_DEDUCTION_HDR — Removes a deduction header, typically with its dependent transactions.
• DELETE_DEDUCTION_TXN — Removes an individual deduction transaction.
• VALIDATE_DEDUCTION_HDR — Performs business-rule validation on header data before insert or update.
• VALIDATE_DEDUCTION_TXN — Performs business-rule validation on transaction data. This is the procedure most commonly referenced by callers searching the "validate_deduction_txn" pattern, and it is invoked to confirm that a deduction line is internally consistent and legally allowed before the DML procedures persist it.

Tables Accessed

The ETRM metadata lists PLITBLM as the referenced table via an APPS synonym. PLITBLM is the Oracle Applications temporary/interface table used by the PL/SQL table-handling utility layer that supports the Rosetta bridge; it is not a base application table and stores transient data needed for passing PL/SQL tables between the Java middle tier and the database. The deduction header and transaction records ultimately live in PA_DEDUCTIONS-owned base tables accessed through the package body, but only PLITBLM is documented in the metadata excerpt provided. Readers should treat PLITBLM as infrastructure rather than a transactional store, and should not build custom reports directly against it.

Usage Notes

PA_DEDUCTIONS_W is normally invoked indirectly. Oracle Forms and the Oracle E-Business Suite middle-tier services call the Rosetta bridge procedures to marshal a PL/SQL table of deduction records across JDBC, then the corresponding CREATE, UPDATE, DELETE, and VALIDATE procedures execute the business logic. Typical declarative callers are Deductions setup forms and any deduction maintenance screens in Projects. Custom integrations and extensions may call the business procedures directly from PL/SQL to load or adjust deductions, but because the package is AUTHID CURRENT_USER, the invoking schema must hold EXECUTE on PA_DEDUCTIONS_W and the necessary object privileges on PA_DEDUCTIONS and PLITBLM. The validate procedures should be called before create and update calls so that business-rule violations are handled as return errors rather than failed DML. The package is referenced by zero other packages per the documented metadata, indicating it sits at the top of the call chain for deduction maintenance rather than acting as a shared internal library.