Search Results je_nl_eft_batches
Overview
The JE_NL_EFT_BATCHES table, owned by the AP schema, stores Dutch Electronic Funds Transfer (EFT) payment batch definitions within the JE — European Localizations product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a core component of the Netherlands localization that enables Payables to consolidate payment instructions into a single bank transmission file. Each row represents one EFT batch — typically aligned to a payment process request or checkrun — and carries both aggregation totals and formatting attributes required to render the Dutch EFT output file.
Under the heuristic Data Vault classification provided in the ETRM metadata, this table is hub-leaning: its primary key (BATCH_ID) is a stable, non-business surrogate, and the table serves as a central anchor to which descriptive detail and media-related attributes attach. This classification is a modeling suggestion only; the physical table itself remains a conventional AP transactional entity.
Key Information Stored
The table contains 19 documented columns. The most significant are:
BATCH_ID— the surrogate primary key (JE_NL_EFT_BATCHES_PK); uniquely identifies each EFT batch and is the column referenced by child tables.CHECKRUN_NAME— a business-key candidate (unique indexJE_NL_EFT_BATCHES_U1); the payment batch or checkrun identifier to which the EFT batch corresponds.MEDIUM_IDandMEDIUM_SEQNO— together form the unique indexJE_NL_EFT_BATCHES_U3, and link the batch to the physical medium (tape, diskette, or file) defined inJE_NL_EFT_MEDIA.BATCH_FORMAT— the file/record layout used when the batch is written.DATE_CREATED— the date the EFT batch was generated.PAYER_BANK_ACCOUNT— the disbursement bank account from which payments in the batch originate.TOT_PAYMENTS,TOT_PAYMENT_AMOUNT,TOT_RECORDS,TOT_BANK_ACCOUNTS— aggregation totals for payment count, monetary value, record count, and number of distinct beneficiary bank accounts.NO_OF_CANCELLATIONS— count of payments voided or cancelled within the batch.FIRST_PAYMENT_NUMBERandLAST_PAYMENT_NUMBER— the range of payment document numbers encompassed.- Standard audit columns:
CREATION_DATE,CREATED_BY,LAST_UPDATE_DATE,LAST_UPDATED_BY,LAST_UPDATE_LOGIN.
Common Use Cases and Queries
Typical usage centers on reconciliation, audit, and reporting of Dutch EFT transmissions. A common query pattern retrieves the summary totals for a given checkrun:
SELECT batch_id, checkrun_name, tot_payments, tot_payment_amount, no_of_cancellations FROM je_nl_eft_batches WHERE checkrun_name = :p_checkrun;- Joining to
JE_NL_EFT_MEDIAviaMEDIUM_IDto obtain medium-level detail for a batch. - Audit reports that compare
TOT_PAYMENT_AMOUNTagainst summedAP_PAYMENT_SCHEDULESvalues to verify completeness before transmission. - Queries by
PAYER_BANK_ACCOUNTto consolidate all Dutch EFT activity per disbursement account.
Because CHECKRUN_NAME is unique, it is the most practical business identifier for user-facing lookups, while BATCH_ID should be used for programmatic joins.
Related Objects
- JE_NL_EFT_MEDIA — referenced by
MEDIUM_ID; conversely,JE_NL_EFT_MEDIA.JE_NL_EFT_MEDIA_BATCH_IDreferences this table'sBATCH_ID, forming a bidirectional relationship. - AP_PAYMENT_SCHEDULES / AP_CHECKS — source of the underlying payments aggregated into each batch, linked via checkrun and payment identifiers.
- AP_BANK_ACCOUNTS — provides the disbursement account referenced by
PAYER_BANK_ACCOUNT. - IBY_PAYMENT_INSTRUCTIONS — upstream payment instruction data feeding Dutch EFT formatting.
Together these objects form the Dutch EFT processing chain within Oracle Payables.
-
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 ,
-
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 ,
-
SYNONYM: APPS.JE_NL_EFT_BATCHES
12.1.1
owner:APPS, object_type:SYNONYM, object_name:JE_NL_EFT_BATCHES, status:VALID,
-
VIEW: AP.JE_NL_EFT_BATCHES#
12.2.2
owner:AP, object_type:VIEW, object_name:JE_NL_EFT_BATCHES#, status:VALID,
-
SYNONYM: APPS.JE_NL_EFT_BATCHES
12.2.2
owner:APPS, object_type:SYNONYM, object_name:JE_NL_EFT_BATCHES, status:VALID,
-
VIEW: AP.JE_NL_EFT_BATCHES#
12.2.2
-
TABLE: AP.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,
-
TABLE: AP.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,
-
12.2.2 DBA Data
12.2.2
-
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 ,
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 FND Design Data
12.1.1
-
12.2.2 FND Design Data
12.2.2
-
View: JE_NL_EFT_BATCHES_V
12.2.2
product: JE - European Localizations , implementation_dba_data: Not implemented in this database ,
-
View: JE_NL_EFT_BATCHES_V
12.1.1
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