Search Results jenl_mediumcode

Overview

The view JE_NL_EFT_BATCHES_V belongs to the JE – European Localizations product family within Oracle E-Business Suite, specifically supporting the Dutch (NL) electronic funds transfer (EFT) localizations delivered under the European globalization track. The view consolidates payment batch information for electronic funds transfers generated through Oracle Payables, exposing a denormalized, human-readable representation of EFT batch activity alongside related bank, check format, medium, and status attributes.

Its primary role is to serve as a reporting and inquiry surface for payment runs processed through the Dutch EFT medium. Rather than joining numerous Payables and localization tables manually, reporting tools, custom concurrent programs, and functional inquiries can select from this view directly. Because the view joins to AP_INVOICE_SELECTION_CRITERIA and related bank master tables, it is particularly useful for reconciling payment batch totals, cancellation counts, and first/last payment number ranges against the corresponding check run. The user's search term date_created maps directly to the DATE_CREATED column, which is exposed as TRUNC(JNEB.DATE_CREATED), meaning the time component is intentionally stripped to promote day-level grouping and reporting.

Underlying Base Objects

The documented view text defines JE_NL_EFT_BATCHES_V as a join across the following base objects:

• JE_NL_EFT_BATCHES (alias JNEB) — the driving table containing EFT batch header information.
• JE_NL_EFT_MEDIA (alias M) — the generated medium (tape/file) records, outer-joined via M.MEDIUM_ID(+) = JNEB.MEDIUM_ID.
• AP_INVOICE_SELECTION_CRITERIA (alias ISC) — the payment selection/check run criteria, joined on CHECKRUN_NAME.
• AP_CHECK_STOCKS (CS) and AP_CHECK_FORMATS (CF) — joined via CHECK_STOCK_ID and CHECK_FORMAT_ID to derive the payment format name.
• AP_BANK_ACCOUNTS (BA) and AP_BANK_BRANCHES (BB) — joined to expose bank account and branch descriptive attributes.
• FND_LOOKUPS (L) — outer-joined on MEDIUM_TYPE with LOOKUP_TYPE = 'JENL_MEDIUMCODE' to translate the medium code into a meaningful description.

Note that the ETRM metadata records no implemented base objects in the referenced database, indicating the view is documented from source rather than an installed instance. All joins are effectively inner joins except for the medium and lookup joins, which are outer joins.

Key Columns

Among the most significant columns are:

• DATE_CREATED — the truncated creation date of the EFT batch; the principal filter/grouping attribute when users search on "date_created".
• BATCH_ID and CHECKRUN_NAME — the batch identifier and its associated Payables check run.
• TOT_PAYMENT_AMOUNT, TOT_PAYMENTS, TOT_RECORDS — aggregate totals for value, payment count, and record count.
• NO_OF_CANCELLATIONS — number of cancelled payments within the batch.
• FIRST_PAYMENT_NUMBER / LAST_PAYMENT_NUMBER — payment number range boundaries.
• MEDIUM_ID, MEDIUM_SEQNO, MEDIUM_IDENTIFICATION, MEDIUM_TYPE — medium identification and its decoded lookup meaning.
• STATUS, CHECK_DATE, CURRENCY_CODE — selection criteria status and currency context.
• BANK_NUMBER, BANK_ACCOUNT_NAME, BANK_NAME, PAYMENT_FORMAT — descriptive bank and format attributes.
• DATE_GENERATED, DATE_DUPLICATE, DATE_SENT — medium lifecycle timestamps, all truncated.

Common Use Cases and Queries

Typical usage includes reconciling EFT batches for a given day, auditing cancellations, and tracing medium generation status. A representative query filtering on the creation date is:

• SELECT batch_id, checkrun_name, date_created, tot_payment_amount, tot_payments, status FROM je_nl_eft_batches_v WHERE date_created = TRUNC(SYSDATE);
• SELECT medium_identification, medium_type, date_generated, date_sent, count(*) FROM je_nl_eft_batches_v GROUP BY medium_identification, medium_type, date_generated, date_sent;
• SELECT checkrun_name, no_of_cancellations, first_payment_number, last_payment_number FROM je_nl_eft_batches_v WHERE no_of_cancellations > 0;

Because DATE_CREATED is truncated, date-range predicates should compare against truncated values to ensure index-friendly, precise filtering.