Search Results store_blob




Overview

PO_MOD_UTIL_PVT is a private (PVT) PL/SQL utility package owned by the APPS schema in Oracle E-Business Suite, present in both the 12.1.1 and 12.2.2 releases. The "PVT" suffix indicates that the package is not exposed as a public API: Oracle does not certify its procedures for direct third-party integration, and it is intended strictly for internal consumption by Oracle Purchasing and Oracle Contracts modules. Its role is to serve as a shared helper layer for the Oracle Purchasing document modification and authoring flow, most notably the Contract Terms and Conditions (RTF/SGD) and change-description features.

The package is declared with AUTHID CURRENT_USER, meaning its unqualified object references resolve against the privileges and synonyms of the calling user rather than the owner. It exposes no public documentation for external callers, and the indexed metadata records zero packages that reference it — support code is embedded at runtime through internal forms-level or concurrent-program calls and through dynamic PL/SQL. The functions getDocumentId, getPoDraftId, and getTestFlag return the current execution context — the active document identifier, draft identifier, and test/diagnostic flag — so that downstream routines behave consistently within a session.

Key Procedures and Functions

  • STORE_BLOB — Stores a binary document payload (for example, an RTF or generated output file) and returns the media identifier of the newly created FND_LOBS record. It receives the five key values, revision number, document type, file name, entity name, and blob type, and writes through x_media_id. This is the routine associated with the "store_blob" query.
  • GETOUTPUT — Retrieves a previously stored output document as a BLOB, together with its output type, for a given draft identifier, file name, language, and entity name.
  • STORE_CHANGE_DESCRIPTION — Persists a CLOB change description for a document, capturing the editor, generation, and source application flags.
  • ISDOCUPDATEDAFTERCDGENERATED — Returns a flag indicating whether a document has been modified since its change description was generated, guarding against stale output.
  • GET_PREV_AUCTIONHDRID — Retrieves the preceding auction header ID for a given auction header, supporting auction revision and history logic.
  • SET_CONTRACT_VARIABLES — Populates the global temporary variables used to resolve contract clauses when a modification document is processed against its base document.

Tables Accessed

The package reaches Oracle foundation and document objects through APPS synonyms. FND_LOBS, FND_DOCUMENTS, FND_DOCUMENTS_TL, FND_ATTACHED_DOCUMENTS, FND_ATTACHED_DOCUMENTS_S, and FND_DOCUMENT_CATEGORIES form the attachment and BLOB repository used by STORE_BLOB and GETOUTPUT. PO_DRAFTS and PO_HEADERS_ALL hold the purchasing document header and draft context. PON_AUCTION_HEADERS_ALL supports the auction lookups. OKC_ARTICLE_VARIABLES, OKC_BUS_VARIABLES_B, OKC_K_ARTICLES_B, OKC_K_ART_VARIABLES, and PO_OKC_VARS_GT back the contract clause variable population, with the GT table acting as a session-scoped work area. FND_FLEX_VALUE_SETS supplies configuration values used to class

Usage Notes

Because PO_MOD_UTIL_PVT is a private package, it should not be called from custom code; Oracle may change its signature without notice. Invocation originates from the standard Purchasing forms and concurrent programs that author, preview, and store contract terms and change descriptions. Customizations that must persist document blobs should prefer supported public APIs and the FND_LOBS attachment APIs rather than calling STORE_BLOB directly.