Search Results source_entity_code

Overview

APFV_AP_INVOICE_LINES is a business view owned by the APPS schema in Oracle E-Business Suite Payables (AP). It exposes invoice line-level detail for reporting, inquiry, and integration purposes. In both 12.1.1 and 12.2.2, the object is registered with status VALID in the ETRM repository, and its documented description is simply "Business View." The view presents a flattened, denormalized projection of invoice distribution and matching attributes, allowing report writers, concurrent programs, and interfaces to retrieve line information without navigating the more heavily normalized transactional base table directly.

The naming convention (the "FV" infix) indicates a view intended primarily for read-only access, typically surfaced through Oracle Forms inquiry windows, Oracle Business Intelligence Publisher reports, and custom extensions. Because it is owned by APPS and presented as a business view, consumers should treat it as a stable reporting interface rather than as an updateable entity.

Underlying Base Objects

The ETRM 12.2.2 metadata documents a single referenced base object: AP_INVOICE_LINES_ALL, accessed through a synonym in the APPS schema. AP_INVOICE_LINES_ALL is the core Payables table holding all invoice line records across operating units, and it is partitioned by ORG_ID. The view therefore inherits the multi-org architecture of that table: ORG_ID is exposed as a column, and querying without an operating unit predicate will return lines across organizations to which the session has access.

Because the view is defined over a single base table, join semantics are straightforward. Additional descriptive data (supplier, invoice header, PO, receipt, and project context) is not resolved within the view itself and must be obtained by joining to AP_INVOICES_ALL, PO_HEADERS_ALL, PO_LINES_ALL, RCV_TRANSACTIONS, or PA_PROJECTS as required. The view text is a direct column projection, with no aggregation or UNION, so row counts correspond one-to-one with the qualifying rows in AP_INVOICE_LINES_ALL.

Key Columns

• INVOICE_ID, LINE_NUMBER — Primary identifiers linking the line to its invoice header and to distributions.
• LINE_TYPE_LOOKUP_CODE, LINE_SOURCE, MATCH_TYPE — Classify the line type (ITEM, FREIGHT, TAX, MISCELLANEOUS), its origin, and its matching basis (PO, RECEIPT, or none).
• AMOUNT, BASE_AMOUNT, ORIGINAL_AMOUNT, QUANTITY_INVOICED, UNIT_PRICE — Financial and quantity measures central to line-level reconciliation and audit.
• PO_HEADER_ID, PO_LINE_ID, PO_DISTRIBUTION_ID, RCV_TRANSACTION_ID, FINAL_MATCH_FLAG — Link invoice lines to procurement and receiving documents for three- and four-way match reporting.
• CREDIT_CARD_TRX_ID, CC_REVERSAL_FLAG, MERCHANT_NAME, MERCHANT_REFERENCE, MERCHANT_TAX_REG_NUMBER — The columns relevant to the search term "credit_card_trx_id." CREDIT_CARD_TRX_ID associates a line originating from a corporate credit card transaction with its record in the credit card transaction tables, while CC_REVERSAL_FLAG indicates whether the line represents a reversal of a previously charged card transaction.
• PROJECT_ID, TASK_ID, EXPENDITURE_TYPE, PA_QUANTITY — Project accounting context for expenditure items.
• DEFERRED_ACCTG_FLAG and DEF_ACCTG_* columns — Describe deferral schedules for prepaid or deferred expense lines.

Common Use Cases and Queries

The view supports credit card reconciliation reporting, unmatched line analysis, project expenditure extracts, and audit trails. A typical query isolating credit card lines is:

SELECT invoice_id, line_number, credit_card_trx_id,
       cc_reversal_flag, merchant_name,
       amount, base_amount
FROM   apps.apfv_ap_invoice_lines
WHERE  credit_card_trx_id IS NOT NULL
AND    org_id = :p_org_id;

For match exception reporting, filter on MATCH_TYPE and FINAL_MATCH_FLAG; for project reporting, filter on PROJECT_ID and EXPENDITURE_ITEM_DATE. Always constrain ORG_ID in multi-org environments, and join to AP_INVOICES_ALL for supplier and invoice date context.