Search Results receipt_status

Overview

AP_RECEIPT_STATUS_V is a Payables (AP) lookup view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the internal lookup values that define the set of valid receipt statuses used within Oracle Payables. The view is a thin, filtered projection over the AP_LOOKUP_CODES view, restricted to the lookup type RECEIPT_STATUS. Because it isolates a single lookup category, it presents the receipt status domain in a clean, self-contained form suitable for reporting, validation, and integration rather than reading the broader lookup table directly.

The view is documented in ETRM as a VALID object under the AP - Payables product. Its role in reporting and integration is to provide a stable, human-readable enumeration of receipt statuses, including the internal code, the display text shown to users, and an optional description. External systems and interfaces that must map or validate Payables receipt status values can query this view instead of hard-coding the status list, so that the set of valid values stays synchronized with the application's own lookup definitions. The view also participates implicitly in Application Object Library context through FND_GLOBAL, which supplies runtime environment information used by the underlying lookup mechanism.

Underlying Base Objects

Per the documented ETRM metadata, AP_RECEIPT_STATUS_V references the following base objects:

• AP_LOOKUP_CODES (VIEW) — the primary source object. The view text is a simple SELECT from AP_LOOKUP_CODES with the filter LOOKUP_TYPE = 'RECEIPT_STATUS', projecting the LOOKUP_CODE, DISPLAYED_FIELD, and DESCRIPTION columns.
• FND_GLOBAL (PACKAGE) — referenced by the underlying lookup infrastructure to resolve session and environment context, such as the current application and language, ensuring the returned lookup values are consistent with the executing session.

Because AP_LOOKUP_CODES is itself a view rather than a physical table, AP_RECEIPT_STATUS_V forms part of a layered lookup access path: the physical lookup data resides in the Application Object Library lookup tables, AP_LOOKUP_CODES presents the Payables-relevant subset, and AP_RECEIPT_STATUS_V narrows that subset further to a single lookup type. This layering means the view does not store data and cannot be updated directly; it reflects whatever values are maintained for the RECEIPT_STATUS lookup type in the underlying lookup framework.

Key Columns

The view exposes three columns, as documented in the view text:

• LOOKUP_CODE — the internal, stored code that identifies a receipt status. This is the value typically held on transactional records and used in programmatic comparisons, joins, and interfaces.
• DISPLAYED_FIELD — the user-facing text for the status, as displayed on forms and reports. This is the value suitable for presentation in output and for mapping codes to readable labels.
• DESCRIPTION — additional explanatory text for the status value, where maintained. It provides supplementary context and is often null or optional depending on how the lookup value was defined.

Collectively, these columns let consumers translate between the internal lookup code and the label shown to end users without accessing the wider lookup structures directly.

Common Use Cases and Queries

Typical scenarios include populating report layouts with readable receipt status labels, validating inbound or outbound interface values against the set of permitted receipt statuses, and building LOV-style reference lists for custom forms or integrations. The following query returns the complete, current receipt status enumeration:

• SELECT LOOKUP_CODE, DISPLAYED_FIELD, DESCRIPTION FROM APPS.AP_RECEIPT_STATUS_V ORDER BY LOOKUP_CODE;

To resolve a single status to its display text, filter by the code:

• SELECT DISPLAYED_FIELD, DESCRIPTION FROM APPS.AP_RECEIPT_STATUS_V WHERE LOOKUP_CODE = :p_code;

The view can also be joined to any transactional or interface table that stores a receipt status code, using LOOKUP_CODE as the join key to attach descriptive text. Because the object is a view over lookup data, results always reflect the currently maintained RECEIPT_STATUS values, making it a dependable reference source across both 12.1.1 and 12.2.2.