Results for “pa_fp_of_webadi_xface”

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

Overview

PA_FP_OF_WEBADI_XFACE is a staging and interface table in the Oracle E-Business Suite Projects (PA) module, owned by the PA schema. Its name reflects its purpose: it supports the WebADI (Web Application Desktop Integrator) interface for the Forecast and Planning (FP) functionality within Oracle Projects. WebADI allows users to download data into a Microsoft Excel spreadsheet, edit it, and upload it back into Oracle EBS; PA_FP_OF_WEBADI_XFACE serves as the transient holding area for that uploaded forecast and planning data before it is validated and posted to the permanent budgeting and forecasting tables.

The table is documented as VALID and carries 61 physical columns in ETRM 12.2.2. Its structure — a session key, budget version and category references, an organization reference, and a wide block of period columns (PRD1 through PRD52) — indicates that it stores row-per-planning-line forecast amounts spread across weekly or periodic buckets. Because WebADI uploads are inherently transaction-oriented and reference multiple existing entities, the metadata's heuristic Data Vault classification of this table as a link is consistent with a modeling suggestion: it captures associations between sessions, budget versions, categories, and organizations rather than serving as a standalone hub or satellite.

Key Information Stored

The columns are organized into three logical groups:

• SESSION_ID — Identifies the WebADI upload session. This is the primary correlation key for a batch of rows loaded in a single spreadsheet submission, and it functions as the strongest business-key candidate for retrieval and cleanup operations.
• BUDGET_VERSION_ID — Foreign key to PA_BUDGET_VERSIONS, indicating the budget or forecast version into which the interface rows will be posted.
• CATEGORY_ID and CATEGORY — The resource category identifier and its descriptive label. CATEGORY_ID has a documented foreign key to PA_AMOUNT_TYPES_B.
• AMOUNT_TYPE_CODE — The amount type (for example, cost or revenue) that qualifies the forecast quantities.
• ORG_ID — Organization identifier, referencing PA_IMPLEMENTATIONS_ALL, used for multi-org security and partitioning.
• PROJECT_NAME and OTHER_ORGANIZATION_NAME — Descriptive fields captured from the WebADI template.
• RESOURCE_NAME — Identifies the resource or person associated with the forecast line.
• PRD1 through PRD52 — The period amount columns. WEBADI spreads the user-entered forecast across up to 52 periods, one amount per PRD column, which corresponds to the planning calendar buckets for the selected budget version.

No surrogate single-column primary key is documented; the effective unique identity is a composite of the session, budget version, category, and organization plus the resource or project context. The three FK relationships (BUDGET_VERSION_ID, CATEGORY_ID, ORG_ID) are the documented business-key anchors.

Common Use Cases and Queries

The table is primarily used for diagnostics and validation of WebADI forecast uploads. Typical scenarios include auditing a failed upload, purging orphaned session rows, or reconciling uploaded amounts against posted budget lines.

• Review a session's data before posting:
  SELECT session_id, project_name, category, resource_name, prd1, prd2, prd3 FROM pa.pa_fp_of_webadi_xface WHERE session_id = :p_session_id;
• Total forecast by category for a budget version:
  SELECT category_id, SUM(prd1 + prd2 + prd3) FROM pa.pa_fp_of_webadi_xface WHERE budget_version_id = :p_version GROUP BY category_id;
• Cleanup of stale interface rows by session:
  DELETE FROM pa.pa_fp_of_webadi_xface WHERE session_id = :p_session_id;
• Multi-org validation before posting:
  SELECT COUNT(*) FROM pa.pa_fp_of_webadi_xface x WHERE NOT EXISTS (SELECT 1 FROM pa.pa_implementations_all i WHERE i.org_id = x.org_id);

Reporting queries should never treat this table as a system of record; it should be treated as transient staging. Persistent forecast values reside in the PA budget and forecast tables after the upload process completes.

Related Objects

• PA_BUDGET_VERSIONS — Referenced via PA_FP_OF_WEBADI_XFACE.BUDGET_VERSION_ID; defines the target budget or forecast version.
• PA_AMOUNT_TYPES_B — Referenced via PA_FP_OF_WEBADI_XFACE.CATEGORY_ID; supplies category and amount type semantics.
• PA_IMPLEMENTATIONS_ALL — Referenced via PA_FP_OF_WEBADI_XFACE.ORG_ID; enforces organization and operating unit context.
• PA_BUDGET_LINES / PA_BUDGET_ASSIGNMENTS — The persistent destination tables ultimately populated from the interface rows during the posting process.
• PA_PROJECTS_ALL — Source of project validation when PROJECT_NAME is resolved during upload.
• WebADI integrator and PA forecast planning concurrent programs — The upload and validation logic that reads PA_FP_OF_WEBADI_XFACE, performs WebADI integration validation, and transfers validated rows into the permanent planning structures.

These relationships confirm the table's role as a link across sessions, budget versions, categories, and organizations within the Oracle Projects forecasting workflow.