Search Results transferred_flag




Overview
Explore in AI Chat

Overview

The JG_ZZ_INTEREST_BATCHES_ALL table resides in the AR schema and belongs to the JG (Regional Localizations) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the master repository for interest invoice batch details, capturing the header-level definition of each interest calculation run processed by the regional localization interest engine. This includes Latin American localization scenarios, where statutory late-payment interest on overdue receivables must be computed and invoiced in controlled batches.

From a dimensional-modeling perspective, the mined foreign-key structure classifies this table as hub-leaning. It holds the core business identity of an interest batch, while downstream transactional detail (individual interest invoices) attaches through foreign-key relationships. The table is owned by AR and is documented as VALID in the ETRM reference for release 12.2.2, with eleven physical columns.

Key Information Stored

The physical schema captures batch identity, processing parameters, and audit lineage. The most significant documented columns are:

  • INTEREST_BATCH_ID — surrogate identifier for the batch; participates in the composite primary key and the unique business-key index.
  • ORG_ID — operating unit discriminator, enforcing multi-org data separation; also part of the primary key and unique index.
  • BATCH_NAME — user-assigned descriptive label identifying the interest batch for reporting and reconciliation.
  • CALCULATE_INTEREST_TO_DATE — the cutoff date through which interest is computed for the batch.
  • GL_DATE — the general ledger accounting date applied to the resulting interest invoices.
  • TRANSFERRED_FLAG — status indicator denoting whether the batch has been transferred or posted downstream.
  • CREATED_BY, CREATION_DATE — audit columns recording batch creation identity and timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit trail capturing the most recent modification session.

The surrogate primary key is JG_ZZ_INTEREST_BATCHES_PK (INTEREST_BATCH_ID, ORG_ID). The unique index JG_ZZ_INTEREST_BATCHES_U1 (INTEREST_BATCH_ID, ORG_ID) functions as the documented business-key candidate, confirming that batch identity is meaningful only within the scope of a single operating unit.

Common Use Cases and Queries

Typical usage centers on batch monitoring, interest reconciliation, and transfer-status reporting. A standard query retrieves batch headers for an operating unit within a date range:

  • SELECT interest_batch_id, batch_name, calculate_interest_to_date, gl_date, transferred_flag FROM jg_zz_interest_batches_all WHERE org_id = :p_org_id AND creation_date >= :p_from_date;
  • Join to invoice detail to reconcile batch totals: SELECT b.batch_name, COUNT(i.interest_invoice_id) FROM jg_zz_interest_batches_all b, jg_zz_interest_invoices_all i WHERE b.interest_batch_id = i.interest_batch_id AND b.org_id = i.org_id GROUP BY b.batch_name;
  • Identify untransferred batches: SELECT * FROM jg_zz_interest_batches_all WHERE transferred_flag = 'N' AND org_id = :p_org_id;

Reporting scenarios include aging analysis of pending interest batches, audit extraction of GL date assignments, and operational dashboards tracking batch throughput by operating unit.

Related Objects

The following objects are most directly coupled to this table through documented relationships:

  • JG_ZZ_INTEREST_INVOICES_ALL — the primary dependent child table; joins on INTEREST_BATCH_ID and ORG_ID. Each interest invoice belongs to exactly one batch.
  • JG_ZZ_INTEREST_BATCHES_PK — the primary key constraint enforcing batch uniqueness.
  • JG_ZZ_INTEREST_BATCHES_U1 — the unique business-key index supporting batch lookup.
  • Interest calculation and invoice generation concurrent programs within the JG localization module, which populate and consume this table.
  • General Ledger interface objects downstream of the GL_DATE column for accounting transfer.

Together these objects form the interest-batch hierarchy used across Latin American localization deployments in EBS 12.1.1 and 12.2.2.