Search Results action_cd

Overview

The PQH_WORKSHEET_DETAILS table is a core transactional data object within the Oracle E-Business Suite Public Sector Human Resources (PQH) module, specifically for releases 12.1.1 and 12.2.2. It functions as a work table that stores detailed budget-related information for human resources entities during the budget planning and worksheet creation processes. Its primary role is to act as a staging and calculation area where proposed personnel costs, based on specific jobs, grades, positions, and organizations, are defined and manipulated before being finalized into budget details. The table's structure, with its extensive foreign key relationships to other HR and PQH tables, ensures data integrity and supports the complex workflows of public sector budgeting, where personnel costs are a major budgetary component.

Key Information Stored

The table stores a comprehensive set of identifiers that link a worksheet detail line to the broader HRMS structure and the budget process. The primary identifier is the system-generated WORKSHEET_DETAIL_ID. A unique key constraint ensures the combination of ACTION_CD and WORKSHEET_ID is unique, highlighting the table's role in tracking specific actions within a budget worksheet. Critical foreign key columns define the HR context: GRADE_ID (PER_GRADES), POSITION_ID, JOB_ID (PER_JOBS), and ORGANIZATION_ID (HR_ALL_ORGANIZATION_UNITS). The BUDGET_DETAIL_ID links to the PQH_BUDGET_DETAILS table, connecting the worksheet line to a finalized budget element. The POSITION_TRANSACTION_ID (PQH_POSITION_TRANSACTIONS) ties the detail to a specific HR action. The PARENT_WORKSHEET_DETAIL_ID supports hierarchical data structures, allowing for parent-child relationships between detail lines, which is common in multi-level budget roll-ups.

Common Use Cases and Queries

This table is central to generating and analyzing budget worksheets. A common use case involves querying all proposed personnel costs for a specific budget worksheet to review totals before submission. For example, a report summarizing details by organization for worksheet ID 1001 would join to HR_ALL_ORGANIZATION_UNITS. Another critical scenario is tracing the lineage of a budget detail back to its originating worksheet entries for audit purposes, joining on BUDGET_DETAIL_ID. Analysts also run queries to identify all worksheet details associated with a specific position or job to assess the budgetary impact of proposed changes. A sample query pattern to fetch worksheet details with descriptive information would be:

• SELECT wd.WORKSHEET_DETAIL_ID, wd.ACTION_CD, org.NAME, job.NAME AS JOB_NAME, g.NAME AS GRADE_NAME
• FROM PQH_WORKSHEET_DETAILS wd,
• HR_ALL_ORGANIZATION_UNITS org,
• PER_JOBS job,
• PER_GRADES g
• WHERE wd.ORGANIZATION_ID = org.ORGANIZATION_ID
• AND wd.JOB_ID = job.JOB_ID(+)
• AND wd.GRADE_ID = g.GRADE_ID(+)
• AND wd.WORKSHEET_ID = :p_worksheet_id;

Related Objects

The PQH_WORKSHEET_DETAILS table is a central hub with numerous documented foreign key relationships, as per the provided ETRM metadata. Its primary dependencies are:

• PQH_WORKSHEETS: The parent worksheet header (via WORKSHEET_ID).
• PQH_BUDGET_DETAILS: The finalized budget detail record (via BUDGET_DETAIL_ID).
• HR_ALL_ORGANIZATION_UNITS: The organization (via ORGANIZATION_ID).
• PER_JOBS: The job definition (via JOB_ID).
• PER_GRADES: The grade (via GRADE_ID).
• PQH_POSITION_TRANSACTIONS: The associated HR position transaction (via POSITION_TRANSACTION_ID).
• PQH_WORKSHEET_DETAILS (Self-Referential): For hierarchical parent-child relationships (via PARENT_WORKSHEET_DETAIL_ID).
• PQH_WORKSHEET_PERIODS: Child table storing period-level breakdowns for a worksheet detail line (foreign key from PERIODS to WORKSHEET_DETAIL_ID).