Results for “trading_partner_contact_name”

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

Overview

PON_BIDDERS_LISTS is a Sourcing module table in the PON schema of Oracle E-Business Suite, holding the header-level data of an invitation list used within the Oracle Sourcing negotiation workflow. Each row represents a single bidders list — the reusable roster of suppliers (and optionally their contacts) that a buyer may invite to a sourcing event such as an RFQ, RFI, or auction. Because the table stores the identity and descriptive metadata of the list itself, distinct from the individual suppliers that make up the list, it functions as the header or parent record for invitation list configuration.

From a data-modeling perspective, the ETRM metadata classifies this object as satellite-leaning in its heuristic Data Vault classification. This classification reflects the fact that PON_BIDDERS_LISTS records descriptive attributes attached to a core business entity, with foreign key references outward to HZ_PARTIES for trading partner details, rather than acting as a pure association (link) or a purely independent hub. It should be treated as a modeling suggestion rather than an enforced rule.

Key Information Stored

The table is defined by a surrogate primary key and a documented set of business-relevant columns:

• LIST_HEADER_ID — the primary key (PON_BIDDERS_LISTS_PK) and also the sole unique index candidate (PON_BIDDERS_LISTS_U1). It uniquely identifies each invitation list header.
• NAME — the user-assigned name of the bidders list.
• DESCRIPTION — free-text descriptive detail for the list.
• SCOPE — denotes the scope or usage context of the list within sourcing.
• LIST_STATUS — the current lifecycle/status of the list (for example active or inactive).
• TRADING_PARTNER_ID — foreign key to HZ_PARTIES identifying the owning or associated trading partner (supplier) entity.
• TRADING_PARTNER_NAME — the denormalized name of that trading partner.
• TRADING_PARTNER_CONTACT_ID — foreign key to HZ_PARTIES identifying a specific contact party.
• TRADING_PARTNER_CONTACT_NAME — the denormalized name of that contact.
• CREATION_DATE / CREATED_BY — audit columns recording who created the list header and when.
• LAST_UPDATE_DATE / LAST_UPDATED_BY — audit columns recording the most recent modification.

The distinguishing structural point is that LIST_HEADER_ID is both the surrogate primary key and the unique business-key candidate, while TRADING_PARTNER_ID and TRADING_PARTNER_CONTACT_ID are the two documented foreign keys reaching into HZ_PARTIES.

Common Use Cases and Queries

Typical scenarios involve reporting on supplier invitation lists, validating list membership before a negotiation, and reconciling lists against the trading partners they reference. A frequent query joins the header to its child detail rows in PON_BIDDING_PARTIES via LIST_ID:

• SELECT l.list_header_id, l.name, l.list_status, p.party_name FROM pon.pon_bidders_lists l JOIN pon.pon_bidding_parties b ON b.list_id = l.list_header_id JOIN hz_parties p ON p.party_id = b.trading_partner_id;
• Filtering active lists with WHERE list_status = 'ACTIVE' for pick-list or LOV population.
• Auditing list ownership and change history using created_by, creation_date, last_updated_by, and last_update_date.
• Resolving trading partner and contact names through HZ_PARTIES when the denormalized columns are insufficient.

Reporting use cases include a bidders-list registry, supplier coverage analysis across sourcing events, and identifying stale or unused lists by status and last update date.

Related Objects

The following objects are the most significant dependencies and references:

• PON_BIDDING_PARTIES — the child/detail table whose LIST_ID references PON_BIDDERS_LISTS.LIST_HEADER_ID, holding the individual suppliers on each list.
• HZ_PARTIES — referenced twice: via TRADING_PARTNER_ID and TRADING_PARTNER_CONTACT_ID, supplying party and contact identity.
• PON_BIDDERS_LISTS_PK / PON_BIDDERS_LISTS_U1 — the primary key constraint and unique index on LIST_HEADER_ID.
• Sourcing negotiation and auction event tables in the PON schema that consume invitation lists through PON_BIDDING_PARTIES membership.
• Sourcing application program interfaces (APIs) and concurrent programs that create or maintain bidders lists and their supplier members.