Results for “start_with”

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

Overview

PQH_COPY_ENTITY_TXNS is a table in the HR schema of Oracle E-Business Suite, owned by the PQH - Public Sector HR product. It stores batch details for mass processes, specifically acting as the transaction header that drives the "Copy Entity" mass processing framework used by public sector HR customers. Each row represents a single copy-entity transaction definition: a reusable, parameterized batch instruction that determines what entity is copied, how many copies are produced, and which transaction category governs the behavior.

The table occupies a central position within a small, tightly coupled cluster of PQH objects. It is referenced by attribute, preference, and result tables, and it in turn references transaction category, context, and organization unit definitions. Based on the foreign key topology mined from the schema, the table leans toward a satellite classification in Data Vault terms: it carries descriptive batch attributes and depends on upstream reference tables (transaction categories, contexts, business groups) rather than acting as a pure hub of business keys or a pure link between two hubs. Modelers should treat this as a suggested classification rather than a documented one, since the metadata is heuristic.

Key Information Stored

The surrogate primary key is COPY_ENTITY_TXN_ID, enforced by the PQH_COPY_ENTITY_TXNS_PK index. A separate unique index, PQH_COPY_ENTITY_TXNS_UK, captures the business-key candidate combination of TRANSACTION_CATEGORY_ID, CONTEXT_BUSINESS_GROUP_ID, and DISPLAY_NAME, meaning a transaction is uniquely identified in business terms by its category, the business group context in which it operates, and its user-facing name.

• COPY_ENTITY_TXN_ID — surrogate primary key and the column referenced by all dependent tables.
• TRANSACTION_CATEGORY_ID — foreign key to PQH_TRANSACTION_CATEGORIES; defines the type of mass copy operation.
• WF_TRANSACTION_CATEGORY_ID — a second reference to PQH_TRANSACTION_CATEGORIES, typically associating the workflow-driven category variant.
• TXN_CATEGORY_ATTRIBUTE_ID — foreign key to PQH_TXN_CATEGORY_ATTRIBUTES; links the transaction to its configured attribute set.
• CONTEXT — foreign key to PQH_COPY_ENTITY_CONTEXTS; identifies the entity context (for example, position or assignment) being copied.
• CONTEXT_BUSINESS_GROUP_ID — foreign key to HR_ALL_ORGANIZATION_UNITS; isolates the transaction to a business group.
• DISPLAY_NAME — the user-visible name of the batch transaction.
• ACTION_DATE — the effective date on which the copy action is applied.
• SRC_EFFECTIVE_DATE — the source effective date from which entity data is read.
• NUMBER_OF_COPIES — how many copies the batch produces.
• START_WITH and INCREMENT_BY — numbering controls used when generating successive copies.
• REPLACEMENT_TYPE_CD — governs how values are substituted across generated copies.
• STATUS — lifecycle state of the batch transaction.
• DATETRACK_MODE — indicates the date-tracking behavior applied during the copy.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard EBS audit and optimistic-locking columns.

Common Use Cases and Queries

The primary operational use is to inspect or troubleshoot configured mass copy batches before execution, and to reconcile the results that those batches produced. A typical lookup resolves the display name and business group back to the surrogate key:

• Retrieve active batches for a business group: SELECT copy_entity_txn_id, display_name, transaction_category_id, status FROM pqh_copy_entity_txns WHERE context_business_group_id = :p_bg_id AND status = 'A';
• Join the transaction to its category and context to describe the operation in a report: SELECT t.display_name, tc.name, c.context_name, t.number_of_copies FROM pqh_copy_entity_txns t, pqh_transaction_categories tc, pqh_copy_entity_contexts c WHERE t.transaction_category_id = tc.transaction_category_id AND t.context = c.context;
• Audit throughput by linking to results: SELECT t.display_name, COUNT(r.copy_entity_txn_id) FROM pqh_copy_entity_txns t, pqh_copy_entity_results r WHERE t.copy_entity_txn_id = r.copy_entity_txn_id GROUP BY t.display_name;

Reporting use cases include batch configuration audits, effective-dating validation between ACTION_DATE and SRC_EFFECTIVE_DATE, and volume analysis of copy operations by business group. Because the table carries audit columns, it also supports change-tracking queries for records modified after a given LAST_UPDATE_DATE.

Related Objects

The table sits within a compact dependency graph. The most significant related objects, with their join columns, are:

• PQH_COPY_ENTITY_ATTRIBS — child table joined on COPY_ENTITY_TXN_ID; holds attribute-level detail for each transaction.
• PQH_COPY_ENTITY_PREFS — child table joined on COPY_ENTITY_TXN_ID; stores preferences controlling copy behavior.
• PQH_COPY_ENTITY_RESULTS — child table joined on COPY_ENTITY_TXN_ID; records the outcome of executed batches.
• BEN_COPY_ENTITY_RESULTS — cross-product child table joined on COPY_ENTITY_TXN_ID; captures benefits-side results for the same transaction.
• PQH_TRANSACTION_CATEGORIES — parent reference via TRANSACTION_CATEGORY_ID and WF_TRANSACTION_CATEGORY_ID.
• PQH_TXN_CATEGORY_ATTRIBUTES — parent reference via TXN_CATEGORY_ATTRIBUTE_ID.
• PQH_COPY_ENTITY_CONTEXTS — parent reference via CONTEXT.
• HR_ALL_ORGANIZATION_UNITS — parent reference via CONTEXT_BUSINESS_GROUP_ID, tying the transaction to its business group.

Together these objects form the complete Copy Entity framework: this table defines the batch, the attribute and preference tables configure it, and the results tables record its execution.