Results for “so_payment_types_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view APPS.SO_PAYMENT_TYPES_V is a lightweight, lookup-driven reporting object in the Oracle E-Business Suite Order Entry (OE) product family. Its purpose is to expose the list of valid payment types defined for order capture and order management, presenting each payment type through two derived columns: PAYMENT_TYPE (the descriptive meaning) and PAYMENT_TYPE_CODE (the internal lookup code). The view is documented as VALID and owned by the APPS schema, which is consistent with the standard EBS convention of centralizing shared lookup and reference data in APPS so that it can be consumed by multiple modules without duplicating seeded data.

Rather than storing any data of its own, the view acts as a filtered projection over the Order Entry lookup repository. It presents the subset of lookup values associated with the lookup type 'PAYMENT TYPE', so that reports, concurrent programs, forms, and integration layers can retrieve a clean, human-readable enumeration of payment types without repeatedly encoding the filter predicate or joining directly to the underlying lookup infrastructure. In this sense it functions as an application-facing reference view: developers query it to populate selection lists, validate inbound interface values, or drive conditional logic in order-processing extensions.

Underlying Base Objects

The documented referenced base objects are SO_LOOKUPS (accessed through a synonym) and FND_GLOBAL (a package). The view text is defined as:

• SELECT MEANING PAYMENT_TYPE, LOOKUP_CODE PAYMENT_TYPE_CODE FROM SO_LOOKUPS WHERE LOOKUP_TYPE = 'PAYMENT TYPE'

SO_LOOKUPS is the Order Entry lookup table that stores the actual lookup rows, including the MEANING (display text) and LOOKUP_CODE (stored code value) columns used by the view, together with the LOOKUP_TYPE discriminator that classifies each row. The view simply restricts that table to a single lookup type and renames MEANING and LOOKUP_CODE to the more contextual PAYMENT_TYPE and PAYMENT_TYPE_CODE. The reference to FND_GLOBAL, the standard EBS package that exposes session context such as USER_ID, RESP_ID, ORG_ID, and language-dependent values, indicates that lookup resolution may be sensitive to the runtime environment, particularly the current language and application context. This dependency is typical of EBS lookup views and ensures the descriptive MEANING values returned reflect the caller's session.

Key Columns

• PAYMENT_TYPE — Derived from SO_LOOKUPS.MEANING. This is the descriptive, user-facing label for the payment type, suitable for display in reports, LOVs, and interface messages. It is subject to the language/translation behavior governed by the session context.
• PAYMENT_TYPE_CODE — Derived from SO_LOOKUPS.LOOKUP_CODE. This is the stored, internal code value used for validation, joins to transactional tables, and any programmatic comparison logic. Any extension or interface should match on this code rather than on the display meaning.

Common Use Cases and Queries

A typical and complete retrieval returns all configured payment types and is the most common use for populating pick lists or validating reference data:

• SELECT PAYMENT_TYPE_CODE, PAYMENT_TYPE FROM APPS.SO_PAYMENT_TYPES_V ORDER BY PAYMENT_TYPE; — Returns the full set of payment types ordered by description, appropriate for selection lists and review reports.
• SELECT PAYMENT_TYPE FROM APPS.SO_PAYMENT_TYPES_V WHERE PAYMENT_TYPE_CODE = :p_code; — Retrieves the descriptive label for a specific code, useful for decoding stored transactional values in custom reports and interfaces.
• Joins against order-related facts to enrich payment information for analysis, using PAYMENT_TYPE_CODE as the join key to whichever transactional table stores the assigned payment type.

Because the view only resolves reference data from the PAYMENT TYPE lookup type, it is best regarded as a stable presentation layer over OE lookups. Administrators maintain the underlying values through the standard lookup maintenance framework, and the view reflects those changes automatically. Consumers should avoid writing to lookup data through the view and should rely on PAYMENT_TYPE_CODE for any persistent records or comparisons.