Results for “open_bidding”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.PON_BUYER_MANAGE_DELIV_V view is an Oracle E-Business Suite sourcing object that identifies the buyers and negotiation team members authorized to manage deliverables related to a sourcing event. It is defined over the Oracle Sourcing (PON) and Oracle Trading Community Architecture (HZ, FND) schemas and surfaces a filtered list of bid numbers joined to the FND user IDs that may act on them. Its principal role is to support the buyer-side delivery and management responsibilities within the Sourcing application, distinguishing internal employees who belong to the negotiation team from external trading partner contacts.

Because the view reconciles bid headers, auction headers, user identities, and party relationships, it is typically consumed by concurrent programs, OAF pages, or custom reports that need to resolve which internal user owns or may manage a given negotiation's deliverables. The user search term "sealed_auction" is directly relevant, as the view's WHERE clause explicitly encodes sealed-auction visibility logic.

Underlying Base Objects

The documented base objects referenced by this view are all synonyms in the APPS schema:

• PON_AUCTION_HEADERS_ALL — the sourcing auction/negotiation header, supplying auction status, visibility code, security level, trading partner, and sealed auction status.
• PON_BID_HEADERS — the bid header joined to its parent auction header, restricted to bids with a bid_status of 'ACTIVE'.
• FND_USER — the application user record, providing the user_id and linking to the person party.
• HZ_PARTIES — used twice (aliased user_parties and company_parties) to represent the individual user party and the company/trading partner party.
• HZ_RELATIONSHIPS — establishes the POS_EMPLOYMENT / EMPLOYEE_OF relationship between the user party and the company party, with start and end dates validated against SYSDATE.
• HZ_CODE_ASSIGNMENTS — classifies the company party as POS_PARTICIPANT_TYPE = ENTERPRISE.
• PON_NEG_TEAM_MEMBERS, FND_MENUS, FND_FORM_FUNCTIONS, FND_COMPILED_MENU_FUNCTIONS — used in subqueries to identify negotiation team members holding the PON_AUC_VIEWNEG function.

Key Columns

The view exposes two primary projected columns:

• bid_number — the human-readable negotiation/bid identifier from PON_BID_HEADERS, used for referencing the sourcing event.
• user_id — the FND_USER identifier of the buyer or entitled user associated with the bid.

Implicit, the query logic also derives visibility eligibility from ah.bid_visibility_code ('OPEN_BIDDING', 'SEALED_BIDDING', 'SEALED_AUCTION'), ah.sealed_auction_status (defaulting to 'LOCKED' via NVL), ah.security_level_code (defaulting to 'PUBLIC'), and auction_status constrained to 'ACTIVE' or 'AUCTION_CLOSED'.

Common Use Cases and Queries

Typical use cases include identifying the buyer responsible for a negotiation's deliverables, restricting views to legitimate negotiation team members, and enforcing sealed-auction confidentiality. A basic query follows:

• SELECT bid_number, user_id FROM apps.pon_buyer_manage_deliv_v;
• SELECT bid_number FROM apps.pon_buyer_manage_deliv_v WHERE user_id = :p_user_id; — to list negotiations a given user may manage.

For sealed-auction scenarios, the view already filters out cases where sealed_auction_status is 'LOCKED' for non-contact users, so reporting queries inherit that security automatically without additional predicates. Analysts should note the view returns only ACTIVE bid headers under ACTIVE or AUCTION_CLOSED auctions, so historical or voided negotiations are excluded by design.