Search Results resubmit_waiting_txns




Overview
Explore in AI Chat

Overview

CSI_RESUBMIT_PUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the CSI (Complex Maintenance, Repair, and Overhaul / Enterprise Asset Management) product family. Its business purpose is to re-drive the processing of material transaction records that have stalled within the CSI transaction interface. When transactions submitted through the CSI interface fail or remain in a waiting state, they accumulate rather than completing. This package provides the mechanism by which those stuck transactions are re-queued and reprocessed without requiring manual data re-entry.

The package is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute under the privileges of the invoking user rather than the definer. The documented header carries the version string $Header: csiprshs.pls 115.6 2004/05/13 20:03:20 brmanesh ship $, indicating a long-stable code line carried forward into EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents three public procedures, all of which follow the concurrent-program standard signature convention of an OUT error buffer and an OUT return code.

  • RESUBMIT_INTERFACE — The primary entry point. It accepts an additional option parameter (p_option) that selects which category of interface records is to be resubmitted. This procedure is the general-purpose resubmission driver.
  • RESUBMIT_WAITING_TXNS — Targets transactions that are in a waiting state within the CSI interface. It re-drives those records through the interface processing logic so that they advance toward completion.
  • RESUBMIT_ERROR_TXNS — Targets transactions that previously ended in error. It accepts a process_flag parameter that governs how the errored records are handled during resubmission.

Supporting internal behaviour is governed by the package-level constant g_default_num_rec_fetch NUMBER := 30;. This global variable defines the default number of records fetched per call. The g_ prefix follows Oracle's naming convention for global variables, and the name g_default_num_rec_fetch — the term the user searched for — identifies the batch size used when the resubmission routines fetch interface rows for processing. Because it is a package variable rather than a literal embedded in each procedure, the fetch size is centrally maintained and can be referenced consistently by all three procedures.

Tables Accessed

The package operates against the following tables through APPS synonyms:

  • CSI_TXN_ERRORS — The error repository for CSI transactions. It is read to identify errored records and updated as those records are resubmitted.
  • CSI_TXN_TYPES — Defines the transaction types recognised by the CSI interface, used to classify and validate records before resubmission.
  • MTL_MATERIAL_TRANSACTIONS — The core inventory transaction table; CSI processing generates or reconciles material transactions, so this table is central to the business outcome.
  • XNP_MSGS — The messaging/notification table used for inter-process communication and status propagation.
  • DBMS_LOB — The Oracle-supplied large object package, referenced for manipulation of LOB columns within the interface records.

Usage Notes

CSI_RESUBMIT_PUB is designed for invocation as a concurrent program, evidenced by the errbuf/retcode OUT parameter pattern common to Oracle concurrent managers. It is additionally referenced by one other documented package, allowing programmatic resubmission from within dependent processing logic. Typical operational use occurs after a batch of CSI transactions has failed or stalled and an administrator elects to reprocess them in bulk rather than correcting records individually. The declared fetch size of 30 records per call bounds memory consumption and transaction chaining during large resubmission runs.