Search Results defer_payment_processing_flag

Overview

The OE_PAYMENT_TYPES_VL view is a seeded, multilingual (VL, or "translated") view owned by the APPS schema within the Oracle Order Management (ONT) product family. It presents the set of payment types that can be assigned to sales orders and returns, exposing both the operational configuration attributes of each payment type and its language-specific descriptive text. Because Oracle EBS stores translatable columns separately from the base transactional table, this view provides a single, convenient source that joins the untranslated definition rows in OE_PAYMENT_TYPES with the translated name and description rows in OE_PAYMENT_TYPES_TL, filtered by the session language through USERENV('LANG'). Status is documented as VALID.

In reporting and integration contexts, OE_PAYMENT_TYPES_VL serves as the reference view for retrieving payment type lookups keyed by PAYMENT_TYPE_CODE and ORG_ID. The view is particularly relevant to users investigating the defer_payment_processing_flag, which controls whether payment processing for an order is deferred to a later stage rather than executed immediately.

Underlying Base Objects

The view is defined over two documented base objects, presented as synonyms:

• OE_PAYMENT_TYPES — the base configuration table holding payment type codes, activation dates, enabled status, credit checking, receipt method, and the operational flags.
• OE_PAYMENT_TYPES_TL — the translation table supplying NAME and DESCRIPTION in the session language.

The join condition links the two tables on PAYMENT_TYPE_CODE and ORG_ID, and restricts the translation rows to the user's current language. All base-table columns, including the DFF attributes (ATTRIBUTE1 through ATTRIBUTE15) and the standard WHO/audit columns, are projected through, along with ROW_ID derived from the base table's ROWID.

Key Columns

• PAYMENT_TYPE_CODE — primary business key identifying the payment type.
• DEFER_PAYMENT_PROCESSING_FLAG — indicates whether payment processing is deferred for orders using this payment type.
• CREDIT_CHECK_FLAG — indicates whether a credit check applies.
• ENABLED_FLAG — whether the payment type is active and selectable.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range.
• RECEIPT_METHOD_ID — foreign reference to the associated receipt method.
• ORG_ID — operating unit context.
• NAME / DESCRIPTION — translated descriptive text from OE_PAYMENT_TYPES_TL.
• ATTRIBUTE1–15, CONTEXT — descriptive flexfield segments.

Common Use Cases and Queries

Typical uses include LOV and lookup validation, payment type configuration audits, and integration extracts. A representative query listing enabled payment types with their deferral setting:

SELECT payment_type_code, name, defer_payment_processing_flag,
       credit_check_flag, org_id
FROM   oe_payment_types_vl
WHERE  enabled_flag = 'Y'
AND    NVL(defer_payment_processing_flag,'N') = 'Y';

To validate configuration of a specific payment type within an operating unit:

SELECT payment_type_code, name, receipt_method_id,
       start_date_active, end_date_active
FROM   oe_payment_types_vl
WHERE  payment_type_code = :p_code
AND    org_id = :p_org_id;

Because the view enforces USERENV('LANG') filtering, integration jobs should verify the session language or join directly to the base tables when a specific language is required regardless of the runtime environment.