Results for “invoice_eligible_flag”
16 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The view APPS.PA_CUST_REV_DIST_LINES_EI_V is a Projects (PA) module reporting and integration object that exposes customer revenue distribution lines together with their associated expenditure item context. Its name follows Oracle's ETRM naming conventions: the _EI_ segment indicates that the view joins revenue distribution line data to expenditure items, and the _V suffix confirms it is a view rather than a base table. The view is delivered by Oracle and held in the APPS schema in a VALID state in both Oracle EBS 12.1.1 and 12.2.2.
In substance, the view presents a single row per customer revenue distribution line, enriched with the primary key of the expenditure item it was generated from and with a broad set of currency and amount columns. Because revenue distribution lines naturally carry multiple simultaneous monetary representations (project, project functional, funding, revenue processing, invoice processing, and billing transaction currencies), this view is particularly useful for financial reporting, reconciliation, and outbound integration where a consolidated, denormalized read of revenue line data is required. Users searching on the term mrc_amount will generally be attempting to locate a Multiple Reporting Currency (MRC) amount column; the documented projection of this view does not expose a column literally named MRC_AMOUNT, but it does expose the analogous reporting amounts through the PROJCURR, PROJFUNC, and FUNDING currency families, which in an MRC environment serve the equivalent reporting-currency purpose.
Underlying Base Objects
The ETRM 12.2.2 metadata documents a single referenced base object for this view: the synonym PA_CUST_REV_DIST_LINES_ALL. The view text confirms this, selecting from an alias RDL that resolves to PA_CUST_REV_DIST_LINES_ALL, the multiorg base table that stores customer revenue distribution lines for a project.
Critically, the view also exposes RDL.EXPENDITURE_ITEM_ID and RDL.ORG_ID. The EXPENDITURE_ITEM_ID column functions as the correlating key to PA_EXPENDITURE_ITEMS_ALL, which is what justifies the _EI_ designation in the view name. This allows reporting to relate a revenue distribution line back to the originating expenditure item and its cost, quantity, and assignment context, while ORG_ID preserves the operating unit for multiorg security. Because the view is built directly on the _ALL table, row-level operating unit filtering is applied through Oracle's standard multiorg views rather than through a separate secure view layer.
Key Columns
The projection can be grouped into functional identifiers, status and control flags, cost basis, and currency/amount families.
- Identifiers and keys:
EXPENDITURE_ITEM_ID,LINE_NUM,PROJECT_ID,DRAFT_REVENUE_NUM,DRAFT_REVENUE_ITEM_LINE_NUM,DRAFT_INVOICE_NUM,DRAFT_INVOICE_ITEM_LINE_NUM,CODE_COMBINATION_ID, andORG_ID. - Amounts:
AMOUNT(the revenue distribution amount),BILL_AMOUNT, andRAW_COST(the underlying cost basis used for revenue generation). - Flags and status:
ADDITIONAL_REVENUE_FLAG,INVOICE_ELIGIBLE_FLAG,REVERSED_FLAG,PRC_GENERATED_FLAG, andLINE_NUM_REVERSED. - Currency families:
BILL_TRANS_*(billing transaction currency code, amount, bill amount, and rate),REVPROC_*(revenue processing currency, rate type, rate date, exchange rate),INVPROC_*(invoice processing currency and rate),PROJECT_CURRENCY_CODEwithPROJECT_REVENUE_AMOUNT,PROJECT_BILL_AMOUNTand their rate type/date/exchange rate,PROJFUNC_CURRENCY_CODEwithPROJFUNC_REVENUE_AMOUNTandPROJFUNC_BILL_AMOUNTplus rate details, andFUNDING_CURRENCY_CODEwithFUNDING_REVENUE_AMOUNT,FUNDING_BILL_AMOUNTand rate details. - Tax attributes:
OUTPUT_VAT_TAX_ID,OUTPUT_TAX_CLASSIFICATION_CODE,OUTPUT_TAX_EXEMPT_FLAG,OUTPUT_TAX_EXEMPT_REASON_CODE, andOUTPUT_TAX_EXEMPT_NUMBER. - Audit and processing context:
CREATION_DATE,CREATED_BY,REQUEST_ID,PROGRAM_APPLICATION_ID,PROGRAM_ID,PROGRAM_UPDATE_DATE,FUNCTION_CODE,FUNCTION_TRANSACTION_CODE, andBATCH_NAME.
The FUNDING_CURRENCY_CODE family and the PROJCURR/PROJFUNC families are the columns that reporting users typically substitute when the search term mrc_amount is used, since they represent amounts expressed in reporting and funding currencies rather than in the transaction currency.
Common Use Cases and Queries
The view is commonly used for revenue reconciliation, billing preparation audits, and extracts feeding downstream financial systems. A typical reconciliation query compares the distribution amount against bill amounts and the underlying expenditure item cost:
SELECT rdl.project_id,
rdl.expenditure_item_id,
rdl.draft_revenue_num,
rdl.line_num,
rdl.amount,
rdl.bill_amount,
rdl.raw_cost,
rdl.project_currency_code,
rdl.project_revenue_amount,
rdl.projfunc_currency_code,
rdl.projfunc_revenue_amount,
rdl.funding_currency_code,
rdl.funding_revenue_amount
FROM apps.pa_cust_rev_dist_lines_ei_v rdl
WHERE rdl.org_id = :p_org_id
AND rdl.project_id = :p_project_id
AND NVL(rdl.reversed_flag,'N') = 'N';
A second frequent pattern identifies revenue lines eligible for invoicing that also carry a positive bill amount:
SELECT rdl.project_id,
rdl.draft_invoice_num,
rdl.draft_invoice_item_line_num,
rdl.code_combination_id,
rdl.bill_trans_currency_code,
rdl.bill_trans_amount,
rdl.bill_trans_bill_amount
FROM apps.pa_cust_rev_dist_lines_ei_v rdl
WHERE rdl.invoice_eligible_flag = 'Y'
AND rdl.bill_amount > 0
AND rdl.org_id = :p_org_id
ORDER BY rdl.project_id, rdl.draft_invoice_num;
Because the view is functionally similar to an MRC-aware currency view, developers should also note that it is a reporting projection and not a substitute for the base table during DML operations; updates and inserts must target PA_CUST_REV_DIST_LINES_ALL. When a column named MRC_AMOUNT is required, it is normally obtained by joining this view to Multiple Reporting Currency views or by selecting the appropriate project, project functional, or funding currency amount column, which are the documented reporting-currency representations available here.
-
APPS.PA_CUST_REV_DIST_LINES_EI_V·↳ PA_CUST_REV_DIST_LINES_ALL·Explore PA module →
-
View: PA_CUST_RDL_ALL_MRC_V2 12.2.2
Multi-org, single currency view
APPS.PA_CUST_RDL_ALL_MRC_V2·↳ PA_CUST_REV_DIST_LINES_ALL·↳ PA_EXPENDITURE_ITEMS_ALL·↳ PA_IMPLEMENTATIONS_ALL·Explore PA module →
-
View: PA_CUST_RDL_ALL_MRC_V2 12.1.1
Multi-org, single currency view
APPS.PA_CUST_RDL_ALL_MRC_V2·↳ PA_CUST_REV_DIST_LINES_ALL·↳ PA_EXPENDITURE_ITEMS_ALL·↳ PA_IMPLEMENTATIONS_ALL·Explore PA module →
-
View: PA_CUST_RDL_ALL_MRC_V 12.1.1
Multi-org, single currency view
APPS.PA_CUST_RDL_ALL_MRC_V·↳ PA_CUST_REV_DIST_LINES·↳ PA_EXPENDITURE_ITEMS_ALL·↳ PA_IMPLEMENTATIONS_ALL·Explore PA module →
-
View: PA_CUST_RDL_ALL_MRC_V 12.2.2
Multi-org, single currency view
APPS.PA_CUST_RDL_ALL_MRC_V·↳ PA_CUST_REV_DIST_LINES·↳ PA_EXPENDITURE_ITEMS_ALL·↳ PA_IMPLEMENTATIONS_ALL·Explore PA module →
-
APPS.PA_CUST_REV_DIST_LINES_EI_V·↳ PA_CUST_REV_DIST_LINES_ALL·Explore PA module →
-
Pa_Cust_Rev_Dist_Lines_ar is a table for Archive/Purge. Refer to comments on the columns in the main table
-
Information about expenditure item revenue distribution
-
Pa_Cust_Rev_Dist_Lines_ar is a table for Archive/Purge. Refer to comments on the columns in the main table
-
Information about expenditure item revenue distribution
-
View: PA_CUST_REV_DIST_LINES 12.2.2
Single-Org
Not implemented in this database·Explore PA module →
-
View: PA_CUST_REV_DIST_LINES 12.1.1
Single-Org
Not implemented in this database·Explore PA module →
-
View: PA_CUST_RDL_MRC_V 12.1.1
Single-org, single currency MRC view
Not implemented in this database·Explore PA module →
-
Not implemented in this database·Explore PA module →
-
Not implemented in this database·Explore PA module →
-
View: PA_CUST_RDL_MRC_V 12.2.2
Single-org, single currency MRC view
Not implemented in this database·Explore PA module →