Search Results pon_emd_payment_types_all




Overview
Explore in AI Chat

Overview

The PON_EMD_PAYMENT_TYPES_ALL table is a Sourcing (PON) module table within the Oracle E-Business Suite database, owned by the PON schema. It serves as the reference and configuration store for payment type definitions used in Oracle Sourcing and negotiation workflows, particularly those involving payment instruments, refunds, and authorization deferral. The table is org-striped, meaning records are partitioned by operating unit via the ORG_ID column, and it carries a multi-language "_ALL" designation consistent with Oracle's MLS/translation conventions.

From a Data Vault modeling perspective, the mined relationship data classifies this table as a standalone object. This is a heuristic suggestion rather than a definitive classification; the table exhibits a single foreign key outward to AR_RECEIPT_METHODS without being referenced by documented FK children, which is characteristic of a reference/lookup hub rather than a link or satellite. In practice it behaves as a configuration hub supplying payment type codes to dependent transactional tables.

Key Information Stored

The table contains 18 documented columns. The most significant of these are:

The surrogate primary key is PON_EMD_PAYMENT_TYPES_PK1, defined on (PAYMENT_TYPE_CODE, ORG_ID). A business-key candidate unique index, PON_EMD_PAYMENT_TYPES_U1, extends this to (PAYMENT_TYPE_CODE, ORG_ID, ZD_EDITION_NAME), reflecting the presence of the ZD_EDITION_NAME editioning column typical of Oracle's online patching architecture in 12.2.

Common Use Cases and Queries

Typical use cases include validating whether a payment type is enabled for a given operating unit, resolving the Receivables receipt method behind a payment type, and reporting on active payment type configurations.

A common lookup pattern joins to the receipt method table:

  • SELECT p.PAYMENT_TYPE_CODE, p.ENABLED_FLAG, a.NAME FROM PON_EMD_PAYMENT_TYPES_ALL p JOIN AR_RECEIPT_METHODS a ON p.RECEIPT_METHOD_ID = a.RECEIPT_METHOD_ID WHERE p.ORG_ID = :org_id AND p.ENABLED_FLAG = 'Y'

A date-window validation query checks the active period:

  • SELECT PAYMENT_TYPE_CODE FROM PON_EMD_PAYMENT_TYPES_ALL WHERE ORG_ID = :org_id AND SYSDATE BETWEEN START_DATE_ACTIVE AND END_DATE_ACTIVE

Reporting queries commonly filter by ORG_ID for multi-org security and use DEFER_AUTHORIZATION or REFUND_PAYMENT_METHOD as filter predicates for configuration audits.

Related Objects

The most significant related objects are:

  • AR_RECEIPT_METHODS — referenced via RECEIPT_METHOD_ID; supplies receipt method names and validation.
  • PON_EMD_PAYMENT_TYPES_PK1 — the primary key constraint enforcing (PAYMENT_TYPE_CODE, ORG_ID).
  • PON_EMD_PAYMENT_TYPES_U1 — the unique business-key index including ZD_EDITION_NAME.
  • Oracle Sourcing negotiation and auction configuration tables that consume PAYMENT_TYPE_CODE as a lookup value.
  • Receivables payment and refund transaction tables that inherit payment method behavior from the linked receipt method.

The sparse documented FK footprint confirms the standalone heuristic; referential integrity is largely enforced through the composite primary key and the outbound receipt method reference rather than through multiple inbound child keys.