Results for “pei_attribute3”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_XLA_EXP_HEADER_V is a Projects (PA) module reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a denormalized, accounting-ready projection of project expenditure transactions for use by the Subledger Accounting (SLA) engine and by downstream reporting and integration consumers. The view joins the XLA events interface table (XLA_EVENTS_GT) to the two core Projects expenditure entities to produce one row per expenditure item event, carrying both the event header context and the descriptive attributes needed to build accounting entries and reconciliation reports.

The view is restricted in its WHERE clause to XEV.APPLICATION_ID = 275, the application identifier for Oracle Projects, ensuring that only Projects-sourced SLA events are returned. Because XLA_EVENTS_GT is a global temporary table populated during the accounting event generation program, the view is transient by design: it exposes the current event set for the session or run in which accounting is being processed. This makes it a foundational object for SLA rule evaluation, journal line creation, and for diagnosing why a given expenditure item did or did not generate accounting.

Underlying Base Objects

The documented view metadata identifies three referenced base objects, all accessed through APPS synonyms:

• PA_EXPENDITURES_ALL (aliased E) — the expenditure header entity, supplying expenditure class code, person type, incurred-by person, and the ORIG_EXP_TXN_REFERENCE columns. It is joined to the item table on EXPENDITURE_ID.
• PA_EXPENDITURE_ITEMS_ALL (aliased EI) — the expenditure item (detail/distribution) entity, supplying project, task, expenditure type, dates, inventory and WIP references, cross-charge and transfer price attributes, and the ATTRIBUTE1–ATTRIBUTE10 descriptive flexfield columns.
• XLA_EVENTS_GT (aliased XEV) — the Subledger Accounting events global temporary table, supplying EVENT_ID, SOURCE_ID_INT_1, and EVENT_DATE. The join condition EI.EXPENDITURE_ITEM_ID = XEV.SOURCE_ID_INT_1 links each expenditure item to its accounting event.

All three objects are exposed to the APPS schema as synonyms, and the view therefore inherits standard EBS multi-org and security behavior through those base entities rather than enforcing its own.

Key Columns

• EVENT_ID / EXPENDITURE_ITEM_ID / EXPENDITURE_ID — the SLA event and the Projects transaction identifiers that anchor the row.
• PROJECT_ID, TASK_ID, EXPENDITURE_TYPE — the project cost collection context used for cost and revenue accounting.
• EXPENDITURE_ORGANIZATION_ID — defined as NVL(EI.OVERRIDE_TO_ORGANIZATION_ID, E.INCURRED_BY_ORGANIZATION_ID), resolving the effective expenditure organization.
• EXPENDITURE_CLASS_CODE — the class of the originating expenditure (for example labor, expense, or usage).
• PERSON_ID — the incurred-by person; PERSON_TYPE defaults to 'EMP' via NVL(E.PERSON_TYPE, 'EMP').
• ORIG_TRANSACTION_REFERENCE and ORIG_EXP_TXN_REFERENCE1–3 — transaction traceability references linking back to the source system document.
• INVENTORY_ITEM_ID, WIP_RESOURCE_ID, NON_LABOR_RESOURCE, SYSTEM_LINKAGE_FUNCTION — inventory and work-in-process linkage identifiers used when expenditure originates in Oracle Inventory or WIP.
• ATTRIBUTE1–ATTRIBUTE10 — descriptive flexfield attributes surfaced from both the item and the expenditure header, providing the user-defined context columns commonly referenced in accounting rules.

Common Use Cases and Queries

A frequent requirement is locating a transaction or accounting line by a descriptive flexfield value. The search term pei_attribute3 commonly corresponds to ATTRIBUTE3 on the expenditure item (PA_EXPENDITURE_ITEMS_ALL), which is surfaced in this view. Such a query is used to confirm which SLA event and accounting entries were produced for a specific expenditure item attribute value.

SELECT event_id, expenditure_item_id, project_id, task_id,
       expenditure_type, expenditure_class_code, attribute3
FROM   apps.pa_xla_exp_header_v
WHERE  attribute3 = :pei_attribute3;

Additional practical scenarios include reconciling event headers to journal lines, joining the view to XLA_AE_LINES by APPLICATION_ID and EVENT_ID, and validating that cross-charge or transfer price items are routed to the correct organization. Because the view depends on XLA_EVENTS_GT contents, queries executed outside the accounting event run context may return no rows, and the view should be used within the appropriate Subledger Accounting or Projects accounting process.