Search Results cleanup_transaction_temps




Overview
Explore in AI Chat

Overview

APPS.CSE_PO_RECEIPT_INTO_PROJECT is a public PL/SQL package in Oracle E-Business Suite that supports the flow of purchasing and receiving information into Oracle Projects and Oracle Installed Base. It belongs to the "CSE" (Communications/Service Enterprise, now largely subsumed into Installed Base) schema family and is designed to take receipt transaction data originating from Purchasing and Receiving and convert it into project interface records. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling session rather than its owner, which is typical of EBS public APIs that must respect the invoker's security context.

The package version string (120.1.12000000.1, dated 2007) indicates it is a long-standing component carried forward across the 12.1.1 and 12.2.2 releases. It builds on the shared structures in CSE_DATASTRUCTURES_PUB and the interface table type defined in CSE_IPA_TRANS_PKG, giving it a consistent message-oriented signature. In practice, the package is invoked when a goods receipt tied to a project-related purchase order must be reflected in Oracle Projects so that project costs, commitments, and installed base instances remain synchronized.

Key Procedures and Functions

  • DECODE_MESSAGE — Populates the outbound return status and error message, and returns a populated Rcv_Attributes_Rec_Type structure. It acts as the translation point between an inbound XNP message (header plus text) and the internal attribute structure used by the rest of the package.
  • UPDATE_CSI_DATA — The procedure most directly associated with the search term "update_csi_data". It accepts a populated receipt attribute record and returns a receipt transaction table along with standard return status and error message outputs. Its role is to refresh or synchronize the CSI (Customer/Installed Base) related data derived from the receipt attributes, producing the transaction rows that downstream processing consumes.
  • GET_RCV_TRANSACTION_DETAILS — Given a receipt transaction identifier, it retrieves the corresponding transaction details into the Rcv_Txn_Tbl_Type structure, again returning standard status and error outputs. This supports lookups and re-processing of individual receipts.
  • INTERFACE_NL_TO_PA — Takes a populated receipt transaction table and interfaces it to Oracle Projects (PA). This is the transfer step that moves validated receipt data into the Project interface layer.
  • CLEANUP_TRANSACTION_TEMPS — Accepts a receipt transaction ID and removes temporary/staging rows associated with that transaction, preventing accumulation of transient data after processing completes.

All procedures use the standard EBS return status and error message convention, leveraging FND_API constants such as G_RET_STS_SUCCESS, G_RET_STS_ERROR, and G_RET_STS_UNEXP_ERROR.

Tables Accessed

Usage Notes

This package is not typically called directly by end users. It is invoked from the receiving-to-project integration flow, and its metadata records it as referenced by two other packages, indicating it is consumed programmatically rather than exposed through a form. Custom code that needs to re-drive a failed receipt-to-project interface can call GET_RCV_TRANSACTION_DETAILS to reload a transaction, UPDATE_CSI_DATA to refresh CSI attributes, and INTERFACE_NL_TO_PA to push the result into Projects, finishing with CLEANUP_TRANSACTION_TEMPS. Because it is an OTHER-classified API rather than a formally supported public API, callers should treat its signature as internal and stable only within the shipped release, and should rely on the documented return status and error message outputs for diagnostics.