Results for “pa_segment_rule_pairings”

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

Overview

The PA_SEGMENT_RULE_PAIRINGS view is a single-organization (Single-Org) reporting and integration object within the Oracle E-Business Suite Projects (PA) module. Its primary function is to expose the pairing relationships that exist between accounting segment rules used in Oracle Projects and the key flexfield structures against which those rules are applied. These pairings allow Oracle Projects to determine which segment rule should be used to derive accounting flexfield segment values for a given application, function, and transaction type. The view is typically consumed by reporting layers, interfaces, and extensions that need to resolve how project-related transactions are mapped to General Ledger accounting combinations.

Because it is a Single-Org view, the result set is filtered by the operating unit (ORG_ID) derived from the session context. The view text applies a security predicate against USERENV('CLIENT_INFO'), ensuring that only rows belonging to the current organization are returned, or rows where ORG_ID is null (shared or global records).

Underlying Base Objects

According to ETRM documentation, the view is defined over a single documented base object: PA_SEGMENT_RULE_PAIRINGS_ALL. The relationship between the view and the base table is that the view is essentially a filtered projection of the _ALL table, applying the organization security predicate at runtime.

The view text selects columns from PA_SEGMENT_RULE_PAIRINGS_ALL and adds a WHERE clause that compares the ORG_ID column to the current session's organization identifier. When ORG_ID is null, the view substitutes -99, meaning global rows are included. The security logic decodes the first ten characters of CLIENT_INFO, which in Oracle EBS commonly carries the operating unit identifier, and matches it against the stored ORG_ID.

No other referenced base objects are documented in the ETRM metadata. The underlying _ALL table, being a multi-org table, stores the same core columns plus the ORG_ID column that the single-org view leverages for filtering.

Key Columns

The view exposes fourteen columns, each serving a specific purpose:

• APPLICATION_ID — Identifies the Oracle application that owns the segment rule context (for example, Projects or another EBS application).
• FUNCTION_CODE — The functional area code used to categorize which segment rules apply to a given business function.
• FUNCTION_TRANSACTION_CODE — A further refinement identifying the transaction type within the function for which the segment rule pairing is valid.
• ID_FLEX_CODE — The key flexfield code (such as GL#) against which segment rules are defined.
• ID_FLEX_NUM — The specific flexfield structure number, indicating which version or structure of the key flexfield is in play.
• SEGMENT_NUM — The segment number within the key flexfield to which the rule pairing applies.
• RULE_ID — The identifier of the segment rule itself, linking to the rule definition.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard audit columns tracking who created and last modified each row, and when.
• DISPLAY_FLAG — A flag controlling whether the pairing is displayed in configuration or setup screens.
• ORG_ID — The operating unit identifier, used by the single-org security predicate to filter results.

Common Use Cases and Queries

This view is commonly used in diagnostics, reporting, and extension development where there is a need to understand which segment rules are paired with which flexfield structures and application functions. Typical scenarios include troubleshooting why a project transaction failed to derive an accounting flexfield value, verifying configuration during a segment rule setup review, and building custom reports that document the segment rule configuration landscape.

A simple query to retrieve all pairings for the current operating unit is:

• SELECT APPLICATION_ID, FUNCTION_CODE, FUNCTION_TRANSACTION_CODE, ID_FLEX_CODE, ID_FLEX_NUM, SEGMENT_NUM, RULE_ID, DISPLAY_FLAG FROM PA_SEGMENT_RULE_PAIRINGS WHERE DISPLAY_FLAG = 'Y';

For a targeted lookup by flexfield structure and segment, use:

• SELECT RULE_ID, FUNCTION_CODE FROM PA_SEGMENT_RULE_PAIRINGS WHERE ID_FLEX_CODE = 'GL#' AND ID_FLEX_NUM = :flex_num AND SEGMENT_NUM = :seg_num;

Because the view applies operating unit security automatically based on CLIENT_INFO, reports and interfaces do not need to add their own ORG_ID predicates when querying through it. Administrators investigating global (shared) pairings should note that rows with a null ORG_ID are returned to all operating units, which is consistent with the -99 substitution logic in the view text.