Search Results dpp_mtl_txn_iface_id_seq

Overview

APPS.DPP_ITEMCOST_PVT is the private implementation package body behind the Oracle EBS Distributed Process Procurement (DPP) item-costing API. In the context of Oracle E-Business Suite 12.1.1 and 12.2.2, it underpins the functionality that derives, validates, and persists item cost information flowing through DPP transaction processing, including the interface staging of cost adjustments that ultimately feed Oracle's landed cost and transaction cost accounting for procurement transactions. The private (PVT) classification indicates the package is not intended as a public integration surface; its members are exposed to the ETRM/DPP architecture mainly for internal invocation, encapsulated public wrappers, or dependent packages. Its responsibilities span reading cost master and quantity-layer data, staging costs through the CST_ITEM_CST_DTLS_INTERFACE, and writing XLA (Subledger Accounting) header and line records for downstream accounting.

Key Procedures and Functions

The documented API surface exposes a single public routine:

• UPDATE_ITEMCOST — the primary entry point that applies item cost updates within the DPP process. It coordinates the cost derivation logic, references execution details through DPP_EXECUTIONDETAILS_PVT, and produces the cost and accounting records required to complete a costing run. The metadata does not document a parameter list, so callers should treat it as an internal API and avoid hard-coding argument assumptions.

In addition to the documented routine, the body relies on several supporting private procedures and utility calls, notably through DPP_UTILITY_PVT, DPP_EXECUTIONDETAILS_PVT, and FND_API (for the standard API framework, including message handling via FND_MSG_PUB and error logging via FND_LOG).

Tables Accessed

The package touches the following documented objects and synonyms, grouped by purpose:

• Cost data: CST_ITEM_COSTS, CST_ITEM_CST_DTLS_INTERFACE, CST_COST_TYPES, CST_COST_UPDATES, and CST_QUANTITY_LAYERS — used to read existing cost records and to stage new or updated item costs and quantity-layer adjustments.
• Staging and output: DPP_TRANSACTION_LINES_ALL, DPP_OUTPUT_XML_GT, DPP_XLA_HEADERS, and DPP_XLA_LINES — the DPP transaction line store XML output global temp table, and the XLA accounting header/line entries generated by the process.
• Sequences: DPP_CST_GROUP_ID_SEQ and, notably, DPP_MTL_TXN_IFACE_ID_SEQ — the latter is the sequence referenced directly by the search term; it supplies primary keys for the DPP material-transaction interface records populated during costing.
• Definition and profile tables: BOM_PARAMETERS, MTL_PARAMETERS, MTL_SYSTEM_ITEMS_B / _KFV, MTL_MATERIAL_TRANSACTIONS, MTL_TRANSACTIONS_INTERFACE, MTL_TXN_COST_DET_INTERFACE, CST_ORGANIZATION_DEFINITIONS, ORG_ORGANIZATION_DEFINITIONS, GL_SETS_OF_BOOKS, HR_OPERATING_UNITS, and the FND profile and user/responsibility tables used for security and configuration checks.

Usage Notes

Because DPP_ITEMCOST_PVT is a PVT package, it is not a supported public integration point. It is typically invoked internally by the DPP concurrent programs and by the public API layer (for example, through DPP_EXECUTIONDETAILS_PVT) during transaction-costing runs. The package references WF_ENGINE and FND_REQUEST, indicating that it may participate in workflow-driven or concurrent-request-driven processing. Custom code should integrate at the public DPP or CST API level rather than calling this package directly. The presence of MO_GLOBAL and PER_SECURITY_PROFILES in its dependency list confirms that multi-org and security-profile context must be initialized before the routine can resolve organization-specific data correctly. The object is classified VALID in the ETRM repository and is referenced by one other package.