Search Results dpp_trans_int_line_id_seq

Overview

APPS.DPP_TRANSACTION_PVT is a private PL/SQL package body belonging to the Oracle E-Business Suite Procurement and Payables family of modules, specifically supporting the supplier payment and invoice transaction flow commonly associated with Oracle Payables and its associated payment transaction infrastructure. The PVT suffix designates this package as an internal, non-public API implementation: it exposes the procedural logic that public packages in the same schema call into, rather than serving as a directly documented integration point for external developers. The package is VALID in the APPS schema, confirming it compiles cleanly against the referenced dependencies.

The package encapsulates the core create, insert, and inbound processing logic for payment transactions, bridging header and line staging structures with the base transaction tables. It also publishes outbound business events through the Oracle Workflow event system, enabling subscribing applications to react to transaction state changes.

Key Procedures and Functions

The metadata documents six procedures within this package body:

• CREATE_TRANSACTION — Orchestrates the creation of a new transaction record, assembling header and line data for persistence.
• INSERT_TRANSACTION — Performs the physical insert of transaction header and line rows into the base tables, drawing sequence values as needed.
• RAISE_OUTBOUNDEVENT — Publishes a WF_EVENT to the Oracle Workflow Business Event System to signal downstream subscribers that a transaction event has occurred.
• INBOUND_TRANSACTION — Accepts and processes transactions arriving from an external or upstream source into the interface tables.
• CREATE_WEBADI_TRANSACTION — Creates transactions originating from Web ADI (Application Desktop Integrator) uploads, a common supplier self-service entry path.
• INBOUND_APPROVAL — Handles the approval lifecycle step for inbound transactions, validating and advancing status.

No parameter signatures are reproduced here, as the documented metadata does not publish them.

Tables Accessed

The package reads and writes base transaction tables including DPP_TRANSACTION_HEADERS_ALL, DPP_TRANSACTION_LINES_ALL, and DPP_TRANSACTION_CLAIMS_ALL. It draws primary keys from the sequences DPP_TRANSACTION_HDR_ID_SEQ, DPP_TRANSACTION_LINE_ID_SEQ, and notably DPP_TRANSACTION_NUMBER_SEQ — the sequence referenced in the user's search — which supplies the human-readable transaction number. Interface and integration staging is handled through DPP_TXN_HEADERS_INT_ALL, DPP_TXN_LINES_INT_ALL, and the DPP_TRANS_INT_HDR_ID_SEQ / DPP_TRANS_INT_LINE_ID_SEQ sequences. Supplier context is resolved via AP_SUPPLIERS, AP_SUPPLIER_SITES, and AP_SUPPLIER_SITES_ALL. Currency, set of books, and operating unit context come from FND_CURRENCIES, GL_SETS_OF_BOOKS, and HR_OPERATING_UNITS, while FINANCIALS_SYSTEM_PARAMS_ALL and MO_GLOBAL supply environment and multi-org defaults.

Usage Notes

As a PVT (private) API, DPP_TRANSACTION_PVT is not intended for direct invocation by customer extensions. It is invoked internally by its sibling public packages and by concurrent programs and Oracle Forms that manage payment transactions and Web ADI imports. The presence of FND_MSG_PUB, FND_API, and FND_LOG dependencies indicates standard EBS error-handling and debug-logging conventions are applied throughout. Because the sequence DPP_TRANSACTION_NUMBER_SEQ governs transaction numbering, organizations seeking to understand or reset transaction number generation should inspect this package alongside that sequence.