Results for “position_transaction_id”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PQH_WORKSHEET_DETAILS is a Public Sector HR (PQH) transactional table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a work table for HR entities associated with budget information, holding the individual budget worksheet lines that drive position budgeting, budget validation, and budget roll-up activity in the Public Sector budgeting and position management flows. Each row represents a single budgeting entity — an organization, job, position, grade, or position transaction — combined with an action performed against that entity on a parent worksheet.
From a Data Vault modeling perspective, the mined foreign key structure suggests a satellite-leaning classification. The table is anchored by surrogate keys and carries a large complement of descriptive and quantitative attributes (percentages, values, availability flags, status), which is characteristic of a satellite record rather than a pure hub or link. This is offered as a heuristic modeling suggestion only; the physical table is a native EBS transactional object.
The table is uniquely identified at the physical level by PQH_WORKSHEET_DETAILS_PK on WORKSHEET_DETAIL_ID, with a 35-column documented schema.
Key Information Stored
The surrogate primary key is WORKSHEET_DETAIL_ID, which uniquely identifies each worksheet detail line. Several business-key candidates are enforced through unique indexes:
- ACTION_CD — the action code applied to the worksheet line. This is the column the user searched for, and it participates directly in the unique key
PQH_WORKSHEET_DETAILS_UKalongsideWORKSHEET_ID,ORGANIZATION_ID,JOB_ID,POSITION_ID,GRADE_ID, andPOSITION_TRANSACTION_ID. Together these columns distinguish the exact entity-action combination for a worksheet. - WORKSHEET_ID — the parent worksheet header this detail belongs to; the primary linkage back to
PQH_WORKSHEETS. - ORGANIZATION_ID, JOB_ID, POSITION_ID, GRADE_ID — the HR entity identifiers that the budget line targets.
- POSITION_TRANSACTION_ID and BUDGET_DETAIL_ID — references into position transaction and budget detail source records.
- PARENT_WORKSHEET_DETAIL_ID — self-referencing parent linkage that supports worksheet detail hierarchies.
- BUDGET_UNIT1_PERCENT, BUDGET_UNIT2_PERCENT, BUDGET_UNIT3_PERCENT — the distribution percentages across the three budget units.
- BUDGET_UNIT1_VALUE, BUDGET_UNIT2_VALUE, BUDGET_UNIT3_VALUE — the monetary or unit values associated with each distribution.
- STATUS and DEFER_FLAG — workflow status and deferral indicator for the detail line.
- PROPAGATION_METHOD — controls how budget values propagate.
Standard EBS audit columns (LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER) are also present.
Common Use Cases and Queries
Typical usage centers on querying worksheet detail lines by action and entity. A common pattern filters on ACTION_CD to isolate a specific budget action type across one or more worksheets:
SELECT wd.worksheet_detail_id, wd.worksheet_id, wd.action_cd,
wd.organization_id, wd.position_id, wd.grade_id, wd.status
FROM hr.pqh_worksheet_details wd
WHERE wd.action_cd = :p_action_cd
AND wd.worksheet_id = :p_worksheet_id;
Other frequent scenarios include budget percentage reconciliation across BUDGET_UNIT1_PERCENT through BUDGET_UNIT3_PERCENT, seeking deferred lines via DEFER_FLAG, rolling detail up to the worksheet header, and joining to PQH_WORKSHEET_PERIODS to obtain the period breakdown for each detail line.
Related Objects
- PQH_WORKSHEETS — parent worksheet header, joined on
WORKSHEET_ID. - PQH_WORKSHEET_PERIODS — child period records referencing
WORKSHEET_DETAIL_ID. - PPQH_WORKSHEET_DETAILS (self-reference) — parent/child hierarchy via
PARENT_WORKSHEET_DETAIL_ID. - PQH_BUDGET_DETAILS — source budget data joined on
BUDGET_DETAIL_ID. - PQH_POSITION_TRANSACTIONS — position transaction linkage on
POSITION_TRANSACTION_ID. - HR_ALL_ORGANIZATION_UNITS — organization reference on
ORGANIZATION_ID. - PER_JOBS and PER_GRADES — job and grade references on
JOB_IDandGRADE_ID.
-
Work table of Hr entities for Budget information
-
Transaction Job Requirements Shadow Table
-
View: HR_ALL_POSITIONS 12.2.2
Date-effective view.
APPS.HR_ALL_POSITIONS·↳ FND_SESSIONS·↳ HR_ALL_POSITIONS_F·↳ HR_GENERAL·Explore PER module →
-
Position Extra information shadow used for refreshing position transaction extra information.
-
Work table of Hr entities for Budget information
-
Deployment factors shadow for Position Transaction
-
Deployment factors for Position Transaction records are stored until the transaction is applied to PER_DEPLOYMENT_FACTORS
-
Deployment factors for Position Transaction records are stored until the transaction is applied to PER_DEPLOYMENT_FACTORS
-
Transaction table for per_job_requirements ( part of position control )
-
Extra information details for Position transaction.
-
View: HR_ALL_POSITIONS_V1 12.2.2
Date-effective view with reduced pl/sql functions for performance.
APPS.HR_ALL_POSITIONS_V1·↳ FND_SESSIONS·↳ HR_ALL_POSITIONS_F·↳ HR_ALL_POSITIONS_F_TL·Explore PER module →
-
Extra information details for Position transaction.
-
Deployment factors shadow for Position Transaction
-
View: HR_POSITIONS_X 12.2.2
Date-effective view based on secured positions view.
APPS.HR_POSITIONS_X·↳ FND_PROFILE·↳ HR_GENERAL·↳ HR_POSITIONS_F·Explore PER module →
-
APPS.PQH_TXN_JOB_REQUIREMENTS_V·↳ HR_GENERAL·↳ PQH_TXN_JOB_REQUIREMENTS·Explore PQH module →
-
Transaction table for per_job_requirements ( part of position control )
-
View: HR_POSITIONS_X 12.1.1
Date-effective view based on secured positions view.
APPS.HR_POSITIONS_X·↳ FND_PROFILE·↳ HR_GENERAL·↳ HR_POSITIONS_F·Explore PER module →
-
View: HR_POSITIONS 12.1.1
Date-effective view based on secured positions view.
APPS.HR_POSITIONS·↳ FND_PROFILE·↳ FND_SESSIONS·↳ HR_GENERAL·Explore PER module →
-
Copy of the Position Transaction Table. This is used for position transaction refresh.
-
Position Extra information shadow used for refreshing position transaction extra information.
-
View: GHR_POSITIONS_H_V 12.2.2
Mapping of GHR_PA_HISTORY columns to HR_ALL_POSITIONS_F.
APPS.GHR_POSITIONS_H_V·↳ FND_DATE·↳ GHR_GENERAL·↳ GHR_PA_HISTORY·Explore GHR module →
-
View: HR_POSITIONS_F 12.2.2
Secure view based on the corresponding _ALL_ table.
APPS.HR_POSITIONS_F·↳ FND_PROFILE·↳ HR_ALL_POSITIONS_F·↳ HR_ALL_POSITIONS_F_TL·Explore PER module →
-
Transaction Job Requirements Shadow Table
-
APPS.PQH_TXN_JOB_REQUIREMENTS_V·↳ HR_GENERAL·↳ PQH_TXN_JOB_REQUIREMENTS·Explore PQH module →
-
POSITION_TRANSACTION is used to maintain and create positions. Each transaction needs to be approved by pre-identified approvers. On approval these transactions are applied to database.Each transaction can have a combination of one or more
-
View: HR_POSITIONS_F 12.1.1
Secure view based on the corresponding _ALL_ table.
APPS.HR_POSITIONS_F·↳ FND_PROFILE·↳ HR_ALL_POSITIONS_F·↳ HR_ALL_POSITIONS_F_TL·Explore PER module →
-
View: HR_POSITIONS 12.2.2
Date-effective view based on secured positions view.
APPS.HR_POSITIONS·↳ FND_PROFILE·↳ FND_SESSIONS·↳ HR_GENERAL·Explore PER module →
-
View: GHR_POSITIONS_H_V 12.1.1
Mapping of GHR_PA_HISTORY columns to HR_ALL_POSITIONS_F.
APPS.GHR_POSITIONS_H_V·↳ FND_DATE·↳ GHR_GENERAL·↳ GHR_PA_HISTORY·Explore GHR module →
-
POSITION_TRANSACTION is used to maintain and create positions. Each transaction needs to be approved by pre-identified approvers. On approval these transactions are applied to database.Each transaction can have a combination of one or more
-
Copy of the Position Transaction Table. This is used for position transaction refresh.
-
View: HR_ALL_POSITIONS 12.1.1
Date-effective view.
APPS.HR_ALL_POSITIONS·↳ FND_SESSIONS·↳ HR_ALL_POSITIONS_F·↳ HR_GENERAL·Explore PER module →
-
View: HR_POSITIONS_V1 12.1.1
To support User Interface.
APPS.HR_POSITIONS_V1·↳ FND_PROFILE·↳ HR_GENERAL·↳ HR_POSITIONS_F·Explore PER module →
-
View: HR_ALL_POSITIONS_F_VL 12.1.1
APPS.HR_ALL_POSITIONS_F_VL·↳ HR_ALL_POSITIONS_F·↳ HR_ALL_POSITIONS_F_TL·Explore PER module →
-
View: HR_POSITION_API_V 12.2.2
APPS.HR_POSITION_API_V·↳ HR_ALL_POSITIONS_F·↳ PER_POSITION_DEFINITIONS·Explore PER module →
-
View: HR_POSITIONS_V 12.2.2
To support User Interface.
APPS.HR_POSITIONS_V·↳ FND_SESSIONS·↳ HR_ALL_POSITIONS_F·↳ HR_GENERAL·Explore PER module →
-
View: HR_POSITIONS_V 12.1.1
To support User Interface.
APPS.HR_POSITIONS_V·↳ FND_SESSIONS·↳ HR_ALL_POSITIONS_F·↳ HR_GENERAL·Explore PER module →
-
View: HR_ALL_POSITIONS_V1 12.1.1
Date-effective view with reduced pl/sql functions for performance.
APPS.HR_ALL_POSITIONS_V1·↳ FND_SESSIONS·↳ HR_ALL_POSITIONS_F·↳ HR_ALL_POSITIONS_F_TL·Explore PER module →
-
View: HR_POSITION_API_V 12.1.1
APPS.HR_POSITION_API_V·↳ HR_ALL_POSITIONS_F·↳ PER_POSITION_DEFINITIONS·Explore PER module →
-
APPS.PQH_POSITION_TRANSACTIONS_V·↳ HR_GENERAL·↳ PQH_POSITION_TRANSACTIONS·↳ PQH_UTILITY·Explore PQH module →
-
Position definition information.
-
Position definition information.
-
View: HR_POSITIONS_V1 12.2.2
To support User Interface.
APPS.HR_POSITIONS_V1·↳ FND_PROFILE·↳ HR_GENERAL·↳ HR_POSITIONS_F·Explore PER module →
-
View: HR_ALL_POSITIONS_F_VL 12.2.2
APPS.HR_ALL_POSITIONS_F_VL·↳ HR_ALL_POSITIONS_F·↳ HR_ALL_POSITIONS_F_TL·Explore PER module →
-
APPS.PQH_POSITION_TRANSACTIONS_V·↳ HR_GENERAL·↳ PQH_POSITION_TRANSACTIONS·↳ PQH_UTILITY·Explore PQH module →
-
PACKAGE: APPS.PQH_PTX_UTL 12.1.1