Search Results je_nl_eft_media




Overview

The AP.JE_NL_EFT_MEDIA table is a European Localizations (JE) data object that stores media information used to generate Dutch Electronic Funds Transfer (EFT) documents. It resides in the AP (Payables) schema and is classified as VALID in the ETRM metadata for Oracle EBS 12.1.1 and 12.2.2. The table holds the definition and status of each EFT transmission medium — the physical or logical carrier through which a batch of Dutch payment instructions is delivered to the bank or clearing institution. Each medium record ties a set of payment batches to a specific delivery mechanism, format, and lifecycle state.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this table as satellite-leaning. The single foreign key to JE_NL_EFT_BATCHES and the presence of descriptive, mutable attributes (dates, notes, numbers, formats) indicate a descriptive satellite attached to a parent business entity rather than an independent hub or an associative link.

Key Information Stored

The table is documented with 15 physical columns. The most significant are summarized below.

Common Use Cases and Queries

Typical usage centers on tracking the status of Dutch EFT submissions and reconciling generated media against their parent batches. A representative query joins the medium to its batch:

  • Locating media by identification or type: SELECT MEDIUM_ID, MEDIUM_TYPE, BATCH_FORMAT, DATE_SENT FROM AP.JE_NL_EFT_MEDIA WHERE MEDIUM_IDENTIFICATION = :p_id;
  • Auditing transmission status: SELECT MEDIUM_ID, DATE_GENERATED, DATE_SENT FROM AP.JE_NL_EFT_MEDIA WHERE DATE_SENT IS NULL;
  • Joining medium to batch: SELECT m.MEDIUM_ID, m.BATCH_FORMAT, b.* FROM AP.JE_NL_EFT_MEDIA m, AP.JE_NL_EFT_BATCHES b WHERE m.JE_NL_EFT_MEDIA_BATCH_ID = b.<batch_key>;

These patterns support operational dashboards, bank-submission reconciliation reports, and audit extracts for Dutch localization payment cycles.

Related Objects

  • JE_NL_EFT_BATCHES — The parent table referenced through JE_NL_EFT_MEDIA.JE_NL_EFT_MEDIA_BATCH_ID. It also references back to the medium via its MEDIUM_ID column, forming a bidirectional relationship.
  • JE_NL_EFT_MEDIA_PK — The primary-key constraint on MEDIUM_ID.
  • JE_NL_EFT_MEDIA_U1 — The unique index on MEDIUM_ID and MEDIUM_IDENTIFICATION, serving as the business-key candidate.

Because the documented metadata is limited to the AP schema and the batch dependency, the most significant dependent object is JE_NL_EFT_BATCHES; broader Dutch EFT functionality (payment formatting and bank submission) typically operates through the European Localizations payment APIs that consume these records.