Search Results vehicle_category_code

Overview

APBV_EXPENSE_REPORT_LINES is a Payables (AP) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the descriptive and accounting attributes of individual expense report lines and is intended primarily for reporting, inquiry, and integration purposes rather than for transactional data entry. The view presents one row per expense report line, keyed to its parent expense report header by REPORT_HEADER_ID, alongside the full set of descriptive, tax, mileage, per diem, and receipt-tracking columns carried by the underlying table.

Because it is a view rather than a base table, APBV_EXPENSE_REPORT_LINES provides a stable, read-only interface for consumers such as custom reports, Oracle Business Intelligence extracts, and third-party interfaces. The object carries a VALID status in the data dictionary, confirming that its definition resolves cleanly against the referenced objects in both release levels.

Underlying Base Objects

The documented base object for this view is AP_EXPENSE_REPORT_LINES_ALL, accessed through a synonym in the APPS schema. The view is a straightforward projection of that base table: its SELECT list maps directly to AERLA columns, and no aggregation, join, or filter logic is applied. Column aliases in the view correspond to the base table columns without transformation, and the FIRST_UPDATE_DATE, LAST_UPDATED_BY, and audit columns are carried through unchanged.

One notable element in the view text is the literal expression '_DF:SQLAP:AP_EXPENSE_REPORT_LINES:AERLA', which is a descriptive flexfield reference string identifying the source application and table for flexfield processing. This indicates that the view participates in the descriptive flexfield framework for expense report lines, with AERLA as the registered table alias.

Key Columns

The view exposes the complete column set of the expense report line, organized into logical groups:

• Header and identity: REPORT_HEADER_ID links the line to its expense report; ITEMIZE_ID and DISTRIBUTION_LINE_NUMBER identify the line position.
• Amounts and currency: AMOUNT, STAT_AMOUNT, CURRENCY_CODE, EXCHANGE_RATE_TYPE, EXCHANGE_RATE, and EXCHANGE_DATE support multi-currency expense entry and statutory reporting.
• Tax handling: VAT_CODE, AMOUNT_INCLUDES_TAX_FLAG, TAX_CODE_OVERRIDE_FLAG, TAX_CODE_ID, MERCHANT_TAX_REG_NUMBER, MERCHANT_TAXPAYER_ID, and COUNTRY_OF_SUPPLY. The TAX_CODE_OVERRIDE_FLAG indicates whether the user manually overrode the default tax code for the line, while TAX_CODE_ID points to the applied tax code.
• Receipt and justification controls: RECEIPT_VERIFIED_FLAG, RECEIPT_REQUIRED_FLAG, RECEIPT_MISSING_FLAG, JUSTIFICATION_REQUIRED_FLAG, JUSTIFICATION, POLICY_SHORTPAY_FLAG, and credit card and merchant attribution columns.
• Per diem and mileage: EXPENSE_GROUP, START_EXPENSE_DATE, END_EXPENSE_DATE, DAILY_AMOUNT, NUM_PDM_DAYS1-3, PER_DIEM_RATE1-3, DEDUCTION_ADDITION_AMT1, plus mileage attributes such as VEHICLE_CATEGORY_CODE, DAILY_DISTANCE, AVG_MILEAGE_RATE, DESTINATION_FROM/TO, TRIP_DISTANCE, and MILEAGE_RATE_ADJUSTED_FLAG.
• Project and accounting: EXPENDITURE_TYPE, EXPENDITURE_ITEM_DATE, PA_QUANTITY, USSGL_TRANSACTION_CODE, and USSGL_TRX_CODE_CONTEXT support project costing and federal accounting.
• Multi-org: ORG_ID supports the operating unit security model.

Common Use Cases and Queries

Typical uses include expense analysis by tax code, receipt compliance reporting, and integration extracts for downstream systems. A sample query listing tax-overridden lines is:

SELECT REPORT_HEADER_ID, ITEM_DESCRIPTION, AMOUNT,
       TAX_CODE_OVERRIDE_FLAG, TAX_CODE_ID, VAT_CODE, ORG_ID
FROM   APPS.APBV_EXPENSE_REPORT_LINES
WHERE  TAX_CODE_OVERRIDE_FLAG = 'Y'
AND    ORG_ID = :p_org_id;

Aggregating receipt exceptions by header is likewise straightforward:

SELECT REPORT_HEADER_ID,
       SUM(AMOUNT) total_amount,
       COUNT(*)    line_count
FROM   APPS.APBV_EXPENSE_REPORT_LINES
WHERE  RECEIPT_MISSING_FLAG = 'Y'
GROUP  BY REPORT_HEADER_ID;

Because the view has no embedded business logic, all filtering, security enforcement through ORG_ID, and join logic to header or tax tables must be supplied by the querying application. Reports should therefore join to AP expense report header views or tables on REPORT_HEADER_ID and apply operating unit predicates explicitly.