Search Results is_far_clause_present




Overview

APPS.PON_DT_CUSTOM_PKG is a customer-modifiable stub package belonging to the Oracle Sourcing (PON) module of Oracle E-Business Suite. In Release 12.1.1 and 12.2.2 the PON schema governs the sourcing lifecycle: RFQs, auctions, negotiation documents, awarding, and the generation of associated printed artifacts. The "_CUSTOM" suffix follows the standard Oracle naming convention for extension packages that are shipped intentionally empty so that implementers can override or augment seeded behavior without directly modifying Oracle-owned code. The version header ($Header: PON_DT_CUST.plb 120.0 2011/02/17 ...) indicates this body exists at form factor 120.0 and is flagged noship, meaning it is a non-shipped, deployment-local artifact.

The package's business purpose is to serve as a hook point for document-template logic used by the Sourcing "document type" (DT) framework. The functions return descriptive answers about a given negotiation — whether a FAR clause is present, whether addenda are attached, whether the document is an award or a notice, whether a guarantee is required — that the Sourcing engine can consult when assembling negotiation or award content for display or printing. As delivered, each function returns a constant placeholder value rather than querying live data.

Key Procedures and Functions

The ETRM metadata documents five functions, all accepting only a negotiation identifier (parameter named in the source as p_auction_header_id; the declared public signature is NUMBER):

  • IS_FAR_CLAUSE_PRESENT — Intended to indicate whether a Federal Acquisition Regulation (FAR) clause is associated with the negotiation. The shipped implementation unconditionally returns the literal 'N'.
  • IS_ADDENDA_ATTACHED — Intended to report whether addenda have been attached to the negotiation document. The shipped implementation returns NULL.
  • IS_DOC_AWARD_OR_NOTICE — Intended to classify the document as an award versus a notice. The shipped implementation returns the literal 'Award'.
  • IS_GUARANTEE_REQD — Intended to indicate whether a guarantee (bid bond, performance guarantee, or comparable instrument) is required for the negotiation. The shipped implementation returns NULL.
  • GET_CALENDAR_DAYS — The function surfaced by the user's search term. It is intended to return a calendar-day value or descriptor associated with the negotiation, presumably controlling deadline or duration presentation. As delivered, it declares a local VARCHAR2(50) variable, assigns NULL, and returns that NULL. Consequently, any caller relying on this function receives an unpopulated value until the customer supplies logic.

Tables Accessed

No tables are documented as being referenced by this package, and the shipped function bodies indeed perform no SQL. The stub implementations neither select nor write. In a production customization, an implementer would typically query negotiation headers and related Sourcing tables via APPS synonyms — for example PON_AUC_HEADERS_ALL and its attributes or terms — to populate the return values, but the delivered package contains no such data access.

Usage Notes

The package is not referenced by any other packaged object per the metadata, so it is invoked only where explicitly wired in: negotiation print or preview flows, document-template assembly, or customer-written extensions that call these functions by name. Implementers adopting this stub must preserve the exact function signatures, since the calling Sourcing code expects the declared NUMBER parameter and VARCHAR2 return type. Because the functions are defined in a package body without an accompanying specification in the excerpt, deployment must ensure the corresponding package specification (or the calling form's dynamic binding) remains consistent in 12.1.1 and 12.2.2 environments. Modifications should be reapplied after patching, as the noship artifact may be regenerated.