Search Results p_table_name

Overview

PO_NOTES_SV is a server-side PL/SQL package in the Oracle E-Business Suite APPS schema that provides attachment and note-copying services for Purchasing and Receiving entities. Its primary business function is to allow Oracle Purchasing to replicate the "notes" and attached documents that a user has associated with one document onto another related document, most commonly when a purchasing document is duplicated, copied, or generated from an earlier source such as a requisition. The package abstracts the mapping between physical database tables and the internal entity names understood by the Oracle Application Object Library (AOL) attachment framework, so that calling code can pass table names such as PO_HEADERS or RCV_SHIPMENT_HEADERS without needing to know the corresponding FND attachment entity identifiers.

In EBS 12.1.1 and 12.2.2 the package remains an internal, undocumented "SV" (server) utility rather than a published API. It is classified as OTHER in the ETRM metadata and is referenced by one other package, indicating that it is consumed internally by Oracle Purchasing rather than being called directly from forms or concurrent programs.

Key Procedures and Functions

• get_entity_name — A function that accepts a physical table name and returns the corresponding AOL attachment entity name. It maps PO_HEADERS to PO_HEADERS, PO_LINES to PO_LINES, PO_LINE_LOCATIONS to PO_SHIPMENTS, PO_RELEASES to PO_RELEASES, PO_REQUISITION_HEADERS to REQ_HEADERS, PO_REQUISITION_LINES to REQ_LINES, RCV_SHIPMENT_HEADERS to RCV_HEADERS, RCV_SHIPMENT_LINES to RCV_LINES, RCV_TRANSACTIONS to RCV_TRANSACTIONS, RCV_TRANSACTIONS_INTERFACE to RCV_TRANSACTIONS_INTERFACE, MTL_SYSTEM_ITEMS to MTL_SYSTEM_ITEMS, and PO_VENDORS to PO_VENDORS. Any unrecognised input returns the sentinel value NOT_PO_ENTITY.
• copy_notes — A procedure that copies notes and attachments from a source document to a target document. It takes the source and target identifiers, columns and tables, an add-on title, and audit columns (last updated by and last update login). Internally it resolves both the source and target table names to entity names using get_entity_name, then delegates the actual work to FND_ATTACHED_DOCUMENTS2_PKG.COPY_ATTACHMENTS.

Tables Accessed

The package does not read or write the Purchasing and Receiving base tables directly. Instead, it references them only as string literals for entity-name resolution: PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, PO_RELEASES, PO_REQUISITION_HEADERS, PO_REQUISITION_LINES, PO_VENDORS, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, RCV_TRANSACTIONS, RCV_TRANSACTIONS_INTERFACE, and MTL_SYSTEM_ITEMS. The actual attachment data resides in the FND attachment tables, which are manipulated by FND_ATTACHED_DOCUMENTS2_PKG. The user's search term "rcv_headers" corresponds to the entity name returned for the RCV_SHIPMENT_HEADERS table, i.e. receiving shipment headers.

Usage Notes

PO_NOTES_SV is invoked internally by Oracle Purchasing during document duplication and copy operations, for example when a release is created from a purchase order or when receiving records inherit notes. It is not intended for direct invocation by customers, and Oracle does not document it as a supported public API. Customisations that require attachment copying should call FND_ATTACHED_DOCUMENTS2_PKG.COPY_ATTACHMENTS directly rather than relying on this private package, since its contents and entity mappings may change between releases without notice. Support analysts should treat PO_NOTES_SV as a diagnostic reference for understanding how Purchasing entity names map to AOL attachment entities, particularly when troubleshooting missing notes on requisitions, purchase orders, or receiving records in 12.1.1 and 12.2.2.