Search Results pa_distribution_rules_lov_v




Overview
Explore in AI Chat

Overview

PA_DISTRIBUTION_RULES_LOV_V is an APPS-owned database view in the Oracle E-Business Suite Project Accounting (PA) module, available under the same definition in releases 12.1.1 and 12.2.2. It is documented with a VALID status in the ETRM repository and is classed as a list-of-values (LOV) support object. Its stated purpose is to display all the relevant distribution rules available for a template. In practical terms, the view drives the distribution rule selection list presented to users when they attach a distribution rule to a project type template, and it supplies the same rule set to any concurrent program, form, or custom integration that needs to resolve a valid distribution rule for template-based project setup.

The view is date-sensitive because it filters distribution rules on their activation window, so a rule that is inactive on the current system date is suppressed. It is also template-sensitive, because the join to PA_PROJECTS restricts results to records flagged as templates.

Underlying Base Objects

The view is defined over three base objects, all referenced through APPS synonyms: PA_PROJECT_TYPE_DISTRIBUTIONS (aliased PTD), PA_DISTRIBUTION_RULES (aliased DR), and PA_PROJECTS (aliased PAP).

  • PA_PROJECT_TYPE_DISTRIBUTIONS is the driving table. It maps a distribution rule to a project type, so each row represents one valid rule-to-project-type association.
  • PA_DISTRIBUTION_RULES supplies the descriptive name of the rule through its MEANING column, and the START_DATE_ACTIVE / END_DATE_ACTIVE pair used for the effective-date filter.
  • PA_PROJECTS is joined on PROJECT_TYPE and contributes the PROJECT_ID of the template, restricted by TEMPLATE_FLAG = 'Y'.

The documented join conditions are: PTD.DISTRIBUTION_RULE = DR.DISTRIBUTION_RULE, and PTD.PROJECT_TYPE = PAP.PROJECT_TYPE, with the additional predicates PAP.TEMPLATE_FLAG = 'Y' and TRUNC(SYSDATE) BETWEEN DR.START_DATE_ACTIVE AND NVL(DR.END_DATE_ACTIVE, TRUNC(SYSDATE)). The NVL on the end date means rules with no expiry are treated as open-ended and always current.

Key Columns

The view exposes four columns. The DATA column names documented in ETRM differ from the underlying expression aliases, and both are given here for clarity.

  • CODE — corresponds to the select expression DISTRIBUTION_RULE. It holds the internal distribution rule identifier and is the value typically stored by the calling form or interface.
  • DESCRIPTION — corresponds to DR.MEANING. It is the user-facing name of the distribution rule and is the text displayed in the LOV.
  • PROJECT_TYPE — the project type to which the rule association applies, taken from PA_PROJECT_TYPE_DISTRIBUTIONS.
  • PA_SOURCE_TEMPLATE_ID — corresponds to PAP.PROJECT_ID, the identifier of the template project row matched on project type.

Common Use Cases and Queries

The principal use case is validating or presenting the set of distribution rules that a given project type template may use. The following query returns the full LOV contents:

  • SELECT code, description, project_type, pa_source_template_id FROM apps.pa_distribution_rules_lov_v ORDER BY project_type, description;

To restrict the list to a single project type, for example when populating a dependent LOV or a custom concurrent program parameter:

  • SELECT code, description FROM apps.pa_distribution_rules_lov_v WHERE project_type = :p_project_type;

A third common pattern is to identify which template project supplies a rule, which is useful when tracing configuration issues during project template troubleshooting. Because the view already applies the effective-date and template-flag predicates, custom code that queries it inherits the same business filtering as the standard application forms and avoids returning expired or non-template rule associations.