Results for “expense_report_id”

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

Overview

The AP_AUD_QUEUES table in the AP (Payables) schema is a transactional control table used by the Oracle E-Business Suite expense auditing workflow. It stores the audit queue — a list of expense reports that have been submitted for auditing together with the auditor to whom each report has been assigned. In Oracle Payables and Internet Expenses, expense reports may be routed to auditors for review before reimbursement; AP_AUD_QUEUES functions as the assignment ledger that drives that review process, tracking which expense reports are pending audit and who owns them.

Because the table's documented structure is a pure association between two independent entities (an expense report and an auditor), a Data Vault modeling heuristic classifies AP_AUD_QUEUES as a link table. It carries no descriptive attributes of its own beyond a weighting value and standard audit columns, which reinforces its role as a join artifact recording a many-to-many-style relationship. This classification is a modeling suggestion derived from the foreign-key structure, not an Oracle-declared designation.

Key Information Stored

The documented physical schema (ETRM 12.2.2) contains eight columns. The most important are:

• EXPENSE_REPORT_ID — The foreign key to AP_EXPENSE_REPORTS_ALL identifying the expense report placed in the audit queue. It is also the primary key column of AP_AUD_QUEUES_PK and the business-key candidate captured by the unique index AP_AUD_QUEUES_U1, so each expense report can appear only once in the queue.
• AUDITOR_ID — The foreign key to AP_AUD_AUDITORS identifying the auditor assigned to review the expense report.
• REPORT_WEIGHT — A numeric weighting value used to order or prioritize the queued reports, typically to drive the sequence in which auditors process their workload.
• CREATION_DATE, CREATED_BY — Standard WHO columns recording when and by whom the queue row was inserted.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO columns recording the most recent modification and the login context of the last updater.

The surrogate primary key is AP_AUD_QUEUES_PK, defined on EXPENSE_REPORT_ID. The unique index AP_AUD_QUEUES_U1 on the same column confirms EXPENSE_REPORT_ID as the business-key candidate, meaning the table enforces a one-report-per-queue-entry constraint. Note that AUDITOR_ID is a foreign key but not part of the unique key, so while a given report maps to a single queue row, an auditor may hold many rows.

Common Use Cases and Queries

Typical scenarios include reporting on audit backlog, balancing auditor workloads, and identifying the auditor responsible for a specific report. A common query joins the queue to the expense report header to list pending audits by auditor:

• SELECT q.auditor_id, q.expense_report_id, q.report_weight, r.expense_report_num, r.total FROM ap.ap_aud_queues q, ap.ap_expense_reports_all r WHERE q.expense_report_id = r.expense_report_id ORDER BY q.auditor_id, q.report_weight;
• Counting queued reports per auditor: SELECT auditor_id, COUNT(*) FROM ap.ap_aud_queues GROUP BY auditor_id.
• Locating a report's assignment: SELECT auditor_id, report_weight FROM ap.ap_aud_queues WHERE expense_report_id = :report_id.
• Auditing row history using the WHO columns: SELECT creation_date, created_by, last_update_date, last_updated_by FROM ap.ap_aud_queues WHERE expense_report_id = :report_id.

These queries support audit-workload dashboards, SLA monitoring for expense reimbursement, and reconciliation of reports that have been routed but not yet released.

Related Objects

The following objects are directly related to AP_AUD_QUEUES through documented primary and foreign key relationships:

• AP_EXPENSE_REPORTS_ALL — The parent expense report table joined on EXPENSE_REPORT_ID; supplies report number, employee, and amount context.
• AP_AUD_AUDITORS — The auditor definition table joined on AUDITOR_ID; identifies who owns the queued assignment.
• AP_AUD_QUEUES_PK — The primary key constraint enforcing one row per expense report.
• AP_AUD_QUEUES_U1 — The unique index on EXPENSE_REPORT_ID, confirming the business key.
• AP_AUD_AUDITORS and its auditor-assignment configuration — Related through the AUDITOR_ID foreign key and typically joined when reporting auditor workload.

Additional integration points include the Internet Expenses (OIE) audit workflow and the Payables audit pages, which read and write queue rows as auditors claim, review, and release expense reports.