Search Results gen_eda_idx




Overview
Explore in AI Chat

Overview

PO_EDA_IDX_FILE_GEN is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Electronic Data Access (EDA) indexing and file generation process within Oracle Purchasing. The package is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute under the privileges of the calling user rather than the package owner, which is significant for a utility that performs file system operations through UTL_FILE and must respect the runtime schema context of the concurrent request that invokes it. Its documented API classification is OTHER, reflecting that it is an internal technical utility rather than a public, supported business API.

The central purpose of the package is to produce the index and data files required by the EDA framework, which supplies procurement documents to external or downstream systems under controlled access and classification rules. The source header (POEDAIXS.pls, version 120.5.12020000.3) indicates the file has been maintained through the 12.2 release cycle, and the object is present in both Oracle EBS 12.1.1 and 12.2.2 environments. In 12.2.2 the package continues to serve this role alongside the Online Patching file system layout, where concurrent output and staging directories are resolved relative to the run edition of the application tier.

Key Procedures and Functions

The package exposes two documented procedures.

  • GEN_EDA_IDX — Generates the EDA index content for a given document context. It returns the standard concurrent program error buffer and return code, accepts an indicator of whether the run is performed in modification mode, takes the document number to be indexed, a timestamp value, and a system name identifying the target system. Its signature includes user-defined PLS integer types for the errbuf and retcode parameters, consistent with concurrent program conventions.
  • GEN_EDA_FILES — Generates the EDA data files. It also returns errbuf and retcode and accepts modification mode, one or two document numbers, paired approved dates and effective dates, a document status, an EDA status, the schema version in use, the system administrator (DODAAC) value, the data template code, a DITPR number, the document purpose, and the system name. The paired date and document parameters support both single-record and range-based selection.

A package-level variable, p_doc_id, and p_draft_id, are declared in the specification body but are internal state rather than callable APIs.

Tables Accessed

The package references the following objects through APPS synonyms:

  • PO_HEADERS_ALL — the base purchasing document header table, read to identify approved purchase orders and their attributes for indexing and file extraction.
  • PO_HEADERS_DRAFT_ALL and PO_DRAFTS — the draft and change-order tables, consulted when documents are processed in modification or draft mode.
  • FND_CONCURRENT_REQUESTS — used to correlate the running concurrent request, its parameters, and its output context.
  • UTL_FILE — the Oracle-supplied file I/O package used to write the generated index and data files to a database directory object.
  • PLITBLM — a PL/SQL internal table/utility reference supporting bulk data handling during generation.
  • DUAL — used for scalar evaluations and database-level function calls.

Usage Notes

PO_EDA_IDX_FILE_GEN is not referenced by any other package in the ETRM repository; it therefore sits at or near the top of its call chain and is invoked directly rather than as a dependency of another API. In practice it is driven as the PL/SQL body of a concurrent program, most likely the program associated with the EDA/CLM index and file generation submission, with GEN_EDA_IDX and GEN_EDA_FILES mapped to executable parameters such as document number, modification mode, and system name. The errbuf and retcode parameters confirm this concurrent program contract. Because output is written through UTL_FILE, the invoking concurrent program must be associated with a valid database directory object, and the APPS user or requesting user must hold the corresponding file system permissions. The AUTHID CURRENT_USER declaration means custom callers should verify that the calling schema has EXECUTE privilege on the package and the necessary directory grants. Typical invocation is from the Purchasing or Contract Lifecycle Management responsibility when procurement documents must be exported in EDA format.