Search Results ap_expense_report_lines_all

Overview

The AP_EXPENSE_REPORT_LINES_ALL table is a core data structure within the Oracle E-Business Suite Payables (AP) module, specifically for the Employee Expenses (iExpenses) functionality. It stores detailed line-level information for individual expense items submitted on employee expense reports. Each record in this table represents a single expense entry, such as a meal, hotel stay, or mileage, that is part of a larger expense report header. Its primary role is to capture the transactional details, accounting distributions, and policy compliance attributes for each incurred expense, serving as the foundation for validation, approval, auditing, and subsequent accounting processes in Oracle EBS releases 12.1.1 and 12.2.2.

Key Information Stored

The table's columns can be categorized into several key functional areas. The primary identifier is REPORT_LINE_ID, with REPORT_HEADER_ID linking the line to its parent report in AP_EXPENSE_REPORT_HEADERS_ALL. Critical financial data includes ITEM_AMOUNT, CURRENCY_CODE, and the derived accounting CODE_COMBINATION_ID. For policy and audit trails, columns like EXPENSE_CATEGORY_CODE, MERCHANT_NAME, RECEIPT_CURRENCY_CODE, and RECEIPT_CONVERSION_RATE are essential. Project accounting integration is facilitated by PROJECT_ID, TASK_ID, and EXPENDITURE_TYPE. The table also manages tax withholding via AWT_GROUP_ID and tracks corporate card transactions through CREDIT_CARD_TRX_ID. The SET_OF_BOOKS_ID ensures multi-org accounting integrity.

Common Use Cases and Queries

This table is central to numerous operational and analytical processes. Common use cases include auditing expense reports for policy compliance, reconciling corporate card statements, generating detailed expense analytics by category or project, and troubleshooting accounting interface errors. A frequent reporting query involves joining to the header table to analyze expenses:

• SELECT h.report_header_id, h.employee_id, l.expense_category_code, l.item_amount, l.merchant_name FROM ap_expense_report_headers_all h, ap_expense_report_lines_all l WHERE h.report_header_id = l.report_header_id AND h.org_id = :p_org_id;

For project costing, a join to PA_PROJECTS_ALL and PA_TASKS on PROJECT_ID and TASK_ID is standard. Technical integrations often query this table to validate or extract expense data before creating invoices or interfacing to GL via the AP_EXP_REPORT_DISTS_ALL distribution lines.

Related Objects

AP_EXPENSE_REPORT_LINES_ALL has extensive relationships within the EBS schema, as indicated by its foreign keys. The primary parent table is AP_EXPENSE_REPORT_HEADERS_ALL. Its most critical child table is AP_EXP_REPORT_DISTS_ALL, which holds the detailed accounting distributions for each expense line. For Project Accounting integration, it references PA_PROJECTS_ALL, PA_TASKS, and PA_EXPENDITURE_TYPES. Financial integration points include GL_CODE_COMBINATIONS, FND_CURRENCIES, and GL_DAILY_CONVERSION_TYPES. Other significant related objects are AP_CREDIT_CARD_TRXNS_ALL for card data, AP_INVOICES_ALL for prepaid expenses, and AP_POL_LOCATIONS_B for policy locations. The OIE_ATTENDEES_ALL table may also link to it for expense lines with attendee details.