Search Results update_edi_date




Overview
Explore in AI Chat

Overview

IGW_EDI_PROCESSING is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Grants/Proposal management and Electronic Data Interchange (EDI) interface within the Oracle Grants Management (IGW) product family. Its principal business function is to submit proposal-related data for external electronic transmission—typically proposal and purchase requisition/purchase order (PRPO) information—to a trading partner or federal funding agency, and to record the resulting EDI activity timestamp against the originating proposal record. The package header carries a package-level constant, G_PKG_NAME, set to 'IGW_EDI_PROCESSING', which is used for consistent error and message logging. The package is declared AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking session rather than the package owner, a common pattern for concurrent-program-callable EDI utilities in EBS.

Key Procedures and Functions

The documented package exposes two procedures:

  • SUBMIT — Submits a proposal for PRPO EDI processing based on a supplied proposal identifier. It is implemented as a concurrent-program entry point, accepting the standard concurrent manager errbuf and retcode OUT parameters alongside the proposal ID, an output path for generated files, a narrative type code, a narrative submission code, and a debug mode flag. The output path and narrative parameters allow the caller to control where EDI artifacts are written and which narrative content is included in the transmission. Debug mode provides a verbose execution path for diagnostics.
  • UPDATE_EDI_DATE — Accepts a proposal identifier and updates the EDI-related date on the referenced proposal record, marking the point at which the proposal was submitted or transmitted. This supports reporting, reconciliation, and de-duplication of EDI submissions.

Tables Accessed

The package operates against the following objects, referenced through APPS synonyms:

  • IGW_PROPOSALS_ALL — the base proposal entity; read to validate and retrieve the proposal being submitted, and updated by UPDATE_EDI_DATE.
  • IGW_PROP_ABSTRACTS — proposal abstract narrative content, read when narrative type and submission codes are supplied to SUBMIT.
  • IGW_BUDGETS — proposal budget lines, which may be included in the transmitted PRPO payload.
  • ECE_OUTPUT_RUNS_S — the EDI/e-commerce output run sequence and control table, used to create or reference the output run identifier for the generated transmission.
  • DUAL — used for singleton evaluations (for example, sequence retrieval or date/flag expression checks).

Usage Notes

IGW_EDI_PROCESSING is not referenced by any other documented package, indicating it sits at the outer edge of the call graph and is intended to be driven externally. In practice it is invoked in three ways. First, as a concurrent program: SUBMIT's errbuf/retcode signature and output-path parameter are characteristic of a registered EBS concurrent program, allowing proposal EDI submission to be scheduled or requested from the Submit Requests form. Second, from Oracle Forms or OAF pages within the Grants/Proposals responsibility, where a user action triggers submission of a selected proposal. Third, from custom PL/SQL or wrapper scripts, where a developer calls SUBMIT or UPDATE_EDI_DATE directly. On the ETRM 12.1.1 metadata, the object is classified as API classification OTHER and carries no public API designation; the header comment ($Header: igwecpos.pls 115.5 ...) and the absence of dependent packages suggest a stable, self-contained utility whose behavior is unchanged between 12.1.1 and 12.2.2. Because it is AUTHID CURRENT_USER, callers must have appropriate grants on the underlying IGW and ECE objects to execute successfully.