Results for “program_id”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
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:
- REQUEST_ID — Oracle Concurrent Manager request identifier of the spawned program; part of the composite primary key and business key.
- PROGRAM_ID — Concurrent program definition identifier for the spawned program; the second component of the composite primary key.
- PROGRAM_APPLICATION_ID — the application owning the concurrent program.
- PROGRAM_UPDATE_DATE — the date/time the spawned program's status was last updated, used to track progression.
- REQUEST_ID + PROGRAM_ID — together form the composite primary key PA_SPAWNED_PROGRAM_STATUSES_PK and the unique business-key index PA_SPAWNED_PROGRAM_STATUSES_U1.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS WHO columns providing audit lineage.
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:
- FND_CONCURRENT_REQUESTS — joins on REQUEST_ID to retrieve phase and status codes.
- FND_CONCURRENT_PROGRAMS — joins on PROGRAM_ID / PROGRAM_APPLICATION_ID for program definitions.
- FND_CONCURRENT_PROGRAMS_TL — provides translated program names.
- FND_CONCURRENT_PROCESSES — relates running processes to requests.
- PA_PROCESSES / PA_INTERFACE controls — PA processes that spawn child requests.
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.
-
Statuses of spawned programs
-
Statuses of spawned programs
-
View: PA_ADW_CURRENT_TASKS 12.1.1
APPS.PA_ADW_CURRENT_TASKS·↳ PA_TASK_HISTORY·Explore PA module →
-
View: PA_ADW_CURRENT_TASKS 12.2.2
APPS.PA_ADW_CURRENT_TASKS·↳ PA_TASK_HISTORY·Explore PA module →
-
View: PA_RES_LISTS_IT 12.1.1
View of resource lists for the business group in implementation options for Oracle Project Analysis Collection Pack
APPS.PA_RES_LISTS_IT·↳ PA_RES_LISTS_IT_ALL_BG·↳ PA_UTILS·Explore PA module →
-
View: PA_RES_LISTS_IT 12.2.2
View of resource lists for the business group in implementation options for Oracle Project Analysis Collection Pack
APPS.PA_RES_LISTS_IT·↳ PA_RES_LISTS_IT_ALL_BG·↳ PA_UTILS·Explore PA module →
-
APPS.PA_ADW_INTERFACED_TASKS·↳ PA_TASK_HISTORY·Explore PA module →
-
APPS.PA_ADW_INTERFACED_TASKS·↳ PA_TASK_HISTORY·Explore PA module →
-
PA_AUD_COST_DIST_LINES stores audit information for summarized burden expenditure items.
-
Information about the top level of the standard hierarchy on the service type dimension
-
Information about the top level of the standard hierarchy on the expenditure type dimension
-
Business groups for expenditure organizations for Oracle Project Analysis Collection Pack
-
Information about the top level of the standard hierarchy on the time dimension
-
Information about submitted streamline process requests
-
Information about business groups for project/task organizations for Oracle Project Analysis Collection Pack
-
Single-Org
APPS.PA_CUST_EVENT_REV_DIST_LINES_V·↳ PA_CUST_EVENT_REV_DIST_LINES·↳ PA_MULTI_CURRENCY·Explore PA module →
-
Information about legal entities for Oracle Project Analysis Collection Pack
-
Single-Org
APPS.PA_CUST_EVENT_REV_DIST_LINES_V·↳ PA_CUST_EVENT_REV_DIST_LINES·↳ PA_MULTI_CURRENCY·Explore PA module →
-
Business groups for expenditure organizations for Oracle Project Analysis Collection Pack
-
PA_PROJECT_CTX_SEARCH stores the concatenated attributes for the columns of PA_PROJECTS_ALL that we perform keyword search on, including Name, Long Name, Segment1 and Description
-
Information about sets of books for Oracle Project Analysis Collection Pack
-
Information about the top level of the standard hierarchy on the project dimension
-
PA_PROJECT_CTX_SEARCH stores the concatenated attributes for the columns of PA_PROJECTS_ALL that we perform keyword search on, including Name, Long Name, Segment1 and Description
-
Stores complied capitalized interest schedule revisions, denormalized by revision, organization and rate name. The multipliers in this table are used during the calculation and generation of Capitalized Interest transactions.
-
Single-Org
APPS.PA_PROJECT_ASSETS_AMG_V·↳ PA_PROJECT_ASSETS·Explore PA module →
-
Single-Org
APPS.PA_PROJECT_ASSETS_AMG_V·↳ PA_PROJECT_ASSETS·Explore PA module →
-
Purged details for projects in a purge batch
-
Groups of compiled multipliers
-
Stores complied capitalized interest schedule revisions, denormalized by revision, organization and rate name. The multipliers in this table are used during the calculation and generation of Capitalized Interest transactions.
-
Groups of compiled multipliers
-
Information about GL periods for Oracle Project Analysis Collection Pack
-
Pa_Expenditure_Comments_ar is a table for Archive/Purge. Refer to comments on the columns in the main table
-
Information about financial years for Oracle Project Analysis Collection Pack
-
Information about invoice details for cross charged transactions in each reporting set of books
-
Information about the top level of the standard hierarchy on the project dimension
-
Information about business groups for project/task organizations for Oracle Project Analysis Collection Pack
-
Information about the top level of the standard hierarchy on the time dimension
-
Information about the top level of the standard hierarchy on the expenditure type dimension
-
Pa_Expenditure_Comments_ar is a table for Archive/Purge. Refer to comments on the columns in the main table
-
Information necessary to drill down from an asset line to the cost distribution line
-
Information about financial quarters for Oracle Project Analysis Collection Pack
-
Information about cost and/or revenue adjustments made to expenditure items through the Oracle Projects forms
-
Stores information about events used to group costs and assets for capitalization and events used to generate retirement cost adjustments. Based on the Event Processing Method defined at the project level, capital events are system generat
-
Stores information about events used to group costs and assets for capitalization and events used to generate retirement cost adjustments. Based on the Event Processing Method defined at the project level, capital events are system generat
-
Free text entered for expenditure items to explain or further describe work performed
-
Archive/Purge Draft Invoice Detail
-
The PA_RESOURCE_ACCUM_DETAILS table records that are deleted when accumulation is refreshed
-
Drilldown information from PA_TXN_ACCUM to cost, revenue, and event revenue distribution lines, and to commitments
-
This view based on pa_project_fundings table, stores incremental allocations of agreement funds to projects or top tasks. Funding is required for a contract project before that project can accrue revenue and generate invoices. Indirect or
APPS.PA_PROJECT_FUNDINGS_AMG_V·↳ PA_PROJECT_FUNDINGS·Explore PA module →