Results for “deployment_factor_id”

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

Overview

PQH_PTX_DPF_DF is a transaction staging table owned by the HR schema and shipped with the PQH (Public Sector HR) product family in Oracle EBS 12.1.1 and 12.2.2. Its purpose is to hold deployment factor rows associated with Position Transaction records until those transactions are validated and applied. During the position transaction lifecycle, deployment factor information is captured against a pending transaction, stored in this table, and then written forward to the permanent PER_DEPLOYMENT_FACTORS table once the transaction is applied. The table therefore acts as a transient, transactional holding area rather than a master data repository.

Following the heuristic Data Vault classification mined from its foreign key structure, this object is best modeled as a link. It resolves a many-to-many style association between a position transaction and a deployment factor, carrying the transaction context alongside the factor reference. It is not a hub (it does not own the deployment factor or transaction business keys) and not a pure satellite, since its grain is defined by the pairing of those two references.

Key Information Stored

The table contains 30 documented columns. The most operationally significant are:

• PTX_DEPLOYMENT_FACTOR_ID — the surrogate primary key, enforced by the unique index PQH_PTX_DPF_DF_PK. This is the system-generated identifier for each staging row.
• POSITION_TRANSACTION_ID — foreign key to PQH_POSITION_TRANSACTIONS; identifies the pending position transaction that owns this deployment factor row.
• DEPLOYMENT_FACTOR_ID — foreign key to PER_DEPLOYMENT_FACTORS; identifies the deployment factor being staged for that transaction.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20 — the standard Oracle EBS descriptive flexfield (DFF) segment columns. The object name suffix "_DF" reflects that the table carries a flexfield context and its twenty context-sensitive segments, allowing customers to capture site-specific deployment factor detail.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns recording row provenance.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the ORM layer to detect concurrent updates.

The surrogate key PTX_DEPLOYMENT_FACTOR_ID is the sole documented unique index. No composite business-key unique index over POSITION_TRANSACTION_ID plus DEPLOYMENT_FACTOR_ID is documented, so uniqueness of the pairing is enforced by application logic rather than by a database constraint.

Common Use Cases and Queries

The primary use case is diagnostics: reconciling deployment factors captured on pending position transactions against the rows ultimately written to PER_DEPLOYMENT_FACTORS. A typical query lists all staged factors for a transaction:

• SELECT ptx_deployment_factor_id, position_transaction_id, deployment_factor_id FROM hr.pqh_ptx_dpf_df WHERE position_transaction_id = :transaction_id;

Joining to the transaction header provides context useful for transaction workbench reporting:

• SELECT t.transaction_id, d.deployment_factor_id FROM hr.pqh_ptx_dpf_df d, hr.pqh_position_transactions t WHERE d.position_transaction_id = t.position_transaction_id;

Data-cleansing scripts frequently identify orphaned or stale staging rows, for example rows whose parent transaction has been fully applied or rolled back. Because the DFF columns are populated via ATTRIBUTE_CATEGORY, flexfield-aware extracts must read the category before interpreting ATTRIBUTE1 through ATTRIBUTE20. Reporting on this table is normally confined to in-flight transactions, since applied data is expected to reside in PER_DEPLOYMENT_FACTORS.

Related Objects

• PQH_POSITION_TRANSACTIONS — parent transaction table; joined via PQH_PTX_DPF_DF.POSITION_TRANSACTION_ID. This is the driving relationship for all staging lookups.
• PER_DEPLOYMENT_FACTORS — target table to which rows are applied; joined via PQH_PTX_DPF_DF.DEPLOYMENT_FACTOR_ID.
• PER_DEPLOYMENT_FACTOR_VALUES (and related PER deployment factor value objects) — hold the effective-dated factor values referenced once the staging row is applied.
• PQH_POSITION_TRANSACTIONS_API — the public API through which position transactions, and their deployment factor rows, are created, validated, and applied; it is the supported programmatic path rather than direct DML against this table.
• PQH_POSITION_TRANSACTION_* concurrent programs — the transaction maintenance processes that consume these staging rows and post them forward.

Direct modification of PQH_PTX_DPF_DF is unsupported; integrations should use the PQH position transaction APIs so that validation, DFF handling, and the forward write to PER_DEPLOYMENT_FACTORS remain consistent.