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.
MEDIUM_ID— The surrogate primary key, enforced byJE_NL_EFT_MEDIA_PK. It uniquely identifies each medium record.MEDIUM_IDENTIFICATION— A business-key candidate, protected by the unique indexJE_NL_EFT_MEDIA_U1alongsideMEDIUM_ID. It provides the externally recognizable identifier for the medium.MEDIUM_TYPE— Classifies the medium (for example the physical or logical delivery channel used for the bank submission).BATCH_FORMAT— Identifies the file or record layout used when the EFT document is produced.MEDIUM_NUMBER— The sequence or reference number assigned to the medium.EFT_USER_NUMBER— The user or subscriber number associated with the EFT transmission.DATE_GENERATED,DATE_DUPLICATE,DATE_SENT— Lifecycle timestamps recording when the medium was generated, duplicated, and transmitted.NOTES— Free-form descriptive or operational commentary.JE_NL_EFT_MEDIA_BATCH_ID— The foreign-key column referencingJE_NL_EFT_BATCHES.- Audit columns —
CREATION_DATE,CREATED_BY,LAST_UPDATE_DATE,LAST_UPDATED_BY,LAST_UPDATE_LOGIN— support standard EBS audit tracking.
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 throughJE_NL_EFT_MEDIA.JE_NL_EFT_MEDIA_BATCH_ID. It also references back to the medium via itsMEDIUM_IDcolumn, forming a bidirectional relationship.JE_NL_EFT_MEDIA_PK— The primary-key constraint onMEDIUM_ID.JE_NL_EFT_MEDIA_U1— The unique index onMEDIUM_IDandMEDIUM_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.
-
Table: JE_NL_EFT_MEDIA
12.1.1
owner:AP, object_type:TABLE, fnd_design_data:JE.JE_NL_EFT_MEDIA, object_name:JE_NL_EFT_MEDIA, status:VALID, product: JE - European Localizations , description: Media information for creating Dutch EFT documents , implementation_dba_data: AP.JE_NL_EFT_MEDIA ,
-
Table: JE_NL_EFT_MEDIA
12.2.2
owner:AP, object_type:TABLE, fnd_design_data:JE.JE_NL_EFT_MEDIA, object_name:JE_NL_EFT_MEDIA, status:VALID, product: JE - European Localizations , description: Media information for creating Dutch EFT documents , implementation_dba_data: AP.JE_NL_EFT_MEDIA ,
-
SYNONYM: APPS.JE_NL_EFT_MEDIA
12.2.2
owner:APPS, object_type:SYNONYM, object_name:JE_NL_EFT_MEDIA, status:VALID,
-
VIEW: AP.JE_NL_EFT_MEDIA#
12.2.2
-
SYNONYM: APPS.JE_NL_EFT_MEDIA
12.1.1
owner:APPS, object_type:SYNONYM, object_name:JE_NL_EFT_MEDIA, status:VALID,
-
VIEW: AP.JE_NL_EFT_MEDIA#
12.2.2
owner:AP, object_type:VIEW, object_name:JE_NL_EFT_MEDIA#, status:VALID,
-
TABLE: AP.JE_NL_EFT_MEDIA
12.2.2
owner:AP, object_type:TABLE, fnd_design_data:JE.JE_NL_EFT_MEDIA, object_name:JE_NL_EFT_MEDIA, status:VALID,
-
TABLE: AP.JE_NL_EFT_MEDIA
12.1.1
owner:AP, object_type:TABLE, fnd_design_data:JE.JE_NL_EFT_MEDIA, object_name:JE_NL_EFT_MEDIA, status:VALID,
-
Table: JE_NL_EFT_BATCHES
12.1.1
owner:AP, object_type:TABLE, fnd_design_data:JE.JE_NL_EFT_BATCHES, object_name:JE_NL_EFT_BATCHES, status:VALID, product: JE - European Localizations , description: Dutch EFT payment batches , implementation_dba_data: AP.JE_NL_EFT_BATCHES ,
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
Table: JE_NL_EFT_BATCHES
12.2.2
owner:AP, object_type:TABLE, fnd_design_data:JE.JE_NL_EFT_BATCHES, object_name:JE_NL_EFT_BATCHES, status:VALID, product: JE - European Localizations , description: Dutch EFT payment batches , implementation_dba_data: AP.JE_NL_EFT_BATCHES ,
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.1.1 FND Design Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.2.2 FND Design Data
12.2.2
-
View: JE_NL_EFT_BATCHES_V
12.1.1
product: JE - European Localizations , implementation_dba_data: Not implemented in this database ,
-
View: JE_NL_EFT_BATCHES_V
12.2.2
product: JE - European Localizations , implementation_dba_data: Not implemented in this database ,
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
eTRM - JE Tables and Views
12.1.1
-
eTRM - JE Tables and Views
12.2.2
-
eTRM - JE Tables and Views
12.1.1
-
eTRM - JE Tables and Views
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1