Search Results pa_project_types_all

Overview

The PA_PROJECT_TYPES_ALL table is a fundamental setup and control table within the Oracle E-Business Suite Projects module (PA). It stores implementation-defined classifications for projects, serving as a critical template mechanism. When a new project is created and assigned a project type, the system automatically populates it with a comprehensive set of default attributes and processing rules defined in this table. This drives core project functionality, including budgeting, billing, costing, and resource management, ensuring consistency and efficiency across projects of the same classification. As an "_ALL" table, it is multi-organization enabled (Multi-Org), meaning it contains an ORG_ID column to segregate data by operating unit, supporting deployments with multiple legal entities or business units.

Key Information Stored

The table's primary key is a composite of PROJECT_TYPE and ORG_ID, enforcing uniqueness of type definitions within each operating unit. Key columns store codes and identifiers that link to other setup entities, effectively configuring the project type's behavior. These include BILLING_CYCLE_ID for invoicing frequency, various *_RESOURCE_LIST_ID columns for default planning resources, and *_IND_RATE_SCH_ID columns for indirect cost calculation. Crucially, it holds foreign keys to budget entry methods (COST_BUDGET_ENTRY_METHOD_CODE, REV_BUDGET_ENTRY_METHOD_CODE), standard bill rate schedules for labor and non-labor, and invoice formats. Columns like BILL_JOB_GROUP_ID and COST_JOB_GROUP_ID link to job groupings for billing and costing purposes.

Common Use Cases and Queries

The primary use case is during project creation and defaulting, where the project type's attributes are copied to the project definition. It is also central for reporting and auditing setup configurations. Administrators frequently query this table to validate or document the setup. A common SQL pattern retrieves all project types with their key defaults for a specific operating unit:

• SELECT project_type, description, billing_cycle_id, default_resource_list_id FROM pa_project_types_all WHERE org_id = :p_org_id ORDER BY project_type;

Another critical query involves joining to referenced tables to produce a comprehensive setup report, such as listing project types alongside their assigned budget entry methods and resource lists for troubleshooting configuration issues.

Related Objects

PA_PROJECT_TYPES_ALL has extensive relationships with other PA setup tables, as documented by its foreign keys. Key related objects include:

• PA_INVOICE_FORMATS: Linked via LABOR_INVOICE_FORMAT_ID and NON_LABOR_INVOICE_FORMAT_ID for formatting project invoices.
• PA_RESOURCE_LISTS_ALL_BG: Linked via DEFAULT_RESOURCE_LIST_ID, COST_BUDGET_RESOURCE_LIST_ID, and REV_BUDGET_RESOURCE_LIST_ID for resource planning and budgeting.
• PA_BILLING_CYCLES: Linked via BILLING_CYCLE_ID to define invoicing schedules.
• PER_JOB_GROUPS: Linked via BILL_JOB_GROUP_ID and COST_JOB_GROUP_ID for grouping jobs.
• PA_IND_RATE_SCHEDULES_ALL_BG: Linked via COST_IND_RATE_SCH_ID, REV_IND_RATE_SCH_ID, INV_IND_RATE_SCH_ID, and CINT_RATE_SCH_ID for various indirect rate applications.
• PA_STD_BILL_RATE_SCHEDULES_ALL: Linked via columns for LABOR_STD_BILL_RATE_SCHDL and NON_LABOR_STD_BILL_RATE_SCHDL (with their respective ORG_IDs) for standard billing rates.
• PA_BUDGET_ENTRY_METHODS: Linked via REV_BUDGET_ENTRY_METHOD_CODE and COST_BUDGET_ENTRY_METHOD_CODE to define how budget amounts are entered.