Search Results oe_payment_types_all




Overview
Explore in AI Chat

Overview

OE_PAYMENT_TYPES_ALL is a multiorganization table owned by the ONT schema within the Oracle Order Management (ONT) product family. It stores the set of valid payment types defined for each operating unit, allowing an enterprise to maintain operating-unit-specific payment classifications for order entry and order capture. Because the table is org-striped through the ORG_ID column, the same payment type code may exist independently across multiple operating units, and Multi-Org security (MOAC) filters rows according to the responsibility's accessible organizations. Each payment type row may be linked to a receipt method, and may carry flags that govern downstream credit checking and deferred payment processing behavior during the order-to-cash flow.

From a data modeling perspective, the ETRM metadata classifies this object heuristically as standalone within its Data Vault classification. This suggests that OE_PAYMENT_TYPES_ALL functions primarily as an independent reference or setup entity rather than as a transactional hub or link, though its foreign key to AR_RECEIPT_METHODS implies a mild outbound association. Modelers should treat it as a reference data candidate for a satellite-style construct keyed on the natural business key.

Key Information Stored

The table contains 34 documented columns. The most operationally significant columns include:

The surrogate-style unique index OE_PAYMENT_TYPES_ALL_U1 is defined on PAYMENT_TYPE_CODE, ORG_ID, and ZD_EDITION_NAME, representing the business-key candidate. The primary key constraint, OE_PAYMENT_TYPES_ALL_PK, is defined on PAYMENT_TYPE_CODE and ORG_ID. The ZD_EDITION_NAME column is associated with editioning support in the E-Business Suite environment.

Common Use Cases and Queries

Typical uses include validating payment types during order entry, configuring operating-unit-specific payment behavior, and reporting on credit-check or deferred-processing rules. A common query retrieves enabled payment types for a given operating unit:

  • SELECT payment_type_code, receipt_method_id, enabled_flag FROM oe_payment_types_all WHERE org_id = :org_id AND enabled_flag = 'Y';
  • Effective-date filtering: add predicates on START_DATE_ACTIVE and END_DATE_ACTIVE to return only currently valid records.
  • Reporting on credit-check configuration: group by CREDIT_CHECK_FLAG across operating units to audit policy consistency.
  • Joining to AR_RECEIPT_METHODS on RECEIPT_METHOD_ID to enrich payment type listings with receipt method names.

Related Objects

  • AR_RECEIPT_METHODS — referenced via RECEIPT_METHOD_ID; the principal outbound foreign key relationship.
  • OE_PAYMENT_TYPES_ALL_PK and OE_PAYMENT_TYPES_ALL_U1 — the primary key constraint and unique business-key index defined on this table.
  • ONT.ORG_ID relationships — MOAC-driven associations to HR_OPERATING_UNITS for operating unit resolution.
  • Order capture and order entry form/report programs in the ONT module that read payment types during transaction processing.