Search Results pa_integration_settings

Overview

PA_INTEGRATION_SETTINGS is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the integration configuration parameters used when a project or project template is synchronized with an external planning or budgeting application. Each row represents the integration settings for a single project or template, controlling whether integration is enabled, which structures are exchanged, and how budgeting, forecasting, and task information flows between Oracle Projects and the connected system. The table is part of the standard PA schema and is owned by the PA account.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is standalone. This suggests that PA_INTEGRATION_SETTINGS is best modeled as a standalone satellite-like entity keyed on a single business object (the project), rather than as a hub with extensive link relationships, because the FK topology shows only one referenced parent table and no dependent child tables. It is, however, functionally a configuration child of the project itself.

Key Information Stored

The surrogate primary key is the constraint SYS_C00741180, defined on PROJECT_ID, which is a foreign key to the project master. PROJECT_ID is therefore both the physical PK and the primary business-key candidate for joining to project entities. All documented columns number 22; the following are the most significant for configuration and reporting purposes.

• PROJECT_ID — primary key; identifies the project or template whose integration settings are stored.
• ENABLE_INTEGRATION — flag indicating whether integration is active for the project.
• STRUCTURE_TYPE — the work breakdown / financial structure type used during the integration exchange.
• SEND_ACTUAL_COST_TYPE — controls how actual costs are transmitted to the external system.
• SEND_TASK, SEND_TASK_REF, RECEIVE_TASK — govern outbound and inbound task-level data flow and task reference behavior.
• SEND_BUDGET, SEND_BUDGET_REF, RECEIVE_BUDGET — govern outbound and inbound budget data, including budget reference handling.
• FIN_PLAN_TYPE_ID — foreign key to PA_FIN_PLAN_TYPES_B, defining the financial plan type applied to the integration.
• FIN_STRUCT_MAX_LEVEL — maximum level of the financial structure included in synchronization.
• BUDGET_TYPE — the budget type associated with the project integration.
• SYNCHRONIZE_MARK, LAST_SYNCHRONIZATION_DATE, SYNCHRONIZATION_STAGE — track and drive the synchronization lifecycle, including the stage of the current run.
• CREATE_PLANNING_RESOURCE — determines whether a planning resource is created during integration.
• Standard audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) record who created and last modified each settings row.

Common Use Cases and Queries

Typical uses include identifying projects with integration enabled, troubleshooting failed synchronizations by inspecting SYNCHRONIZATION_STAGE and LAST_SYNCHRONIZATION_DATE, and reporting on which financial plan types and budget types each project uses. A representative query joins the settings to the project master and financial plan types:

• SELECT p.project_id, p.name, i.enable_integration, i.fin_plan_type_id, i.budget_type, i.last_synchronization_date FROM pa_integration_settings i JOIN pa_projects_all p ON p.project_id = i.project_id;
• Reporting projects not yet synchronized: filter on SYNCHRONIZATION_STAGE or where LAST_SYNCHRONIZATION_DATE is null.
• Config audits for send/receive budget and task flags to confirm alignment with the external planning tool.

Related Objects

The FK relationship identifies the most significant referenced object, PA_FIN_PLAN_TYPES_B, joined on FIN_PLAN_TYPE_ID. The table also intersects with project and project-template master tables through PROJECT_ID, and its integration behavior is driven by standard Oracle Projects integration APIs and concurrent programs that update synchronization columns.

• PA_FIN_PLAN_TYPES_B — joined on FIN_PLAN_TYPE_ID; defines the financial plan type.
• PA_PROJECTS_ALL — joined on PROJECT_ID; project master.
• PA_PROJECTS — project detail entity.
• PA_PROJECT_TEMPLATES — templates whose integration settings are stored.
• PA_BUDGET_TYPES — budget type reference.
• Oracle Projects integration concurrent programs / APIs — consume these settings during synchronization.