Search Results to_job_group_id




Overview
Explore in AI Chat

Overview

APPS.PA_JOB_RELATIONSHIPS_VIEW is a reporting view in Oracle EBS Projects (PA) that flattens the job-to-job relationships stored in PA_JOB_RELATIONSHIPS into a readable, human-friendly form. Rather than exposing raw surrogate identifiers, the view resolves job IDs and job group IDs into their corresponding names and displayed names by joining to PER_JOBS and PER_JOB_GROUPS. It is used primarily in Projects reporting and integration scenarios where the relationship between a "from" job and a "to" job — and the job groups that govern those jobs — must be presented in business terms.

Because it is owned by APPS and references several HR/PER objects as synonyms, it serves as a bridge between Oracle Projects job definitions and Oracle HR job and job group definitions. The view also honors the multi-business-group security profile through PA_CROSS_BUSINESS_GRP and FND_PROFILE, so results are filtered according to whether the user operates in a cross-business-group context.

Underlying Base Objects

The documented base objects are:

  • PA_JOB_RELATIONSHIPS (SYNONYM) — the primary transactional table holding FROM_JOB_ID, TO_JOB_ID, FROM_JOB_GROUP_ID and TO_JOB_GROUP_ID pairings.
  • PER_JOBS (SYNONYM) — supplies the job NAME for both the from and to jobs.
  • PER_JOB_GROUPS (SYNONYM) — supplies DISPLAYED_NAME and MASTER_FLAG for the from and to job groups.
  • PA_CROSS_BUSINESS_GRP (PACKAGE) — determines whether cross-business-group visibility applies.
  • FND_PROFILE (PACKAGE) — used via fnd_profile.value('PER_BUSINESS_GROUP_ID') to enforce the current business group.

The view is defined as a UNION. The first branch joins PA_JOB_RELATIONSHIPS twice (JR1 and JR2) to stitch a multi-hop path (from job to intermediate to job), requiring the intermediate group to have MASTER_FLAG='Y' and the endpoint groups MASTER_FLAG='N'. The second branch (introduced for bug 1654186) handles the case where the HR job equals the master job, using a DECODE on the cross-business-group profile to reproduce the business group filter.

Key Columns

  • FROM_JOB_NAME — name of the originating job.
  • FROM_JOB_ID — identifier of the originating job.
  • TO_JOB_NAME — name of the destination job, the target of the "to_job_group_id" relationship sought.
  • TO_JOB_ID — identifier of the destination job.
  • FROM_JOB_GROUP_NAME — displayed name of the from job group.
  • FROM_JOB_GROUP_ID — identifier of the from job group.
  • TO_JOB_GROUP_NAME — displayed name of the destination job group.
  • TO_JOB_GROUP_ID — identifier of the destination job group, the column most frequently referenced in "to_job_group_id" searches.

Common Use Cases and Queries

Typical uses include validating Projects job mappings, troubleshooting job group assignments during implementation, and building reports that explain which job group a destination job belongs to. A common query searches by destination job group:

  • SELECT from_job_name, to_job_name, from_job_group_name, to_job_group_name FROM apps.pa_job_relationships_view WHERE to_job_group_id = :group_id;
  • SELECT to_job_name, to_job_group_name FROM apps.pa_job_relationships_view WHERE from_job_name = :job_name;
  • SELECT DISTINCT to_job_group_name FROM apps.pa_job_relationships_view ORDER BY 1;

Because the view applies business-group security logic internally, queries automatically return only the job groups visible under the current PER_BUSINESS_GROUP_ID, making it safe for secured reporting without additional predicates.