Results for “row_type_cd”

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

Overview

The PQH_COPY_ENTITY_ATTRIBS table is a core data object within the Oracle E-Business Suite Public Sector HR (PQH) module. It resides in the HR schema and holds the criteria and change lists that drive the mass process (mass copy or mass update) functionality used by public sector customers to replicate or transform HR entities across organizations, positions, and related records. In ETRM 12.2.2 the table is documented with 43 columns and a single unique index, PQH_COPY_ENTITY_ATTRIBS_PK, defined on COPY_ENTITY_ATTRIB_ID.

The table is classified as VALID and is present in both 12.1.1 and 12.2.2; the physical schema documented here reflects the 12.2.2 ETRM snapshot. A heuristic Data Vault classification, mined from its foreign-key structure, suggests that this object behaves as a satellite-leaning entity — it hangs off a parent transaction record and stores descriptive, attribute-level detail rather than acting as a standalone hub. It should be noted that this classification is a modeling suggestion derived from FK topology, not an Oracle-designated designation.

Key Information Stored

Although the table contains 43 columns, its most significant columns fall into a small number of functional groups:

• COPY_ENTITY_ATTRIB_ID — the surrogate primary key (PK PQH_COPY_ENTITY_ATTRIBS_PK), uniquely identifying each attribute row.
• COPY_ENTITY_TXN_ID — the foreign key to PQH_COPY_ENTITY_TXNS, linking each attribute row to its parent mass-process transaction. This is the primary business-key candidate for joining back to the transaction.
• ROW_TYPE_CD — a code distinguishing the type of row (for example, criterion versus change-list entry) being stored.
• INFORMATION_CATEGORY — categorizes the type of information being captured for the mass process.
• INFORMATION1 … INFORMATION30 — a wide, repeating set of generic attribute slots holding the actual criteria values and change-list values. These are heavily used by the mass-process engine to store per-attribute configuration.
• CHECK_INFORMATION1, CHECK_INFORMATION2, CHECK_INFORMATION3 — dedicated slots for validation/check-related values tied to the criteria.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard EBS WHO columns providing concurrency control and audit tracking.

The surrogate key (COPY_ENTITY_ATTRIB_ID) is distinct from any business identifier; the documented unique index confirms it as the sole business-key candidate. The wide INFORMATIONn naming is characteristic of PQH's flexible attribute model, allowing new criteria without schema change.

Common Use Cases and Queries

Typical usage centers on auditing, troubleshooting, and reporting on mass-process executions. A common pattern joins attributes back to their parent transaction:

• Reviewing the attributes configured for a specific mass-process run: SELECT * FROM PQH_COPY_ENTITY_ATTRIBS WHERE COPY_ENTITY_TXN_ID = :txn_id.
• Reporting on which criteria categories were used: filter or group by ROW_TYPE_CD and INFORMATION_CATEGORY.
• Joining to PQH_COPY_ENTITY_TXNS to correlate attribute detail with transaction status and timestamps.
• Auditing change history via the WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY) to identify who modified a criteria set.

Because the INFORMATIONn columns are generic, reporting queries generally decode them against the mass-process setup or metadata rather than referencing fixed meanings.

Related Objects

The most significant related object is its parent transaction table, established directly by the documented foreign key:

• PQH_COPY_ENTITY_TXNS — joined via PQH_COPY_ENTITY_ATTRIBS.COPY_ENTITY_TXN_ID = PQH_COPY_ENTITY_TXNS.COPY_ENTITY_TXN_ID (per the documented FK). This parent table holds the transaction-level context for each mass-process run.
• PQH_COPY_ENTITY_ATTRIBS_PK — the primary-key index on COPY_ENTITY_ATTRIB_ID, supporting direct lookups and referential integrity.

Additional PQH mass-process objects (for example, related transaction and entity tables in the same PQH_COPY_ENTITY_* family) are typically referenced through the parent transaction record, but only PQH_COPY_ENTITY_TXNS is explicitly documented as a FK target in the ETRM metadata above.