Results for “bank_code”

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

Overview

The JE_DK_PAY_CATEGORIES table is an AP-schema object delivered as part of the JE – European Localizations product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores payment categories and their descriptive attributes, and functions as a configuration reference source for Danish and broader European localization payment processing, including remittance formats that require standardized payment means, channels, and settlement codes. The table is documented as VALID in the ETRM repository with 17 columns and a single primary key, JE_DK_PAY_CATEGORIES_PK, defined on PAYMENT_CATEGORY_ID.

Under the heuristic Data Vault classification mined from foreign-key structure, this table is identified as standalone. As a modeling suggestion, this implies the table holds reference or setup data that is not tightly bound through declarative foreign keys to transactional hubs or links, and it can reasonably be treated as an independent reference set rather than a satellite attached to an upstream hub. Implementers designing a Data Vault or warehouse layer should validate this classification against actual runtime referential usage, since payment category references may be resolved by application logic rather than database constraints.

Key Information Stored

The documented physical schema contains 17 columns. The most significant are listed below.

• PAYMENT_CATEGORY_ID – Surrogate primary key. It is also documented as a unique index candidate via JE_DK_PAY_CATEGORIES_U1, making it the only documented business-key candidate in the table.
• PAYMENT_CATEGORY – The user-facing category name or code that classifies a payment for reporting and localization processing.
• PAYMENT_MEANS – The instrument used to settle the payment, such as bank transfer or other localized means.
• PAYMENT_CHANNEL – The channel through which the payment is initiated or delivered.
• AGREEMENT_TYPE – The agreement classification associated with the payment category.
• PARTY_ID – Identifier of the party (typically supplier or payee) linked to the category.
• SETTLEMENT_CODE – Localization-specific code used in settlement or clearing processing.
• IMPORT_CODE and IMPORT_MONTH – Codes and month references supporting imported payment data, commonly used in Danish localization reporting.
• BANK_CODE – Bank identifier relevant to payment routing and localization validation.
• FOREIGN_PAYMENT_FLAG – Indicates whether the payment category represents a foreign or cross-border payment.
• SUPPLIER_MESSAGE – Free-text message conveyed to or from the supplier as part of the payment instruction.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard EBS audit columns capturing who created and last modified the row and when.

Common Use Cases and Queries

Typical uses include validating that a payment has been assigned a recognized category, reporting on foreign versus domestic payment volumes, and extracting settlement and import codes for localization reporting. A simple lookup by surrogate key is:

SELECT payment_category, payment_means, payment_channel
FROM ap.je_dk_pay_categories
WHERE payment_category_id = :p_id;

A report of foreign payments by category could be written as:

SELECT payment_category, bank_code, settlement_code
FROM ap.je_dk_pay_categories
WHERE foreign_payment_flag = 'Y';

Because the table is standalone, queries generally join to it by PAYMENT_CATEGORY_ID from localization-specific or custom staging tables rather than through enforced constraints. This makes it a reliable reference source for setup validation and for populating payment instruction templates.

Related Objects

The documented metadata records no enforced foreign-key relationships to or from this table, consistent with its standalone classification. Consequently, related objects are referenced through the surrogate key rather than declarative constraints. The most significant associated objects are:

• AP.JE_DK_PAY_CATEGORIES_PK – Primary key constraint on PAYMENT_CATEGORY_ID.
• AP.JE_DK_PAY_CATEGORIES_U1 – Unique index on PAYMENT_CATEGORY_ID, the documented business-key candidate.
• AP.AP_SUPPLIERS – Supplier master; the PARTY_ID value in the payment category can be correlated with supplier party identifiers.
• AP.AP_INVOICES_ALL – Invoices whose payment processing may be classified against a payment category.
• AP.AP_CHECKS_ALL – Payment records that consume payment means and channel attributes.
• AP.IBY_PAYMENTS – Payments architecture records that may be mapped to localization payment categories.
• JE localization setup and remittance views – Reporting objects that resolve SETTLEMENT_CODE, IMPORT_CODE, and BANK_CODE for Danish and European formats.

Any join to these objects should be performed explicitly on the relevant payment or party identifier, as no database-enforced relationships are documented.