Results for “batch_status”

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

Overview

HZ_MERGE_BATCH is the party merge batch header table in Oracle E-Business Suite, owned by the AR (Receivables) schema and classified as VALID in both release 12.1.1 and 12.2.2. It is the master record for a batch-level party merge operation. Each row corresponds to a distinct merge batch and serves as the grouping header for the parties, duplicate set parties, and entity attributes that participate in that batch. The table effectively provides the entry point for reconciling what was merged, under which rule set, and by which concurrent request.

The 14 documented columns capture the identity, execution context, and status of each merge batch. The primary key HZ_MERGE_BATCH_PK is defined on BATCH_ID. A unique index, HZ_MERGE_BATCH_U1, also exists on BATCH_ID, making it the sole documented business-key candidate. From a Data Vault modeling perspective, the structure of this table—a single durable key with attributes and no composite dependent key—is hub-leaning. This means it can be reasonably modeled as a hub entity, with its status and audit columns treated as satellite-type descriptive attributes rather than part of the business key.

Key Information Stored

The most operationally significant columns of HZ_MERGE_BATCH are:

• BATCH_ID — Surrogate primary key and the batch identifier referenced by all child tables. It is the only column identified as both PK and unique business key candidate.
• BATCH_NAME — User-meaningful label for the merge batch, useful in reports and UI lookups.
• RULE_SET_NAME — The name of the merge rule set applied when the batch executes, governing matching and survivorship logic.
• BATCH_STATUS — Current processing state of the batch, used to distinguish completed merges from in-progress or failed ones.
• BATCH_COMMIT — Indicator controlling whether the batch changes are committed.
• BATCH_DELETE — Indicator for deletion handling within the batch.
• MERGE_REASON_CODE — Code describing the business reason for the merge, supporting audit and reporting by cause.
• REQUEST_ID — The concurrent request that created or ran the batch, linking the batch to the concurrent manager log.
• CREATED_BY / CREATION_DATE — Standard audit columns identifying who created the batch and when.
• LAST_UPDATED_BY / LAST_UPDATE_DATE — Standard audit columns identifying the most recent update to the batch.
• LAST_UPDATE_LOGIN — Login identifier associated with the last update.
• CREATED_BY_MODULE — Indicates the application module that created the batch row.

The remaining audit and control columns follow standard EBS WHO-column conventions and are less frequently used in custom reporting.

Common Use Cases and Queries

The primary use case is auditing and troubleshooting party merges. Administrators and developers query HZ_MERGE_BATCH to find a merge batch by name, request, or status and then drill into its child records.

• Identifying batches executed by a specific concurrent request:
  SELECT batch_id, batch_name, batch_status FROM hz_merge_batch WHERE request_id = :request_id;
• Listing completed merges by reason and rule set for audit reporting:
  SELECT batch_id, batch_name, merge_reason_code, rule_set_name FROM hz_merge_batch WHERE batch_status = 'COMPLETE';
• Counting parties processed per batch by joining to HZ_MERGE_PARTIES on BATCH_ID.
• Reconstructing the parties whose entity attributes were merged by joining HZ_MERGE_ENTITY_ATTRIBUTES on MERGE_BATCH_ID.
• Reporting on duplicate set membership per batch through HZ_DUP_SET_PARTIES on MERGE_BATCH_ID.

Because BATCH_ID is the documented unique key, joins should always anchor on this column rather than on BATCH_NAME, which is not guaranteed unique.

Related Objects

The following objects reference HZ_MERGE_BATCH through documented foreign keys and are the most significant for dependency analysis:

• HZ_MERGE_PARTIES — References BATCH_ID. Holds the individual party records processed within the batch.
• HZ_DUP_SET_PARTIES — References MERGE_BATCH_ID. Holds the duplicate set parties associated with the batch.
• HZ_MERGE_ENTITY_ATTRIBUTES — References MERGE_BATCH_ID. Stores entity attribute details for merged parties.
• Concurrent request tables (FND_CONCURRENT_REQUESTS) — Joined via REQUEST_ID to obtain comple