Search Results oe_payment_types_all_u1

Overview

ONT.OE_PAYMENT_TYPES_ALL is a multiorg seed table within the Oracle Order Management (ONT) schema that stores the set of payment types available to each Operating Unit. It is the ordering-side master of payment type definitions, referenced when sales orders are entered so that the correct collection method, credit-checking behavior, and payment-processing timing can be derived for each order. The table resides in the APPS_TS_SEED tablespace, consistent with its role as a setup/reference object rather than a high-volume transactional entity, and is registered in FND Design Data as ONT.OE_PAYMENT_TYPES_ALL with status VALID in Oracle EBS 12.1.1 and 12.2.2.

Each row represents one payment type enabled for a specific Operating Unit. The PAYMENT_TYPE_CODE column carries a lookup code for lookup type OE_PAYMENT_TYPE, while ORG_ID partitions the definition by Operating Unit, which is why the same code can exist more than once across the organization hierarchy. Effectivity is controlled through START_DATE_ACTIVE and END_DATE_ACTIVE, and availability to users is gated by ENABLED_FLAG. The documented heuristic Data Vault classification for this table is standalone, meaning it is treated as a self-contained reference structure rather than a hub, link, or satellite in a mined dependency graph; this should be read as a modeling suggestion only, since the table does participate in a foreign key to AR payment methods.

Key Information Stored

The business identifier of a payment type is the combination of PAYMENT_TYPE_CODE and ORG_ID, and the surrogate primary key OE_PAYMENT_TYPES_ALL_PK is defined on exactly those two columns. The documented physical schema also exposes a unique index, OE_PAYMENT_TYPES_ALL_U1, on PAYMENT_TYPE_CODE, ORG_ID, and ZD_EDITION_NAME, which is the business-key candidate in the editioned 12.2.2 data model. Users searching for "oe_payment_types_all_u1" are typically examining this uniqueness constraint or validating duplicate payment type definitions per Operating Unit.

The most operationally significant columns are:

• PAYMENT_TYPE_CODE — lookup code for OE_PAYMENT_TYPE; the user-facing identifier of the payment type.
• ORG_ID — the Operating Unit that owns the definition.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effectivity window controlling when the payment type may be selected.
• ENABLED_FLAG — Y or N; only enabled payment types are selectable by users.
• DEFER_PAYMENT_PROCESSING_FLAG — when Y, payment processing for the type is performed offline.
• CREDIT_CHECK_FLAG — indicates whether the payment type is subject to credit checking.
• RECEIPT_METHOD_ID — foreign key to AR receipt methods; the collection method applied on the invoice to collect the open balance.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield storage.
• ZD_EDITION_NAME — editioning column supporting the 12.2 online patching model.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the concurrent program columns (PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID) provide audit and traceability.

Common Use Cases and Queries

Typical reporting and validation scenarios include confirming which payment types are active for a given Operating Unit, auditing the receipt method assigned to each type, and identifying types configured for offline payment processing or credit checking.

• List enabled, currently effective payment types for an organization:
  SELECT payment_type_code, receipt_method_id, credit_check_flag
FROM ont.oe_payment_types_all
WHERE org_id = :org_id
AND enabled_flag = 'Y'
AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE-1) AND NVL(end_date_active, SYSDATE+1);
• Check uniqueness of the business key across editions:
  SELECT payment_type_code, org_id, zd_edition_name, COUNT(*)
FROM ont.oe_payment_types_all
GROUP BY payment_type_code, org_id, zd_edition_name
HAVING COUNT(*) > 1;
• Join to AR receipt methods to resolve the collection method name for each payment type, using RECEIPT_METHOD_ID.
• Report payment types flagged for deferred (offline) processing with DEFER_PAYMENT_PROCESSING_FLAG = 'Y'.
• Audit setup changes over time using LAST_UPDATE_DATE and LAST_UPDATED_BY to identify recent modifications.

Related Objects

The following objects are most significant in relation to OE_PAYMENT_TYPES_ALL:

• AR.OE_PAYMENT_TYPES? / AR_RECEIPT_METHODS — referenced through the documented foreign key OE_PAYMENT_TYPES_ALL.RECEIPT_METHOD_ID → AR_RECEIPT_METHODS, providing the collection method applied to invoices.
• AR.OE_PAYMENT_TYPES_VL / OE_PAYMENT_TYPES_ALL — the translated views that expose payment type descriptions to users.
• Order Management order headers and lines — order entry validates the selected payment type against this table for the current Operating Unit.
• FND Lookups (OE_PAYMENT_TYPE) — source of the PAYMENT_TYPE_CODE lookup values.
• FND_CONCURRENT_PROGRAMS and FND_APPLICATION — referenced by the PROGRAM_ID and PROGRAM_APPLICATION_ID who columns for traceability.
• FND_CONCURRENT_REQUESTS — referenced by REQUEST_ID.
• ZD_EDITION_NAME / AD_ZD_EDITION — supports the 12.2.2 editioning and online patching framework.