Search Results ap_invoice_lines_interface_v

Overview

The AP_INVOICE_LINES_INTERFACE_V view resides in the APPS schema and belongs to the Oracle Payables (AP) product module. It is the reporting and inquiry layer over the AP_INVOICE_LINES_INTERFACE table, which serves as the staging area for invoice lines loaded through the Payables Open Interface Import process. While the base table accepts raw, unvalidated invoice line data, the view enriches those rows with resolved descriptive information drawn from related EBS entities such as purchase orders, projects, tasks, withholding tax groups, and distribution sets, so that implementers and support analysts can inspect interface content before, during, or after import.

In EBS 12.1.1 and 12.2.2, the view is documented as VALID and is referenced heavily during Open Interface diagnostics. It presents the interface line together with the distribution accounting flexfield, making it possible to trace exactly how an invoice line is expected to be accounted at the moment of import.

Underlying Base Objects

The view is defined principally over AP_INVOICE_LINES_INTERFACE (aliased AILI) and joins to AP_INVOICES_INTERFACE for header-level context. To resolve reference values, it accesses AP_AWT_GROUPS, AP_DISTRIBUTION_SETS, AP_TAX_CODES, and AP_LOOKUP_CODES. Purchasing attributes are resolved through PO_DISTRIBUTIONS, PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, and PO_RELEASES. Project-related columns are enriched using PA_PROJECTS_ALL, PA_TASKS_EXPEND_V, PA_TASK_UTILS, and PA_UTILS4.

Security and environmental context are supplied by FND_GLOBAL, FND_PROFILE, HR_GENERAL, HR_SECURITY, HR_LOCATIONS, and HR_ORGANIZATION_UNITS. This dependence on HR security packages means the view respects operating unit and organization-level access rules at runtime, which is significant when querying interface data across multiple operating units.

Key Columns

Column naming mirrors the base interface table almost one-for-one. Core attributes include INVOICE_ID, LINE_NUMBER, LINE_TYPE_LOOKUP_CODE, AMOUNT, UNIT_PRICE, and QUANTITY_INVOICED. Matching and correction flags such as PRICE_CORRECTION_FLAG, FINAL_MATCH_FLAG, and ASSETS_TRACKING_FLAG govern downstream processing behavior.

Purchasing references are exposed via PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, PO_RELEASE_ID, and PO_DISTRIBUTION_ID. Project accounting columns include PROJECT_ID, TASK_ID, EXPENDITURE_TYPE, EXPENDITURE_ITEM_DATE, EXPENDITURE_ORGANIZATION_ID, and PA_QUANTITY. The columns most directly relevant to the search term dist_code_concatenated are DIST_CODE_CONCATENATED and its companion DIST_CODE_COMBINATION_ID. The concatenated column carries the human-readable accounting flexfield string for the interface distribution line, while the ID column holds the surrogate key to GL_CODE_COMBINATIONS. When DIST_CODE_COMBINATION_ID is null, DIST_CODE_CONCATENATED is typically the only populated value the loader can use to derive the code combination, making it the critical diagnostic field for import failures.

Common Use Cases and Queries

Typical usage includes auditing interface rows prior to Open Interface Import, diagnosing failures where no accounting combination could be derived, and reconciling interface amounts against posted invoice distributions. A representative query locating rows where only the concatenated segment exists:

• SELECT line_number, amount, dist_code_concatenated, dist_code_combination_id, line_type_lookup_code FROM ap_invoice_lines_interface_v WHERE invoice_id = :invoice_id;
• SELECT line_number, description FROM ap_invoice_lines_interface_v WHERE dist_code_concatenated IS NOT NULL AND dist_code_combination_id IS NULL;
• SELECT po_header_id, po_line_id, dist_code_concatenated, amount FROM ap_invoice_lines_interface_v WHERE invoice_id = :invoice_id AND line_type_lookup_code = 'ITEM';

Because the view enriches interface data with PO, project, and HR security context, it is preferable to querying AP_INVOICE_LINES_INTERFACE directly when investigating cross-module validation errors.