Results for “project_task_id”

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

Overview

PON_AUC_PAYMENTS_SHIPMENTS is a Sourcing (PON) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the payment details defined on a negotiation for complex services. In the Oracle sourcing workflow, complex services negotiations require bidders and buyers to agree not only on price but also on payment scheduling, ship-to destinations, project accounting attributes, and work approvers. This table captures those payment line definitions at the negotiation (auction) header and line level, allowing payment terms to be authored, revised, and ultimately propagated to the resulting sourcing award and purchasing documents.

From a data modeling perspective, the metadata's heuristic Data Vault classification suggests this object behaves as a satellite. Each row describes descriptive payment attributes that hang off core negotiation and project reference keys rather than serving as a standalone hub or as a pure transactional link. The table is owned by the PON schema and is documented as VALID in the ETRM repository.

Key Information Stored

The table comprises 24 columns, but its analytical value concentrates in a smaller set of descriptive and relational attributes:

• PAYMENT_ID — the surrogate primary key, enforced by PON_AUC_PAYMENTS_SHIPMENTS_PK and also exposed through the unique index PON_AUC_PAYMENTS_SHIPMENTS_U1, making it the dominant business-key candidate in the documented metadata.
• AUCTION_HEADER_ID — identifies the parent negotiation in PON_AUCTION_HEADERS_ALL.
• LINE_NUMBER — associates the payment record with the corresponding negotiation line in PON_AUCTION_ITEM_PRICES_ALL.
• PAYMENT_DISPLAY_NUMBER and PAYMENT_DESCRIPTION — user-facing numbering and narrative text for the payment.
• PAYMENT_TYPE_CODE — classifies the payment (for example, advance, milestone, or progress payment) as defined by the negotiation.
• SHIP_TO_LOCATION_ID — the delivery destination, validated against HR_LOCATIONS_ALL.
• QUANTITY and UOM_CODE — the quantity and unit of measure to which the payment applies.
• TARGET_PRICE — the negotiated or target amount for the payment line.
• NEED_BY_DATE — the required date driving payment scheduling.
• WORK_APPROVER_USER_ID — the approver of delivered work, referencing FND_USER.
• PROJECT_ID, PROJECT_TASK_ID, PROJECT_AWARD_ID, PROJECT_EXPENDITURE_TYPE, PROJECT_EXP_ORGANIZATION_ID, and PROJECT_EXPENDITURE_ITEM_DATE — the Project Accounting attributes that enable costing against PA_PROJECTS_ALL, PA_TASKS, and HR_ALL_ORGANIZATION_UNITS.
• NOTE_TO_BIDDERS — instructional text surfaced to suppliers during the negotiation.

Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) follow Oracle's WHO column conventions.

Common Use Cases and Queries

Typical applications include extracting payment schedules for a negotiation, reconciling bid responses against buyer-defined payments, and reporting on project-charged services spend. A representative query joins the header and line tables to reconstruct the payment plan:

• Payment schedule by negotiation: select p.PAYMENT_DISPLAY_NUMBER, p.PAYMENT_TYPE_CODE, p.TARGET_PRICE, p.NEED_BY_DATE from PON_AUC_PAYMENTS_SHIPMENTS p join PON_AUCTION_HEADERS_ALL h on p.AUCTION_HEADER_ID = h.AUCTION_HEADER_ID where h.AUCTION_HEADER_ID = :header_id.
• Bid comparison: join to PON_BID_PAYMENTS_SHIPMENTS on AUCTION_PAYMENT_ID to compare supplier-proposed payments against the buyer's definition.
• Project costing integration: join PROJECT_ID, PROJECT_TASK_ID, and PROJECT_EXP_ORGANIZATION_ID to PA_PROJECTS_ALL, PA_TASKS, and HR_ALL_ORGANIZATION_UNITS to validate project accounting setups for complex services.
• Interface monitoring: join to PON_INTERFACE_ERRORS on PAYMENT_ID to identify payment records that failed to load or validate.

Related Objects

The most significant dependent and referenced objects, grounded in the documented foreign-key relationships, are:

• PON_AUCTION_HEADERS_ALL — parent negotiation header, joined on AUCTION_HEADER_ID.
• PON_AUCTION_ITEM_PRICES_ALL — negotiation line, joined on LINE_NUMBER and AUCTION_HEADER_ID.
• PON_BID_PAYMENTS_SHIPMENTS — supplier bid payment responses, referencing AUCTION_PAYMENT_ID.
• PON_INTERFACE_ERRORS — load and validation errors, referencing PAYMENT_ID.
• PA_PROJECTS_ALL and PA_TASKS — project and task validation, joined on PROJECT_ID and PROJECT_TASK_ID.
• HR_ALL_ORGANIZATION_UNITS — expenditure organization, joined on PROJECT_EXP_ORGANIZATION_ID.
• HR_LOCATIONS_ALL — ship-to destination, joined on SHIP_TO_LOCATION_ID.
• FND_USER — work approver, joined on WORK_APPROVER_USER_ID.

Together these relationships establish PON_AUC_PAYMENTS_SHIPMENTS as the central satellite holding negotiation-level payment terms for complex services across the Oracle Sourcing and Project Accounting flows.