Search Results provider_organization

Overview

APPS.PA_XLA_CROSSCHARGE_V is an Oracle E-Business Suite view that consolidates cross-charge expenditure information for Projects reporting and integration. Cross-charging enables costs incurred by one organization to be transferred and billed to another organization, and this view presents the descriptive attributes that surround each cross-charged expenditure item. Rather than returning raw identifiers alone, the view resolves the project, task, expenditure type, system linkage, organization, and lookup meanings into human-readable values, making it suitable for operational reporting, reconciliation of inter-organization transfers, and downstream feeds into Subledger Accounting (XLA) and General Ledger analysis.

The name embeds "XLA," indicating the view is commonly consumed alongside the Projects subledger accounting and cross-charge processing flows, particularly when the cross-charge code stored on the expenditure item must be translated into its descriptive meaning. The user search term cc_cross_charge_code corresponds directly to the join predicate exp.cc_cross_charge_code = pl.lookup_code in the view definition, where pl.lookup_type = 'CC_CROSS_CHARGE_CODE'.

Underlying Base Objects

The view is defined over the following documented base objects, all accessed through APPS synonyms and one view:

• PA_EXPENDITURE_ITEMS_ALL (SYNONYM) — the fact table holding individual expenditure items, including the cross-charge code and organization references.
• PA_EXPENDITURES_ALL (SYNONYM) — the parent expenditure header, joined on expenditure_id.
• PA_PROJECTS_ALL (SYNONYM) — project name and segment1 (project number).
• PA_TASKS (SYNONYM) — task name and task number.
• PA_EXPENDITURE_TYPES (SYNONYM) — expenditure type and expenditure category.
• PA_SYSTEM_LINKAGES (SYNONYM) — descriptive meaning of the system linkage function.
• PA_LOOKUPS (VIEW) — lookup meanings, filtered to lookup_type 'CC_CROSS_CHARGE_CODE'.
• HR_ALL_ORGANIZATION_UNITS (SYNONYM) — referenced three times to resolve the expenditure, provider, and receiver organizations.

The joins align each expenditure item with its project and task, its expenditure header, the incurring organization (using NVL between override and incurred-by organization), the expenditure type and system linkage, and the provider and receiver organizations via CC_PRVDR_ORGANIZATION_ID and CC_RECVR_ORGANIZATION_ID.

Key Columns

• EXPENDITURE_ITEM_ID — unique identifier of the expenditure item.
• Project descriptor — pp.name || ' (' || pp.segment1 || ')', combining project name and number.
• Task descriptor — pt.task_name || ' (' || pt.task_number || ')'.
• EXPENDITURE_TYPE and EXPENDITURE_CATEGORY — classification of the cost.
• System linkage meaning (SYS.MEANING) — the descriptive function driving the expenditure.
• EXPENDITURE_ITEM_DATE — the accounting-relevant date of the item.
• Expenditure organization name — the incurring organization.
• Provider and receiver organization names — the source and destination of the cross-charge.
• PL.MEANING — the descriptive meaning of the cross-charge code resolved from PA_LOOKUPS.

Common Use Cases and Queries

Typical reporting needs include listing all cross-charged items with provider and receiver organizations, filtering by project or task, or validating that cross-charge codes resolve against valid lookup values.

SELECT expenditure_item_id,
       expenditure_item_date,
       expenditure_category,
       pl_meaning
FROM   apps.pa_xla_crosscharge_v
WHERE  pl_meaning IS NOT NULL
ORDER BY expenditure_item_date DESC;

To reconcile transfers between specific organizations:

SELECT v.expenditure_item_id, v.expenditure_type, v.expenditure_category
FROM   apps.pa_xla_crosscharge_v v
WHERE  v.pl_meaning = :cross_charge_code;

Because the view hard-codes the lookup join, records whose cross-charge code does not match a valid 'CC_CROSS_CHARGE_CODE' lookup are excluded, so an INNER-JOIN-to-lookup validation query should be paired with a count of expenditure items lacking a matching lookup entry.