Results for “created_by_module”

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

Overview

HZ_GROUP_VAL_GT is a transient staging table owned by the AR (Receivables) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name and column structure indicate it functions as a global temporary (GT) object used during group or party validation processing—most likely the intermediate validation of customer grouping structures (for example, groups created through Trading Community Architecture or party relationships) before those records are committed to their final destination tables.

From a heuristic Data Vault modeling perspective, this object is classified as standalone, meaning the mined foreign-key structure does not expose the classic hub/link/satellite relationships typical of persistent master data. In practice, this classification suggests treating the table as a transient staging or batch-processing construct rather than a durable dimension, and any downstream modeling should reference the persistent HZ tables it feeds rather than this GT table itself.

Key Information Stored

The documented physical schema (ETRM 12.2.2) exposes six columns:

• GROUP_NAME — the business identifier for the group being staged or validated; a candidate business-key attribute.
• TEMP_ID — the surrogate/technical identifier linking the staging row back to the originating lockbox or IPA process (see FK below).
• TEMP_PARTY_ID — the party identifier associated with the temporary group record, used to resolve the customer or party being grouped.
• GROUP_TYPE — classification of the group, distinguishing the nature of the grouping (for example, party vs. account grouping).
• CREATED_BY_MODULE — the module or process that generated the staging row, useful for auditing which concurrent program or application loaded the data.
• APPLICATION_ID — the Oracle Applications identifier owning the record, typically AR for this schema.

No primary-key or unique-index metadata is documented, which is consistent with a global temporary table whose rows are session- or transaction-scoped and therefore do not require a persistent unique constraint.

Common Use Cases and Queries

As a staging table, HZ_GROUP_VAL_GT is typically read during validation and reconciliation of group data before final inserts into the persistent HZ tables. Common scenarios include verifying that staged groups match expected lockbox or IPA-derived positions, and tracing which module created a given group record.

A representative query re-joins the staging table to its documented parent to audit group staging:

• SELECT g.GROUP_NAME, g.GROUP_TYPE, g.TEMP_PARTY_ID, g.CREATED_BY_MODULE FROM AR.HZ_GROUP_VAL_GT g WHERE g.APPLICATION_ID = :app_id;
• Join to resolution: SELECT g.*, t.* FROM AR.HZ_GROUP_VAL_GT g JOIN FV_LOCKBOX_IPA_TEMP t ON g.TEMP_ID = t.TEMP_ID;

Reporting use cases focus on troubleshooting group-validation failures, confirming module provenance via CREATED_BY_MODULE, and reconciling staged group names against downstream customer records.

Related Objects

The documented foreign key constrains the following relationship:

• FV_LOCKBOX_IPA_TEMP — referenced through HZ_GROUP_VAL_GT.TEMP_ID → FV_LOCKBOX_IPA_TEMP, indicating the staging rows descend from lockbox/IPA temporary processing.

Additional significant objects include the persistent HZ group and party tables that receive validated output, the TCA party model objects keyed by TEMP_PARTY_ID, and the concurrent programs that populate this GT table during Receivables processing. Practitioners should treat HZ_GROUP_VAL_GT as a transient artifact and query its permanent counterparts for durable reporting.