Search Results report_weight

Overview

APPS.AP_AUD_QUEUE_SUMMARIES_V is an Oracle E-Business Suite database view that consolidates audit queue workload information by auditor. It provides a pre-aggregated summary of the records held in the Payables audit queue, presenting one row per auditor together with a total workload figure and supporting count metrics. Because the view performs its own GROUP BY aggregation, consumers obtain derived summary statistics directly without writing their own aggregation logic against the underlying queue table.

The object is owned by the APPS schema and is registered in the E-Business Suite Technical Reference Manual (ETRM) for release 12.2.2, and it is also applicable to 12.1.1. In the context of Oracle Payables reporting and integration, the view functions as a lightweight, read-only presentation layer over the audit queue. It is typically consumed by audit workload dashboards, printable reports, and downstream interfaces that require a per-auditor workload snapshot rather than the full detail of individual queued documents. The term "report_weight" is central to its semantics: the view does not merely count queued items, it sums a weighting factor that quantifies the relative effort associated with each queued report.

Underlying Base Objects

The view is defined over a single documented base object, referenced as AP_AUD_QUEUES (SYNONYM). AP_AUD_QUEUES is the Payables audit queue, the structure in which individual Payables documents awaiting audit review are held and assigned to an auditor. Each row in AP_AUD_QUEUES represents a queued item, carries an auditor identifier, and includes a REPORT_WEIGHT value representing the workload contributed by that item.

Because the view is defined strictly on AP_AUD_QUEUES and applies no joins, its contents are coextensive with the aggregated contents of that table. The view does not persist data; it is re-evaluated on each query, so results always reflect the current state of the audit queue. The APPS synonym exposes the underlying queue to the EBS application schema, and AP_AUD_QUEUE_SUMMARIES_V inherits that same APPS ownership and accessibility.

Key Columns

• AUDITOR_ID — The identifier of the auditor to whom queued items are assigned. This is the grouping key; exactly one row is returned per distinct auditor present in the audit queue.
• CURRENT_TOTAL_WORKLOAD — Defined as SUM(REPORT_WEIGHT). This is the aggregate workload for the auditor, derived by summing the report weight of every queued item assigned to that auditor. It is the primary metric for assessing how much audit effort is currently outstanding.
• COUNT_REPORT_WEIGHTS — Defined as COUNT(REPORT_WEIGHT). This counts only those rows where REPORT_WEIGHT is not null. Comparing it with COUNT_REPORTS reveals how many queued items lack a weight value.
• COUNT_REPORTS — Defined as COUNT(*). This is the total number of queued reports for the auditor, regardless of whether REPORT_WEIGHT is populated, providing the raw volume behind the weighted total.

Common Use Cases and Queries

The principal use case is auditor workload balancing. Auditors and their supervisors compare CURRENT_TOTAL_WORKLOAD across auditors to identify uneven distribution and reassign queued items accordingly. A second use case is reconciliation: comparing COUNT_REPORT_WEIGHTS against COUNT_REPORTS highlights queued records with a missing or null REPORT_WEIGHT, which would otherwise understate total workload.

Typical queries include:

• Retrieve all auditors ranked by workload: SELECT auditor_id, current_total_workload, count_reports FROM apps.ap_aud_queue_summaries_v ORDER BY current_total_workload DESC;
• Inspect a single auditor's summary: SELECT * FROM apps.ap_aud_queue_summaries_v WHERE auditor_id = :auditor_id;
• Detect unweighted queued items: SELECT auditor_id, count_reports - count_report_weights AS items_without_weight FROM apps.ap_aud_queue_summaries_v WHERE count_reports > count_report_weights;

Because aggregation is embedded in the view, these queries require no GROUP BY clause at the call site, simplifying report and dashboard development.