Results for “ptx_deployment_factor_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PQH_PTX_DPF_DF_SHADOW is a table owned by the HR schema within the Public Sector HR (PQH) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a deployment factors shadow table for position transactions. In the context of Position Transaction (PTX) processing, shadow tables preserve a staging or snapshot copy of deployment factor data associated with a position transaction, allowing the application to compare, validate, or roll back configuration changes before they are committed to the transactional deployment factor structures.

The table is documented as VALID in the ETRM 12.2.2 physical schema with 30 columns. Its heuristic Data Vault classification, mined from the foreign key structure, is standalone — meaning the mined relationship model does not identify it as a classic hub, link, or satellite. This should be treated as a modeling suggestion rather than a definitive architectural statement; functionally, the table behaves like a satellite-like shadow record keyed to a position transaction and a deployment factor, tracking changes over time through WHO columns.

Key Information Stored

• PTX_DEPLOYMENT_FACTOR_ID — Surrogate primary key of the row, forming the PDS_PK unique index (the business-key candidate).
• POSITION_TRANSACTION_ID — Identifies the position transaction to which the shadow deployment factor row belongs, linking the shadow record to the transaction context.
• DEPLOYMENT_FACTOR_ID — References the underlying deployment factor defined in PER_DEPLOYMENT_FACTORS (documented foreign key).
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — The descriptive flexfield (DFF) columns that capture client-specific, context-sensitive attributes attached to the shadow deployment factor record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO columns providing audit and change-tracking metadata; these support time-variant, satellite-style analysis of shadow rows.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the EBS framework to detect concurrent updates.

The surrogate primary key (PTX_DEPLOYMENT_FACTOR_ID) is distinct from the sole unique index candidate, PDS_PK, which the metadata identifies with this column. No additional composite unique business key is documented, so joins should rely on POSITION_TRANSACTION_ID and DEPLOYMENT_FACTOR_ID together.

Common Use Cases and Queries

Typical usage centers on position transaction lifecycle validation and reconciliation. Practitioners query this table to compare shadow deployment factors against their transactional or base counterparts before a transaction is approved or applied.

• Retrieve shadow rows for a given position transaction:
  SELECT PTX_DEPLOYMENT_FACTOR_ID, POSITION_TRANSACTION_ID, DEPLOYMENT_FACTOR_ID FROM HR.PQH_PTX_DPF_DF_SHADOW WHERE POSITION_TRANSACTION_ID = :ptx_id;
• Join to the base deployment factor to inspect DFF context:
  SELECT s.DEPLOYMENT_FACTOR_ID, s.ATTRIBUTE_CATEGORY, s.ATTRIBUTE1 FROM HR.PQH_PTX_DPF_DF_SHADOW s, PER_DEPLOYMENT_FACTORS d WHERE s.DEPLOYMENT_FACTOR_ID = d.DEPLOYMENT_FACTOR_ID;
• Audit recent shadow record changes using WHO columns for troubleshooting transaction processing.
• Reconcile shadow data against the primary deployment factor table to detect orphaned or divergent rows after a failed position transaction.
• Report on client-specific flexfield values (ATTRIBUTE1–20) captured during position transaction staging.

Related Objects

• PER_DEPLOYMENT_FACTORS — Referenced by the documented foreign key on DEPLOYMENT_FACTOR_ID; the master deployment factor definition.
• PQH_PTX_DPF_DF (transactional deployment factor equivalent) — The non-shadow counterpart holding committed deployment factor data for position transactions.
• Position Transaction tables (PQH_POSITION_TRANSACTIONS and related PTX entities) — Linked via POSITION_TRANSACTION_ID.
• HR FND flexfield views and DFF definitions — Consumed by the ATTRIBUTE_CATEGORY and ATTRIBUTE1–20 columns.
• FND_WHO audit infrastructure — Applied through CREATED_BY/LAST_UPDATED_BY and OBJECT_VERSION_NUMBER.