Results for “service_minimum”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PQH_PTX_SHADOW is a Public Sector HR (PQH) table owned by the HR schema. Its documented description states that it is a "Position Extra information shadow used for refreshing position transaction extra information." In Oracle EBS 12.1.1 and 12.2.2, it functions as a staging or shadow store that mirrors the extra (descriptive and flexfield) attributes attached to a position transaction, allowing those attributes to be refreshed, reconciled, or re-derived without directly mutating the position transaction record. It sits beneath the transactional layer that drives Position Management in the Public Sector HR product family, where position definitions, amendments, and their rich descriptive data are maintained.
From a data modeling perspective, the heuristic Data Vault classification is satellite-leaning. This suggestion reflects the table's structure: it is keyed uniquely by POSITION_TRANSACTION_ID, which is a foreign reference to the parent transaction, and it carries a wide set of descriptive attributes rather than acting as a hub of business keys or a many-to-many link. Under this interpretation, PQH_PTX_SHADOW would behave as a satellite table whose driving key is the position transaction identifier, storing the descriptive context associated with each transaction row.
Key Information Stored
The table is documented with 147 columns in the 12.2.2 schema. The most operationally significant columns include:
- POSITION_TRANSACTION_ID — the primary key column of the PQH_PTX_SHADOW_PK unique index and the foreign key to PQH_POSITION_TRANSACTIONS. This is the dominant business-key candidate on the table and the join anchor for all transaction-level reporting.
- POSITION_ID — identifies the position to which the shadowed extra information belongs.
- PAY_BASIS_ID — foreign key to PER_PAY_BASES, linking the transaction to its pay basis definition.
- BUSINESS_GROUP_ID and ORGANIZATION_ID — the multi-tenant and organizational context for the record.
- ACTION_DATE, DATE_EFFECTIVE, and DATE_END — the effective-dating and action timing columns that govern when the position transaction extra information applies.
- ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE30, ATTRIBUTE_CATEGORY, and INFORMATION1 through INFORMATION30 with INFORMATION_CATEGORY — the descriptive flexfield and extra-information segments that constitute the core payload this shadow table exists to refresh.
- OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS Who columns supporting concurrency control and audit.
The surrogate key is POSITION_TRANSACTION_ID via PQH_PTX_SHADOW_PK. A second documented index, SYS_IL0000137912C00147$$, is a system-managed LOB index and is not a business-key candidate.
Common Use Cases and Queries
Typical usage centers on verifying and reconciling extra information between a position transaction and its shadow copy. A common pattern joins the shadow table back to the parent transaction:
- Detecting rows where the shadow's ATTRIBUTE or INFORMATION segments have not yet been refreshed against the parent transaction.
- Reporting the current extra-information payload for a set of position actions within a business group or date-effective window.
- Auditing changes to descriptive flexfield values against LAST_UPDATE_DATE and OBJECT_VERSION_NUMBER.
A representative query shape is: select the transaction and shadow columns from PQH_PTX_SHADOW s join PQH_POSITION_TRANSACTIONS t on s.POSITION_TRANSACTION_ID = t.POSITION_TRANSACTION_ID, filtered by BUSINESS_GROUP_ID and an ACTION_DATE or DATE_EFFECTIVE range. Reporting frequently pivots on ATTRIBUTE_CATEGORY or INFORMATION_CATEGORY to group the extra information by category.
Related Objects
The following objects are most significant to this table, based on the documented foreign keys and the PQH transactional model:
- PQH_POSITION_TRANSACTIONS — referenced via PQH_PTX_SHADOW.POSITION_TRANSACTION_ID; the primary parent of the shadow record.
- PER_PAY_BASES — referenced via PQH_PTX_SHADOW.PAY_BASIS_ID; supplies pay basis definitions.
- PER_ALL_POSITIONS — the position definition referenced by POSITION_ID.
- HR_ALL_ORGANIZATION_UNITS — the organizational unit referenced by ORGANIZATION_ID.
- FND_DESCR_FLEX_COLUMN_USAGES and related flexfield metadata views — describe the ATTRIBUTE and INFORMATION segment usage that this shadow table refreshes.
Together these relationships position PQH_PTX_SHADOW as a dependent, satellite-style store beneath the PQH position transaction entity, supporting refresh and reconciliation of position extra information.
-
Position Extra information shadow used for refreshing position transaction extra information.
-
APPS.PQH_POSITION_TRANSACTIONS_V·↳ HR_GENERAL·↳ PQH_POSITION_TRANSACTIONS·↳ PQH_UTILITY·Explore PQH module →
-
APPS.PQH_POSITION_TRANSACTIONS_V·↳ HR_GENERAL·↳ PQH_POSITION_TRANSACTIONS·↳ PQH_UTILITY·Explore PQH module →
-
Used to support user interface
APPS.PER_DEPLOYMENT_FACTORS_V·↳ FND_TERRITORIES_VL·↳ HR_API·↳ HR_GENERAL·Explore PER 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
-
A factor affecting a person's capacity to be deployed within an organization.
-
A factor affecting a person's capacity to be deployed within an organization.
-
Used to support user interface
APPS.PER_DEPLOYMENT_FACTORS_V·↳ FND_GLOBAL·↳ FND_TERRITORIES_VL·↳ HR_API·Explore PER 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
-
Position Extra information shadow used for refreshing position transaction extra information.
-
VIEW: HR.PQH_PTX_SHADOW# 12.2.2
-
VIEW: HR.PQH_PTX_SHADOW# 12.2.2
-
Business view template from which the flexfield view is generated.
APPS.HRFV_DEPLOYMENT_FACTORS·↳ FND_TERRITORIES_VL·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ HR_ALL_POSITIONS_F_TL·Explore PER module →
-
Business view template from which the flexfield view is generated.
APPS.HRFV_DEPLOYMENT_FACTORS·↳ FND_TERRITORIES_VL·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ HR_ALL_POSITIONS_F_TL·Explore PER module →
-
TABLE: HR.PQH_PTX_SHADOW 12.1.1
-
TABLE: HR.PQH_PTX_SHADOW 12.2.2