Results for “distribution_rule”

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

Overview

PA_PROJ_TYPE_DISTRIBUTIONS_ALL is an Oracle Projects (PA) implementation table that stores the set of distribution rules available to each project type. A distribution rule determines how project expenditure, revenue, or burden amounts are distributed across general ledger accounts — for example, which account segments receive costs, how they are split, and whether a rule is applied by default. Because distribution behavior is frequently tied to the nature of a project, Oracle Projects allows administrators to constrain which rules may be selected for a given project type. This table stores those implementation-defined associations.

The table resides in the PA schema and is listed as VALID in the ETRM 12.1.1 / 12.2.2 file. Its documented physical schema contains nine columns. The primary key is PA_PROJECT_TYPE_DISTRIBUTIO_PK (note the truncated constraint name), defined over PROJECT_TYPE, DISTRIBUTION_RULE, and ORG_ID. A supporting unique index, PA_PROJECT_TYPE_DISTS_U1, enforces the same three-column business key. Based on the foreign-key structure, this object is best described as a link table in Data Vault terms: it resolves a many-to-many relationship between project types and distribution rules within an operating unit, rather than holding descriptive attributes about either entity.

Key Information Stored

The most significant columns are the composite business key and the default indicator:

• PROJECT_TYPE — Foreign key to PA_PROJECT_TYPES_ALL. Identifies the project type (for example, a capitalized or burdened project type) to which the rule is made available.
• DISTRIBUTION_RULE — Foreign key to PA_DISTRIBUTION_RULES. Identifies the distribution rule itself.
• ORG_ID — The operating unit (multi-org) identifier, ensuring rule availability is scoped to the correct organization.
• DEFAULT_FLAG — Indicates whether this rule is the default distribution rule for the project type. This is the principal non-key attribute of business interest.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle Applications WHO columns providing audit trail information.

The unique index PA_PROJECT_TYPE_DISTS_U1 (PROJECT_TYPE, DISTRIBUTION_RULE, ORG_ID) confirms that a given rule may be associated with a project type only once per operating unit.

Common Use Cases and Queries

Typical reporting and validation scenarios involve confirming which rules are available for a project type, identifying defaults, and reconciling implementation setup across operating units.

• Listing all rules for a project type:

  SELECT distribution_rule, default_flag FROM pa_proj_type_distributions_all WHERE project_type = :p_type AND org_id = :p_org;

• Locating the default rule for a project type:

  SELECT distribution_rule FROM pa_proj_type_distributions_all WHERE project_type = :p_type AND org_id = :p_org AND default_flag = 'Y';

• Joining to rule definitions to retrieve descriptive detail:

  SELECT ptd.project_type, dr.distribution_rule_name FROM pa_proj_type_distributions_all ptd, pa_distribution_rules dr WHERE ptd.distribution_rule = dr.distribution_rule AND ptd.org_id = :p_org;

These queries support setup audits after a clone or implementation, and are useful when troubleshooting why a particular distribution rule is not selectable for a project.

Related Objects

The following objects are most significant in relation to this table:

• PA_PROJECT_TYPES_ALL — Referenced via PROJECT_TYPE (and ORG_ID); the parent project type definition.
• PA_DISTRIBUTION_RULES — Referenced via DISTRIBUTION_RULE; holds the rule header definition.
• PA_DISTRIBUTION_RULE_DETAILS — Child of the rule header, defining account derivation logic used when the rule is applied.
• PA_PROJECTS_ALL — Projects carry a project type, so availability here indirectly governs which rules a project may use.
• PA_EXPENDITURE_ITEMS_ALL and PA_COST_DISTRIBUTION_LINES_ALL — Consume distribution rules during cost processing, linking this setup to actual distributed amounts.

Because the table is a setup/link object, it is generally maintained through the Projects setup UI rather than direct DML, and any direct changes should be accompanied by concurrent program or cache refreshes where applicable.