Results for “je_cz_eft_contracts_u1”

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

Overview

The AP.JE_CZ_EFT_CONTRACTS_ALL table is a multi-organization (denoted by the _ALL suffix) transactional data object within the Oracle E-Business Suite Payables (AP) schema. It stores the configuration and runtime state of Electronic Funds Transfer (EFT) contracts used by the Czech localization (JE product prefix) for outbound payment processing. Each row defines a payment contract between a paying organization and a client or beneficiary, including branch assignment, client identification, security codes, and the interval-tracking attributes that govern how payment batches and reference numbers are generated and sequenced.

The table participates in the standard EBS concurrency and audit framework, using the WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) plus the request-tracking columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) and ORG_ID for multi-org partitioning.

From a heuristic Data Vault perspective, the mined FK structure classifies this object as hub-leaning. It carries a single-column primary key and a foreign key to the branch reference table, suggesting it can be modeled as a hub for the EFT contract business key, with the descriptive and mutable interval attributes potentially separated into a satellite.

Key Information Stored

• CONTRACT_ID — Surrogate primary key (NUMBER 15) and the column backing the unique index JE_CZ_EFT_CONTRACTS_U1, which also serves as the business-key candidate.
• BRANCH_ID — Foreign key referencing AMS_DLG_BRANCHES_B, identifying the bank branch associated with the contract.
• CLIENT_NAME / CLIENT_NUMBER — Human-readable and numeric identifiers for the contract counterparty.
• SECURITY_FIXED_CODE — Contract-level security code used in Czech EFT file generation.
• AP_INTERVAL_START / AP_INTERVAL_END — Bounds of the application-level interval range tracked for the contract.
• INTERVAL_START / INTERVAL_END — Bounds of the active allocation interval.
• LAST_USED_INTERVAL / LAST_USED_TIMESTAMP — The interval number most recently consumed and the time it was used, supporting sequencing and audit.
• PREVIOUS_INTERVAL — The prior interval, useful for reconciliation of generated batches.
• LAST_BATCH_FORMATTED — Identifier of the last batch formatted for this contract.
• ORG_ID — Operating unit partition key.
• INACTIVE_DATE — Effective end date for the contract, if any.
• ATTRIBUTE_CATEGORY / ATTRIBUTE1..20 — Descriptive flexfield storage.

Common Use Cases and Queries

Typical reporting scenarios include identifying active contracts, auditing interval consumption, and reconciling EFT batches. A common pattern joins the contract to its branch and to allocation records:

SELECT c.contract_id, c.client_name, c.client_number,
       c.last_used_interval, c.last_used_timestamp,
       a.allocation_id, a.amount
  FROM ap.je_cz_eft_contracts_all c,
       ap.je_cz_cont_alloc_all a
 WHERE c.contract_id = a.contract_id
   AND c.org_id = :p_org_id
   AND (c.inactive_date IS NULL OR c.inactive_date > SYSDATE);

Other use cases include monitoring LAST_USED_TIMESTAMP to detect stalled contracts, comparing LAST_USED_INTERVAL against AP_INTERVAL_END to flag exhausted sequences, and driving the EFT batch formatter by reading SECURITY_FIXED_CODE and BRANCH_ID. Because the table is partitioned by ORG_ID, all queries should include the operating-unit predicate when run outside a multi-org session.

Related Objects

• AP.JE_CZ_CONT_ALLOC_ALL — Child allocation table; joins on CONTRACT_ID.
• AMS_DLG_BRANCHES_B — Branch master; joined via BRANCH_ID to obtain branch metadata.
• JE.JE_CZ_EFT_CONTRACTS_ALL — FND design-data registration for the entity.
• AP.JE_CZ_EFT_CONTRACTS_U1 — Unique index on CONTRACT_ID supporting lookups and FK enforcement.
• AP.JE_CZ_EFT_CONTRACTS_ALL_PK — Primary-key constraint on CONTRACT_ID.
• Payables EFT payment APIs — Consume contract rows during Czech EFT file generation and validation.