Search Results renumber_lines

Overview

APPS.PON_NEGOTIATION_HELPER_PVT is a private PL/SQL package body in the Oracle E-Business Suite Advanced Procurement family, specifically within the Sourcing (Negotiations/Auctions) module. It provides internal utility logic that supports the negotiation authoring and maintenance flows for auction headers, lines, lots, and groups. The package aggregates helper routines used by the Sourcing user interface — most notably the Negotiation Workbench — to manage line numbering, line deletion, attribute and price element detection, bidding party synchronization, and the staging of line close dates.

The body originates from the file PONNEGHB.pls (rdbms version $Header: PONNEGHB.pls 120.30 2007/07/24), reflecting the long-standing line of code maintained across EBS 12.1.1 and 12.2.2. Its procedures are classified as PVT, meaning they are internal building blocks called by other packages and are not intended as public, standalone APIs. Three other packages reference this body, confirming its role as a shared internal foundation rather than a directly-invokable interface.

The package encapsulates the procedural intelligence that the Sourcing forms layer relies upon to keep line-level data consistent, to compute display order, and to maintain the association between negotiation lines, price elements, attachments, and discussions.

Key Procedures and Functions

The documented 27 routines fall into several functional clusters:

• Line and structure queries: GET_NUMBER_OF_LINES, COUNT_LINES_LOTS_GROUPS, GET_MAX_INTERNAL_AND_DOC_NUM, and GET_AUCTION_REQUEST_ID support counting and identifying negotiation structure elements and their internal/document numbering.
• Existence checks: HAS_ITEMS, HAS_GOODS_LINE_FIXED_AMOUNT_PE, HAS_FIXED_AMT_OR_PER_UNIT_PE, HAS_PRICE_ELEMENTS, HAS_SUPPLIER_PRICE_ELEMENTS, HAS_BUYER_PRICE_ELEMENTS, and WILL determine whether lines, items, or price elements of a given type are present, enabling conditional UI behavior.
• Line maintenance: RENUMBER_LINES (the term the user searched) resets the display/sequence numbering of negotiation lines after structural changes; DELETE_ALL_LINES and DELETE_SINGLE_LINE remove line data; UPDATE_STAG_LINES_CLOSE_DATES propagates close dates to staged lines.
• Synchronization: SYNC_PF_VALUES_BIDDING_PARTIES and SYNC_PF_VALUES_ITEM_PRICES align price factor values with bidding parties and item prices.
• Cleanup of dependent data: REMOVE_SCORE, DELETE_PAYMENT_ATTACHMENTS, and DELETE_DISCUSSIONS remove scores, payment-related attachments, and discussion threads when lines or structures change.

Tables Accessed

The package reads and writes the core negotiation tables through APPS synonyms. Header and line pricing structures are held in PON_AUCTION_HEADERS_ALL, PON_AUCTION_ITEM_PRICES_ALL, and PON_AUCTION_ITEM_PRICES_EXT_B; shipment data in PON_AUCTION_SHIPMENTS_ALL; attributes and their mappings in PON_AUCTION_ATTRIBUTES and PON_AUCTION_ATTR_MAPPING_B; and scores in PON_ATTRIBUTE_SCORES. Document types are resolved from PON_AUC_DOCTYPES and PON_AUC_DOCTYPES_TL. Supplier and payment configuration is drawn from PON_BIDDING_PARTIES and PON_AUC_PAYMENTS_SHIPMENTS. Supporting objects include PON_DISCUSSIONS for negotiation threads, PON_AUCTION_EXHIBIT_DETAILS for attached exhibits, PON_LARGE_NEG_PF_VALUES for large price factor sets, and FND_ATTACHED_DOCUMENTS for the generic attachment framework.

Usage Notes

RENUMBER_LINES and its companion routines are typically invoked when a user adds, deletes, or reorders lines, lots, or groups within the Sourcing negotiation authoring UI. Renumbering ensures that display sequence numbers and sub-line sequence numbers remain contiguous, which is essential for search behavior — for example, the package's search helper logic, illustrated by GET_SEARCH_MIN_DISP_LINE_NUM, locates the minimum display line number above which lines matching a search condition should be shown.

Because the package is classified PVT, it should not be called directly by customer extensions. Customizations that must manipulate negotiation lines should preferably go through the supported Sourcing public APIs, or at minimum closely mirror the calling conventions and preconditions used by the internal Sourcing forms and related packages. Since these routines perform mass deletes and cross-table synchronization, invoking them out of context can leave line, attachment, score, and discussion data inconsistent.