Search Results master_flag




Overview
Explore in AI Chat

Overview

APPS.PA_JOB_GROUP_COMBOS_V is a reporting view in Oracle E-Business Suite (documented against 12.1.1 and 12.2.2) that exposes the relationships defined between job groups. It is built over the job-group relationship table and joins that table twice to the job groups table so that both the source ("from") and destination ("to") job group names can be presented side by side in a single row. The view is owned by the APPS schema and serves as a read-only integration and reporting object for Project Management and Human Resources data consumers.

A distinguishing characteristic of the view is its treatment of the MASTER_FLAG attribute. Each job group referenced in the relationship is displayed with its own MASTER_FLAG value, allowing report authors to identify whether the from-group and to-group are master job groups. The view does not store data; it is a dynamic SQL definition that resolves business group context at runtime through profile option evaluation.

Underlying Base Objects

The ETRM metadata documents four referenced base objects:

  • PA_JOB_RELATIONSHIPS (synonym) — the driving table, aliased PJR, which stores the from/to job group identifiers that define each relationship.
  • PER_JOB_GROUPS (synonym) — joined twice as PJG1 (from-group) and PJG2 (to-group) to resolve displayed names and master flags.
  • PA_CROSS_BUSINESS_GRP (package) — invoked as PA_CROSS_BUSINESS_GRP.IsCrossBGProfile to determine whether cross-business-group operation is enabled.
  • FND_PROFILE (package) — invoked as FND_PROFILE.VALUE('PER_BUSINESS_GROUP_ID') to restrict results to the current business group when the cross-business-group profile is 'N'.

The join between PA_JOB_RELATIONSHIPS and the two PER_JOB_GROUPS instances is driven by the respective FROM_JOB_GROUP_ID and TO_JOB_GROUP_ID columns. The WHERE clause applies a business-group filter only when the cross-business-group profile evaluates to 'N'; when it is 'Y', the filter is bypassed and relationships across business groups are returned. A DISTINCT operator eliminates duplicate rows.

Key Columns

  • DISPLAYED_NAME (from PJG1) — the user-visible name of the source job group.
  • FROM_JOB_GROUP_ID — the identifier of the source job group in the relationship.
  • PJG1.MASTER_FLAG — indicates whether the source job group is a master job group; this is the column most relevant to the "master_flag" search.
  • DISPLAYED_NAME (from PJG2) — the user-visible name of the destination job group.
  • TO_JOB_GROUP_ID — the identifier of the destination job group in the relationship.
  • PJG2.MASTER_FLAG — indicates whether the destination job group is a master job group.

Because the view exposes two MASTER_FLAG columns with identical names, callers should alias them explicitly in the SELECT list to avoid ambiguity in downstream processing.

Common Use Cases and Queries

The view is typically used to validate and report on job group relationships, particularly where master job group designation must be confirmed on either side of a relationship, and to support data migration or integration extracts that must respect business group boundaries.

A representative query identifying relationships in which either job group is a master group is shown below:

  • SELECT DISTINCT DISPLAYED_NAME, FROM_JOB_GROUP_ID, MASTER_FLAG FROM PA_JOB_GROUP_COMBOS_V;
  • To isolate master-group relationships, filter on the aliased master flag columns after wrapping the view in an inline query, since both columns share the name MASTER_FLAG.
  • To enumerate all from/to pairs regardless of master status: SELECT FROM_JOB_GROUP_ID, TO_JOB_GROUP_ID FROM PA_JOB_GROUP_COMBOS_V;

Because business group context is resolved at runtime, the result set varies with the value of the PER_BUSINESS_GROUP_ID profile option and the cross-business-group setting. Queries should be executed in the appropriate operating context to produce consistent results.