Search Results doc_category_code

Overview

OKL_EXT_PAY_INVS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL – Leasing and Finance Management product family. It exposes header-level information about invoices that originate in Oracle Lease and Finance Management and are exported to Oracle Payables for payment processing. In both EBS 12.1.1 and 12.2.2 the view operates as a read-only integration surface: the Leasing application creates and manages invoice records internally, then publishes them to Payables through the standard export process, and this view provides the queryable representation of those exported invoice headers.

The object is therefore primarily consumed by reporting, reconciliation, and interface-monitoring activities rather than by transactional data entry. Because its columns mirror the attributes required by the Payables invoice interface, the view is frequently the point of reference when validating whether a leasing invoice has been staged, exported, or successfully transferred.

Underlying Base Objects

According to the ETRM 12.2.2 metadata, the view is defined over two base objects, both exposed through synonyms in the APPS schema:

• OKL_EXT_PAY_INVS_B — the base table holding invoice header attributes such as invoice number, invoice type, vendor, amount, currency, terms, payment method, and GL date.
• OKL_EXT_PAY_INVS_TL — the translation table supplying descriptive and stream-related attributes, including DESCRIPTION, SOURCE, and STREAM_TYPE.

The view text joins these two objects, aliased XPIB (base) and XPIT (translation), and selects the base table ROWID as ROW_ID. The join is an equijoin on the shared ID column, with the translation attributes layered onto each invoice header row. Because the metadata lists the underlying objects as synonyms, direct reads should be performed through the APPS view rather than by referencing the base tables individually, particularly in a multi-org context.

Key Columns

The view exposes a broad set of invoice header attributes. Principal columns include:

• INVOICE_ID / PAYABLES_INVOICE_ID — the internal identifier and the corresponding Payables invoice identifier once the record has been interfaced.
• INVOICE_NUM, INVOICE_TYPE, INVOICE_DATE — invoice identification and dating attributes.
• VENDOR_ID, VENDOR_SITE_ID, VENDOR_INVOICE_NUMBER — supplier and supplier site references, together with the vendor's own invoice reference.
• INVOICE_AMOUNT, INVOICE_CURRENCY_CODE — monetary value and transactional currency.
• CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_DATE — conversion information applied when the invoice currency differs from the ledger currency.
• DOC_CATEGORY_CODE — the document category that classifies the invoice; this is the column most often sought when reconciling the view against Payables invoice categories.
• TRX_STATUS_CODE, WORKFLOW_FLAG, SFWT_FLAG — status and workflow indicators describing the position of the record in the export lifecycle.
• TERMS_ID, PAY_GROUP_LOOKUP_CODE, PAYMENT_METHOD, PAY_ALONE_FLAG, NETTABLE_YN — payment and terms attributes carried into Payables.
• GL_DATE, ACCTS_PAY_CC_ID — accounting date and the accounts payable code combination.
• ORG_ID — the operating unit identifier, essential for multi-org filtered queries.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard descriptive flexfield columns available for client-specific extensions.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns identifying the process that created or last updated the row.
• CREATED_BY, OBJECT_VERSION_NUMBER, ROW_ID — standard WHO column, optimistic locking value, and row identifier.

Common Use Cases and Queries

The view supports a range of reconciliation and monitoring scenarios. A frequent requirement is to confirm which invoices have already reached Payables by checking for a populated PAYABLES_INVOICE_ID, or to verify that the DOC_CATEGORY_CODE assigned to each exported invoice matches the intended Payables document category.

The following query lists exported leasing invoices for a given operating unit, ordered by invoice date, and is typical of reconciliation extracts:

• SELECT invoice_num, invoice_type, invoice_date, vendor_id, vendor_invoice_number, invoice_amount, invoice_currency_code, doc_category_code, trx_status_code, payables_invoice_id FROM okl_ext_pay_invs_v WHERE org_id = :p_org_id AND invoice_date BETWEEN :p_start_date AND :p_end_date ORDER BY invoice_date;

To identify invoices still awaiting transfer to Payables, the view can be filtered where PAYABLES_INVOICE_ID is null. To audit the concurrent process that populated the rows, REQUEST_ID and PROGRAM_ID can be joined to the standard concurrent request tables. Because the view is a join over a base table and a translation table, all queries should be executed against the APPS synonym and scoped by ORG_ID to respect operating unit security in a multi-org environment.