Results for “inactive_date”

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

Overview

AP_LOOKUP_CODES is a Payables (AP) module view owned by the APPS schema and defined over the Oracle Application Object Library lookup infrastructure. In Oracle EBS 12.1.1 and 12.2.2, it exposes the set of lookup values that pertain specifically to Oracle Payables, filtering the general FND_LOOKUP_VALUES repository by the Payables application identifier (VIEW_APPLICATION_ID = 200) and by the language and security group of the current session. The view therefore behaves as a curated, session-aware window onto Payables lookup codes such as payment terms categories, invoice match options, hold classifications, and other code/meaning pairs used throughout the AP product.

Because it presents lookup codes in a denormalized, human-readable form (code plus translated meaning), AP_LOOKUP_CODES is frequently used for reporting and integration rather than for transactional processing. Report developers, discoverer workbooks, and outbound interfaces rely on it to resolve stored lookup codes into their descriptive meanings without writing joins against FND_LOOKUP_VALUES directly. The ETRM metadata records the object as VALID and owned by APPS, confirming it is a supported, documented view in both release levels.

Underlying Base Objects

The ETRM metadata documents two referenced objects: the FND_LOOKUP_VALUES synonym and the FND_GLOBAL package. The view text selects from FND_LOOKUP_VALUES (aliased LV), applying the following predicates: LV.LANGUAGE = USERENV('LANG'), LV.VIEW_APPLICATION_ID = 200, and LV.SECURITY_GROUP_ID = FND_GLOBAL.LOOKUP_SECURITY_GROUP(LV.LOOKUP_TYPE, LV.VIEW_APPLICATION_ID).

• FND_LOOKUP_VALUES — the underlying lookup value repository holding every lookup code across applications, with language-specific rows and security group partitioning.
• FND_GLOBAL — the PL/SQL package supplying LOOKUP_SECURITY_GROUP, which resolves the security group applicable to the current lookup type and application, ensuring only values visible to the session are returned.
• USERENV('LANG') — the session language, restricting rows to the installed language of the connecting user.

Consequently the view does not store data; it is a filtered projection over the shared lookup tables, and any change to a Payables lookup value is immediately reflected.

Key Columns

The documented column list comprises LOOKUP_TYPE, LOOKUP_CODE, DISPLAYED_FIELD, DESCRIPTION, ENABLED_FLAG, START_DATE_ACTIVE, and INACTIVE_DATE. Note that the ETRM column listing uses DISPLAYED_FIELD and INACTIVE_DATE, which correspond in the underlying FND_LOOKUP_VALUES structure to the MEANING and END_DATE_ACTIVE attributes shown in the view text.

• LOOKUP_TYPE — the lookup category (for example, payment terms or invoice types) that groups related codes.
• LOOKUP_CODE — the stored internal code value.
• DISPLAYED_FIELD / MEANING — the translated, user-facing description of the code.
• DESCRIPTION — additional free-text detail about the lookup value.
• ENABLED_FLAG — indicates whether the value is currently active (Y/N).
• START_DATE_ACTIVE / INACTIVE_DATE — the effective date range during which the lookup value is valid.

Common Use Cases and Queries

Typical uses include resolving codes on AP reports, populating LOVs or reference lists in custom forms, and validating codes during inbound interface processing. A common query retrieves all active Payables lookups for a given type:

• SELECT lookup_code, displayed_field FROM ap_lookup_codes WHERE lookup_type = 'PAYMENT_TERMS' AND enabled_flag = 'Y' ORDER BY lookup_code;
• SELECT lookup_type, COUNT(*) FROM ap_lookup_codes GROUP BY lookup_type;

Because the view already applies language and security group filtering, queries require no additional join to FND_LOOKUP_VALUES, simplifying both reporting and integration code.