Results for “je_cz_cont_alloc_all”

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

Overview

The table JE_CZ_CONT_ALLOC_ALL is a localization artifact within the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 environment, owned by the AP schema and registered under the JE – European Localizations product family. Its documented purpose is to associate a bank account with a Compatible Media contract, reflecting the Czech-specific electronic payment and tax-compliant cash register (Compatible Media) requirements. The relationship is expressly cardinal: a single contract may relate to one or more bank accounts, meaning this table functions as an allocation or mapping intersection between a contract header and one or more financial institution accounts.

The ETRM metadata records a primary key named JE_CZ_CONT_ALLOC_ALL_PK defined on BANK_ACCOUNT_ID, and a foreign key from JE_CZ_CONT_ALLOC_ALL.CONTRACT_ID to JE_CZ_EFT_CONTRACTS_ALL. Following Data Vault heuristic classification, this object is satellite-leaning: its grain is keyed to a bank account identifier, while the contract relationship is carried as a foreign reference. A satellite classification is a reasonable modeling suggestion, though the presence of a twenty-column ATTRIBUTE1–ATTRIBUTE20 descriptive block and standard audit columns reinforces that this is a descriptive, attribute-bearing table rather than a pure link.

Key Information Stored

The table is documented with 30 physical columns. The most operationally significant include:

• BANK_ACCOUNT_ID – the documented primary key column and the surrogate identifier anchoring each allocation row to a specific bank account. Because it is the sole PK member, it is the controlling unique key of the table.
• CONTRACT_ID – foreign key referencing JE_CZ_EFT_CONTRACTS_ALL; the business-key candidate linking the allocation to its Compatible Media contract.
• ORG_ID – multi-org operating unit discriminator, enabling the allocation to be scoped to a legal entity or business unit.
• INACTIVE_DATE – effective-end dating for the allocation, allowing historical or superseded bank-account associations to be preserved.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard EBS concurrent-manager audit columns capturing who created and updated each row and when.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 – the descriptive flexfield block used for Czech-localization-specific extension attributes.

The composite of BANK_ACCOUNT_ID and CONTRACT_ID is the practical business key candidate, since the allocation exists precisely to join these two entities.

Common Use Cases and Queries

Typical scenarios involve reporting which bank accounts are allocated to a given Compatible Media contract, and validating that an active allocation exists before an electronic payment is generated. Because INACTIVE_DATE supports time-bounded validity, queries frequently filter on it to obtain the current allocation set.

A representative query listing active allocations for a contract:

• SELECT alloc.bank_account_id, alloc.contract_id, alloc.org_id, alloc.inactive_date
• FROM ap.je_cz_cont_alloc_all alloc
• WHERE alloc.contract_id = :p_contract_id
• AND (alloc.inactive_date IS NULL OR alloc.inactive_date > SYSDATE);

Reporting use cases include reconciliation of Czech electronic payment bank accounts against contract setup, audit trails of allocation changes via the audit columns, and joins to JE_CZ_EFT_CONTRACTS_ALL to combine allocation details with contract header information. The flexfield attributes may be queried when localization-specific data has been configured.

Related Objects

The most significant dependent and referenced objects are:

• JE_CZ_EFT_CONTRACTS_ALL – the parent contract table, joined on JE_CZ_CONT_ALLOC_ALL.CONTRACT_ID = JE_CZ_EFT_CONTRACTS_ALL.CONTRACT_ID.
• JE_CZ_CONT_ALLOC_ALL_PK – the primary key constraint/index on BANK_ACCOUNT_ID.
• AP.JE_CZ_CONT_ALLOC_ALL – the schema-qualified object reference as documented.
• Bank account and payment-related AP objects referenced through BANK_ACCOUNT_ID.
• Oracle Application Object Library (FND) flexfield and audit infrastructure underlying ATTRIBUTE_CATEGORY and the audit columns.