Search Results pon_emd_payment_types_u1

Overview

PON.PON_EMD_PAYMENT_TYPES_ALL is a transactional setup table in the Oracle E-Business Suite PON (Purchasing) schema that stores the payment types available for use in Earnest Money Deposit (EMD) transactions. In Oracle EBS 12.1.1 and 12.2.2, EMD functionality is typically associated with government, public sector, and contract bid management flows where bidders submit deposits — by cheque, demand draft, or other instruments — alongside their bids or tenders. This table defines which of those payment instruments may be selected for a given operating unit, along with the receipt method and refund behavior tied to each one.

The table is organization-partitioned through the ORG_ID column, meaning each operating unit maintains its own set of permitted EMD payment types. The presence of the ZD_EDITION_NAME column indicates participation in the Edition-Based Redefinition (EBR) / Online Patching architecture introduced with EBS 12.2, while the table also remains valid in 12.1.1 without that column populated. The documented Data Vault classification (heuristic, derived from FK structure) is standalone, suggesting this object is best modeled as an independent reference/lookup entity rather than as a hub, link, or satellite in a Data Vault sense, since it carries no inbound dependency relationships driving it as a transactional junction.

Key Information Stored

The primary key is defined as PON_EMD_PAYMENT_TYPES_PK1 on (PAYMENT_TYPE_CODE, ORG_ID), establishing the payment type code as the natural business identifier scoped by operating unit. A unique index, PON_EMD_PAYMENT_TYPES_U1, enforces uniqueness on (PAYMENT_TYPE_CODE, ORG_ID, ZD_EDITION_NAME), confirming that under EBR the same business key can exist in separate editions.

• PAYMENT_TYPE_CODE (VARCHAR2(30), mandatory) — the business code identifying the payment type, such as cheque or DD (demand draft).
• ORG_ID — the operating unit that owns this payment type row.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date window during which the payment type is valid for selection.
• ENABLED_FLAG — indicates whether the financial setup for this payment type is enabled.
• RECEIPT_METHOD_ID — foreign key to AR_RECEIPT_METHODS, identifying the receipt method used to record the deposit.
• REFUND_PAYMENT_METHOD (VARCHAR2(100)) — the payment method to use when refunding the deposit.
• DEFER_AUTHORIZATION — indicates whether authorization should be deferred for this payment type.
• PROGRAM_ID, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns identifying the last program that processed or updated the row.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ZD_EDITION_NAME (VARCHAR2(30)) — EBR edition name for Online Patching under 12.2.

The primary key is composite and natural (no surrogate sequence), while PON_EMD_PAYMENT_TYPES_U1 acts as the business-key candidate including the edition discriminator.

Common Use Cases and Queries

Typical usage is validation and reporting: confirming which payment types are currently active for a given operating unit, tying them to oracle receivables receipt methods, and reporting on refund configuration. A fundamental query retrieving active payment types is:

SELECT payment_type_code, receipt_method_id, refund_payment_method
FROM   pon.pon_emd_payment_types_all
WHERE  org_id = :p_org_id
AND    enabled_flag = 'Y'
AND    TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE)
                          AND NVL(end_date_active, SYSDATE);

Joining to AR_RECEIPT_METHODS enriches reporting with the receipt method name:

SELECT p.payment_type_code, r.name receipt_method, p.refund_payment_method
FROM   pon.pon_emd_payment_types_all p,
       ar_receipt_methods r
WHERE  p.receipt_method_id = r.receipt_method_id
AND    p.org_id = :p_org_id;

Common scenarios include EMD setup audits, refund method reconciliation, and R12.2 edition-aware extracts filtered by ZD_EDITION_NAME.

Related Objects

• AR_RECEIPT_METHODS — referenced via RECEIPT_METHOD_ID; supplies the receipt method definition for each EMD payment type.
• PON_EMD_PAYMENT_TYPES_PK1 — primary key constraint on (PAYMENT_TYPE_CODE, ORG_ID).
• PON_EMD_PAYMENT_TYPES_U1 — unique index on (PAYMENT_TYPE_CODE, ORG_ID, ZD_EDITION_NAME).
• FND Design Data: PON.PON_EMD_PAYMENT_TYPES_ALL — the EBS design metadata defining this table.
• HR_ALL_ORGANIZATION_UNITS / ORG_ID lookup — the operating unit referenced by ORG_ID.
• FND_CONCURRENT_PROGRAMS — referenced implicitly through PROGRAM_ID and REQUEST_ID audit columns.