Results for “payment_description”

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

Overview

PON_BID_PAYMENTS_INTERFACE is an interface (staging) table in the PON – Sourcing module of Oracle E-Business Suite, owned by the PON schema. It stores imported information about the payment terms that suppliers define when responding to a negotiation (auction) for complex services. In the Sourcing flow, suppliers can propose payment schedules tied to service milestones; these proposed payments arrive from external systems or bulk-load utilities and are staged in this table before validation and transfer into the base Sourcing payment tables.

The table is populated by import processes and read by concurrent programs that validate and apply the staged rows against the corresponding auction and bid records. Its scope is deliberately narrow: it holds supplier-proposed payment lines for complex services bids, not general payment terms.

From a Data Vault modeling perspective, the documented foreign key structure suggests classifying PON_BID_PAYMENTS_INTERFACE as a link entity. It associates a bid (via BID_NUMBER) and an auction header (via AUCTION_HEADER_ID) with individual payment detail rows, making it a connective/associative structure rather than a standalone hub or descriptive satellite.

Key Information Stored

The table contains 21 documented columns. The most significant are:

• BATCH_ID – Groups a set of imported payment rows processed together; part of the primary key.
• INTERFACE_LINE_ID – Unique line identifier within a batch; the second component of the primary key.
• AUCTION_HEADER_ID – Foreign key to PON_AUCTION_HEADERS_ALL, tying the payment to a specific negotiation.
• BID_NUMBER – Foreign key to PON_BID_HEADERS, identifying the supplier response.
• DOCUMENT_DISP_LINE_NUMBER – Display line number of the associated bid document line.
• PAYMENT_DISPLAY_NUMBER – Sequence number shown for the payment line.
• PAYMENT_TYPE – Classification of the proposed payment.
• PAYMENT_DESCRIPTION – Free-text description of the payment line.
• QUANTITY and UNIT_OF_MEASURE – Quantity and UOM associated with the payment.
• BID_CURRENCY_PRICE – Price expressed in the bid currency.
• PROMISED_DATE – Date on which the payment is promised.
• ATTACHMENT_DESC and ATTACHMENT_URL – Description and location of any supporting attachment.
• WORKSHEET_NAME and WORKSHEET_SEQUENCE_NUMBER – Identify the worksheet context for the payment.

Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) track row provenance. The surrogate primary key is PON_BID_PAYMENTS_INTERFACE_PK on (BATCH_ID, INTERFACE_LINE_ID); BID_NUMBER and AUCTION_HEADER_ID function as business-key references to parent entities.

Common Use Cases and Queries

Typical scenarios include pre-import validation, batch monitoring, error diagnosis, and post-import reconciliation.

• Reviewing pending staged rows for a batch:

  SELECT batch_id, interface_line_id, auction_header_id, bid_number,
         payment_type, bid_currency_price, promised_date
  FROM   pon.pon_bid_payments_interface
  WHERE  batch_id = :batch_id;

• Joining staged payments to their auction and bid parents for reporting:

  SELECT p.bid_number, p.payment_display_number, p.payment_type,
         p.bid_currency_price, a.auction_header_id
  FROM   pon.pon_bid_payments_interface p,
         pon.pon_auction_headers_all a,
         pon.pon_bid_headers b
  WHERE  p.auction_header_id = a.auction_header_id
  AND    p.bid_number        = b.bid_number;

• Reconciling imported payment totals against bid currency values for a negotiation.
• Detecting incomplete rows (missing PROMISED_DATE, PAYMENT_TYPE, or pricing) prior to running the import concurrent program.

Related Objects

• PON_AUCTION_HEADERS_ALL – Parent negotiation header; joined on AUCTION_HEADER_ID.
• PON_BID_HEADERS – Parent bid response; joined on BID_NUMBER.
• PON_BID_PAYMENTS_INTERFACE_PK – Primary key constraint enforcing uniqueness on (BATCH_ID, INTERFACE_LINE_ID).
• Sourcing import/validation concurrent programs that consume BATCH_ID-grouped rows and transfer validated payments into the base Sourcing payment tables.
• Auction and bid reporting views that surface supplier-proposed payment schedules for complex services.