Results for “apbv_exp_report_dists”

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

Overview

APBV_EXP_REPORT_DISTS is a read-only view owned by the APPS schema within the Oracle Payables (AP) module. In Oracle E-Business Suite 12.1.1 and 12.2.2, the view exposes the distribution lines of expense reports that originate in Oracle Internet Expenses (OIE) and are interfaced into Payables for reimbursement processing. Each row represents a single accounting distribution associated with an expense report line, capturing the accounting flexfield, the reimbursable amount, and the project-related attributes required for cost allocation.

The view is defined as an operational security (VPD) filtered projection of AP_EXP_REPORT_DISTS_ALL. Its defining predicate, expressed as WHERE '_SEC:AERDA.ORG_ID' IS NOT NULL, invokes the Oracle EBS multi-org security policy bound to the ORG_ID column. As a result, a query executed under a given operating unit context returns only those distribution records belonging to the responsibility's authorized organization. The view is additionally declared WITH READ ONLY, preventing any DML against its contents and confirming its role as a reporting and integration surface only.

Underlying Base Objects

APBV_EXP_REPORT_DISTS is defined exclusively over the single synonym AP_EXP_REPORT_DISTS_ALL, which resolves to the partitioned base table storing expense report distributions across all operating units. Because the underlying object is an _ALL table, it holds data for every organization in the instance; the security clause on ORG_ID is what narrows visibility to the current operating unit. The view does not join to any additional tables, so no denormalized descriptive flexfields or code combination descriptions are included—consumers must join to general ledger or Payables lookup tables separately when descriptive information is required. The view's status is documented as VALID, confirming that its definition compiles successfully against the referenced synonym in both 12.1.1 and 12.2.2 environments.

Key Columns

• REPORT_DISTRIBUTION_ID — Primary identifier for the individual distribution row.
• REPORT_LINE_ID / REPORT_HEADER_ID — Foreign keys linking the distribution to its parent expense report line and header.
• ORG_ID — Operating unit identifier; drives the VPD security predicate applied by the view.
• SEQUENCE_NUM — Ordering attribute for distributions within a line.
• CODE_COMBINATION_ID — Reference to the accounting flexfield combination charged by the distribution.
• PREPARER_MODIFIED_FLAG — Indicator recording whether the expense report preparer manually altered the distribution (for example, changing the account or amount) prior to submission.
• AMOUNT — Monetary value allocated to the distribution.
• PROJECT_ID, TASK_ID, AWARD_ID, EXPENDITURE_ORGANIZATION_ID, COST_CENTER — Project accounting attributes used when expense costs are burdened against a project, task, award, and expenditure organization.
• WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY provide standard audit tracking.

Common Use Cases and Queries

Typical usage includes reconciling expense report costs against Payables invoices, auditing preparer-initiated adjustments, and extracting project cost distributions for downstream reporting. The PREPARER_MODIFIED_FLAG column is frequently queried to isolate distributions that deviated from the default accounting generated by the system.

Sample query listing preparer-modified distributions for the current operating unit:

• SELECT report_distribution_id, report_header_id, report_line_id, code_combination_id, amount, preparer_modified_flag FROM apbv_exp_report_dists WHERE preparer_modified_flag = 'Y';
• SELECT report_header_id, SUM(amount) FROM apbv_exp_report_dists GROUP BY report_header_id;
• SELECT d.report_distribution_id, d.amount, d.project_id, d.task_id FROM apbv_exp_report_dists d WHERE d.project_id IS NOT NULL;

Because the view is READ ONLY and VPD-filtered, queries are safe for ad hoc reporting, but users must initialize the correct operating unit context to obtain complete results.