Results for “process_batch_id”

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

Overview

CN_PROCESS_BATCHES_ALL is a transactional table in the Oracle Incentive Compensation (CN) module of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. The table stores the process batches generated during the incentive compensation calculation process. Each row represents a unit of calculation work assembled for a given sales representative within a specific incentive period, linking the representative, the period, and the associated sales transaction batch used to derive commission and bonus earnings.

In Data Vault modeling terms, the heuristic classification derived from the foreign key structure is a link. This is consistent with the table's role: it associates independent business entities — sales representatives, periods, SRP periods, quota records, and transaction batches — through a set of foreign key references, rather than serving purely as a descriptive hub or as a change-tracking satellite.

The table is owned by the CN schema and is the parent of downstream incentive calculation results, making it a central orchestration object in the calculation pipeline.

Key Information Stored

The documented physical schema contains 29 columns. The most operationally significant are:

• PROCESS_BATCH_ID — the surrogate primary key (CN_PROCESS_BATCHES_PK), uniquely identifying each calculation batch.
• ORG_ID — the operating unit context; combined with PROCESS_BATCH_ID it forms unique index CN_PROCESS_BATCHES_U1.
• LOGICAL_BATCH_ID — a logical grouping identifier used across related physical batches.
• PHYSICAL_BATCH_ID — the physical batch identifier used for parallel or partitioned processing.
• SRP_PERIOD_ID — foreign key to CN_SRP_PERIODS_ALL, tying the batch to a sales representative period.
• SALESREP_ID — foreign key to CN_SALESREPS_API_ALL, identifying the sales representative.
• PERIOD_ID and END_PERIOD_ID — foreign keys to CN_PERIOD_STATUSES_ALL, defining the calculation period window.
• STATUS_CODE — the current processing state of the batch.
• PROCESS_BATCH_NAME and PROCESS_BATCH_TYPE — descriptive and classification attributes.
• SALES_LINES_TOTAL and COMMISSION_HEADERS_COUNT — aggregated volume metrics for the batch.
• TRX_BATCH_ID — foreign key to CN_TRX_BATCHES_ALL, referencing the source transaction batch.
• QUOTA_ID — foreign key to CN_QUOTAS_ALL, linking quota assignment.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS for row-level security.

Two documented business-key candidates exist beyond the primary key: CN_PROCESS_BATCHES_UK1 (LOGICAL_BATCH_ID, SRP_PERIOD_ID) and CN_PROCESS_BATCHES_UK2 / CN_PROCESS_BATCHES_U3 (LOGICAL_BATCH_ID, SALESREP_ID, PERIOD_ID). These enforce that a logical batch is unique per representative-period combination. Standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrent program columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE) are also present, along with START_DATE and END_DATE.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include retrieving all batches for a given representative and period, tracking batch status during a calculation run, and reconciling counted transaction volumes. Common query patterns select batches joined to CN_SALESREPS_API_ALL and CN_SRP_PERIODS_ALL, filtering on PERIOD_ID or ORG_ID. A representative query:

SELECT p.PROCESS_BATCH_ID, p.PROCESS_BATCH_NAME, p.STATUS_CODE, p.SALES_LINES_TOTAL FROM CN_PROCESS_BATCHES_ALL p WHERE p.SALESREP_ID = :salesrep_id AND p.PERIOD_ID = :period_id;

Additional uses include monitoring batches tied to a specific concurrent REQUEST_ID, identifying orphaned or incomplete batches by STATUS_CODE, and summarizing COMMISSION_HEADERS_COUNT per logical batch for calculation audits. Because security is enforced through SECURITY_GROUP_ID, queries are typically scoped by the FND security model.

Related Objects

CN_PROCESS_BATCHES_ALL sits at the center of several relationships:

• CN_SRP_PERIODS_ALL — joined on SRP_PERIOD_ID (sales representative period).
• CN_SALESREPS_API_ALL — joined on SALESREP_ID (sales representative master).
• CN_PERIOD_STATUSES_ALL — joined on PERIOD_ID and END_PERIOD_ID.
• CN_TRX_BATCHES_ALL — joined on TRX_BATCH_ID (source transaction batch).
• CN_QUOTAS_ALL — joined on QUOTA_ID.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID for security resolution.
• CN_COMM_LINES_API_ALL — child table referencing PROCESS_BATCH_ID, holding calculated commission lines.
• QA_RESULTS and QA_RESULTS_INTERFACE — child tables referencing PROCESS_BATCH_ID for processing quality results.