Search Results ap_lc_payment_methods_v

Overview

The view AP_LC_PAYMENT_METHODS_V is a Payables (AP) module object that exposes valid payment method lookup values in a denormalized, reporting-friendly form. The object is explicitly documented as a Release 10SC artifact, and the ETRM metadata records its description as "(Release 10SC Only)." It presents a filtered, three-column projection of the lookup codes table, restricted to the lookup type PAYMENT METHOD and to records that are both enabled and currently active. In practice, the view answers a single business question: which payment methods can be selected or reported against at the current point in time. Because payment methods in Payables drive how a payment is created, formatted, and transmitted — for example check, wire, ACH, or electronic funds transfer — a stable, pre-filtered source of these values is useful for validation logic, concurrent report output, and integrations that must not present retired or disabled methods. The ETRM documentation records this view as not implemented in this database, which indicates that in the documented environment the object either does not exist or is not deployed; any reference to it must be validated against the actual database before use.

Underlying Base Objects

The view text is a single-table select over AP_LOOKUP_CODES, the Payables lookup codes table, aliased as LC. There are no joins, unions, or subqueries. The documented metadata lists no referenced base objects; however, the view text itself identifies AP_LOOKUP_CODES as the sole source. Three predicates define the projection:

• LOOKUP_TYPE = 'PAYMENT METHOD' — isolates the payment method lookup set.
• ENABLED_FLAG = 'Y' — excludes lookup values that have been disabled.
• SYSDATE < NVL(INACTIVE_DATE, SYSDATE+1) — excludes values whose inactive date has passed, while treating a null inactive date as perpetually active, since SYSDATE+1 is always greater than SYSDATE.

The view is therefore a date-sensitive, status-sensitive filter rather than a transformation or aggregation. Because the predicate depends on SYSDATE, the row set returned can change over time without any underlying data modification: once an active row's INACTIVE_DATE passes the current date, that row silently drops out of the result set.

Key Columns

The view exposes three columns, mapped directly from the base table:

• LOOKUP_CODE — the internal code identifying the payment method. This is the value typically stored on transaction or payment records and is the join key for downstream queries.
• PAYMENT_METHOD — sourced from AP_LOOKUP_CODES.DISPLAYED_FIELD. This is the user-visible name of the payment method and is the appropriate column for report display, LOV presentation, and user-facing output.
• DESCRIPTION — the descriptive text associated with the lookup value, providing additional context about the method's purpose or usage.

The distinction between LOOKUP_CODE and PAYMENT_METHOD is important for integration: persist the code, display the name.

Common Use Cases and Queries

Typical scenarios include validating a payment method entered into a custom form or interface, populating a list of values, and restricting a report to currently active methods. A representative query is:

• SELECT LOOKUP_CODE, PAYMENT_METHOD, DESCRIPTION FROM AP_LC_PAYMENT_METHODS_V ORDER BY PAYMENT_METHOD; — returns the active, enabled payment methods for display or LOV use.
• SELECT LOOKUP_CODE FROM AP_LC_PAYMENT_METHODS_V WHERE LOOKUP_CODE = :p_method; — validates a supplied code, returning a row only if the method is enabled and not expired.
• Joining the view to a payments or invoice payments table on LOOKUP_CODE to resolve the display name while excluding inactive methods from results.

Because the ETRM metadata states the view is not implemented in the documented database and is Release 10SC only, teams on 12.1.1 or 12.2.2 should verify existence in their instance — for example, by querying ALL_VIEWS — before relying on it, and should consider querying AP_LOOKUP_CODES directly with equivalent predicates where the view is absent.