Search Results pa_spawned_program_statuses




Overview
Explore in AI Chat

Overview

PA_SPAWNED_PROGRAM_STATUSES is a table owned by the PA (Projects) schema in Oracle E-Business Suite. As its description states, it stores statuses of spawned programs, meaning it tracks the execution state of concurrent programs that have been launched programmatically — or "spawned" — by Project Accounting processes rather than submitted directly by a user. Spawned programs are common in Oracle Projects, where a parent process such as cost distribution, interface importing, or revenue generation must initiate one or more child concurrent requests and then monitor their completion.

The table exists in both EBS 12.1.1 and 12.2.2 (12.2.2 documented with nine columns). The heuristic Data Vault classification mined from the foreign-key structure is standalone, which — as a modeling suggestion — indicates the table is not dependent on a parent-child hierarchy within the Data Vault sense and could be modeled as a link or satellite keyed by its composite identifier without requiring a hub join.

Key Information Stored

The most significant columns are:

Note that there is no separate surrogate numeric key; the business key (REQUEST_ID, PROGRAM_ID) is also the primary key.

Common Use Cases and Queries

Developers and DBAs query this table to determine whether a Project Accounting process has successfully launched and completed its dependent concurrent requests. Typical scenarios include troubleshooting stalled cost interfaces, diagnosing incomplete revenue distribution runs, and monitoring program chains in production.

A basic query joins spawned statuses to the Concurrent Manager request table:

  • SELECT s.request_id, s.program_id, s.program_application_id, s.program_update_date FROM pa.pa_spawned_program_statuses s WHERE s.request_id = :request_id;
  • SELECT s.request_id, s.program_id, s.program_update_date, r.phase_code, r.status_code FROM pa.pa_spawned_program_statuses s, fnd_concurrent_requests r WHERE s.request_id = r.request_id;

Reporting use cases include listing all spawned programs for a given parent request, identifying requests that never updated (indicating a hang), and auditing which concurrent programs are commonly spawned by a given PA process.

Related Objects

The following objects are most significant for joins and dependencies:

Because the table is classified standalone, no direct FK constraints tie it elsewhere; joins to FND Concurrent Manager tables are made by convention on the composite key columns.