Results for “ap_oie_ticket_class_v”

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

Overview

AP_OIE_TICKET_CLASS_V is a lightweight reporting view owned by the APPS schema within the Oracle Payables (AP) module. Its purpose is to expose the set of valid ticket classification codes used by Oracle Internet Expenses (OIE) in a form that is directly consumable by reports, integrations, and extensions. The underlying data is sourced from the Payables lookup mechanism, specifically the lookup type OIE_TICKET_CLASS. Because the view is a simple projection over lookup data rather than a transactional table, it returns a small, stable reference list rather than dynamic business transactions, which makes it suitable for joining, caching, and validation logic.

The view carries a VALID status in the ETRM 12.2.2 metadata, and the object is present in both the 12.1.1 and 12.2.2 releases as an APPS-owned artifact. In practice it behaves as a dictionary-style view that decodes and labels ticket class values for downstream applications such as expense audit reporting, ticket creation, and classification extracts.

Underlying Base Objects

According to the documented view text, AP_OIE_TICKET_CLASS_V is defined over AP_LOOKUP_CODES, filtered to the lookup type OIE_TICKET_CLASS:

• AP_LOOKUP_CODES — a Payables view that stores lookup code values used throughout the AP module. The view restricts this source to a single lookup type, so only ticket classification entries are surfaced.
• FND_GLOBAL — listed as a referenced base object. This package supplies session context such as USER_ID, RESP_ID, and ORG_ID. Its presence indicates the view definition may incorporate a security or context predicate, even though the exposed column list is limited to lookup attributes.

Because the source is itself a view over the Payables lookup data, changes to the underlying lookup configuration propagate immediately to AP_OIE_TICKET_CLASS_V. No materialization or staging table is involved.

Key Columns

The view exposes three columns, all inherited directly from the lookup source:

• LOOKUP_CODE — the internal code value stored on the ticket record. This is the value that OIE and Payables validation logic compares against; it is the canonical key returned by the view.
• DISPLAYED_FIELD — the user-facing or displayed value presented in the application UI. It is typically the descriptive label shown in selection lists and reports in place of the raw code.
• DESCRIPTION — a longer descriptive text associated with the lookup entry, useful for explanatory columns in reports and for documenting the meaning of each ticket class.

No audit, timestamp, or who-columns are exposed; the view is intentionally narrow and reference-oriented.

Common Use Cases and Queries

Typical applications include expense audit reporting, ticket class reference listings, and joining classification codes to expense or ticket facts. A basic listing follows:

• Retrieve all ticket classes: SELECT lookup_code, displayed_field, description FROM ap_oie_ticket_class_v ORDER BY lookup_code;
• Decode a stored class: SELECT displayed_field FROM ap_oie_ticket_class_v WHERE lookup_code = :ticket_class;
• Join to expense lines: relate the view to ticket or expense tables on lookup_code to translate stored codes into readable labels in custom reports.
• Validation: use the view to confirm that a supplied code is a current, valid OIE ticket class before persisting it.

Consult the Oracle Payables and OIE documentation before extending dependent logic, since new lookup codes for OIE_TICKET_CLASS automatically appear in the view without code changes.