Results for “ap_po_usrdef_lookup_codes_v”

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

Overview

AP_PO_USRDEF_LOOKUP_CODES_V is a Payables (AP) module view in Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented as retrofitted, meaning it was introduced or adapted to preserve backward compatibility for customizations, extensions, or integrations that previously referenced an equivalent lookup structure. The view consolidates user-defined lookup code information drawn from both Payables and Purchasing (PO) lookup code tables into a single, uniformly shaped result set.

The object was searched in the context of the column "application_name", which is the first column exposed by the view and serves as the human-readable label of the owning application. Because the view unions Payables and Purchasing lookup data, the application_name column allows consumers to distinguish which product module a given lookup code belongs to — for example, Payables versus Purchasing — without joining to FND_APPLICATION_VL themselves. This makes the view convenient for reporting, ad hoc queries, and lightweight integration views where lookup values must be presented with their originating application context.

Underlying Base Objects

The view is defined over two lookup code tables joined to the application definition view. The documented view text references AP_LOOKUP_CODES and PO_LOOKUP_CODES, each joined to FND_APPLICATION_VL to resolve the application name. The structure consists of a UNION of two SELECT statements.

• AP_LOOKUP_CODES — the Payables lookup codes table, contributing rows with a hard-coded APPLICATION_ID of 200 and the application name resolved from FND_APPLICATION_VL for that application.
• PO_LOOKUP_CODES — the Purchasing lookup codes table, contributing rows with a hard-coded APPLICATION_ID of 201 and the application name resolved from FND_APPLICATION_VL for that application.
• FND_APPLICATION_VL — the application definition view used to translate application identifiers into display names.

Both branches filter on LOOKUP_TYPE = 'LOOKUP TYPE', which appears in the documented text as a placeholder literal. In practice the filter restricts the results to a specific lookup type, so the view as documented represents a template or retrofitted definition whose effective lookup type may be parameterized or replaced in deployed environments. Notably, the ETRM metadata records that the view is "Not implemented in this database", and no referenced base objects are separately documented, indicating the definition may not be active in every instance.

Key Columns

• APPLICATION_NAME — the display name of the owning Oracle application, resolved from FND_APPLICATION_VL. This is the column referenced by the supplied search term and is the primary differentiator between the two union branches.
• APPLICATION_ID — numeric application identifier. Payables rows carry 200; Purchasing rows carry 201. Because these are literal values, the column reliably identifies the source module.
• LOOKUP_CODE — the code value of the user-defined lookup entry.
• DISPLAYED_FIELD — the displayed description or label associated with the lookup code, taken directly from the source lookup table.
• DESCRIPTION — the longer descriptive text for the lookup code.

Common Use Cases and Queries

Typical uses include validating user-defined lookup values across Payables and Purchasing, building reports that show lookup codes together with their owning application, and supporting migration or reconciliation scripts that compare lookup definitions between modules.

Sample query to list lookup values with their application context:

• SELECT application_name, application_id, lookup_code, displayed_field, description FROM ap_po_userdef_lookup_codes_v ORDER BY application_name, lookup_code;
• SELECT lookup_code, displayed_field FROM ap_po_userdef_lookup_codes_v WHERE application_name = 'Payables';
• SELECT application_id, COUNT(*) FROM ap_po_userdef_lookup_codes_v GROUP BY application_id;

Because the documented definition contains a placeholder lookup type and is marked not implemented, developers should verify the deployed view text before relying on it, and confirm whether the filter must be adjusted or whether an alternative lookup view should be used.