Results for “po_quality_codes_val_v”

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

Overview

The view APPS.PO_QUALITY_CODES_VAL_V belongs to the Oracle Purchasing (PO) module and is documented in ETRM with the description "10SC ONLY - Retrofitted." It exposes a filtered, validation-ready list of quality codes that are currently active, making it suitable for use as a value set backing in Oracle E-Business Suite 12.1.1 and 12.2.2. Rather than presenting the full contents of the underlying quality code table, the view restricts rows to those that have not yet reached an inactivation date, so consumers see only codes that remain valid as of the current system date.

Within Oracle EBS, this object serves a reporting and integration function. It returns a stable, read-only projection of quality code data that can be referenced by concurrent programs, value sets, PL/SQL validation routines, and external integrations that need the effective set of quality codes. Its status is recorded as VALID under the APPS schema, confirming that it is an active, compiled object in the documented environment.

Underlying Base Objects

The view is defined over a single documented referenced base object: the synonym PO_QUALITY_CODES. By qualifying that synonym through the view definition, the projection selects only three of the base table's columns — CODE, RANKING, and DESCRIPTION — and applies a row-level filter based on the base table's INACTIVE_DATE column.

The filtering predicate is expressed as SYSDATE < NVL(INACTIVE_DATE, SYSDATE + 1). Where INACTIVE_DATE is null, the NVL function substitutes a future value that always satisfies the comparison, so null-dated codes are treated as active indefinitely. Where an inactivation date is present, the code is returned only while the current database date precedes that date. This produces a date-sensitive, self-maintaining active set without requiring any additional maintenance by the calling application.

Key Columns

• CODE — The quality code identifier. It is the primary lookup value returned by the view and is typically the value presented to users or stored on purchasing transactions that reference a quality code.
• RANKING — The ranking attribute associated with the quality code. In the context of quality codes, ranking carries the ordering or grading value used to sequence or prioritize codes.
• DESCRIPTION — The descriptive text for the quality code, used for display, reporting, and list-of-values presentation.

The view exposes no columns beyond these three. Notably, it does not project the INACTIVE_DATE column even though that column drives the filter, so consumers cannot see the inactivation date through the view and should query the base table directly if that attribute is required.

Common Use Cases and Queries

The most common use is as a validation source where only active quality codes should be selectable. A typical query returns all currently effective codes:

• SELECT code, ranking, description FROM apps.po_quality_codes_val_v ORDER BY ranking, code;
• SELECT code, description FROM apps.po_quality_codes_val_v WHERE ranking = :p_ranking;
• SELECT COUNT(*) FROM apps.po_quality_codes_val_v;

These patterns suit list-of-values definitions, report parameter validations, and integration extracts that must observe the same active-code logic as the EBS application. Because the active-status decision is evaluated against SYSDATE at execution time, results can change from one day to the next without data maintenance, and any query relying on a fixed expected result set should account for this behavior.