Results for “je_de_ap_batches”

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

Overview

JE_DE_AP_BATCHES is a table owned by the AP (Payables) schema within the JE – European Localizations product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The table is documented as VALID and carries a single, narrow purpose: it stores the checkrun names for which German separate payment letters (Einzelleistungsnachweis) have already been printed. This table is therefore a control or tracking object tied to the German localization of the Oracle Payables payment process, ensuring that a payment letter is not regenerated for a checkrun that has already been processed.

The ETRM metadata classifies this object heuristically as a standalone Data Vault entity. From a modeling standpoint, given that the table holds a single business attribute (the checkrun name) acting as its own unique key and has no documented foreign key relationships, it is best understood as a reference or control list rather than a hub, link, or satellite in a full Data Vault sense. If modeled in Data Vault terms, it would behave as a small standalone hub keyed on the checkrun name, with no dependent satellites or links defined in the documented schema.

Key Information Stored

The documented physical schema for this table contains only one column: CHECKRUN_NAME. The primary key constraint, JE_DE_AP_BATCHES_PK, is defined on CHECKRUN_NAME, and a unique index, JE_DE_AP_BATCHES_U1, is also defined on the same column. There is no separate surrogate primary key column and no additional business-key candidate distinct from the primary key; the checkrun name serves simultaneously as the primary key, the unique index, and the sole business attribute.

• CHECKRUN_NAME — the identifier of the Oracle Payables checkrun (payment batch run) for which German separate payment letters have been printed. It functions as the primary key (JE_DE_AP_BATCHES_PK) and as the unique business key (JE_DE_AP_BATCHES_U1).

Because the documentation lists only this single column, no other attributes such as print dates, user identifiers, or printer names are confirmed as part of the physical schema. Any consumption of the table should assume that its sole meaningful datum is the presence or absence of a given checkrun name.

Common Use Cases and Queries

The primary use case is determining whether the German separate payment letters have already been generated for a given checkrun, typically to prevent duplicate printing. A reporting or validation query takes the following form:

• Existence check: SELECT CHECKRUN_NAME FROM AP.JE_DE_AP_BATCHES WHERE CHECKRUN_NAME = :p_checkrun_name;
• Listing processed checkruns: SELECT CHECKRUN_NAME FROM AP.JE_DE_AP_BATCHES ORDER BY CHECKRUN_NAME;
• Reconciliation against payment batches: joining to AP payment batch tables to identify checkruns that have not yet had letters printed.

Typical business scenarios include reprint control during the German payment letter process, audit confirmation that localization output was produced for a specific checkrun, and troubleshooting when a payment letter appears to be missing or duplicated. Because the table is small and narrow, queries against it are inexpensive and are generally used as a gating lookup rather than as a source of transactional detail.

Related Objects

The documented metadata does not include explicit foreign keys, consistent with its standalone classification. The following related objects are the most operationally significant in the context of the German separate payment letter process:

• AP.JE_DE_AP_BATCHES_PK — the primary key constraint defined on CHECKRUN_NAME, enforcing uniqueness of each tracked checkrun.
• AP.JE_DE_AP_BATCHES_U1 — the unique index on CHECKRUN_NAME, supporting both the primary key and business-key lookups.
• AP_CHECK_STOCKS and AP_PAYMENT_SCHEDULES — payment components associated with the checkrun referenced by CHECKRUN_NAME.
• IBY_PAY_INSTRUCTIONS and IBY_PAYMENTS_ALL — payment instruction and payment records underlying the checkrun and its letters.
• AP_INV_SELECTION_CRITERIA_ALL — selection criteria that generate the payment batches processed by the checkrun.
• FND_CONCURRENT_REQUESTS — the concurrent program records that execute the German payment letter report.
• JE_DE_AP_BATCHES joins conceptually to AP payment batch/checkrun identifiers, though no formal foreign key between these columns is documented in the ETRM metadata.