Search Results ai_invoice_currency_code

Overview

The view PA_XLA_BC_PKT_AP_DETAIL_V is an Oracle Projects (PA) subledger accounting extraction view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents Payables-sourced burden cost packet detail lines destined for the Subledger Accounting (XLA) accounting program. Its role is to flatten the burden packet structures held in PA_BC_PACKETS and join them to the originating Payables distribution lines so that the Create Accounting process can derive the correct entered and accounted amounts, distribution link types, and descriptive attributes.

The view resolves the classic burden cost extraction problem: burden distributions are stored in Projects tables, but their source amounts reside on Payables invoice distributions. By exposing the currency, ledger, event type, and category context for each packet row, the view supplies the columns the XLA event entity requires to build journal entries for burden costs applied against AP invoice distributions, including prepayment applications and prepayment application nonrecoverable tax lines.

Underlying Base Objects

The documented base objects underlying this view are:

• AP_INVOICE_DISTRIBUTIONS_ALL — source of the invoice distribution lines and the invoice currency.
• AP_PREPAY_APP_DISTS — identifies prepayment application distributions used to reverse the sign of the amount.
• GL_LEDGERS — provides currency and ledger context; supplies the column exposed as AI_INVOICE_CURRENCY_CODE (aliased GLL.CURRENCY_CODE).
• PA_BC_PACKETS — the burden cost packet header/detail driving the extraction (PBC alias).
• PA_RESOURCE_LIST_MEMBERS — supplies event type, expenditure category, revenue category, person, and job attributes.
• XLA_EVENTS_GT — the global temporary table used by the accounting program to correlate events.
• PA_FUNDS_CONTROL_UTILS — a package invoked inline via PA_FUNDS_CONTROL_UTILS.GET_SLA_NOTUPGRADED_FLAG to flag whether the SLA upgrade applies for AP or PO document types.

Key Columns

• BC_EVENT_ID / SOURCE_EVENT_ID — identifies the burden cost event and its originating XLA source event.
• DOCUMENT_DISTRIBUTION_ID — the AP invoice distribution identifier linking the packet line to Payables.
• AI_INVOICE_CURRENCY_CODE — the invoice currency code, sourced from GL_LEDGERS.CURRENCY_CODE; this is the column most commonly referenced in searches for SLA currency mapping.
• AID_AMOUNT — the entered amount, computed with a DECODE that reverses sign for prepayment application and prepayment application nonrecoverable tax distributions.
• AID_BASE_AMT_NO_ROUND — the accounted (base) amount, applying the same sign-reversal logic.
• DISTRIBUTION_LINK_TYPE — returns PA_PO_BURDEN for PO document types and PA_AP_BURDEN for AP.
• AID_PROJECT_ID, AID_TASK_ID, AID_EXPENDITURE_ORG_ID, AID_EXPENDITURE_ITEM_DATE — project, task, organization, and expenditure item date context.
• AI_INVOICE_ID — the AP invoice header identifier (PBC.DOCUMENT_HEADER_ID).
• EVENT_TYPE, EXPENDITURE_CATEGORY, REVENUE_CATEGORY, PERSON_ID, JOB_ID — resource list attributes from PA_RESOURCE_LIST_MEMBERS.
• SET_OF_BOOKS_ID, BURDEN_COST_FLAG, VENDOR_ID, BUDGET_CCID — ledger and packet control attributes.

Common Use Cases and Queries

The view is queried primarily during diagnosis of burden cost accounting, SLA event feeds, and currency discrepancies on AP-sourced burden lines. A typical diagnostic query retrieves invoice currency and amounts for a given burden packet:

• SELECT bc_event_id, source_event_id, document_distribution_id, ai_invoice_id, ai_invoice_currency_code, aid_amount, aid_base_amt_no_round FROM apps.pa_xla_bc_pkt_ap_detail_v WHERE bc_packet_id = :p_packet_id;
• Joining to PA_BC_PACKETS or PA_EXPENDITURE_ITEMS_ALL when reconciling burden costs to a project expenditure item.
• Filtering by distribution_link_type = 'PA_AP_BURDEN' to isolate AP burden lines from PO burden lines.
• Reviewing event_type and expenditure_category when validating SLA event classification.

Because the view references XLA_EVENTS_GT, queries executed inside the accounting program's session can see transient accounting events; ad hoc queries outside that session should be limited to the persisted packet and distribution columns.