Results for “burden_cost_flag”

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

Overview

PA_PROJECT_TYPES_ALL is the implementation-defined classification master in the Oracle Projects (PA) module, residing in the PA schema. Each row represents a project type that supplies default information and drives downstream project processing, including billing, budgeting, costing, capital asset interfacing, and workflow enablement. Because it holds the authoritative descriptive context for a project classification and is referenced by many transactional and configuration tables, the heuristic Data Vault classification for this object is a hub — a modeling suggestion that positions PROJECT_TYPE_ID (or the composite PROJECT_TYPE/ORG_ID) as a durable business key around which satellites of descriptive attributes and links to related configuration tables would be built.

The table is multi-org enabled through ORG_ID and includes the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN). In the documented 12.2.2 physical schema it contains 90 columns.

Key Information Stored

The surrogate primary key is defined by PA_PROJECT_TYPES_PK, composed of PROJECT_TYPE and ORG_ID. Two unique indexes act as business-key candidates: PA_PROJECT_TYPES_U1 on (PROJECT_TYPE, ORG_ID) and PA_PROJECT_TYPES_U2 on PROJECT_TYPE_ID, indicating PROJECT_TYPE_ID functions as a system-generated identifier used by the many referencing tables. The most significant descriptive and control columns include:

• PROJECT_TYPE and DESCRIPTION — the user-facing classification name and its narrative.
• PROJECT_TYPE_CLASS_CODE and SERVICE_TYPE_CODE — categorize the type (for example, capital versus contract) and its service nature.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating for the type.
• DIRECT_FLAG, BURDEN_COST_FLAG, ADMINISTRATIVE_FLAG, SPONSORED_FLAG — processing indicators controlling cost treatment and project behavior.
• LABOR_INVOICE_FORMAT_ID / NON_LABOR_INVOICE_FORMAT_ID and LABOR_BILL_RATE_ORG_ID, LABOR_STD_BILL_RATE_SCHDL, NON_LABOR_STD_BILL_RATE_SCHDL — default billing and rate schedule references.
• COST_IND_RATE_SCH_ID, REV_IND_RATE_SCH_ID, INV_IND_RATE_SCH_ID, CINT_RATE_SCH_ID — default indirect rate schedules per cost, revenue, invoice, and burdened cost.
• COST_BUDGET_ENTRY_METHOD_CODE / REV_BUDGET_ENTRY_METHOD_CODE and their resource list IDs — budget entry rules.
• DEFAULT_RESOURCE_LIST_ID — the resource list applied when a project is created.
• ALLOWABLE_FUNDING_LEVEL_CODE, BASELINE_FUNDING_FLAG, BUDGETARY_OVERRIDE_FLAG — funding control attributes.
• CAPITAL_COST_TYPE_CODE, ASSET_ALLOCATION_METHOD, INTERFACE_ASSET_COST_CODE, CIP_GROUPING_METHOD_CODE — capital and asset interface behavior.
• ENABLE_BUDGET_WF_FLAG and ENABLE_PROJECT_WF_FLAG — workflow enablement toggles.

Common Use Cases and Queries

Typical usage includes reporting on active project types for a given operating unit, retrieving default billing or rate schedules at project creation, and validating that a type is currently in its effective range. A representative query:

• SELECT project_type, description, project_type_class_code FROM pa_project_types_all WHERE org_id = :org AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);
• Join to PA_PROJECTS_ALL on PROJECT_TYPE to obtain the type description for a project listing.
• Join to PA_BILLING_ASSIGNMENTS_ALL or PA_EMPLOYEE_ACCUM_ALL on PROJECT_TYPE for billing and labor accumulation reporting.

Because the table is small and configuration-oriented, it is frequently used as a lookup hub in custom reports and in integration extracts that must resolve a project's classification.

Related Objects

The following depend on or are referenced by PA_PROJECT_TYPES_ALL through documented foreign keys:

• PA_PROJECTS_ALL — references PROJECT_TYPE; the primary consumer of the classification.
• PA_BILLING_ASSIGNMENTS_ALL — references PROJECT_TYPE for billing assignment definitions.
• PA_ALLOC_RUNS_ALL — references PPL_PROJECT_TYPE for allocation processing.
• PA_PROJ_TYPE_DISTRIBUTIONS_ALL — references PROJECT_TYPE for distribution rules.
• PA_EMPLOYEE_ACCUM_ALL and PA_EMPLOYEE_ORG_ACCUM_ALL — reference PROJECT_TYPE for labor accumulation.
• PER_JOB_GROUPS — referenced via BILL_JOB_GROUP_ID and COST_JOB_GROUP_ID.
• PA_INVOICE_FORMATS — referenced via LABOR_INVOICE_FORMAT_ID and NON_LABOR_INVOICE_FORMAT_ID.
• PA_RESOURCE_LISTS_ALL_BG — referenced via DEFAULT, COST_BUDGET, and REV_BUDGET resource list IDs.
• PA_IND_RATE_SCHEDULES_ALL_BG and PA_STD_BILL_RATE_SCHEDULES_ALL — referenced for indirect and standard billing rate schedules.
• PA_BILLING_CYCLES, PA_BUDGET_ENTRY_METHODS, and PA_ROLE_LISTS — referenced for billing cycle, budget entry method, and role list defaults.