Search Results po_eda_files_location

Overview

APPS.PO_EDA_IDX_FILE_GEN is a Purchasing (PO) package body that generates the EDA (Electronic Data Access) index file associated with a contract document transmitted to an external EDA processing system. In Oracle EBS 12.1.1 and 12.2.2, this package supports the integration between Oracle Purchasing and the U.S. Government EDA/CLM interface. It produces a flat, pipe-delimited index file named after the CLM document number and a timestamp, using UTL_FILE to write the file into the directory configured in the PO_EDA_FILES_LOCATION profile option. The package maps Purchasing header, draft, and award information into EDA index fields such as contract number, delivery order, modification type, issuing/administering/paying DoDAAC, CAGE code, DUNS, and issue date.

Key Procedures and Functions

• GEN_EDA_IDX — The primary procedure. It accepts a modification indicator, the CLM document number, a timestamp, and the target system name. It resolves the source document by looking up PO_DRAFTS by MODIFICATION_NUMBER and joining to PO_HEADERS_DRAFT_ALL for modification records, or querying PO_HEADERS_ALL by CLM_DOCUMENT_NUMBER for base documents. It determines whether the document is an order off an IDV (BPA Call or Delivery Order), retrieves the CLM effective date as the issue date, builds the EDA index record, and opens/writes the "clm_document_number_timestamp.idx" output file. The output directory is obtained from the PO_EDA_FILES_LOCATION profile.
• GEN_EDA_FILES — The companion procedure that orchestrates generation of the EDA output files for the document, driving the index creation and related file production. It is the entry point typically called by the EDA concurrent program.

Tables Accessed

• PO_HEADERS_ALL — Read to locate the base purchasing document by CLM_DOCUMENT_NUMBER and to derive award type, effective date, and identifying attributes.
• PO_HEADERS_DRAFT_ALL and PO_DRAFTS — Read to locate pending modification/draft records by MODIFICATION_NUMBER, draft ID, and header ID.
• FND_CONCURRENT_REQUESTS — Read for concurrent program context (request identification and output handling).
• DUAL — Used to resolve the PO_EDA_FILES_LOCATION profile value via FND_PROFILE.VALUE.
• UTL_FILE and PLITBLM — Used to open and write the index file (UTL_FILE) and to handle line/byte processing (PLITBLM utility).

Usage Notes

The package is designed to run from a concurrent program rather than interactively, as indicated by the standard concurrent errbuf/retcode OUT parameters on GEN_EDA_IDX and by its use of UTL_FILE for server-side file generation. It is typically invoked when an EDA/CLM transmission must be assembled for a contract award, delivery order, BPA call, or one of their modifications. The PO_EDA_FILES_LOCATION profile must point to a valid, writable directory on the database server file system. Because the file name embeds the CLM document number and a millisecond timestamp, repeated runs yield distinct output files. The package is not referenced by any other packaged object, so it is driven by concurrent processing or by custom code that supplies the CLM document number, system name, and optional timestamp. The clm_document_number column on PO_HEADERS_ALL is the principal search key for identifying the document to serialize.