Search Results get_doctype_suffix
Overview
APPS.PON_LARGE_AUCTION_UTIL_PKG is a utility package within the Oracle E-Business Suite Sourcing (Oracle Sourcing / Advanced Procurement) module. Its header revision string ($Header: PONLGUTS.pls 120.6 2006/03/09 ...) indicates the package has been part of the product since the early 11i era and remains shipped in EBS 12.1.1 and 12.2.2 without significant structural change. The package exists to support the processing of large auctions — negotiations that may contain thousands of bid lines and supplier responses. Its two central concerns are (1) managing the lifecycle of large, potentially long-running concurrent requests associated with auction and bid operations, and (2) performing bulk maintenance operations such as deleting bids and purging interface errors without exceeding database resource limits.
Two package-level constants frame the scale problem the package addresses: BATCH_SIZE (2500) governs the commit/batch granularity for bulk DML, and g_default_lines_threshold (500) establishes the boundary beyond which an auction is treated as "large." These values are referenced throughout the procedures that determine whether a request is still pending, complete, or has errored.
Key Procedures and Functions
The nineteen documented program units fall into several functional clusters.
- Concurrent request status inspection: GET_REQUEST_INFO is a wrapper around FND_CONCURRENT.GET_REQUEST_STATUS, returning displayable and developer phase/status values plus a diagnostic message. GET_REQUEST_DISPLAY_STATUS, GET_REQUEST_INTERNAL_STATUS, REQUEST_HAS_ERRORS, REQUEST_ERROR_COUNT, and IS_REQUEST_COMPLETE provide narrower queries used by callers monitoring asynchronous auction processes. The user search term "request_has_errors" maps directly to REQUEST_HAS_ERRORS, which returns whether a given concurrent request terminated in error.
- Pending-request checks: IS_AUCTION_REQUEST_PENDING and IS_BID_REQUEST_PENDING determine whether conflicting work is already in flight for an auction or bid.
- Auction state evaluation: IS_AUCTION_COMPLETE, IS_AUCTION_NOT_UPDATED, and UPDATE_AUCTION_IMPORT_COLS support auction import and status transitions.
- Bid deletion: DELETE_BID, DELETE_BID_BY_HEADER, and DELETE_BID_HEADER_ATTACHMENT remove bids and their attachments, iterating in batches conforming to BATCH_SIZE.
- Numeric threshold helpers: IS_SUPER_LARGE_NEG and IS_LARGE_NEG classify large negative values, supporting the "large auction" logic.
- Interface and maintenance utilities: PURGE_INTERFACE_ERRORS_CP clears PON_INTERFACE_ERRORS, CANCEL_CONCURRENT_REQUEST terminates running requests, and GET_DOCTYPE_SUFFIX returns a document-type suffix used when constructing numbering or filenames.
Parameter lists are not reproduced here; callers should consult the package specification in the ETRM for exact signatures.
Tables Accessed
The package reads and writes a focused set of Sourcing and concurrent-manager tables through APPS synonyms. FND_CONCURRENT_REQUESTS and FND_ATTACHED_DOCUMENTS are consulted for request status and attachment handling. PON_AUCTION_HEADERS_ALL, PON_AUCTION_SUMMARY, and PON_AUC_DOCTYPES hold auction header, summary, and document-type data. Bid-level data resides in PON_BID_HEADERS and the associated PON_BID_ATTRIBUTE_VALUES, PON_BID_ITEM_PRICES, PON_BID_PAYMENTS_SHIPMENTS, PON_BID_PRICE_DIFFERENTIALS, PON_BID_PRICE_ELEMENTS, and PON_BID_SHIPMENTS tables, which are the primary targets of the DELETE_BID family. PON_INTERFACE_ERRORS is purged by PURGE_INTERFACE_ERRORS_CP, and PON_PARTY_PREFERENCES supplies supplier preference context.
Usage Notes
PON_LARGE_AUCTION_UTIL_PKG is not an end-user API; it is an internal utility invoked from Oracle Sourcing forms, concurrent programs, and other PON packages. The metadata notes it is referenced by fifteen other packages, confirming its role as a shared service layer. Typical invocations occur when a buyer deletes a bid, when a large auction import or update runs as a concurrent request and the caller must poll its status, and when administrators purge interface errors or cancel stuck requests. Customizations should avoid calling DELETE_BID procedures outside supported flows because they cascade across numerous bid detail tables. Because the package interacts with FND_CONCURRENT, request-status calls should be made within the same application context as the submitting process. In 12.2.2 the package behaves compatibly with 12.1.1; the online patching architecture does not alter its runtime semantics.