Results for “ap_oie_cc_validation_error_v”

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

Overview

The AP_OIE_CC_VALIDATION_ERROR_V view is a lightweight lookup-extraction view owned by the APPS schema in Oracle E-Business Suite Payables (AP). Rather than storing data of its own, it exposes a filtered subset of rows from the Oracle Applications lookup repository, specifically those belonging to the lookup type OIE_CC_VALIDATION_ERROR. The view is documented as VALID in ETRM for both release 12.1.1 and 12.2.2, and its definition consists of a single SELECT against AP_LOOKUP_CODES.

Its role in the EBS application stack is that of a controlled access point for the set of validation-error codes and messages used by the Oracle Internet Expenses (OIE) credit card (CC) processing flow. Instead of querying the generic lookup table directly, forms, concurrent programs, or integration routines can reference this view to retrieve the canonical list of validation-error lookup codes, the displayed field text, and the corresponding description. This promotes consistency in how credit card validation errors are presented to end users and recorded for reconciliation and reporting.

Underlying Base Objects

The ETRM metadata identifies two referenced base objects:

• AP_LOOKUP_CODES (VIEW) — the immediate source of the three projected columns. It is itself a view over the Oracle Applications lookup foundation tables and provides lookup rows keyed by LOOKUP_TYPE.
• FND_GLOBAL (PACKAGE) — the standard EBS session-context package supplying application, responsibility, and user identifiers. Referencing it indicates the view operates within the standard Oracle Application Object Library (AOL) context, so lookups resolved may be influenced by language and application environment settings.

The view text is defined as:

SELECT LOOKUP_CODE, DISPLAYED_FIELD, DESCRIPTION FROM AP_LOOKUP_CODES WHERE LOOKUP_TYPE = 'OIE_CC_VALIDATION_ERROR'

Because AP_LOOKUP_CODES is a view rather than a base table, the underlying physical storage resides in the AOL lookup tables maintained by the Applications DBA. The effective ETRM 12.2.2 metadata confirms the same dependency chain, so behavior is consistent across 12.1.1 and 12.2.2.

Key Columns

• LOOKUP_CODE — the unique code identifying each validation error within the OIE_CC_VALIDATION_ERROR lookup type. This is the value consumed programmatically by OIE credit card validation logic.
• DISPLAYED_FIELD — the rendered value or field representation associated with the lookup code, used to populate UI fields or generated messages.
• DESCRIPTION — the human-readable explanation of the validation error, suitable for message text, log entries, and troubleshooting documentation.

All three columns are derived directly from the underlying lookup view and inherit its language and context sensitivity.

Common Use Cases and Queries

Typical scenarios include validating the completeness of OIE credit card error messages, extracting error text for reconciliation reports, and confirming that a specific lookup code is defined before it is referenced in customization or extension code.

A basic retrieval of all defined validation errors:

SELECT lookup_code, displayed_field, description FROM apps.ap_oie_cc_validation_error_v ORDER BY lookup_code;

Filtering for a single code during troubleshooting:

SELECT lookup_code, displayed_field, description FROM apps.ap_oie_cc_validation_error_v WHERE lookup_code = :p_code;

Joining to credit card transaction data to add descriptive error text:

SELECT t.transaction_id, t.lookup_code, v.description FROM ap_credit_card_trxns t, apps.ap_oie_cc_validation_error_v v WHERE v.lookup_code = t.lookup_code;

Because the view is a thin filter over lookup data, no maintenance should be performed against it; corrections are made by maintaining the OIE_CC_VALIDATION_ERROR lookup type through the standard Oracle Applications lookup maintenance forms. This guarantees the view remains synchronized with the reference data across both 12.1.1 and 12.2.2 environments.